Explaination of Messages (Debug verbosity 2)

[keo_video]

I was wondering if someone could help me understand the following input.
I am trying to see what the thread time means. IE real, kernel, user.

I am also trying to figure out if i launch with a cache of 100ms if there is any other latency due to vlc happening in the background.

I tried to figure this out from looking at the developers information at doxygen but i was unable.

Thank you for any help or advise.

main debug: thread times: real 147m39.645956s, kernel 11m21.171875s, user 6m22.765625s
main debug: thread 5520 joined (playlist/engine.c:244)
main debug: TIMER input launching for 'rtp://@192.168.1.30:10000' : 79.000 ms - Total 79.000 ms / 1 intvls (Avg 79.000 ms)
main debug: starting new item
main debug: processing request item rtp://@192.168.1.30:10000 node Playlist skip 0
main debug: resyncing on rtp://@192.168.1.30:10000
main debug: rtp://@192.168.1.30:10000 is at 0
main debug: creating new input thread
main debug: Creating an input for 'rtp://@192.168.1.30:10000'
main debug: waiting for thread initialization
main debug: thread started
main debug: thread 5508 (input) created at priority 1 (input/input.c:370)
qt4 debug: Updating the stream status: 3
main debug: `rtp://@192.168.1.30:10000' gives access `rtp' demux `' path `@192.168.1.30:10000'
main debug: creating demux: access='rtp' demux='' path='@192.168.1.30:10000'
main debug: looking for access_demux module: 1 candidate
main debug: net: opening 192.168.1.30 datagram port 10000
main debug: net: opening 192.168.1.30 datagram port 10001
main debug: using access_demux module "rtp"
main debug: TIMER module_Need() : 9.000 ms - Total 9.000 ms / 1 intvls (Avg 9.000 ms)
main debug: looking for a subtitle file in C:\Program Files\VideoLAN\VLC\
main debug: `rtp://@192.168.1.30:10000' successfully opened
rtp debug: detected MPEG2 TS
rtp debug: added payload type 33 (f = 90000 Hz)
main debug: thread 5652 (stream out) created at priority 1 (input/demux.c:358)
rtp debug: added RTP source (00000000)
main debug: control type=1
main debug: thread started
main debug: creating demux: access='' demux='ts' path=''
main debug: looking for demux module: 1 candidate
main debug: using demux module "ts"
main debug: TIMER module_Need() : 3.000 ms - Total 3.000 ms / 1 intvls (Avg 3.000 ms)
ts debug: pid[49] unknown
qt4 debug: New Event: type 1103
qt4 debug: Updating the stream status: 3
ts debug: PATCallBack called
ts debug: new PAT ts_id=1 version=0 current_next=1
ts debug: * number=2 pid=63
ts debug: PMTCallBack called
ts debug: new PMT program number=2 version=0 pid_pcr=49
ts debug: * es pid=49 type=2 fcc=mpgv
main debug: selecting program id=2
qt4 debug: New Event: type 1108
main debug: looking for decoder module: 34 candidates
main debug: using decoder module "libmpeg2"
main debug: TIMER module_Need() : 1.000 ms - Total 1.000 ms / 1 intvls (Avg 1.000 ms)
main debug: thread 5688 (decoder) created at priority 0 (input/decoder.c:217)
main debug: thread started
ts warning: first packet for pid=49 cc=0xc
libmpeg2 debug: 1920x1080 (display 1920,1080), aspect 768000, sar 1:1, 29.971 fps
main debug: no usable vout present, spawning one
main debug: window size: 1920x1080
main debug: looking for video output module: 6 candidates
vout_directx debug: creating DirectXEventThread
main debug: waiting for thread initialization
main debug: thread started
vout_directx debug: DirectXCreateWindow
main debug: looking for vout window module: 2 candidates
qt4 debug: waiting for interface...
qt4 debug: requesting window...
qt4 debug: Video was requested -1, -1
qt4 debug: Video is resizing to: 1920 1080
qt4 debug: Qt FS: Attaching Vout
qt4 debug: Qt: Changing Fullscreen Mode
main debug: using vout window module "qt4"
main debug: TIMER module_Need() : 64.000 ms - Total 64.000 ms / 1 intvls (Avg 64.000 ms)
vout_directx debug: created video sub-window
main debug: thread 5844 (Vout Events Thread) created at priority 0 (directx.c:281)
vout_directx debug: Vout EventThread running
vout_directx debug: DirectXInitDDraw
qt4 debug: Updating the geometry
vout_directx debug: directx-device:
vout_directx debug: DirectXEnumCallback: Primary Display Driver, display
vout_directx debug: DirectXEnumCallback: NVIDIA GeForce 8600M GT, \\.\DISPLAY1
vout_directx debug: selecting NVIDIA GeForce 8600M GT, \\.\DISPLAY1
vout_directx debug: screen dimensions (0x0,1920x1200)
vout_directx debug: DirectDraw Capabilities: overlay=1 yuvoverlay=1 can_deinterlace_overlay=1 colorkey=1 stretch=1 bltfourcc=1
vout_directx debug: align_boundary_src=0,0 align_boundary_dest=1,1 align_size_src=0,0 align_size_dest=0,0
vout_directx debug: End DirectXInitDDraw
vout_directx debug: DirectXCreateDisplay
vout_directx debug: DirectXCreateClipper
vout_directx debug: disabling screen saver
main debug: using video output module "vout_directx"
main debug: TIMER module_Need() : 231.000 ms - Total 231.000 ms / 1 intvls (Avg 231.000 ms)
main debug: waiting for thread initialization
main debug: thread started
vout_directx debug: NewPictureVec overlay:yes chroma:YV12
vout_directx debug: YUV overlay created successfully
vout_directx debug: End NewPictureVec (succeeded)
main debug: got 1 direct buffer(s)
main debug: picture in 1920x1088 (0,0,1920x1080), chroma I420, ar 16:9, sar 1:1
main debug: picture user 1920x1088 (0,0,1920x1080), chroma I420, ar 16:9, sar 1:1
main debug: picture out 1920x1088 (0,0,1920x1080), chroma I420, ar 16:9, sar 1:1
main debug: direct render, mapping render pictures 0-6 to system pictures 1-7
main debug: thread 5744 (video output) created at priority 1 (video_output/video_output.c:502)
main warning: decoder synchro warning: pts != current_date (1023911)
qt4 debug: New Event: type 1109

[ivoire]

AFAIK:
real=how long the thread exist
kernel=how long the thread goes in the kernel (ie doing mostly I/O)
user=how long the thread compute in the user space (ie classical computation)

[keo_video]

Thank you very much.

I also have a question regarding the following line.

main debug: TIMER module_Need() : 9.000 ms - Total 9.000 ms / 1 intvls (Avg 9.000 ms)

Is the time above given as the time needed for the configuration of the module or the continued use?

Ie with the

main debug: using video output module "vout_directx"
main debug: TIMER module_Need() : 231.000 ms - Total 231.000 ms / 1 intvls (Avg 231.000 ms)

That 231 ms is only seen as a one time setup cost and then once the module is setup the time to write to the vout_directx would be processing time * pipe time.
And the time to viewing would be processing time * pipe time * video card latency * display latency ?

As always thank you very much for any help.

[ivoire]

"TIMER module_Need()" is the time needed by the function (module_need) to execute.