Hello,
I just bought the Satin plugin a few days ago.
I wanted to automate some movements with the 'range' knob, but that doesn't seem to work. Other parameters from seemed to be recorded without problems. Maybe a bug?
DAW: Logic Pro X
OS: Yosemite
Greets,
L.
satin range automatisation doesn't work
- KVRist
- 183 posts since 14 May, 2014 from Berlin | Germany
Hi,
it is not a bug. Automating the range would lead to strange effects and mess with the overall delay scheme (since it's through-zero flanging). Should be noted in the manual.
Cheers,
Michael
it is not a bug. Automating the range would lead to strange effects and mess with the overall delay scheme (since it's through-zero flanging). Should be noted in the manual.
Cheers,
Michael
-
- KVRer
- Topic Starter
- 4 posts since 6 Feb, 2015
Hello Michael,
thanks for your reply!
Strange that there was decided not to make this possible. U-he thinks clearly more out of the box with the design of their plugins than some other plug-in designers do with similar products (tape effects, compressors,... all of them featuring mostly the same features as the hardware units they're modelled on).
These particular strange effects I just found very interesting on a specific part of my track, when I was moving around with this knob. It resulted in very nice, but ok also a little weird, pitch-shifting effects.
So, why not make this parameter to be able to automate too, even if this might not be an existing hardware feature?
L.
thanks for your reply!
Strange that there was decided not to make this possible. U-he thinks clearly more out of the box with the design of their plugins than some other plug-in designers do with similar products (tape effects, compressors,... all of them featuring mostly the same features as the hardware units they're modelled on).
These particular strange effects I just found very interesting on a specific part of my track, when I was moving around with this knob. It resulted in very nice, but ok also a little weird, pitch-shifting effects.
So, why not make this parameter to be able to automate too, even if this might not be an existing hardware feature?
L.
- KVRian
- 1141 posts since 2 Oct, 2001 from Berlin, Germany
As Michael already pointed out, our decision is a technical one. It just doesn't work right with many hosts. The reason is latency compensation, especially what happens when the value gets changed on-the-fly or bypass gets pressed. We encountered so many strange effects - depending on platform and host - that we had to disable automation for this parameter entirely.
Sascha Eversmeier [formerly digitalfishphones]
TOURAGE DSP
croquesolid drum processor- mix real drums fast & focused
TOURAGE DSP
croquesolid drum processor- mix real drums fast & focused
