Hi Ron!
Just been playing around heaps to get scenes working well with the GT, and I thought I'd share how I've come up with things so far, plus a few questions/feature request
My button setup is still evolving, but so far I've decided to have 3 presets and 3 scenes all along the bottom row to maintain IA real estate, and with scenes it's almost as if I now have 9 presets to chose from now!
To get it working properly the IAs have to send CC momentary, with on/off values being the same. They should be assigned a group. I managed to get the GT to default to the first button in the group by turning on 'local update' for all of the buttons, otherwise the selected scene will persist upon preset change even though the axefx defaults to scene 1. I noticed this changed from 'dev update' between firmware 1 and 1.1 - are they the same thing/is this the intended behaviour?
Anyhow it works great but what would make it truly awesome and keep it above par with the MFC-101 is to have the IA buttons update with each scene selection. I'm not sure how you'd implement it, whether have 'Scene' as a new button type, or have an extra setting in 'more setting' to toggle for any button to poll the axefx when pressed?
Also it would be really neat to either assign for each preset in the GT a starting scene so you can send a scene CC to the axe after the PC message, or alternatively to poll the axe on each PC change for the current scene (if that's possible) for those using the custom mapping feature on the axefx. Although I think the first suggestion might allow more flexibilty, keeping the GT at the top of the chain and having it do all the work.
What do you think?
Cheers
Glenn
Just been playing around heaps to get scenes working well with the GT, and I thought I'd share how I've come up with things so far, plus a few questions/feature request
My button setup is still evolving, but so far I've decided to have 3 presets and 3 scenes all along the bottom row to maintain IA real estate, and with scenes it's almost as if I now have 9 presets to chose from now!
To get it working properly the IAs have to send CC momentary, with on/off values being the same. They should be assigned a group. I managed to get the GT to default to the first button in the group by turning on 'local update' for all of the buttons, otherwise the selected scene will persist upon preset change even though the axefx defaults to scene 1. I noticed this changed from 'dev update' between firmware 1 and 1.1 - are they the same thing/is this the intended behaviour?
Anyhow it works great but what would make it truly awesome and keep it above par with the MFC-101 is to have the IA buttons update with each scene selection. I'm not sure how you'd implement it, whether have 'Scene' as a new button type, or have an extra setting in 'more setting' to toggle for any button to poll the axefx when pressed?
Also it would be really neat to either assign for each preset in the GT a starting scene so you can send a scene CC to the axe after the PC message, or alternatively to poll the axe on each PC change for the current scene (if that's possible) for those using the custom mapping feature on the axefx. Although I think the first suggestion might allow more flexibilty, keeping the GT at the top of the chain and having it do all the work.
What do you think?
Cheers
Glenn