Sysex in XT2 ?
- KVRist
- 443 posts since 13 Feb, 2006
yes, i understand.
what do you use to develop vst? do you think that i can make midi tools with synthedit?
what do you use to develop vst? do you think that i can make midi tools with synthedit?
-
- KVRAF
- 3948 posts since 8 Sep, 2003 from germany
This is mainly C++ in Visual Studio. Of course, you can do A LOT in synthedit if you prefer this , and this includes midi related plugins. Have a look at Nicfit's or soma's plugin collections and you'll see what's already been done as examples.
For an alternative solution there is also Synthmaker, but I haven't seen many midi plugins so far (it's noticably newer than SE though).
For help or links for those development environments also check out KVR's modular synthesis forum, I'm sure you'll find the right SE/SM geeks there.
For an alternative solution there is also Synthmaker, but I haven't seen many midi plugins so far (it's noticably newer than SE though).
For help or links for those development environments also check out KVR's modular synthesis forum, I'm sure you'll find the right SE/SM geeks there.
-
- KVRer
- 22 posts since 13 Nov, 2005
Thanks, great!plastique wrote: [Changes] 1.01:
- added volume setting (CC7) per slot
Feels much better...plastique wrote: - changed control behaviour (to 0-127 instead of 127-0)
But... to be picky ... The volume control should start from 127 since it's the default value in the synth.
Hmm... this might be disastrous if you forgot to activate the preset button. And my goal is to keep off the computer during performance. You don't have time to turn around from the master keyboard, finding the mouse pointer on screen and hitting the Preset switch. To prevent double-triggering, you could use a conditional statement. If initiation is not triggered and preset is enabled, then send messages on preset change.plastique wrote: - added "send values on preset change" option (not stored within preset/bank to prevent unintended value sending)
Much more intuitive now. great!plastique wrote: - changed MSB/LSB-swap button
This might be the plug that makes eXT THE plug host for contemporary live music performance. Because there's still no chance a professional keyboard player would rely completely on a vsti-based setup. There's always external gear!
You're doing myself and alot other keyboardists a huge favour when developing this plug.
Thanks!
Regards, Magnus
-
- KVRAF
- 3948 posts since 8 Sep, 2003 from germany
So you want it to default to 127 instead of "off" ? Which means a value of 127 will get sent (if the channel is set). If it is off (like now), no value is sent (no change).yatzy wrote: Feels much better...
But... to be picky ... The volume control should start from 127 since it's the default value in the synth.
Just reassuring
If you mean you'd like it to go from 127-0, I have to disagree, cause having those controls behave in different ways will just cause confusion sooner or later. I think one will be able to live with how it is right now
(on a side-note, for fine-tuning you can hold down SHIFT and the values will change a lot slower, or use mouse-wheel).
I'll see what I can do. Believe me, I tried a lot to get this right with setting different plugin load states, but couldn't get it to ignore sending even if these are set.yatzy wrote: Hmm... this might be disastrous if you forgot to activate the preset button. And my goal is to keep off the computer during performance. You don't have time to turn around from the master keyboard, finding the mouse pointer on screen and hitting the Preset switch. To prevent double-triggering, you could use a conditional statement. If initiation is not triggered and preset is enabled, then send messages on preset change.
I'll try to see if I not get it working for the next version update. For now I had to leave it like that.
Last edited by plastique on Mon Sep 04, 2006 2:04 pm, edited 1 time in total.
-
- KVRAF
- 3948 posts since 8 Sep, 2003 from germany
Well blimey, but it seems I got it right this time, using a different approach.
The plugin is not backwards compatible anymore as I had to extend the presets, but this should be a fair price to pay.
Also, as promised, you can now change presets also via PC messages if the according switch is enabled.
(changes and download url see one page before this one in the original announcement post)
The plugin is not backwards compatible anymore as I had to extend the presets, but this should be a fair price to pay.
Also, as promised, you can now change presets also via PC messages if the according switch is enabled.
(changes and download url see one page before this one in the original announcement post)
-
- KVRer
- 22 posts since 13 Nov, 2005
I'm sorry to say that I don't think so...plastique wrote:Well blimey, but it seems I got it right this time, using a different approach.
When I enabled PC and Init and sent a ProgCh to S-PC-Init, the preset was changed and program changes was sent according to the Init delay time.
The Preset switch and delay wasn't changing the behavior at all.
I saved the setup and restarted eXT, and this time it worked as intended...
Not too fool-proof at this stage... I'll try to recreate the bug and get back to you.
Super Trooper!!The plugin is not backwards compatible anymore as I had to extend the presets, but this should be a fair price to pay.
Also, as promised, you can now change presets also via PC messages if the according switch is enabled.
Regards, Magnus
(changes and download url see one page before this one in the original announcement post)
-
- KVRAF
- 3948 posts since 8 Sep, 2003 from germany
You probably didn't replace the plugin with the new version did you ?
And I mean, deleting the old one, and loading the new one .
That's what I meant about not being backwards compatible (as it can mess up with previously created presets).
Just load it new, and start building new presets.
And I mean, deleting the old one, and loading the new one .
That's what I meant about not being backwards compatible (as it can mess up with previously created presets).
Just load it new, and start building new presets.
-
- KVRAF
- 3948 posts since 8 Sep, 2003 from germany
And thanks to you for helping fine-shaping the plugin to a state where I can say also myself that it's got to a point where I am very happy about how it turns outyatzy wrote: You're doing myself and alot other keyboardists a huge favour when developing this plug.
Thanks!
I will close adding features now (to avoid future backward incompatibilities of the created presets) and concentrate on bug fixing. As far as I can tell there is only some host related stuff to figure out (samplitude plugin resizing for example), but something not high on priority since it's not the plugin's fault, but maybe I find some workarounds.
-
- KVRer
- 22 posts since 13 Nov, 2005
Nooooo! Just one more:plastique wrote:I will close adding features now...
When changing preset via PC the preset list on top of the window is not changed.
So If I named one preset "001-Verse 1-Like a Prayer" and the next "002-Verse 2-Like a prayer" the preset list will not reflect what's actually loaded...
I suppose this is a VST behavior since all VST plugs acts like this.
It would therefore be great if you could add a title row at the top of the plugin that shows the currently loaded setup. It could be truncated with an elipsis, (that's the name of the three dots "002-Verse 2...") if it doesn't fit in the plug window.
This might be a good feature to have sorted out already now since it might be useful in later plugs developed by you as well...
Regards, Magnus
-
- KVRAF
- 3948 posts since 8 Sep, 2003 from germany
I said I close adding of features apart from useful ones, didn't I

Finally fixed the sending of presets (I guess), which turned out to be a genuine bug after all, which only happens after newly inserting the plugin so was rather difficult to track down. Let me know if there are still weirdnesses .
Initial post updated again.
Finally fixed the sending of presets (I guess), which turned out to be a genuine bug after all, which only happens after newly inserting the plugin so was rather difficult to track down. Let me know if there are still weirdnesses .
Initial post updated again.
-
- KVRer
- 22 posts since 13 Nov, 2005
Well, you asked for it...plastique wrote:I said I close adding of features apart from useful ones, didn't I![]()
The possibility to copy&paste presets.
Like two buttons to the left of the "+" button.
I just caught myself pushing the program change buttons on my synth in a completely manic way, just to see the S-PC-Init panel changing size rapidly, depending on the preset setup... It was a blast!
Yes, I'm loosing it...
Regards, Magnus
-
- KVRAF
- 3948 posts since 8 Sep, 2003 from germany
I'll think about ityatzy wrote: Well, you asked for it...Here's another one:
The possibility to copy&paste presets.
Like two buttons to the left of the "+" button.
It's no "must-have" feature but definitely a "nice-to-have" one.
For now you can just save/load fxps with the host for C/P presets.
- KVRist
- 443 posts since 13 Feb, 2006
is it possible to add other midiout ports? like in the xt sequencer or in the soma's midi swithcer... it's useful when different machines or vst are working on the same midi channel but connected to different ports.
-
- KVRAF
- 3948 posts since 8 Sep, 2003 from germany
No, not possible with the current vst specification (only allows one midi in- and output per plugin). What the seq does is internal to eXT and soma's midi switcher is only using one port as well as far as i can see (internally routing, but channels, not ports).
-
- KVRAF
- 3948 posts since 8 Sep, 2003 from germany
updated (for changes see original post on page 2).plastique wrote:I'll think about ityatzy wrote: Well, you asked for it...Here's another one:
The possibility to copy&paste presets.
Like two buttons to the left of the "+" button.
It's no "must-have" feature but definitely a "nice-to-have" one.
For now you can just save/load fxps with the host for C/P presets.
