Originally Posted by
jtrosky
What I mean is that I can't simply load a "standard" format house curve text file into the Helix RTA setup (so that I don't have to manually adjust those sliders). For very basic curves, adjusting the sliders isn't that big of a deal to create the Helix-specific curve file, but I create custom house curves that aren't as "simple". :-) My method just allows me to tune towards my specific house curve, which ends up being just how I want things - without having to adjust for "tonal" preferences afterwards - my process just combines those two steps (tuning to a curve and then adjusting for tonal preferences) into a single step using a custom house curve.
I knew you could load a house curve into the Helix RTA setup window if you had already manually setup the sliders and then saved it from within the Helix RTA setup (which saves it to a ".atref" file), but what I didn't realize is that the .atref files that it creates are just standard text files with a ".atref" extension. I had assumed that those files were in some sort of binary format, but I just checked and they are just regular text files, so yes, that does make things easier.
However, you still can't just load a standard house curve text file created with REW or even Jazzi's speadsheet, for example. This is because the Helix software wants a VERY specific format for the house curve file - it seems to have 30 values, one value per line without any reference to frequency (just a single value for the dB level of each slider). So unfortunately, it won't figure out the values it needs from a standard house curve text file - there is still some work to be able to load a standard house curve text file, created with REW or even with Jazzi's spreadsheet, for example, since they all create text files with both a frequency *and* a dB value on each line.
This is still good news though - at least I know the .ateef curve files are just standard text files. Now I know that I can manually edit those files directly instead of messing with those sliders.
Thanks for replying about that or I probably would have never even checked the format of the .atref files! :-)