Simultaneously record into an arrangement from session midi clips and from a midi keyboard on the same track.

[Valkon]

Dear Sirs!
Currently, when recording the contents of a midi track from session mode to arrangement mode, we cannot record the sum of data from both the keyboard (from the "In" input) and from the session clip, since when starting a clip in "Auto" mode, the input "In" is immediately disabled (the selector is forced into "Off" mode).
This creates unreasonable difficulties during live performances: we cannot by simple means modify the sound of a repeating midi clip of a session in order to rid the final recording of excessive mechanicalness by achieving diversity in individual fragments (for this, we will have to run the session clip on a separate service track and route its output to the input of the summing track)! Moreover, an unnecessary monotonously repeating service clip of the session, without our consent (even if the “Record” button is not pressed), will be recorded in the arrangement clip on the duplicate track (uselessly wasting processor power).
Questions arise: why can’t we record into the arrangement mode signals from both a midi clip and from the keyboard, simultaneously sounding on ONE track, and why do we need to ARTIFICIALLY multiply the tracks, forcing the processor to double the load and at the same time clutter the screen with unnecessary (service) ones? tracks intended for roaming only?
Who and why decided that when recording into an arrangement, from the moment the session midi clip starts to start, recording from the keyboard input should completely stop (and not be combined with signals from the clip, as simple logic dictates, since - if the performer wanted to refuse from recording from the keyboard, he would have chosen the “Off” mode in the selector)?
Don't you think it should be the other way around: live keyboard performance signals should block signals from the midi clip (since the human factor should take precedence over the machine factor) or, at a minimum, record from both signal sources simultaneously (and the user will choose which ones will they need to be blocked)?!
I already drew the attention of developers to this problem on the Centercode resource, but there was no reaction.
In my deep conviction, the action of the input selector in the "Auto" mode is devoid of logic, and should be changed to the opposite (or the "ALL" mode should be added).
I would be grateful if you share your opinion on this matter...

[chapelier fou]

I probably don’t get your post, because my answer is too simple : arm the track and enable overdub ?

[Valkon]

Thanks for your reply! You really didn't quite understand me: we are not talking about re-recording an arrangement clip, but about recording from SESSION mode to ARRANGEMENT (with additional user data overdubbing on a short looped session clip)! Yes, in this case you can PLAY both a midi clip and notes from the keyboard at the same time, but as soon as you turn on the global recording mode, midi data from the keyboard is blocked (and the session clip continues to be recorded in the arrangement). The most interesting thing is that if you additionally enable the session recording mode, then recording notes from the keyboard resumes (but the original clip of the session is also overwritten, which is unacceptable)!

[schlam]

Hello.

I sent this issue to support some years ago...
Like lots of little bugs like that, it's stilll not fixed, and surely will never be.
...I find this issue very annoying too.

[chapelier fou]

Ok, for some obscure reason I never got bothered by the issue, but you're damns right, I see how annoying it can be.

[Valkon]

Hello.

I sent this issue to support some years ago...
Like lots of little bugs like that, it's stilll not fixed, and surely will never be.
...I find this issue very annoying too.

Could you please tell me what was the response to that request? Was any justification given for the current situation?

[[jur]]

Yep, this is an (old) known issue/limitation.

[Valkon]

Yep, this is an (old) known issue/limitation.

Thanks for your reply! Please tell me what is the root of the problem? Is it possible to make a switch in the settings (in which the priority is reversed) so that users can choose the desired setting for the "Auto" selector mode?! And on whom (or on what external circumstances) does such a decision depend?

[schlam]

Sorry to dont be very nice with Ableton here but I am sure that there is no real reason for this limitation...And I am quite sure that it will be never fixed like lots of others "little" limitations/bugs

I dream of a moment where they will say. "Ok lets stop to add more new synths and more effects and more stuffs and lets fix all those littles limitations"

[chapelier fou]

Don't take it bad @schlam, but this is a typical "this should be easy to code" situation.
You have no idea what this implies in the source code, and neither do I.

[schlam]

I dont say it's easy at all. I am not a coder, I just say that it is not fixed since years like lots of other important things that have to be fixed...

[[jur]]

A bug report to Support never hurts

[schlam]

yes I know... I sent one few years ago, it was on Live 10...=)

[[jur]]

yes I know... I sent one few years ago, it was on Live 10...=)

Yeah, I remember this topic being discussed here back then.

[schlam]

Fun.
Everey one rediscovers this "limitation" (.hhhmmm this bug the same week

viewtopic.php?t=245691