v1.3.4

Download

Ready to run - the filters are already inside. Unzip, run aura-engine.exe, drop a track on it. The app opens on the filter that came with it.

Bundle	Filter	Output rates	Size
Compact	5k taps	every FS multiplier (FS2-FS16)	7 MB	Download
Starter	1M taps	every FS multiplier (FS2-FS16)	135 MB	Download
Standard	10M taps	FS8 (352.8 / 384 kHz)	327 MB	Download
Reference	30M taps	FS8 (352.8 / 384 kHz)	967 MB	Download

Unzip more than one into the same folder and the app offers every tap count you have.

Already have the filters, or want to build from source? The plain app zip is below, and the individual filter packs are on the 1.0.0 release.

Checksums (SHA-256)

d10678c8448d170599562ac5201e18bebd94e54f12542d00be98436e510818e5  aura-engine-v1.3.4-bundle-5k-windows-x64.zip
7930510e3a701ec2e65b137ee059aa7d289ed9137e51164e17501e9b2b1e1891  aura-engine-v1.3.4-bundle-1M-windows-x64.zip
64f15a30354346545c8bcda2ae4284ae8ad270fdb7d91170b90ce42f561cce46  aura-engine-v1.3.4-bundle-10M-windows-x64.zip
c80793e6c681928869ec7d407203650790914626dce9ca588a94a8fe57fe9316  aura-engine-v1.3.4-bundle-30M-windows-x64.zip

What changed in 1.3.4

If you updated from 1.2.x, two settings you never chose are put right, and
very long files now get the same output chain as everything else. For files
that fit in memory no DSP changed: the same settings give the same file as in
1.3.3.

Long files get the whole output chain

A file too long to convert in memory takes the segmented route. After the
phase blend that route skipped XTC, the ISP output limiter and the second
subsonic pass. All three now run there, streamed, with the in-RAM arithmetic,
each held to its in-RAM twin bit for bit by a test. Where the limiter can work
locally, a long file no longer comes down as a whole. On a 17-minute dynamic
master it trimmed 33 overs, and the file lost 0.01 dB instead of 0.33. With
Hybrid-Phase at FS8 the route starts at about 5 minutes on a 16 GB machine,
10–11 on 32 GB and 16 on 64 GB.

Polyphase FIR comes up on

PFR shipped off before 1.3.0 and on since. Settings saved by older versions
kept it off, so those files took the standard route. TFS stands down on that
route, and a very long track gets no segmented pass there. An 18-minute track
at FS8 with Hybrid-Phase was refused on a 32 GB machine for needing 28–29 GB;
through the polyphase route the same kind of file peaked at 6.3 GB.

Settings saved by 1.3.3 or earlier now get PFR switched on, once. If you
switch it off again, that choice is kept from now on. In the audio band the two
routes measure the same; file names gain PFR, and TFS, if its row is lit, now
actually runs.

Hybrid-Phase and TFS

Settings from 1.2.x with Hybrid-Phase on came up with TFS on too, and the
engine ran TFS instead of Hybrid-Phase. That is now settled in favour of
Hybrid-Phase for any saved settings, including ones saved since 1.3.0.

Smaller fixes

• Very long files, the ones that take the segmented route, now carry PFR and
  HP in their names. The tag inside them already did.
• The out-of-memory message suggests turning PFR on before it suggests
  lowering FS or turning Hybrid-Phase off.
• The version number is shown above the heading, in the app and on the web
  converter.

Thanks to formdissolve on Audio Science Review, whose question about a
28 GB estimate turned up the first one.