jackaudio
Could not connect to JACK server as client. - Overall operation failed. -
I am completely confounded after many hours of trying to resolve.
Win 10 Pro ver 20H2 build 19042.1288 all current OS and driver updates Jack2 ver 1.9.19 onboard audio Realtek audio all drivers current
Installed Jack2 1.9.19 configured with defaults start with Qjackctl Result:
14:13:05.085 Statistics reset. 14:13:09.074 JACK is starting... 14:13:09.074 C:/Program Files/JACK2/jackd.exe -S -X winmme -dportaudio 14:13:09.084 JACK was started with PID=7500. jackdmp 1.9.19 Copyright 2001-2005 Paul Davis and others. Copyright 2004-2016 Grame. Copyright 2016-2021 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 14:13:11.213 Could not connect to JACK server as client. - Overall operation failed. - Unable to connect to server. Please check the messages window for more info. 14:13:14.129 JACK is stopping... 14:13:14.189 JACK was stopped
I've tried every suggestion I could find in the forums. Uninstalled, cleared registry, reinstalled, no change. Have tried using the ASIO::Realtek ASIO interface and ASIO4All as interface instead of default, no change. Also tried those along with different sample rates and frames settings, no change. This seems to be a not uncommon issue.
I frequently and successfully install & use JACK on Linux boxes. So I'm pretty discouraged. Any advice or input, or a definitive "it just won't work on Win 10" would be appreciated. I'm trying to route audio without using external hardware. Thanks!
I had this working on Windows 10, but I recently upgraded my workstation hardware and installed Windows 11. Now I get this error.
It seems related to this log message.
Cannot connect to named pipe after wait = \\.\pipe\server_jack_default_0 err = 2
I installed the 64 bit version of jack for Windows.
I just got it working by switching the sound output device in Windows. Maybe Windows got exclusive access to my audio interface, and it interfered with jack. All I did was open the Windows Settings > System > Sound panel and toggle from my USB audio interface to another interface. I was able to run jack. Then I stopped jack and closed qjackctl, switched Windows' default sound output back to my preferred interface and was still able to open qjackctl and start jack. I haven't even selected an interface in the qjackctl setup menu. Hopefully toggling your default audio output interface in Windows fixes this, but I can't explain why it is working for me now other than Windows might have had some exclusive lock on the audio stack and toggling the interfaces in Windows settings "fixed" it.
I'm having a simulair problem. Unfortunately switching my sound output device does not solve the problem. After selecting my audio interface in the qjackctl setup the interface does not show in Graph. Interface is working without problems in other apps.
Any ideas?
You could try installing ASIO4ALL and seeing if that driver helps. In the interface selection menus there are lots of options for various Windows driver options. I haven't had any problem with the ASIO4ALL driver.
I'm having this same issue with 1.9.20 on a new machine. No matter what I try, it just no longer connects. Luckily it's only one ASIO client, everything else works, but the log is:
]Cannot open client Jack: JackWinSemaphore::Destroy jack_pipe.default_Resolve Jack: JackExternalClient::Close Jack: JackWinNamedPipeNotifyChannel::Close Jack: JackClientPipeThread::Execute 2c8a8e0 Jack: JackRequest::ClientClose Jack: JackEngine::ClientExternalClose ref = 2 Jack: JackEngine::ClientCloseAux ref = 2 Jack: JackGraphManager::RemoveAllPorts ref = 2 Jack: JackDriver::ClientNotify ref = 2 driver = system name = qjackctl notify = 1 Jack: JackDriver::ClientNotify ref = 2 driver = freewheel name = qjackctl notify = 1 Jack: JackWinSemaphore::Destroy jack_pipe.default_qjackctl Jack: JackExternalClient::Close Jack: JackWinNamedPipeNotifyChannel::Close Jack: JackShmMem::delete size = 0 index = 12 Jack: JackClientPipeThread::ClientRemove ref = 2 Jack: JackClientPipeThread::Close 0 2c8abe0 2 Jack: JackWinThread::ThreadHandler : exit Jack: JackRequest::Notification Jack: JackDriver::ClientNotify ref = 1 driver = freewheel name = freewheel notify = 18 Jack: JackDriver::ClientNotify ref = 1 driver = freewheel name = freewheel notify = 18 Jack: JackDriver::ClientNotify ref = 1 driver = freewheel name = freewheel notify = 18 Jack: JackDriver::ClientNotify ref = 1 driver = freewheel name = freewheel notify = 18 Jack: JackEngine::ClientNotify: no callback for notification = 4 Jack: JackEngine::ClientNotify: no callback for notification = 4 Jack: JackClientPipeThread::Execute 2c5b1f0 Jack: Cannot read named pipe name = \.\pipe\server_jack_default_0 err = 109 Jack: JackClientPipeThread::Execute : cannot decode header Jack: JackClientPipeThread::ClientKill ref = -1 Jack: Kill a closed client 2c8a8e0 Jack: JackClientPipeThread::Close 0 2c8a8e0 -1 Jack: JackWinThread::ThreadHandler : exit`
I had this issue as well, specifically with ASIO4ALL as the interface. I solved it by going to the Advanced tab and changing Start Delay from 2 seconds to 10 seconds. It seems ASIO4ALL needs some more time to start up than the default 2 seconds. Hope this helps others.
EDIT: NVM, seemed like it fixed it yesterday, but today it is again not working despite this fix...
