Hi Sean, Thanks for attaching that. I believe I've lost track of that original document myself. Having followed those guidelines for so long,I haven't looked at them for years and simply lost it along the way. Glad you had a copy. Cheers!
Slau On Jan 3, 2016, at 1:47 PM, Sean A. Cummins <seanacumm...@gmail.com> wrote: > Hi Slau, > > Yes, I realized that after good old JAWS inadvertently clicked on the > wrong button. I ment to delete, but the focus suddinly switch just as > I clicked on the button. LOL! > > For the listers, I have attached the Charles Dye PDF. > > Sean > > On 1/1/16, Slau Halatyn <slauhala...@gmail.com> wrote: >> Just to clarify, what Steve is referring to is sending to a "new track" >> under the contextual menu when clicking on a send. In the resulting dialog, >> you can define the track as an auxiliary input and in this process, whatever >> you name the Aux input will become the name of the bus automatically. >> regarding the naming of busses, it should be noted that people sometimes get >> sessions recorded elsewhere and most folks ignore the naming of busses which >> makes things a nuisance. It would be nice if people followed session >> exchange guidelines set forth by the P&E wing of NARAS. Charles Dye also put >> together a guidelines doc. Anyway, throwing that in there. bTW, Sean, I saw >> a reply from you on this thread but it had nothing in it, FYI. >> Slau >> >> On Jan 1, 2016, at 10:42 AM, TheOreoMonster <monkeypushe...@gmail.com> >> wrote: >> >>> In the interest of keeping things simple Why not just create an Aux track >>> mono or stereo and name it. Then route the other tracks to it the way you >>> would route to a bus. The AUX track will set up and handle all the buss >>> assignments in the back ground for you and it gives you the option to name >>> the Aux track when creating it instead of the run around you have to do to >>> name the busses. >>> >>> Just a thought. >>> >>>> On Dec 30, 2015, at 7:49 PM, Christopher-Mark Gilland >>>> <clgillan...@gmail.com> wrote: >>>> >>>> I'm thinking in this case, either. >>>> >>>> Chris. >>>> >>>> ----- Original Message ----- From: "Brian Howerton" >>>> <bshowert...@gmail.com> >>>> To: <ptaccess@googlegroups.com> >>>> Sent: Wednesday, December 30, 2015 6:50 PM >>>> Subject: Re: question about buses in pro tools >>>> >>>> >>>> And to double click, would that be the VO shift space command twice or >>>> would I route the mouse with vo command f5 and then double click on the >>>> track pad. Just clarifying. Thanks Slau. >>>> Brian >>>>> On Dec 30, 2015, at 6:37 PM, Slau Halatyn <slauhala...@gmail.com> >>>>> wrote: >>>>> >>>>> Oops, I might have just replied on the wrong thread. To keep it in this >>>>> thread, here it is again, JIC: >>>>> In the Bus tab of the I/O Setup window, double-click on the name of the >>>>> bus, type the name and hit Return. >>>>> Slau >>>>> >>>>> On Dec 30, 2015, at 3:32 PM, Brian Howerton <bshowert...@gmail.com> >>>>> wrote: >>>>> >>>>>> Hello all, >>>>>> Can someone explain to me how to rename buses in pro tools? For >>>>>> example, if I am creating sub mixes, and I set the input of an aux >>>>>> track to a bus such as bus 1-2, how can I then rename that bus to >>>>>> something like drums with voiceover? Also, does this rename only >>>>>> effect the current session that I am working on? I don’t necessarily >>>>>> want to rename my buses permanently, just for mixing purposes so I >>>>>> don’t always have to remember that drums are buses 1-2. Thanks for the >>>>>> help, >>>>>> Brian >>>>>> >>>>>> -- >>>>>> 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. >>>>>> For more options, visit https://groups.google.com/d/optout. >>>>> >>>>> -- >>>>> 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. >>>>> For more options, visit https://groups.google.com/d/optout. >>>> >>>> -- >>>> 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. >>>> For more options, visit https://groups.google.com/d/optout. >>>> -- >>>> 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. >>>> For more options, visit https://groups.google.com/d/optout. >>> >>> -- >>> 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. >>> For more options, visit https://groups.google.com/d/optout. >> >> -- >> 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. >> For more options, visit https://groups.google.com/d/optout. >> > > -- > 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. > For more options, visit https://groups.google.com/d/optout. > <PTGuidelines.pdf> -- 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. For more options, visit https://groups.google.com/d/optout.
