Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Traktor pro 3 crashed when choosing Jackrouter as audio device #393

Open
kdejaeger opened this issue Nov 13, 2018 · 12 comments
Open

Traktor pro 3 crashed when choosing Jackrouter as audio device #393

kdejaeger opened this issue Nov 13, 2018 · 12 comments
Labels
Windows Bug or feature related to using JACK on Windows

Comments

@kdejaeger
Copy link

It's been known that to solve this issue on traktor 2, you needed to copy traktor.exe from the x86 folder and use the x86 version of traktor. Now with pro 3, there's no more x86 version. Is there any other workaround for this on the side of jackaudio?

@7890 7890 added the Windows Bug or feature related to using JACK on Windows label Jan 14, 2019
@madhatter68
Copy link

I met the same issue with UVI products. I suspect that the root cause is the same as #275, #332, #380. I mean libjack64.dll in the current jack distribution is not compatible with recent Windows.

I tried several things and found some ways to avoid this issue.

Option 1: Use jackaudio environment distributed by Radium
Download from here and replace C:\Windows\libjack*.dll by DLLs in bin\jack_local directory.
I think this is the most reliable way, but it doesn't include net driver.

Option 2: Use JackRouter.dll which doesn't rely on libjack.dll.
I build my own JackRouter.dll which is linked with the objects of libjack.dll statically. It works well for now. But it works only for the application which uses JackRouter.
For reference, I published source code on my github (branch_name: JackRouter_static). I also put the pre-built binary here. It's not tested well. Please try at your own risk.

In addtion, I built libjack64.dll from the latest source in 'develop' branch with the latest MSYS MinGW envrionment. The issue looks resolved, but it looks require to rebuild all binaries including qjackctl. So I don't think it's good option for now.

@cjunekim
Copy link

cjunekim commented May 11, 2019

I met the same issue with UVI products. I suspect that the root cause is the same as #275, #332, #380. I mean libjack64.dll in the current jack distribution is not compatible with recent Windows.

Hi. I have similar issues.

I tried several things and found some ways to avoid this issue.

Option 1: Use jackaudio environment distributed by Radium
Download from here and replace C:\Windows\libjack*.dll by DLLs in bin\jack_local directory.
I think this is the most reliable way, but it doesn't include net driver.

I couldn't run jack server(qjackctl and start jack server) with the libjack*.dlls from Radium as you wrote. The official jack server runs with the original dlls, though.

Option 2: Use JackRouter.dll which doesn't rely on libjack.dll.
I build my own JackRouter.dll which is linked with the objects of libjack.dll statically. It works well for now. But it works only for the application which uses JackRouter.
For reference, I published source code on my github (branch_name: JackRouter_static). I also put the pre-built binary here. It's not tested well. Please try at your own risk.

In addtion, I built libjack64.dll from the latest source in 'develop' branch with the latest MSYS MinGW envrionment. The issue looks resolved, but it looks require to rebuild all binaries including qjackctl. So I don't think it's good option for now.

Could you share that dll file please?

@madhatter68
Copy link

I tried several things and found some ways to avoid this issue.
Option 1: Use jackaudio environment distributed by Radium
Download from here and replace C:\Windows\libjack*.dll by DLLs in bin\jack_local directory.
I think this is the most reliable way, but it doesn't include net driver.

I couldn't run jack server(qjackctl and start jack server) with the libjack*.dlls from Radium as you wrote. The official jack server runs with the original dlls, though.

Sorry, you are right. I tried this option again and it fails. Please try below.

  1. Copy all libraries (lib*) in bin\jack_local directory to C:\Windows.
  2. Run the original 'Jack Control' (not Radium one which crashes at start time somehow)
  3. Choose Radium's jackd.exe in 'Setup'->'Setting'->'Advanced'->'Server Prefix'
    e.g.) c:<your extracted path>\radium_64bit_windows-5.9.46-demo\bin\jack_local\jackd.exe -S
    NOTE: '-S' option is required in my environment.
  4. Start jack

It works in my environment.

Option 2: Use JackRouter.dll which doesn't rely on libjack.dll.
I build my own JackRouter.dll which is linked with the objects of libjack.dll statically. It works well for now. But it works only for the application which uses JackRouter.
For reference, I published source code on my github (branch_name: JackRouter_static). I also put the pre-built binary here. It's not tested well. Please try at your own risk.
In addtion, I built libjack64.dll from the latest source in 'develop' branch with the latest MSYS MinGW envrionment. The issue looks resolved, but it looks require to rebuild all binaries including qjackctl. So I don't think it's good option for now.

Could you share that dll file please?

Which dll, JackRouter.dll or libjack64.dll. The former one is already shared here. For the latter one, I need more work to rebuild and confirm something. I remember it requires other libraries replacement and command line starting up method because 'Jack Control' doesn't work.

