> From: Werner Schweer <ws@...>
> yes, this is correct. For most continuous controllers it makes no
> to associate them with tracks. If you have two tracks routed to the
> midi port/channel you cannot put controller events of the same type
> tracks and expect sane results. This was possible in old MusE.
> Parts can overlap (not recommended) and this produces unwanted
> Controllers events do not move when you move parts.
> There are controllers (example sustain) you want to move too when
Personally I think it would be very confusing if this wouldn't
possible. For me, the timing of controllers are very dependent of the
notes. The way you speak of it makes it sound to me as it might be a
feature also, for some controllers (I can't think of a situation
myself, but that's me).
> I don't know how to handle this GUI wise (Maybe there should be an
> controller type: bound to part / midi port+channel).
Sounds good, if it's set to sane default-values (whatever that means).
Personally, I think it should be mapped to part as default. If not just
to avoid confusing current users with new unexpected behaviour.
> Main reason for this change was to unify controller behaviour for
midi & audio
One more question:
As of now, the drum-editor can output things on other ports than the
one for the track. Do you expect problems with the new controller-deal
w respect to that?
Get latest updates about Open Source Projects, Conferences and News.