MK1 devices dont seem to work at all with KompleteSynthesia #13
Assignees
Labels
Comments
Wait, this is a bit different from the screenshot in the setup, maybe a new version of Synthesia broke it? |
|
If I have the keyboard turned off I do get a different error message: 
|
|
Managed to capture the full app launch and crash lifecycle in the logs, see below. This looks like the culprit: Or maybe this is the problem? Does the app need some accessibility functionality that it's trying to generate a prompt for? Logs filtered to Errors and Faults: Full logs: |
Can you try quitting that thing before trying KompleteSynthesia? |
I tried, but it's an Apple daemon and pops right back up. 
|
|
Oh interesting - I'll look into that later... |
|
Ok - I am just now realising that indeed MK2 is the problem. #1st bug #2nd never tested on MK1 and already know there will be issues However, the basic lightguide support should be there - KompleteSynthesia should support MK1 and MK2 controllers alike. I'll release a new version soon that makes the video support fully optional and thus might have a better chance working for you. |
|
Please try https://github.com/tillt/KompleteSynthesia/releases/tag/v0.53 and report back. Thanks a bunch for your help. |
|
Oh, I made a bad mistake now - forget 0.53 - it is problematic. |
|
Checkout https://github.com/tillt/KompleteSynthesia/releases/tag/v0.54 please... |
|
Great, thank you so much! There's progress, the app launches now, detects the keyboard and I can see the notes coming up in the log: 
Unfortunately, the lights still don't change on the keyboard though in any of the play modes 😿 I tried the troubleshooting steps like "Repair light configuration" and "Reset", making sure no NI apps are running, etc, but still no lights. Is there a debug / verbose mode to get more logs? Or should I try to build the project in XCode so I can help debugging it? |
|
Oh jeez - so sorry for that @daaain . I just never tested it with MK1 devices. We see you receiving data from the LoopBe interface just fine. We also see no further error messages from the HID interface when detecting your controller or when sending an update of the lightguide to the controller; . That leaves us with a potential problem in the light-guide message itself. Are we using the correct command code for MK1 and are we encoding the colours correctly? After now reviewing the code I once copied from, I can see the encoding KompleteSynthesia is using won't work for MK1 devices. This would need a slighty more involved update for the lightguide messages but also a more involved update for the colour selection in the preferences pane - as the MK1 devices did support a larger colour space. Worst part here is that I can't test things - so development will be slow. However, I would really love to support all breeds of Komplete Kontrol controllers, MK1, MK2 and MK3. |
tillt
changed the title
|
Come on, no need to apologise, you don't owe me anything 😉 I can definitely try to contribute, haven't done Mac development, but it's a relatively simple app and I'm quite motivated to get it working with my keyboard 😸 I'll try to compile the app and see if I can get something going. Basically the job is to make sure the app is always in the right mode for each keyboard (and might need a bit of abstraction to make it work with MK3 in the future I guess?) and to double check the MK1 hex codes from the Python library, right? One thing I noticed is that there's a ternary to choose between One interesting thing is that I tried pressing |
|
There is hope; see #14. I am now producing an alpha release for you to test. It definitely won't be perfect, but it might show some lightguide effect for MK1 devices. Things that I am already pretty sure that won't be perfect:
|
|
This is it, with 0.55.0.4 I think the MK1 support is perfect (at least with my S49 and without the swoosh)! |
|
Hey, so now that this is all working, do you want me to record a video of it to put in the README or something? |
|
A video might actually be super cool. I was also just wondering how we can point out this new feature. The video would have to be hosted somewhere - ie YouTube. PR welcome!!! :D Maybe you have a good idea on where to add your experience with a MK1 controller? Then lastly, lets definitely add the following paragraph at the end of the README: |
|
Resolved by #14 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Just got v0.52 installed, followed SETUP.md to create the LoopBe device and then figured I need to specially approve the app in Privacy & Security and then finally managed to open it and pointed to the
multiDevice.xmlfile (that dialog was a bit confusing and only found out about it by searching for the filename and finding #1).Everything seems to be in order, but I can't even get the app to start, just get this unhelpful error message that is not covered in troubleshooting.
I have an M1 Mac running Mac OS 13.5.2 (22G91).
Any idea what's going on?
Wait, does it only work with MK2?
The text was updated successfully, but these errors were encountered: