Probably a long shot because most of y’all are on Linux, but I’m on Windows and trying to use Jack2 on Windows to connect MIDI applications and failing horribly.
In QJackCtl the option to select a MIDI driver is just greyed out? I’ve been able to use loopMIDI for a loopback MIDI device to connect programs, but that sidesteps Jack completely which is not what I want.
In my testing scenario, I have Pure Data (Pd) running the audio/midi test patch, and Virtual MIDI Piano Keyboard (VMPK) as well, a piano keyboard. I can use loopMIDI to connect the two and Pd will successfully send random MIDI notes to VMPK which it will then play as audio. But again, I want to be using Jack for this instead so I can manage things in one place.
How can I route MIDI data between these two applications via Jack on Windows?
Hello there,
I am running asahi Linux/Fedora on a MacBook Pro 16" with a M1Pro Chip.
Everything works out of the box, but I have severe issues with jack. I
need Jack for other Lisp-based stuff so: when I start jack using alsa,
the speakers are literally gone, there is only a dummy device left
without sound. I already created the audio groups etc. The speaker
problem does not occur, if I youse portaudio in Jack (which is useless)
or if I start Qjackctl as root, but then I cannot access jackserver from
within Emacs, so this doesn’t solve anything. Pulseaudio cannot be
installed without destroying the whole system sound on Asahi. So I am
confused, if there could be another workaround. This is, what jack is doing
danielhensel@danielhensel-macbookpro:~$ jackd -R -dalsa
jackdmp 1.9.22
Copyright 2001-2005 Paul Davis and others.
Copyright 2004-2016 Grame.
Copyright 2016-2023 Filipe Coelho.
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
no message buffer overruns
no message buffer overruns
no message buffer overruns
JACK server starting in realtime mode with priority 20
self-connect-mode is “Don’t restrict self connect requests”
audio_reservation_init
Acquire audio card Audio0
creating alsa driver … hw:0|hw:0|1024|2|48000|0|0|nomon|swmeter|-|32bit
configuring for 48000Hz, period = 1024 frames (21.3 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
As soon as this starts, there is no audio device left.
All the best Daniel