Could someone please clarify if it is OK that ear HRTF wraps around the zero millisecond mark in the resulting SOFA file? I think I did something wrong, but the settings in the Output2HRTF.m file seem to be correct:
% source information sourceType = 'vibratingElement'; sourceCenter(1,1:3) = [-0.000075 0.061193 0.000278]; sourceArea(1,1) = 3.3792e-07; sourceCenter(2,1:3) = [0.004424 -0.065447 0.001078]; sourceArea(2,1) = 4.63999e-07; % Reference to a point source in the origin % accoring to the classical HRTF definition % (https://doi.org/10.1016/0003-682X(92)90046-U) reference = true; % Compute HRIRs via the inverse Fourier transfrom. % This will add data at 0 Hz, mirror the single sided spectrum, and % shift the HRIRs in time. Requires reference = true. computeHRIRs = true;
Hi Sergejs,
Its not ok, and it should appear in the HRIRs computed by Mesh2HRTF. How did you do the plot? My guess is, that this is a problem of the Matlab/Octave SOFA API, not Mesh2HRTF.
Best, Fabian
Good morning Sergejs,
I am more familiar with the Matlab/Octave SOFA API than with Mesh2HRTF. I will check if the issue is caused by the SOFA API.
How did you create the figure? Can you please tell me how I can reproduce it?
Best regards,
Michael
We leave this issue, because it is superseded by ticket #70 and this issue involved older Matlab code executed in Octave. The latest approach uses a different Python code for post-processing, so no point in debugging this old run.