Recent content by juicehifi

I think I may haven taken care of that in the code quite some time ago. Try and see if it works.

[27 june 2025] Audiolense 7.2 (64 bit) Audiolense 7.2 (32 bit) Brought back the measurement quality report on unsuccesful measurements Eliminated a minor bug in the measurement that could lead to unhandled exception. Fixed improper initialisation related to the speaker connection check...

[24 jun 2025] Audiolense convolver 1.11.exe Fixed a bug related to the manual output selection.

You could wire them in parallel and just let Audiolense see the couple as one single sub. They maye have a small timing difference between them, but if you place them symmetrical I believe it will be insignificant at these frequencies. And if you don't want to correct their combined response you...

[22 jun 2025] Audiolense convolver 1.10.exe Fixed a few minor gui display issues. Implemented the improved resampler that has been in use in Audiolense for a while Implemented support for the revised AL correction format, needed to supppport very high channel count. This version is...

That was a complex setup and I am not sure I understand if there's a question there.

Audiolense does not support that. You can treat the two subs as a single entity ... a sub with two drivers running in parallel. It will still do individual correction, but also a combined one. It's the closest you will get.

[20 june 2025] (beta) Audiolense 7.1 (64 bit) Audiolense 7.1 (32 bit) Speeded up additional processes with parallel processing. Fixed a bug where low pass was omitted on subwoofers if they were not also used to bass offloading. Known issues: There are errors in the progress reporting...

I think you should proceed with these measurements. I believe they are good. The first negative peak is interpreted as the peak of the midranges here, that's why the mids are interpreted to arrive earlier than the tweeters. For a TTD correction the peak finding has no consequence unless you...

Yes, that doesn’t look right. Could be only the numbers, though. How do the pulses look? Do they have the anticipated delay?

I have already implemented a very similar filter format, so this could be made possible with a limited effort. However, the ratio filterlength to samplerate gives a filter duration of around 46 ms. FOr TTD correction this is reasonably effective down to around 200 Hz, but not quite...

Probably doesn't matter since the upsasmpling will be above human hearing frequency.

Are you sure it Hypex DSP has FIR processing capabilities? A few years back they only did IIR filtering, but perhaps things have changed since. If so, what are they and what is the filter format?

There's a manual procedure, but you beat me to it. Anyway you should have the key now.

I prefer 6 dB and sometimes higher to get the result I want. But there’s no correct answer here.