Vienna Symphonic Library Forum
Forum Statistics

194,379 users have contributed to 42,916 threads and 257,956 posts.

In the past 24 hours, we have 2 new thread(s), 4 new post(s) and 77 new user(s).

  • Feature Request - MIR bypass button

    Ok, I think I wrote about this before, but at the risk of sounding redundant I have to ask again. Am I the only one who thinks that a per VEP instance "MIR bypass" button would not be hugely helpful? It would be just awesome to be able to disable all the instances of MIR on a given VEP instance and re-enable with one click. As it is I have to CTRL-click click click click click click click click click click click click click click to disable, (thereby reducing latency of the instance), and then CTRL-click click click click click click click click click click click click click to re-enable. All instances of MIR have to be disabled for the latency time to get reduced.

    I can't help thinking, (with my very limited understanding of programming) that it shouldn't be that hard or expensive to implement, and at least for me it would be a massive time saver. Perhaps I'm the only person who works the way I do, in which case I suppose I'll just have to suffer it, but I can't help but think this would be useful to more than a few people.

    If you agree please +1 this post or comment so maybe they'll see I'm not the only one!????

    Just so I don't sound ungrateful, I take this opportunity to again say thanks for such amazing great software and libraries VSL, it would be a sad world for me without it... just hope you can do this one feature - it would be unbelievably fantastic!


  • You're absolutely right. Personally I think that switching plugins (and internal processes like MIR Pro) on and off in VE Pro should support Selection Groups.

    I'll put it on the wish list (... it's quite possible that it's there already, BTW. :-) ...) Thanks for your input!


    /Dietz - Vienna Symphonic Library
  • Not (yet) being a MIR user, I couldn't comment on this either way, but I wondered about a similar thing for some of the VI controls.

    Would it be feasible for each VE instance to have master on/off switches along its top panel for all the VI instances contained within? So one button for VI built-in convolution reverb on/off, one button for velocity crossfade on/off, one for optimise off/learn/enable. So you'd press this one button, and instantly change the settings for all VI instances contained within that VE instance, which (I think) would be great for quickly changing settings to A-B between options, or for immediate deactivation of reverbs/optimising of samples when CPU limits start to loom. Obviously these parameters could also be controlled individually within each VI track, the new buttons would simply be master on/off switches (rather like each VI track has a velocity crossfade on/off button, but this can also be specified individually at the cell level).

    I hesitate to mention it, as it might be a step too far, but what about a universal velocity crossfade slider for each VE instance? I doubt it would sound that great on a final product, to have the entire orchestra crossfading exactly in unison, but it might be handy when sketching initial ideas.

    Just my thoughts, for all I know there's a much easier way to do all of the above already in place, and I just haven't found it yet.

    Pyre

    AMD Ryzen 7 3700X 8-Core 3.59Mhz Processor, 64 GB RAM, Windows 10.0.19045, Cubase 10.5.20, Sibelius 7, VEP 5.4.16181, VIP 2.4.16399, Symphonic Cube, MIR Rooms 1-5, Suite, Choir, Organ, Imperial, Solo Voices, Dimension Strings, Historic Winds, World Winds
  • Thanks for the reply Dietz, that's great news :) Yes I think it's the only feature I would say is missing right now.

    I wouldn't say you need to have bypasses for other individual plug ins such as normal reverbs or eq's, no other hosts have that feature and it isn't really necessary in most cases, especially as those don't introduce latency for the most part, and if they do it's very little in most cases - even multiband compressors don't introduce much latency and most people won't be using those on every single channel or even many channels. But MIR is another thing. For me when I'm performing parts I need that to be snappy especially fast string lines or anything really. So MIR has to be disabled so you can hear things in low latency, then renabled so you can hear how it sounds in the mix, etc. For me at least it becomes a real issue over time.