BUG - removing a midi controller doesn;t work

[davidweese]

I assigned gain to a knob on my XBoard. I then reopen assign midi controller and choose none for source. The knob still controls the gain.

Also when recording automation of the gain using this controller, no automation is recorded. Not implemented yet? I noticed on the editor page there's no option to do Muzys-type automation curves yet or to choose another control than velocity...

OK UPDATE : if I do not merge the new automation recording, and instead name the automation activity as a new clip, it IS recorded. That's good, but I assumed a merge would...er....merge the clips and the automation curve would be available from the midi edit (TAB) view. I see the routing widow shows an icon to represent the mixer strip, so I gather that keeping automation curves as a separate clip is intentional. I'll buy that.

[muzycian]

I assigned gain to a knob on my XBoard. I then reopen assign midi controller and choose none for source. The knob still controls the gain.

This was not yet a supported case.

Finetuned in the coming release version.

Also when recording automation of the gain using this controller, no automation is recorded. Not implemented yet? I noticed on the editor page there's no option to do Muzys-type automation curves yet or to choose another control than velocity...

OK UPDATE : if I do not merge the new automation recording, and instead name the automation activity as a new clip, it IS recorded. That's good, but I assumed a merge would...er....merge the clips and the automation curve would be available from the midi edit (TAB) view. I see the routing widow shows an icon to represent the mixer strip, so I gather that keeping automation curves as a separate clip is intentional. I'll buy that.

Automation events must go to their proper target.

So currently it is not possible to merge automation to target A with automation to target B all into 1 sequence part.

Or better said: technically you can merge them, but it won't work as you expect, because a part can only have a single target, and thus all automation events in that part will go to that single target.

Note that "Event Targets" functionality already is on the whishlist

This means that a sequence part could be set to "Event Targets", and then every single event in that sequence can have its own target!

This way it will be possible to merge automation recordings to multiple targets into a single sequence.

Not yet for version 1.0 though.

[pljones]

<questions-regarding-forward-looking-statements>
If we have merge, then please let us have demerge-by-target, Jo.
And will this also mean multi-timbral sequences (i.e. channel at event level) - or does channel stay at part (not sequence) level?
</questions-regarding-forward-looking-statements>

[muzycian]

<questions-regarding-forward-looking-statements>
If we have merge, then please let us have demerge-by-target, Jo.

Added on the whishlist

Functionality also needed for auto expanding type 0 midi files.

And will this also mean multi-timbral sequences (i.e. channel at event level) - or does channel stay at part (not sequence) level?
</questions-regarding-forward-looking-statements>

Yes, if you set a part to "Event Target", then the channel will be on event level too then

Note that we're talking future here.