On the horizon stands a new version of the program....just when will it happen? Dunno yet, sometime *soon*. Also a note about a recent article post.
David and I have been enthralled in 'life' at the moment and so a new version of NVRT really hasn't crossed our minds any time lately. Yet with the release of 41.03, and some ideas given to us by other developers, NVRT will soon be out...
What I can tell you is this: NVRT will support 41.03 in the next run, but support will be experimental. Thanks to Unwinder(RivaTuner Developer) for his helpful discussion earlier this morning about it. Though I still may want to label 41.03 support as experimental, but for all intents and purposes should still work fine. I've been running on refresh fixed 41.03 drivers for quite some time now(self-fixed).
Add support for Horizontal and Vertical span modes. Again, suggested to us by *someone* and so we'll see what we can do. I can't say that anybody else has emailed us about this but hey what the hell, right? As a note for this latest article going around the internet claiming about how such registry modifying programs damage TV-Out abilities, we have had no claims supporting this *whatsoever*. To my knowledge, nobody has had issues with TV-Out provided they do it correctly.
If it does not work for you, you can do the following: For the resolution you want to run tv-out, make sure to set that resolution to support 60Hz. Sorry 'bout that, LOL. Just how it goes.
In the event that the previous fix does not fix it, do that fix, and then set your Windows resolution to that resolution, with 60Hz. Then try again.
Finally, if none of that works, there's always good old TV-Tool. Again, as far as I know, the 'problem' does not affect NVRefreshTool as the methods I have described have been used for the duration that NVRT has been around. But hey if you've experienced otherwise, that's why we have a support email to contact. Though I do believe that this 'problem' may lie with how the other programs store registry key information...though I haven't had the chance to see for myself.
Hope that this proves helpful and that yes, we are still dedicated to the project.
David and I have been enthralled in 'life' at the moment and so a new version of NVRT really hasn't crossed our minds any time lately. Yet with the release of 41.03, and some ideas given to us by other developers, NVRT will soon be out...
What I can tell you is this: NVRT will support 41.03 in the next run, but support will be experimental. Thanks to Unwinder(RivaTuner Developer) for his helpful discussion earlier this morning about it. Though I still may want to label 41.03 support as experimental, but for all intents and purposes should still work fine. I've been running on refresh fixed 41.03 drivers for quite some time now(self-fixed).
Add support for Horizontal and Vertical span modes. Again, suggested to us by *someone* and so we'll see what we can do. I can't say that anybody else has emailed us about this but hey what the hell, right? As a note for this latest article going around the internet claiming about how such registry modifying programs damage TV-Out abilities, we have had no claims supporting this *whatsoever*. To my knowledge, nobody has had issues with TV-Out provided they do it correctly.
If it does not work for you, you can do the following: For the resolution you want to run tv-out, make sure to set that resolution to support 60Hz. Sorry 'bout that, LOL. Just how it goes.
In the event that the previous fix does not fix it, do that fix, and then set your Windows resolution to that resolution, with 60Hz. Then try again.
Finally, if none of that works, there's always good old TV-Tool. Again, as far as I know, the 'problem' does not affect NVRefreshTool as the methods I have described have been used for the duration that NVRT has been around. But hey if you've experienced otherwise, that's why we have a support email to contact. Though I do believe that this 'problem' may lie with how the other programs store registry key information...though I haven't had the chance to see for myself.
Hope that this proves helpful and that yes, we are still dedicated to the project.
