Post Reply
Custom Resolution Utility (CRU)
09-19-2017, 02:23 PM
Post: #3141
RE: Custom Resolution Utility (CRU)
(09-18-2017 03:25 PM)ToastyX Wrote:  
(09-18-2017 08:02 AM)netW0RTHplus Wrote:  You're correct the monitor is showing - "PNP09FF - Generic Non-PNP Monitor with no data.
Yeah, sounds like a faulty HDMI cable or problem with the monitor. With a working EDID, CRU would show you everything the monitor defines by default, and the resolution would be correct out of the box.

Might be the EDID, coz ive tried lot of dp and hdmi cables but the resolution is still the same despite reinstalling gpu driver and downgrading OS.
Find all posts by this user
Quote this message in a reply
09-19-2017, 07:30 PM
Post: #3142
RE: Custom Resolution Utility (CRU)
(09-19-2017 02:23 PM)netW0RTHplus Wrote:  Might be the EDID, coz ive tried lot of dp and hdmi cables but the resolution is still the same despite reinstalling gpu driver and downgrading OS.
HDMI and DisplayPort have separate EDIDs. If the problem is happening with both, then the monitor is definitely faulty. Get it replaced.
Find all posts by this user
Quote this message in a reply
09-21-2017, 03:43 AM (Last edited: 09-21-2017, 03:46 AM by jak soro)
Post: #3143
RE: Custom Resolution Utility (CRU)
hey forum,

i got a new computer with a nvidia NVS 510 Graphics card, which by description should be able to do up to 4 monitors at 4k resolution at 60hz.
3840-2160 is selected automatically however no option higher than 30hz is possible. i tried adding with higher refresh rate on the CRU and also used the nvidia patch to disable the pixel clock limits but still not able increase the refresh rate.
mouse is not smooth enough at 30hz, if someone could help me please understand what the problem is, im not very expert, thank you.

i use displayport to connect the monitor, windows 10
Find all posts by this user
Quote this message in a reply
09-21-2017, 10:24 AM (Last edited: 09-22-2017, 07:27 AM by TechnicalMonkey)
Post: #3144
RE: Custom Resolution Utility (CRU)
Hello,

I am new to this forum, and want to open up by saying,"Thank you for a great piece of software like CRU." I hope that one day I can provide something as useful to this forum one day, but alas I am a beginner at how to make custom resolutions work--particularly with EDIDs. So it brings me to my question that I would hope others would like to hear about.

I own a few capture cards as I practice live streaming more for learning the technical aspects of it. The capture cards that I am experimenting with right now are the Datapath VisionAV line of cards. I have a VisionAV/B, a VisionAV-SDI, and a VisionAV-HD. I went with Datapath cards as I have been a long time owner of an E1 and E2 card, as well as a user of the E2S, and I know how well they are at accepting any resolution that you can throw at it for the most part. I've had much success in working analog capture, as well as DVI-SL to their maximum potential. However, the card itself is supposed to be able to receive HDMI 1.3 signals (if I said that correctly,) but this line of cards has a limitation that I can accept for what it is. The receiver chip that Datapath uses in this line of capture cards is the ADV7604, which receives 3 types of signals. The first is analog capture with a limit of 170 Mega Sample per Second (170MSps) that makes for really nice sharp RGB capture. The Second is DVI-SL in which can sample at 165MHz, which I was able to push 2560x1440@42Hz with reduced blanking timings. The last and one that has me stumped the most, is HDMI 1.3 which is supposed to allow custom resolutions, but the chip itself can only sample at 225MHz.

The thing that I am trying to do is capture, as an HDMI signal an output from a modern nVidia card, 2560x1440@50fps. I know I should be able to do this as it would only take about 201MHz to accomplish this, or that is what I belive is supposed to happen. However, when I try to do this, the image will not capture.

I ran Datapath's application called RGBHelper that comes with the downloaded driver and application package from their site, and it shows that the signal shows as DVI-SL. I tried patching the card to remove it's limitations, and tried to write in a custom block that would hopefully show the video card as HDMI instead of DVI-SL. In the end it will not show up as anything other than DVI-SL.

