LAV Filters - DirectShow Media Splitter and Decoders

[P.J]

Is it possible to use iGPU's DXVA native when the monitor is connected to dGPU?

[nevcairiel]

Originally Posted by P.J

Is it possible to use iGPU's DXVA native when the monitor is connected to dGPU?

No, Native requires decoding and output on the same GPU.

[P.J]

Originally Posted by nevcairiel

No, Native requires decoding and output on the same GPU.

Thanks, and what about the DXVA2 copy-back?
Then the only way is to use QS/CUDA

[nevcairiel]

Copy-Back doesn't care, you can use it with any GPU and output to any other. Or don't output at all. Or do whatever you like.
Only DXVA2-Native has this limitation, because it keeps the image on the GPU, and you cannot switch GPU because you wouldn't have the image then.

[hubblec4]

Originally Posted by nevcairiel

I would need a sample of the menu to check. You can create a menu-only sample by taking the VIDEO_TS folder without the main movie .vobs

On most DVDs, just exclude the 1GB .vob files, usually those with their name being VTS_xx_1 (or ending with a higher number), while those ending with a zero are often for the menu.

However, if you are not even seeing the menu background image, then its unlikely to be related to the recent fixes, but maybe something else. I'll check if I get a sample.

I have copyed all files except the big vob's in a new folder.
(right click on folder -> play with mpc-hc)
The DVD don't start with playing, sure I should upload this folder?

[nevcairiel]

Originally Posted by hubblec4

I have copyed all files except the big vob's in a new folder.
(right click on folder -> play with mpc-hc)
The DVD don't start with playing, sure I should upload this folder?

Well make a copy of the full folder, and see how many of the big VOBs you can delete without breaking the menu. Maybe you deleted one too many. Make sure to keep all the IFO/BUP files and the VIDEO_TS.VOB

[hubblec4]

Originally Posted by nevcairiel

Well make a copy of the full folder, and see how many of the big VOBs you can delete without breaking the menu. Maybe you deleted one too many. Make sure to keep all the IFO/BUP files and the VIDEO_TS.VOB

mmh bad news: When I delete any vob, the DVD don't start.
The whole DVD must be complete and that are 6,82gb.

I cant upload it from home, but maybe at work in few days.

[Magik Mark]

Nev, may I know if cuvid is:

1. Well supported in windows 10?

2. What are its limitations in madvr and windows 10?

3. Which processing (upscaling & downscaling algorithms) are supported & not?

4. Can it do 10bit or higher video playback?

Thanks

[huhn]

nvidia driver have broken CUVID when "any" other problem is using openCL under windows 10.

CUVID has the same limitation as DXVA it is the same decoder anyway. 10 bit HEVC is possible on a 960 or 950.

DXVA copyback is better anyway so just let CUVID R.I.P.

[ryrynz]

Originally Posted by huhn

DXVA copyback is better anyway so just let CUVID R.I.P.

Basically already has. There won't be updates for it.. Only a matter of time until it's removed.

[FreeFall]

hubblec4,

You can try using DGSplit to cut the VOB and see if that works, just split using a small size, around 60-80MB and tick the box stop after 1 chunk(s) written.

https://trac.mpc-hc.org/raw-attachme.../dgsplit12.zip

If that doesn't work try VobBlanker, It's not too hard to figure out how to use. If you have AnyDVD running just close it first.

http://www.doom9.org/Soft21/Vobtools...r_2130_exe.zip

Here is a basic run down on how to use it:

After opening the IFO select the largest VOB in the top list and edit by selecting the the PGC (largest) in bottom list, Use Prev/Cut to reduce the size of the VOB.
Blank removes the stream entirely, you can use this to remove trailers / special features to save a bit more space.
When your finished click process.

[nevcairiel]

Originally Posted by Magik Mark

Nev, may I know if cuvid is:

1. Well supported in windows 10?

2. What are its limitations in madvr and windows 10?

3. Which processing (upscaling & downscaling algorithms) are supported & not?

4. Can it do 10bit or higher video playback?

Thanks

CUVID in its current form is somewhat broken on 10, because the D3D9 mode it uses is no longer available, and the pure CUDA mode it has as a fallback seems to conflict with OpenCL. On top of that, the pure CUDA mode doesn't offer the best deinterlacing quality, if thats the reason people used it for.

