Hi
For MacOSX softwares, Using Github, the packaging instruction had been
simply "brew install jack" ( rather than apt-get install -y libjack-
jackd2-dev" )
It worked in the past.
After a modification, I am having now the problem of the dev not found
(can not find the file <jack/jack.h>. I can not see why the
modification disrupts. I have only added one more variable to the make
command.
Regards
Patrick
Hello,
when I use Jack2 on macOS, how can I get realtime prio 95? I only get 10, no matter what I am trying.
This is my command /usr/local/bin/jackd -X coremidi -d coreaudio
JACK server starting in realtime mode with priority 10
Qjackctl doesn’t allow me to set a new value.
All the best, Daniel
> Am 02.03.2024 um 12:00 schrieb jackaudio-request(a)lists.linuxaudio.org:
>
> Send JackAudio mailing list submissions to
> jackaudio(a)lists.linuxaudio.org
>
> To subscribe or unsubscribe via email, send a message with subject or
> body 'help' to
> jackaudio-request(a)lists.linuxaudio.org
>
> You can reach the person managing the list at
> jackaudio-owner(a)lists.linuxaudio.org
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of JackAudio digest..."
>
> Today's Topics:
>
> 1. Re: Jack2 MIDI on Windows (Happy)
>
>
> ----------------------------------------------------------------------
>
> Message: 1
> Date: Fri, 01 Mar 2024 21:26:57 +0800
> From: Happy <happy.musicmaker(a)gmail.com>
> Subject: [Jackaudio] Re: Jack2 MIDI on Windows
> To: Isaac Beckett <isaactbeckett(a)gmail.com>,
> jackaudio(a)lists.linuxaudio.org
> Message-ID: <2e211bf0d4d49b66cb15a1b2b5348f2f5b4b6f69.camel(a)gmail.com>
> Content-Type: multipart/alternative; boundary="=-BdNvHSfboYZIAwJzLkP0"
>
> Hi there,
>
> My few takes on this
>
> Linux (ALSA) applications can create a virtual midi ports either with
> jack or ALSA
>
> On windows this is not possible (*)
>
> The only reson loopMIDI can be seend is that LoopMIDI is a Windows MIDI
> device driver, so it can be seen by windows a a MIDI device and thus
> also by Jack.
>
> VMPK is a client, it connects to TO a Windows MIDI port (not sure it
> supports jack)
>
> Pd could only connect to jack if it supported to create a jack client
> port, suppose it' can't
>
> Here is discord for MIDI , you could also try to post on midi.org forum
> or on linuxmuscians.com
> Not sure if there are any other forums for MIDI, targeting non-Linux.
> https://discord.gg/bkdNqbF3
>
> (*) until Windows MIDI 2.0 comes out, and then, no idea if jack will
> support the new Window service as the new service is similar to jack
> Windows MIDI 2.0 will support legacy MIDI 1.0, so perhaps then it may
> support connecting ports to each other and also Pd to jack through that
> new service.
> I haven't looked at this scenario yet.
>
> Besides that , perhaps we will see something alike pipewire on windows
> which already has replaced the jack driver on Linux.
>
> Thanks
>
>
> -----Original Message-----
> From: Isaac Beckett <isaactbeckett(a)gmail.com>
> To: jackaudio(a)lists.linuxaudio.org
> Subject: [Jackaudio] Jack2 MIDI on Windows
> Date: 03/01/2024 02:37:18 AM
>
> 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?
> _______________________________________________
> JackAudio mailing list -- jackaudio(a)lists.linuxaudio.org
> To unsubscribe send an email to jackaudio-leave(a)lists.linuxaudio.org
>
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