The VideoLAN Forums

I love VLC. That's why I am posting this info. Because I do have a workaround for this problem.

My problem: the sound on various files (avi, mpg mov) sometimes stops for a few seconds. The only thing that really works is playing the files in Windows Media Player. And I can't stand the Media Player being better at something than VLC

So, I am sure there is something wrong with these files, or my drivers or...... but if Media Player can handle it, why not VLC?

I have tried several settings in audio. The only setting that makes it a little better (less stops) is setting the output mode to: Win32 waveOut Extension output.

In that setting I get the following messages: (debug mode)
main warning: resampling stopped after 20135296 usec (drift: 1116)
waveout warning: aout_PacketNext no buffer got next_date=18167116 ms, 7 frames to play, waiting...
waveout warning: aout_PacketNext no buffer got next_date=18201194 ms, 7 frames to play, waiting...
waveout warning: aout_PacketNext no buffer got next_date=18234900 ms, 7 frames to play, waiting...

If set to Directx Sound (or default) I get these messages:
main warning: audio output out of sync, adjusting dates (-46504 us)
main warning: not synchronized (-46503 us), resampling
main warning: audio output out of sync, adjusting dates (-44603 us)
main warning: not synchronized (-44602 us), resampling
main warning: audio output out of sync, adjusting dates (-43637 us)
main warning: not synchronized (-43635 us), resampling
main warning: resampling stopped after 5745830 usec (drift: 35912)
main warning: audio output out of sync, adjusting dates (-44602 us)
main warning: not synchronized (-44600 us), resampling
main warning: buffer too early (-80513), down-sampling
main warning: audio output out of sync, adjusting dates (-44588 us)
main warning: not synchronized (-44587 us), resampling
main warning: buffer way too early (-123920), clearing queue
main warning: timing screwed, stopping resampling

Is there a way that I can make VLC better than de mediaplayer?

Can you try the latest VLC nightly build and use DirectX or Waveout output?

Yes I can!

Used the windows 64bit version (since I have WIndows7-64 bit)
Result:
DirectX: Sound is good, no "chops"
Messages:
main debug: resampling stopped (drift: -27029 us)

Win32 WaveOut extension output: sound good
no messages

Automatic: bad sound and picture
This suprised me. I expected bad sound, but any change on the video.
Messages:Lots
direct3d debug: Reusing 373x29 texture for OSD
direct3d debug: Reusing 373x29 texture for OSD
avcodec error: more than 5 seconds of late video -> dropping frame (computer too slow ?)
main warning: picture is too late to be displayed (missing 775 ms)
main warning: picture is too late to be displayed (missing 805 ms)
main warning: picture is too late to be displayed (missing 835 ms)
main warning: picture is too late to be displayed (missing 866 ms)
main warning: picture is too late to be displayed (missing 826 ms)
main debug: resampling stopped (drift: 2430 us)
avcodec error: more than 5 seconds of late video -> dropping frame (computer too slow ?)
main error: ES_OUT_SET_(GROUP_)PCR is called too late (pts_delay increased to 300 ms)
main error: ES_OUT_RESET_PCR called
mmdevice debug: state changed: 0
main debug: Buffering 0%
main debug: Buffering 8%
main debug: Buffering 16%
main debug: End of audio preroll
main debug: Buffering 25%
main debug: Buffering 33%
main debug: Buffering 41%
main debug: Buffering 50%
main debug: Buffering 58%
main debug: Buffering 66%
main debug: Buffering 75%
main debug: Buffering 83%
main debug: Buffering 91%
main debug: Buffering 100%
main debug: Stream buffering done (325 ms in 0 ms)
main debug: End of video preroll
main debug: Received first picture
main debug: Decoder buffering done in 10 ms
mpgatofixed32 debug: libmad error: bad main_data_begin pointer
mmdevice debug: extrapolating position: still propagating buffers
main debug: inserting 176 zeroes
mmdevice debug: state changed: 1
mmdevice debug: extrapolating position: still propagating buffers
mmdevice debug: extrapolating position: still propagating buffers
mmdevice debug: extrapolating position: still propagating buffers
main warning: playback too early (-98163): down-sampling
main warning: playback way too early (-140408): playing silence
main debug: inserting 6739 zeroes
main warning: playback way too early (-166530): playing silence
main debug: inserting 7993 zeroes
main warning: playback way too early (-187653): playing silence
main debug: inserting 9007 zeroes
main warning: playback way too early (-213775): playing silence

I would like VLC to play with normally with the automatic mode. So, I don't mind doing a bit more testing. But are you interested?

Automatic just means mmdevice which needs some patches to work correctly with 2.1 new audio core. It will be fixed eventually but for now waveout and directsound are the way to go for 2.1

