From the original SynthMaker forum (2004–2014), with its members’ names and dates.
jorge ·
Here's an example of sending and receiving sysex messages:
[old link]
The float output of the knob is converted into two 7 bit values which are then converted to a hex string. A sysex message is then created as F0+header+hex value+F7. The message is then sent through the MIDI Out component.
On the receiving side the relevant information part of the sysex message is extracted and converted to a float value if and only if the header of the message matches the required ID. The header is defined from a combination of the required manufacturer Id and parameter Id.
It should now be possible to create a GUI in synthmaker to control external hardware or even a synth running on another computer.
Nu Audio Science ·
Thanks for this Jorge
Very useful very very ueful
Trying to create a controller for my MKS50 at the moment
NAS
Acrobat ·
Nu Audio Science wrote: Thanks for this Jorge
Very useful very very ueful
Trying to create a controller for my MKS50 at the moment
NAS
I have an AlphaJuno-1 which shares the same sysex messages! IF can I help you in any way, let me know!
A.
Nu Audio Science ·
Have you already created a control VSTi for it ?
Acrobat ·
Nu Audio Science wrote: Have you already created a control VSTi for it ?
No...but I can arrange a good GUI/interface for a PG-300 emulation in SM, for example... 😉
Nu Audio Science ·
I think a pg300 emulation would be pointless
For instance the Alpha ranges envelope could be displayed as a multipoint
Acrobat ·
Nu Audio Science wrote: I think a pg300 emulation would be pointless
For instance the Alpha ranges envelope could be displayed as a multipoint
Sure, fidelty to the the old Roland interface is not necessary...
malc ·
Hey, look who's back in town! 🙂
Hope all is well NAS.
Nu Audio Science ·
Yep back and looking forward to messing with SM
NAS
Tom7777 ·
Welcome back NAS 😀
Wrote something here? To have a post removed or your name hidden, write to [email protected].
SynthMaker