> > The first MIDI track had it's output to "MIDI external device 2" and now > it's changed to "MIDI output system device", that's better.
In case it's not clear (and it's not), these are just names. The key point is to make sure you are pointing to the right devices. Feel free to change the names of those devices in Rosegarden and save yourself a template. So far it seems to be solved, but I've to say it's still to hear that > it's not 100% fixed, anyway, playing two kicks in unison the "attack > click sound" of the kicks is one phased click and no longer two single > clicks. It's not 100% because the phasing isn't the same for each note, > but for a good groove I think this sync is good enough. Still it might > only be pseudo-solved because I don't know if it will be possible to > hold a latency of 5.8ms, while producing a song and I didn't test until > now what will happen if I try to include external equipment like the > Alesis D4, Oberheim Matrix-1000 etc. and also I got unspecified ALSA > errors while doing the tests. This is what I was telling you that I fixed. Don't run your plugins in Rosegarden or this will happen. Run your plugins in ghostess, route everything in JACK, and this problem will go away. At least that was my experience. I don't know what the culprit is with the "flamming" and I'd hestitate to point at Rosegarden because it's such a simple problem we are having (in that if we're having it like we are, *everyone* would be having it, and complaining!). I just know that the above solution solved it for me. Once you start ghostess, assign it as a MIDI device in Rosegarden. In JACK, under the MIDI tab (I have no idea what an ALSA tab is), you should point the Rosegarden ghostess device to the ghostess input. And that's it. If you aren't feeling like your timing isn't just perfect, then something is wrong. Don't try to test or use your ears to see if it is "good enough". At least with RME 96/52, you can set your buffers to 128 and the system won't skip a beat (assuming you have a decent system). QJackCtl handles all my audio and MIDI connections. For audio I'm using > the audio tab, but for MIDI not the MIDI tab, but the ALSA tab. As far > as I've understood or misunderstood this, the audio and MIDI tab is for > jackd clients and the ALSA tab for ALSA clients, so MIDI is handled by > QJackCtl but not by "JACK". QJackCtl's ALSA tab seems to handle ALSA > clients. Does this mean your midi drivers are not compatible with JACK? In that case, get a new midi device! Edirol or something. For my small production studio (mainly soft synths), I've been using an E-MU Xmidi 2x2 with great success and I don't even have to install any drivers, even with 64Studio 1.0: http://www.emu.com/products/product.asp?category=610&subcategory=611&product=15187 PS: OT: Is SWISSONIC a brand or a no-name brand? I can't find a homepage > of SWISSONIC. It's possible SWISSONIC is out of business. Like I said, they are a boutique brand. There speciality is not MIDI, but digital/analog conversion. Cheers, mb
_______________________________________________ 64studio-users mailing list [email protected] http://lists.64studio.com/mailman/listinfo/64studio-users
