That’s what I mean. But when muting CPU is still being used, isn’t it?
That’s why I’d like to have an on/off button for the global part so that any function is disabled, also the connection to the keyboard controller… Maybe it would be in general a good idea having a button for switching on and off layers as they wouldn’t use CPU anymore and won’t be processed then any longer…
Hi! If u use it globally, you need it anyways. If you just need it / song basis, you can even use song layer&stack. Furthermore you can automate functions for global layer&stack via midi
Export to text coming.
Ability to attach/edit a list of MIDI commands to a song part to be fired when the part is selected and before playback is started (i.e. when playback is stopped).
This would enable me to have all my outboard gear load the correct presets to start the song before I hit the play button. It would be great to verify everything is automatically ready to go before starting, and there are some songs where I would riff with some ambient swells even before pressing play.
Also: if there could be an optional way to ensure playback starts at the top of the part. rather than the last playhead position I would make use of that too. Similar to toggling cycle on/off. It would help ensure any MIDI commands at the top of the part are not skipped by an inadvertent movement of the playhead before starting playback.
HI! you can with “Layers” ![]()
look:
ups, sorry, wrong screen, corrected ![]()
just make a “dummy” layer
What do you mean by “fired”?
When a Part is selected, everything should be ready to go. Layers send all of their values etc.
If chase events is on (preferences), and you send events from tracks at Part trigger time, those should also be primed.
And: you know about the “File/Preload” functions, right?
Use the play icon on the Part.

So the manual seems to only describe how to map incoming controllers. How do you set up outbound messaging to send a list of PC and CC’s to certain channels on a layer?
Right side of input ![]()
What does File/Preload have to do with outboard gear? Isn’t that just for pre-loading plugins?
WRT the Play icon… I guess that’s a workaround, but I was hoping I’d just be able to hit the spacebar when I was ready rather than fiddling with the mouse pointer.
just hit SPACEBAR for PLAY any prepared SONG from the start position by default ![]()
So are you saying that anything configured on this Layer interface is sent to the output the instant the part is selected (as opposed to when the part has playback started)?. If so, then I can indeed accomplish what I’m looking to do.
The specific reason that I overlooked layers is that the manual only seems describe Layers as mapping MIDI inputs to outputs as opposed to also being a potential source of its own list of pre-programmed outbound MIDI messages.
The manual says only this:
"Layers are optimized to host VST instruments, but can also be configured for two other functions:
- Host a MIDI effect.
- Pass MIDI data from the Layer’s MIDI input source to its selected MIDI output. The inputs and outputs can be hardware interfaces or virtual MIDI ports."
I’m not trying to host a VST Instrument. I’m not trying to host a MIDI effect. I’m also not trying to pass MIDI data from the Layer’s MIDI input source. My intention is literally none of the above.
I guess I was just looking for some sort of simple MIDI List Editor that doesn’t seem to exist for Layers like it does for MIDI tracks. I don’t need knobs for this, and the displayed CC labels are totally wrong for what the outboard device actually does in response to it. Is there any way to fix the labelling to match what the CC function actually controls on the targeted device?
That’s only by virtue of the fact that the playhead is at the start position by default. If the playhead is first moved by any means the spacebar will NOT take you back to the start which is specifically the corner case I was referring to in the original post.
everithing is true but there are lot’s of flexible solution in the app already.
When reading your question, my first idea was to write you this one with “layer”, just I needed to get back to a computer provide u screen rec. In this specific case you probably won’t need input for LAYER but set output to reach your external fx.
I think it does, just meight need to change preferences here maybe (“locate last start”)
So just click together what you need and enjoy ![]()
Sweet! Thank you so much for your help! I really appreciate it.
I just started trialing the software but I’ve already decided to buy it. It’s much more streamlined for my use case than Ableton so I’m very happy to have found it!
You can map Keys to Actions - I have Z as return to zero. Can be dangerous because it will also work when the transport is running.
Also, with the Layer Controller Map featuring the “Send” option, you can send any controllers when a Layer (more precicely, its Part) gets selected.
Considering that this thread has more than 500 entries now and is labeled “Feature Requests”, we would kindly ask you to create new threads, unless it is exactly that ![]()
Is there an ETA when the ability to jump transport using parts will be available? I know it has been indicated it is being worked on for a while but hasn’t happened yet. Seems like a very useful and basic needed feature to me. I would love to stop using Ableton.
It’s beeing tested already, but we can’t provide an ETA yet.
Thanks for that! I’m having an issue where the knob in the GUI doesn’t retain the specific CC value that I set when you leave the part and come back to it (if I set it to 14 it always changes to 18 when I leave the song and come back - possibly because you can’t even select 14 when turning the knob, only by typing it). The Map feature is now my workaround as it is holding the exact value I set.
