MOTUnation.com

groove wrote:...if what I'm listening is fine, then I know the file is.

Groove, how do you figure that? I mean, isn't listening in real-time like listening to the Input side of a tape machine? You still had to do real-time playback to be sure what was on the tape was good? (and you still have to do a real-time playback to be *sure* that the file is good?)


BTW, I'm in for BTD....when there are a dozen plus stems on a score with a dozen plus cues, bouncing MIDI tracks is a HUGE time saver. IT only kills me that I don't think VEPro5 ever got that sorted out?

This was a fairly simply mix with a around 10 audio tracks going to one master AUX that in turn was sent via another bus to a STEREO track for real time recording. Typically my song session will have around a dozen AUX busses for stems. A film might have even 30 of them, depending on how many different STEMS I will need in the end.

williemyers wrote:

groove wrote:...if what I'm listening is fine, then I know the file is.

Groove, how do you figure that? I mean, isn't listening in real-time like listening to the Input side of a tape machine? You still had to do real-time playback to be sure what was on the tape was good? (and you still have to do a real-time playback to be *sure* that the file is good?)


BTW, I'm in for BTD....when there are a dozen plus stems on a score with a dozen plus cues, bouncing MIDI tracks is a HUGE time saver. IT only kills me that I don't think VEPro5 ever got that sorted out?

groove wrote: Maybe I wasn't clear enough - apologies for my bad english - I should have said that the gain in time of BTD is small so I prefer to do real time. This gives me the opportunity to stop the recording if needs be. I've never said I just "watch" the wavefile for any problem and that I don't listen to the master file. I've used redundancy for lack a better word. Don't worry, I have more than my share of stems listening sessions before delivery to the re-recording house!

Most problems that occurs in a file are input related most of the time: random digital clips, skipped samples playback, etc. Real time recording still allows you to hear them and stop the recording. The other problem that can occurs is a corrputed file on the HD and even that you'll know right after the recording. Other reasons are related to limitations on some VIs and fx: for instance, Kontakt instruments with built-in delays fx sometime create artifacts on tempo changes in BTD. As I said, I never said I don't do real-time playback but I'm pretty confident that what I ear in real-time recording will be fine, hense what I wrote.

Tritonemusic wrote:...(didn't notice which version you're using)

So sorry...I must have read your signature three times and just now noticed you're using DP 9.01.

Real-time mixdown for me. Haven't done a BTD since 2002.

williemyers wrote: BTW, I'm in for BTD....when there are a dozen plus stems on a score with a dozen plus cues, bouncing MIDI tracks is a HUGE time saver. IT only kills me that I don't think VEPro5 ever got that sorted out?

Wow...

This goes under:

1. I guess you CAN teach an old dog "new" tricks.

2. I should read the manual more often.

For years (and years), I have been freezing the MIDI VI tracks which is a real time procedure. On average about 3 1/2 minutes per track. Very time consuming.

Watching paint dry.

First thing this morning, I opened a project and tried the BTD on a couple of MIDI VI tracks. Takes about a 10th of the time!

Only thing I miss is the VU meter display to make sure that I'm not red-lining.

So glad I saw this thread.

(And, yes, I do real time mixes, too, unless it's just a quick run-off for a client.)

Merci...

Buzzy

Actually your meters should still run but super fast.

When I first upgraded to an SSD, I was puzzled that BTD wasn't working. Well, it was but so fast I couldn't see the process.

I'm ok with that.

David Polich wrote:Real-time mixdown for me. Haven't done a BTD since 2002.

Any particular reasons David?

MIDI Life Crisis wrote:Actually your meters should still run but super fast.

I think I checked that, but I'll look again. I did see the Master Bus metering active.

Buzzy


Sent from my iPad using Tapatalk

buzzsmith wrote:

williemyers wrote: BTW, I'm in for BTD....when there are a dozen plus stems on a score with a dozen plus cues, bouncing MIDI tracks is a HUGE time saver. IT only kills me that I don't think VEPro5 ever got that sorted out?

Wow...

Merci...

Buzzy

not at all! took me a few *years* to spot this - instant addiction!

MIDI Life Crisis wrote:Actually your meters should still run but super fast.

correct (as usual!), MLC

williemyers wrote:correct (as usual!), MLC

Did you zoom in and make sure they're aligned at the sample level?

Occasionally PT will bounce things just fine, but the file will be stamped 1 (or a few) samples off. I haven't seen that in DP, but what you're describing sounds like 2 files that are a sample off, you will only hear very high frequency content then as the lower stuff is still in phase enough to cancel out.

Been 100% realtime here for maybe a decade. I forget what the problem was with BTD. But I do recall we moved to realtime due to some kind of scary inconsistencies.

I would certainly try BTD again for stems if all is well with all plugs and VEP.