Unfortunately there is no good system to "change rack programs" or "change rack presets" . So, I can't switch from one main rack to another. I could use chains - but this does not de-activate the un-needed racks it just routes midi away from them.
This means that in my current live set, where I have 8 main racks, each with many sub racks, I am currently stuck with CPU drain for all 8 racks at once, even though I only play one of them at a time.
With a true 'program change' the Rack would be un-loaded when I was finished with it, as it is I have to map the on/off buttons of the racks to a certain range and make an external application which manages incrementing of a midi variable.
it's clumsy and un-lovely, also I can't see what the hell I am doing.
I need a big screen that says "PROGRAM 2 - PIANOID" really large, not a little macro that says "33%" and I must mentally equate that to the correct preset.
change Rack Preset
Re: change Rack Preset
Hi,Angstrom wrote:Unfortunately there is no good system to "change rack programs" or "change rack presets" . So, I can't switch from one main rack to another. I could use chains - but this does not de-activate the un-needed racks it just routes midi away from them.
This means that in my current live set, where I have 8 main racks, each with many sub racks, I am currently stuck with CPU drain for all 8 racks at once, even though I only play one of them at a time.
With a true 'program change' the Rack would be un-loaded when I was finished with it, as it is I have to map the on/off buttons of the racks to a certain range and make an external application which manages incrementing of a midi variable.
it's clumsy and un-lovely, also I can't see what the hell I am doing.
I need a big screen that says "PROGRAM 2 - PIANOID" really large, not a little macro that says "33%" and I must mentally equate that to the correct preset.
I'm not sure I understand what you're asking for, even though I sense I know what it is.. But to be clear:
- You have a Rack, with many Racks inside. Is that this situation, you want to avoid?
A problem with Rack "programs", or "preset" change, is obviously loading times, if you're using samples inside. So, I'm not sure that what you want is a way to load unload presets, is it? Isn't it that you'd like a better way/display for selecting which sub-rack is "active?
Also, as it is, devices that don't do anything don't consume CPU, or not much.
Let me know what I've missed.
Regards,
Amaury
Ableton Product Team
Hi Amo,
here is the current situation :
I have a Live set, where I play 'keyboards' over the top.
For each song in the set I have a 'preset', each preset is a multi-chain.
here is one of my "presets"
there are about 7 more of those, similar but different. One for each 'song' I play. This is the current situation and I currently attempt to 'change presets' like this:
the on/off' of each 'preset' (sub-rack) is currently mapped to a macro, the macro will de-activate each 'preset' in sequence. This is my method of turning off racks that I don't currently need.
I can;t use chain-select on the main rack, because each of the sub-racks (the presets) will remain actively consuming CPU. This is why I map the on/off switches to de-activate the dis-used presets.
----
the problem
using a macro as a preset select is a lot less useful than the traditional preset selection method for synths. The traditional method can incrementing through a sequence of presets. In a live setting it is good if the presets mirror the set list, the performer usually moves to the next song 'preset' by pressing "up" or may have the preset change pre-programmed into the sequence by using midi program change messages.
A second benefit of the traditional preset system is the ability to see the name of the preset - ("tiny bells" or "Hideous Mighty Klang!" ) to help the performer avoid making the wrong noise.
Currently we can't increment through a set of 'presets' without weird hackery, and without any visual feedback we can;t really see what we have selected.
--------
The Suggestion
The requirements are -
I suggest that a rack of sub-rack 'presets' needs a dedicated facility to select and de-activate presets.
I propose that the user has a rack of specific presets, looking very like the one in my image , but that the rack is optimised for live use. There needs to be a facility to step through the racks easily, via midi and midi-program change, there needs to be good visibility.
here is a rough idea. And this is the size I would prefer it too!
in this image - the orange chain is selected and active, the others are de-selected and inactive and consuming no CPU.
right, I better get back to work now!
here is the current situation :
I have a Live set, where I play 'keyboards' over the top.
For each song in the set I have a 'preset', each preset is a multi-chain.
here is one of my "presets"
there are about 7 more of those, similar but different. One for each 'song' I play. This is the current situation and I currently attempt to 'change presets' like this:
the on/off' of each 'preset' (sub-rack) is currently mapped to a macro, the macro will de-activate each 'preset' in sequence. This is my method of turning off racks that I don't currently need.
I can;t use chain-select on the main rack, because each of the sub-racks (the presets) will remain actively consuming CPU. This is why I map the on/off switches to de-activate the dis-used presets.
----
the problem
using a macro as a preset select is a lot less useful than the traditional preset selection method for synths. The traditional method can incrementing through a sequence of presets. In a live setting it is good if the presets mirror the set list, the performer usually moves to the next song 'preset' by pressing "up" or may have the preset change pre-programmed into the sequence by using midi program change messages.
A second benefit of the traditional preset system is the ability to see the name of the preset - ("tiny bells" or "Hideous Mighty Klang!" ) to help the performer avoid making the wrong noise.
Currently we can't increment through a set of 'presets' without weird hackery, and without any visual feedback we can;t really see what we have selected.
--------
The Suggestion
The requirements are -
- to select one preset from a small bunch
- seeing the name of the selected preset
- having a small memory and CPU overhead
I suggest that a rack of sub-rack 'presets' needs a dedicated facility to select and de-activate presets.
I propose that the user has a rack of specific presets, looking very like the one in my image , but that the rack is optimised for live use. There needs to be a facility to step through the racks easily, via midi and midi-program change, there needs to be good visibility.
here is a rough idea. And this is the size I would prefer it too!
in this image - the orange chain is selected and active, the others are de-selected and inactive and consuming no CPU.
right, I better get back to work now!
+1
I just came to the wishlist forum to either search for or start another "proper program changes" type thread - in relation to this thread:
http://www.ableton.com/forum/viewtopic. ... highlight=
Since I upgradeed Reaktor I've been painfully reminded just how desperately lacking this is - hotswapping is not convenient at all really - I want to use my Program up/down or number buttons on my MIDI keyboard
I just came to the wishlist forum to either search for or start another "proper program changes" type thread - in relation to this thread:
http://www.ableton.com/forum/viewtopic. ... highlight=
Since I upgradeed Reaktor I've been painfully reminded just how desperately lacking this is - hotswapping is not convenient at all really - I want to use my Program up/down or number buttons on my MIDI keyboard
yes, there are some weird workarounds but all have serious drawbacks.
I was working with the on/off method for a while but was getting clicks when the signal path is re-calculated.
I'm currently going for a chain-select solution, with greatly slimmed down racks to try and get under the CPU ceiling.
I am selecting the active chainby a Clip with macro automation on the relevant track. The problem is that I can't use 'arm' anymore to select tracks - because I will record into the clip with the macro automation in it and it comes back around at me. Not what I want. I need 'arm' because it is visible on my hardware controller as a nice red LED "you are about to play this", without arm I am literally in the dark.
So I'm looking at ditching that method now too, I'm running out of ideas.
I was working with the on/off method for a while but was getting clicks when the signal path is re-calculated.
I'm currently going for a chain-select solution, with greatly slimmed down racks to try and get under the CPU ceiling.
I am selecting the active chainby a Clip with macro automation on the relevant track. The problem is that I can't use 'arm' anymore to select tracks - because I will record into the clip with the macro automation in it and it comes back around at me. Not what I want. I need 'arm' because it is visible on my hardware controller as a nice red LED "you are about to play this", without arm I am literally in the dark.
So I'm looking at ditching that method now too, I'm running out of ideas.
-
Soupsounds
- Posts: 29
- Joined: Sat Jul 21, 2007 12:21 pm
- Contact:
Using racks as presets
i would like to add my support for ehansed Midi control of racks.
1. If one chain (or embeded rack) in a rack is selected all the other ones in the rack should be disabled to avoid CPU overload. This should be indicated by a greying out of the chain.
2. If any Chain / Rack is disabled any midi control data sent to it should not change the parameters. This is because you may have many racks with similar effects and 1 midi controller - Within a live set you don't want want to alter another deactivated preset while you are using another.
3. When you Chance the chain number in a Rack the Chain with all its plugins should be shown - whatever the configuration of the Rack display - At present this only happens when you have all the Macro parameters on display.
4. All Midi assignments should be saved with the Rack data.
If these four things were to happen the Racks would provide an excellent way of dealing with presets for live preformance.
I have used a complex working around for the muting chains / cpu issue with Bome Translator - But that has its limitations
All the best
Richard
1. If one chain (or embeded rack) in a rack is selected all the other ones in the rack should be disabled to avoid CPU overload. This should be indicated by a greying out of the chain.
2. If any Chain / Rack is disabled any midi control data sent to it should not change the parameters. This is because you may have many racks with similar effects and 1 midi controller - Within a live set you don't want want to alter another deactivated preset while you are using another.
3. When you Chance the chain number in a Rack the Chain with all its plugins should be shown - whatever the configuration of the Rack display - At present this only happens when you have all the Macro parameters on display.
4. All Midi assignments should be saved with the Rack data.
If these four things were to happen the Racks would provide an excellent way of dealing with presets for live preformance.
I have used a complex working around for the muting chains / cpu issue with Bome Translator - But that has its limitations
All the best
Richard
angstroms solution is an excellent idea.
to simply place rack presets into a folder for a performance and be able to select or switch presets easily would be fantastic. i've had to incorporate reasons combinator into live sets because it allows me to do just that. it'd be great to have this option in live
to simply place rack presets into a folder for a performance and be able to select or switch presets easily would be fantastic. i've had to incorporate reasons combinator into live sets because it allows me to do just that. it'd be great to have this option in live
-
friend_kami
- Posts: 2255
- Joined: Mon May 29, 2006 10:10 pm
Re: change Rack Preset
+1 (in fact +3 as my bandmembers would very much appreciate this feature too!)
CPU usage is a real issue especially if you're trying to use Live "live"!
CPU usage is a real issue especially if you're trying to use Live "live"!
Re: change Rack Preset
+1 Use programe change in ableton rack could be realy interesting for Live situation ... and for CPU used.
