> Really, it seems a lot more sensible for Rosegarden to do controllers on
> some
> "conductor track" at the global level, on a per instrument basis.
> Rosegarden
> definitely gives you the rope to hang yourself with in this respect, since
> you
> won't see controllers that are in some other segme
> On Monday, November 28, 2011, Tom Breton (Tehom) wrote:
>
>> behave as expected. The biggest problem is that they can't offset from
>> the current value of a controller.
>
> The "current value" of a controller is really more complicated than it
> seems
> at a glance. I guess you could search ba
On Tue, Nov 29, 2011 at 10:45 AM, D. Michael McIntyre <
michael.mcint...@rosegardenmusic.com> wrote:
I wish I'd thought of this 10 years ago, when it would have been easy to do
> something about it.
>
Not so sure. I seem to remember it getting pretty heated about
_everything_ back then!
R
-
On Tuesday, November 29, 2011, Richard Bown wrote:
> Rosegarden has always been a compromise between a notation editor and MIDI
> editor and latterly an audio workstation too. The whole design is
> therefore a compromise and we've done nothing more or less than any other
> piece of software that
