Few questions from potential AL user

jrobbins50 · Feb 26, 2024

I’d bet that is adequate for running Audiolense 2 channel and also to host your filters if you want Roon as your convolution engine. Try it and see. JCR

Ofer · Feb 26, 2024

I will add a few notes. A lot is affected by filter length and the number of filters run. If you use 32k-65k filters then it doesn't take much, my experience is with 44.1k/48k. If you run longer filters 130k it takes more. I use HLC which enables you to run several filters and compare them. For some reason even though only one filter is 'playing' the others take CPU load. In a setup similar to yours I can't load more then 3-4 long filters at once without getting cracks and crinkle, even in the highest buffers.

jrobbins50 · Feb 27, 2024

And as a data point on the more extreme side, I use an i9-10900K processor and an RTX 2080Ti video card to enable HQPlayer to convert DSD64 5.1 files to 352.8 PCM for application of Audiolense XO convolution filters, and then to upscale back to DSD64 for native playback on the Okto dac8pro. My processor and video card can just barely handle this. I can’t do upscaling to DSD128 for 5.1 files without stuttering. Your setup doesn’t require this kind of horsepower and mine still is not enough to take full native multichannel advantage of the Okto unit. It still sounds great. JCR

whoareyou · Mar 1, 2024

jrobbins50 said:
And as a data point on the more extreme side, I use an i9-10900K processor and an RTX 2080Ti video card to enable HQPlayer to convert DSD64 5.1 files to 352.8 PCM for application of Audiolense XO convolution filters, and then to upscale back to DSD64 for native playback on the Okto dac8pro. My processor and video card can just barely handle this. I can’t do upscaling to DSD128 for 5.1 files without stuttering. Your setup doesn’t require this kind of horsepower and mine still is not enough to take full native multichannel advantage of the Okto unit. It still sounds great. JCR

How many paths are in your filters?

I have 14 paths for a 5.2 system, each speaker with XO, and with JRiver and HLConvolver I can load one filter bank DSD->352.8 conversion. Any more and I have stuttering. Converting to 176.4 I can have 4 filters loaded simultaneously.

This is with i7-12700k processor.

jrobbins50 · Mar 1, 2024

15 paths for my 5.1.2 system. I load my 352.8 convolution filters in wav format into the Pipeline Matrix of HQPlayer. I’d really like to use HLC but Mitch and I were unable to get it to configure properly in my setup. JCR

juicehifi · Mar 4, 2024

dima1stg said:
In the mean time I just downloaded AL. Selected surround version because of subs. While trying to do the first measuremet for 2.1 config - hitting the error. Please see attached.

I believe your mini-dsp unit only has stereo input. In other words it is impossible to access the sub directly from the PC. Therefore, as long as you use the mini-dsp you should treat your speaker setup as a regular stereo system in Audiolense ... and setup the bass management and crossover configuration before you measure.

In fact, I recommend that you use some IIR filters in the mini-DSP to take it as far as it goes. The FIR capacity is limited and ability for Audiolense to correct in the bass will be reduced. But if you get the bass reasonably level by using IIR filters in the mini-dsp unit you could get a pretty good end result here. The limited FIR capacity may also pose significant limitations on the time domain correction, and you may need to tweak more for the best result. You will get a much easier calibration process and better sound if you replace the miniDSP with a sound card or dac that lets you do multichannel streaming to your speakers and drivers.

Few questions from potential AL user

jrobbins50

Member

Ofer

Member

jrobbins50

Member

whoareyou

Member

jrobbins50

Member

juicehifi

Audiolense

Popular tags

OUR MISSION

Quick Navigation

Buy us a cup of coffee!