Improvements!

[Bronto Scorpio]

Another small suggestion:

When inserting an MSEG as a modulation source in Zebra, it would be nice if the lower panel would automatically switch to that MSEG.

Cheers
Dennis

[Urs]

Another small suggestion:

When inserting an MSEG as a modulation source in Zebra, it would be nice if the lower panel would automatically switch to that MSEG.

Cheers
Dennis

True. But it does jump there when you click the knob...?

[Bronto Scorpio]

Another small suggestion:

When inserting an MSEG as a modulation source in Zebra, it would be nice if the lower panel would automatically switch to that MSEG.

Cheers
Dennis

True. But it does jump there when you click the knob...?

It does!

I never noticed that! I always manually opened the MSEG pane before adjusting the modulation amout. How could I not notice that for so long?

In that case it's good as it is now

Cheers
Dennis

[3ee]

Another small suggestion:

When inserting an MSEG as a modulation source in Zebra, it would be nice if the lower panel would automatically switch to that MSEG.

Cheers
Dennis

True. But it does jump there when you click the knob...?

Can clicking/selecting an OSC module for example have the same behavior?
I always confuse which osc tab I'm tweaking when working with multiple oscs.

[Urs]

Another small suggestion:

When inserting an MSEG as a modulation source in Zebra, it would be nice if the lower panel would automatically switch to that MSEG.

Cheers
Dennis

True. But it does jump there when you click the knob...?

Can clicking/selecting an OSC module for example have the same behavior?
I always confuse which osc tab I'm tweaking when working with multiple oscs.

It works for the MSEG because it's a ModSource. I could probably add a similar behaviour to the Grid when clicking an Osc...

[Trahast]

Can clicking/selecting an OSC module for example have the same behavior?
I always confuse which osc tab I'm tweaking when working with multiple oscs.

It works for the MSEG because it's a ModSource. I could probably add a similar behaviour to the Grid when clicking an Osc...

A great idea. + a bunch!

Cheers,
Trahast

[3ee]

Another small suggestion:

When inserting an MSEG as a modulation source in Zebra, it would be nice if the lower panel would automatically switch to that MSEG.

Cheers
Dennis

True. But it does jump there when you click the knob...?

Can clicking/selecting an OSC module for example have the same behavior?
I always confuse which osc tab I'm tweaking when working with multiple oscs.

It works for the MSEG because it's a ModSource. I could probably add a similar behaviour to the Grid when clicking an Osc...

That would be great! thanks

[Tom Drinkwater]

It seems that DIVA is always in omni mode is that right? ie it just ignores what channel input comes in on and treats it as if it was all on one channel.

It would be really good if instead of that, if when I play a note on one channel, and then the same note on another channel, that it would play a new instance of that note, and keep the CC data separate too.

This would allow multiple instances of the same note with different expression, something possible on many stringed instruments, but not on most synths, even with PolyAT.

It would also allow a PolyAT like modulation to occur, but using regular CCs if the incoming notes were assigned to different channels (before they arrive in DIVA) and better still this per note expression would not be limited to one dimension but could use the full range of CCs.

This would be sort of like having a separate instance of DIVA for each channel, but without the overhead, and in what I am suggesting all channels would play the currently selected patch, glide would work between channels within the one instance of DIVA.

If all input was all on one channel it would behave the same as it does now, so the feature could be always on, and people not needing it would be unlikely to have any problem.

[Arrested Developer]

A little question/suggestion for Zebra:

When choosing "user mode" for an LFO, is there a possiblity to zoom the little window, without zooming the whole zebra-GUI?
This would be great!
(sorry, if it's possible anyway, couldn't find it in the manual....)

[EvilDragon]

I'd really like some sort of shortcut for removing a module from the grid... Alt+click should be good (Shift+click being bypass).

[#rob]

It seems that DIVA is always in omni mode is that right?

Yes, that's right.

You can usually control in your host software which channel is forwarded to the plugin, so you can set up Track #1 with Diva instance #1 listening on all MIDI channels and Track #2 with Diva instance #2 listening on all MIDI channels, then set the host to send only MIDI channel 1 to Track #1 and send only MIDI channel 2 to Track #2, for example.

That way, Diva instance #1 will only receive messages from MIDI channel 1 and Diva instance #2 will only receive messages from MIDI channel 2, even though both instances are -theoretically- listening to all channels.

[Arrested Developer]

A little question/suggestion for Zebra:

When choosing "user mode" for an LFO, is there a possiblity to zoom the little window, without zooming the whole zebra-GUI?
This would be great!
(sorry, if it's possible anyway, couldn't find it in the manual....)

I still would be interested in an answer...

[Tom Drinkwater]

It seems that DIVA is always in omni mode is that right?

Yes, that's right.

You can usually control in your host software which channel is forwarded to the plugin, so you can set up Track #1 with Diva instance #1 listening on all MIDI channels and Track #2 with Diva instance #2 listening on all MIDI channels, then set the host to send only MIDI channel 1 to Track #1 and send only MIDI channel 2 to Track #2, for example.

That way, Diva instance #1 will only receive messages from MIDI channel 1 and Diva instance #2 will only receive messages from MIDI channel 2, even though both instances are -theoretically- listening to all channels.

I know all this, but it has little to do with my post. I'm interested in getting plugins to do stuff that is musically useful but not properly supported by MIDI. multiple instances of the same note in the same synth is one of those as described in my post.

Another thing I'm very interested in is per-note expression. Midi only supports one stream of this with PolyAT. VST3.5 supports note expression, but is itself not well supported by hosts or plugin makers.

The workaround for instruments that produce multiple streams of per note expression (like eigenharp, or touchkeys http://www.eecs.qmul.ac.uk/~andrewm/touchkeys.html) is usually to split each note off onto a separate channel and send regular midi CC s to that channel, and they act per note since only one note is playing on each channel.

The catch with this is that you need a separate instance of the plugin for each note of polyphony, and that duplicates overhead for no good reason, as well as creating a clutter in the DAW. It also breaks things like glide.

It would be great if U-he and other synth makers were to implement a way of dealing with this. More and more instruments are going to start being made that create polyphonic per note expression, and current synths are not ready for that.

However, Diva responds fine to PolyAT, so there's obviously no major barrier to per note expression in the code. The barrier is in the Midi spec.

I would like to suggest that U-he (and others) start including a midi interpreter for the split channel polyphony with per note/channel CCs I described. The code would be fairly simple, but it has to be in the plugin, it isn't something we can hack from outside, except by using multiple instances of the plugin.

clear as mud?

PS this is all in the context of a single patch receiving midi from a single polyphonic performance. there's no multimbrality or anything.

[Urs]

Hi Tom,

What you describe is pretty much exactly what we have in mind. We're going to listen on individual MIDI channels, and have each channel have its own MIDI controllers. This will be regardless of poly/mono/duo settings. In Legato mode for instance you'll have up to 16 monosynths with the same patch. In poly mode you'll get 16 voices dynamically assigned to those 16 channels.

Nevertheless, our curent focus is AAX, then Diva 1.3 then Bazille. Until then we do not know exactly what's next and when.

Cheers,

- Urs

[hakey]

our curent focus is AAX

I know this is a business decision made for sound commercial reasons and the rest, but heres to wishing a plague on bloody Pro Tools and all of their customers!