Why does Instrument X need a custom editor?

Synthesizer V Studio
1

There does not seem to be a category for Instrument X yet - sorry if this post is in the wrong place…

First, I do agree that I personally would prefer Dreamtonics focusing on better vocals and more vocal features (growls and “dirty” blues voices, speaking, more languages) rather than venturing into new instruments.

But now that they have done so, I would love to understand why Instrument X uses its own editor, and if that is really necessary. From my perspective, I understand why Synth V needs a custom editor - the overall vocal features such as lyrics cannot easily be expressed by using midi controller data from a standard Midi editor. For instrument X, however, it seems that much of the performance could be driven by mapping midi controllers to the parameters in the editor? I would GREATLY prefer that to having yet another editor that requires me to make arrangement changes in yet another additional place. For vocals, I am willing to jump through that hurdle because I can’t get vocals otherwise - but for an instrument or orchestra, I am not sure that this is a trade-off I am willing to make, especially if it feels unnecessary.

Any thoughts on this?

Thanks!

1 Like
2

A VSTi plugin can only receive real time MIDI data from the host DAW as it’s being played.
Both Synthesizer V Studio 2 Pro and Instrument X pre-render their outputs prior to playback, which makes them unsuitable to receive MIDI data directly from the DAW.
Additionally, detailed articulation information could not be easily added on top of the MIDI data, requiring a workaround that could possibly not be intuitive, and would risk falling out of sync with the underlying MIDI notes.
One of the highlights for Instrument X is that it doesn’t use key switches for articulations. Other virtual instrument plugins do use them because they use real time MIDI data, and articulations cannot be naturally expressed within the MIDI protocol.

2 Likes