Welcome to Doom9's Forum, THE in-place to be for everyone interested in DVD conversion. Before you start posting please read the forum rules. By posting to this forum you agree to abide by the rules. |
19th March 2019, 18:38 | #23382 | Link |
Registered Developer
Join Date: Mar 2010
Location: Hamburg/Germany
Posts: 10,348
|
I don't have any experience with UtVideo. I just pass it to ffmpeg. I suggest to try the ffmpeg commandline to see if it supports such videos.
__________________
LAV Filters - open source ffmpeg based media splitter and decoders |
20th March 2019, 23:18 | #23384 | Link |
Registered User
Join Date: Jun 2006
Posts: 353
|
LAV Video seems to report the active hardware accelerator incorrectly.
The test system has dual graphics: AMD Radeon HD 6620G (integrated) and AMD Radeon HD 6750M (discrete). I renamed mpc-hc64.exe to ~mpc-hc64.exe (or else the video driver doesn't allow to use the discrete graphics for MPC-HC), set it to use the discrete graphics in Radeon Additional Settings applet, launched it - LAV Video decoder (0.74.1, tried internal 0.74.0, too) says: "Active Hardware Accelerator AMD Radeon 6620G" (while Switchable Graphics Application Monitor reports that ~mpc-hc64.exe is using the "High Performance" (discrete) GPU). If I set MPC-HC64 to use the integrate graphics LAV Video decoder reports the same. That is, switching between adapters doesn't affect what LAV Video is reporting. Then I installed FurMark. By default, it uses the discrete graphics, shows 14 fps with it and reports: "AMD Radeon 6600M and 6700M Series". If it forced to use the integrated graphics it shows 2 fps and reports: "AMD Radeon 6620G". That is, it's really been switched and correctly reports what GPU is currently being used.
__________________
Windows 8.1 x64 Magically yours Raistlin |
21st March 2019, 02:03 | #23385 | Link |
Registered Developer
Join Date: Mar 2010
Location: Hamburg/Germany
Posts: 10,348
|
With which hardware decoder mode is that?
Generally LAV will ask the D3D device it uses for decoding during startup about its name, and then store that name somewhere. If its being switched out behind its back, then it won't catch that (and since its cosmetic only, also not really care).
__________________
LAV Filters - open source ffmpeg based media splitter and decoders |
21st March 2019, 02:40 | #23386 | Link |
Registered User
Join Date: Oct 2012
Posts: 7,926
|
you are not supposed to rename anything to use a different GPU there are other ways that should work.
like display-> Graphics settings -> browse -> add mpc-hc and now you can manipulate windows to use a different GPU for that program. |
21st March 2019, 08:22 | #23388 | Link | |
Registered User
Join Date: Jun 2006
Posts: 353
|
Quote:
The OS being used is Windows 8.1 x64.
__________________
Windows 8.1 x64 Magically yours Raistlin |
|
21st March 2019, 11:51 | #23389 | Link | |
Registered Developer
Join Date: Mar 2010
Location: Hamburg/Germany
Posts: 10,348
|
Quote:
I don't suppose you have any way to check which device is actually doing the decoding, based on hardware usage etc, instead of just trusting the tool that says it should be the dedicated?
__________________
LAV Filters - open source ffmpeg based media splitter and decoders |
|
21st March 2019, 14:32 | #23390 | Link |
Registered User
Join Date: Nov 2004
Location: Poland
Posts: 2,843
|
Is there any reason why LAV decoder can't read MOV headers for color flagging (including new tags for master display information: https://patchwork.ffmpeg.org/patch/6409/) and pass it to madVR (like it does for h265)?
This would allow to play eg ProRes, DNxHR etc. HDR files to HDR TV. |
21st March 2019, 16:30 | #23391 | Link |
Registered Developer
Join Date: Mar 2010
Location: Hamburg/Germany
Posts: 10,348
|
Of course, the reason is that the decoder doesn't get access to the container file. It can only read the video stream itself, anything else would require manual handling of some sort.
__________________
LAV Filters - open source ffmpeg based media splitter and decoders |
21st March 2019, 17:33 | #23392 | Link |
Registered User
Join Date: Jun 2006
Posts: 353
|
nevcairiel
Switching the GPU for an app is, for some unknown reason, often a hack thing in AMD systems, with all that renamings of exe's. So I was hoping to get another proof from LAV that all is working in the right way. The fact is that I can't see any difference in madVR's performance when MPC-HC set to use the integrated GPU or the discrete GPU. The conclusion is either 6620G and 6750M have the equal possibilities in video processing made by madVR or MPC-HC ignores the GPU setting and always uses the integrated graphics, though the driver reports the reverse.
__________________
Windows 8.1 x64 Magically yours Raistlin |
21st March 2019, 17:57 | #23393 | Link |
Registered User
Join Date: Oct 2016
Posts: 896
|
Configure DXVA Checker the same way as MPC-HC, then do a decode benchmark while monitoring your integrated and discrete GPU. If the iGPU is used for decoding you should see some GPU load on it even in pure decode mode.
__________________
HTPC: Windows 10 22H2, MediaPortal 1, LAV Filters/ReClock/madVR. DVB-C TV, Panasonic GT60, Denon 2310, Core 2 Duo E7400 oc'd, GeForce 1050 Ti 536.40 |
21st March 2019, 21:55 | #23395 | Link |
Registered User
Join Date: Oct 2016
Posts: 896
|
Install DXVA Checker: http://bluesky23.yukishigure.com/en/DXVAChecker.html
go to DS/MF Decoder ==> Check Decoders ==> Select media file ==> click the arrow next to LAV Decoder ==> Decode Performance ==> DXVA2. For usage monitoring you can use GPU-Z: https://www.techpowerup.com/gpuz/
__________________
HTPC: Windows 10 22H2, MediaPortal 1, LAV Filters/ReClock/madVR. DVB-C TV, Panasonic GT60, Denon 2310, Core 2 Duo E7400 oc'd, GeForce 1050 Ti 536.40 |
22nd March 2019, 11:38 | #23397 | Link | |
Registered User
Join Date: Nov 2004
Location: Poland
Posts: 2,843
|
Quote:
In case of ProRes and DNxHR it's (except master display info). They have private headers flagging inside as well. |
|
22nd March 2019, 11:40 | #23398 | Link |
Registered Developer
Join Date: Mar 2010
Location: Hamburg/Germany
Posts: 10,348
|
Yes. I'm not sure what it tries to read there, but it works regardless.
__________________
LAV Filters - open source ffmpeg based media splitter and decoders |
22nd March 2019, 11:41 | #23399 | Link |
Registered Developer
Join Date: Mar 2010
Location: Hamburg/Germany
Posts: 10,348
|
If you can provide example files, I could take a look. In theory there already are some mechanisms to transport this data, since I added it for HDR WebM Files, which only have it in the container data as well, but it needs to be implemented for every container specifically, unfortunately.
__________________
LAV Filters - open source ffmpeg based media splitter and decoders |
22nd March 2019, 14:08 | #23400 | Link |
Registered User
Join Date: Nov 2004
Location: Poland
Posts: 2,843
|
In all cases you have the same container flagging (ProRes also has correct private frames headers flagging, but DNxHR/Cineform not). Best to relay on MOV flagging. In this case: colr, clli and mdcv tags. Those fully describe HDR content.
DNxHR also stores range info in ACLR tag. ProRes has no range info as it should be rather always limited range (although you can make full range file as well). Cineform has no known range flagging either. Link: https://drive.google.com/open?id=1Dm...3Pni2cSGvTQ1hq Values for different standards HDR10, HLG etc are the same as for h265. Mediainfo has support for all those tags. Last edited by kolak; 22nd March 2019 at 14:11. |
Tags |
decoders, directshow, filters, splitter |
|
|