Keith_W
Major Contributor
... or any other DSP with only 1024 taps per channel.
Over the weekend, I went to a friend's place to help generate some filters for his system. His system consists of 2 subwoofers and 2 mains, with a MiniDSP SHD, which accepts a 2 channel input, convolves filters, and has 4 analog outputs. It has built-in Dirac, which I am unfamiliar with (and he is not confident that he has used Dirac properly), so my plan was to use Acourate to perform all the measurements and corrections, and figure out how to export it to his MiniDSP. I brought along my RME Fireface UC interface, which has 8 channels analog out.
After I did all the measurements, I made the corrections, and generated a crossover filter for his subwoofers. It looks like this:
Red/Green lines: Left and Right channel generated by Acourate. It looked pretty good, and we had a quick listen using my interface and it sounded great.
However, Acourate has 65536 taps per channel, and to get it to work with MiniDSP I had to cut it down to 1024 taps. Using Acourate's "CutNWindow" function, I reduced the taps down to 1024. This was the result (I have only displayed one channel for clarity):
Note where I placed the marker, this was at about 43Hz. I did a quick calculation - 44100Hz sampling rate / 1024 = bin size 43Hz. In other words, you only have two bins to correct < 100Hz.
You can also see:
- the fine corrections for subwoofer amplitude are gone
- the crossover slope has changed
I have no doubt that this difference would be audible. It is better than no correction at all, but there to me there should be no doubt that with a side-by-side comparison with a more powerful DSP engine, the differences should be heard.
And then there was the issue of exporting these FIR filters to the MiniDSP. My plan was to export the filters from Acourate in .WAV format, then use REW to convert the .WAV to MiniDSP compatible biquad .TXT format. I kept on failing (examination of the .TXT file shows zero values for all the corrections), so I asked a more experienced friend for help since I have never done this before, and this procedure is new to me. That's when I learnt that this particular MiniDSP model does not support FIR filters.
I suppose I knew the difference between 65536 taps and 1024 taps already, but I thought that ASR might be interested to visually see the difference between 65536 taps and 1024.
So, if 1024 taps is not enough, how many taps would be enough? I performed the "CutNWindow" operation again, selecting different tap outputs:
(Apologies for the typo, it should be 8192 not 8182). You can see bass resolution increasing as sample rate goes up. By 32768 taps it is starting to look like a reasonable approximation of the original curve, by 65536 it looks perfectly smooth. I would say at least 8192 taps should be the minimum, but the more you have the better.
At this point you might be wondering whether you can really hear the effect of higher resolution correction. To be honest, I am not so sure myself. I know that there should be a measurable difference which should probably disappear by 32768 taps, but whether this is audible or not is another story.
Over the weekend, I went to a friend's place to help generate some filters for his system. His system consists of 2 subwoofers and 2 mains, with a MiniDSP SHD, which accepts a 2 channel input, convolves filters, and has 4 analog outputs. It has built-in Dirac, which I am unfamiliar with (and he is not confident that he has used Dirac properly), so my plan was to use Acourate to perform all the measurements and corrections, and figure out how to export it to his MiniDSP. I brought along my RME Fireface UC interface, which has 8 channels analog out.
After I did all the measurements, I made the corrections, and generated a crossover filter for his subwoofers. It looks like this:
Red/Green lines: Left and Right channel generated by Acourate. It looked pretty good, and we had a quick listen using my interface and it sounded great.
However, Acourate has 65536 taps per channel, and to get it to work with MiniDSP I had to cut it down to 1024 taps. Using Acourate's "CutNWindow" function, I reduced the taps down to 1024. This was the result (I have only displayed one channel for clarity):
Note where I placed the marker, this was at about 43Hz. I did a quick calculation - 44100Hz sampling rate / 1024 = bin size 43Hz. In other words, you only have two bins to correct < 100Hz.
You can also see:
- the fine corrections for subwoofer amplitude are gone
- the crossover slope has changed
I have no doubt that this difference would be audible. It is better than no correction at all, but there to me there should be no doubt that with a side-by-side comparison with a more powerful DSP engine, the differences should be heard.
And then there was the issue of exporting these FIR filters to the MiniDSP. My plan was to export the filters from Acourate in .WAV format, then use REW to convert the .WAV to MiniDSP compatible biquad .TXT format. I kept on failing (examination of the .TXT file shows zero values for all the corrections), so I asked a more experienced friend for help since I have never done this before, and this procedure is new to me. That's when I learnt that this particular MiniDSP model does not support FIR filters.
I suppose I knew the difference between 65536 taps and 1024 taps already, but I thought that ASR might be interested to visually see the difference between 65536 taps and 1024.
So, if 1024 taps is not enough, how many taps would be enough? I performed the "CutNWindow" operation again, selecting different tap outputs:
(Apologies for the typo, it should be 8192 not 8182). You can see bass resolution increasing as sample rate goes up. By 32768 taps it is starting to look like a reasonable approximation of the original curve, by 65536 it looks perfectly smooth. I would say at least 8192 taps should be the minimum, but the more you have the better.
At this point you might be wondering whether you can really hear the effect of higher resolution correction. To be honest, I am not so sure myself. I know that there should be a measurable difference which should probably disappear by 32768 taps, but whether this is audible or not is another story.