The built in MUX plug in offers several effects, e.g.
1) Leveller: is this the same as an compressor or limiter ?
2) parametric EQ: Is there only one channel ? , must I cascade several plug ins for more channels, or should I add further components in the deep editor view ?
3) some examples for the typical use of the other effects ?
Mostly I use external plug ins, like the "classic" series,
but this won't be necessary if build in functions could be used instead.
questions to built in MUX effects
-
- KVRAF
- 13863 posts since 24 Jun, 2008 from Europe
No, it just affects the level, just like a volume slider.Eggu wrote:1) Leveller: is this the same as an compressor or limiter ?
But this one can tweak the level more drastically.
It's indeed about a single frequency band.2) parametric EQ: Is there only one channel ? , must I cascade several plug ins for more channels, or should I add further components in the deep editor view ?
But you can easily build a MUX patch that contains multiple parallel frequency bands if you want.
Euh, aren't they self-explanatory?some examples for the typical use of the other effects?
If not feel free to ask more about a specific MUX patch.
NB: I've added a note to the (m3) whishlist that each patch can contain specific info about it. Then in the context menu "Show Patch Info".
-
- KVRist
- Topic Starter
- 152 posts since 15 May, 2009 from Germany
Sure, in principle self-explanatory.Mulab wrote:Euh, aren't they self-explanatory?
I'm not so experienced in use of all these effects.
Which are typically used for mastering,
which for correcting bad tracks, which for special effects.
Everything should be made as simple as possible, but not simpler!
-
- KVRAF
- 13863 posts since 24 Jun, 2008 from Europe
-
- KVRAF
- 7412 posts since 8 Feb, 2003 from London, UK
Even ignoring "Synths" and "Effects", there's rather a lot to cover! I'll skim down the list.
In summary, you don't use a single plugin inside MUX to do anything. You create a MUX patch, which you then use for mixing or mastering, depending what you created it to do. The patch would expose the important parameters you wanted to tweak.
First section
All Pass Filter: usually used to colour a sound as an effect. Here it appears to include a delay (not something I've seen before).
The next few are echos and are used to create time-delayed copies of a signal overlaid onto the signal. (I guess a "pure" delay would split.)
As the echos are mono, the first section includes stereo splitter/combiner routing tools.
Second section
Rack, Mixer strip and Send are obvious. Patch point is just that - lets you wire many wires in and out.
Test Sine Generator: not getting any sound out? Well patch this in and work back from the audio out until you find your break.
Event Monitor: not getting any sound/MIDI out? Well patch this in and work forward from the Event in until you find your break.
Third section
Synthy bits. Sound sources.
Fourth section
Sound mangling and amplification. Not sure exactly what the balancers are meant for but they look fun. The limiter isn't exactly the classic interface, either but looks rather interesting. (I'm glad I'm looking more closely...)
Fifth section
"CV" generators. Control signals to be routed to other plugin's parameters. Mod Mapper looks like a CV "compressor".
MIDI Channel Splitter and Note Modifier do simple things to MIDI events.
Sixth section
Additional input and output patch points.
In summary, you don't use a single plugin inside MUX to do anything. You create a MUX patch, which you then use for mixing or mastering, depending what you created it to do. The patch would expose the important parameters you wanted to tweak.
First section
All Pass Filter: usually used to colour a sound as an effect. Here it appears to include a delay (not something I've seen before).
The next few are echos and are used to create time-delayed copies of a signal overlaid onto the signal. (I guess a "pure" delay would split.)
As the echos are mono, the first section includes stereo splitter/combiner routing tools.
Second section
Rack, Mixer strip and Send are obvious. Patch point is just that - lets you wire many wires in and out.
Test Sine Generator: not getting any sound out? Well patch this in and work back from the audio out until you find your break.
Event Monitor: not getting any sound/MIDI out? Well patch this in and work forward from the Event in until you find your break.
Third section
Synthy bits. Sound sources.
Fourth section
Sound mangling and amplification. Not sure exactly what the balancers are meant for but they look fun. The limiter isn't exactly the classic interface, either but looks rather interesting. (I'm glad I'm looking more closely...)
Fifth section
"CV" generators. Control signals to be routed to other plugin's parameters. Mod Mapper looks like a CV "compressor".
MIDI Channel Splitter and Note Modifier do simple things to MIDI events.
Sixth section
Additional input and output patch points.
Last edited by pljones on Mon Aug 31, 2009 8:37 pm, edited 1 time in total.
-
TheGuysanIdiot TheGuysanIdiot https://www.kvraudio.com/forum/memberlist.php?mode=viewprofile&u=213066
- KVRist
- 308 posts since 10 Aug, 2009 from United Kingdom
[Eggu & Jo]
I have got to go away for a day or so, but when I get back I will help on this thread.
Not too sure what Eggu wants explaining but I will have a go when I get back.
Bye for now!
OZ
I have got to go away for a day or so, but when I get back I will help on this thread.
Not too sure what Eggu wants explaining but I will have a go when I get back.
Bye for now!
OZ
-
TheGuysanIdiot TheGuysanIdiot https://www.kvraudio.com/forum/memberlist.php?mode=viewprofile&u=213066
- KVRist
- 308 posts since 10 Aug, 2009 from United Kingdom
Looks like [pljones] has jumped in.
I will leave you in his capable hands.
Goodnight all
OZ
I will leave you in his capable hands.
Goodnight all
OZ
-
TheGuysanIdiot TheGuysanIdiot https://www.kvraudio.com/forum/memberlist.php?mode=viewprofile&u=213066
- KVRist
- 308 posts since 10 Aug, 2009 from United Kingdom
[Eggu] - I am back now. [pljones] seems to have explained the MUX well.
Do you need any further help on this thread, if you do, what exactly?
OZ
Do you need any further help on this thread, if you do, what exactly?
OZ
-
- KVRist
- Topic Starter
- 152 posts since 15 May, 2009 from Germany
Thank you for all the explanation.
Will try to experiment with all the elements in the deep editor.
Will try to experiment with all the elements in the deep editor.
Everything should be made as simple as possible, but not simpler!
-
- KVRist
- Topic Starter
- 152 posts since 15 May, 2009 from Germany
tried the "note modifer" element.
This is interesting, because changing the velocity is not the same as changing the volume.
But I can't make visible the (e.g.) velocity knob in the play editor.
I the deep editor view I can double click the note modifer element and a pop up appears with the knobs for velocity and transpose.
But when editing a parameter knob I can chose "note modifer" as target but no parameters are visible to chose from (only none, see picture).
What is the reason ?
This is interesting, because changing the velocity is not the same as changing the volume.
But I can't make visible the (e.g.) velocity knob in the play editor.
I the deep editor view I can double click the note modifer element and a pop up appears with the knobs for velocity and transpose.
But when editing a parameter knob I can chose "note modifer" as target but no parameters are visible to chose from (only none, see picture).
What is the reason ?
Everything should be made as simple as possible, but not simpler!
-
- KVRAF
- 7412 posts since 8 Feb, 2003 from London, UK
Confirmed. I'd expect to be able to modulate the transpose and velocity amounts through a parameter mapping but they're not available.
-
- KVRAF
- 13863 posts since 24 Jun, 2008 from Europe
The reason is that the note modifier velocity is not published as a 'parameter'. This is a bit technical, but that's the reason.Eggu wrote:But when editing a parameter knob I can chose "note modifer" as target but no parameters are visible to chose from (only none, see picture).
What is the reason ?
-
- KVRist
- Topic Starter
- 152 posts since 15 May, 2009 from Germany
Ok, understand.The reason is that the note modifier velocity is not published as a 'parameter'. This is a bit technical, but that's the reason.
Please put it on the wishlist.
Everything should be made as simple as possible, but not simpler!
-
- KVRAF
- 7412 posts since 8 Feb, 2003 from London, UK
Could there be some (colour?) coding system to make it clear which parameters can be automated?
-
- KVRAF
- 13863 posts since 24 Jun, 2008 from Europe
I'm aware of the aspect. It's not yet on the M3 list though.pljones wrote:Could there be some (colour?) coding system to make it clear which parameters can be automated?