Beginner trying to figure stuff out.

[juicehifi]

The drop-off is mostly left alone by Audiolense in the default configuration. So a target that goes out right will lead to a correction that does the same. Furthermore, you can tweak the top of the correction to be even more minimalistic by using the partial correction functionality.

 

[Bobski321]

Is there any way to reset the full zoom?

For whatever reason, when I left click and hold to up-left full zoom, it only zooms back to show 1-13,500Hz.

It's not letting full zoom out anymore.

 

[Bobski321]

Actually, I'll probably just have to find a settings file or something.... So I can delete it and then do a reinstall.

Edit: OK, I can't find the right file to delete. Please help.

 

[moedra]

Actually, I'll probably just have to find a settings file or something.... So I can delete it and then do a reinstall.

Edit: OK, I can't find the right file to delete. Please help.

You can adjust the values in the chart editor, under the Axes tab...
Change the Left and Bottom axis values.

 

[Bobski321]

Perfect, thank you. I was digging around in that menu.... But I couldn't really wrap my head around it. It's actually pretty easy. LOL

 

[Bobski321]

So....right now I'm using a STEINBERG UR12 for my mic pre, and a SoundID Reference XLR mic from Sonarworks.

What mic and pre would be recommended as an upgrade?

I was looking at a Earthworks M23 for a mic....but not sure what would be a better mic/pre then what I'm using.

Any recommendations?
Thanks

 

[Bobski321]

Or maybe the m23 is overkill...you mentioned that Audiolense doesn't correct much after 20khz anyway, and my speakers only go down to 40hz(ish).

What do you think?

 

[whoareyou]

Or maybe the m23 is overkill...you mentioned that Audiolense doesn't correct much after 20khz anyway, and my speakers only go down to 40hz(ish).

What do you think?

A good (calibrated) microphone certainly doesn't hurt, but for me and others, the big difference maker is probably the computer interface and that its input and output channels use the same clock.

 

[Bobski321]

A good (calibrated) microphone certainly doesn't hurt, but for me and others, the big difference maker is probably the computer interface and that its input and output channels use the same clock.

Yeah, I noticed an improvement when I went from a umik-1 to what I have now. I'm just curious if the M23 will make a difference at all.... I might just take the risk.

Cool thing is, with HQplayer.... You can switch convolution files on the fly. Takes a second to switch over, but makes comparing super easy. I think that's what I'll do... And I'll definitely report back.

 

[Ofer]

Yeah, I noticed an improvement when I went from a umik-1 to what I have now. I'm just curious if the M23 will make a difference at all.... I might just take the risk.

Cool thing is, with HQplayer.... You can switch convolution files on the fly. Takes a second to switch over, but makes comparing super easy. I think that's what I'll do... And I'll definitely report back.

Can you adjust gain between the filters in HQplayer? It is super important to have the filters play at the same volume when comparing, otherwise louder almost always sounds better.

 

[Bobski321]

Can you adjust gain between the filters in HQplayer? It is super important to have the filters play at the same volume when comparing otherwise louder is almost always sounds better.

Yes you can. And yes, having all the filters the same volume when comparing is absolutely necessary....like you say.

I'm not sure if other playback programs can do instant convolution switching on the fly but....without it, it's crazy how easily our brains start to take over on what we think we hear.

You can even use the free version for 30 minutes before it shuts down... More than enough time to compare different Audiolense settings.

 

[Ofer]

I use HLC and it is basically designed to allow filter comparison on the fly. HLC can be integrated into software that don't have that feature like JRiver as a VST plugin.

 

[Bobski321]

I use HLC and it is basically designed to allow filter comparison on the fly. HLC can be integrated into software that don't have that feature like JRiver as a VST plugin.

Nice

Also in HQplayers matrix profile, when I name the profile with the appropriate convolution files/settings.... I just randomly press keys on the keyboard without looking, so that I don't actually know what I'm saving each different convolution as.

That way when I do comparisons, I don't know what is what.... I just make observations like, is "A" better then "B". Then after I'm satisfied I can identify what each is doing, at the end I'll check which setting was actually what specific convolution file. Hope that makes sense...LOL.

 

[Ofer]

Nice, that is taking it up a notch to almost blind A/B testing.

 

[whoareyou]

Yeah, I noticed an improvement when I went from a umik-1 to what I have now. I'm just curious if the M23 will make a difference at all.... I might just take the risk.

Cool thing is, with HQplayer.... You can switch convolution files on the fly. Takes a second to switch over, but makes comparing super easy. I think that's what I'll do... And I'll definitely report back.

