New Audiolense releases

Hi Bernt,

I’m running into a consistent issue trying to use a MOTU UltraLite mk5 for multichannel measurements in Audiolense (latest version 7.5), and I’ve narrowed it down pretty carefully but can’t seem to resolve it. I’m working with a 6-channel active setup.

If I run in simple stereo mode using MOTU ASIO for both input and output, everything behaves exactly as expected. The sweeps are clean, the impulse response looks correct, and the timing is stable and physically believable.

As soon as I switch to multichannel (6 channels) using MOTU ASIO for both input and output, I get a repetitive chirp or pulse-type artifact riding on top of the sweep. This happens even with the microphone unplugged, which makes me think the playback signal is somehow being fed back into the input stream internally. I’ve verified that loopback is disabled and all CueMix inputs are muted, so it doesn’t appear to be a straightforward routing issue.

If I instead use MOTU ASIO for playback and WASAPI for recording, the sweep itself becomes clean with no chirp, but then the timing is completely wrong. The reported delays are large, inconsistent, and not physically plausible, and they vary between runs, so it doesn’t seem to be just a fixed offset problem.

So at this point I can get either clean audio with invalid timing, or correct timing only in stereo, but not a valid multichannel measurement. Since stereo ASIO works correctly, it seems like the hardware and driver are fundamentally fine, but something about multichannel ASIO input or how Audiolense is interpreting it may be introducing an internal return path.

Have you seen this behavior with MOTU interfaces before, or is there a recommended way to ensure Audiolense only captures the actual analog input and not any internal playback signal when running multichannel?

I’m planning to move to separate devices for input and output if needed, but I wanted to check first in case there’s a proper way to make this work with a single interface.

Thanks for any insight — I feel like I’m very close but missing one piece.

Steve
 
The measurement is done using a multichannel wave file with sweep in only one channel at a time. So this does not come from Audiolense.

Most audio drivers have issues, vut some more than others….

Try to play around with different apis (Wasapi, Direct Sound, WinMME), use a low sample rate … and try with Asio4All too. And perhaps align the default windows audio settings with the ones you use for measuring.
 
Hi @juicehifi
Hoping that for next release you could take another look at the high DPI settings for a couple menus? Most important, at least for me :), is partial corrections in CPD as last two rows (left top back/RTB) are not displayed for a 7.1.4 system because scrolling stops too soon and before rows come into view. Because of this, only way to configure speakers in these last two rows is to change to low resolution setting. With lower resolution, scrolling works as expected. It can be done, but it is a real pain in neck as all the graphing is low resolution.
Other nice to have would be if the chart editor could be made to work with high dpi resolution.
 
This is a 4k TV with scale set to 300% as recommended by windows. Other windows scaling factors don't seem to help.
Setting this screen's resolution to 1920 x 1080 brings the rows into view, but then graphs become hard to see, so it's switching back and forth via windows settings.

On native 1920 x 1080 at 100% computer monitor, everything works as expected and graphs are fine.
 
3840 x 2160 - Native 4k via hdmi from my computer.
 
Back
Top