Following this post
I’m started to develop a new plug which aims to make this process a bit more comfortable.
It features a round trip measurement routine.
This allow to load the plug, connect the output to the system output,
loop over external gear (soft or hardware) and back to the profiler input.
Simply press “Profile” to play the “input.wav” file to the output and record the returning input
delayed by the measured round trip latency.
The round-trip latency will be measured on each “Profile” start.
Resulting recorded “target.wav” file will be perfectly in sync with the used “input.wav” file.
Currently, both files would be saved under “/data/user-files/Audio Recordings/profiles/”.
The “target.wav” file get overwritten on each Profile run, so there will be always only one target file.
You need to download it from the device in order to use it with the AIDA-X trainer.
The “input.wav” file comes as resource with the plug and get copied over to that folder,
when no input.wav file was found there.
This allow advanced users to use there own input.wav file by simply replace the one in that folder.
Still you could reuse the input.wav file when you upload it to your google drive once.
The target.wav file get checked during record and run to a normalization function when needed.
(Only when the max peek in target is above the max peek in input).
The record will be saved in the PCM24 wav format (same as the input.wav file).
The UI provide a progress bar, a vu-meter, a clipping indicator and, well the profile button.
I’m not sure if the folder “/data/user-files/Audio Recordings/profiles/” is the right directory to store the files, as then, they been available in the audio-file-player. May be better to hide them from there as they didn’t been meant to listen to.
Other than that, from the description above, is there anything I’ve forgotten to implement to make it more comfortable?