I'm getting this choppiness in audio playback too.
I've tried, to the extent of my knowledge, altering the (Simple) Audio output module choice - from Win32 waveOut extension output, and DirectX audio output - with no improvement.
The subsections on each use 'Msft SoundMapper' and 'Primary Sound Driver' respectively; I don't know whether to use 'Use float32 output' or not. Either way: no improvement.
Win7 32, i7 920, 4 GB... No Samsung Kies. VLC 205.
All closable background apps closed. Process Hacker shows no CPU-grabbing miscreants.
Podcasts miss part of words, so significant. On the same mp3 files, WMP sounds smooth as silk.

I also had choppy audio with vlc player 2.0.5 on Windows XP, downloaded a non-debug version from http://nightlies.videolan.org/build/win ... 0212-0003/ and it's fine now, didn't change any settings.

I'm getting this choppiness in audio playback too.
waveOut extension output, and DirectX audio output - with no improvement.[...] VLC 205.

The waveout/directsound fixes apply to 2.1 not 2.0.5. To get a vlc 2.1 use the nightly builds.

I also had choppy audio with vlc player 2.0.5 on Windows XP, downloaded a non-debug version from http://nightlies.videolan.org/build/win ... 0212-0003/ and it's fine now, didn't change any settings.

That's because IIRC the default audio output for XP is directsound.

I'm getting this choppiness in audio playback too.
waveOut extension output, and DirectX audio output - with no improvement.[...] VLC 205.

The waveout/directsound fixes apply to 2.1 not 2.0.5. To get a vlc 2.1 use the nightly builds.

Okay, that makes sense. Thanks.
I got a nightly, non-debug in a zip and ran it as a portable.
Choppiness has gone - except for 5 consistent 'bips' at the beginning of every mp3 I play. Lasts just a few seconds. Maybe it's just needing fine tuning.
vlc-2.1.0-git-20130212-0003

Using which output? can you share the verbose logs when this beeps happen?

TypX: using standard speaker output. Primary sound driver. Is that an answer..?
I've had a look around but I can't find the verbose logs. Where would they be? Win7, Standard User.
The bips occur with time jumps, too, with recorded audio. 5 secs, 10 secs, a minute; anything.

By output I meant waveout or directsound or both.
To have the logs it's Tools->Messages set verbosity to 2 then start playback.

I'm having a hard time determining what sound output is active - they both exist in the Advanced, Output modules, DirectX and WaveOut - but what's operating, I can't tell.
I see in Simple settings, Audio, Output module is set to automatic.
I've just chosen 'DirectX audio output' and tried it - same bips.
'Win32 waveOut extension output': does the same.

As for verbose logs - I have 100+ lines. 34k .txt. Should I post here? Other?

Automatic means mmdevice on Vista+. When you change the setting, you have to save and restart vlc to apply the changes.
As for the logs, post it here or use the pastebin like of your choice.

Automatic means the mmdevice on Vista+. When you change the setting, you have to save and restart vlc to apply the changes.
As for the log, post it here or use the pastebin of your choice.

Okay, TypX, let's see if this works.
http://pastebin.com/ZjMzF9vS
Thanx re mmdevice.

THis is stilll using mmdevice

Ah, I see that now.
I wasn't reconciling the difference between the Simple and the All/Advanced settings. I see now that 'Default' must be 'mmdevice'. ('Automatic' seems to have disappeared in this recent build.)
And I see that the indented DirectX, File and WaveOut are refinements of the 'Output module'/'Output modules' (plural) choices.

I've run vlc-2.1.0-git-20130212-0003 with both Win32 waveOut extension output and DirectX audio output, and performance and the rate of errors have much improved.

I note that while the indented > DirectX, File and WaveOut < options are in a certain order in Advanced settings, the drop-down for module choice has the order:
> Default, Win32 waveOut extension output, File audio output, DirectX audio output, Audio memory output, Dummy audio output < - quite a different order. Puzzling, especially for a novice.
And, of course, the wording is quite different, as is capitalisation: 'waveOut' versus 'Win32 waveOut extension output' versus 'WaveOut'. It all takes a bit of learning.
I've found that exact and consistent wording throughout a GUI interface is, by far, the best policy.

In this thread, Win32 waveOut extension output = waveout and DirectX = DirectX audio output ('directsound'..?)

I notice that the hover-tip for the output module choices is 'This is the audio output method used by VLC. The default behaviour is to automatically select the best method available. Save and restart VLC if altered.'
This isn't particularly clear. My recent experience demonstrates that the best wasn't automatically selected.
I'd recommend: 'This is the audio output decoder used by VLC. The best choice available is automatically detected and selected by default.'

Signing out unless and until the choppiness recurs.