fpga4fun tft lcd driver quotation

I haven"t used LVDS at all - cheaper and easier to purchase boards for that. And the highest (or is it lowest?) VEE I"ll use is -28V for the dual scan 640x480"s. Driving TFT"s is much easier, just faster. Things start to get hairy when you have to deal with colour tables for CSTN, using FRM where each byte written to the display is RGBRGBRG etc..

Thanks, I wasn"t sure it would do that or delete the mode, so instead, I did a clean install of the drivers to make sure I started with a clean slate.

The only thing bad, the display of my laptop will not let me add another mode. He says "the GPU driver rejected this mode, for unknown reasons". Is a Intel HD 630...

When I"m trying to apply the modes, there"s an error message with "The GPU driver rejected this mode, for unknown reasons". It behave the same way with the Intel"s internal GPU.

OMGosh. I"m not sure if it"s the new Nvidia drivers or Windows 10, but I can"t get 3D to work *at all* on my PC now, using my Nvidia 1070. Activating 3D in the OS control panel doesn"t do squat. Trying to activate 3D in the Nvidia control panel is painful, it opens up a new window, which then crashes. There"s a reason why I recommend people to stick to Windows 8.1. Unfortunately nobody seems to be listening to me. Personally, I"d have loved to stay on Windows 8.1, but I had to switch to Windows 10 because of my commercial work.

The only thing bad, the display of my laptop will not let me add another mode. He says "the GPU driver rejected this mode, for unknown reasons". Is a Intel HD 630...

When I"m trying to apply the modes, there"s an error message with "The GPU driver rejected this mode, for unknown reasons". It behave the same way with the Intel"s internal GPU.

I think Optimus always runs through the Intel GPU for final output, so this will only work if the Intel GPU drivers work correctly. Unfortunately they"re mostly broken for custom resolutions. I"m trying to get them fixed, though.

I let the movie run for 2/3min. The thing is that, while the movie is playing, if I switch from wfs to fse in the settings, the frame repeat/drop stat immediatly updates to a value coherent with the optimization done previously and with the clock deviation. It"s as if the wfs mode wasn"t taking into account the new custom mode, even if the madvr settings indicates it is currently active. I did not tinker with custom modes in the nvidia cpl, I"m currently on a fresh driver install.I do however have an AVR in my display chain, not sure if this could have an impact ..

OMGosh. I"m not sure if it"s the new Nvidia drivers or Windows 10, but I can"t get 3D to work *at all* on my PC now, using my Nvidia 1070. Activating 3D in the OS control panel doesn"t do squat. Trying to activate 3D in the Nvidia control panel is painful, it opens up a new window, which then crashes. There"s a reason why I recommend people to stick to Windows 8.1. Unfortunately nobody seems to be listening to me. Personally, I"d have loved to stay on Windows 8.1, but I had to switch to Windows 10 because of my commercial work.

Same crash with the 3D Vision wizard. So it doesn"t seem to be a driver issue, maybe an OS update issue? I hope you can get your nVidia contact to look at this, as you"re able to reproduce in your system.

I let the movie run for 2/3min. The thing is that, while the movie is playing, if I switch from wfs to fse in the settings, the frame repeat/drop stat immediatly updates to a value coherent with the optimization done previously and with the clock deviation. It"s as if the wfs mode wasn"t taking into account the new custom mode, even if the madvr settings indicates it is currently active. I did not tinker with custom modes in the nvidia cpl, I"m currently on a fresh driver install.I do however have an AVR in my display chain, not sure if this could have an impact ..

I"ve found that sometimes I was able to create 23p overrides, but then at some point it stopped working for me completely. So I wonder if now maybe your driver got into a state where you can"t define 23p overrides, anymore, either? At all, I mean? So please double check if the standalone tool really still works. Also interesting would be to check if the Nvidia custom res control panel works. In my situation, whenever the "custom modes" tab isn"t able to create a custom mode, the Nvidia custom res control panel fails, too. Well, it doesn"t report any errors, but it also doesn"t create any custom modes.

Same crash with the 3D Vision wizard. So it doesn"t seem to be a driver issue, maybe an OS update issue? I hope you can get your nVidia contact to look at this, as you"re able to reproduce in your system.

