INTERACT FORUM

More => Old Versions => JRiver Media Center 18 for Windows => Topic started by: dean70 on February 22, 2013, 09:24:45 pm

Title: SACD Library tags
Post by: dean70 on February 22, 2013, 09:24:45 pm
Is it possible to tag SACD ISO tracks with bit depth and sample rate? At the moment these fields are blank (and locked), which is causing issues with a view for HD Audio, which has the file display rules as bit depth > 16 and sample rate > 44100. Something like bit depth=64 and sample rate as 352800 (for DSD64), would make it easier to define views.

Title: Re: SACD Library tags
Post by: kstuart on February 22, 2013, 09:40:10 pm
The correct Bit Depth for SACD is 1 (yes, "one").

The "64" refers to the amount of oversampling.

See:

http://en.wikipedia.org/wiki/Direct_Stream_Digital

As far as Views, just use the following rule (use import/export to add) to show only 24-bit and SACD:

([File Type]=[sacd] or [Bit Depth]=24)

( Currently, "Bit Depth > 16" does not work, because MC18 falsely reports some files as having Bit-Depth of "32", see:  http://yabb.jriver.com/interact/index.php?topic=78241.0  )
( "sample rate > 44100" does not work for me, because it leaves out the 24-bit 44.1 khz Beatles files, and includes 16-bit 48khz files that are not really High Resolution )

Title: Re: SACD Library tags
Post by: dean70 on February 22, 2013, 10:06:28 pm
Thanks I will give that a try. I was using the UI, which only allows an and relationship, eg: >44100 and >16 bit depth. Did not know you could use import to enter manual expressions.
Title: Re: SACD Library tags
Post by: MrC on February 22, 2013, 10:14:25 pm
Hover immediately to the left of the first rule.  You'll see the OR parenthesis, etc.
Title: Re: SACD Library tags
Post by: dean70 on February 23, 2013, 05:05:48 am
I noticed it had added the parenthesis after entering the expression above.  It works well  :D

On another note I have noticed a firecracker like pop at the start of playback if the Output mode setting for sample rate over 192000 is set to 192000. Setting to 176400 alleviates this (I assume because it divides evenly down from 352800Hz).