And as mimidancer said 1 mb is a lot of midi data, i only remember some odd situations where you'd like to send so much data, like a bulk load definition for a controller, or something like that.Īnyway on some older devices you can see it updating initial device status (i.e. It only sends a big chunk on device changing or block change (grouping), and I think it even doesn't do it as a batch. I think all reason SDK's are now open source? So you can easily check the specification for remote here:Īs for your "1 mb" limit, I think what reason does is sending and receiving data through and trough as needed. However, if the throughput is too slow, then a different approtch is needed, perhaps a page based system a little like the Nektar codecs.
Virtual midi patchbay software#
I was hoping to build the software to be non midi hardware specific and allow multiple midi hardware devices be connected together to form large remote mappings and by managing the mapping in the software instead of the remotemap, allow for more customisable maps. There will be other things to consider like the throughput of the virtual midi cables, the process time of the software and any midi hardware also connected to the software. However, if it would take say several minutes to send large blocks of data, then the software would need a different design to get optimised performance. If the remote system can send large blocks of data to cover for example every remotable item in the master mixer in say under a second, then the software can load an initial snapshot of all parameters on device focus and then the software manage the mappings. The automap software has a limit of 256 buttons and 256 pots but no delta encoders and some devices in the rack have over 700 remote items while the master mixer has over 5000 remote items. This is a little like the native instruments NKS project but for Reason Remote and coded a little like the Novation Automap software as far as the codec/maps are concerned. Thanks for getting back to us, the reason I ask these questions is I am looking to write a virtual midi controller, that provides speech feedback of mapped parameters. Remember to set up a default template with your routings. I am sorry I do not know more techy stuff to tell you. I did not know there was none, but 1 mb is huge in midi terms. I use a midi patchbay to distribute clock. You can only send clock to one midi source from reason. I use and control hardware from reason without any issues.
I didn't find any info for this in the sdk, is their any other documentation on the remote system anywhere else?
Has anyone done any timed testing of the remote system? I know there is a 1mb size limit on the length of sysex messages but how many sysex messages can be sent per second from Reason, does the size of sysex message affect the speed? How many general midi messages like note/cc data can be sent and recieved per second?ĭo midi messages get sent in batches from reason? If so is this based on sample rate or system time or midi clock? What is the max speed and volume of midi data reason can receive per second?
0 kommentar(er)