I"ve found that sometimes I was able to create 23p overrides, but then at some point it stopped working for me completely. So I wonder if now maybe your driver got into a state where you can"t define 23p overrides, anymore, either? At all, I mean? So please double check if the standalone tool really still works. Also interesting would be to check if the Nvidia custom res control panel works. In my situation, whenever the "custom modes" tab isn"t able to create a custom mode, the Nvidia custom res control panel fails, too. Well, it doesn"t report any errors, but it also doesn"t create any custom modes.

Note: all this testing was done after clean re-install of the latest nVidia drivers, as the older ones make no difference re the non-MadVR related 3D Wizard crashing bug.

Thanks but I never used the nVidia custom res, and the last tests I reported were made after a clean re-install of the latest drivers, so no MadVR custom res either to start with.

OMGosh. I"m not sure if it"s the new Nvidia drivers or Windows 10, but I can"t get 3D to work *at all* on my PC now, using my Nvidia 1070. Activating 3D in the OS control panel doesn"t do squat. Trying to activate 3D in the Nvidia control panel is painful, it opens up a new window, which then crashes.

I have a LG B6 OLED 4K TV. Prior to starting this adventure I uninstalled the old GPU driver by using DDU, then installed the latest Geforce 385.28 driver for my GTX 1060.

It works up to the point where I get the same problems with �jumping� frames (both, in 2D and 3D) which was already addressed some month ago for Win10 (�an Intel driver issue). You were able to fix it for Win10.

I know you are deep into other things� but maybe now, since in principle you know what the basic problem is, it would be easier to fix it for Win81� (the very same driver 154519.4678.zip works for Win10)

First I would like to thank madshi for the latest madvr release. HDR10 now works fine with the latest nvidia drivers (385.28 on gtx 1080), even in FSE. Automatic switching works flawlessly as well. I have finally moved from 378.92 as it seems all HDR problems are now fixed with the latest drivers.

Unfortunately 3D has stopped working with the latest drivers. I am able to enable stereoscopic 3D and run the wizard successfully. But once 3D is enabled MPC-HC crashes as soon as it goes to full screen. I have tried with both 3D and non-3D mkvs. Even 4K files which will not launch in a 3D resolution crash MPC instantly on going into full screen (if stereoscopic 3D is enabled in nvidia).

I have another PC with a gtx 1080 still on the old drivers (378.92) on which 3D works fine with madvr 0.92.1. Both PCs are on windows 10 creators update. My feeling is something has changed recently on the nvidia 3D drivers. I humbly request madshi to please look into this problem as madvr 3D is a great feature.

I"ve made a batch file (adapted from the one in the link in my earlier post) to fix the registry keys and enable 3D on the fly (without having to go through the buggy 3D wizard). I now run this batch file every time I switch my PJ to 3D with iRule, so 3D works for me 100% of the time, whether it was enabled or not in the nVidia control panel. I hit the 3D button on iRule, it runs the batch file to make sure 3D is enabled in the nVidia control panel, selects the 3D mode on my JVC (high lamp) and 3D works reliably (finally!). Of course not as good as a driver/OS fix, but a very acceptable temporary workaround.

Unfortunately 3D has stopped working with the latest drivers. I am able to enable stereoscopic 3D and run the wizard successfully. But once 3D is enabled MPC-HC crashes as soon as it goes to full screen. I have tried with both 3D and non-3D mkvs. Even 4K files which will not launch in a 3D resolution crash MPC instantly on going into full screen (if stereoscopic 3D is enabled in nvidia).

I have another PC with a gtx 1080 still on the old drivers (378.92) on which 3D works fine with madvr 0.92.1. Both PCs are on windows 10 creators update. My feeling is something has changed recently on the nvidia 3D drivers. I humbly request madshi to please look into this problem as madvr 3D is a great feature.

See above. My rig is similar to yours (see my sig below) and I have no crash, but I still have to use FSE for 3D otherwise I get 2D, even if the display switches to 1080p23FP and MadVR OSD reports D3D11 (3D). The picture definitely isn"t 3D without FSE. With FSE, no crash, all perfect, and that"s with the latest drivers.

Ok, I had some time to tinker around and here are my findings (I did a reset of madvr settings on a clean driver install with madvr custom mode enabled and optimized for 2160p23).

It worked! I did a clean uninstall + reinstall of mpc-hc, madvr, lav filters and the nvidia drivers. Enabled stereoscopic 3D in nvidia which ran the wizard successfully. Enabled 3D in madvr and FSE. Opened 3D mkv and voila, TV switches to 3D and no crash! Thanks again for the responses, gave me the confidence it could be done and just something was wrong at my end. Not too sure what it was, but clean install did the trick.

