Re: [fluid-dev] Re: CoreMIDI driver changes

2009-01-28 Thread Josh Green
Great to hear. Thanks as always for your testing efforts. Cheers! Josh On Wed, 2009-01-28 at 09:16 -0500, Ebrahim Mayat wrote: > Hello > > Following up from yesterday, I just tried the new enhanced CoreMIDI > feature with a dual port MIDI interface and sure enough I can trigger > sa

[fluid-dev] Re: CoreMIDI driver changes

2009-01-28 Thread Ebrahim Mayat
Hello Following up from yesterday, I just tried the new enhanced CoreMIDI feature with a dual port MIDI interface and sure enough I can trigger samples of two different soundfonts from the two MIDI ports. Also worth noting, is that I could also use the CoreMIDI driver in SWAMI after selec

[fluid-dev] Re: CoreMIDI driver changes

2009-01-27 Thread Josh Green
On Tue, 2009-01-27 at 21:18 +0100, Pedro Lopez-Cabanillas wrote: > > Hello Pedro > > > > I am unable to add any feedback on the ticket referred to above. > > Trac requires to log in with your user/password to edit tickets. If you > provided it, then there is a problem with the site. Josh, can you

[fluid-dev] Re: CoreMIDI driver changes

2009-01-27 Thread Ebrahim Mayat
On Jan 27, 2009, at 3:18 PM, Pedro Lopez-Cabanillas wrote: Not sure what this means. QSynth is not yet ready to understand the options for the new coremidi driver. It knows the Jack audio driver, though. Jack requires a different client name for each instance, QSynth being aware of this and

[fluid-dev] Re: CoreMIDI driver changes

2009-01-27 Thread Pedro Lopez-Cabanillas
Ebrahim Mayat wrote: > On Jan 26, 2009, at 4:34 PM, Pedro Lopez-Cabanillas wrote: > > Hi, > > > > I've added two settings to the CoreMIDI driver (SVN revision 145) as > > it was > > proposed: > > > > * "midi.coremidi.id" setting adds the provided identifier to the > > Client Name. > > If not set, t