The VideoLAN Forums

That would not work. In general, the time spent transfering the picture to and from the GPU would be longer than that saved in offloading computations. Using the GPU for postprocessing only makes sense if the picture is either coming from (i.e. decoded by) the GPU, or going (i.e. rendered by) to the GPU - not if it does a round-trip.

Also in this specific case, Yadif2x is a CPU algorithm...

Is it called accelerated video output (overlay) or use hardware yuv->RGB conversions? Both are checked already.

I can't find the GPU anywhere.



Help?

Hardware accelerated decoding.

I have a Dell laptop with a Quadro NVS 160M.

If I enable GPU support and play a Blu Ray encoded with handbrake, it plays fine. If I play a .ts file, created by NextPVR from an OTA recording, I get lots of blocking.

If GPU support is not enabled, the dual core CPU is not fast enough to play either video type smoothly.

Is there any setting I need to change to get GPU support to work with the .ts file?

Can you explain "encoded with handbrake"? I don't know what that means. I downloaded handbrake and couldn't get it to do anything with the blu-ray on my disk. (Other than handbrake seeing that it was a blu-ray)

I'm using vlc 2.2.1 on Windows 10 and I'm trying to get VLC to use my HD7700. If I leave "Automatic" the the CPU still does the work while watching a movie, the GPU does nothing at all.
From the dropdown I can only choose the following.



Am I missing something?

Windows 10 Pro x64
i7 2600K
Asus P67 Sabbertooth
Radeon HD7700

Yeah. "Automatic" does not yet work on Windows in VLC 2.2.x.

Thanks, went back to 2.1.6 until that is fiexed

You do realize it does not work in VLC 2.2.x nor any earlier versions...

You do realize it does not work in VLC 2.2.x nor any earlier versions...

Well something must work because when I watch a movie using 2.1.6 my GPU load is at 30-40%. doing the same with vlc 2.2.1 my GPU is at 0% load, same movie same settings.

On Windows "Automatic" is the same as "Disabled" in VLC 2.2 and VLC 2.1. You can check the source code or your VLC logs. So your statement that it broke in VLC 2.2 and worked in VLC 2.1.6 makes absolutely no sense.

On Windows "Automatic" is the same as "Disabled" in VLC 2.2 and VLC 2.1

What's the point of this so-called 'Automatic' option then ?

On Linux, it actually works.

On Linux, it actually works.

That doesn't answer the question: what's the point in having an option called Automatic if it's not automatic ?
Especially since you just admitted it's disabled in the source code, so you know it but you don't fix it.

Patch welcome.

I'm using vlc 2.2.1 on Windows 10 and I'm trying to get VLC to use my HD7700. If I leave "Automatic" the the CPU still does the work while watching a movie, the GPU does nothing at all.
From the dropdown I can only choose the following.



Am I missing something?

Windows 10 Pro x64
i7 2600K
Asus P67 Sabbertooth
Radeon HD7700

I tried to used directx acceleration, but this options is showing the video with a lot of a random artifacs

Open VLC Media Player and click on Tools > Preferences or press Ctrl-P to open the settings window of the program. If you are using the simple settings interface, click on Input & Codecs on the left sidebar and check the Use GPU accelerated decoding box there.

GPU acceleration is broken since 2.2.x release. No GPU is used

If you change the vlc.exe to vlc-test.exe, you can use GPU acceleration. At least with my Nvidia Quadro M3000M I could then pick that exe to run with GPU. When it was named vlc.exe it would only let me use integrated. I had to change this in the GPU settings, not VLC settings.

Then, this is not a VLC issue, but a driver one.

I have tested the VLC version 2.2.4 GPU hardware acceleration (DxVA) on several systems and I have obtained the following results:

- on Windows 7 x64 and VLC 2.2.4 (32 bit version) everything works great with hardware accelerated decoding!
- on Windows 10 x64 and VLC 2.2.4 (32 bit version) it crashes to desktop instantly (probably access violation error in libdxva2_plugin.dll according to the crashdump).
- on Windows 10 x64 and VLC 2.2.4 (64 bit version) everything works great with hardware accelerated decoding!
- on Windows 10 x86 and VLC 2.2.4 (32 bit version) it crashes to desktop instantly (probably access violation error in libdxva2_plugin.dll according to the crashdump).

So the conclusion is that if you want hardware accelerated decoding under Windows 10 you must use the 64 bit version of VLC at the moment. It would be awesome if this bug could be fixed for the 32 bit version as well.

Thank you for your continuous efforts in developing this great program!

Yes, it's weird, that this happens only on Windows 10. Can you try our nightly builds of 3.0, please?

Mine works after re-install, the 3rd time of installation it lagged and now after the Window 10 update (or maybe its about the 64 bit not sure) its working nicely .

I have Windows 10 32 and I just read that I'll have to change over to 64 but I also have a question. My GPU is ATI Mobility Radeon HD 4200 Series. So is it too old for me to be able to use GPU Acceleration?

I cant enable it too?! where can I find?!
Is this experimental?