[ATrpms-users] Multiple problems with new vlc 0.9.2

[Jeffrey J. Kosowsky]

Paulo Cavalcanti wrote at about 13:53:57 -0300 on Monday, September 22, 2008:
 > On Mon, Sep 22, 2008 at 11:15 AM, Jeffrey J. Kosowsky
 > <atrpms at kosowsky.org>wrote:
 > 
 > > I am having multiple issues with the latest vlc 0.9.2
 > >
 > > 1. The option --m3u-extvlcopt is not recognized on the command line
 > 
 > 
 > This is a new major version update. Maybe this option is deprecated.
 > Why do you need this option?

I read through the changelog and didn't see any mention of it being
deprecated. On the CONTRARY, this option was added somewhere in the 0.8
series as a security measure allowing vlc to default to not accept
extended options in playlists. Before then, you didn't need to include
this option.

I find this capability VERY IMPORTANT since it allows me to write
general scripts for streaming that I can then interact with through
remote http by switching entries in the playlists. The extended
options allow me to switch between tuners (in addition to just
switching channels), such as between analog and digital signals.

 > 
 > 
 > 
 > >
 > > 2. The 'deinterlace' filter seems to be missing/broken:
 > >
 > >   [00000421] main interface: creating httpd
 > >   [00000427] main stream out error: Failed to create video filter2
 > >   'deinterlace'
 > >   [00000419] signals interface error: Caught Interrupt signal,
 > >   exiting...
 > 
 > 
 > The filter is there. Go to tools -> preferences and check "show settings" to
 > ALL.
 > 
 > Then choose video -> filters
 > 
 > Deinterlace has two modes: display (default : discard) and stream (default :
 > blend).

Is this a change?
Because before the following line worked:

:sout=#transcode{vcodec=$VCODEC,acodec=$ACODEC,vb=$VBITRATE,ab=$ABITRATE,scale=1,channels=1,fps=$FPS,deinterlace,audio-sync,width=$WIDTH}:std{access=$ACCESS,mux=$MUX,dst=$STREAM_PORT}

But now I am getting an error. Do I now need to specify one of the
modes? If so which one and how?

 > Are you streaming?
Yes I am. Can you help me understand why this matters and how this
affects deinterlacing?
Thanks!

 > 
 > 
 > >
 > > 3. Debugging code seems to be compiled in which results in a lot of
 > >   extra "messiness" being spewed on the screen.
 > 
 > 
 > Upstream should be using a more verbose debugging here, while this version
 > is still new.
 > 

I guess I wonder whether this is ready for prime time in atrpms or
whether it should still be in 'testing' if verbose debugging output is
still needed.

Of course, understand that none of the above is meant as criticism of
your fine efforts in adding to the diversity of atrpms!!! THANKS FOR
THE GREAT WORK AND SUPPORT.

 > 
 > -- 
 > Paulo Roma Cavalcanti
 > LCG - UFRJ