|
|
|
|
|
|
|
Re: Quickest way to get from 24 to 16 bit [message #70272 is a reply to message #70271] |
Wed, 12 July 2006 17:46 |
Kim
Messages: 1246 Registered: October 2005
|
Senior Member |
|
|
Ah, well in that case forget what I said. ;o)
Cheers,
Kim.
"Rod Lincoln" <rlincoln@nospam.kc.rr.com> wrote:
>
>Kim...I was talking about rendering individual 16 bit tracks to 24 bit.
Like
>all the seperate drum tracks.
>I agree with you on the bounce thing (as in bounce to disk).
>I usually record in 16 bit and bounce the mix at 24 for just the reason
you
>mentioned.
>Cheers
>Rod
>"Kim" <hiddensounds@hotmail.com> wrote:
>>
>>
>>Just because the original project was in 16 bit doesn't mean you only get
>>16 bits out of it when bouncing at 24 bit.
>>
>>The mix bus, eq and effects all have more than 16 bit resolution, plus
multiple
>>16 bit tracks added together equals more than 16 bits of resultion.
>>
>>Bouncing a 16 bit project at 24 bit does increase resolution. If you look
>>at the files you will see the last 8 bits are not empty.
>>
>>Cheers,
>>Kim.
>>
>>"Rod Lincoln" <rlincoln@nospam.kc.rr.com> wrote:
>>>
>>>If your running 3.0 set the project window for 16 bit and render. You
can
>>>go the other way too. I've had projects where I found out the client really
>>>wanted 24 bit files, after it was too late. I just render the 16 bits
to
>>>24. Yeah, the last 8 bits are empty, but I've NEVER had anyone complain.
>>>Actually, they all remark on how good it sounds. One guy even said how
>glad
>>>he was I could do 24 bit....it really made a difference.
>>>Go figure.
>>>Rod
>>>Rod
>>>"Don Nafe" <dnafe@magma.ca> wrote:
>>>>any ideas
>>>>
>>>>Don
>>>>
>>>>
>>>
>>
>
|
|
|