I'll try installing 2.0.1 again next week when I'm back on my main computer and try your suggestion as well as the other suggestions (about reducing threads) that I found at the Wiki you linked to.Does the loop filter trick help?
http://wiki.videolan.org/WindowsFAQ-2.0 ... r_laggy.29
Developers and testers are volunteers. If noone tests during the development time, end user are the ones testing...What would be GREAT is that developers do not use us as beta testers... back to version 1.x or find something better.
This goes on and on.main debug: audio output is too slow (28809 us): trashing 50000 us
main warning: audio output out of sync, adjusting dates (353990 us)
main warning: not synchronized (353991 us), resampling
main warning: buffer way too late (441310), dropping buffer
main warning: buffer way too late (418090), dropping buffer
main warning: buffer way too late (394870), dropping buffer
main warning: buffer way too late (371650), dropping buffer
main warning: buffer way too late (348430), dropping buffer
main warning: buffer way too late (325210), dropping buffer
main warning: buffer way too late (301990), dropping buffer
main warning: buffer way too late (278770), dropping buffer
main warning: buffer way too late (255550), dropping buffer
main warning: buffer way too late (232330), dropping buffer
main warning: buffer way too late (209110), dropping buffer
main warning: buffer way too late (185891), dropping buffer
main warning: timing screwed, stopping resampling
main warning: buffer too late (162671), up-sampling
main debug: audio output is too slow (12636 us): trashing 50000 us
main warning: audio output out of sync, adjusting dates (347950 us)
main warning: not synchronized (347951 us), resampling
main warning: buffer way too late (508693), dropping buffer
main warning: buffer way too late (485473), dropping buffer
main warning: buffer way too late (462253), dropping buffer
main warning: buffer way too late (439033), dropping buffer
main warning: buffer way too late (415814), dropping buffer
main warning: buffer way too late (392594), dropping buffer
It defaults to two threads. Changing it to 1 or 0 (automatic) didn't have much effect, but setting it to 4 made it skip much worse, causing the video to skip as well with "picture too late (xxx ms)" warnings, and the sound plays at the wrong speed, giving me the chipmunks effect. The only thing that works so far is forcing VLC to run on only one CPU core.Eikka: the FFMPEG threads option also works?
http://wiki.videolan.org/WindowsFAQ-2.0 ... r_laggy.29
Close, but no cigar. There's also the additional problem that now I can only get plain stereo out instead of 5.1. Only the two front speakers actually play anything, whereas with DirectX output I get sound coming though all speakers.main debug: Received first picture
direct3d debug: Created 224x17 texture for OSD
main debug: Post-processing available
main debug: Decoder buffering done in 332 ms
waveout debug: Wakeup sleeping output thread.
waveout debug: will start to play in 17272 us
main debug: audio output is too slow (200826 us): trashing 92879 us
main debug: audio output is too slow (107947 us): trashing 92879 us
main debug: audio output is too slow (15068 us): trashing 92880 us
waveout warning: aout_PacketNext no buffer got next_date=1073978795 ms, 7 frames to play, waiting...
main debug: auto hiding mouse cursor
main debug: picture might be displayed late (missing 5 ms)
main debug: picture might be displayed late (missing 10 ms)
main debug: picture might be displayed late (missing 12 ms)
main debug: picture might be displayed late (missing 8 ms)
main debug: picture might be displayed late (missing 5 ms)
main debug: picture might be displayed late (missing 7 ms)
main debug: auto hiding mouse cursor
main debug: picture might be displayed late (missing 6 ms)
main debug: EOF reached
The audio is largely unaffected. It still skips, maybe a little more.Does it skip less with OpenGL video output module?
Return to “VLC media player for Windows Troubleshooting”
Users browsing this forum: Google [Bot] and 15 guests