Bug in timecode display on DVD playback?

[number42]

Hello!

Researched this in tickets/wiki/forum but haven't seen it addressed, maybe it's a new bug?

Versions 1.0.2 and 1.0.3 on Windows and Linux - I am playing certain DVDs such as Star Wars (episodes 4, 5 and 6.) I'm using the version of VLC that I've downloaded from the Videolan.org downloads page, fresh install, no configuration changes. I choose "Media | Open Disc" (control-d) and choose my DVD player. The DVD begins to play. Once the DVD menu loads, I press the DVD menu option to Play the movie.

Once the movie intros such as the THX logo and Lucasarts logos load and the movie itself begins to play - I start seeing a problem.

First, the timecode updates too quickly - for instance, on my computer (and on another workstation across the country) the timecode updates at almost double the expected rate - so that after a minute of DVD playback, the timecode in the lower right displays almost 2 minutes. As the famous "Slanted Text" intro (a long time ago in a galaxy far far away...) fades into the starfield background, there is a jerky pause (buffering?) then a sudden jump. Maybe a few seconds of movie-time, but the timecode jumps to around the 12 minute mark (should be more like 3 minutes.)

I have loaded the DVD using alternate interfaces, such as the RC interface and Telnet interfaces and displayed the time through those interfaces, and I see the same problem displayed there as well as the GUI. Happens same for Linux and Windows in both 1.0.2 and 1.0.3 versions of VLC. Other DVD players display the timecode normally.

For most people this wouldn't be a big deal, but we are using the RC and Telnet interfaces for syncing external sound sources and having accurate timecode is vital to the success of our project.

I guess the question to ask - is this a known bug? Should I report it through the official bug reporting channels?

Thank you very much in advance for your help.

- Tony

[number42]

BTW, I just tested this with the latest windows release of 1.0.5 and it's still a problem.

Does my explanation need some work? Would some screen snapshots help?

Thanks in advance for any feedback about this issue - this is actually kind of a major bug for us and I'd like to see if there's anyone else that has seen this kind of thing. Thanks!

- Tony