The basic workflow is the following:
1. Scanning your head ...
2. Use meshmixer ...
3. ... blender.
4. Run hrtf_mesh_grading ...
5. ... hrtf export script
6. Run NumCalc
7. Run finalize_hrtf_simulation
Hmm, I had the hope that Mesh2HRTF would make the process available to people without a professional career in numerical maths, BEM modelling and programming. Seems I was wrong.
So I still shy away from a serious attempt to do this. I will probably use Windows (on my mac) to do it with the tutorials.
Mesh2HRTF has excellent tutorials. My biggest problem was that I tried to run it on a mac, and haven’t done programming for a long-long time. Git and cMake was bigger issue than running mesh2HRTF. For windows there are prebuilt binaries.
-Personal hrtf fixes tonality and response to big head movements mostly.
I do not about you, but that is quite a big fix for me.
- Externalization is much more dependendent on headtracking (or motion), than accurate hrtf.
My experience is that it is more complex.
I was always interested in binaural recordings and most of the time with disappointment. When I listen i.e. to the Chesky demos the whispering in the ear works convincing but most of everything (basketball..) is not externalised in the front but in the back. The music recordings seem to be done in a funny room with the musicians placed under the ceiling and so on.
I never knew what was wrong until I made some test recordings with in ear mics. Well, that was a surprise. The realism (even without proper EQ) was stunning. Hearing back a recording of a conversation in the living room fooled me several times about about who was speaking (or not). It worked outdoors too.
So I would estimate the influence of the hrtf to be bigger than you seem to do. Of course a binaural virtualization of stereo listening is a different thing than a (true) binaural recording.
No doubt there are several things that contribute to a convincing presentation of stereo via binaural:
- HRTF
- virtual room reflections
- head tracking
The second and third point will probably be similar for most people. But it is very difficult to gauge the first.
A "generic" hrtf can always be more or less similar to one's own hrtf. So the effect of changing to a personal solution can be quite different.
I tried Virtuoso with KU100 first and was a bit underwhelmed. Then I tried the integrated hrtfs and (luckily) found those to be much better. So again there is a considerable difference from hrtf for me as everything else is the same.
Head tracking is great and gives that extra realism that gets stunning with greater head movements when the sound stays put. But even with head tracking the KU100 hrtf never did give a presentation with the same clarity and precision as the integrated hrtf (without tracking). And my self-tinkered cross feed solution from in ear measurements sounds even better to me in that regard.
(But Virtuoso gives me a very good room, head tracking and multichannel, so it is coming out in front in many cases.)
About differences in HRTFs I at some point traced a collection of curves from
Oksanen et al „Estimating individual sound pressure levels at the eardrum in music playback over insert headphones“ . Here are the hrtfs and the differences to the averaged hrtf as an illustration.