It would need a revamp to make use of D3D11 instead, then it might be able to be restored to full functionality on 10 as well (although there are no guarantees that it won't still conflict with OpenCL), but I would rather focus my efforts on DXVA2, as any improvements made there can benefit anyone, and not just NVIDIA users.
On top of all that, CUVID lacks support for 10-bit entirely. It doesn't specify a 10-bit output format. So its not exactly future proof.

So just consider CUVID dead. I might even forcefully disable it on Windows 10 soon to avoid conflicts with madVR and other things using OpenCL.

[hubblec4]

Originally Posted by FreeFall

hubblec4,

You can try using DGSplit to cut the VOB and see if that works, just split using a small size, around 60-80MB and tick the box stop after 1 chunk(s) written.

https://trac.mpc-hc.org/raw-attachme.../dgsplit12.zip

If that doesn't work try VobBlanker, It's not too hard to figure out how to use. If you have AnyDVD running just close it first.

http://www.doom9.org/Soft21/Vobtools...r_2130_exe.zip

Here is a basic run down on how to use it:

After opening the IFO select the largest VOB in the top list and edit by selecting the the PGC (largest) in bottom list, Use Prev/Cut to reduce the size of the VOB.
Blank removes the stream entirely, you can use this to remove trailers / special features to save a bit more space.
When your finished click process.

Thanks for this info.

I know DGSplit, i will try this first.

6,82 GB ist not sooo much at this times :-)
But my Inet-Connection so very small :-(

[P.J]

Originally Posted by nevcairiel

Copy-Back doesn't care, you can use it with any GPU and output to any other. Or don't output at all. Or do whatever you like.
Only DXVA2-Native has this limitation, because it keeps the image on the GPU, and you cannot switch GPU because you wouldn't have the image then.

Well, I want my iGPU to decode in DXVA2 copy-back mode then output to dGPU.
How is it possible?

[hubblec4]

Hi nevcairiel

The DVD don't playing after i modify any file.
So i will upload the whole DVD, have you a FTP server like Mosu's FTP?

[lolo258]

Hi, is there any chance that LAV Audio Decoder can decode Dolby Atmos？

[CruNcher]

Originally Posted by huhn

nvidia driver have broken CUVID when "any" other problem is using openCL under windows 10.

CUVID has the same limitation as DXVA it is the same decoder anyway. 10 bit HEVC is possible on a 960 or 950.

DXVA copyback is better anyway so just let CUVID R.I.P.

How do you get to this conclusion ?

it might be broken currently under WDDM 2.0 but it's stronger then ever on WDDM 1.1

at least currently on the GTX 970 it shows much more stable playback acceleration results (less jitter problems) for alot of HEVC samples than either DXVA Native nor Copy Back from Lav Decoders point.

Especially in combination with Nvidias DSR

[clsid]

Maybe that is simply a result of your GPU running in high performance mode (P0) when using CUVID?

With the "Multi Display Power Saver" functionality of NVIDIA Inspector you can force a desired power state when specific apps are running.

[nussman]

With CUVID you can do GPU deinterlacing before copyback and with DXVA Copyback you can not (copyback is still interlaced)? Or am I wrong?

So CUVID could be useful for processing between decoder and renderer?

[CruNcher]

Originally Posted by clsid

Maybe that is simply a result of your GPU running in high performance mode (P0) when using CUVID?

With the "Multi Display Power Saver" functionality of NVIDIA Inspector you can force a desired power state when specific apps are running.

Let me see if i can get a clear measure result on that but yeah geez i didn't thought about it, it's CUDA afterall

You are right the memory and core clock are fluctuating heavily with DXVA and seem to cause these brakeups, this is a rather low timing resolution though to see exactly how heavy it is per frame (trying to avoid more interferences)



And these interference's with DXVA i can measure on much much more HEVC samples with Copy Back and Native compared to CUVID

I will experiment a little based on this new Data thx clsid i was so blind, now i know @ least the cause of these DXVA render interferences that especialy become visible in the jitter OSD Graph i experienced since a while for GM204 + VP6 with HEVC

MPC-BEs OSD Graph seems very precise that it can pick up these fast Frequency fluctuations of DXVA and make them so nicely visible