Q1: Where should I put Endura in my project?
Endura should be the very last thing in the chain before your master fader. Make sure no audio processing - such as gain, dither, or normalization - is applied after Endura. By having Endura as the last process, you can assure your DAW signal path is bit-perfect by verifying the QA Metadata.
Q2: How long should I let Endura “Learn” my track to create the best custom noise shaper?
You should have Endura learn on the quietest part of your track (usually the intro to the song is fine) and it only needs 10-20 seconds of audio to fully analyze the noise floor.
Q3: How do I export my project to make sure I’m getting the maximum out of Endura?
With Endura as the last process in your DAW, you can export in any of 3 ways:
- Export Off-Line using your normal “Bounce” or “Render” workflow with Endura enabled on the master bus. Endura does not have to be in “Record” mode.
- Export Off-Line with Endura in “Record” mode to provide an alternate export directly out of the plugin. Usually, this method will output 2 distinct files. One directly from Endura and the other after your master fader as per your usual off-line capture.
- Real-time export from Endura. A fail-safe option (and much slower option) that bypasses all background processes and functions.
Method 1 - Standard Off-Line Rendering or Bounce:
Endura’s Verify Export tool (with Write Assurance Metadata enabled) can be used to check if your DAW will successfully export bit-perfectly. Follow these steps to complete the check:
-
- Bounce your project as usual, ensuring Endura is the final plugin in your FX chain.
- Open Endura, go to the Record and Export menu, and use the Verify Export file browser to select your exported WAV or FLAC file.
- Click Verify.
If the result is PASS, your DAW export is bit-perfect. You should continue to export via this method.
If the result is FAIL, your audio has been altered after Endura – see Why does my export fail assurance metadata verification? for troubleshooting.
Method 2 – Parallel Off-Line Rendering with Endura and your DAW:
If your DAW cannot export bit-perfectly using Method 1 and the problem cannot be found, you can use Endura’s built-in Record and Export function:
-
- Open the Record and Export menu.
- Choose your file name, location and format.
- Arm the Record button. At this point, any audio passed to the plugin will be exported.
- Perform an offline bounce - Endura will export the track in parallel to the DAW standard offline render.
Note: In this scenario, you’ll get two files - one from your DAW and one from Endura. Only the Endura file is guaranteed to pass verification.
Method 3 – Parallel Real-Time Rendering with Endura and your DAW:
If your DAW cannot export bit-perfectly after following the methods above, you can use Endura’s built-in Record and Export function and try rendering in real time:
-
- Open the Record and Export menu.
- Choose your file name, location and format.
- Arm the Record button. At this point, any audio passed to the plugin will be exported.
- Perform a Real Time capture – Play back the track at normal speed through Endura and your DAW. Endura will export the track in parallel to the output post of your master fader.
Note: In this scenario, you’ll get two files - one from your DAW and one from Endura. Only the Endura file is guaranteed to pass verification.
Q4: Why does the file size of my DAW export not match the Endura export?
Endura’s built-in Record and Export mechanism will export all audio received from the DAW. Some DAWs add silence (padding) when sending audio to plugins at the end of an export. Check your DAW’s export settings - there may be an option to disable this behaviour.
Q5: What is ‘Distribution Assurance Metadata’ and do I need it?
The Endura export writes metadata in your exported audio containing details to preserve your intent. It enables:
- Bit-perfect export and distribution verification via Endura’s Verify Export tool.
- Optimal playback on compatible hardware.
We strongly recommend enabling it for quality assurance and long-term compatibility.
Q6: Why does my export fail assurance metadata verification?
A failed verification means the exported file does not contain valid, unaltered Assurance Metadata. Common causes include:
- Write Assurance Metadata was not enabled in Endura’s Record and Export menu.
- Endura was not the final plugin in your chain.
- The master fader wasn’t at 0 dB, or gain automation was applied on the master bus.
- Your DAW applied dither or normalization during export - ensure these are disabled.
Once you’ve addressed these issues, try the verification steps again (see How do I export my project?).