Hey...it WORKS !

[lemix]

Hi Guys,

This maybe a little bit of a no news for some of you, but let me share my exitement regardless ;
As I am getting more and more comfortable using PT (bought an Mbox just to learn it )have been recently porting some of my studio sessions over to their HD/Mac rig.
Recently put together an additional external FW box w/WD Caviar 120gb drive. Aquired MacDive5...so now I'm able to move session back and forth.
Initially I was facing formatting difficulties , due to my lack of Mac knowledge...this forum to the rescue !! >>


thanx Chris !

It works like a charm
Those little red apples are the only clues right now, that a Mac OSX partitioned drive is mounted
on my home PC. COOL...

On closing let me just paste my last unanswered question here, ( bump )maybe I'll get lucky this time.

Hi All,

So, I was just wondering ;
If all parameters, like sample rate/bit depth/output format of the bounce destination file is exactly the same as your source...why is the option > "process during/after BTD" appear ???
What else will actually be done to my files, once the real time BTD process has finished ?
I do not need to dither/rate convert or change the format ( dual mono is OK )

any info will be appreciat

thanx all,
cheers,

[Chris Cavell]

Digi states that processing AFTER is more ACCURATE when it needs to be processed or changed in some way, implying that processing DURING is LESS ACCURATE, my own experience shows me that DURING is less strenuous (sometimes it was the only way to make it through a bounce). Don't ask me how or why, I could make an educated guess, but I really don't know.

[lemix]

Chris,

thanx again for responding,
I wasn't really questioning " during/after", but simply wanted to clear up >>
why is the option still available, if NO processing is required at all ...what is being done to my audio on " convert" if :
1)sampling rate=same for destination
2)bith depth =same for destination
3file format =same for destination



thank you,
cheers,

[Chris Cavell]

simple:

the DAE deals with a floating 32 bits, but the file formats are either 16 or 24 bit, so obviously there has to be some processing.

[lemix]

Oh I see...
I'm not sitting front of my PT machine right now, but isn't there also a "32 bit foating" export option ?
If there was, WaveLab, my usual burning app. could open that one ...

cheers,

[Chris Cavell]

Bounce options are 8, 16, and 24 for uncompressed audio. The export options are the same. Even if they weren't, the export regions as audio files is coming from a pre-existing file or set of regions from files that are at 24 bit or less.

(on the same note, does anyone know if the rewire audio inputs are at the resolution of the DAE or at the resolution of the session files and then mixed at the resolution of the DAE?)

[tele_player]

The conversion that happens is conversion between the 24-bits always supplied to the converters (regardless of session depth) and the destination depth of your bounce. You can verify this by examining the temporary files produced during a bounce.

If you bounce to 24-bit multiple mono, the conversion options go away, regardless of the bit depth of the session.

[lemix]

If you bounce to 24-bit multiple mono, the conversion options go away, regardless of the bit depth of the session

Great...thanx guys. I'll check on the next session. It does make sense that way, right ?

happy tooling,