Forum Replies Created
-
13 January 2023 at 9:39 pm #605Thanks. And did you have 4 FIR Designer windows open – one for input IIRs and one each for the 3 module output channels? Email us the FIR Designer project FDP files and we’ll take a look.
Best regards,
EA Support
13 January 2023 at 9:59 am #603Hi URI,
Which product (FIR Designer, FIR Designer M) and which product version are you using?
Which Lake module are you using? (The Lake FIR 3-way – that comes with our Lake plugin – or one of the Lake XP modules?)
Can you email us your FIR Designer project and/or system files? info (at) eclipseaudio.com
Also, can you provide a screenshot of the FIR Designer Lake DTP or “Export to Lake” window?Best regards,
EA Support
9 December 2022 at 11:51 am #598I just emailed you a link to the plugin.
Note that FIR Creator EX and FIR Designer work with the Lake FIR 3-way module. Th newer Lake XP 1, 2, 3 and 4-way modules, with FIR, can only be loaded from FIR Designer M.
Best regards,
EA Support
19 November 2022 at 7:32 pm #594My apologies. 2.6.1 includes support for importing CLIO IR txt files so we have just uploaded a 2.6.1 dmg.
Best regards,
EA Support
19 November 2022 at 4:19 pm #593As per the notes, 2.6.1 is an update for MS Windows only. The adjacent 2.6.0 dmg link for mac is provided to save time scrolling further down the page; if upgrading from 2.5.x or lower.
Best regards,
EA Support
12 November 2022 at 7:23 am #588This morning we wrote an importer specifically for this CLIO time format. It will be available in the next release.
Best regards,
EA Support
12 November 2022 at 5:43 am #587>> Hi,
>>
>> Thanks for the explanation it all make sense,
>>
>> Side question is there any chance the time IR accept files with 3 column and
>> ignore the 3rd one? Many software export with a 3rd imaginary column and it
>> would be nice to not have to modify the file every time to import in FIR designer.
>> See attached example. Or did I miss something.
>>
>> Thanks a lotHi,
Our 3+ column TXT import by default assumes freq|mag|phase|coherence.
We do some checking of the file for specific formats that can be inferred from header or comment text, but without any headers or comments, we assume freq|mag|phase|coherence.
>> Many software export with a 3rd imaginary column
I have never seen anything like this before, but since the header text is
Time[s] Real[V] Imag[V]
we could write a customer importer for this. I’ve added this to the TODO list but I can’t say when it will be ready.Best regards,
EA Support
2 November 2022 at 6:44 pm #583Hi Weiguo,
>> Is there anyway to convert this response file using FIR Creator EX?
No.
>> I don’t know how to change it to 0 dB.
You don’t need to have the measurement at around 0 dB. The “Import” tab has the gain adjustment for exactly this purpose.
I have taken a look at your FDP file. Here are a few suggested minor adjustments:
– On the “Mag Adjust” tab, change the gain of the “High Shelf” to -7.9 dB.
– On the “Auto Mag” tab, change the “Min Freq” to 90 Hz.>> I imported a speaker response and created a fir file. But the result seems hardly doing anything.
From what is shown on the “Export” tab, the FIR filter should definitely be audible.
All I can suggest is checking that the processor is importing the file and that the filter is enabled. What processors are you using and what FIR filter format did you export?
Best,
EA Support
1 November 2022 at 7:08 pm #581Regarding the -108.1 dB gain, with “Normalise magnitude to max” checked, the Import tab looks for the peak in the measurement and shifts the response so that the peak is at 0 dB. The FIR Creator workflow needs the response to be around 0 dB. (Maybe your measurement magnitude response has units of dB SPL and your mic was close to the loudspeaker.)
Regarding your FIR filter, provide a screenshot of the Export tab and a link to you project *.fdp file.
Best regards,
EA Support
20 October 2022 at 2:48 pm #576Crown itechHD’s require a specific number of coefficients. The last we checked, it was 897, but it might have changed. You may need to try different files with different numbers of coefficients until it works.If you still can’t get it to work, I suggest contacting Crown. They may have a problem with the FIR loading.
Regarding precision, your 2nd screenshot shows that the coefficients do match. It’s just that the iTech display is rounding/truncating at 6 decimal places, which equates to approximate -120 dB relative to full scale; so I think you’ll find the trunction doesn’t matter.
Best regards,
EA Support
19 October 2022 at 6:36 pm #574Hi Thomas,
The region around 150 Hz has fairly high phase slope at import and it looks like the tabs, prior to the Phase Adjust tab, have added additional phase slope; which looks to be from HP filtering. The result is a phase slope high enough that it’s marginal*, in the plotting, between showing a step between plot points (as in your screenshot) and wrap. Given that this freq region way out of band – it looks to be at approximately -60 dB relative to the passband – it’s safe to ignore.
* The plotting groups/averages the >16000 raw FFT data points into a smaller log frequency spaced set at approx. 1/96th oct spacing. Sometimes in this averaging, very high phase slope regions can go either way.
Best regards,
EA Support
16 October 2022 at 10:07 am #571The Target response import loads almost all of our supported formats, including CSV. See Text and CSV on:
If your CSV is a magnitude curve, ensure your CSV file has 3 columns; frequency (Hz), mag (dB) and phase (degrees). The phase can be set to 0.0.
Best,
EA Support
13 September 2022 at 6:25 pm #565Hi Lukas,
We’ll take a look but can’t promise any changes to address this. Odd handling of “.” in filenames is a problem shared by many apps; not just ours. All I can suggest for now is to not use “.” and instead use something else like the underscore. For example “filter_xyz_V0_2”. I do this myself in other apps.
Best regards,
EA Support -
|