Hello, Making this more simple, once youu have the desired plugin on your aux track, on the vocal track or whatever you call it just go under the sends menu, and instead of choosing bus, you can choose tracks under a submenu and choosing the aux track.
> On Nov 2, 2019, at 8:43 AM, Charles <rumber...@hotmail.com> wrote: > > Hello Dammie > > Based on your message, what you are doing wrong is to use the sense in your > auxiliary track. Please delete any sense you may have created in your aux > track. The only thing you need to do in your aux track is to go into the > input menu and select the buss that you are using which could be either one > Dash two or 3–4. I assume the reverb you want to use is already inserted in > the auxiliary track. then, go back to your audio tracks and make sure that > you go into the sends menu and have them go through the same buss that your > auxiliary track is using. Here is where you need to adjust the send level to > tell ProTools how much of your audio track you want to send to your auxiliary > track. I hope that helps. > Sent from my iPhone > >> On Nov 2, 2019, at 1:14 AM, Dammie Onafeko <mindofdhe...@gmail.com> wrote: >> >> Hi guys: >> >> I did what yo'll told me to do and I can't still hear the reverb. This >> is what I have: >> a track Connection, another called Radio Effect, and the Aux called Group >> Verb. >> I routed sends oA of Connections and Radio Effect to Group Verb. >> Then I go into sends A of Group Verb, VO space on it to open the menu, >> and went down to bus 3, 4. >> I did same thing for Connections and Radio Effect. >> While in the sends menu, I went to the level fader and took it to -15 >> I don't how to control the dryness and wetness. >> When I play the audio back, I couldn't hear the reverb effect. What am >> I still doing wrong? Somebody help! >> >> Best, >> >> Dammie >> >>> On 11/1/19, TheOreoMonster <monkeypushe...@gmail.com> wrote: >>> When you use a send, you ae sending a copy of the audio signal So in essence >>> you are creating a wet/dry blend. This is useful for things like reverb and >>> delays or other time based effects. When you put the reverb or delay on the >>> aux track, you will want to set it to be 100% wet. Then the send level will >>> act as the wet dry balance. Since the original audio track’s output is still >>> going to the master fader, and the AUX’s output is also going to the master >>> fader, the send level will set how much of that dry signal” gets pushed into >>> the reverb and as a result how much reverb’ed signal shows up in the master >>> fader. >>> Chaning the output of the track to the AUX or bus, means you are sending all >>> the tracks signal to a bus and not a duplicate of it as you would be if you >>> use a send. A useful example for this use case is lets say you have 5 vocal >>> tracks. You can set the output of those 5 tracks to a AUX or bus, and now >>> you can just EQ and compress all your vocals and use that AUX/Bus fader as a >>> master fader for the vocals. But since the AUX/bus is still being sent to >>> the master fader you still get the vocals in the mix. >>> >>> >>> >>>> On Nov 1, 2019, at 4:53 PM, Christopher Gilland <clgillan...@gmail.com> >>>> wrote: >>>> >>>> So, what is the difference in using a send on an audio track, sending to >>>> an AUX track, then letting PT do the routing, vs. setting your output IO >>>> of an audio track to a bus, then going to an AUX track, and setting the >>>> input to that same bus, and leaving, on the AUX track, your output IO set >>>> to your main out L/R? >>>> >>>> >>>> IN other words, what I'm asking is, what's the difference in doing this >>>> with a send, vs doing it via your IO paths without a send involved? >>>> >>>> >>>> I've seen it done both ways. I know there is a key major difference, and a >>>> reason why you'd do the ladder, but I just can't seem to grasp why? >>>> >>>> >>>> Chris. >>>> >>>> -- >>>> You received this message because you are subscribed to the Google Groups >>>> "Pro Tools Accessibility" group. >>>> To unsubscribe from this group and stop receiving emails from it, send an >>>> email to ptaccess+unsubscr...@googlegroups.com. >>>> To view this discussion on the web visit >>>> https://groups.google.com/d/msgid/ptaccess/4f5216dd-0016-a2c2-501e-33750b22bcb4%40gmail.com. >>> >>> -- >>> You received this message because you are subscribed to the Google Groups >>> "Pro Tools Accessibility" group. >>> To unsubscribe from this group and stop receiving emails from it, send an >>> email to ptaccess+unsubscr...@googlegroups.com. >>> To view this discussion on the web visit >>> https://groups.google.com/d/msgid/ptaccess/4B1161A7-A4A8-4DC8-9C1A-2894D82AF1AA%40gmail.com. >>> >> >> -- >> You received this message because you are subscribed to the Google Groups >> "Pro Tools Accessibility" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to ptaccess+unsubscr...@googlegroups.com. >> To view this discussion on the web visit >> https://groups.google.com/d/msgid/ptaccess/CAN%3Dh5d-e%3DMgpsgw-y%3D6HdwuCPa1k%3DQaDK9tQFKRhDFF%2ByqXiRw%40mail.gmail.com. > > -- > You received this message because you are subscribed to the Google Groups > "Pro Tools Accessibility" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to ptaccess+unsubscr...@googlegroups.com. > To view this discussion on the web visit > https://groups.google.com/d/msgid/ptaccess/BY5PR03MB52991D71394654E8143648BABB7D0%40BY5PR03MB5299.namprd03.prod.outlook.com. > -- You received this message because you are subscribed to the Google Groups "Pro Tools Accessibility" group. To unsubscribe from this group and stop receiving emails from it, send an email to ptaccess+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/ptaccess/9033A10C-8A18-455B-9AF1-FAE0B8565D3E%40tznet.com.
