Often when jackd disconnected while using Rosegarden, the error message
advices to close some applications, even if there were no other
applications running, but QJackCtl and Rosegarden.

Reaper was fine with 128 frames, 8 periods at 44100Hz, excepted the
timing, that wasn't fine. Maybe I can't remember crashes for Reaper,
there might be also often such crashes, but not all the time, like it is
at the moment.

Jitter and sync for Linux applications were fine when using 128 frames,
2 periods at 44100Hz, while limits.conf also was changed, but the
problem are the crashes.

The actual limits.conf is the default limits.conf and I'll keep it.

Oops! I opened and closed QJackCtl some times, while writing, there are
no audio applications opened. When opening QJackCtl the last time,
"07:39:01.254 JACK was started with PID=6180.

07:39:01.459 Could not connect to JACK server as client. - Overall
operation failed. - Unable to connect to server."
The sound device for Jack is the correct one. At the moment I'm not
running the default 64 Studio, but this error appears often for all my
Linux.


This kinds of crash I never got with my old hardware, 1024 frames, 2
periods, 441000Hz, there I got problems with less resources.


I'll try MusE without fluidsynth plugins, but QSynth instead and will
set jackd values extreme high, 512 frames, 4 periods for 48000Hz. I'll
reduce the ticks for MusE from 1024 to less than 400 and will see what
will happen.


Attachment: signature.asc
Description: OpenPGP digital signature

_______________________________________________
64studio-users mailing list
[email protected]
http://lists.64studio.com/mailman/listinfo/64studio-users

Reply via email to