The Glue shows exactly what latency is reported and introduced in the oversampling menu, and this does not change when switching from realtime to render mode, or when bypassing, it always stays the same.DJMaytag wrote: ↑Thu Oct 25, 2018 6:08 amI got a reply of “it’s up to the VST to report the delay” and basically “sorry, not our problem.”
I did follow up and ask how Reason handles real-time (which works fine) versus render (where the problem appears). Clearly there is a problem when rendering, so either Reason doesn’t “tell” VST’s that rendering is happening, or The Glue isn’t somehow reporting the increased latency in render mode.
Whatever the case may be, the recommendation might be to use the same real-time and render oversampling setting to avoid this problem in Reason (I’m on 10.2, but I assume 9.5 and above have the same issue).
There is an advanced feature in Cytomic plugins where you can disable this default behaviour of keeping the latency constant. It is in the Settings.xml file:
<Tuple Key="ForceDynamicLatency" Value="false"/>
This defaults to false, since otherwise it can cause issues with some hosts. Can you please confirm you haven't opened up a text editor and changed this to "true" ?
I have tested the crap out of latency compensation and reporting. I am not trying to pass the buck, but I doubt very much the issue lies with The Glue, this code has been in place for 10 years or so, and Reason has not been hosting VST plugins for very long. What I can do is give you a build of The Glue with debug logging enabled, which will write to a file when it reports latency changes to the host. We can then confirm exactly the latency, and when (with timestamps) the latency is reported with each instance of The Glue. Once we see that The Glue does not dynamically change the latency once reported we can, with complete confidence, contact the Propellerheads and get them to look at it themselves. You will most likely need to give them a cut down example project so they can reproduce the issue, I can give them a license of The Glue with debug logging enabled as well.
ps: I remember a similar issue with Sonar, where I told them they were sending double precision numbers to the sidechain input of VST plugins that reported they only wanted single precision numbers, and so caused The Glue to crash. Cakewalk denied the issue black and blue until years later they finally found out they were doing exactly what I guessed, and then they finally apologised and fixed it. I happily gave my customer a refund because of Cakewalk's bug, and I will happily give you a refund too if you want, since I can't fix bugs in hosts.