It might be related to other problems that VLC 2.05 and later have with multiple monitors. Does it work correctly for you on version 2.04 or earlier? If the problems are related, then Jean-Baptiste Kempf says that the problem is not actually in VLC, but is in the version of Qt4 that they are using. ...
With multi-monitors, VLC forgets the monitor it was last displayed on and reverts to monitor 1, so that users can no longer have VLC automatically open on monitors 2, 3, 4, or higher. This previous post has the repro steps: https://forum.videolan.org/viewtopic.php?f=14&t=113150 Jean-Baptiste sai...
2.0.4 and earlier would correctly remember which monitor vlc was last opened on when vlc is maximized, 2.0.5 and later forget. Steps to reproduce the bug: 1) Do a clean install of 2.0.0 or later. 2) The first time the vlc window appears, move it to monitor 2. 3) Maximize the vlc window. 3) Exit vlc....
I just tested the nightly builds for 2.0.6 and 2.1.0, and they both work correctly, so apparently the bug in 2.0.5 has already been fixed in future versions. Oops. I just tested the release build of 2.0.6, and this bug from 2.0.5 has returned. In the nightly build of 2.0.6 on Jan. 11 the bug was fi...
Take this direct link, http://ftp.free.org/mirrors/videolan/vlc/2.0.6/win32/vlc-2.0.6-win32.exe I just downloaded this version and the version from the main page at www.videolan.org. They are different sizes, and the version from the main page is still broken. Why is the broken version still the &q...
More info: What works: A clean install of the nightly build of 2.0.6 from Jan 11, 2013. No problems. What fails: A clean install of the release build of 2.0.6. Nothing displays on the screen when running vlc at the end of installation, 1 cpu core is at 100%, and the memory usage climbed to over 2 GB...
Windows 7, 64-bit. Clean install of 2.0.6, no preferences, no cache. At the end of the installation process, when it should run vlc, nothing appears on the screen, and the vlc process is using 100% of one of the cores.
I just tested the nightly builds for 2.0.6 and 2.1.0, and they both work correctly, so apparently the bug in 2.0.5 has already been fixed in future versions.
I am having the same problem. Clean installs (no preferences, no cache) of 2.0.2 and 2.0.4 work correctly, a clean install of 2.0.5 does not work correctly. Reproduction steps: 1) Do a clean install of 2.0.2, 2.0.4, or 2.0.5. 2) The first time the vlc window appears, move it to monitor 2. 3) Exit vl...
Still no luck at creating file names from the Scene filter that can be parsed for starting time information so that VLC can be started at the location where the image was captured (e.g. via the --start-time option). Two other possibilities I've tried which seemed like they might work but I couldn't ...
Nope. It looks like VLC does not work as per the documentation at http://wiki.videolan.org/Documentation:Play_HowTo/Format_String . The doc says that format string variables can be used with "--scene-prefix in 1.0.0 and newer". However, after extensive testing, the format string variables ...
I think I may have solved my own problem. I think the information at http://wiki.videolan.org/Documentation:Play_HowTo/Format_String will be sufficient for me to figure out how to format the --scene-prefix string so that I can parse out sufficient information to start VLC at the time corresponding t...
Is there a way to use the image numbers from the file names generated by the Scene filter output module to start VLC playing at the image number where a selected image was generated? Or, alternatively, is there a setting that tells the Scene filter to encode the number of seconds where the image was...