11-26-2024, 07:44 AM
I can imagine that it indeed generates too much data to all together push out via midi.
If I just think about the fact that the input is being already received back to back via midi and you double the data for the output which could cause the output data to be buffered = midi data limits.
Maybe I need to add a limitation for the midi data that the mappings could generate. Just keep in mind that every row gets executed every millisecond. So each millisecond a CC data could be added which is faster already than each midi cc data needs to be send out. Imagine now multiple rows being executed within that millisecond….traffic jam :-)
However, that doesn’t explain everything you describe. Maybe you can also send me your project so I can take a look.
If I just think about the fact that the input is being already received back to back via midi and you double the data for the output which could cause the output data to be buffered = midi data limits.
Maybe I need to add a limitation for the midi data that the mappings could generate. Just keep in mind that every row gets executed every millisecond. So each millisecond a CC data could be added which is faster already than each midi cc data needs to be send out. Imagine now multiple rows being executed within that millisecond….traffic jam :-)
However, that doesn’t explain everything you describe. Maybe you can also send me your project so I can take a look.
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!