Post by guydenruyter on Dec 9, 2006 14:43:30 GMT
Hi,
In song mode, I like to use controller messages to change padding, volume etc on the spot in a track. I do this by manually inserting the CC# events in the track.
However, it appears that the Fusion ignores those messages unless you select 'Enable Mixer Automation'.
So far so good, but the annoying thing is that when you check this 'Enable Mixer Automation', as soon as you record one thing on one track, the Fusion takes the liberty of inserting tuns of CC# events in EVERY track (more precisely, CC#9, CC#7, CC#10, CC#91 and CC#93). These controller events correspond to the settings you have in your track for volume, pan, FX bus send etc.
I consider this very annoying and pollutive:
- annoying because often at the end of your composition you start mastering and want to tweak volume, pan, FX etc
- pollutive because all those CC#s are inserted on every track and every time you press record
I guess I can avoid this by deselecting the 'Mixer Automation' option each time before I start recording, but this is of course quite cumbersome.
Does anyone have an idea why Alesis implemented this that way?
I see two ways to improve this behaviour:
- Alesis could make the Fusion always respond to CC#messages (also without this record mixer automation option checked)
- Alesis could give us an option to indicate what we want to record when we enable mixer automation (both in terms of events and in terms of 'crosstalk' to other tracks)
Just curious about your thoughts and experiences!
In song mode, I like to use controller messages to change padding, volume etc on the spot in a track. I do this by manually inserting the CC# events in the track.
However, it appears that the Fusion ignores those messages unless you select 'Enable Mixer Automation'.
So far so good, but the annoying thing is that when you check this 'Enable Mixer Automation', as soon as you record one thing on one track, the Fusion takes the liberty of inserting tuns of CC# events in EVERY track (more precisely, CC#9, CC#7, CC#10, CC#91 and CC#93). These controller events correspond to the settings you have in your track for volume, pan, FX bus send etc.
I consider this very annoying and pollutive:
- annoying because often at the end of your composition you start mastering and want to tweak volume, pan, FX etc
- pollutive because all those CC#s are inserted on every track and every time you press record
I guess I can avoid this by deselecting the 'Mixer Automation' option each time before I start recording, but this is of course quite cumbersome.
Does anyone have an idea why Alesis implemented this that way?
I see two ways to improve this behaviour:
- Alesis could make the Fusion always respond to CC#messages (also without this record mixer automation option checked)
- Alesis could give us an option to indicate what we want to record when we enable mixer automation (both in terms of events and in terms of 'crosstalk' to other tracks)
Just curious about your thoughts and experiences!
