Ableton Program Change

[leeleema]

Hi,

I've started using program change messages to select different patches in vsts, within midi clips, in an effort to streamline. But have noticed this disables automation for the track that has clips with program change data, and the 're-enable automation' button needs to be constantly re-pressed.

Automation is controlling the same parameters regardless of patch selection, so this appears to be needlessly restrictive. A google search has proved fruitless. I believe I can do a workaround by using a max device as a midi trigger to re-enable automation but still, this shouldn't be necessary?

This is repeatable with FM8 with program change selecting 1 patch in each of two clips. Automation will grey out at the beginning of each clip. And it is repeatable with other vsts using program change to select patches i.e. all automation greys out when the instrument receives program change data.

Any ideas if this is just frustrating default behaviour, or I'm doing something wrong, or a better workaround?

Thanks

[billybuck]

ClyphX (free or pro version) allows you to drop locator markers that can send specific PC messages when the play head passes over them. I’ve never tried it, so I don’t know if those locators can easily be moved along with your MIDI if you’re shuffling things around to build an arrangement (as you can with automation).

ClyphX has a bit of an installation and learning curve, but it’s definitely easier to get your head around than M4L. For controlling the interface and scripting tedious processes, it’s invaluable.

[Winstontaneous]

If you have Max for Live, there is a very handy device that automatically re-enables automation, put it on one channel as a MIDI effect and it should work across the whole session:
http://www.maxforlive.com/library/devic ... automation

This solved some persistent issues I had in the most complex Ableton project I've made, which had Session MIDI clips with tempo change info and a bunch of other automation (but no program changes). Not sure if its timing works at sample, buffer, or PPQ tick level - but it did the job perfectly for me with no audible artifacts.

The Ableton help for this is not very helpful, and ideally you should not need M4L to automatically re-enable automation.

[leeleema]

ClyphX (free or pro version) allows you to drop locator markers that can send specific PC messages when the play head passes over them. I’ve never tried it, so I don’t know if those locators can easily be moved along with your MIDI if you’re shuffling things around to build an arrangement (as you can with automation).

ClyphX has a bit of an installation and learning curve, but it’s definitely easier to get your head around than M4L. For controlling the interface and scripting tedious processes, it’s invaluable.

Cheers mate

[leeleema]

If you have Max for Live, there is a very handy device that automatically re-enables automation, put it on one channel as a MIDI effect and it should work across the whole session:
http://www.maxforlive.com/library/devic ... automation

This solved some persistent issues I had in the most complex Ableton project I've made, which had Session MIDI clips with tempo change info and a bunch of other automation (but no program changes). Not sure if its timing works at sample, buffer, or PPQ tick level - but it did the job perfectly for me with no audible artifacts.

The Ableton help for this is not very helpful, and ideally you should not need M4L to automatically re-enable automation.

This looks like what I was after. My original workaround didn't work as it appears the re-enable automation button is not midi controllable. The whole thing is a bit of a bug really and as much as I appreciate and respect Ableton, part of me does wonder what the developers do all day when something like this should be an easy fix.

Thanks a lot!

[leeleema]

Also, sorry for delay in replying guys, I thought I would get automatic notification of replies to a post, but checking just now, that isn't an option. I'll have to get stuck into my settings!

[pabaker85]

Just wanted to say cheers for this! Definite life saver as I was building a set using MIDI program change messages and was going crazy with automation getting disabled. Ableton really do need to find a solution for this like adding a setting to disable it.

If you have Max for Live, there is a very handy device that automatically re-enables automation, put it on one channel as a MIDI effect and it should work across the whole session:
http://www.maxforlive.com/library/device/3351/fgc-reenableautomation

This solved some persistent issues I had in the most complex Ableton project I've made, which had Session MIDI clips with tempo change info and a bunch of other automation (but no program changes). Not sure if its timing works at sample, buffer, or PPQ tick level - but it did the job perfectly for me with no audible artifacts.

The Ableton help for this is not very helpful, and ideally you should not need M4L to automatically re-enable automation.