More > JRiver Media Center 18 for Windows

Format of .cfg files for convolving

(1/2) > >>

gtandzi:
Hi, I've recently created a bunch of FIR .wav files for convolving my music for my room/system using Acourate, and would really appreciate a clear and concise statement of the structure of .cfg files necessary to use these FIR files within the Options/DSP Studio/Convolution pathways of JR MC. I understood that I needed to create .cfg files using the Sound Forge format (as in http://convolver.sourceforge.net/config.html) but experimentation seems to show that it is sufficient to simply point the JRiver engine to the folder that contains all the impulse audio files in 64bit, labelled by sample rate (eg Cor1S96.wav - as generated by Acourate). Is this correct, and how do I check that it is working properly - in particular, that it is switching filters to match the sample rate of the original file?
Thanks, and apologies if this is answered simply somewhere and I have simply been too dumb and/or impatient to find it.

Matt:
Welcome.

The display in DSP Studio > Convolution shows what filter gets used.  So play different sample rate content and check that it's switching.  If it is, you're all set.

gtandzi:
Weird. It's confusing (to me at least). I originally selected the 96kHz .wav filter, and played a 96kHz music file, and then started mixing up the files, so I was playing different sample rate music files. The sample rate indicator on the DAC changes with the music files, but when i look inside JRiver MC, it appears to be continuing to use the 96kHz .wav filter. Does that mean it's automatically switching, or not?

gtandzi:
OK. More playing. Tried to see if upgrading to MC19 changed anything. No.
Created a bunch of config files, with the labels CorS_441.cfg; CorS_48.cfg; CorS_882.cfg; CorS_96.cfg; CorS_1764.cfg; and CorS_192.cfg (Had to fiddle to get around them being named blahblah.cfg.txt, but eventually did it), each with the format:

(eg CorS_96.cfg)

96000 2 2 0
0 0
0 0
C:\ACR FIR\Cor1S96.wav
0
0.0
0.0
C:\ACR FIR\Cor1S96.wav
1
1.0
1.0

and pointed the Convolution settings to the folder with all the .wav files and .cfg files. Of course it makes you select one of the .cfg files first, so I tried selecting 44.1 and playing a 44.1/16 track.

I open DSP Studio>Convolution, and find the following happening:

It's using the CorS_441.cfg file, with 'normalize volume' & 'Automatically switch..' both selected. Status shows
Processing: 2 paths
Performance: 57.9X realtime (using SSE3) [speed varies slightly]
Filter: blahblah\CorS_441.cfg

Source: 44.1kHz 16bit 2ch       Internal: 44.1kHz 64bit 2ch

BUT, when I select another sample rate -- eg a track that's at 96/24, all that changes is

Performance -- the speed drops to about half
Source: 96kHz 24bit 2ch             Internal: 96kHz 64bits 2ch.

Which makes it appear that it's using the 44.1 filter on the 96/24 files.

Is that so? And if so, what am I doing wrong? Is the mistake to create a bunch of different config files, and I should conflate them all into a single .cfg file, containing all the different 'segments' consecutively?

Thanks

gtandzi:
OK. Yet more experimentation.

This time I created an ALLUP.cfg file with all the various sequences in order (see below) - but this just shows as invalid if you try and select it.

Any more thoughts?

44100 2 2 0
0 0
0 0
M:\ACR FIR\Cor1S44.wav
0
0.0
0.0
M:\ACR FIR\Cor1S44.wav
1
1.0
1.0

48000 2 2 0
0 0
0 0
M:\ACR FIR\Cor1S48.wav
0
0.0
0.0
M:\ACR FIR\Cor1S48.wav
1
1.0
1.0

88200 2 2 0
0 0
0 0
M:\ACR FIR\Cor1S88.wav
0
0.0
0.0
M:\ACR FIR\Cor1S88.wav
1
1.0
1.0

96000 2 2 0
0 0
0 0
M:\ACR FIR\Cor1S96.wav
0
0.0
0.0
M:\ACR FIR\Cor1S96.wav
1
1.0
1.0

176400 2 2 0
0 0
0 0
M:\ACR FIR\Cor1S176.wav
0
0.0
0.0
M:\ACR FIR\Cor1S176.wav
1
1.0
1.0

192000 2 2 0
0 0
0 0
M:\ACR FIR\Cor1S192.wav
0
0.0
0.0

Navigation

[0] Message Index

[#] Next page