How to get better performance when playing HD H.264

[j-b]

H.264 codecs are pretty CPU intensive and VLC can't use multi-cores to decode it yet.

So if your computer is dying when decoding 1080p samples from H264, do the following.

• Open the preferences
• Tick advanced in the lower right corner
• Go to "Input/Codec"
• Go to "other codecs" subcategory
• Go to "FFmpeg"
• Put the "skip-filter for H264" to all
• Restart VLC

DON'T ASK help about this on IRC or I may kill you

Edited on public intrest by MetalheadGautham:

to the guys complaining that C2Q Q6600 and AMD Phenom can't run HD H.264:

Only ONE CORE among their 4 cores is used. Their indivudual core power is quite average. You would have a better performance with a high power per core CPU like C2D E8400.

...Thats UNLTIL multicore support appears on H264 decoder

[fred333]

Thanks for the advice and guidance. I will have to try it tonight.

[CloudStalker]

DON'T ASK help about this on IRC or I will kill you

I'm asking on IRC right now.

[j-b]

DON'T ASK help about this on IRC or I may kill you

I'm asking on IRC right now.

I don't care, I wasn't on IRC all day... SOme people have to work...

[Ux64]

Thank you!

This solved my problem with choppy h264 videos.

[Ux64]

I found higher bitrate H.264 videos which still won't run on with Q6600 CPU. ;( (One core maxes out)

But I'm sure problem is being solved.

[brass2themax]

I've had VLC lag out on H.264 quite often myself. It's decent when you change the settings like suggested above, but I still get better overall performance out of Media Player Classic with the 'proper' builds of ffdshow and even CAVC.

Things can only get better though, VLC is a great tool, lots of room for improvement.

[thresh]

we all hope this would be "fixed" once there's a slice-based decoding implementation available in ffmpeg.

[Ux64]

VLC lag out on H.264 quite often myself. It's decent.

Unfortunately it isn't. In case there is some heavy h.264 stuff coming in. Like direct Blu-ray / HD-DVD rip. -> 45 gigabytes of data for 1.5 hour of stuff. It got pretty hefty bitrate so it totally kills my Q6600 CPU. And everything turns to very slow slide show.

Those settings are barely adequate for ~4 Gbytes / 1.5 hour rips.

[revolunet]

welcome back to the 80's when we needed the most up-to-date computer to play a single video...

[Ux64]

welcome back to the 80's when we needed the most up-to-date computer to play a single video...

I knew I had problem with my old AMD 4500+ CPU... But now I got Q6600 and it's not enough either. ;(

Off topic babbling.

I remember time when it was better to convert JPG images to GIF images before showing. It took so long time to show JPG images. ~20-30 seconds / image. (At that moment most hard drives got something like 40 megabytes of space and 286 cpu was hot!)

Also often palette was better optimized with proper conversion.

After that came MP3 it was so heavy compression. At first compressing CD to MP3 took several days. And also most of comps didn't play mp3 files directly. So it was better to convert those to wav for playing. Which wasn't either too bright idea, because most of hard drives got something like 120 megabytes of space.

When DivX came, it was quite nice. My 450 MHz Pentium just barely decoded it in time. But yeah, since that though challenge for home comps have been video compression. It's nice to see what the challenge will be in future when we get 1000 more or even more. Now I got 1 terabyte of hard disk space and 4x 2400 MHz cores. But that's still not enough for pre-uncompression or realtime decoding with software which uses only one core. And having 4 gigabyte of memory won't help.

[j-b]

We are working on it, but this is complex stuff.

[native]

Really appreciate this - solved a very confusing problem for me

Works a treat with 1080p movie I grabbed earlier that just would not play correctly..

You are a Champ , Thanks

[Ux64]

These are non-educated thoughts. Just a quick brainstorm without any deeper thoughts...

I wonder if it would be possible to allow longer buffering and if it would help pipelining decoding process? Even so that every core would work separately from different keyframe. Altough current video compressors place keyframes very sparsely. Having enough (?) memory would allow this kind of processing.

Did I get something wrong or does field decoding require also field compressed material? Or can any material easily be decoded with field decoding? Striping image in to different fields.

[LudwigJ]

Thanks for the info. It's running smoothly right now