how to set the parameters when switching to next song

[chrom]

hi together,

within a complete gig when you only lay down the stuff of the songs in the session-view & nothing into the arrangement & then manually change parameters (sends & individual fx-parameters) within one song, how can you set the many parameters correct for the next song?

thank you

[Dragonbreath]

dummy clips and clip envellopes

[kanuck]

and hot swapping.. although dummy clips/envelopes will be more instant I prefer to use hot swapping.. keeps things cleaner.

[chrom]

as an explanation a simple example what i want to do.
a track-send-parameter can at the end of the first song at an arbitrary value by live adjusting. now i want to set these track-send-parameter at -6db at the beginning of the second song. (in the sum there are sends, insert-fx-parameters for 8 tracks)

clip envs make no sense when it is an live adjusted parameter, because clip envs are only relative values which depends on the absolute value (the arbitrary value at the first song's end ). & the parameter is not set once to an exact value, but only holds the relative value until the clip with the clip env runs. so further live adjusting of the parameter isn't useful doable.
or am i wrong?


isn't there any way to initially set absolute values or presets automatically within audio-clips?
but only (!) when starting the clip (= only at the begin of the first run & not every run when looping)


in my opinion there would be a need of absolute parameter-values in a clip (in session-view) like the combination of clip & automations in the arrangement-view. these values then would / should be overwritten by manually adjustments like in the arrangement-view.
or something like a clip-parameter clip-env-mode which you can set to "relative" or "absolute".


@ topic "hotswapping"
but hotswapping means that you manually have to hotswap every device (in my example for 8 tracks).
there is no automatically hotswapping / preset-load in a clip, or?

[Hermanus]

You could use Group devices and chain + chain selector mapped to a macro knob.
The overall idea is to have one chain/one device active at a time.

You can even avoid the macro knob mapping by editing he chain selector dirctly within the clip enveloppe.

The only important thing is to be sure devices on inactive chains are disabled, that's where I think you'll need to map the chain selector to a macro knob.
This way you'll be able to map the on/off button for devices and set it through the macro panel.
You can seriously have plenty of instruments within a single track.
Having only one active instrument for avoiding cpu load spikes.
If you want further details, tell me

cheers

EDIT: one last thing I would want to add;

I ALWAYS use macro knobs the way you can edit enveloppe clip window.
This means max value [127] represents my zero value for such parameter.
The 8 knobs are set by default at 127 for enveloppe editing purpose
This can help for clip envelope editing and session playing.
That's kind of making half the job done in arrangement view.
my two cents

Last one: use unlooped envelope for what you want, it "fades" your parameter once for all.
If you set it sliding from 127 to zero, ending the loop marker [<] just after the zero value, it will slide once and your clip is good to go with it at zero forever till you launch next clip.
All the magic is there man

[kanuck]

also, do you happen to have m4l? kapture would be perfect for the job.

[Muzik 4 Machines]

another way would be to MIDI map a button or knob on a controller to all the parameters that need zeroing with a value range of zero to zero, so when you press the button, whatever state the controls are after the song, the button press will bring them all to 0

[chrom]

thank you all for your answers

@Hermanus
that's really interesting to "chain-route" a track individual for every song

i think, clip-envs are not useful in combination with live-adjusting via knobs like i want.
for e.g. if a value is faded to 0 (or better named 0% of the current absolute value) by clip-env you can turn a knob like you want it stays on 0%. so it is not set to a default value at the begin of the new song to start a new manually live knob-automation.


@ kanuck
no, i don't have it & also not max


@Muzik 4 Machines
a great idea!

my first idea now was to take an individual button for every song, so you can press button x for the song x's initial setting.

!!! BUT unfortunately you cannot map several midi-cc to one parameter.
so also in conclusion you cannot map initial values of parameters to a button when you also want these parameters manually automate by a midi-cc-knob (you can only either map a parameter to the button or the knob)

or am i wrong?


i tried it with my apc 40. & i find out that you can map an apc-predefined parameter also to a midi-cc without destroying the apc-predefined-controlling (e.g. the send a to c stay apc-predefined while using a midi-cc-button for initial-status of the send-parameters )
so i will decide to one common all-song-initial-setting and map it to the button

[Dragonbreath]

if you have an ipad or iphone kapture pad would exactly what you need