[Ardour-Dev] A couple of ideas (mostly sequencer)

Cedric Sodhi manday at gmx.net
Tue Jan 10 05:00:43 PST 2012

Hi Alexandre,

On Tue, Jan 10, 2012 at 04:48:25PM +0400, Alexandre Prokoudine wrote:
> On Tue, Jan 10, 2012 at 4:28 PM, Cedric Sodhi wrote:
> > My opinion on the WIP of sequencer: Controller data should be offered in
> > separate timeline below the piano roll, as it is standard with other
> > sequencers (RG,qTractor,LMMS, etc).
> And that stuff being a standard in free sequencers is automatically a
> good thing? Eh? :)

No, I did not say that. I'm not making such blind assumptions.
> Completely disagreed. It might work in applications where pianoroll is
> in external window, but not in Ardour.

To be shown...
> How many MIDI tracks do you think you will be able to work on
> simultaneously when each one has a controllers timeline below?
Would take a lot of space, yes. I did not go into the details.

Same argument could apply to automation tracks. Automation?!

"How many tracks do you think you will be able to work on simultaneously
when each one has a automation timeline below?"

Wait... they do! How is it solved? It can be hidden. Same would work for
controllers, too, I assume.

> That, and also the fact that you have to scroll the screen with your
> own eyes up and down all the time just to edit anything. I'd like to
> have a better use for my eyes, thank you so very much :)

Did you read the proposal completely? I did not ask for the coloring of
notes according to velocity to removed. In fact, I asked for it to be
enhanced by using H(S)V to indicate not only one but two (three) ctrl

So, saying "no" is easy. You think to offer full control over all
controllers only below is too much for your eyes? How else would you go
about it?

I would neither want to clutter the timeline (in which, I agree, is
still plenty of room and colors to be made use of) with half a dozen
controller values, either.

I think offering controller data, aligned with the notes, below the
piano roll (one controller at a time) is a fine solution.

Suggestion: Why do you not tell us what problems you have with the
approach taken in, say, qTractor and how you would solve it?

-- Cedric
> Alexandre Prokoudine
> http://libregraphicsworld.org
> _______________________________________________
> ardour-dev mailing list
> ardour-dev at lists.ardour.org
> http://lists.ardour.org/listinfo.cgi/ardour-dev-ardour.org

More information about the Ardour-Dev mailing list