|
Post by jeremyfitz on May 4, 2016 13:07:18 GMT -8
Anyone else having an issue when executing a batch command...like add eq 8 for example.....and then the next batch command you execute like maybe add compressor for example.....yields ANOTHER eq 8 being added....?
It doesn't seem to matter if it's the same track or not, and hitting the batch command a 2nd time seems to execute the intended function....But it's almost like the batch commander has a "ghost memory" of your previous instruction and carries it out regardless of the current one.....Ableton 9.6.1, OSX Mavericks, latest Raven software etc
|
|
|
Post by jameyz on May 4, 2016 13:30:36 GMT -8
Anyone else having an issue when executing a batch command...like add eq 8 for example.....and then the next batch command you execute like maybe add compressor for example.....yields ANOTHER eq 8 being added....? It doesn't seem to matter if it's the same track or not, and hitting the batch command a 2nd time seems to execute the intended function....But it's almost like the batch commander has a "ghost memory" of your previous instruction and carries it out regardless of the current one.....Ableton 9.6.1, OSX Mavericks, latest Raven software etc I have seen this before. The name of the plugin was still in the search field and didn't get overwritten. I find adding a "CMND A" then a "backspace" after the CMND F is useful, to be sure the name was overwritten before searching. A script like this works every time for me.
|
|