BTD assignment gone awry. What'd I do?

[studiojimi]

yesterday i imported some 002 files from another studio into my HD rig

i locked everything up and was happy with the sound

then the client came over and did some vocals and i made her a rough BTD

she left with her CD and called me from phone saying that only the drums were on the CD.

i opened up the session and found that the MIX out assign on the BTD screen had normaled to one of my busses ....how did that happen?

could not get it so stay on 1 and 1 with i have named in my session temp "•MIX•"
(try it you might liike it)

is this a fluke?

or did i pick up some bad juju routing from the other studio?

i re routed everything and it fixed it by cleaning all the inputs and outputs of the bad session and importing them into my known good template.

have others of you seen this type of event?

....it caught me off guard and caused a world o' reassign and wasted time.

[WernerF]

Did you import session files or just audio? I get the screwed up IO settings all of the time when I import session files from other studios. It's a major pain in the butt and importing my saved IO settings also never seems to work 100% accurately either. Results in a whole bunch of timewasting resetting here too.

[studiojimi]

Originally Posted by WernerF

Did you import session files or just audio?

session files....

i'm gonna be really neat and tidy next time

all ins outs and plugs will be out of their session before i import

i may even default the I/O as well

this kind of stuff wears you down when you pick up unwanted stuff and kills the vibe of working on the music..... but an overcomer am i!

[jeremyroberts]

Yeah - the i/o paradigm is not without its plusses and minuses. There are more than a few threads on the DUC exploring best/better/not so good i/o workflows.

In the old days -- we'd bring in a multitrack and then spend a few minutes with the track sheet and the patchbay. It would take 5+ minutes of patching to make it all happy.

My conservative way to bring stuff in from outside is to import session data, and discard the i/o routing. Copy audio from source (so you're always working on YOUR production drives, not the client drives).

But you knew that -- and yes, it will take you 5 minutes to assign i/o routing for the stuff you're importing. But then, it's on your terms and your i/o template. When you're done, just give it all to the client, and document which tracks to import session data from on their end (I use a naming convention and drag all new tracks to the top of the session)

Same 5 minutes as the old days. Usually less.

Chalk it up to "i won't do that again".

[studiostuff]

Sending out a client ref CD without checking the playback is a newbie error.

Always check your work.

[studiojimi]

Originally Posted by studiostuff

Sending out a client ref CD without checking the playback is a newbie error.

Always check your work.

gimme a break dude please.

not when my dinner is ready and the client was late to begin with and made me work right to the wire.....under protest LOL we're talkin' 7:55 pm here....you want ME to miss American Idol LOL

what are you...cwazy?

[BaileyBass]

Originally Posted by studiojimi

and i made her a rough BTD

Yet another reason to make BTT/RTD ones preferred workflow. This scenario would have been impossible.. SB

[studiojimi]

Originally Posted by BaileyBass

Yet another reason to make BTT/RTD ones preferred workflow. This scenario would have been impossible.. SB

no.
this was just a quick reference
not RTD time for me yet in this tune

1st time this happened in 12 years of PT use.

but how you would put in a light bulb?

[jeremyroberts]

not RTD time for me yet in this tune

Jimmy, it's all the same, right?
RTD workflow for a ref:
1. length of tune = time to print track.
2. select bounced region.
3. command-shift-K (export somewhere)
4. Open file in iTunes.
5. Burn your ref.

BTD workflow for a ref:
1. length of tune = time to bounce + making sure bounce settings are correct.
2. Open file in iTunes.
3. Burn your ref.

Both take exactly the same duration.

Benefits of RTD:

1. ref mix is done in-place, in the timeline of the song, archived forever with the session. solves data management issues that may arise.
2. what you hear is what it is (unless you F it up with bad routing)
3. you can actually try to do a rough mix in real time if needed.

Downside to RTD:

1.

Downside to BTD:

1. Can't make any adjustments on the fly.
2. Where did you put the bounce file?

Zero justification for using BTD for ref mixes. BTD is useful when you need a sample accurate bounce, dithered, truncated, etc... but not for routine ref mixes.

Why not embrace this workflow? It is actually faster and more convenient and less filling and tastes better...

[studiojimi]

this thread wasn't about lessons in RTD or BTD

my BTD normaled and got stuck on bus 5-6

i'm still trying to figure out why my session got so toxic

imported everything into a new session and fixed it....

i'm just wondering if it or something similar has happened to any of you guys

and keep it good vibes please.