INTERACT FORUM

Please login or register.

Login with username, password and session length
Advanced search  
Pages: [1]   Go Down

Author Topic: MC18 bitdepth fixed 64bit  (Read 1389 times)

jacqlan111

  • Junior Woodchuck
  • **
  • Posts: 95
MC18 bitdepth fixed 64bit
« on: July 14, 2013, 07:50:30 pm »

Hi
My computer seems not to be able to manage 24/176khz files without stuttering.  At 96khz the cpu runs at around 12% of it's capacity but at 176 or 192 Khz some stutters appear and it goes up to 54% and higher peaks.  

Audio format is automatically set at 64bits as i can see in the audio format window.  I think that in MC17 (not sure) manual setting at "source bitdepth" was keeping it at 24 bits for  24/176 files.  Now i can't find a way to reduce it from 64 to 24bits, does it make a difference?  
This computer should not be in trouble.

I use a RME audio card (AES 32) and 2 DACs limited at 176 khz, and 2 at 192 khz (8 ch).  This is why i want to manage files up to the maximun dac capacity.

Meanwhile i must keep playing file not higher than 96 khz.  Could it be the MC18 automatic 64 bit setting that is shifting the CPU from 12 to 54% ?
Logged

jacqlan111

  • Junior Woodchuck
  • **
  • Posts: 95
Re: MC18 bitdepth fixed 64bit
« Reply #1 on: July 14, 2013, 08:52:03 pm »

Meanwhile i must keep playing file not higher than 96 khz.  Could it be the MC18 automatic 64 bit setting that is shifting the CPU from 12 to 54% ?
The answer must be no, i just realized that it is the same 64 bits setting for both the 12% and 54% cpu demand.  The difference must come from the sample rate from 96 to 176 khz.
Logged

Matt

  • Administrator
  • Citizen of the Universe
  • *****
  • Posts: 42323
  • Shoes gone again!
Re: MC18 bitdepth fixed 64bit
« Reply #2 on: July 14, 2013, 09:05:34 pm »

MC18 improved audio bitdepth handling, but is no difference in performance (faster if anything) than MC17.  A little more here:
http://yabb.jriver.com/interact/index.php?topic=80522.msg548095#msg548095

However, playing a 176 or 192 file with no resampling should not require a lot of CPU.  If you're getting stuttering, increasing buffering in Options > Audio > Output mode settings might help.
Logged
Matt Ashland, JRiver Media Center

jacqlan111

  • Junior Woodchuck
  • **
  • Posts: 95
Re: MC18 bitdepth fixed 64bit
« Reply #3 on: July 15, 2013, 07:06:28 pm »

MC18 improved audio bitdepth handling, but is no difference in performance (faster if anything) than MC17.  A little more here:
http://yabb.jriver.com/interact/index.php?topic=80522.msg548095#msg548095

However, playing a 176 or 192 file with no re sampling should not require a lot of CPU.  If you're getting stuttering, increasing buffering in Options > Audio > Output mode settings might help.

Thank you Matt, in your answer you made me think of a question about side effects having the re-sampling option in the path.  Is there a difference between setting mc18, as example, for a 96khz input, selected to "no change" from selected at "96" (96 to 96)?

I'm asking this because when i eliminate re sampling, (say 44 and 88 to 96), to "no change", there is less or no stutters.  The bad side of it is cracking noises at  sample rate changes from hardware.  There is no noise when the card sample rate stays the same for all files (all at 96 or all at 176) but stutters are back for sample rate files 176 and 192.

For buffering I usually set it at 5 sec and I checked the highest hardware buffering box.  The same for pre-buffering.  However I wonder what is happening if i check this box and also set the audio card buffering option to the highest level from the RME setting pannel.  Two time setting??

Logged

Matt

  • Administrator
  • Citizen of the Universe
  • *****
  • Posts: 42323
  • Shoes gone again!
Re: MC18 bitdepth fixed 64bit
« Reply #4 on: July 15, 2013, 08:42:25 pm »

Thank you Matt, in your answer you made me think of a question about side effects having the re-sampling option in the path.  Is there a difference between setting mc18, as example, for a 96khz input, selected to "no change" from selected at "96" (96 to 96)?

They'll function exactly the same.

I suppose the program could hide the option so "96 to 96" isn't a possible selection, but internally it will do the exact same thing as picking 'No change.'
Logged
Matt Ashland, JRiver Media Center
Pages: [1]   Go Up