Re: [Rosegarden-user] Cannot connect to jack

[Ted Felix]

On 5/24/20 12:46 PM, stefano franchi wrote:
some progress: the errors above were due to pulseaudio being active and 
messing with jack. Once I cut pulseaudio off the loop with a direct 
ALSA--> jackd connection (done with the cadence jack manager), most of 
the errors disappeared.


  Sounds like you are making good progress.  I recommend going through 
my Linux MIDI Guide.  It's designed to help you understand and 
troubleshoot JACK and ALSA and MIDI.  Should save you a lot of time in 
the long run.


  http://www.tedfelix.com/linux/linux-midi.html

Ted.


___
Rosegarden-user mailing list
Rosegarden-user@lists.sourceforge.net - use the link below to unsubscribe
https://lists.sourceforge.net/lists/listinfo/rosegarden-user

Re: [Rosegarden-user] Cannot connect to jack

[stefano franchi]

On Sun, May 24, 2020 at 11:25 AM stefano franchi 
wrote:

> I seem to be unable to get Rosegarden to connect to jack.
> I am using (well, trying to use) Rosegarden on an Archlinux setup, with
> jack2 and qjackctl:
>
> Name: rosegarden   Version : 19.12-1
> Name: jack2   Version : 1.9.14-
> Name: qjackctlVersion : 0.6.2-1
>
> qjackctl tells me that jack is running, and if i start rosegarden, I can
> see its icon pop up in qjackctl graph.
> However, I don't get any sound in rosegarden itself, not can I import any
> audio track into it. The File>Manage Audio Files menu item is greyed out.
>
> When Rosegarden starts, I see the following audio-related error messages
> in the console:
>
> [JackDriver] initialise() - cannot connect to JACK output port
> [AlsaDriver] setCurrentTimer(): WARNING: using system timer with only  300
> Hz resolution!
> [AlsaDriver] renameDevice(): WARNING: Cannot find device  1  in port map
>
> which seem to confirm that indeed there is something wrong with the
> rg/jack connection. How do I tell rg to connect to jack's imput and output
> ports? Is it something I have to do through qjackctl?
>
> some progress: the errors above were due to pulseaudio being active and
messing with jack. Once I cut puilseaudio off the loop with a direct
ALSA--> jackd connection (done with the cadence jack manager), most of the
errors disappeared.
But one ALSA error is still there, and I think it's blocking everything. I
now see the following:

JACK server starting in realtime mode with priority 10
self-connect-mode is "Don't restrict self connect requests"
audio_reservation_init
Acquire audio card Audio0
creating alsa driver ...
hw:PCH,0|hw:PCH,0|1024|2|44100|0|0|nomon|swmeter|-|32bit
configuring for 44100Hz, period = 1024 frames (23.2 ms), buffer = 2 periods
ALSA: final selected sample format for capture: 32bit integer little-endian
ALSA: use 2 periods for capture
ALSA: final selected sample format for playback: 32bit integer little-endian
ALSA: use 2 periods for playback
[AlsaDriver] setCurrentTimer(): WARNING: using system timer with only  300
Hz resolution!
[AlsaDriver] renameDevice(): WARNING: Cannot find device  1  in port map
do_connect: could not connect to socket
connect: No such file or directory

Which seems to suggest that rg found jack but cannot somehow connect to
alsa through it?

I can't find any settings in rg itself that would affect alsa,
unfortunately.

Suggestions welcome

-- 
__
Stefano Franchi

stefano.fran...@gmail.com 
*https://www.researchgate.net/profile/Stefano_Franchi*

___
Rosegarden-user mailing list
Rosegarden-user@lists.sourceforge.net - use the link below to unsubscribe
https://lists.sourceforge.net/lists/listinfo/rosegarden-user