help to send sysex messages

[222]

help

vst version not send sysex

[222]

help to change the vst form
i like a buttons to select panel: lower o upper

[oddson]

I'm having trouble too... I can't get it working even within SynthMaker. The sysex primitives are responding as expected.
Anyone else verified they work under the most recent versions?

[222]

help

[trogluddite]

I'm having trouble too... I can't get it working even within SynthMaker. The sysex primitives are responding as expected.
Anyone else verified they work under the most recent versions?

No problem here from within the SM application or when exported as .exe's. I tested using a MIDI cable routed between hardware in and out. The only quirk that I found is that it's essential to use to use the trigger output on the Sysex-to-String, as the string output sends no triggers of its own.

No joy at all in Reaper though - I've tried various combinations of sending and receiving using VST exports with no joy at all. There's the odd flicker of a 'signal present' indicator when transmitting, but no recognisable messages. The receiver plugin gets nothing, even if I insert a SysEx message into a track by hand.
Nothing in VSThost either - even with transmit and receive plugins chained directly together.

Not been using Reaper too long, so that could be just me missing a vital setting (all of the filtering options I have found are cleared) - but VSThost has been my standard test-bed for a long time now, so I'm pretty confident that the plugins are to blame for the lack of MIDI data.

[222]

this is a new bug ?

[trogluddite]

Not sure, seems that most of the SysEx designs I've seen communicate directly to the hardware rather than through a host.

I had a little dig around on the net (searched for 'SysEx VST plugins') - and found quite a few discussions about using SysEx with VST plugins (not just SM). I get the impression from what I've read that there are some limitations due to the VST specification itself, so it could be that it's not possible to use SysEx with any VST plugin.

Probably best to send an e-mail to admin@synthmaker.com, and ask the developers - if there is some reason why VST's are unable to do SysEx, I'm sure they would know.

[DigitalWhiteByte]

Was one of my primary research at the beginning I used synthmaker,
and came to the conclusion that communication is possible only by sending the sysex data to an external midi port, directly by the plugin.
The reasons for not having a full MIDI support, was that the host, until recently,
were not developed with the support of sysex, but now the vast majority of its users.
It would be the case, to have a full midi support based on samples as per specifications sdk,
and the remaining messages not yet present, those realtime etc..

[222]

synthmaker support full sysex for vst ?

[DigitalWhiteByte]

Synthmaker support sysex messages even when it is exported as a VST,
does not seem to successfully send messages through the internal routing host. If you need to send sysex messages,
for an external equipment synthmaker can do this by connecting directly to the midi port where you have your own equipment, except that that port may not be available for hosts, unless you have a midi card multiclient .

[222]

problem, not save the preset of a float
panel selector uses a counter to change waveform