MUX Vst : What do you need?

[Robert Randolph]

Also, I can't get my head around the delay times. Why are they in 24ths, not 16ths/8ths etc?

Because this give you more rythmical options, while 16ths (=6/24ths) and 8ths (=12/24ths) are still possible.

I haven't played with the echo much yet, but that labeling would not be musically correct. Even though there's no such thing as 24th notes, they would be called 16th note triplets. That yields 24 notes in a measure.

Thusly:

24 = whole note

18 = dotted half note

12 = half note

8 = half note triplet

6 = quater note

4 = quater note triplett

3 = eighth note

2 = eighth note triplet

1.5 = 16th note (not possible in the echo that I see)

1 = 16th note triplet

----

If 6 is giving 16th notes, then it's mislabeled or ambiguous.


EDIT It seems to be labelled in 24ths of a quarter note. That would be "96ths notes", assuming that was acceptable terminology

I guess it could be 24th's of some other timing mechanism such as ppq or whatnot? It would be nice if it was more clear.

Sorry for the sidetrack.

[> DiGiT <]

what do you think of the aux midi/audio input idea jo?

[MuTools]

To be honnest i don't understand it.

[robenestobenz]

I think marquee selection (or at least multiple selection) should be in the first release. Some method of multi select is a pretty fundamental feature in any software. Having such a powerful modular system in a host is a big bonus, so it's easier to look past this. In Mux standalone, the modular system is the main stage, the entirety of what customers have paid for, and so I think it should be in there.

[MuTools]

Note that it's not about an easy thing. It may sound easy but there are some complications: As soon as we're able to multiselect modules, the user also wants to drag-drop / cut-copy-paste these modules and the relevant connections between them. And i got some work to do there. If 1.0 would be postponed for that, it will be postponed for a serious time. I don't want that. About users having paid for good value: Note that users who buy a MUX Vst 1 user license will get a free upgrade to MUX Vst 2! Same as for users who bought a MuLab 4 UL user license, they'll gete a free upgrade to MuLab 5 UL. So you can step into the game, enjoy it immediately and then you'll get many extras lateron!

[Juan Mendoza]

Also, I can't get my head around the delay times. Why are they in 24ths, not 16ths/8ths etc?

Because this give you more rythmical options, while 16ths (=6/24ths) and 8ths (=12/24ths) are still possible.

true, but i also agree that labeling it in 24ths is a bit (if not a lot) confusing!
Specially if you're used to more standard divisions and just want quick, inmediate access to your favourite delay tempo settings without having to make some math exercise.

Same applies for the tempo synced LFO that is expressed in Cpb, sure it's the most correct way to express it, but i miss inmediate acces to regular tempo divisions like 1/2 1/3 etc.

[robenestobenz]

Note that it's not about an easy thing. It may sound easy but there are some complications: As soon as we're able to multiselect modules, the user also wants to drag-drop / cut-copy-paste these modules and the relevant connections between them. And i got some work to do there. If 1.0 would be postponed for that, it will be postponed for a serious time. I don't want that. About users having paid for good value: Note that users who buy a MUX Vst 1 user license will get a free upgrade to MUX Vst 2! Same as for users who bought a MuLab 4 UL user license, they'll gete a free upgrade to MuLab 5 UL. So you can step into the game, enjoy it immediately and then you'll get many extras lateron!

Don't get me wrong, I have no doubts that MUX will be excellent value for money. I just think that this is something users will expect, and that will probably harm first impressions. Not a lot, but a bit.

Whether or not it's in on day one, I'll still be buying the first release!

[> DiGiT <]

To be honnest i don't understand it.

ok here goes.

i use native instruments maschine. you can send only 1 channel of midi to any vst, making it impossible to use the vst multitimbrally. thus the need for an auxillary midi input. just one of those would defeat the limitations of maschine and allow you to use fully the multitimbral capability of mux vst and any vst loaded inside mux vst. all you would need is a 'midi patch point plugin' that reroutes midi to the mux vst that is loaded on an adjacent track in maschine... this would eliminate the need to load multiple instances of mux vst. im sure theres another host out there where this would be useful.

an audio 'patch point' would be useful in many ways to a modular environment... like the forementioned 'side chain' duty, among other uses. this is pretty self explanatory. as an example, the plugin 'fxpansion geist' uses what they call a 'spitter plugin' that routes audio from anywhere in the vst signal chain within the host DAW to geists internal sampler/resampler.

[MuTools]

I'm still not sure that i understand. Note that the MUX in MuLab can have as many audio/event/modulation inputs + outputs as you want. The MUX Vst however will have 1 MIDI input and 1 MIDI output (VST 2.4 limitation) and 2 stereo audio inputs and 4 stereo audio outputs. I read in your post that you want more than 1 MIDI input for the MUX Vst. That's not possible.

[> DiGiT <]

not possible? i would think that anything is possible in the world of software. are you thinking outside the box as they say?

oh well. ok then aux audio inputs not possible too? that cant be right since geist clearly does it. how will you achieve side chaining in vst environment where there is no modular patch architecture?

you dont understand me? why dont you understand me? is it the words i choose? i dont understand why you dont understand me. others seem to understand what i write perfectly well. how can i make it even more simple?

[AndreasD]

About the Delay times:

24/24 = 1 Beat(!!)=1/4 note
12/24 = 1/8 note
9/24 = 3/16 note
6/24 = 1/16 note
96/24= 1 full note

[Caco]

I'm still not sure that i understand. Note that the MUX in MuLab can have as many audio/event/modulation inputs + outputs as you want. The MUX Vst however will have 1 MIDI input and 1 MIDI output (VST 2.4 limitation) and 2 stereo audio inputs and 4 stereo audio outputs. I read in your post that you want more than 1 MIDI input for the MUX Vst. That's not possible.

I think > DiGiT < would like additional VSTs that can communicate directly with the MUX VST even if they are not connected together. Imagine having a special VST on one track that receives audio/midi and then passes it directly into the MUX VST on a completely different track via shared memory/static data/tcp/ip/udp etc in the plugins rather than through its standard audio/midi inputs.

[janamdo]

(VST 2.4 limitation) and 2 stereo audio inputs and 4 stereo audio outputs. I read in your post that you want more than 1 MIDI input for the MUX Vst. That's not possible.

I read that steinberg has a VST 3.5 ..how about VST 2.4 is this not outdated?

[Robert Randolph]

(VST 2.4 limitation) and 2 stereo audio inputs and 4 stereo audio outputs. I read in your post that you want more than 1 MIDI input for the MUX Vst. That's not possible.

I read that steinberg has a VST 3.5 ..how about VST 2.4 is this not outdated?

The VST 3.x spec is not fully supported, and it's a HUGE pita to use (often because it's not supported fully in most hosts).

There are ways to get around the 1 midi I/O problem though. Whether or not they are viable in develop is up to Jo.

[> DiGiT <]

oh really? you mean jo calls shots around here? when did you get here? are you tellin me that hes the big cheese? thanks, after a few years using mboom, muzys and now mulab i wasnt sure who was in charge. but you cleared it up for me and now there is no mistake. thanks brah.