I found the built-in speaker frequency response of Realiser A8 in the discussion about Realiser A16.
Is it possible to run them in Impulcifer?
Is it possible to run them in Impulcifer?
pip install -U -r requirements.txt
Also anyone getting errors plotting charts make sure you update your dependencies
Happened to me on one of my recordings (not the other) but soon as I updated it went through fineCode:pip install -U -r requirements.txt
(venv) C:\Users\dushy\Impulcifer>python impulcifer.py --test_signal="data/sweep-6.15s-48000Hz-32bit-2.93Hz-24000Hz.pkl" --dir_path="data/my_hrir " --decay=300 --fs=44100
Creating impulse response estimator...
Running room correction...
Running headphone compensation...
Creating headphone equalization...
Creating frequency response target...
Opening binaural measurements...
Cropping impulse responses...
Equalizing...
Adjusting decay time...
Normalizing gain...
Plotting results...
Resampling BRIR to 44100 Hz
Writing BRIRs...
Thanks. I debugged this a bit but actually got some other errros than what you reported, at first. My problems was caused by a bug which I found and fixed. I'm using branch reverb-management which is going to be merged to the master branch soonish so I'm not eager to spend a lot of time debugging and fixing the master branch at this point.
Your measurements are looking quite odd. There is a massive amount of harmonic distortion in all of your measurements. Impulcifer's algorithms aren't necessarily robust with this level of THD. What kind of speakers are you using for the purpose? How about microphones and other components of the recording chain?
Here are the plots: https://imgur.com/a/smhBuTv
For an example FL-left measurement graphs look like this:
While my own measurements look like this:
For some reason your decay graph shows 10 dB bump after the initial (fundamental) impulse has already decayed. Also the third harmonic impulse is just under -10 dB while my own has the highest harmonic at under -50 dB. Also the spectrogram graph for you measurements looks like nothing I've seen before. Your room measurement graphs actually looked a lot better although they do have the crazy spectrogram behaviour.
Another problem is that in this case the decay time detection algorithm fails with one of the impulse responses resulting in a very long BRIR file. My demo hesuvi.wav is less than 2 MB while the hesuvi.wav generated from your measurements is over 13 MB. This doesn't mean it wouldn't work but will introduce unnecessary CPU load, which might or might not be noticeable on your machine. The noise tail can always be cropped out in Audacity if that seems necessary.
All this doesn't necessarily mean that you wouldn't get results out of it that don't sound good or at least create the illusion of speakers. Especially the harmonic distortion is (in theory) negated entirely by Impulcifer as long as it doesn't mess up too badly with the different heuristic algorithms I'm using there.
Try out the reverb-management branch:
Code:git fetch git checkout reverb-management git pull
Looking very good! How does it sound?I think Creative Sxfi dosen`t fit to measure audio signal.
Below plot is measured by Topping D50s today.
Thanks a lot.
It's supposed to work. Is the result any different if you use eq.csv vs not using it?@jaakkopasanen. Is eq.csv still supported? Trying to transform a recording for my Air Pods Pro - but the output doesn't sound right and I can't see it doing anything on the terminal. It's been like this way for a while - I was assuming I just couldn't get a decent headphone transform done anymore. But I remember early on, when it was eq.wav it used to work fine.
Code:(venv) C:\Users\dushy\Impulcifer>python impulcifer.py --test_signal="data/sweep-6.15s-48000Hz-32bit-2.93Hz-24000Hz.pkl" --dir_path="data/my_hrir " --decay=300 --fs=44100 Creating impulse response estimator... Running room correction... Running headphone compensation... Creating headphone equalization... Creating frequency response target... Opening binaural measurements... Cropping impulse responses... Equalizing... Adjusting decay time... Normalizing gain... Plotting results... Resampling BRIR to 44100 Hz Writing BRIRs...
I don't know why... that's just result.I use my SXFI amp and it works perfect.
Looking very good! How does it sound?
It's supposed to work. Is the result any different if you use eq.csv vs not using it?
python autoeq.py --input_dir="C:\Users\dushy\AutoEq\oratory1990\data\earbud\Apple Airpods Pro" --output_dir="my_results/APP (Aurvana)" --compensation="compensation/harman_over-ear_2018_wo_bass.csv" --sound_signature="C:\Users\dushy\AutoEq\results\oratory1990\harman_over-ear_2018\Creative Aurvana Live!\Creative Aurvana Live!.csv" --equalize --parametric_eq --max_filters=5+5 --ten_band_eq --bass_boost=4
--balance
modes to see if any work well.I think balance is affect to headphone record. Dosen't it? I said about speaker record.You should try the--balance
modes to see if any work well.
I found that while they worked well for restoring channel balance - they did have an impact on HRTF. I guess because your ears aren't actually identical so it messed with the localization and you got an unusual feeling from it.