search

x42 / xjadeo

X JAck viDEo mOnitor: a tool that displays a video clip in sync with an external time source (jack-transport, LTC and MTC). Applications include: soundtrack composition/editing, video monitoring and -installations.
http://xjadeo.sf.net/
GNU General Public License v2.0
41 stars 7 forks source link

Xjadeo not connecting to Jack #42

Open JustSomeDudeWithAProblem opened 3 years ago

JustSomeDudeWithAProblem commented 3 years ago

I'm very new to all this, so if this is a common error, sorry about that.

I can confirm that jack is working correctly, as I'm able to use it to start/stop musescore (my notation program). I'm trying to sync Xjadeo to Jack as well, so that I can write to picture, however whenever I start Xjadeo, I am unable to connect to jack, and XJadeo doesn't show up in the Jack Graph (see attached picture). I ran Xjadeo from Command Prompt, and it gave me the error message "Failed load JACK shared library", as well as "jack_client_open() failed". Anyone know what this means, and can help me fix it?

Thanks, -Nick image image

x42 commented 3 years ago

XJadeo doesn't show up in the Jack Graph (see attached picture).

This is normal. it does not have any Audio or MIDI ports. You can explicitly select JACK-MIDI (if you want to use MTC).

"Failed load JACK shared library", as well as "jack_client_open() failed". Anyone know what this means, and can help me fix it?

It means that xjadeo searches for libjack.so at runtime and fails to find it. Which GNU/Linux distribution are you using, and where did you get xjadeo from?

JustSomeDudeWithAProblem commented 3 years ago

I'm on windows 10, not Linux. Using the Windows versions of both Jack and Xjadeo. I downloaded the installers from the respective websites (https://jackaudio.org/downloads/ and http://xjadeo.sourceforge.net/download.html) I tried running both the installers again but it didn't do anything. Is there something else I should download?

x42 commented 3 years ago

Oh, OK. In that case does the architecture match? 64bit JACK + 64 bit Xjadeo?

@falktx is libjack64.dll installed to C:\Windows\System32\ or a place where it can be found via LoadLibraryA()?

falkTX commented 3 years ago

the jack libs are installer in %windir%, so yes they are loadable by applications. same as old installer, libjack64.dll is used for 64bit client lib, and libjack.dll for 32bit.

I have tested and seen working ardour, bitwig and carla, so this is working fine afaik

JustSomeDudeWithAProblem commented 3 years ago

I installed the 64 bit versions of both. However I did notice that the files for Xjadeo were in the "Program Files x86" as opposed to the 64 bit folder. Is that normal?

mbaklor commented 3 years ago

A little late but just found this thread. Did you get it to work?

JustSomeDudeWithAProblem commented 3 years ago

A little late but just found this thread. Did you get it to work?

Unfortunately, I still haven't gotten it to work. I keep getting the same error even after a re-install of both programs.

linuxgeek commented 3 years ago

I have this problem on Win10. I've done some troubleshooting. I think it might not be loading the proper library. I have 64-bit jack, 64-bit musescore, 64-bit ardour all working. I have an ASIO compatible sound card (M-Audio 192 6 ASIO)

The DLLs should be in C:\Windows\libjack.dll C:\Windows\libjack64.dll

It should be loading "libjack64.dll", but it's not. You can tell it's looking for "libjack.dll". I can delete "libjack64.dll" and nothing different happens. Still says failed to load library. I rename libjack.dll to something else, and copy "libjack64.dll" so that it's ALSO "libjack.dll". xjadeo then comes up with different messages. It should never have gotten to "libjack.dll", cause it should have found "libjack64.dll", so I think it's not compiled correctly.

C:\Program Files\xjadeo>selected MIDI driver: JACK-MIDI using JACK-transport as sync source. Cannot open xjadeo client JackShmReadWritePtr1::~JackShmReadWritePtr1 - Init not done for -1, skipping unlock JackShmReadWritePtr::~JackShmReadWritePtr - Init not done for -1, skipping unlock JackShmReadWritePtr::~JackShmReadWritePtr - Init not done for -1, skipping unlock jack_client_open() failed, status = 0x21

linuxgeek commented 3 years ago

FYI, the 32-bit version seems to connect with JACK in Win10(64-bit).

43

45

linuxgeek commented 3 years ago

Update. I have everything working fairly well with the 64-bit versions. Sometimes I have to restart an application. Musescore 3.6 w/jack Ardour 3.6 w/jack xjadeo 0.8.10 w/jack jack 1.9.19 win64

hardware: M-Audio Air 192/6 (32-bit ASIO driver) MIDI keyboard

The problems came down to a few things.

  1. Everything needs to be run as Administrator, so put this in the compatibility tab for all the shortcuts.
  2. I had to force quit the ASIO driver if it was loaded before qjackctl. Works better if qjackctl grabs the ASIO driver directly when it launches. If qjackctl is the one grabs it, it'll also unload when you exit or force-quit qjackctl.
  3. Sometimes had to get MIDI ports active by connecting to them beforehand to make sure qjackctl would bind them.
  4. Often times the qjackctl would fail the first time launching the jack server. It ends with this in the messages: "JackClientPipeThread::Execute". It works if you try again by stopping the jack server, but you'll have to force quit qjackctl. Launch it again and this next time will work and Messages will end with one more line, being this: JACK active patchbay scan.."
  5. Lastly, but most importantly, the .jackrc file in C:\Users\.jackrc is problematic as I can't figure out how it gets altered. I manually edited it until it worked and then I made it read-only.
spechtstatt commented 1 year ago

I was successful by removing the "C:\Windows\libjack.dll" and copying the "C:\Windows\libjack64.dll" to "C:\Windows\libjack.dll" so that there are in fact two 64-bit dlls with two different names.