New Audiolense releases

[juicehifi]

@juicehifi - In my case, it's approaching a year since paying the extended support and upgrade fee.
Although there are no showstopper defects, it would have been nice to receive a program update addressing some of the issues / enhancements discussed over the course of that year.

Can you provide any information as to when your schedule will allow for releasing a program update?

I realize and appreciate that a product takes time and effort to support, but I would also like to receive some type of product improvements from time to time.
Thanks

I can understand why you’re asking. And I guess some progress reporting is due here.

The plan for the next release is direct resampling of correction filters and Atmos support.

This has not been the best year for Audiolense development with documented progress. About a year ago I was working on an API for the convolver to enable 3rd party GUI development. Unfortunately that work hasn’t surfaced yet. I need to do at least one more rotation. Then some of you guys may be able to make your own GUI. And then I have one or two GUI ideas in my own.

By the start of this year I was forced to abandon my old provider of accounting system and webstore, which took most of the available Audiolense time in the first half year. That job isn’t fully completed yet, but when I’m done I will have a very effective system for most of the paperwork associated with this small business … and I expect it to be that way for years to come. So there has been plenty of development there, just not on the software. When I’m done I will be able to spend most of the time on development and support, which is what I really want to spend time on.

This autumn I have also been very busy with my other job, so progress has been a bit slower than normal for this time of the year. But I have good hopes of getting the new release out by end of January.

 

[juicehifi]

Audiolense 6.22 is out


Audiolense 6.22 (64 bit)

Audiolense 6.22 (32 bit)

• New optional correction filter resampling. The time duration of the filter is kept intact on the resampling, so there will be no truncation of the low frequency correction. The frequency response is extended on upsampling, but frequency and time domain behavior is practically identical within the common bandwidth. The upsampling supports rates up to 5.6 million Hz. Upsampling to very high frequencies will be disabled when an upsampling will exceed the maximum filter-length, which is limited by the capacity of the math library used in Audiolense. The solution then is to shorten the filter length in the correction procecure designer until the desired sample rate is enabled.
• Added phase view, with wrapped and unwrapped phase.
• Modified draw charts functions to support phase switching.
• Removed delete rows in speaker setup since it caused unanticipated problems. The delete button gets the job done…
• Updated the help file, which now only comes as a PDF.

 

[whoareyou]

HI. To look at new features, I installed demo version (my license has expired). With same settings, filters, etc. my simulations are very different. For example ....
Same correction filter ("10"), target, setup, measurement, polarity correction disabled . Just doing a quick sanity check but you should get the idea of what I see (I hope).
I've upgraded several times prior to this and never had this happen to me. Suggestions?

Also, just a small request. When running program in demo mode it always seems to destroy all of the current correction filters. Anyway you can change program so that it doesn't wipe them out?

Thanks

 

[juicehifi]

Mine are identical as before, but if you could send me the measurement file you were using here I will check this out.

 

[whoareyou]

Mine are identical as before, but if you could send me the measurement file you were using here I will check this out.

Files should be in attached zip of my original post. Thanks

Edit: I just looked everything over once again and can't find any different settings. Frequency simulations are also different and if you look at the step simulation each speaker looks kind of like a linear phase rather than Minimum phase response. The target included with the zip file is minimum phase.

 

[sledwards]

I concur that something is going on with 6.22. See attached freq resp plots. Created with the same correction procedures.

 

[juicehifi]

Yes this doesn’t look right. I’ll give it a try tomorrow. If I don’t find it fast then, it may take a couple of weeks.

 

[juicehifi]

[31 jul 2024]

Audiolense 6.23 (64 bit)
Audiolense 6.23 (32 bit)


• A driver alignment error was unfortunately introduced in 6.22, which is fixed now.
• Fixed a bug related to manual speaker/driver delay entry.

I've put the same relase date on this, and 6.22 should not be used when digital crossovers are used.

Thank you @whoareyou and @sledwards for pointing out the problem.

 

[sledwards]

@juicehifi

I was trying to test out the new Resample Correction feature and am wondering what I may be doing wrong. When I select the output rate (96kHz or any other value), I get the error shown in the attached file.

Steve

 

[Rsg11]

@juicehifi

I was trying to test out the new Resample Correction feature and am wondering what I may be doing wrong. When I select the output rate (96kHz or any other value), I get the error shown in the attached file.

Steve

I suspect this error is due to the filter length, as described in the notes for the 6.22 release:

• New optional correction filter resampling. The time duration of the filter is kept intact on the resampling, so there will be no truncation of the low frequency correction. The frequency response is extended on upsampling, but frequency and time domain behavior is practically identical within the common bandwidth. The upsampling supports rates up to 5.6 million Hz. Upsampling to very high frequencies will be disabled when an upsampling will exceed the maximum filter-length, which is limited by the capacity of the math library used in Audiolense. The solution then is to shorten the filter length in the correction procecure designer until the desired sample rate is enabled.

 

[sledwards]

@Rsg11

Thanks, didn't quite understand the warning. It seems like the best solution after playing with this feature is just to write out correction filters with no upsampling (48kHz in my case) at the highest filter length available in the correction procedure designer (131072). I use HQPlayer for convolution, and it will expand high frequency when the music base sample rate exceeds 48kHz. Please correct me if this thinking seems flawed.

 

[juicehifi]

@juicehifi

I was trying to test out the new Resample Correction feature and am wondering what I may be doing wrong. When I select the output rate (96kHz or any other value), I get the error shown in the attached file.

Steve

Hi Steve,

You have stumbled over a bug. I am not able to reproduce it here. Could you be so kind and send me your measurement, target and all the correction details?

 

[juicehifi]

