Threaded Mode | Linear Mode

jdubzisfaded · (Last edited: 06-09-2015, 04:04 PM by jdubzisfaded)

(06-06-2015 07:06 PM)ToastyX Wrote:
(06-05-2015 04:54 PM)jdubzisfaded Wrote: What I meant by 320MHz when using nVidia custom resolution, is that I used CRT Timings which brought me to 312MHz and then added extra pixels to the total pixels amount in the manual timings section which may have made it look better or worse I am not a TV guru but I know my way around a PC.
You shouldn't do that unless the TV can't handle standard timing parameters correctly. You're just wasting bandwidth with a higher pixel clock. Use the "LCD standard" timing option.

(06-05-2015 04:54 PM)jdubzisfaded Wrote: and yes 1440p does not show up in Windows but it shows up in nVidia custom resolutions.
I don't understand what you mean because the problem doesn't make sense. If you mean the resolution is selectable in the NVIDIA control panel but not in the Windows screen resolution settings, then I don't see how that could happen unless there's a driver bug. If you mean the resolution is listed in the NVIDIA control panel as a "Custom" resolution instead of a "PC" or "HD" resolution, then that could only happen if you added a custom resolution using the NVIDIA control panel, but then it should also be listed in the Windows screen resolution settings. CRU resolutions wouldn't be listed as "Custom" resolutions, and you don't need to add the same resolutions with both.

(06-05-2015 04:54 PM)jdubzisfaded Wrote: One Time it even showed as native so I thought it was sure to work. Yet as I said I just got an incompatible signal causing my display to display a "no signal" blue screen.
The first detailed resolution in the main window is considered the native resolution. Your screen shot covers up the main window, so I can't see what you have defined for the native resolution. You need to define the resolution you want to be native as the first detailed resolution.

(06-05-2015 04:54 PM)jdubzisfaded Wrote: Also, will the CRU work on all the driver versions.
CRU is not driver-specific. CRU will work with any driver that supports Windows EDID overrides.

(06-05-2015 04:54 PM)jdubzisfaded Wrote: And why do I have no need for pixel patcher. From what I have read on it I will be limited to 165MHz on HDMI.
That is the case with single-link DVI and HDMI on older cards. Newer cards can handle higher pixel clocks with HDMI, but HDMI support must be defined in the extension block or it will behave like single-link DVI.

(06-05-2015 04:54 PM)jdubzisfaded Wrote: I read that I needed an HDMI.dat file but I am at my programming job and can't remote in to my pc too much.
The hdmi.dat file just contains an HDMI support data block with the default settings, so you don't need it if you already added it manually.

(06-05-2015 04:54 PM)jdubzisfaded Wrote: If all of my BS is not 20$ I understand I am being a pain. Name your price in a PM and I will think if it is reasonable
Any donation is welcome.

(06-05-2015 04:54 PM)jdubzisfaded Wrote: edit 3: lol I think my monitor may be off... and thats the only reason it seems to work. I am an idiot. DAMNIT
Some monitors won't send an EDID when they're off or switched to a different input, which can cause problems with monitor detection. Did you get everything sorted out?

yes everything worked out fine. your money will be arriving at the end of the week. If not then it will be the week after. LCD standard is a good option definitely but I have run some tests on a 16x9 ratio calculator and found many other alternatives making the tv look slightly better every time I find a better one. the problem is blur on the scaling.. I dont know if you own or used this tv but at 1440p in order to get 60hz, you sacrifice a lot of picture quality which i am trying to iron out now that the pixel clock is unlocked up to 325Mhz (hardware limit i think). with the original firmware the TV allocated 4400 total pixel width and 2250 height at 1440p if my memory serves. When this is applied it looks wonderful but obviously the pixel clock skyrockets and can only handle 31hz. I am guessing it is just due to the fact the tv is actually running a 4k res but scaling it to 1440p. So I will tinker and tinker some more until I remove this blur. Although it is noticeably better than 1080p (blocky) I am still hoping to achieve atleast 45fps for gaming at a very clear 1440p. I doubt you could have any suggestions since you probably dont own the device and already suggested your recommended timings which amount to a measly 247MHz pixel clock, but I would love for this to be the TV I was looking so forward to receiving. either way CRU is a great utility and I am very thankful for you taking the time to program it as I know next to nothing of EDID customization. But I am going to tear the firmware apart see if i can hex edit some binaries to lower some voltages and allow more power to a single hdmi port and see how hard I can push the pixel clock.

Best Regards,
Thankful User

jarda · 06-11-2015, 04:15 AM

Nobody really has it installed on tens?

Explas · 06-11-2015, 02:11 PM

I'm wondering if this patch is still needed with 353 nVidia drivers? Or it depends on video card? Saw somewhere that GTX 780Ti does not need this patch, how about GTX 980?

***ToastyX*** · 06-11-2015, 09:59 PM

(06-11-2015 02:11 PM)Explas Wrote: I'm wondering if this patch is still needed with 353 nVidia drivers? Or it depends on video card? Saw somewhere that GTX 780Ti does not need this patch, how about GTX 980?

You need to be more specific. What limits are you talking about? Are you using CRU or the NVIDIA control panel?

The patch is required to get past 330 MHz pixel clock with dual-link DVI when using CRU but not when using the NVIDIA control panel.

The patch is always required if you're trying to run a single-link DVI monitor past 165 MHz pixel clock on a dual-link DVI port.

The patch isn't required with HDMI if HDMI support is defined in the extension block. Otherwise, it behaves like single-link DVI, which has a 165 MHz pixel clock limit.

400-series and some 500-series cards need the full patch to get past 400 MHz pixel clock with dual-link DVI.

The full patch is required to get past 400 MHz pixel clock with SLI except for Titan, GTX 780, and 900-series cards.

Explas · 06-12-2015, 07:45 AM

(06-11-2015 09:59 PM)ToastyX Wrote:
(06-11-2015 02:11 PM)Explas Wrote: I'm wondering if this patch is still needed with 353 nVidia drivers? Or it depends on video card? Saw somewhere that GTX 780Ti does not need this patch, how about GTX 980?
You need to be more specific. What limits are you talking about? Are you using CRU or the NVIDIA control panel?

The patch is required to get past 330 MHz pixel clock with dual-link DVI when using CRU but not when using the NVIDIA control panel.

The patch is always required if you're trying to run a single-link DVI monitor past 165 MHz pixel clock on a dual-link DVI port.

The patch isn't required with HDMI if HDMI support is defined in the extension block. Otherwise, it behaves like single-link DVI, which has a 165 MHz pixel clock limit.

400-series and some 500-series cards need the full patch to get past 400 MHz pixel clock with dual-link DVI.

The full patch is required to get past 400 MHz pixel clock with SLI except for Titan, GTX 780, and 900-series cards.

I'm using QNIX QX2710 monitor and GTX 980 card, want to get from it like 100hz, I'm using DVI cable, as per your comment I think that I still need to path my drivers to achieve that.

Explas · 06-12-2015, 04:29 PM

another issue I'm facing at is that via nVidia control panel I cannot control brightness of the screen, what could be the issue?

***ToastyX*** · 06-16-2015, 12:05 AM

(06-12-2015 04:29 PM)Explas Wrote: another issue I'm facing at is that via nVidia control panel I cannot control brightness of the screen, what could be the issue?

I don't know what you mean by that. Is the option not there? Is it grayed out? Is it not having any effect?

Are you not able to adjust the brightness using the monitor's brightness controls? It's better to adjust the brightness through the monitor instead of through the video card.

Explas · 06-17-2015, 09:39 AM

(06-16-2015 12:05 AM)ToastyX Wrote:
(06-12-2015 04:29 PM)Explas Wrote: another issue I'm facing at is that via nVidia control panel I cannot control brightness of the screen, what could be the issue?
I don't know what you mean by that. Is the option not there? Is it grayed out? Is it not having any effect?

Are you not able to adjust the brightness using the monitor's brightness controls? It's better to adjust the brightness through the monitor instead of through the video card.

I have QNIX QX2710 which does not have any adjustments on the screen itself, the options on the nVidia control panel are not greyed out but they does nothing, when I have GTX 560Ti they worked fine, replaced my card with GTX 980, reinstalled drivers and I cannot adjust brightness contrast etc on nVidia control panel Sad

***ToastyX*** · 06-17-2015, 04:11 PM

(06-17-2015 09:39 AM)Explas Wrote: I have QNIX QX2710 which does not have any adjustments on the screen itself, the options on the nVidia control panel are not greyed out but they does nothing, when I have GTX 560Ti they worked fine, replaced my card with GTX 980, reinstalled drivers and I cannot adjust brightness contrast etc on nVidia control panel

The QNIX has backlight brightness controls. The NVIDIA brightness setting won't work the same way. Make sure you are adjusting the desktop color settings and not the video color settings.

Explas · 06-24-2015, 07:08 PM

(06-17-2015 04:11 PM)ToastyX Wrote:
(06-17-2015 09:39 AM)Explas Wrote: I have QNIX QX2710 which does not have any adjustments on the screen itself, the options on the nVidia control panel are not greyed out but they does nothing, when I have GTX 560Ti they worked fine, replaced my card with GTX 980, reinstalled drivers and I cannot adjust brightness contrast etc on nVidia control panel
The QNIX has backlight brightness controls. The NVIDIA brightness setting won't work the same way. Make sure you are adjusting the desktop color settings and not the video color settings.

Thanks, just now realized those buttons really work, tough they are just fake as screen does not give any feedback..