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. |
14th May 2009, 09:32 | #1001 | Link | |
Registered User
Join Date: Feb 2006
Posts: 293
|
Quote:
__________________
Spec: Intel Core i5-3570K, 8g ram, Intel HD4000, Samsung U28D590 4k monitor+1080p Projector, Windows 10. |
|
14th May 2009, 15:48 | #1004 | Link | |
Registered User
Join Date: Jul 2004
Location: ILLINIOS
Posts: 50
|
Quote:
MAK |
|
14th May 2009, 16:42 | #1006 | Link | |
Registered User
Join Date: Jul 2004
Location: ILLINIOS
Posts: 50
|
Quote:
Thanks, MAK |
|
14th May 2009, 16:51 | #1007 | Link | |
Registered User
Join Date: Apr 2009
Posts: 37
|
Quote:
|
|
14th May 2009, 17:08 | #1008 | Link |
Registered User
Join Date: Feb 2008
Posts: 152
|
i have a question to madVR at present i am using mpc-hc with dxva and for a better picture the pixel-shader "sharpen complex 2".
now i would like to know how do i get the same (and perhaps better???) results with madVR? i am using vista 32 with a geforce 8600 gt hdmi. so and an other question is, does anyone get coreavc 1.95 working with cuda and madVR? |
14th May 2009, 17:28 | #1012 | Link |
Registered User
Join Date: Mar 2006
Posts: 567
|
Ok, since this gets repeated:
- CoreAVC using CUDA and madVR works. If you get issues, it simply means you need to use a less demanding algorithm for resampling (max gpu rendering times may seem to be below frame duration, but in reality you have spikes in max gpu rendering times which go above frame duration and that's why you get jerky playback). - subtitles with madVR work. I'm using ZoomPlayer and vsfilter.dll (the subtitle renderer). MPCHC might not work since it has code that deliberately skips vsfilter from loading (I'm not very sure about this though, I'm not using MPCHC). The most recent version of vsfilter.dll is usually the one packaged in Aegisub, since jfs is the one that did most vsfilter patches in recent times. jfs, I hope you don't mind if I post a direct link to your latest version: vsfilter-2.39e. Download it, unrar it, and register it with your favorite filter manager or on the command line. Last edited by KoD; 14th May 2009 at 17:40. |
14th May 2009, 17:31 | #1013 | Link | |
Registered User
Join Date: Jul 2004
Location: ILLINIOS
Posts: 50
|
Quote:
The reason I ask this is: Is MadVR is using the scaling values from powerstrip to identify 601 or 709, or is it using a flag within the stream to identify SD or HD. If using the first situation we will have the wrong lut in use. The use of the PC to scale has been done by many as you are aware, and to give control over custom porch values on a CRT as well. MadVr has no capabilities to change resolution, it is the job of the graphics card; ie from (SD)720 x 480 to (HD)1920 x 1080p. Please correct me if I am mistaken as to how MadVr determines LUT usage. Thanks, MAK |
|
14th May 2009, 17:32 | #1014 | Link | |
Registered User
Join Date: Apr 2008
Posts: 1,106
|
Quote:
|
|
14th May 2009, 17:53 | #1015 | Link | |
Registered User
Join Date: Apr 2009
Posts: 37
|
Quote:
i didn't wanted to be rude in my last post, but i think you still have some misunderstanding about madVR and how it works. Powerstrip changes the resolution of your PC/Desktop and Player software (if its fullscreen), but the scaling is done by the renderer (if you do not use ffdshow or similar and you should *not* use it if you use madVR instead), common renderers doesn't allow you to choose how they scale and they scale bad compared to madVR (or ffdshow, thats why everyone uses ffdshow to scale before madVR was around), but madVR gives you the full control over it, you can even choose differend scalingmethods for luma and chroma ! This has nothing to do with the LUT btw. the LUT is for changing the colorspace and for correcting the primaries/etc. of your display. So now to your "problem", madVR looks at the input resolution (if you feed SD it uses 601, if you feed HD it uses 709) and not at the output resolution to determine which colormatrix/LUT to use. It does not use the output resolution for the determination or some flag or so, just the input resolution you feed into madVR (thats one reason why it is bad to scale before madVR). |
|
14th May 2009, 18:07 | #1016 | Link |
Registered User
Join Date: Apr 2008
Posts: 1,106
|
madshi, you can download a TestDVD here http://merifon.altervista.org/TestDVD.html
This also gives the macrovision failed error with madVR and Haali renderers so you might be able to get around that issue Best of luck! |
14th May 2009, 18:25 | #1017 | Link | |
Registered User
Join Date: Jul 2004
Location: ILLINIOS
Posts: 50
|
Quote:
Thanks, MAK |
|
14th May 2009, 18:26 | #1018 | Link | |
Registered User
Join Date: Jan 2009
Location: UK
Posts: 403
|
Quote:
|
|
14th May 2009, 18:47 | #1019 | Link | ||
Registered User
Join Date: Jul 2004
Location: ILLINIOS
Posts: 50
|
Quote:
Quote:
Thanks, MAK |
||
14th May 2009, 18:49 | #1020 | Link | |||
Registered Developer
Join Date: Sep 2006
Posts: 9,140
|
Quote:
NV12 could eventually be added later, but you can also use ffdshow to convert YV12 to NV12 right now. So it's not high priority for me. Quote:
Quote:
Grmpf already explained that perfectly well. |
|||
Tags |
direct compute, dithering, error diffusion, madvr, ngu, nnedi3, quality, renderer, scaling, uhd upscaling, upsampling |
|
|