Tips for bouncing when using bus->audiotrack->output

[Sir Hannes]

I have all my tracks feeding busses. They (a ka subgroups) go to my main bus. And the mainbus to an 2.0 audio track for recording.
How can speed up my workflow with "bounce" offline? In the timeline I select the length and go to bounce. PT asks me which output/bus: if I choose my A1-2 outputs (my interface outputs) I get no signal. If I choose the bus (2.0 rec) feeding the audio track - there's no signal.

[studiostuff]

I use the same work flow as you. I think it is better than outputting everything through a master fader. The reason I like it best is because when you print a mix to your 2.0 audio track, it lives in the protools session in the clip bin and is easily available as soon as you open your session.

So, I can't offer a speedier workflow than recording your mix through your bus to an audio track. However, you will definitely save time when you are looking for mixes.

Who does just one mix? Not me. No vocal, vocal down a few dB, vocal up a few dB, all those live in your clip bin with the session forever. At that point, a simple export region to file command exports any of those mixes instantly, and will do a lot more (rate conversion, all of that stuff). (The key command is Shift+Command+K...?)

Select the mix (which is a region in the edit window, or a clip in the clip bin) and press Shift+Command+K.)

[john1192]

Originally Posted by Sir Hannes

I have all my tracks feeding busses. They (a ka subgroups) go to my main bus. And the mainbus to an 2.0 audio track for recording.
How can speed up my workflow with "bounce" offline? In the timeline I select the length and go to bounce. PT asks me which output/bus: if I choose my A1-2 outputs (my interface outputs) I get no signal. If I choose the bus (2.0 rec) feeding the audio track - there's no signal.

my first guess is you are using Hardware Inserts on your Master Aux Track !!! right or wrong ???

you are not getting any Signal to Output A1-2 ??? you say NO

how are you hearing your mix ??? A1-2 right ?? or ??

if you can hear it it should be able to be bounced .. does a Realtime Bounce give you any signal ???

just tring to understand your workflow and why you are not hearing anything ..

if you did hear something you could do offline bounce and choose Import After Bounce - then Choose NEw Track ..

[Sir Hannes]

Hi, I am not using Hardware. I will try that next time. Right now I just bounce on the fly, but the mp3 export I do with studiostuff's tip.

best
Johannes

[Sir Hannes]

Okay, here I am again. With a short question:
Does the Bounce-function does care about Solo enabled? I mean, can I bounce one track in solo, just to get all plugins in one wav, which I reimport?

Edit:
Well, why I am asking: the answer seems "no". I routed my kick track on physical output A1, put it in solo, doing bounce to disk - and I have all the other stuff within this audio object.

[john1192]

Originally Posted by Sir Hannes

Okay, here I am again. With a short question:
Does the Bounce-function does care about Solo enabled? I mean, can I bounce one track in solo, just to get all plugins in one wav, which I reimport?

Edit:
Well, why I am asking: the answer seems "no". I routed my kick track on physical output A1, put it in solo, doing bounce to disk - and I have all the other stuff within this audio object.

try AFL Solo Mode .. might work

[Stig Eliassen]

I don't get why this doesn't work for you. I just tested routing a single track to a physical output (which I never do), right-click track name, and choose "bounce". Works just fine. Commit works fine too.

[Sir Hannes]

Well, I guess I save a template and load it up on a server? You could try?

[Stig Eliassen]

What is your hardware setup, Sir?

[Sir Hannes]

Okay, this is my tracks setup. I don't know what I changed, but when I bounce this track and import = I've got my content. But while bouncing in non-offline mode, I can't hear anything. There's no output to my speaker. Also all meters are working.

Hardware-Setup is Output1-2 (Playbackengine SystemWide) -> Systemwide Output MackieOnyx -> via Thunderbolt-Firewire to Mackie Onyx.

hint: the problem was before using Systemwide already.