Has anyone here have any experience with this matter?

Thanks for reading this post, and for any responses in this matter.

Sincerely,

TechnicalMonkey

EDIT: I just wanted to update you guys on what I found. According to Datapath, the DVI/HDMI dongle that they pack with their VisionAV cards are proprietary, and the seemingly DVI-I looking ports can work as standard DVI-SL, but are also wired for HDMI on the pins normally not used in a DVI-SL configuration. I plan on ordering some of these dongles and will post an update on this section.

Lesson to be learned here: DON'T lose your capture card accessories.
Find all posts by this user
Quote this message in a reply
09-24-2017, 09:33 AM
Post: #3145
RE: Custom Resolution Utility (CRU)
Hey!

I tried looking for answers cause i do not like asking questions that have been answered already, nor i do not like seeing others doing it, but i really didn't find a solution.

So i have a PC with Intel HD 4400 on board. I am using it as a Car PC and i use its HDMI output with a car head-unit. To connect the HDMI output to a card head unit i am using a HDMI adapter that takes HDMI and feeds an RGB signal to a car monitor. The supported resolution of the monitor is 800x480. The HDMI adapter takes whatever signal, re-scales it to 800x480 and feeds it to a car monitor. The quality of the image is just awful. I hope that when i feed a native resolution, it will look nicer.

Now, i can not choose anything lower that 800x600 on the PC. It is just not on the list. So i tried the CRU, but for the life of me i do not understand how i can make it work. I used the "Detailed Resolutions" block and added 800x480 as a resolution with "Automatic LCD Standard" setting, restarted the driver but it held to 800x600. And the new resolution didn't appear on the list.

I am using the whichever driver that was installed with Windows 10 so i will try those suggested in the original post. But... am i doing anything wrong? Is it even possible to make the graphic adapter produce the resolution that is required for my application?
Find all posts by this user
Quote this message in a reply
09-24-2017, 10:44 AM
Post: #3146
RE: Custom Resolution Utility (CRU)
(09-24-2017 09:33 AM)StabMe Wrote:  Now, i can not choose anything lower that 800x600 on the PC. It is just not on the list. So i tried the CRU, but for the life of me i do not understand how i can make it work. I used the "Detailed Resolutions" block and added 800x480 as a resolution with "Automatic LCD Standard" setting, restarted the driver but it held to 800x600. And the new resolution didn't appear on the list.
Windows will not list resolutions lower than 800x600 in the display settings, but it's possible to choose resolutions as low as 640x480 by going to Display settings > Display adapter properties > List All Modes.

(09-24-2017 09:33 AM)StabMe Wrote:  I am using the whichever driver that was installed with Windows 10 so i will try those suggested in the original post. But... am i doing anything wrong? Is it even possible to make the graphic adapter produce the resolution that is required for my application?
Adding a detailed resolution should be enough. You need to make sure the driver is one of the versions listed in the first post or newer because earlier versions didn't support EDID overrides.
Find all posts by this user
Quote this message in a reply
09-24-2017, 10:45 AM
Post: #3147
RE: Custom Resolution Utility (CRU)
(09-21-2017 10:24 AM)TechnicalMonkey Wrote:  The thing that I am trying to do is capture, as an HDMI signal an output from a modern nVidia card, 2560x1440@50fps. I know I should be able to do this as it would only take about 201MHz to accomplish this, or that is what I belive is supposed to happen. However, when I try to do this, the image will not capture.

