Hi James, thanks for replying.
No, please believe me; You know how long I have been around here. There are broken vsync implementations all over the place. There are numerous people on this forum that have been helped by Reclock vsync, even with the latest commercial players. This here is just the latest:
http://forum.slysoft.com/showthread.php?p=328538#post328538
With the non-commercial players several codes have tried to fix EVR's broken vsync - A chap called Arto Jarvinen, who I have had extensive discussions with, as had a go at a custom renderer for mpc-hc, as well as writing his own player -
http://www.ostrogothia.com/. mpc-hc actually has two custom renderers that try to fix vsync. Both get very close but are not perfect. MediaPortal has also written it's own custom EVR renderer to try to fix the same problem.
It is not that EVR does not try to fix it, it is just that it does not do it reliably, at least for a lot of people. A small percentage of the time it will start or drift into a judder state and, with Reclock's improved clock especially, this state can go on forever!! You are right, though, that normally Reclock would "fight" against standard EVR. Fortunately, new renderers, like Arto's "EVR Sync" allow you to turn off all vsync correction so Reclock can take over, at least in fullscreen exclusive mode, or when Aero is used, both of which effectively introduce triple buffering, which allow Reclock to successfully move its vsync target, without fighting. The custom EVR renderers used for protected mode playback in PDVD and TMT have the same effect. Aero though introduces a significant latency that can really alter the ideal target point.
And I really really promise I know the difference between players and Reclock fighting to control vsync and when Reclock can and is controlling it. You can see in the link to this forum above that we saw that problem when crisliv tried MadVR and straight away got problems because of its, working, vsync code fighting Reclock.
Anyway, I don't want to waste your time reading a huge novel.
All I can say is that some enthusiasts out there
really really still appreciate Reclock and its vsync correction. The little change I have asked for would sure help me.
I have seriously tried fixing this myself. I wrote a Reclock notification script that changed "VsyncTarget". Trouble is I discovered that Reclock has already loaded this value from the registry by the time the script is run and the new value is not effective until the next time Reclock starts.
I know you are busy and I do understand why Reclock is "done". However. all that would be needed is for Reclock to look in the registry for a manually created custom vsync target when it loads and instead load that instead of the value from "VsyncTarget". Easy, for me to say I know, but it is probably less than 10 lines of code, I wish I could do it myself.
I would be very, very grateful, but understand if not!