Re: [Lmuse-user] MusE and ALSA ports again

[Mark K. <mar...@gm...>]

On Fri, 4 Mar 2005 16:05:37 +0100, Joachim Schiele <js...@du...> wrote:
> On Thursday 03 March 2005 22:42, Christoph Eckert wrote:
> > Hi,
> >
> >
> > some time ago, we have been discussing the MusE ports and
> > their behaviour. <SNIP>
> 
> hehe yes welcome ;-)

Joachim,
   Thanks for your explanations. They are helpful to me also.

> 
> ok here we go. if you want to set in and outs you have to do it in MusE
> because of the "inner" architecture Werner has created. It's quite clear you
> just have to get it once. Here we go:
> 
> In your picture have a look at this coordinates 618,84 and you'll find a green
> dot indicating that midi in is accepted from this device on 640,84 there is
> midi out also set, click it once and you get a midi disabled by this channel.

Great. I had this same question, and I knew about this page, but for
whatever reason I hadn't thought to handle this issue here. It makes
lots of sense now.

> And if you want to connect MusE to a midi device you have to use the MusE
> dialog rather qjackctl (which in my opinion - and as you have just prooved -
> is not clear to everybody at first). In the menu F10 you'll find a Dropdown
> or at least a menu entry named "routing" (there is also a button somewhere in
> the dialog) click this once and the routing of MusE gets opened. The MusE
> routing is basically the same as the qjackctl dialog wich slight other
> attributes:
> - it has a higher priority
> - it's not so nice (color )
> - it's not so meaningful
> - is's working (same as qjackctl)

Helpful again. Thanks.

> 
> I've talked to Werner and the final result was:
> It would be nice to use the qjackctl dialog in MusE so just copy'n'paste the
> code into MusE would be nice. On the other hand it would be nice if external
> connections could be set by both "qjackctl" and "MusE" so it would be "clear"
> for everybody.
> 
> Why do we need the dialog at all?
> We don't need it for external*** connections which are visable for every
> alsacapable program but we need it for the inner part like the routing from
> input1 to wavetrack1 and out of wavetrack1 into out1. (got it?)
> 
> *** This is a lie but it could be if someone did it.
> 
> If you got further questions. ASk.
> Joachim

Thanks. I do have one more question. How do I make my choices
permanent? It seems that every time I open Muse I have to do all of
this stuff over again and again. I only have two inputs. Christoph has
eight. Our hardware synths don't change cables day to day and neither
will our use of Muse, in general. Every time we use Muse we find
ourselves repeating this menial task. Is there not a way to make my
preferred use of my machine and hardware a default?

Thanks,
Mark