The VideoLAN Forums

Open Tools -> Messages (set Verbosity to 2), then start the playback. VLC will say what decoders are used to decode audio and video.

Playing the same videos (avi, mkv mpg ...), the same sopcast channel... and there are a big difference between 1.11.111 and 2.0 about cpu consume, if is only a number no problem, but the video go very slow.. whit a high cpu consume. No codec problems, no audio problems, the problem is with the new version. I have installed again the 1.11 version waiting the bugs can be fixed.
I dont say this to claim nothing, only to help to make a better next version without thouses problems. I only want to help to videolan people.

cheers!

did you test 2.0.1 ?
cheers

Yes, I just testing the 2.0.1 version and the problem still there, a little better, with online sopcast video but for example a mkv 1080 its impossible to see
For example, a simple 720p mkv with vlc 1.11.111:20%-30% cpu, with 2.0.1:88%-94%.
Its impossible to fix it?, I think that there are something diferent between that 2 versions about cpu used, something that has changed on the new version.

Right now... again return to 1.11.111

Please share logs.

using about 30-40% cpu on both cores at the moment

main warning: picture is too late to be displayed (missing 21 ms)
main debug: picture might be displayed late (missing 13 ms)
main debug: auto hiding mouse cursor
main warning: picture is too late to be displayed (missing 36 ms)
main debug: picture might be displayed late (missing 19 ms)
main debug: auto hiding mouse cursor
main debug: picture might be displayed late (missing 12 ms)
main debug: auto hiding mouse cursor
main debug: picture might be displayed late (missing 12 ms)
main warning: picture is too late to be displayed (missing 116 ms)
main warning: picture is too late to be displayed (missing 76 ms)
main warning: picture is too late to be displayed (missing 36 ms)
main debug: picture might be displayed late (missing 10 ms)
main warning: picture is too late to be displayed (missing 120 ms)
main warning: picture is too late to be displayed (missing 80 ms)
main warning: picture is too late to be displayed (missing 40 ms)
main debug: picture might be displayed late (missing 0 ms)
main debug: picture might be displayed late (missing 16 ms)
main warning: picture is too late to be displayed (missing 56 ms)
main debug: picture might be displayed late (missing 17 ms)
main warning: picture is too late to be displayed (missing 57 ms)
main debug: picture might be displayed late (missing 17 ms)
main warning: picture is too late to be displayed (missing 53 ms)
main debug: picture might be displayed late (missing 15 ms)
main warning: picture is too late to be displayed (missing 24 ms)
main warning: picture is too late to be displayed (missing 20 ms)
main warning: picture is too late to be displayed (missing 73 ms)
main warning: picture is too late to be displayed (missing 33 ms)
main debug: auto hiding mouse cursor
main warning: picture is too late to be displayed (missing 91 ms)
main warning: picture is too late to be displayed (missing 51 ms)
main debug: picture might be displayed late (missing 11 ms)
main warning: picture is too late to be displayed (missing 48 ms)
main debug: picture might be displayed late (missing 8 ms)
main warning: picture is too late to be displayed (missing 114 ms)
main warning: picture is too late to be displayed (missing 74 ms)
main warning: picture is too late to be displayed (missing 34 ms)
main debug: picture might be displayed late (missing 17 ms)
main warning: picture is too late to be displayed (missing 24 ms)
main warning: picture is too late to be displayed (missing 91 ms)
main warning: picture is too late to be displayed (missing 51 ms)
main debug: picture might be displayed late (missing 11 ms)
main warning: picture is too late to be displayed (missing 66 ms)
main warning: picture is too late to be displayed (missing 26 ms)
main warning: picture is too late to be displayed (missing 35 ms)
main warning: picture is too late to be displayed (missing 28 ms)
main debug: picture might be displayed late (missing 5 ms)
main debug: picture might be displayed late (missing 5 ms)
main warning: picture is too late to be displayed (missing 23 ms)
main warning: picture is too late to be displayed (missing 31 ms)
main debug: picture might be displayed late (missing 4 ms)
main debug: picture might be displayed late (missing 17 ms)

Does it work better with OpenGL video output module?

Does it work better with OpenGL video output module?

windows 7 sp1 not so much
cheers

I have not been able to get any versions above 1.1.11 to play properly. The video will stop and the sound keeps going, things of that nature. It just seems that with all the newer versions my computer no longer has enough power to do the video processing. This has only happened only on my ASUS EeePC CPU Intel Atom 1.6 GHz 1 Gig RAM. I am guessing it is a resource problem from the other posts I have seen. I have loaded all the other versions between 1.1.11 and 2.01, removing everything in between loadings, and still 1.1.11 is the only only one that works.

It is not a problem for me I just use 1.1.11 but from the posts here my shower machine may have started to show the resource related problem in an earlier version.

m0Zf2B7kdD76pWi3Zon4: does it help on ATOM machine, if you set FFmpeg threads to 1?
http://wiki.videolan.org/WindowsFAQ-2.0 ... r_laggy.29

It didn't help on my core 2 duo machine. Should this problem now be moved into official Trac bug reporting?

If you have a way to replicate the issue, the yes.

It didn't help on my core 2 duo machine. Should this problem now be moved into official Trac bug reporting?

did you try the last version ?
seems to be better , doesn't it

On my system, starting Firefox 3.64 or IE7 with the latest Adobe Flash plugin (11.xx) results in permanently wonky video, even after exiting the browsers.. screen pauses when right-clicking the mouse etc, and VLC loses hardware acceleration (MPC and WMP don't). Also as mentioned in another thread USB mouse movements in 2.x add 20-30% CPU compared to a few % in 1.x.

i have the same issue due this old thread raised a new one.