Waves SuperTap and tempo sync

Hi sharke
This happened to me with my waves plugins. IIRC, I fixed it by manually updating cakewalk's settings for the plugin in the Windows registry. The plugin settings in Sonars plugin manager are actually just updating the registry, so if you search the registry for the plugins filename you should find a spot where you can indicate to Sonar that the super tap plugin is a tempo based effect...I think you just change a value from zero to one...search your registry for the filename and it should be pretty evident when you've found the right spot. 


Good luck
Dean

Thanks Razorwit, I'll search the registry. 

Mosvalve: that's what you'd think, but it doesn't work. SuperTap does not detect the host tempo. You can set it manually, but that's going to be a pain if you have any tempo changes. 

The sliders are a pain in the butt. I usually keep the mouse button pushed down until the slider kinda settles down to the value I want. For me, this works fairly well. Other than that I really like this plug.

Do you know if they register properly as tempo-based etc in other hosts, or whether that's just a Sonar thing as well? It's really weird that they won't have their properties updated through the plugin manager - you would think it was just editing the registry values the same as if you did it manually (which works). 

hey sharke,
the best thing to do with any plugin that you need to configure like this is remove any instances from the project, then close sonar.  run the plug-in manager standalone and change the vst to tempo sync. then, rescan the vsts again. close plugin manager, relaunch sonar and re-insert the plugin.  just tried this with supertap and it follows tempo changes in a project correctly. 

as far as the gui problems, did you run the installer in compatability mode for windows 7??? might be worth a shot.

the plugin manager has a separate executable file located in C:\Program Files\Cakewalk\Shared Utilities

cheers

i tried setting the audio track to my interface input (previously it was none, because it was a loop-only track).  still jitters.  the problem for me starts when i play audio.  i insert super tap and set up the delays (sliders work fine).  play audio and open the plug and move the sliders - jitter city!  turn off the audio engine (i think that's the key) and no jitters moving the sliders.  i'm a little bit suspicious when i hear tech support can't recreate something.  that's why i make videos of the sitch and send it along! :)

anyway - it looks like as long as you turn off the audio engine you'll be jitter-free.  no biggie i guess.

Thanks for those workarounds Don. Does seen strange to JBridge it but if it works it works. Not sure if I'm willing to shell out for JBridge just for this though (or maybe I should bite the bullet and see if it helps with Cakewalk's tape sim crashing as well). 

However, I did receive a reply from Waves this morning, and this is what they said (hope they don't mind me sharing):


"We were able to reproduce this issue on our test machines.
Like you describe, this happens when SuperTap is placed after a VSTi in Sonar X2.


Our QA has acknowledged this as a bug. 
We will be in touch with CakeWalk, and work with them to solve this.
A fix will be issued either by Waves or in a future iteration of Sonar, depending on which code is causing this.


Many thanks for reporting.
We will be working on a fix for this this ASAP.


As for the rounding of entered values, this is by design.


You'll also notice that the slider moves at a certain resolution when moved by mouse.
If you want to get a finer ms resolution, 
you need to increase the (internal) plugin BPM when it is un-synced (manual mode) from the host clock. 


Supertap resolution goes from 40BPM up to 1200BPM.
Explanation: 
you have a time resolution of 8ms under 120BPM clock, 
you can double the BPM (240) to get 4ms resolution, 480BPM gets you to 2ms and 960BPM will get you to a 1ms resolution.


Hope this helps
and thank you again for reporting this bug and for your patience."


So hopefully we'll see a fix in due course. At least I now know why the plug was rounding ms values as well.