-
Notifications
You must be signed in to change notification settings - Fork 378
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
Comments
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 Option 2: Use JackRouter.dll which doesn't rely on libjack.dll. 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. |
Hi. I have similar issues.
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.
Could you share that dll file please? |
Sorry, you are right. I tried this option again and it fails. Please try below.
It works in my environment.
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. |
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:
Yes, I was referring to the latter. |
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 can run the version of qjackctl included with radium to start jackd.
…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.
|
I never succeeded working with jackd with the qjackctl included in radium.
|
On Sun, May 12, 2019 at 5:26 AM cjunekim ***@***.***> wrote:
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.
Hmm, yeah, if I remember correctly, qjackctl included with radium only
uses the version of jackd included with radium if you haven't
installed jack globally. But since you have installed jack globally,
this version of jackd will not be used. If this is the problem, it t
should work to manually write in the full path to the version of jackd
you are using in qjackctl settings.
|
just to add a comment here for anyone still fighting with this issue... |
I have up entirely. We need something simpler or a step by step tutorial. |
I think this has been resolved with Jack 1.9.17. Could someone confirm this? |
i had a (very) quick look, and from what I see, it seems to work as expected now! |
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?
The text was updated successfully, but these errors were encountered: