From: Tim E. Real <termtech@ro...> - 2012-10-14 08:12:01
Brainstorming tonight I thought:
We talked before about the space available
in the track list and how to display more info
in as little space as possible and I mentioned
how muse_evolution shows all info in one
expandable track name column, and as you
expand the track more info is shown.
But I mentioned this would need a redesign
of the track list and, well, do we really want
to rid ourselves of our multiple columns?
I rather like our multi column thang.
So I've come up with an idea to show everything
in our multi-column track list with relatively
And BONUS: Remember when I said the only
thing holding me back from allowing multiple
Midi Track output ports + channels was that I
couldn't figure out a way to display all of this
info without removing our single port and
channel column so we decided to keep it as is?
Trees. Mmm. Trees. Trees good.
Let's put trees into the port column!
You know when you left click on a midi track's port
column and that menu pops up showing the available
ports and unused and empty ports and so on?
Let's put *THAT* permanently in the port column,
arranged as a tree, fully expandable and so on...
I mean holy cow look at all that wasted space when
you expand a track vertically, eh ! Let's use it - NOW.
Now, here's the second part of the deal: Channels.
We keep our channel column, and we show
16 tiny miniature LEDs horizontally - similar to
but smaller than my MIDI router popup.
(Port names can be long, so we don't want to attempt
to put the LEDs in with the port name column because the
user would have to expand the column a lot to see the LEDs.)
I mean look at that channel column: I bet we could
fit 16 of my reasonably small sized LED-Buttons
on there, even if it has to expand horizontally a bit.
There shall be one row of LEDs for each port currently
*showing* in the port tree in the port column.
The more you expand a track vertically, the more of
the "port/channel tree" it can show you.
Of course we give it all manner of bells and whistles -
expand all, auto expand, auto retract to last track height,
yeah that kind of stuff is tough but it will be killer trust me.
So again, the port and channel columns together become
something resembling my popup MIDI router, except
in a tree form.
Now, here's the third part of the deal, and we can do this
*now* without me adding multiple out port + channels:
Using the technique I described above, we add 2 more
columns: "Input ports" and "input channels".
Now here's the fourth part of the deal: Audio tracks.
Using the techniques above, we populate the unused
port column (again wasted space!) with the Jack
output routes, or even routes to other tracks I suppose.
And we populate what /would/ be the empty new
"input ports" column with input Jack routes or even
routes from other tracks.
These would simply be trees in the ports columns,
no channels LEDs required as with midi tracks.
Et voila: We then have all midi input and output ports and
channels, and all audio track input and output routes,
shown in full view in the track list as expandable,
Or something like that. I'll probably wake up tomorrow
and go "what was I thinking", but I believe we could move
forward and make connection visuals substantially better.
I put aside Mr. Knob-Meter for moment.
Dennis: Working on the initializations thing last two nights.
Good progress, I think you'll like it.
I can see where current code may mess up your
setup 'cause although it's smart enough to send only on
ports used in the song, it sends out on all their channels !
New code does not touch any port AND channel not used
in song. It's reeeal quiet now - useless traffic is super low.
Options for sending now, too. Hopefully soon my friends,
hope this stuff works out, tricky...
Soon MusE is gonna be pretty cool I think.
I hope we can make it to Qt5 - that is if Nokia doesn't drop it.
Robert: Song type is gone now. Me thinks warrants MusE 2.2 ?
Cheers, good weekend to all.
From: Dennis Schulmeister <muse-sequencer@wi...> - 2012-10-14 09:47:52
On Sun, 14 Oct 2012 04:11:44 -0400
"Tim E. Real" <termtech@...> wrote:
> Dennis: Working on the initializations thing last two nights.
> Good progress, I think you'll like it.
> I can see where current code may mess up your
> setup 'cause although it's smart enough to send only on
> ports used in the song, it sends out on all their channels !
> New code does not touch any port AND channel not used
> in song. It's reeeal quiet now - useless traffic is super low.
> Options for sending now, too. Hopefully soon my friends,
> hope this stuff works out, tricky...
Cheers, Tim. Great job you're doing, really.