Hi Mike :) > 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.
:( I hope it was an accident, e.g. the jitter was less by accident or it was an effect of perception. > 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. Oops, a misunderstanding. But it's curios, because the plugins are in time with less jitter while the non-plugins for Rosegarden aren't in time, because of to much jitter. Ghostess might adapt the plugins to the other synth to equal jitter, but that won't solve the sync to audio tracks and even if the jitter is the same for all instruments, that won't be a help. If I'm using only virtual synth as non-plugins, e.g. QSynth, while the latency is ex ca. 8ms, it's not only a fix latency, but the jitter is increasing and it's impossible to groove. If I will try ghostess or not, it seems to be, that I have to hold latency under 8ms and than there isn't the need for ghostess. > Run your plugins in ghostess, route everything in JACK, and this > problem will go away. At least that was my experience. For me this sounds not plausible for my trouble, but I'll try ghostess if I run into this trouble again. > 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. > I don't think it's Rosegarden. And not everyone must have this problem, because it might has to do with the hardware, not the soundcard, but maybe the motherboard. > 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). The buffer is set to 128 :S. > 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. !!! The MIDI device is fine. Open QJackCtl and click the "Connect" button. There are 3 tabs, for newer versions of QJackCtl, they are called "Audio", "MIDI" and "ALSA". Rosegarden e.g. only appears in the tab "Audio" and for MIDI in the tab "ALSA", Rosegarden is using ALSA for MIDI and not Jack, but QJackCtl handles ALSA MIDI. Are you still using 64 Studio 1.0? What DE/WM are you using? With 64 Studio I'm using KDE 3.5.9/KWin and with Suse I'm using KDE 4.0.4 at the moment. I'll try Ion again if I have to increase the Latency and if then the jitter also will increase again. Thank you. I would try to make music yesterday in the night, but after eating I get ill. I hope I will be able to make music today. I fear that if Linux will be fine, my instruments will get problems. There is already one problem, the battery of a RAM cartridge for my DX7 seems to be empty and that might be the preadvice that there will be some more troubles simular to this one. I was a musician and av engineer a long time ago, that's why my equipment is old. I'm out of work for a long time, that's why it's not so easy to get new or repair old hardware. But I'm in cheerful spirits :). Greetz, Ralf
signature.asc
Description: OpenPGP digital signature
_______________________________________________ 64studio-users mailing list [email protected] http://lists.64studio.com/mailman/listinfo/64studio-users
