BUG - Waves Supertap GUI does not work in Sonar X2

Yeah, I knew about this one. Take it up with waves and see how seriously they take it... workaround is to double click and enter value manually.

I submitted reports to both Cakewalk and Waves, but no doubt they've both been informed about it before. Of course it's hard to tell whose fault it is but it does seem strange that the sliders work perfectly in Reaper, Pro Tools and I'm assuming other hosts as well (I certainly couldn't find any mention online of the problem in other hosts). 

Another problem I've noticed...and perhaps this is related to my misunderstanding of how the plug works...it will not allow me to set delay times accurately in milliseconds. For example, if I type in a delay of 150ms, it changes when I hit enter. To 143 if I have sync set to auto, 152 if I have sync set to manual. 

I thought this was maybe because it was snapping to some grid, but if I have "snap" turned off and the grid set to "free," the behavior persists. I then found that if I double the BPM of the plug, I can get closer to the ms value I want, but still slightly out. Correct me if I'm wrong, but a delay plug should just let you set the exact ms delay you want without any messing around. 

sharke


Another problem I've noticed...and perhaps this is related to my misunderstanding of how the plug works...it will not allow me to set delay times accurately in milliseconds. For example, if I type in a delay of 150ms, it changes when I hit enter. To 143 if I have sync set to auto, 152 if I have sync set to manual. 

I thought this was maybe because it was snapping to some grid, but if I have "snap" turned off and the grid set to "free," the behavior persists. I then found that if I double the BPM of the plug, I can get closer to the ms value I want, but still slightly out. Correct me if I'm wrong, but a delay plug should just let you set the exact ms delay you want without any messing around. 

Absolutely...


Is this working ok in Pro Tools and Reaper?

If so, then again, I would suspect something "under the hood" in X2a...

When X2 was first released I had an issue where when I opened an X1 project and then
tried to add a Waves Plugin X2 would crash and burn..

My workaround was to open the X1 project and then save it in under a new name in X2.  That solved that problem.  
After saving it in X2 the problem went away and I could work on it just fine.
I've encountered a lot of problems in X2 and now X2a that I don't have in other DAW's.
That's one of the reasons I asked that the "Touch" component be an "Option" and NOT
mandatory.  I really don't use or need the "Touch" and there has to be a "hit" on the 
the graphics engine with the Touch component working in the background.

After I installed X2a, I couldn't even load a few plugins on tracks before things started
getting out of hand.  I have to "freeze" alot now...and I have 16 GB of Ram and lots of free
hard drive space!  Shouldn't be like that.  In  X1d I could load dozens of Plugs and Instruments on lots of tracks and had no problems...so I know it's not my system.
As for "Touch" - that's just an assumption...but I believe a good one...
and if I didn't have to install the "Touch" component it would save some system resources...
I won't use TOUCH for a long while...so I'd like to able to "not install" it for this very reason.

Guitarpima


About the milliseconds being off, maybe the tempo sync is on? An easy way to check it is to find a delay calc and enter in the tempo of your song and see what you get.

No, the problem occurs if have have tempo set to auto or manual. I've also tried all the other possible settings like snap, grid and grid mode. They all produce the same result. 

It's really weird but I cannot find any mention of the ms entry problem anywhere else online. As far as everyone's concerned, it's an excellent plug which works perfectly? How could this be?