I have implemented 5 custom resolutions for my TFT monitor and 5 custom resolutions for my projector according to common video frame rates and the valid refresh rate range for each device.

That"s quite surprising! Both my LCD computer monitor and my Sony 4K TV accept virtually anything I throw at them. And at some point I did a very quick test with my X35 and changing some timing parameter manually worked just fine, too. Maybe I need to improve my "compatability rating" somehow, I"m not sure. Or could it be possible that your AVR doesn"t like custom modes? Could you try without the AVR, just as a test?

There"s only 2 options: Either I call the Nvidia APIs correctly or incorrectly. If I call the APIs correctly, then anything that goes wrong is the Nvidia driver"s fault, and there will be nothing I can do about it. If I call the APIs incorrectly, then of course it"s my bug can I can fix it. So the key question is if I"ve done something wrong or not.

It"s a known driver issue. You can try to work around it by lowering the number of pre-presented frames in the madVR settings. There"s nothing I can do about this.

I have a LG B6 OLED 4K TV. Prior to starting this adventure I uninstalled the old GPU driver by using DDU, then installed the latest Geforce 385.28 driver for my GTX 1060.

Unfortunately that"s an issue with the current Nvidia drivers. I"ve reported it, and hope to get it fixed soon. But it"s out of my hands, so I can"t promise anything.

It works up to the point where I get the same problems with �jumping� frames (both, in 2D and 3D) which was already addressed some month ago for Win10 (�an Intel driver issue). You were able to fix it for Win10.

The fix I made was not specific to win10, it should work on all OSs. So there"s not really much I can do about this right now. It"s definitely a driver issue, but my fix is supposed to help, at least it did for me.

Ok, I had some time to tinker around and here are my findings (I did a reset of madvr settings on a clean driver install with madvr custom mode enabled and optimized for 2160p23).

The custom modes work well for me with Nvidia"s current driver (385.28). madVR has to switch to it once using display modes, entered there as 2160p23, before it shows up but after that it is in Nvidia"s control panel, albeit as a custom 24Hz mode.

The custom modes work well for me with Nvidia"s current driver (385.28). madVR has to switch to it once using display modes, entered there as 2160p23, before it shows up but after that it is in Nvidia"s control panel, albeit as a custom 24Hz mode.

The custom modes work well for me with Nvidia"s current driver (385.28). madVR has to switch to it once using display modes, entered there as 2160p23, before it shows up but after that it is in Nvidia"s control panel, albeit as a custom 24Hz mode.

It worked! I did a clean uninstall + reinstall of mpc-hc, madvr, lav filters and the nvidia drivers. Enabled stereoscopic 3D in nvidia which ran the wizard successfully. Enabled 3D in madvr and FSE. Opened 3D mkv and voila, TV switches to 3D and no crash! Thanks again for the responses, gave me the confidence it could be done and just something was wrong at my end. Not too sure what it was, but clean install did the trick.

How does it work for you ? I tried clean installation and it doesn"t work. since driver 384.xx it didn"t work, 382.xx works fine. did you also install 3DTV ? or just the 3Dvision that comes with nvidia drivers ?

How does it work for you ? I tried clean installation and it doesn"t work. since driver 384.xx it didn"t work, 382.xx works fine. did you also install 3DTV ? or just the 3Dvision that comes with nvidia drivers ?

Just the basic 3D drivers that come with nvidia. I went straight from 378.92 to 385.28 and things are working fine for me. This is the software i reinstalled during the clean installation

The custom refresh rate I added in cru 1.3 was 72 hz with "automatic lcd standart". Also when the optimize message was shown, in madvr it was 1 frame repeat every 1 hour but in optimized timings it was 40 sec...

The Nvidia setting has multiple different settings, I think. If you force it to 8bit then probably the Nvidia driver downconvert madVR"s 10bit output to 8bit, which is bad. So if you want madVR to output 10bit, it would make sense to not force the output to be 8bit in the Nvidia GPU driver, of course. I think you can just let the driver decide the output bitdepth. Or if you have to override/force it to a specific bitdepth, for some reason, then for 10bit output to reach the display, you need to use 10bit (which I think is not available) or 12bit.

Interesting, I tried "reset-all", but it didn"t help for me. The NVidia driver still refuses to override any 2160p modes with my 4K Sony TV, for whatever reason.

