Elevatormusicmaker Posted July 5, 2015 Share Posted July 5, 2015 OK so I am working on a friend's LPX project while he is away, and I am wondering if this problem is something to do with any settings he may have changed, or whether its a bug altogether. Lets say I wanted to automate the downsampling value in Logic's bitcrusher. I select this from the track header automation parameter window. However, when I start drawing an automation line, this parameter changes itself to something completely unrelated to the plugin (or any other plugins used on that particular track). In the screenshot attached, one can see that the automation parameter has changed itself to 'frequency response'. As a result, the automation line has no effect on the audio at all. I have tried the latch automation mode. This works fine while recording in the automation data, but when I am finished, it changes the parameter value again. The MIDI info displayed in the automation event list is the same as the info displayed when I connect this particular channel to a monitor in the MIDI environment window. In the screenshot example below, I have two plugins used. If I add a THIRD plugin and attempt to select the parameter I wish to automate, NO automation line appears. WHAT THE HELL IS GOING ON?!?! Link to comment Share on other sites More sharing options...
Eric Cardenas Posted July 8, 2015 Share Posted July 8, 2015 Is this happening if you start from a new empty template? Link to comment Share on other sites More sharing options...
Elevatormusicmaker Posted July 8, 2015 Author Share Posted July 8, 2015 Hi Eric, No, this strange behavior seemed to happen only with that current track I was using, and any new track created within that Logic session from that point onwards. In a new empty template, everything works fine. Link to comment Share on other sites More sharing options...
Recommended Posts
Archived
This topic is now archived and is closed to further replies.