09-14-2023, 08:29 PM
(09-14-2023, 05:29 PM)nsolarz Wrote:(09-14-2023, 06:30 AM)XORadmin Wrote: I will not support the algorithmic specific commands as this is a hell to program. Just think about an implementation for every gear out there that has its own specific commands and packets for every specific function…and for every gear it is different. Which is already a fact and the worst thing about I2C.
Is there the potential to have a "definition" file format to handle some of these things? could work for midi too; I know other sequencers use similar systems to store things like which MIDI CC map to which parameter etc. that way the community would be able to "crowdsource" the more involved/esoteric I2C implementations. just an idea
That is something for DAWs but not for embedded systems with chronically low memory. And it would definitely not solve the problem to get a good implementation. Often you got to combine packets to get the needed results etc.
So in my opinion this is not an option. Still the custom commands let you define commands which are not there in case you would need them.
PLEASE use the search function if something have been asked or discussed before.
Every (unnessesary) forum support means less time to develop! But of course, i am here to help!Â
Every (unnessesary) forum support means less time to develop! But of course, i am here to help!Â