I did use "reset all" and made a fresh driver install after I stopped using CRU and reverted back to Reclock. But I think somehow something got screwed up OS wise: as cork_OS mentionned, I think it did something to the way the EDID of my TV setup is read, only "reset all" didn"t work for me. After using CRU, the native resolution for my AVR / TV was 1080p whereas beforehand it was 2160p. I frankly don"t want to make you lose time over this until I do a fresh Windows install to be sure.

No I"ve never used CRU. I"ve only tried doing a custom resolution through the nvidia control panel once but I always do a "clean install" when I update drivers.

[EDIT: after taking a glance as to what the HDMI spec (http://www.fpga4fun.com/files/HDMISpecification13a.pdf#page=114) has to say on this (HDMI 1.3a �7.2 and especially table 7-3), this might be a bit more complicated than just aiming for 24/1.001, but I would still expect there is a consistent universal target that can be optimized for. The spec does say that sources are allowed to use different clocks for audio and video but it"s not clear why a GPU would do that since it would just make things more complicated for no reason. There"s no reason why a GPU would not just use the recommended values in table 7-3, in which case an universal target can be made for any hardware that uses these values.]

That"s quite surprising! Both my LCD computer monitor and my Sony 4K TV accept virtually anything I throw at them. And at some point I did a very quick test with my X35 and changing some timing parameter manually worked just fine, too. Maybe I need to improve my "compatability rating" somehow, I"m not sure. Or could it be possible that your AVR doesn"t like custom modes? Could you try without the AVR, just as a test?

There"s only 2 options: Either I call the Nvidia APIs correctly or incorrectly. If I call the APIs correctly, then anything that goes wrong is the Nvidia driver"s fault, and there will be nothing I can do about it. If I call the APIs incorrectly, then of course it"s my bug can I can fix it. So the key question is if I"ve done something wrong or not.

Just the basic 3D drivers that come with nvidia. I went straight from 378.92 to 385.28 and things are working fine for me. This is the software i reinstalled during the clean installation

Its a monitor connected via DVI directly to the GFX card. When I look at the identfication of it in madVR I see the following and there is no tab with "raw edid data". any idea why the custom resolution tab appears and then quickly disapeers in this situation? Screenshot below and I have confirmed windows has the monitors driver installed (win 7 x64 although I use 32bit madVR).

Its a monitor connected via DVI directly to the GFX card. When I look at the identfication of it in madVR I see the following and there is no tab with "raw edid data". any idea why the custom resolution tab appears and then quickly disapeers in this situation? Screenshot below and I have confirmed windows has the monitors driver installed (win 7 x64 although I use 32bit madVR).

It works up to the point where I get the same problems with �jumping� frames (both, in 2D and 3D) which was already addressed some month ago for Win10 (�an Intel driver issue). You were able to fix it for Win10."

The fix I made was not specific to win10, it should work on all OSs. So there"s not really much I can do about this right now. It"s definitely a driver issue, but my fix is supposed to help, at least it did for me.

maybe, but on the other Hand MPC-BE"s EVR-CP renderer does not show such problems in 2D (obviously I can not check for 3D); I have checked several Driver Versions on Win81 (4508, 4526, 4665, 4678) with the same result; somtimes it takes a Minute until the Problem sets in;

I"m not sure this is correct. When I tested the direct connection to the JVC earlier, I"m almost 100% sure that when I added the 4K23 custom mode, it appeared with data available. It shouldn"t be the case as technically it was a different display (AVR vs JVC). In any case, when we delete the custom mode, it might be a good idea to also delete the corresponding recorded data, to make sure we can start afresh if we decide to re-create the mode, without having to do a clean install of the drivers.

I tried adding a custom mode of 1920x1081, but that doesn"t work. I get an error that says "The GPU driver rejected this mode for unknown reasons", even though I copied the front/back porch and sync settings exactly.

I"m not sure this is correct. When I tested the direct connection to the JVC earlier, I"m almost 100% sure that when I added the 4K23 custom mode, it appeared with data available. It shouldn"t be the case as technically it was a different display (AVR vs JVC). In any case, when we delete the custom mode, it might be a good idea to also delete the corresponding recorded data, to make sure we can start afresh if we decide to re-create the mode, without having to do a clean install of the drivers.

I tried adding a custom mode of 1920x1081, but that doesn"t work. I get an error that says "The GPU driver rejected this mode for unknown reasons", even though I copied the front/back porch and sync settings exactly.