[31 jul 2024]

• Beta release. Consider it a beta release for now. I’ll remove this remark if it turns out all right.
• A peak-finding procedure had to be reworked to function properly with the new resampling. This procedure is widely used for speaker and crossover alignment, therefore the beta status for now.
• A small rounding error on the peak finder was discovered, the fix may lead to improved alignments in some setups.
• Detected a small target display error that was fixed.
• Disabled saving of frequency range in the charts, which has caused problems for users frequently.

Audiolense 6.24 (64 bit)
Audiolense 6.24 (32 bit)

 

[sledwards]

@juicehifi

The new resample filter is working well when I compare the magnitude of the .wav filters (96kHz and 192 kHz) to the correction filters. All curves match well. However, when I compare the phase of the resampled filters to the correction filters, I see differences as shown in the attached plots. Should not the resampled filter phase match that of the correction filters?

Steve

 

[juicehifi]

They are probably a lot closer thann this. … but this view is a wrapped phase. In the unwrapped, the top will likely be faster since the high end has been extended.

Personally I mostly look at the time domain and frequency domain.

I am happy if the peak matches and the frequency domain looks clean. And regarding clean … I’ve spent more than a few weeks trying out various alternatives. The difference from before is most unlikely to be audible in most imstances, but in the long run technical quality will get the upper hand. If it does not improve sound quality for the majority, it may give a more predictably & excellent result for everybody. So I aim for technical perfection when I attach such issues, regardless of what I believe of the threshold of hearing and sonic impact short term.

 

[juicehifi]

It appears that the resampling wasn't complete yet...

[31 jul 2024]

• Beta release. Consider it a beta release for now. I’ll remove this remark if it turns out all right.
• Corrections for the native frequency was not saved for all correction formats. This has been fixed.

Audiolense 6.25 (64 bit)
Audiolense 6.25 (32 bit)

 

[juicehifi]

It appears that the resampling wasn't complete yet...

[31 jul 2024]

• Beta release. Consider it a beta release for now. I’ll remove this remark if it turns out all right.
• Corrections for the native frequency was not saved for all correction formats. This has been fixed.

Audiolense 6.25 (64 bit)
Audiolense 6.25 (32 bit)

There are no errors reported on 6.25, so I assume all the important bugs have been taken care of.

 

[whoareyou]

When taking measurements, 6.25 AL has closed without any type of error message on several occasions. No critical error messages or warning displays prior to AL shutting down.
I simply restart the app and measurment and then all is good again.

Never had this happen before, but now with 6.25 it's happened on several occassions. Motu MK-5 and Isemcon microphone, all ASIO.

Is there any logging that can be looked at if this happens again? It's very sproadic, but quite annoying and I never had this occur before 6.25.

 

[juicehifi]

I do not recall any changes in the recording for a long time. But Windows and dotNet sometimes work in misterious ways.

If I were you I would measure with the release that is more stable on measurements and load it into the most recent release. And if you see a pattern in the problems that I can work on I’m all ears.

 

[Urs]

When taking measurements, 6.25 AL has closed without any type of error message on several occasions. No critical error messages or warning displays prior to AL shutting down.
I simply restart the app and measurment and then all is good again.

Never had this happen before, but now with 6.25 it's happened on several occassions. Motu MK-5 and Isemcon microphone, all ASIO.

Is there any logging that can be looked at if this happens again? It's very sproadic, but quite annoying and I never had this occur before 6.25.

This happened to me also just recently. But only twice and I am using v6.22. Therefore I am more looking at Windows than at Audiolense (or its latest updates)

 

[juicehifi]

[26 oct 2024]

Audiolense convolver 1.8.exe

Extended volume control. Now you can adjust the volume without exiting the fullscreen.

Mouse functions has been implemented for better access to the volume control. There are now the following options:

• Tray icon and form only (the same as before)
• show volume control on mousemove – on fullscreen only
• show volume control on mousemove – everywhere
• Volume and mute with mouse wheel and wheel button on fullscreen only
• Volume and mute with mouse wheel and wheel button everywhere

A minimised version of the volume control is displayed when the volume is activated from outside the tray icon / form. This minimised version can be dragged by the mouse to a desired location and will remember the location.

In addition:

• Fixed a couple of screen scaling issues on rarely used forms.
• Fixed a broken link to the help file.
• Fixed a bug on the form moving feature that often led to reset the location. Various minor fixes to smoothen the user experience.

Note: Your current settings will be overwritten when the convolver is started for the first time.

 

[juicehifi]

While we're on a roll here:

[26 oct 2024]

• Atmos support, including support for adding custom speakers.
• The gui had to be reworked to support the customization of speakers.
• Several standard Atmos speaker setups and formats are included up to 9.1.6

Audiolense 6.26 (64 bit)
Audiolense 6.26 (32 bit)

 

[e1guapo]

While we're on a roll here:

[26 oct 2024]

• Atmos support, including support for adding custom speakers.
• The gui had to be reworked to support the customization of speakers.
• Several standard Atmos speaker setups and formats are included up to 9.1.6

Audiolense 6.26 (64 bit)
Audiolense 6.26 (32 bit)

Thank you so much Dr Bernt!

 

[whoareyou]

Thank you so much Dr Bernt!

Any chance you can implement a user configurable global background color for the graphs? This was discussed long time ago, and you thought it was possible. I know it's not really new "functionallity", but when you are dealing with multiples of speakers, like Atmos, some of the individual speaker's measurements disappear into that yellow background . It's a real pain to have to go and change this setting for every graph, and the change is not persisted. Constantly changing this setting is a real pain in the neck.

 

[juicehifi]

I'll look into it.