I don't have time to search at moment, but I know I posted (somewhere in AL group) a link to comparison of bunch of calibrated microphones. From perspective of frequency response, they all performed pretty much the same. . I switched from a umik-1 to isemcon but it was only because of the timing issues I experienced measurement to measurement. Some people don't seem to have the issue.

No way to prove it, but I believe if timing wasn't an issue, my results would not been any different between the two microphones.
My umik-1 is also custom calibrated, and for me that also made a difference. My umik-1 did not fit the "average" calibration data supplied for the batch.
Comparing the custom to stock calibration files, I was surprised with some of the differences as they were significant i.e. not just a couple db here and there.

 

[Bobski321]

I don't have time to search at moment, but I know I posted (somewhere in AL group) a link to comparison of bunch of calibrated microphones. From perspective of frequency response, they all performed pretty much the same. . I switched from a umik-1 to isemcon but it was only because of the timing issues I experienced measurement to measurement. Some people don't seem to have the issue.

No way to prove it, but I believe if timing wasn't an issue, my results would not been any different between the two microphones.
My umik-1 is also custom calibrated, and for me that also made a difference. My umik-1 did not fit the "average" calibration data supplied for the batch.
Comparing the custom to stock calibration files, I was surprised with some of the differences as they were significant i.e. not just a couple db here and there.

Ya, I appreciate your input. The microphone I bought, is supposed to be individually calibrated. I actually went on their Sonarworks website, and typed in a bunch of sequential serial numbers just so I could compare all the calibration files and see if there were slight changes in every file... And there was. So it seems like Sonarworks doesn't do basic batch calibration files. Each one is unique.

It almost sounds like the vibe people are putting out is, buying the Earthworks M23 is going to generally be a waste of money..... hmmmm.

 

[juicehifi]

I don't have time to search at moment, but I know I posted (somewhere in AL group) a link to comparison of bunch of calibrated microphones. From perspective of frequency response, they all performed pretty much the same. . I switched from a umik-1 to isemcon but it was only because of the timing issues I experienced measurement to measurement. Some people don't seem to have the issue.

No way to prove it, but I believe if timing wasn't an issue, my results would not been any different between the two microphones.
My umik-1 is also custom calibrated, and for me that also made a difference. My umik-1 did not fit the "average" calibration data supplied for the batch.
Comparing the custom to stock calibration files, I was surprised with some of the differences as they were significant i.e. not just a couple db here and there.

That is what I generally think about this too. In addition, the microphone has to have a decent calibration file. This is usually the case, but not always.

 

[Bobski321]

So.... I ended up buying the M23 microphone. Using HQplayer, I was able to save both convolution files from each microphone, and compare them on the fly, and switching back and forth instantaneously.

Could I hear a difference... YES.

Does the convolution file from the M23 sound better.... YES.

Is it enough difference to justify the cost...... Probably not, but I didn't want to go back to the Sonarworks. I've heard bigger improvements from cables. I bought it at a retail store that allowed me 30 days and I could return it. But decided to keep it.... Cause of the small improvement and I suppose, peace of mind that I'm using very high quality microphone.

It's mainly improvement in imaging, and possibly better tonality, but that one could be in my head, it's that small.
I took a short video of the measurements being compared back and forth.

 

[whoareyou]

What about the time alignments? Have you taken multiple back to back measurements and checked that the timings are the same?
This was the differenc maker for me. With USB mic timings were very inconsistent between subsequent measurements. With my Isemcon I can take multipls of measurements and the timings are pretty much identical for each and every measurement.

 

[Bobski321]

If you are referring to the delay time after each measurement.... Extremely consistent. Either of the microphones are extremely consistent. Every time I do measurements I take at least 6, so that I can compare and root out the ones with strange anomalies. Never changes.

0.0 delay.

I have a really good way and system set up to make sure the mic is in the exact same spot every time. Infact, I've taken probably over 80 measurements in the past 6 months....and I always get 0.0 delay.

 

[whoareyou]

If you are referring to the delay time after each measurement.... Extremely consistent. Either of the microphones are extremely consistent. Every time I do measurements I take at least 6, so that I can compare and root out the ones with strange anomalies. Never changes.

0.0 delay.

I have a really good way and system set up to make sure the mic is in the exact same spot every time. Infact, I've taken probably over 80 measurements in the past 6 months....and I always get 0.0 delay.

I asked about timing because inconsitency measurement to measurement was main reason that convinced me to switch from my UMIK-1 (weird popping noises while measuring was close second) .

Added bonus for me is that with ASIO interface multichannel setup can easily use REW.

 

[Bobski321]

Understood. My first mic was a umik-1 too. I also had inconsistency with the timing on that one. The Sonarworks was a great upgrade.