Recent content by juicehifi

Why would you want to measure them separately? You will not be able to control them separately with Audiolense. Instead you have to let the crossovers live in the DSP and do only global correction with Audiolense. You can get great results that way, but the work flow will be more cumbersome.

Yes it makes sense to calculate the minphase response of the microphones, since they are minphase transducers. And it takes out any nonminimum phase artifacts that might otherwise be introduced. The multiseat accounts only for frequency responses for the other measurements.

[29 apr 2025] (beta) Audiolense 7.0 (64 bit) Audiolense 7.0 (32 bit) This revision is a major workover to assure that up to 128 channels of correction works in practice. 128 channels is the max allowed in Asio. This workover has led to numerous and far-reaching changes to improve speed and...

No it is not possible to average several measurements like that. You will achieve the same if you increase the length of the sweep. But my experienc is that the upside of this is only theoretical. I never use more than 10 s sweeps, and some users prefer 3 s. Microphones are minimum phase...

I forgot to respond to the 3-way plate-amp. I am running a pair of two-way speakers driven by plate-amps from Hypex myself. I did set up a correction and crossover the Hypex way first, with IIR crossovers and some voicing ... without being too picky about the voicing. Then I measured and...

You need Audiolense XO. With miniDSP you probably have to (and should anyway) create & run the crossovers with IIR filters, and let Audiolense work as a fullrange correction. This works fine, btw. With Roon this should be fairly straight forward. It can be quite easy getting started with...

I took a look at it. This is very unusual. Important information is missing in your ini file. I don't know how that happened, but I am not able to replicate the problem here. Try to delete the al ini file and start over. And please let me know how it goes.

I'm afraid this is more or less a useless measurement. Gross timing errors and perhaps other problems as well. Actually I am working on something now that may help here. Next release, and coming up soon. In the mean time try different measurement settings and check that everything is OK...

If you send me the al ini file (in the program data folder), the target file and tell me which correction procedure you were using, maybe I can replicate it here. And if I can replicate it I can fix it.

Yes, there will be very small differences on gd and ir for a different target.

Inverted gd in the below 100 Hz isn't that uncommon. It typically can happen at a strong cancellation. I can't say whether that's the case here, though. About the focus. You should examine the measurement close if you haven't. About aggressive top: That may have something to do with your...

I was thinking of something like this:

What do the measured impulse responses look like? Can you pust a zoomed image of the two?

Hi Climbclimb, The default in the measuremen module is minus 20 dB. It is set low to protect rigs with very high sensitivity. Perhaps you need to crank it up a few dB?

I'd say yes for Audiolense. There may be slightly more people who experiences measurement problems now than a couple of years back, but it's hard to say. The convolver is very stable.