@cjunekim
Copy link

cjunekim commented May 11, 2019

I tried several things and found some ways to avoid this issue.
Option 1: Use jackaudio environment distributed by Radium
Download from here and replace C:\Windows\libjack*.dll by DLLs in bin\jack_local directory.
I think this is the most reliable way, but it doesn't include net driver.

I couldn't run jack server(qjackctl and start jack server) with the libjack*.dlls from Radium as you wrote. The official jack server runs with the original dlls, though.

Sorry, you are right. I tried this option again and it fails. Please try below.

  1. Copy all libraries (lib*) in bin\jack_local directory to C:\Windows.
  2. Run the original 'Jack Control' (not Radium one which crashes at start time somehow)
  3. Choose Radium's jackd.exe in 'Setup'->'Setting'->'Advanced'->'Server Prefix'
    e.g.) c:\radium_64bit_windows-5.9.46-demo\bin\jack_local\jackd.exe -S
    NOTE: '-S' option is required in my environment.
  4. Start jack

It works in my environment.

Are you sure that works in a clean setting? I tried exactly as you wrote several times and all failed. Following is the error message I got:


17:48:53.670 Statistics reset.
17:48:55.262 JACK is starting...
17:48:55.262 e:\temp\radium_jack\bin\jack_local\jackd -S -R -P 95 -dportaudio -d"ASIO::Focusrite USB ASIO" -r48000 -p64
17:48:55.288 JACK was started with PID=77653104.
jackdmp 1.9.12
Copyright 2001-2005 Paul Davis and others.
Copyright 2004-2016 Grame.
Copyright 2016-2017 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 : e:\temp\radium_jack\bin\jack_local
Drivers/internals found in : e:\temp\radium_jack\bin\jack_local
Could not find any internals in e:\temp\radium_jack\bin\jack_local/jack!
Could not find any internals in driver directory!
JACK server starting in realtime mode with priority 95
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
17:48:57.336 Could not connect to JACK server as client. - Overall operation failed. - Unable to connect to server. Please check the messages window for more info.
17:49:01.256 JACK is stopping...
17:49:01.313 JACK was stopped

Option 2: Use JackRouter.dll which doesn't rely on libjack.dll.
I build my own JackRouter.dll which is linked with the objects of libjack.dll statically. It works well for now. But it works only for the application which uses JackRouter.
For reference, I published source code on my github (branch_name: JackRouter_static). I also put the pre-built binary here. It's not tested well. Please try at your own risk.
In addtion, I built libjack64.dll from the latest source in 'develop' branch with the latest MSYS MinGW envrionment. The issue looks resolved, but it looks require to rebuild all binaries including qjackctl. So I don't think it's good option for now.

Could you share that dll file please?

Which dll, JackRouter.dll or libjack64.dll. The former one is already shared here. For the latter one, I need more work to rebuild and confirm something. I remember it requires other libraries replacement and command line starting up method because 'Jack Control' doesn't work.

Yes, I was referring to the latter.

@cjunekim
Copy link

I succeeded. I had to run jackd from a console and then run qjackctl separately. It's strange. I used to able to run jackd inside qjackctl, but not now. Anyway, thanks!

@kmatheussen
Copy link
Contributor

kmatheussen commented May 11, 2019 via email

@cjunekim
Copy link

You can run the version of qjackctl included with radium to start jackd.

I never succeeded working with jackd with the qjackctl included in radium.

Cannot connect to named pipe = \\.\pipe\client_jack_qjackctl_0 err = 5
Cannot connect client pipe
Cannot connect to client name = qjackctl


On Sat, May 11, 2019 at 11:33 AM cjunekim @.***> wrote: I succeeded. I had to run jackd from a console and then run qjackctl separately. It's strange. I used to able to run jackd inside qjackctl, but not now. Anyway, thanks! — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub, or mute the thread.

@kmatheussen
Copy link
Contributor

kmatheussen commented May 12, 2019 via email

@raphaelquast
Copy link

just to add a comment here for anyone still fighting with this issue...
there is in fact a working solution mentioned here (e.g. disable randomized memory allocation for the application you intend to use with jacrouter) : rodrigodzf/Jack-Audio-For-Unity#15 (comment)

@kdejaeger
Copy link
Author

I have up entirely. We need something simpler or a step by step tutorial.

@dyfer
Copy link

dyfer commented Mar 15, 2021

I think this has been resolved with Jack 1.9.17. Could someone confirm this?

@raphaelquast
Copy link

i had a (very) quick look, and from what I see, it seems to work as expected now!
Thanks for resolving this!! 🚀

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Windows Bug or feature related to using JACK on Windows
Projects
None yet
Development

No branches or pull requests

7 participants