Jump to content

Automation Timing Issue (SOLVED)


gno

Recommended Posts

I'm trying out my new Waves OneKnob Filter on a track and it isn't working correctly. I'm drawing automation curves to control the Filter Frequency, and for some reason, during playback, the Filter Frequency is moving too fast toward the next node. You can see below on the first image, that the knob moved to 7.0 way before it was supposed to.

 

http://i687.photobucket.com/albums/vv239/guitartrek/OneKnob2_zpsvpucuj5s.png

 

If I manually move the playhead, the knob correctly stays at 4.0

 

http://i687.photobucket.com/albums/vv239/guitartrek/OneKnob1_zpskiem8gvx.png

 

I checked other automation curves that are controlling, for example, volume, and those are working perfectly. This seems like a Logic issue, as it must be telling the OneKnob when to move and giving the instructions prematurely?

Link to comment
Share on other sites

It's not the default for historical reasons: it taxes the CPU a little more, which could be an issue on older systems, so default (no sample accurate plug-in automation) was set this way for CPU optimization purposes. No longer relevant on our modern machines. This said, you screen captures do not display the ruler and it's not clear how much "too early" did the knob move, but unless you zoomed in a lot on the horizontal axis before taking the pictures above, I'm surprised you got what appears like a fairly large offset.
Link to comment
Share on other sites

Archived

This topic is now archived and is closed to further replies.

×
×
  • Create New...