Quote:
Originally Posted by Kaneepa  didn't have any success..
Movements in ride are too slow even at maximum speed.. |
Don't forget to nudge the automation back by 300ms.
Quote:
When will the $75 introductory pricing end?
And what will the standard price be afterwards?
|
Once we establish a user base we might bump the price, but when and what I don't know yet.
Quote:
|
Ride function works great but I haven't been able to succesfully to get the duck function to work properly. I'm running PT8 HD cs2. I'll stick to sonalksis ducker which is very flexible and efficient, but i would love this function to work properly.
|
Duck function is tricky to get used to. Main thing to watch is the PARK level. PARK level is the undipped level of your music track (or whatever) to play at. For instance if you leave the PARK level at say -10, your ducking range should be below that. Ducking range is relative to the output slider position. If output slider is as -18 this means the ducking range slider is referencing 0 on the PT fader, therefore -15 on this slider will go to -15 on the PT slider (when output is -18)
Quote:
|
The ride function is impressive, and works as advertised. I just have to figure out it's exact latency. It needs some smoothing in trim but gets the dynamics right. I just wish there was a dynamic range target slider, like make this vocal have a 3db range or 7db range depending on program
|
It's roughly around 300ms on the systems I have been testing it including LE, HD. But you can adjust that to taste. Ducking works fine realtime, again you might want to slide to taste. As for the dynamics, you can play around with the
Silence slider. You could set it high so that it ignores soft levels and attenuates only when the threshold is exceeded, like a standard compressor.
I will try and post some session templates soon. And a page with tips perhaps. thumbsup
Cheers
Vedat