Re: Jack Problems

On Tue, 26 Mar 2019, [email protected] wrote:

> jackdmp comes with ABSOLUTELY NO WARRANTY
> This is free software, and you are welcome to redistribute it
> under certain conditions; see the file COPYING for details
> JACK server starting in realtime mode with priority 10
> self-connect-mode is "Don't restrict self connect requests"
> 01:44:00.249 JACK was started with PID=18192.
> audio_reservation_init
> Acquire audio card Audio1
> creating alsa driver ... hw:VSL|hw:VSL|256|2|44100|0|0|nomon|swmeter|-|32bit
> configuring for 44100Hz, period = 256 frames (5.8 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

This looks good given VSL is the interface that should be used.

> port created: Midi-Through:midi/playback_1
> port created: Midi-Through:midi/capture_1
> port created: AudioBox-1818-VSL:midi/playback_1
> port created: AudioBox-1818-VSL:midi/capture_1
> port created: USB-Uno-MIDI-Interface:midi/playback_1
> port created: USB-Uno-MIDI-Interface:midi/capture_1
> port created: MidiSport-1x1:midi/playback_1
> port created: MidiSport-1x1:midi/capture_1
> port created: rosegarden:midi/capture_1
> port created: rosegarden:midi/playback_2
> port created: rosegarden:midi/playback_3
> port created: rosegarden:midi/capture_3
> port created: rosegarden:midi/playback_4
> 01:44:00.349 ALSA connection graph change.
> 01:44:02.472 JACK connection change.
> 01:44:02.475 Server configuration saved to "/home/johhnycrash/.jackdrc".
> 01:44:02.476 Statistics reset.
> 01:44:02.485 Client activated.
> 01:44:02.486 Patchbay deactivated.
> 01:44:02.487 Post-startup script...
> 01:44:02.488 /usr/bin/pajackconnect start && a2jmidid -e &
> 01:44:02.574 JACK connection graph change.
> sh: 1: /usr/bin/pajackconnect: not found

Whatever pajackconnect is, it is missing. But I think it's only needed
when Pulseaudio is running and is to be configured to output to jackd.

> 01:44:02.893 Post-startup script terminated successfully.

Now try jack clients like Audacity configured for jack. Rosegarden seems
to use the MIDI ports at least.

> With jack started with qjackctl, Mixbus fails unfortunately the same way as
> before.
> [ERROR]: JACK: Cannot callback the server in notification thread!

Mixbus wants to do its own thing. Maybe it needs a jackd running with an
associated server name that's nonstandard. Since Mixbus is a commercial
product I'd ask the vendor/manufacturer.

If they want to run jackd with a different name then everything else
will become a bit more complicated. But that's not jackd's fault.