INTERACT FORUM

Please login or register.

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

Author Topic: 176.4 & 352.8 convolution filters not automatically switching  (Read 748 times)

whoareyou

  • Galactic Citizen
  • ****
  • Posts: 439
176.4 & 352.8 convolution filters not automatically switching
« on: January 05, 2022, 09:28:28 am »

When setting convolution to auto switch, everything switches as expected except for 176.4 and 352.8 rates.
The convolution status never shows these files as current filter.
All other rates work as expected

I am configuring via audiolense cfg files.
Each of these filters load as expected if explicitly selected, but  JRiver will not auto select them.

Any suggestions?



Logged

JimH

  • Administrator
  • Citizen of the Universe
  • *****
  • Posts: 72534
  • Where did I put my teeth?
Re: 176.4 & 352.8 convolution filters not automatically switching
« Reply #1 on: January 05, 2022, 09:34:51 am »

Try using MC's DSP Studio > Output Settings to resample those to something that your sound device supports.
Logged

whoareyou

  • Galactic Citizen
  • ****
  • Posts: 439
Re: 176.4 & 352.8 convolution filters not automatically switching
« Reply #2 on: January 05, 2022, 09:50:07 am »

These rates are supported by my DAC (Exasound E38), so doubtful this is issue.
Everything plays fine for the 352.8 and 176.4 rates when the config files are explicitly configured.

Is it possible the correct filter is loaded but JRiver status is not properly reflecting the selected filter? 

I am asking because although the Status indicates the wrong filter, the SSE real-time Performance has slowed to a level that seems to indicate the proper filter is probably loaded.   

I don't have time to further investigate at moment, but based on JRiver reported performance, that seems like it could be happening.

Thanks



Logged

whoareyou

  • Galactic Citizen
  • ****
  • Posts: 439
Re: 176.4 & 352.8 convolution filters not automatically switching (solved)
« Reply #3 on: January 06, 2022, 07:37:54 am »

Issue was that naming convention did not follow JRiver naming convention.

My files were named 1764.cfg and 3528.cfg and JRiver is expecting 176.cfg and 352.cfg.
So, a bit of inconsistency with the other sample rates of 44.1 and 88.2, which are expected to be 441.cfg and 882.cfg

Would be very nice if the regular expression could be changed to accept file name with or without the decimal portion of sample rate.

Thanks
Logged
Pages: [1]   Go Up