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. |
11th September 2012, 20:22 | #20142 | Link | |
Registered User
Join Date: Dec 2007
Posts: 1,138
|
Quote:
And yes "moving the mixer from MpaDecFilter to AudioSwitcher" seems a good idea EDIT : Also it will be nice if you could add independent volume levels for each channel like in FFD
__________________
Intel UHD Graphics 750; Win 10 22H2 Last edited by Mercury_22; 11th September 2012 at 20:26. |
|
11th September 2012, 22:19 | #20144 | Link |
Registered User
Join Date: Apr 2012
Posts: 37
|
Hello,
with MPC-HC x64 1.6.3.5818, hardware acceleration apparently is not used on videos with resolutions beyond 1920x1080? Why is that? And is there any way to use hardware acceleration on videos with resolutions beyond 1920x1080? Thanks in advance. |
12th September 2012, 03:56 | #20146 | Link |
Registered User
Join Date: Oct 2010
Location: The Netherlands
Posts: 1,083
|
@jq963152: It's at the bottom of the page: https://github.com/mpc-hc/mpc-hc/blo...pegContext.cpp . There are restrictions to the size. If you see any case that needs to be corrected, please give us some documentation. We can then patch these items.
__________________
development folder, containing MPC-HC experimental tester builds, pixel shaders and more: http://www.mediafire.com/?xwsoo403c53hv |
12th September 2012, 13:44 | #20147 | Link | ||||
Registered User
Join Date: Apr 2012
Posts: 37
|
Thanks for your replies.
NVIDIA GeForce GT 520 (GF119) Quote:
Quote:
http://en.wikipedia.org/wiki/H.264/MPEG-4_AVC#Levels AVC HP@L5.1 apparently would allow for much higher resolutions than 1920x1080, wouldn't it? Also, in the LAV Filters thread apparently the following was posted: Quote:
Quote:
But when setting it to LAV DXVA2 (native) or when using internal MPC-HC Video Decoder it apparently is falling back to software decoding. Why are resolutions beyond 1920x1080 blocked with LAV DXVA2 (native) and internal MPC-HC Video Decoder (which is DXVA2 native as well, isn't it?)? Last edited by jq963152; 12th September 2012 at 18:54. |
||||
12th September 2012, 14:01 | #20148 | Link |
Registered Developer
Join Date: Mar 2010
Location: Hamburg/Germany
Posts: 10,344
|
Its blocked with DXVA2 Native in LAV because auto-detection of 4k support is not working properly, and if it enabled it but doesnt support it, you get a black screen, which is no good.
Either i'll have to fix the auto-detection (might be tricky) or simply add a checkbox so people can turn on 4k DXVA if they think their Hardware can do it. In any case, I've been rather busy with a lot of different things over the last few weeks, and not much got done.
__________________
LAV Filters - open source ffmpeg based media splitter and decoders |
12th September 2012, 14:06 | #20149 | Link | |
Registered User
Join Date: Apr 2012
Posts: 37
|
Quote:
That would probably be appreciated . Last edited by jq963152; 12th September 2012 at 14:12. |
|
13th September 2012, 16:57 | #20151 | Link |
Registered User
Join Date: Oct 2010
Location: The Netherlands
Posts: 1,083
|
I recently patched some of the DXVA code, so I know what variables are stored and how these are used. You can take a look at the registry part that is read for this function by using regedit.exe . The keys for the various video adapters are listed in "HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Video" . The correct adapter is selected by using the monitor handle. The device and driver identifier keys can be seen under the "0000" key.
Here comes the problem: only very few keys in there are standardized, the rest is driver-specific. The three identifiers that are stored are the vendor ID, the hardware ID and the driver revision. The device and hardware ID is in plain text. For example, my video adapter is; "pci\ven_1002&dev_9460" . http://www.pcidatabase.com/search.ph..._search=Search These three numbers are used to determine the capabilities of the device and driver, as you can see in the link I posted to the source code. These values are acquired by reading spec sheets and by trial and error testing. There are no ways to directly query these detailed things from the standard driver-linked interfaces in software. So what we need is data on what manufacturer ID, what device ID or which series of IDs and which driver revisions have which specific capabilities.
__________________
development folder, containing MPC-HC experimental tester builds, pixel shaders and more: http://www.mediafire.com/?xwsoo403c53hv |
13th September 2012, 17:13 | #20152 | Link | |||
Registered User
Join Date: Apr 2012
Posts: 37
|
Could you possibly do something similar to what "nevcairiel" suggested for LAV Filters:
Quote:
At least as long as auto-detection is not working properly? Suggestion: In MPC-HC x64 1.6.3.5818, if you go to: Quote:
Quote:
Last edited by jq963152; 13th September 2012 at 17:18. |
|||
13th September 2012, 19:20 | #20153 | Link | ||
Registered User
Join Date: Dec 2008
Posts: 1,959
|
jq963152
Quote:
Nvidia cards are limited: width <= 2032 && height <= 2032 && width*height <= 8190*16*16 Nvidia officially declares support for the width and height of 2048 pixels and 8192 macroblock for H264, but this is not true. Quote:
There were cases in the fall of BSOD. Last edited by v0lt; 13th September 2012 at 19:25. |
||
13th September 2012, 19:33 | #20154 | Link |
契約者
Join Date: Jun 2008
Posts: 1,576
|
Does it work in cuvid mode? Do they really say it should work with DXVA, or they say that this is theoretical limit of the engine? Cause this is different things... Maybe its dxva-specific limitation, which you can expect from such old technology. Also noone cares much about dxva these days
Last edited by Keiyakusha; 13th September 2012 at 19:35. |
13th September 2012, 20:50 | #20156 | Link |
契約者
Join Date: Jun 2008
Posts: 1,576
|
I know. But you better check it too before saying that nvidia's hardware doesn't supports what it claims. Does they realy say it should work with DXVA, or they say the hardware is capable of decoding 2048 pixels and 8192 macroblock? You didn't answered.
Last edited by Keiyakusha; 13th September 2012 at 20:53. |
13th September 2012, 21:09 | #20157 | Link | |
Registered User
Join Date: Dec 2008
Posts: 1,959
|
Quote:
... I specifically checked in CUVID (LAV Video Decoder 0.51.3). It does not support for the width and height of 2048 pixels and 8192 macroblocks. Nvidia is lying. |
|
13th September 2012, 21:22 | #20158 | Link | |
契約者
Join Date: Jun 2008
Posts: 1,576
|
Quote:
But if they say DXVA should work, that's too bad =( On other forums people claim nvidia really decodes what it says, but not in DXVA Last edited by Keiyakusha; 13th September 2012 at 22:21. |
|
13th September 2012, 22:16 | #20159 | Link | |||||||
Registered User
Join Date: Apr 2012
Posts: 37
|
But what about what Wikipedia says for example:
Quote:
Quote:
How did you test that if it is currently blocked in MPC-HC? Quote:
http://us.download.nvidia.com/XFree8...limits-decoder your source for what you just posted? From the LAV Filters thread: Quote:
Quote:
Using GT 520 (GF119) here with LAV Filters 0.51.3, both, LAV CUVID and LAV DXVA2 (copy-back) apparently are shown as being "active" in the LAV Video Configuration panel when playing back 3840x2160p testclip and even when playing back 4096x2304 testclip. But, as mentioned in the quote above, it appears to be very laggy with LAV DXVA2 (copy-back). With LAV CUVID it appears to be much better, although, unfortunately, not necessarily perfect either. So why do you write it would not work? Or has it something to do with 8192 macroblocks? Last edited by jq963152; 14th September 2012 at 09:47. |
|||||||
13th September 2012, 22:39 | #20160 | Link | ||
Registered Developer
Join Date: Mar 2010
Location: Hamburg/Germany
Posts: 10,344
|
Quote:
I'll look into DXVA soon, there were some driver bugs that caused it to fail in earlier versions, but maybe those are fixed now. Quote:
Although the decoder chip isn't really all that fast on 4K content either, it can do 24p just fine, but above 30fps it'll start to lag.
__________________
LAV Filters - open source ffmpeg based media splitter and decoders Last edited by nevcairiel; 13th September 2012 at 22:42. |
||
Tags |
dxva, h264, home cinema, media player classic, mpc-hc |
Thread Tools | Search this Thread |
Display Modes | |
|
|