![]() ![]() Access Virus (and many other devices) does the job as well and comes with full editor support. If you guys are not planing to develop a librarian or editor by yourselves, why then don’t you at least support the development of 3rd party editors? This is a major roadblock to me and I am definitively thinking about returning my Kyra to the vendor now. I don’t understand the product policy of Waldorf. We will continue to monitor the line but, at present, there hasn't been sufficient interest expressed and development is a challenge instead of being straight forward. The last round of Waldorf products either have no SysEx implementation or no SysEx documentation, which definitely makes it more difficult for us to provide support in Midi Quest. While we may add support for the Kyra in the future, currently we are working on other instruments. Here is, what they have answered on my inquiry: And they have confirmed that Waldorf does not (!) provide any sysex documentation - which is a shame. I have been in touch with the developers from Midi Quest who know more about editors. Please Log in or Create an account to join the conversation. So, until / unless Waldorf documents features that may be present, or else substantially increases the MIDI Implementation, it is essentially impossible to provide a computer based patch editor program. ![]() ![]() And yet it never sends any of those parameters from Kyra to the computer when you twist the knobs. I haven't tried this yet, but presumably that would overwrite Kyra's B bank with those patches from the A bank.īeyond that, Kyra responds to a handful of MIDI CC messages from the computer. So that probably means you could send the A Bank to a computer, then set up the Kyra to deal with the B bank, and have the computer send the bulk patches back to the Kyra. But there is no indication of Bank in any of these dumps. But there is no documentation on that state.įrom comparison of successive patch slots in one bank, I could find that byte 7 (from zero) contains the slot number for the patch, in a bulk dump. That will end up with a bulk of bytes that represent its internal state. At most you can manually send across the current editor buffer from Kyra to a computer. I just answered the question on how to back up Banks in the topic that directly asked that question.īut sadly, as I look at the documented MIDI Implementation, it is rather meagre, and cannot support a computer driven patch editor. I was looking at doing a patch editor last night. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |