Page 1 of 1
Why break RTSP?
Posted: 08 Jan 2013 22:07
by fly135
RTSP with MPEG-4 used to work great with our encoder streams, but now it fails with the debug message...
"only real/helix rtsp servers supported for now"
Why break it intentionally?
John
Re: Why break RTSP?
Posted: 08 Jan 2013 22:28
by fly135
Whoops sorry, this message occurred when I had RTP over RTSP enabled and I am working on a bug that popped up with that feature.
For some reason the newer versions of VLC stopped decoding our MPEG-4. The debug messages show it receiving data but not decoding frames....
Code: Select all
main debug: processing request item: rtsp://192.168.1.5, node: Playlist, skip: 0
main debug: resyncing on rtsp://192.168.1.5
main debug: rtsp://192.168.1.5 is at 0
main debug: starting playback of the new playlist item
main debug: resyncing on rtsp://192.168.1.5
main debug: rtsp://192.168.1.5 is at 0
main debug: creating new input thread
main debug: Creating an input for 'rtsp://192.168.1.5'
main debug: using timeshift granularity of 50 MiB, in path 'C:\DOCUME~1\John\LOCALS~1\Temp'
main debug: `rtsp://192.168.1.5' gives access `rtsp' demux `' path `192.168.1.5'
main debug: creating demux: access='rtsp' demux='' location='192.168.1.5' file='\\192.168.1.5'
main debug: looking for access_demux module: 1 candidate
live555 debug: version 2011.12.23
qt4 debug: IM: Setting an input
live555 debug: RTP subsession 'video/MP4V-ES'
main debug: selecting program id=0
live555 debug: setup start: 0.000000 stop:0.000000
live555 debug: play start: 0.000000 stop:0.000000
main debug: using access_demux module "live555"
main debug: TIMER module_need() : 298.570 ms - Total 298.570 ms / 1 intvls (Avg 298.570 ms)
main debug: looking for decoder module: 31 candidates
avcodec debug: libavcodec already initialized
avcodec debug: trying to use direct rendering
avcodec debug: allowing 3 thread(s) for decoding
avcodec debug: ffmpeg codec (MPEG-4 Video) started
avcodec debug: using frame thread mode with 3 threads
main debug: using decoder module "avcodec"
main debug: TIMER module_need() : 1.916 ms - Total 1.916 ms / 1 intvls (Avg 1.916 ms)
main debug: looking for meta reader module: 2 candidates
lua debug: Trying Lua scripts in C:\Documents and Settings\John\Application Data\vlc\lua\meta\reader
lua debug: Trying Lua scripts in C:\Program Files\VideoLAN\VLC\lua\meta\reader
lua debug: Trying Lua playlist script C:\Program Files\VideoLAN\VLC\lua\meta\reader\filename.luac
main debug: no meta reader module matching "any" could be loaded
main debug: TIMER module_need() : 1.858 ms - Total 1.858 ms / 1 intvls (Avg 1.858 ms)
main debug: `rtsp://192.168.1.5' successfully opened
main debug: Buffering 0%
main debug: Buffering 3%
main debug: Buffering 6%
main debug: Buffering 10%
avcodec warning: disabling direct rendering
avcodec warning: cannot decode one frame (4471 bytes)
avcodec warning: cannot decode one frame (4880 bytes)
and so on.....
Re: Why break RTSP?
Posted: 08 Jan 2013 22:44
by fly135
It appears that the pre 2.xx VLC that do work also print the same seq of messages but stops after awhile with the message ....
"no usable vout present, spawning one"
Then the sequence of messages looks like...
Code: Select all
<snip a lot>...
avcodec warning: cannot decode one frame (3064 bytes)
main debug: Buffering 38%
avcodec warning: cannot decode one frame (8696 bytes)
main debug: no usable vout present, spawning one
main debug: looking for text renderer module: 2 candidates
freetype debug: Using Arial as font from file C:\WINDOWS\Fonts\ARIAL.TTF
freetype debug: using fontsize: 2
main debug: using text renderer module "freetype"
main debug: TIMER module_need() : 1.000 ms - Total 1.000 ms / 1 intvls (Avg 1.000 ms)
main debug: Buffering 41%
main debug: looking for video filter2 module: 18 candidates
swscale debug: 32x32 chroma: YUVA -> 16x16 chroma: YUVA with scaling using Bicubic (good quality)
main debug: using video filter2 module "swscale"
main debug: TIMER module_need() : 3.000 ms - Total 3.000 ms / 1 intvls (Avg 3.000 ms)
main debug: looking for video filter2 module: 18 candidates
yuvp debug: YUVP to YUVA converter
main debug: using video filter2 module "yuvp"
main debug: TIMER module_need() : 0.000 ms - Total 0.000 ms / 1 intvls (Avg 0.000 ms)
main debug: window size: 640x480
main debug: Deinterlacing available
main debug: deinterlace 0, mode blend, is_needed 0
main debug: looking for video output module: 1 candidate
vout_wrapper debug: Opening vout display wrapper
main debug: looking for vout display module: 8 candidates
directx debug: creating Vout EventThread
directx debug: DirectXCreateWindow
main debug: looking for vout window hwnd module: 3 candidates
qt4 debug: requesting video...
main debug: Buffering 44%
main debug: Buffering 47%
qt4 debug: Video was requested 0, 0
main debug: using vout window hwnd module "qt4"
main debug: TIMER module_need() : 71.000 ms - Total 71.000 ms / 1 intvls (Avg 71.000 ms)
directx debug: created video sub-window
directx debug: Vout EventThread running
directx debug: disabling screen saver
directx debug: directx-device:
directx debug: DirectXEnumCallback: NVIDIA Quadro PCI-E Series, \\.\DISPLAY1
directx debug: selecting NVIDIA Quadro PCI-E Series, \\.\DISPLAY1
main debug: Buffering 50%
directx debug: screen dimensions (0x0,1920x1080)
directx debug: DirectDraw Capabilities: overlay=1 yuvoverlay=1 can_deinterlace_overlay=1 colorkey=1 stretch=1 bltfourcc=1
directx debug: align_boundary_src=0,0 align_boundary_dest=1,1 align_size_src=0,0 align_size_dest=0,0
main debug: VoutDisplayEvent 'resize' 648x514 window
directx debug: YUV overlay surface created successfully
main debug: Buffering 52%
main debug: using vout display module "directx"
main debug: TIMER module_need() : 126.000 ms - Total 126.000 ms / 1 intvls (Avg 126.000 ms)
main debug: using video output module "vout_wrapper"
main debug: TIMER module_need() : 127.000 ms - Total 127.000 ms / 1 intvls (Avg 127.000 ms)
main debug: got 1 direct buffer(s)
main debug: pic render sz 352x480, of (0,0), vsz 352x480, 4cc I420, sar 20:11, msk r0x0 g0x0 b0x0
main debug: pic in sz 352x480, of (0,0), vsz 352x480, 4cc I420, sar 20:11, msk r0x0 g0x0 b0x0
main debug: pic out sz 352x480, of (0,0), vsz 352x480, 4cc I420, sar 20:11, msk r0x0 g0x0 b0x0
main debug: direct render, mapping render pictures 0-23 to system pictures 1-24
avcodec debug: using direct rendering
main debug: End of video preroll
main debug: Received first picture
main debug: VoutDisplayEvent 'resize' 640x480 window
main debug: Post-processing available
main warning: vlc_object_find_name(postproc) is not safe!
main debug: Buffering 55%
main debug: Buffering 58%
main debug: Buffering 61%
main debug: Buffering 63%
main debug: Buffering 66%
main debug: Buffering 69%
main debug: Buffering 72%
main debug: Buffering 75%
main debug: Buffering 77%
main debug: Buffering 80%
main debug: Buffering 83%
main debug: Buffering 86%
main debug: Buffering 88%
main debug: Buffering 91%
main debug: Buffering 94%
main debug: Buffering 97%
main debug: Stream buffering done (1201 ms in 1075 ms)
main debug: Decoder buffering done in 0 ms
freetype debug: using fontsize: 30
main debug: looking for video blending module: 1 candidate
blend debug: chroma: YUVA -> I420
main debug: using video blending module "blend"
main debug: TIMER module_need() : 1.000 ms - Total 1.000 ms / 1 intvls (Avg 1.000 ms)
main debug: auto hidding mouse
Re: Why break RTSP?
Posted: 08 Jan 2013 23:48
by Jean-Baptiste Kempf
Update to VLC 2.0.5.
If not, force threads to 1.
Re: Why break RTSP?
Posted: 09 Jan 2013 04:30
by fly135
2.0.5 hangs consuming max cpu for a single thread after buffering is complete. 2.0.3 works with threads=1.