0.92: Vids start with couple seconds of black...

[lideofan]

On my winxp sp3 and w2k sp4, both have fresh .92 installed. Both miss a few seconds of video when I click on a video file, showing black instead. However, the audio portion of the video starts immediately. What can I do to fix this?
Thanks

[DJ]

Try looking at messages. Some videos show lost (corrupted) frame at the beginning as the encoder and or machine that did the encoding settles. While this is not the norm, I have seen it happen. Assuming this is not a one off particular to this file, can you bring it down to a format and file type (container)?

[jwo7777777]

I have this problem also with XP SP2. I have tried 0.8.6 and this version and 0.8.6 does not have this problem, and by extension, neither do the vid files I confirmed it with.

[Jean-Baptiste Kempf]

I am looking at this bug.

[Garjala]

I can confirm that this problem happens with some videos. Not all of them, but it still happens.

Vista 64-bit + SP1

EDIT: My problem seems to be fixed. I changed output from default to OpenGL and saved. After that video opened immediately even after changfing output to default and saving setting again. So, it could be settings related.

[qwert500]

This is very annoying bug, it happens with every AVI-file and this issue is only with version 0.9.2. Older 0.8.6x works fine.
(32bit Vista SP1 and clean VLC 0.9.2 install)

Messages:
avcodec error: more than 5 seconds of late video -> dropping frame

[lideofan]

I've been taking note of when this occurs, and as far as I can tell, it's not specific to any format (avi, mkv, mpg). Also, my message window does not indicate anything. Unfortunately, I'm not familiar enough with encoding types and file properties, so I can't discern the difference between the properties of a file that starts immediately and one that has this delayed video effect.

[tibor.nemeth]

Yes, i have a problem with play a VOB files...
If a switch the audio to 5.1 the screen is immediately black - no play video and audio... I must reset VLC...

Message in taskbar is - VLC (hardware YUV overlay DirectX output).
I tried to change the audio output in preferences - nothing...

In the previously VLC player there was no problem...


Thanks...

[VLC_help]

tibor.nemeth: you tried another video output module?

[tibor.nemeth]

Yes, I treid it. If i change it the audio output is 5.1 immediately by start. BUT The problems is also if I want to switch back: from stereo to mono, or stereo to 2 front 2 rear....etc. The result is: No sound and black screen...
In older version in "default" output module there were no problem by switching.

Thanks.

[Mic-Beatz]

I solved mine by switching from default to directx 3d..Win Xp Sp2, VLC 0.92..thanks guys..i don't use 5.1 so i cant help..

[VLC_help]

tibor.nemeth: you pressed Save and restarted VLC after selecting new video output module?

[tibor.nemeth]

Yes, of course....

the message is Direct3D output...

[VLC_help]

tibor.nemeth: Video -> Video track selection allows you to select right video track (during VOB playback)?

[tibor.nemeth]

Yes, it allows.
But, I forgot say that problem is especially by VOB files which were created by ConvertXDVD - convert AVI files with AC3 sound.
I work with this converter so often and the older VLC player (0.8.6i) had none problem with play and selecting the audio output after converting.

[Jean-Baptiste Kempf]

Does it happen with other Video ? Can you give me a sample that has this issue ALL the time ?

[qwert500]

Does it happen with other Video ? Can you give me a sample that has this issue ALL the time ?

You can download one sample (1,18 Mb) from here -> http://rapidshare.com/files/148271458/s ... t.avi.html

This and all other AVI-files with issue more than 5 seconds of black (audio starts always immediately).

[VLC_help]

No issues here. Starts immediately.

[Jean-Baptiste Kempf]

Definitively a race condition...

[digitall2]

No Issues here either with all default settings except Audio: Win32 Waveout and SPDIF.
Who won the Race?

[qwert500]

Version 0.9.4 doesn't fix this very annoying issue.

Well, seems like that only solution is going back to 0.8.6x.