I ran Datapath's application called RGBHelper that comes with the downloaded driver and application package from their site, and it shows that the signal shows as DVI-SL. I tried patching the card to remove it's limitations, and tried to write in a custom block that would hopefully show the video card as HDMI instead of DVI-SL. In the end it will not show up as anything other than DVI-SL.
It's possible the video card is only sending an HDMI signal for TV resolutions, although I don't think that's the case. Try adding the LPCM audio format. If there's audio, then it's definitely HDMI. Let me know if the dongle changes anything.
Find all posts by this user
Quote this message in a reply
09-24-2017, 10:46 AM
Post: #3148
RE: Custom Resolution Utility (CRU)
(09-21-2017 03:43 AM)jak soro Wrote:  i got a new computer with a nvidia NVS 510 Graphics card, which by description should be able to do up to 4 monitors at 4k resolution at 60hz.
3840-2160 is selected automatically however no option higher than 30hz is possible. i tried adding with higher refresh rate on the CRU and also used the nvidia patch to disable the pixel clock limits but still not able increase the refresh rate.
What monitor is this? If the monitor supports 3840x2160 @ 60 Hz, you shouldn't have to add it. It should already be listed somewhere, maybe in the extension block.
Find all posts by this user
Quote this message in a reply
09-25-2017, 11:56 AM
Post: #3149
PC freeze on HDMI 2.0 (1920x1080 240 Hz & 2560x1440 144 Hz)
I have two DisplayPort monitors (2560x1440 144 Hz and 1920x1080 240 Hz) and a HDMI 2.0 AV receiver, all connected to a GTX 1080. I use only one monitor at a time by setting it as primary, disabling the other monitor, and cloning the desktop with the AVR to get HDMI audio.

There has been a bug since Windows 10 where the desktop animation frame rate is capped at the refresh rate of the slowest cloned monitor, even though the primary monitor itself is running at a higher refresh rate. In Windows 8, I could clone my 2560x1440 144 Hz monitor with my AVR at 2560x1440 24 Hz and the desktop would run at 144 fps. But in Windows 10 the desktop animations only run at 24 fps. Games still run at 144 fps though.

The only way to fix this is to also run the HDMI output at 144 / 240 Hz before cloning. My AVR is headless, so I don't care that the signal is out of range. The AVR still extracts the audio. However, even with HDMI 2.0 the maximum stable resolution I'm able to achieve is 1280x720 144 Hz. This prevents me from cloning with either of my monitors.

To work around this I've enabled DSR 4x. This lets me clone the desktop at 2560x1440 144 Hz since 4x 1280x720 is 2560x1440. If 1280x720 240 Hz worked, DSR 2.25x would let me clone with 1920x1080. However the driver crashes and freezes the entire PC (without even a BSOD) when I choose any resolution above 1280x720 144 Hz. I cannot even run 1920x1080 120 Hz which is well within the HDMI 2.0 specification.

According to this, both 2560x1440 144 Hz and 1920x1080 240 Hz should be supported.
https://en.wikipedia.org/wiki/HDMI#Version_2.0
Find all posts by this user
Quote this message in a reply
09-27-2017, 04:02 PM (Last edited: 09-27-2017, 04:07 PM by Jarvmeister)
Post: #3150
RE: Custom Resolution Utility (CRU)
Hi, I've been trying to set up a custom resolution for my LG OLED E6V. I am trying to set a resolution of 1920x1080 with a refresh of 47.952 (2 x 23.976) and if I can get that working I'd like to try 71.928. I've created these refresh rates using CRU, and they are available for me to select when changing my adapter settings and monitor refresh rate. I can select them and confirm that MadVR detects I'm running at the refresh rate I've just created. Something isn't working though, since films that are 23.976fps should in theory look the same as they do with my 23.976hz refresh rate, but they look much more choppy. I would like to use these custom refresh rates, if I can get them working properly, to use SVP, as I'd like to eliminate the need for Reclock.

I discussed this in the SVP forum and there was some suggestion that it may not be possible to effectively use a custom refresh rate on the 2016 LG OLEDs. Can anyone offer any insight into what I might be doing wrong, or if what I am trying to do is impossible?

I've attached some images showing some of what I've done.


Attached File(s) Thumbnail(s)
       
Find all posts by this user
Quote this message in a reply
 Post Reply


Forum Jump:


User(s) browsing this thread: 90 Guest(s)