I used Mux for a live performance the day before yesterday. That this live performance works, I used the old version of mux and set the plugin delay output to zero. I could then live turn on the signal chain with a dry wet knob and used the plugin delay as a delay feature. All my other tracks are keeping the zero latency.
So my QUESTION: How can I again manually set the Plugin delay and switch off the APDC? I didn‘t find it out by trying and reading in the online manual.
MuLab 8.4.18 (APDC)
-
- KVRer
- 12 posts since 29 Jan, 2016
-
- KVRAF
- Topic Starter
- 13863 posts since 24 Jun, 2008 from Europe
I'm not sure if i can follow. Which VST is causing latency and why do you want the other signals to be out of sync with that VST? If you're after a real audio delay, as an effect, then use one of the delay modules. Sorry if i'm missing something.
-
- KVRer
- 12 posts since 29 Jan, 2016
I programmed a complex shepard glissando Patch in Mux with two Pitch Shifters which are causing a big amount of delay.
I performed live with a Cello and a Pianist. These two instruments went into my Audiointerface wich was connected to a computer with Cubase.
The Instruments are causing a Reverb in Cubase, wich is routed to the Mux Patch with the big Latency. I set the Mux Patch to zero Latency, that it doesn‘t report to the DAW. With this trick I was able to work latency free with the instrumentalists. The Delay of the Mux Patch is like a Predelay, because Reverb is routed im it.
Sorry for my bad English. But for me, as I am using Mux live, it is importent that I have control over the Latency. With that I could do a lot of cool tricks and it is also fun to experiment with the Latency. Reason also has the feature that you can deactivate Plugin delay compensation.
I would really appreciate if you could add the function to also manually control the latency again. It would be not that big deal to you as a programmer, wouldn’t it?
I performed live with a Cello and a Pianist. These two instruments went into my Audiointerface wich was connected to a computer with Cubase.
The Instruments are causing a Reverb in Cubase, wich is routed to the Mux Patch with the big Latency. I set the Mux Patch to zero Latency, that it doesn‘t report to the DAW. With this trick I was able to work latency free with the instrumentalists. The Delay of the Mux Patch is like a Predelay, because Reverb is routed im it.
Sorry for my bad English. But for me, as I am using Mux live, it is importent that I have control over the Latency. With that I could do a lot of cool tricks and it is also fun to experiment with the Latency. Reason also has the feature that you can deactivate Plugin delay compensation.
I would really appreciate if you could add the function to also manually control the latency again. It would be not that big deal to you as a programmer, wouldn’t it?
-
- KVRAF
- Topic Starter
- 13863 posts since 24 Jun, 2008 from Europe
Those Pitch Shifters are VST plugins, right?modularreason wrote: Sat Feb 22, 2020 4:18 pm I programmed a complex shepard glissando Patch in Mux with two Pitch Shifters which are causing a big amount of delay.
Which VST plugins?
And if you right-click that pitch shifter VST and do "Show Info" then what's the initialDelay value of it?
-
- KVRer
- 12 posts since 29 Jan, 2016
Just in the case, you didn't understood me. The latency correction works. The delay is right. I just want to set the compensation off, that Mux doesn't report latency to my DAW. Mux was the only way for me to do that for individual plugins. The new APDC works perfect, I really like it, but I wish, the manually option would still exist also.
I am using the Waves SoundShifter. I unrapped the Waves Shell to use it inside Mux and it works fine.
It reports a delay of 6946 Samples.
I am using the Waves SoundShifter. I unrapped the Waves Shell to use it inside Mux and it works fine.
It reports a delay of 6946 Samples.
-
- KVRist
- 388 posts since 28 Oct, 2002
Can I ask, how did you unwrap the waves shell?modularreason wrote: Sat Feb 22, 2020 6:12 pm
I am using the Waves SoundShifter. I unrapped the Waves Shell to use it inside Mux and it works fine.
It reports a delay of 6946 Samples.
-
- KVRer
- 12 posts since 29 Jan, 2016
Of course! I used the shell2vst Software. I noticed that it only works if I do it on the Desctop. Otherwise I get error messages. I am using Windows 10. And Waves V9. I think I did try it once with Waves V10 and it didn't worked.Can I ask, how did you unwrap the waves shell?
-
- KVRAF
- Topic Starter
- 13863 posts since 24 Jun, 2008 from Europe
modularreason, i spent many hours researching your request in detail. Conclusion is that it is less simple as you might expect. The only practical option i see is to add an option for VSTs to overwrite their reported latency. And to add an option to MUX Plug-In so you can overwrite the latency it reports to the host (the "initialDelay"). Maybe that will be added in a future version, but please understand that there are many hundreds of feature requests waiting for attention. For now, if you want to keep that same effect as in MUX 7, which is a consequence of MUX 7 not having APLC, then please use MUX 7 for that.
-
- KVRer
- 12 posts since 29 Jan, 2016
@Mutools:
Thank you very much for your support! This option where you can overwrite the Latency would be great.
I totally understand, that there are a lot of other user requests and thank you for your time.
Thank you very much for your support! This option where you can overwrite the Latency would be great.
I totally understand, that there are a lot of other user requests and thank you for your time.
-
- KVRist
- 149 posts since 31 Mar, 2017 from New Caledonia
Mutools wrote:
"The only practical option i see is to add an option for VSTs to overwrite their reported latency. And to add an option to MUX Plug-In so you can overwrite the latency it reports to the host (the "initialDelay")"
That's what I asked in page 2 of this thread. Hope this will be achieved in a future version. And many thanks to Jo for all the work about APLC.
"The only practical option i see is to add an option for VSTs to overwrite their reported latency. And to add an option to MUX Plug-In so you can overwrite the latency it reports to the host (the "initialDelay")"
That's what I asked in page 2 of this thread. Hope this will be achieved in a future version. And many thanks to Jo for all the work about APLC.
-
- KVRAF
- Topic Starter
- 13863 posts since 24 Jun, 2008 from Europe
-
- KVRist
- 149 posts since 31 Mar, 2017 from New Caledonia
you rock!
-
- KVRer
- 12 posts since 29 Jan, 2016
Wow, thank you so much!