The VideoLAN Forums

libvlc Version 2.0.3

I'm having an issue where if I run vlc as an application, and set the video output to glx, it works very smoothly, but if I attempt the same thing programmatically with libvlc, it goes a little chunky. If I try placing the --vout glx parameters, it doesn't appear to have any effect. I know it's reading the parameters, because if I leave off the glx part, it complains that I didn't put a mandatory parameter in.

If I put in --vout fb, I should get nothing visible, since it can't access the framebuffer while X is running, but I still get a display. (If I run vlc --vout fb, I properly get no display)

Since it appears to be totally ignoring whatever --vout parameter I put in there, I'm not sure exactly where the issue is.

I have tried a variety of parameter methods, to no avail. (ie: --vout glx, --vout xcb_glx, --vout xcb-glx, --vout=glx)

If you do not specify ",none", VLC will fallback to whatever else works. You probably mean --vout=glx,none. However, it is most recommended to let LibVLC choose its output. There is no warranty that a given vout plugin name will remain available in future versions.

I'm working on a fairly specific hardware setup, and basically at the limits of what it can perform. However the --vout parameter is being completely ignored from libvlc. (I can put --vout=fb,none which should fail emphatically, and it does not. I believe it is using x11 all the time) I am providing a mechanism to change this through the command-line, however I really do need it to use the glx right now as it's the only output that appears to run fast enough.

If you use libvlc_media_player, that's normal behaviour. It sets the vout variable internally.

Is there any way to override that? I am using libvlc_media_player currently.

Edit the code.

<sigh> I was hoping for a method that didn't involve using a special compile, but oh well. Thank you for your help.