From: Joachim S. <js...@du...> - 2005-02-16 23:59:26
|
On Thursday 10 February 2005 21:20, Christoph Eckert wrote: > Hi, > > > there are three objects involved in connecting midi > > devices: > > > > =A0 =A0 =A0 midi track - midi port - midi device > > > > The "midi port" introduces an extra layer of indirection > > (programmers love this) > > which obviously causes some confusion. > > The midi track is connected to the "midi port". To hear > > some sound. the "midi port" > > muse be connected to a "midi device". > > At least for the user. Perhaps a first step could be to > clearly divide them into Alsa MIDI devices and MusE MIDI > ports. > > Furthermore, it's currently difficult to undestand how MIDI > inputs are connected to tracks for recording and what are > outputs. > > > Without the "midi port" layer we have to connect a midi > > track directly to a midi > > device. Imagin you have 10 tracks connected to a specific > > device and you want to > > use a different output device. You have to reroute all 10 > > tracks to ouput to a different device. With MusE you only > > have to change the output routing of a midi port. > > Yeah, that's actually cool. > > > Midi devices are a list of available ALSA midi devices. All > > external synthesizer > > appear in this list if they have midi ports. Midi devices > > ara remembered by name. > > If an external software synthesizer does not run when you > > start MusE, the "midi port" - "midi device" connection will > > not be made. "Internal Synthesizers" are a list of > > available synthesizer plugins wether MusE > > MESS, VST or (in current cvs head) DSSI. > > > > To add to the confusion: > > What do you think about a new way to handle midi > > connections: > > > > =A0 =A0 =A0 - the user can dynamically create any number of midi > > output ports; this midi output ports are externally visible > > alsa ports and can be routed by extern tools like jackctrl > > =A0 =A0 =A0 - midi tracks are internally routed to this midi > > ports (same as now) - alsa midi input ports can be routed > > straight to a midi track - midi output ports appear as a > > mixer strip (which gives access to "master volume" > > controller) > > =A0 =A0 =A0 - the "oR" button in the midi output port mixer strip > > allows for routing to ALSA midi devices > > Hm, I feel I have to sit down a bit longer to explore this > issue ;-) . > > > The handling would be similar to the handling of audio > > tracks. The midi port connection dialog could be removed. > > Whats missing is the assignment of "instruments". Maybe > > instruments should be assigned to midi tracks which would > > allow > > for different instruments for one midi port. > > Do you mean the IDF files? > > If so, it would be cool to assign one not simply to a > track/device, but to assign them to an Alsa device (may it be > hardware or software synth) *and* a MIDI channel seperately. > This means, in the worst case, I can assign 16 different IDFs > to one device. Why? Because I excessively using MIDI through > to route MIDI from one hardware synth to an other. Yeah, I > shouldn't do so to prevent timing issues, but hardware MIDI > routers/cards are very expensive. An Edirol UM-880 is about > 370EUR :( . Hey Christoph, then simply put 3 soundcads into your pc. I've had some laying arround. I'v= e=20 now a sblive and a onboard midi connection. If needed i can plug in one mor= e=20 card. And you get a working midi hub for 80 euro and less. Greets, Joachim > > > Best regards > > > ce > > > ------------------------------------------------------- > SF email is sponsored by - The IT Product Guide > Read honest & candid reviews on hundreds of IT Products from real users. > Discover which products truly live up to the hype. Start reading now. > http://ads.osdn.com/?ad_ide95&alloc_id=14396&op=3DClick > _______________________________________________ > Lmuse-user mailing list > Lmu...@li... > https://lists.sourceforge.net/lists/listinfo/lmuse-user |