Merry Christmas - best gift. Thanks! #11
Comments
|
Hi there. What happens if you press the "Open User Client" button? To be honest, the development of the macOS driver has been incredibly frustrating due to issues I explained on the README. Anwyays, should be possible to make it work. Can you try to retrieve some more logging using: |
|
Hey there - I tried the Open User Client button and nothing happened. What should I see?
Any ideas? I tried the "Uninstall Dext" at one point and then aborted because it said it wanted to change system level extensions... that may be some of the errors in the log Just to be clear, I should be running the XoneDB$ app in the releases folder right? Anything else I could try? I think I successfully followed the other steps. |
|
Couple of observations:
|
|
It's ALIVE! It sounds SOOOOOOOOO good! 
Thanks - I did exactly what you said and changed the architecture in the XCode Project file as so: 
Since I am guessing that many of the people who have tried to get this working may have got lost in the software engineering parts of this, I would be happy to create a bit more of a "I like to mix music and don't know anything about compiling software" installation guide if you want!? Thank you! |
surfacescan
changed the title
|
Wait - so I don't need to run the XoneDB4 app to use the mixer? I just realised this! |
|
Glad to hear!
Indeed. The problem you encountered is something I can fix in code tho. Will do. But also many people get lost in code signing issues. Of course: things would be better if I could just make a signed driver available which would avoid the steps required to compile the driver and get macOS to actually accept it. But the only option I found is paying for the Apple Developer Program which I kindly refuse.
That's correct! I'm having a really hard time to get the app to connect to the active driver. I'm not sure if that works correctly, but it's needed in case you want to change the buffersize. The Linux driver was sooooo much easier to get running and get running smoothly. Apple just got in my way at every turn. |
|
Build targets updated in code: |
|
I also seem to be lost in Code Signing issues! I currently have these errors: XoneDB4Driver isn't code signed but requires entitlements. It is not possible to add entitlements to a binary without signing it. system extension didFailWithError: Missing entitlement com.apple.developer.system-extension.install I am not familiar with Xcode at all, but would love to get the DB4 working on my M4 MBP! Cheers. |
|
I will try my best to write up things in a bit more detail in the README. But as you might have guessed I prefer coding and getting things to work to making guides. Maybe you missed changing the CODE_SIGN_IDENTITY in codesign.sh? Change it for the value you find using |
|
hey @mischa85 - I have gotten the driver working but it is a bit hit and miss. I can do a more thorough breakdown of the scenarios that I lose connection to the mixer if that would be helpful.\ But before that, I want to rule out a possible culprit. I am also encountering some challenges now on my Digitakt which I connect through USB to something called Overbridge (a plugin that lives in Ableton and allows 8 virtual tracks). Someone from Elektron thought that perhaps the If yes - what might those commands be? I wonder if this might help make the mixer more stable for my general use on my powerbook. After a bit more testing, I would be happy to help write a more "I like to mix music" step by step guide to getting things up and running. |
|
Hey @surfacescan, first of all, thank you for testing. It's motivating te keep developing when people are actually testing the driver. Interesting case. I know the Digitakt is also using Ploytec software/hardware and I know they've been working on a DriverKit driver. But sadly Elektron never released any source code so I could never have a look. They have also been battling macOS security mechanisms: https://support.elektron.se/support/solutions/articles/43000566545-blocked-overbridge-driver-macos- On top of that, we're also battling signing issues here. I will experiment as well as I have a friend who is a Digitakt warrior, but can you check what prevents the driver to load and function? You can reverse the changes like this:
|
|
Thanks for updating the README @mischa85. I made some progress last night after following the new guide and managed to briefly connect the DB4. Unfortunately the driver seems unstable and after a while I get an error: "XoneDB4Driver has experienced an error during deactivation. When opening in Xcode I see this in the Build: And Initialization of immutable value 'outdiff' was never used; consider replacing with assignment to '' or removing it I copied the full 40 digit code from terminal into codesign.sh XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX "Apple Development: [email protected] (XXXXXXXXXX)" Let me know if I am missing anything! @surfacescan Happy to help out with a guide too if I get this running... |
My first thought is that your DB4 firmware is still using the BULK transfer mode (pre 1.4.1 firmware). I actually just re-added support for this transfer mode to the Linux driver. I'll add it to the macOS driver too. Some 2012-2013ish Macbooks have a bug in the USB controller requiring this update for smooth audio streaming, but some devices never received it. But in your case: please update the audio firmware. |
|
I just checked the DB4 firmware and I am running v2.2.2 I tested on both M1 Max & M4 Max MBP running macOS Sequoia 15.2 and found the same issue. |
|
You are confusing the mixer firmware with the audio interface firmware. The audio firmware updater is part of the "XONE:DB4 Device software": https://www.allen-heath.com/hardware/legacy-products/xonedb4/resources/ For updating the audio firmware you will need a system still supporting the updaters, when I have time I will also implement this in the driver. |
|
Ah ok, I had not installed this on the M series as thought your driver was replacing this. I will test and get back to you.... |
|
You don't need to install the driver though. There's a separate executable in there that allows you to update the audio firmware. |
|
Is that the FWUpdater_XONE_DB4_3.3_1.39? I just get the “FWUpdater_XONE_DB4_3.3_1.39” needs to be updated. |
|
Yep, that's where the problem is. The FWUpdater has never been compiled for arm64 (Apple silicon) and needs to be reverse engineered as well. If you have an older Mac or any Windows machine around you can run it on there. I think the Windows driver even has the update to 1.4.1 in there. |
|
Ah ok, so no chance on the M chip Macs right now? |
|
I'm actually working on adding support for the old BULK transfer mode to the macOS driver. Just like what I did to the Linux driver: df71ad7. That should make DB4/DB2's running on old firmware work. Again, if you have any Windows computer around just for the update, that'll make the driver work properly on your Apple silicon Mac. |
|
Ok, fingers crossed then! I have no Windows machine, I could dig out an old Mac though! |
|
Okay I re-added bulk streaming to the macOS driver. Needs testing, might have some math wrong. |
|
Nice work! I have clean Audio coming out of the DB4 from Ableton! |
|
Ableton doesn't seem to recognise the DB4 for Midi mapping. |
|
Nice to hear audio is working! MIDI is at the moment only implemented in the Linux driver. I'll see if I can get some support in the macOS driver asap. |
|
Good stuff. I will keep an eye on development and test further once you have MIDI implemented. |
Hey there - I am running the built app and I see the following. It all looks good until I click the Open User client button.
I ran the log and got the following:
Timestamp Thread Type Activity PID TTL 2024-12-25 19:05:45.471536-0500 0x3e86 Default 0xec43 1292 0 XoneDB4App: system extension actionForReplacingExtension: <private> <private> 2024-12-25 19:05:45.522811-0500 0x3e86 Default 0xec43 1292 0 XoneDB4App: system extension didFinishWithResult: 0Is it possible for you to upload what I should expect to see/behaviour?
I am considering buying the Ploytec Revival on kickstarter - but first wanted to give your driver a try!
The text was updated successfully, but these errors were encountered: