This was working fine in 3.4.4 but now crashes as soon as I choose the JackRouter driver in the settings Device option. Works fine with my sound card ASIO drivers and other applications work fine with the JackRouter device. I have tried re-installing both Jack and Jamulus to no avail.
I have reverted to 3.4.4 which works for now.
Any help in tracking down the issue would be grately appreciated.
A big thank you for all your hard work as in such times you have brought joy to a lot of locked down musicians.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
3.4.5 is a 64-bit application now. 3.4.4 was 32-bit. Please check if your ASIO driver is 32 bit. If you want to use the new 3.4.5, you have to install a 64 bit version of your ASIO driver.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
The 3.4.5 Jamulus installer automatically detects the OS. So if you have a 32 bit Windows, it will install the Jamulus 32 bit binary. Only if you have a Windows 64 bit installed, the Jamulus installer will install the 64 bit version of Jamulus.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I noticed that and an am under the impression that JackRouter works for both 32 an 64 bit clients as it works fine with Ableton Live which is 64 bit. I'm wondering if this is an issue with how Jamulus is seeing the ASIO drivers and somehow picking the wrong one. As a test I installed Jamulus in the Program Files directory and not the x86 one but that didn't help
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
That is strange. The only change from 3.4.4 to 3.4.5 which could cause the issue is that the Jamulus binary is now 64 bit. The other changes should not have any influence on the ASIO interface.
I also installed the Jack for Windows and actually it crashed on my PC for all Jamulus versions. I have debugged it and I got some strange Windows error which you cannot catch with a standard c++ try-catch mechanism. So it would indicate some fundamental problem like different bit depth. But I am stuck now with the investigation. Maybe someone else has some idea...
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Thanks @Volker for looking into this and sorry you are not able to see what the issue is. I have some more feedback if that is useful.
I've upgraded to 3.4.6 and same issue.
I tried setting the JackRouter with the server not running. I was expecting this to fail and go back to previous driver but it also crashes. It sees the JackRouter and fails immediately.
I've tried different buffer sizes in Jack but no change, still crashes
I've noticed an event in the event viewer if that helps:
On a different note, I've noticed that I can's start Jamulus >=3.4.5 after uninstalling and re-installing and having used 3.4.4. I did a clean install and uninstalled any previous versions then installed 3.4.6. I think there may be an incompatability with the settings .ini files. Once I renamed or deleted these files, the application starts correctly.
Again your help is very much appreciated, thanks
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I see that other people are having issues with the Focusrite driver. I'm using a 2i4 and as discussed above works fine in 32bit but not with JackRouter in 64bit so maybe the strange sample rate (136) is the issue as discussed in the thread https://sourceforge.net/p/llcon/discussion/533517/thread/e0f18d2381/
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I'm also having the same issue, i'm unable to run any Jamulus version > 3.4.4 with JackRouter Asio driver.
I also have a focusrite interface - scarlett 18i20 1st gen and i've updated to the beta drivers which fixed the buffer size issue, however Jamulus still doesn't even run (no error messages at all with version 3.5.0).
Running windows 10 64bit with jack also 64 bit.
Last edit: NecroDM 2020-04-17
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Update: I was able to extract the 32bit binaries from the 3.5.0 installer and it works without issues with JackRouter so the problem lies somewhere with the 64bit version of Jamulus, which is unexpected since it's the only application that's not 64bits
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Thank you for the tip. So now we have to find out why the 64 bit binary is not supported by Jack Audio or what we have to change so that it is compatible...
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
No problem, let me know if you need me for trying out 64bit test builds since it might be hard for you to replicate this issue without the same hardware.
Also in the meantime would it be possible to release the 32bit versions separately for future versions as a workaround?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Actually I do not want to maintain multiple installers. If we get a lot of problems with the 64 bit Jamulus, maybe I switch completely back to 32 bit with the installer...
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I used 7-zip to open the installer, extracting to a folder it'll ask if you want to replace files since it reads the 64bit and 32bit as being in the same folder. Say yes to replacement and you'll end up with the 32bit install
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
This was working fine in 3.4.4 but now crashes as soon as I choose the JackRouter driver in the settings Device option. Works fine with my sound card ASIO drivers and other applications work fine with the JackRouter device. I have tried re-installing both Jack and Jamulus to no avail.
I have reverted to 3.4.4 which works for now.
Any help in tracking down the issue would be grately appreciated.
A big thank you for all your hard work as in such times you have brought joy to a lot of locked down musicians.
3.4.5 is a 64-bit application now. 3.4.4 was 32-bit. Please check if your ASIO driver is 32 bit. If you want to use the new 3.4.5, you have to install a 64 bit version of your ASIO driver.
So us with 32 bit machines should stay with 3.4.4? I am on Ubuntu Studio 18.04 on an old P4 that is the workhorse for my band.
The 3.4.5 Jamulus installer automatically detects the OS. So if you have a 32 bit Windows, it will install the Jamulus 32 bit binary. Only if you have a Windows 64 bit installed, the Jamulus installer will install the 64 bit version of Jamulus.
I noticed that and an am under the impression that JackRouter works for both 32 an 64 bit clients as it works fine with Ableton Live which is 64 bit. I'm wondering if this is an issue with how Jamulus is seeing the ASIO drivers and somehow picking the wrong one. As a test I installed Jamulus in the Program Files directory and not the x86 one but that didn't help
That is strange. The only change from 3.4.4 to 3.4.5 which could cause the issue is that the Jamulus binary is now 64 bit. The other changes should not have any influence on the ASIO interface.
I also installed the Jack for Windows and actually it crashed on my PC for all Jamulus versions. I have debugged it and I got some strange Windows error which you cannot catch with a standard c++ try-catch mechanism. So it would indicate some fundamental problem like different bit depth. But I am stuck now with the investigation. Maybe someone else has some idea...
Thanks @Volker for looking into this and sorry you are not able to see what the issue is. I have some more feedback if that is useful.
I've noticed an event in the event viewer if that helps:
Faulting application name: jamulus.exe, version: 0.0.0.0, time stamp: 0x5e8f0848
Faulting module name: ntdll.dll, version: 10.0.18362.719, time stamp: 0x64d10ee0
Exception code: 0xc0000026
Fault offset: 0x00000000000fbf98
Faulting process ID: 0x392c
Faulting application start time: 0x01d60e6c7ee1dd76
Faulting application path: C:\Program Files\Jamulus\jamulus.exe
Faulting module path: C:\WINDOWS\SYSTEM32\ntdll.dll
Report ID: 681ed240-df78-4589-ae06-136c9f932ce9
Faulting package full name:
Faulting package-relative application ID:
On a different note, I've noticed that I can's start Jamulus >=3.4.5 after uninstalling and re-installing and having used 3.4.4. I did a clean install and uninstalled any previous versions then installed 3.4.6. I think there may be an incompatability with the settings .ini files. Once I renamed or deleted these files, the application starts correctly.
Again your help is very much appreciated, thanks
I see that other people are having issues with the Focusrite driver. I'm using a 2i4 and as discussed above works fine in 32bit but not with JackRouter in 64bit so maybe the strange sample rate (136) is the issue as discussed in the thread https://sourceforge.net/p/llcon/discussion/533517/thread/e0f18d2381/
I'm also having the same issue, i'm unable to run any Jamulus version > 3.4.4 with JackRouter Asio driver.
I also have a focusrite interface - scarlett 18i20 1st gen and i've updated to the beta drivers which fixed the buffer size issue, however Jamulus still doesn't even run (no error messages at all with version 3.5.0).
Running windows 10 64bit with jack also 64 bit.
Last edit: NecroDM 2020-04-17
Update: I was able to extract the 32bit binaries from the 3.5.0 installer and it works without issues with JackRouter so the problem lies somewhere with the 64bit version of Jamulus, which is unexpected since it's the only application that's not 64bits
Thank you for the tip. So now we have to find out why the 64 bit binary is not supported by Jack Audio or what we have to change so that it is compatible...
I can confirm that it works with the 32 bit binary. I just tested it and it works great.
No problem, let me know if you need me for trying out 64bit test builds since it might be hard for you to replicate this issue without the same hardware.
Also in the meantime would it be possible to release the 32bit versions separately for future versions as a workaround?
Actually I do not want to maintain multiple installers. If we get a lot of problems with the 64 bit Jamulus, maybe I switch completely back to 32 bit with the installer...
Any update on how to fix this or install the 32bit from the windows installer? @NecroDM how did you extract the 32bit files?
I used 7-zip to open the installer, extracting to a folder it'll ask if you want to replace files since it reads the 64bit and 32bit as being in the same folder. Say yes to replacement and you'll end up with the 32bit install