Forum Replies Created
-
7 November 2025 at 12:51 pm #501174Use the + – buttons to move the delay by 0.25 of a sample.
>> Also I don’t understand why in import tab delay is negative number
The -4.25 samples is on both channels, so their time relationship is retained. Moving both negative in time just gets their phase into a range that is easier to work. (This delay is not important for the miniDSP.)
>> while in gain/polarity/delay tab it is positive number.
The positive sample delay on the gain/polarity/delay tab is delay ONLY on the tweeter. It moves the tweeter phase to better match the woofer phase in frequency region of the crossover filter. This delay is added with the “FIR alignment delay” to give the “Total Processor Delay” — see the system Export tab. The “Total Processor Delay” is the delay that needs to be set on each channel in the miniDSP, to ensure your overall design works. On the example I gave you, channel 1 – the tweeter – needs 7.3958 ms and the woofer 0 ms. But these numbers may be different since you have changes the channels to 96 kHz and likely adjust the FIR filter sizes.
6 November 2025 at 5:27 am #501172You said the miniDSP runs operates at 96 kHz and you have FIR Designer set to 48 kHz. When a filter is designed at a sample rate of 48 kHz (which you have set in FIR Designer), then actually run at 96 kHz (which the miniDSP operates at), the EQ response of the filter will appear at double frequency – which you confirmed in the statement “I have a 2 kHz crossover in FIR Designer, but it appears at 4 kHz on the miniDSP.”
You need to change the FIR Designer channels to be 96 kHz, so that the exported filter sample rate matches the miniDSP.
Regards,
EA Support
5 November 2025 at 12:40 pm #501170It’s most likely caused by the FIR Designer channel sample rate not matching the sample rate of the miniDSP. For example, if the miniDSP runs at 48 kHz, but the FIR Designer channel is set to 96 kHz, then a crossover in the FIR filter will appear at half the frequency. Similarly if the miniDSP runs at 96 kHz and the FIR Designer channel is set to 48 kHz, then a crossover in the FIR filter appear at double the intended frequency.
Regards,
EA Support
29 October 2025 at 8:44 pm #501168>> When I loaded the FDS file into my FIR Designer M, I received the following message:…
You have version 4.3.15 and the latest is 4.5. To update, ensure “Check for update at program start” is checked in Preferences, then restart FIR Designer M and watch for the Update window.
>> I noticed that you used a Cosine tapered window. Is there perhaps some another window
>> type that could produce a more pleasant, warmer soundFactors other than the window have much more effect on the perceived warmth of the sound, such as the target response, using single measurements instead of spatially averaging measurements, and the amount of fine EQ. A “flat” target response is often perceived as too bright and harsh, and this can be changed on the System Target tab by adding slopes on the “Curve” tab. Fine EQ – such as with the 12th octave smoothing on the Auto Mag and Auto Phase tabs – may also have an impact. Try changing the smoothing to 1/6th or 1/3rd.
>> something that reduces the metallic character and minimizes ringing as much as possible?
Perceptable pre-ringing can be an artifact of trying to make the processed loudspeaker linear-phase, since the FIR filter can have significant taps before the FIR filter peak. However I’d suggest first experimenting with spatial averaging and using a System Target that has some roll-off towards higher frequencies.
Respectfully, most of these questions relate to best practices for loudspeaker tuning, which is beyond the scope of our support. We can explain how to achieve your goals using our software, but the goals themselves are completely for you to decide, either from other learning or experimentation. We don’t advocate for specific tuning approaches.
Regards,
EA Support
26 October 2025 at 3:21 am #501166Hi Tohimir,
The Auto Mag problem you are seeing is because the channel target responses are flat; each channel has a crossover filter set on the Mag Adjust tab but the Auto Mag is trying to push the channel back to flat. If you set crossover filters on the channel targets, the Auto Mag will then push each channel towards the intended crossover target response.
I have sent you an updated FDS file. Please study how every tab is set. The settings are not the only way to set up a 2-way, but they show you what is possible. These methods are in the videos and tutorials available on our website.
Regards,
EA Support
17 October 2025 at 1:34 pm #501161We have many ‘FIR Designer M’ users, but this is the first time we’ve heard about problems with those specific export buttons.
16 October 2025 at 12:14 pm #501158Thanks Olli.
We have replicated the problem. What’s happening is that the first channel to be saved is the current channel you have selected in the ‘Channels’ ‘Edit Channel” drop down. For example, if ‘Edit channel’ is set to channel 3, the first channel FIR file to be saved actually contains data for channel 3 instead of channel 1. The other files, for channels 2 to 6, are correct.
We will have a fix in the next ‘FIR Designer M’ release. In the meantime, set ‘Edit Channel” to 1 before pressing “Save FIR’s” or “Save FIR’s + Summary”.
Regards,
EA Support
8 October 2025 at 5:38 am #501151Hi Olli,
AuditionDSP (like any other audio software on macOS) talks to the hardware through Apple’s CoreAudio software layer and through the hardware manufacturer’s device driver (if the hardware requires it). So AuditionDSP can’t “kill” the hardware.
I’d suggest ensuring the DAC8 is running the latest firmware and googling audio problems with macOS Sequoia. Also, I found this thread on Audio Science Review where a user had to hard reset the Okta DAC8 to get it functioning again.
https://www.audiosciencereview.com/forum/index.php?threads/okto-dac8-update-with-dsp.54196/page-3Regards,
EA Support
2 October 2025 at 10:03 pm #501149We have just released FIR Creator EX 2.2.0 with support for the Hypex 93.75 kHz sample rate.
Regards,
EA Support
2 October 2025 at 10:02 pm #501148We have just released FIR Creator EX 2.2.0 with support for the Hypex 93.75 kHz sample rate.
Regards,
EA Support
2 October 2025 at 10:02 pm #501147We have just released FIR Creator EX 2.2.0 with support for the Hypex 93.75 kHz sample rate.
Regards,
EA Support
3 September 2025 at 8:24 pm #1145Version 4.5 is now available and has an option to remove the system target from the channel target.
Regards,
EA Support
13 August 2025 at 8:24 pm #1141The aim of the AES75 procedure in SpeakerMeasure is to generate a maximum linear SPL number. The SPL number and the plot can be saved to a file. See:
For specific details on the test procedure, you will need to download the AES75-2022 specification from the AES. http://www.aes.org
Regards,
EA Support
3 August 2025 at 10:28 pm #1135Version 4.4.7 is available. Restart FIR Designer M and watch for the update alert.
Regards,
EA Support -
|