jackaudio
Null Client in Windows
Describe the bug
I am trying to set up Jackaudio on Windows system for a customed python-based GUI. The GUI needs to call Jack Client to control the stimulus generation. However, when I run the QjackCtl, it keeps returning Null Client. There is no error reported so far.
Looking forwards to comments and suggestions on how to solve this issue. Many thanks :)
Environment
- JACK Version: jackdmp version 1.9.21 tmpdir server protocol 9
- Operating System: Windows 10 Pro
- Installation: Package manager
- External Audio Device: RME Fireface UC
Steps To Reproduce
- QjackCtl
Sample Rate = 96000 (To meet experimental requirements for high frequency sound) Frames/Periods = 1024 Port Maximum = 256 Timeout (msec) = 500 Output Device = ASIO::ASIO Fireface USB Input Device = ASIO::ASIO Fireface USB Start Delay = 2 secs
13:42:54.684 Statistics reset.
13:42:54.710 JACK is starting...
13:42:54.710 ./jackd.exe -dportaudio -r96000 -p1024 -D -C"ASIO::ASIO Fireface USB" -P"ASIO::ASIO Fireface USB"
13:42:54.730 JACK was started with PID=13640.
jackdmp 1.9.21
Copyright 2001-2005 Paul Davis and others.
Copyright 2004-2016 Grame.
Copyright 2016-2022 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
Drivers/internals found in : C:\Program Files\JACK2
Drivers/internals found in : C:\Program Files\JACK2
JACK server starting in realtime mode with priority 10
self-connect-mode is "Don't restrict self connect requests"
Cannot connect to named pipe after wait = \\.\pipe\server_jack_default_0 err = 2
Cannot connect to server request channel
jack server is not running or cannot be started
JackShmReadWritePtr::~JackShmReadWritePtr - Init not done for -1, skipping unlock
JackShmReadWritePtr::~JackShmReadWritePtr - Init not done for -1, skipping unlock
jack_deactivate called with a NULL client
jack_deactivate called with a NULL client
jack_client_close called with a NULL client
13:42:56.987 JACK connection change.
13:42:56.989 Statistics reset.
13:42:56.993 Client activated.
13:42:56.993 Patchbay deactivated.
13:42:57.013 JACK connection graph change.
- Testing in cmd
C:\Program Files\JACK2>jackd -v -n testing -d portaudio -l
jackdmp 1.9.21
Copyright 2001-2005 Paul Davis and others.
Copyright 2004-2016 Grame.
Copyright 2016-2022 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
Drivers/internals found in : C:\Program Files\JACK2
Drivers/internals found in : C:\Program Files\JACK2
JACK server starting in realtime mode with priority 10
self-connect-mode is "Don't restrict self connect requests"
Jack: JackWinThread::StartImp : create non RT thread
Jack: JackWinThread::ThreadHandler : start
Jack: Initializing PortAudio...
Cannot connect to named pipe after wait = \\.\pipe\server_jack_default_0 err = 2
Cannot connect to server request channel
jack server is not running or cannot be started
JackShmReadWritePtr::~JackShmReadWritePtr - Init not done for -1, skipping unlock
JackShmReadWritePtr::~JackShmReadWritePtr - Init not done for -1, skipping unlock
Open error: is JACK server running?
jack_deactivate called with a NULL client
jack_deactivate called with a NULL client
jack_client_close called with a NULL client
********************** Devices list, 30 detected **********************
**************************** End of list ****************************
Cannot initialize driver
Jack: no message buffer overruns
Jack: JackWinThread::Stop
JJaacckkS:e rJvaecrk:W:iOnpTehnr efaadi:l:eTdh rweiatdhH a-n1d
ler : exit
Jack: Succeeded in unlocking 107341340 byte memory area
Jack: JackShmMem::delete size = 0 index = 0
Jack: ~JackDriver
Jack: Succeeded in unlocking 1196 byte memory area
Jack: JackShmMem::delete size = 0 index = 1
Jack: Cleaning up shared memory
Jack: Cleaning up files
Jack: Unregistering server `testing'
Failed to open server
I have the same issue with a couple of applications on Windows that will connect fine to the native ASIO hardware driver, but won't connect to ASIO if JACK is running. Doesn't even list JACK as an ASIO option as it would seem to return this NULL client error when scanning the audio devices it has available to itself.
