-
Notifications
You must be signed in to change notification settings - Fork 14
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Totally Unstable playback #101
Comments
Check your JACK settings. If the "Period" is large (e.g 2048, 4096, etc.)
there is a known issue with the "rtmidi" code. You can change the period in
QJackCtl. You can also view the current JACK settings (requires jackdbus):
$ jack_control dp
and look at the line "period: Frames per period (uint:set:1024:2048)" and note
that the second number is the current setting. I have it set high at present
in order to work on sticky issue #100.
If set high, try setting it to 128. It will still be slightly raggy but
generally not noticeable.
Thanks for the video, very helpful to see.
…-------- sirjohndfox 05:31 Tue 11 Oct --------
|
Further investigation leads me to believe it might be something with the realtime kernel and video drivers! bloody annoying! I wonder where to start looking... Actually can't pin it on the video driver - I don't know enough - but it seemed to stablise when i tried the vanilla kernel. The realtime kernel I'm using is NSPA's https://github.com/nine7nine/Linux-NSPA-pkgbuild |
As regards the frames, I went down from 128 to 64 no difference. |
One thing I have noted, is that a real-time kernel is not needed for JACK these
days. Still, not sure why that could cause an issue.
…-------- sirjohndfox 06:14 Tue 11 Oct --------
As regards the frames, I went down from 128 to 64 no difference.
|
I've identified some flaws in the configuration of my system overall. I'll fix them and see if the error persists. Feel free to close the issues. Sorry if it was irrelevant.
Sent with [Proton Mail](https://proton.me/) secure email.
…------- Original Message -------
On Thursday, October 13th, 2022 at 3:46 AM, C. Ahlstrom ***@***.***> wrote:
One thing I have noted, is that a real-time kernel is not needed for JACK these
days. Still, not sure why that could cause an issue.
-------- sirjohndfox 06:14 Tue 11 Oct --------
>As regards the frames, I went down from 128 to 64 no difference.
—
Reply to this email directly, [view it on GitHub](#101 (comment)), or [unsubscribe](https://github.com/notifications/unsubscribe-auth/AAWAEN5OPC52RKVYFKJC7EDWC3TN7ANCNFSM6AAAAAARCHUIIU).
You are receiving this because you authored the thread.Message ID: ***@***.***>
|
Whatever you find out, let us know here. It could be very useful to include in
the documentation. Thanks!
|
Closing. If still an issue, make a new report and make me earn my keep! |
Just compiled seq66 can't get steady playback. Not sure if it's my system, new to manjaro and might have done a dubious up-date. But it hangs often and then releases a whole bunch of notes...
Tried with yoshimi too. same thing... Is my system broken?
https://youtu.be/v6H4LGk8Kyc
The text was updated successfully, but these errors were encountered: