-
Notifications
You must be signed in to change notification settings - Fork 27
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
New device: Black Corporation Kijimi #74
Comments
While I really like my Kijimi, Black Corporation are notoriously bad at documenting stuff. I thing your best bet would be the person who wrote Bab Frik. He/She has some direct report with them and even made them fix stuff in the firmware. The repository for Babu Frik is here https://github.com/RitaAndAurora/kijimi-babu-frik |
@markusschloesser Yes, I found that repository. I thought asking for documentation is a better way. But if they don't reply, I'll ask Bab. |
I opened a question ticket with RitaAndAurora, let's see if they are willing to share info. |
I saw that, I follow her/him on gh as well :-) |
First shot at the Kijimi attached. |
@markusschloesser Did you try the Kijimi adaptation I attached here? |
unfortunately haven't been able to, work 😒. Will try on the weekend |
(cherry picked from commit 5555d88)
Kijimi put on hold since I received an email from Black Coporation offering me an NDA first. I need to see what they think is appropriate to disclose. |
test results:
|
@markusschloesser Maybe contact me via email at [email protected]. Quick answers:
|
will write you a mail.
|
Can later log what babufrik does when trying to auto configure thru midi-ox |
00063E48 Loo -- F7 Buffer: 4 Bytes SysEx End 00063E48 Loo -- F0 Buffer: 4 Bytes System Exclusive
|
re 1) changing your 15 to 14 doesn't change anything though 🤔🙄 |
Found it, it wasn't the timing but that my code took the reply from the MIDI loopback device also as a valid reply. I know check for the correct length of the message, and print the firmware version. That should fix it.
Yes, I implemented the friendlyBankName() function (adaptation programming guide) now, so you should get better names.
Yes, KnobKraft is dual licensed, so should somebody offer me tons of money I want to be able to sell it or parts of the code. So I cannot accept GPL3 code, even if KnobKraft is also AGPL. I made a new version that should fix all of the above issues, but I don't want to upload it here before I see what the NDA is that BC is proposing. |
|
@markusschloesser Yes, I got your email, sorry for not getting back on this. I think we still have a timing problem, as the request going out looks correct, at least to my knowledge. And no, I heard nothing from them, so I would suggest we continue getting the adaptation fixed, and when it works for you I'll submit it to them for clearance. |
don't worry, just wanted to make sure, that the mail was received :-) |
hey, to pick up on this (and because BabuFrik is currently crashing all the time): What was the outcome of the NDA thing? Shall we just continue? |
@markusschloesser We can continue, we only use stuff from BabuFrik. The main problem I remember was that you get empty patches all the while, and I believe it is a timing issue. In that way, similar to the one @Andy2No has with the Waldorf Pulse 2, ticket #136. I think I know the solution, but want to get the 1.15.0 out first. Hopefully today :-) |
did you ever change anything? |
@markusschloesser No, not that I know of. Maybe they fixed something, did you give it a firmware update? The Kijimi might be missing because I have not officially included it in the distribution, but could do that now if you have some success. I need to dive in again and see if edit buffer is supposed to work. |
No fw update in ages, but currently in Sicily, so can't check fw version. |
@markusschloesser Nice, enjoy Sicily! Have been there ages ago, still remember Syracuse as being especially nice, but generally awesome places and food. I will add the Kijimi to the official release. We also have a new throttling feature since the last experiments, I remember the Kijimi transferring many patches as plain 0, which might explain the reduced number of unique patches. I found a comment in the code that it has no edit buffer though :-/ Keep your version of the adaptation before installing the new one, I am not sure which version we had floating around in case we have a regression! |
I put in the BC Kijimi adaptation into today's 2.0.3. So you can try the released version and see if we still of open issues! |
Will do! Thank you! 😊 |
finally checked/compared the Kijimi adaptations, and yes, "my" version has a lot more stuff in it (edit buffer, friendly bank name, hasCorrectLength. Attached, does that mean that mine is newer/better? |
Great! That looks much newer/better than what I had. I can't remember to have seen that before, so probably you did it :-)? I can merge the changes in for the next release. The main thing that is missing and what might be problematic is that we can't convert old (short) format to new format, so we do not know if an old program converted to a state message would be accepted as an edit buffer? If that is not possible, we have the problem that only new patches can be sent to the edit buffer, making the adaptation somewhat inconsistent. Can you try to send this, it's a short edit buffer of one of the test patches: |
nope, you sent this to me on 24.01.2021 and I quote to which I replied with, that still too many patches are detected as duplicates and had attached this logfile
when I send this, the Kijimi switches to Bank 1, Patch 1, but does not send anything back. (but I need to check if I'm on the most current kijimi fw version (currently 1.3.6) |
Ha ha, I might remember... was that in the 4th or 5th lockdown :-)? The string I gave you was an edit buffer constructed from an old, short program, by dropping bank and program number from it. I think we have the device sorted out - we just need to check that all the empty patches are either actually empty, or if the device runs into some form of overload. Then we need to increase some message delay or request shorter banks. |
something like that 😂 |
Hey everyone, I'm late to the party, but I just found this thread. I have a Deckard's Dream II and asked BC several times for the SysEx implementation because I wanted to build something. I just got no meaningful answer, so I assumed that the DD just doesn't have SysEx. But now that I saw that Kijimi has it (and DD also mentioned above) it's unlikely. Do you know anything about DD II SysEx – or how to move forward with this? Thanks a lot! |
The guy who wrote babu frik (editor and librarian for the kijimi), also wrote an editor and librarian for the dd. So he must have had access to the full midi spec, incl sysex. As both editors are open source and on github, an adaptation is absolutely possible |
Thanks @markusschloesser ! I just wrote him an email. The editor/librarian you mentioned is J. F. Sebastian. It's great, but unfortunately it crashes when moving specific sliders on the DD II. I assume it was written with/for a DD 1. Anyway, I hope he'll respond. Getting any useful info directly from BC seems close to impossible. |
Interesting! I would expect the information required to be hidden here somewhere: https://github.com/RitaAndAurora/ddrm-jfsebastian/blob/master/Source/DDRMPresetBank.h#L53 though it's a bit sad that there is no proper documentation available. |
Yes, thanks, unfortunately too hidden for me. ;-) I would also mostly be interested in requesting/sending the edit buffer, which is not implemented in J. F. Sebastian. |
Didn't BC do a whole new midi implementation quite recently? And is edit buffer requesting actually supported by the DD? |
I didn't read anything about a new MIDI implementation. I'm pretty sure that I have the latest firmware and manual + addition. I just can't find any info on DD SysEx online, so I don't know if edit buffer request/send is supported. But the fact that it is not implemented in J. F. Sebastian could mean that it is not supported by DD. Hard to tell... |
I was wrong, they implemented quite a lot of nice new features for the Xerxes, but apart from LFO to midi clock sync, nothing new wrt to midi |
Doesn't look too good: RitaAndAurora/ddrm-jfsebastian#8 |
Well spotted. Indeed, doesn't sound good. :-( With their new Buchla 200 line BC will be even more busy, so I don't expect that to happen anymore. |
I sent a mail to Black Corporation asking for the sysex docs for the Kijimi and the Deckard's Dream. As there is already open source available, they might be open to do disclose it.
Originally posted by @christofmuc in #62 (comment)
The text was updated successfully, but these errors were encountered: