Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[Matt]

Media Center now uses a purely 64-bit data path for all audio.

Since Media Jukebox 5 or 6 (I don't remember for sure) we have used a 32-bit floating point data path.  I believe we were the first player to embrace this.

The new 64-bit precision path ensures that no precision is lost even when doing many stacked DSP effects.

Since modern floating point math units on CPUs use 80-bits for calculations, there is little (or no) performance penalty for this switch.  Even an Atom benchmarks within a few % with regards to audio engine speed.  Memory usage for buffering does increase a few MB, but this is a minor cost relative to the gain.

Build 101 includes the updated audio engine:
http://yabb.jriver.com/interact/index.php?topic=59363.0

Enjoy.

[Vincent Kars]

Excellent
Don't forget to mention it here: http://wiki.jriver.com/index.php/Audiophile_Info

[mojave]

My VST plugins also use a 64 bit data path. Does MC maintain the 64 bit data path with the plugin (if supported by the plugin) or does MC convert to the the set bit rate in Output Format (or highest bit rate supported by the hardware if using ASIO) before handing off to any VST plugins?

[Matt]

My VST plugins also use a 64 bit data path. Does MC maintain the 64 bit data path with the plugin (if supported by the plugin) or does MC convert to the the set bit rate in Output Format (or highest bit rate supported by the hardware if using ASIO) before handing off to any VST plugins?

We use 64-bit for any VST that supports 64-bit.

Some VSTs require converting to 32-bit, and then back to 64-bit.

The output format bitdepth is not relevant until the final downmix for delivery to the output plugin.