MAGC - Queries
-
- KVRist
- 128 posts since 11 Jun, 2014
This is not exactly the best workflow but I managed to use MAGC in Studio One by using a bus.
- Have a track with effects
- Create a bus
- Move effects from track to bus
- Add MAGC at end of bus effects
- Set output of track to the bus
- Create a send on track to MAGC sidechain on bus
So basically the input to the bus as well as the sidechain of MAGC are identical (pre-effects). Now you can alter the effects before MAGC with volume balanced.
Another way is with MCompare. Put MCompare before effects in generate source mode. Then put another MCompare after the effects, making Source use ALC. However, this increases the volume of the pre-effects signal to the post-effects one, which may not be desired.
Viraj.
- Have a track with effects
- Create a bus
- Move effects from track to bus
- Add MAGC at end of bus effects
- Set output of track to the bus
- Create a send on track to MAGC sidechain on bus
So basically the input to the bus as well as the sidechain of MAGC are identical (pre-effects). Now you can alter the effects before MAGC with volume balanced.
Another way is with MCompare. Put MCompare before effects in generate source mode. Then put another MCompare after the effects, making Source use ALC. However, this increases the volume of the pre-effects signal to the post-effects one, which may not be desired.
Viraj.
-
Chandlerhimself Chandlerhimself https://www.kvraudio.com/forum/memberlist.php?mode=viewprofile&u=318799
- KVRAF
- 1821 posts since 19 Dec, 2013 from Japan
I'm having the same problem in Sonar. Once I figured out how this was supposed to be used, I was confused because I didn't think it could be done in Sonar. I checked and as I thought, its impossible. Sonar doesn't allow you to send a side-chain signal to something on the same track. It also only sends out side-chain audio post fx. Of course I could always connect things like the tip above using aux tracks, but that would cause me to double my track count and waste a lot of time.
I mentioned the other post, but could you add an RMS capture and RMS set button to this plugin for those of us that aren't able to use sends preFX?
I mentioned the other post, but could you add an RMS capture and RMS set button to this plugin for those of us that aren't able to use sends preFX?
My Youtube page https://www.youtube.com/user/GuitarChandler
- KVRAF
- 2702 posts since 9 Jul, 2015 from UK
I would like to second the fantastic idea from chandlerhimself
RMS set source and target buttons (like matching eq)
I also don't have the ability in live to send the signal correctly.
Vojtech please give this great idea some though.
RMS set source and target buttons (like matching eq)
I also don't have the ability in live to send the signal correctly.
Vojtech please give this great idea some though.
Jason @ Melda Production
- KVRian
- 1094 posts since 23 Sep, 2006
I've been using MChannelMatrix to send things to the side chain in the same track. Have you tried inserting one of them at the start of your effect chain?
- KVRAF
- 2702 posts since 9 Jul, 2015 from UK
To be honest I've never used it before, ill take a look.vectorwarrior wrote:I've been using MChannelMatrix to send things to the side chain in the same track. Have you tried inserting one of them at the start of your effect chain?
Jason @ Melda Production
- KVRAF
- 2702 posts since 9 Jul, 2015 from UK
I don't get it. Please could you elaborate?jmg8 wrote:To be honest I've never used it before, ill take a look.vectorwarrior wrote:I've been using MChannelMatrix to send things to the side chain in the same track. Have you tried inserting one of them at the start of your effect chain?
Jason @ Melda Production
- KVRian
- 1094 posts since 23 Sep, 2006
I dont have sonar so dont know exactly how you'd use it... but essentially the short version is:
-Ensure track is set to FOUR channel somehow (again, dont know how to do that in sonar)
-Add a channel matrix and set ins 1+2 to also go to 3+4 -Add whatever process you want to be loudness matched after the channel matrix
-Add MAGC after that
-And this is where my sonar skills fail me again, you have to ensure inputs 3+4 are used as the sidechain for AGC. Reaper has a routing system that makes this mega easy, no idea about sonar.
There is another method:
-Add process that you want loudness matched
-Make it process the input but output it to 3+4 (again, reaper makes this easy, donno about sonar)
-Add MAGC, but this time 3+4 should be the main input and the side chain should be 1+2 (the original audio)
I dont like the second method because bypassing the AGC is no longer trivial as you've redirected the processed output to 3+4, making it essentially inaudible without MAGC enabled. But, this method does require less steps.
-Ensure track is set to FOUR channel somehow (again, dont know how to do that in sonar)
-Add a channel matrix and set ins 1+2 to also go to 3+4 -Add whatever process you want to be loudness matched after the channel matrix
-Add MAGC after that
-And this is where my sonar skills fail me again, you have to ensure inputs 3+4 are used as the sidechain for AGC. Reaper has a routing system that makes this mega easy, no idea about sonar.
There is another method:
-Add process that you want loudness matched
-Make it process the input but output it to 3+4 (again, reaper makes this easy, donno about sonar)
-Add MAGC, but this time 3+4 should be the main input and the side chain should be 1+2 (the original audio)
I dont like the second method because bypassing the AGC is no longer trivial as you've redirected the processed output to 3+4, making it essentially inaudible without MAGC enabled. But, this method does require less steps.
You do not have the required permissions to view the files attached to this post.
- KVRian
- 1094 posts since 23 Sep, 2006
With the above said, it would be sweet if MChannelMatrix would allow you to send inputs to SIDE CHAIN outputs. Currently you can only redirect inputs to outputs and side chain inputs to side chain outputs... having cross pollination between ins/outs and sidechain ins/outs would simplify this stuff.
Of course, all of the above is not necessary if you have MXXX and the processing you want is all Melda... unfortunately you most likely want to use other 3rd party effects, which is where doing these extra steps becomes necessary.
Of course, all of the above is not necessary if you have MXXX and the processing you want is all Melda... unfortunately you most likely want to use other 3rd party effects, which is where doing these extra steps becomes necessary.
-
- KVRer
- 5 posts since 5 Dec, 2012 from Birmingham, UK
You can easily do this kind of sidechain routing within DDMF's Metaplugin if you don't have MXXX or want to use 3rd party plugins.
-
MeldaProduction MeldaProduction https://www.kvraudio.com/forum/memberlist.php?mode=viewprofile&u=176122
- KVRAF
- 14339 posts since 15 Mar, 2008 from Czech republic
I'm not sure what you are guys discussing, but from the few topics it seems to me like a HUGELY overcomplicated approach. All you need to do is the create a separate buss, send the input to there, insert some eqs and comps or whatever you want to fix afterwards, add MAGC and send the original to its sidechain. Like this:
Track -> Buss
Track -> MAGC sidechain
Buss : eq, comp... MAGC
Track -> Buss
Track -> MAGC sidechain
Buss : eq, comp... MAGC
- KVRAF
- 2702 posts since 9 Jul, 2015 from UK
Live has a limit of 12 busses.
AGC should be super simple and discreet, it shouldn't require doubling the track count.
What are your thoughts on the idea of having a source and target buttons (like in auto EQ) this is a simple aproach to make this useable for those of us without the send flexibility of Cubase.
AGC should be super simple and discreet, it shouldn't require doubling the track count.
What are your thoughts on the idea of having a source and target buttons (like in auto EQ) this is a simple aproach to make this useable for those of us without the send flexibility of Cubase.
Jason @ Melda Production
-
- KVRian
- 509 posts since 28 Oct, 2012 from Argentina
Vojtec, isn't this what was already described above as a not very convenient workflow? Duplicating every channel just for MAGC? Or am I still missing something?
valankar wrote:This is not exactly the best workflow but I managed to use MAGC in Studio One by using a bus.
- Have a track with effects
- Create a bus
- Move effects from track to bus
- Add MAGC at end of bus effects
- Set output of track to the bus
- Create a send on track to MAGC sidechain on bus
So basically the input to the bus as well as the sidechain of MAGC are identical (pre-effects). Now you can alter the effects before MAGC with volume balanced.
