[LAU] [Bulk] Re: Korg microStation editor and Wine

[Ralf Mardorf]

On Sat, 13 Dec 2014 22:12:23 -0500, jonetsu at teksavvy.com wrote:
> On Sun, 14 Dec 2014 03:56:16 +0100
> Ralf Mardorf <ralf.mardorf at rocketmail.com> wrote:
> 
> > On Sat, 13 Dec 2014 21:42:21 -0500, jonetsu at teksavvy.com wrote:
> > > What would a VST plug-in editor offer more ?  Would I be able to
> > > sequence the changing of sound parameters for instance ?
> > 
> > I don't know if Linux sequencers support VST editor automation. As I
> > already pointed out, I used automation for editors, when I used the
> > Atari ST as sequencer.
> > 
> > 1. Atari ST MIDI is hard real-time, since the rout from hardware to
> > software is directly (no protocols from a to b, as for modern
> > computers) and no multi-tasking is involved, IOW real-time abilities
> > were much better these days.
> 
> OK, now I see what you meant.  Vielen Dank.

Are you sure?

For example data entry for the DX7 could be assigned to a parameter and
for the Matrix-1000 control change also could edit parameters, that
usually are only available by SysEx. IOW to edit all parameters you
usually need to use SysEx, but SysEx data isn't real-time data,
anyway, sometimes it's possible to assign a few real-time control
changes to parameters, or at least a data entry, to manipulate one
parameter by control change instead of using SysEx.

But it's important to be aware that e.g. the real-time pitch bend data
or after touch data does cause much more traffic, then very short
non-real-time SysEx data for a single parameter, that even doesn't send
a check sum, while a complete sound bank is much data + a check sum.

IOW you should test 1. if a VST editor can be used with a Linux
sequencers automation and 2. if so, if it can be used in real-time.

You also should read what parameters could be used by control change
real-time data by your synth.