I see you are up and running. I'd like to do a little more digging
into this in case there is a legitimate bug that we can fix. Or even
just something someone else might run into in the future in terms of
system setup.
In order of "easiest for you":
1. Can you send me the message log from QJackCtl?
2. And a screenshot of the connections in QJackCtl.
3. Can you install a real-time kernel? Those 250Hz warnings are
worrisome. Especially if you are running at 88.2kHz. I have a page
with steps:
http://www.tedfelix.com/linux/linux-midi.html
4. Can you build and run the latest Rosegarden? It's a bit of a
complicated task and will suck up an hour or two of your time. But if
you are using Rosegarden for serious endeavors, running the latest is a
good idea. This will also let me make changes to help track down this
issue (if needed) and you can pick them up immediately. Absolutely
understand if you don't want to pursue this. It is a commitment. And
it could lead to some instability for you. (You can always fall back to
running your favorite stable version.)
https://www.rosegardenmusic.com/wiki/dev:building_rosegarden_from_source
Ted.
On 7/15/23 9:42 PM, r...@hydrophones.com wrote:
Hi Ted,
As requested:
Rosegarden 20.06 - AlsaDriver [ALSA library version 1.2.2, module version
5.11.0-7620-generic, kernel version 5.11.0-7620-generic]
===============================================================
JackDriver::initialise() begin...
JACK sample rate = 88200Hz, buffer size = 2048
Creating audio file thread...
Found 1 JACK physical outputs
connecting from "rosegarden:master out L" to "a2j:Midi Through [14]
(playback): Midi Through Port-0"
WARNING: cannot connect to JACK output port
ALSA Client information:
14,0 - (Midi Through, Midi Through Port-0) (DUPLEX) [ctype
2, ptype
655362, cap 99]
128,0 - (FLUID Synth (47987), Synth input port (47987:0)) (WRITE
ONLY) [ctype 1, ptype 1310726, cap 66]
Using low-resolution system timer, sending a warning
Current timer set to "system timer"
WARNING: using system timer with only 250Hz resolution!
AlsaDriver::initialiseMidi - initialised MIDI subsystem
AlsaDriver::setPlausibleConnection: connection like "" requested for device 0
AlsaDriver::setPlausibleConnection: fuzzy match 128:0 Synth input port
(47987:0) (write) available with fitness 1
AlsaDriver::setPlausibleConnection: connection like "" requested for device 1
AlsaDriver::setPlausibleConnection: nothing suitable available
ALSA Client information:
14,0 - (Midi Through, Midi Through Port-0) (DUPLEX) [ctype
2, ptype
655362, cap 99]
128,0 - (FLUID Synth (47987), Synth input port (47987:0)) (WRITE
ONLY) [ctype 1, ptype 1310726, cap 66]
AlsaDriver::setPlausibleConnection: connection like "20:0 UMC1820 MIDI 1
(duplex)" requested for device 0
AlsaDriver::setPlausibleConnection: nothing suitable available
AlsaDriver::setPlausibleConnection: connection like "20:0 UMC1820 MIDI 1
(duplex)" requested for device 1
AlsaDriver::setPlausibleConnection: nothing suitable available
ALSA Client information:
14,0 - (Midi Through, Midi Through Port-0) (DUPLEX) [ctype
2, ptype
655362, cap 99]
128,0 - (FLUID Synth (47987), Synth input port (47987:0)) (WRITE
ONLY) [ctype 1, ptype 1310726, cap 66]
AlsaDriver::setPlausibleConnection: connection like "" requested for device 0
AlsaDriver::setPlausibleConnection: fuzzy match 128:0 Synth input port
(47987:0) (write) available with fitness 1
AlsaDriver::setPlausibleConnection: connection like "" requested for device 1
AlsaDriver::setPlausibleConnection: nothing suitable available
ALSA Client information:
14,0 - (Midi Through, Midi Through Port-0) (DUPLEX) [ctype
2, ptype
655362, cap 99]
128,0 - (FLUID Synth (47987), Synth input port (47987:0)) (WRITE
ONLY) [ctype 1, ptype 1310726, cap 66]
Using low-resolution system timer, sending a warning
Current timer set to "system timer"
WARNING: using system timer with only 250Hz resolution!
Using low-resolution system timer, sending a warning
Current timer set to "system timer"
WARNING: using system timer with only 250Hz resolution!
Using low-resolution system timer, sending a warning
Current timer set to "system timer"
WARNING: using system timer with only 250Hz resolution!
For troubleshooting JACK issues, there is a log viewer in
preferences. Go to Edit > Preferences... > Details...
That will display the log viewer. See if there's anything
interesting there. If needed, copy and paste and email it to the list
and we'll look further.
Ted.
On 7/15/23 12:25 AM, r...@hydrophones.com wrote:
Hi guys,
I'm getting the following error message when I try to activate recording
on an audio track:
"audio subsystem not available - can't record audio"
in a window that has the header:
Rosegarden (as superuser)
This is happening with Rosegarden Version 23.06 "Flutterbye"
Build Key 13280f9033
Qt Version 5.15.9
Running under Pop!_OS 20.10 Linux with
QjackCtl Version 0.5.0
Qsynth Version 0.6.3
Using FluidSynth 2.1.3
QjackCtl and Qsynth are working and sound fine. Qsynth's audio outputs
show up on QjackCtl's patchbay but no audio inputs to Rosegarden appear.
All the MIDI ins and outs seem to be working fine.
The "self-recording" feature of Rosegarden used to work. Is this a bug?
Is there a workaround? I used to use it to record (with perfect
synchronization) track by track, and sometimes double track, various
patches and synths.
Thanks for all you do, and in advance,
r...@hydrophones.com
_______________________________________________
Rosegarden-user mailing list
Rosegarden-user@lists.sourceforge.net - use the link below to
unsubscribe
https://lists.sourceforge.net/lists/listinfo/rosegarden-user
_______________________________________________
Rosegarden-user mailing list
Rosegarden-user@lists.sourceforge.net - use the link below to unsubscribe
https://lists.sourceforge.net/lists/listinfo/rosegarden-user
_______________________________________________
Rosegarden-user mailing list
Rosegarden-user@lists.sourceforge.net - use the link below to unsubscribe
https://lists.sourceforge.net/lists/listinfo/rosegarden-user
