Forum Replies Created

Viewing 15 posts - 256 through 270 (of 345 total)
    • 2 April 2022 at 1:01 pm #457

      Hi Johnson,

      That’s correct; there’s no target phase on the IIR tab right now. And yes, we should add this. (It’s on the TODO list.)

      In the meantime, you could open “Second View” and watch the phase on another tab. For example on the Phase Adjust or Auto Phase tab.

      Best regards,
      EA Support

        1 April 2022 at 8:58 am #454

        Apologies. We have just re-uploaded version 3.2.2. Please try downloading again.

        Best regards,
        EA Support

          14 March 2022 at 4:06 pm #452

          We’ve taken a look at the Processor Editor software.

          Regarding the IIR filtering, many brands have different interpretations of Q (or BW) in their parametric and shelf filters. And some have different frequency interpretations for Bessel filters.

          We may consider adding this processor to our IIR filter modes, however it can take many months to work out the math for a new IIR mode and create all the conversion functions to/from all the existing Branded IIR modes that we have in our products.

          In the meantime, I sugges experimenting with the filters in each of the existing IIR modes to see which ones may closely match the T.racks.

          Best regards,
          EA Support

            28 February 2022 at 6:50 am #447

            Hi liveNathan,

            Take a look at

            Loudspeaker Measurement Import File Formats

            The file starts with:

            * Measurement data measured by REW V5.20.5
            * Source: EQ window target shape
            * Format:
            * Dated: Feb 27, 2022 11:39:39 AM
            * REW Settings:
            * C-weighting compensation: Off
            * Target level: 75.0 dB
            * Note:
            * Measurement: Target Main Native
            * Smoothing: 1/48 octave
            * Frequency Step: 96 ppo
            * Start Frequency: 2.5 Hz
            *
            * Freq(Hz), dBFS(dBFS)
            2.500000, -125.155
            2.518116, -124.904
            2.536363, -124.653
            2.554743, -124.402
            2.573256, -124.151
            2.591902, -123.900
            2.610684, -123.649
            2.629602, -123.399
            2.648658, -123.148
            2.667851, -122.897
            2.687183, -122.646
            2.706656, -122.395
            2.726269, -122.144

            It’s a 2 column file with Freq & Magnitude but “FIR Creator” requires 3 or 4 column for Freq|Mag|Phase|Coherence. Since there are so many different ways TXT and CSV files can be created, we’ve had to put some rules around how we import files. We do look for a few special cases, and for REW, we currently look for the starting line

            * Impulse Response data saved by REW

            We’ll look at adding something for this file’s header also.

            In the meantime I suggest copying this into Excel, adding a 3rd column of 0’s, and saving as a 3 column txt file.

            Alternatively, if your intended target response is something simple, use “FIR Creator” in “Direct Design” mode, make your target response, export as a FIR Designer Target File (FDT) and import this on the Target tab.

            Regards,
            EA Support

              26 February 2022 at 10:27 am #439

              We’ve been working on this most of this last week and should have an update available in the next day or two.

              Thanks for your patience,
              EA Support

                20 February 2022 at 7:34 am #434

                Hi liveNathan,

                On the “Import” tab, uncheck “Normalise magnitude.” This will bring the HF back up to 0 dB.

                (Notice that the “Magnitude offset (dB)” setting is showing that -2.0 dB is being applied by the “Normalise magnitude” process.)

                BTW it looks like the sample rate used to make the filter is different to the sample rate of the app when loading the filter. Note how the phase peak is just below 200 Hz in the upper plot and just below 100 Hz in the lower plot.

                Regards,
                EA Support

                • This reply was modified 4 years ago by EA Support.
                • This reply was modified 4 years ago by EA Support.
                  19 February 2022 at 8:05 pm #432

                  Hi David,

                  We’ve fixed the SSL problem and uploaded new binaries. If you re-download and install the latest 1.6.2, the SSL error won’t appear.

                  Regards,
                  EA Support

                    19 February 2022 at 7:48 pm #431

                    Sorry, there’s not way to change the overall skin right now. It’s on the long term “todo” list but it involves a lot of code changes.

                    Best regards,
                    EA Support

                      19 February 2022 at 7:19 am #427

                      Hi Sunil,

                      Version 2.2.x introduced Marani IIR filters and a “FIR output sample rate” parameter, which is different to the channel sample rate used for IIR and gain & delay. The “FIR output sample rate” parameter broke the Wavelet view for cases where the “FIR output sample rate” is different to the channel sample rate. We are currently working on a fix. (The filters are correct; it’s just the Wavelet display that is broken.)

                      I’d suggest confirming that the channel sample rate and “FIR output sample rate” parameter are the same. If they are the same and you still see problems with the Wavelet view, for now please downgrade to the most recent 2.1 release; 2.1.11. If you don’t have access to the downloads page, email us at the info address on the https://eclipseaudio.com/contact/ page.

                      And if you have time, can you email us your system (fds) and project (fdp) files.

                      Best regards,
                      EA Support

                      • This reply was modified 4 years ago by EA Support.
                      • This reply was modified 4 years ago by EA Support.
                        19 February 2022 at 6:45 am #425

                        Thanks for letting us know. We’ll take a look at this. In the meantime we’ll email you a direct link.

                        Regards,
                        EA Support

                          18 February 2022 at 6:15 am #421

                          >> I use FIR Filters for Hifi Equipment. Do you have an good idea for me which
                          >> FIR Equalizer works fine to build an active crossover with more than 1024 taps
                          >> for each channel?. Balanced Outputs desired if possible. Mini DSP2x4HD is fine,
                          >> but I would wish in first order more channels and more taps if possible. Also
                          >> better sound quality should be fine..

                          Sorry, we don’t have the time to keep up-to-date on the latest processors. MiniDSP have a few multi-channel products that may run longer filters, and a number of their products support balanced IO.

                          Regards,
                          EA Support

                            18 February 2022 at 6:06 am #420

                            In short, Power Averaging averages the magnitude response only and ignores phase. Complex Averaging includes phase, and so frequency regions with substantially different phase will partially cancel and result in lower level in the averaged result.

                            When combining room measurements to EQ a single loudspeaker or loudspeaker cluster, Power Averaging is usually more appropriate. When measuring drivers and designing crossovers, Complex Averaging may be more useful.

                            Regards,
                            EA Support

                              16 February 2022 at 7:51 am #414

                              Hi David,

                              The second and fourth images give a clue.

                              The second image shows the “Design sample rate” set to 48 kHz and the lowest frequency response peak, in the FIR filter, is close to 1 kHz. The fourth image shows the same magnitude response shape but the lowest frequency peak is close to 2 kHz.

                              The MiniDSP2x4HD runs at 96 kHz and so it’s treating the FIR coefficients as if they have been designed for 96 kHz. In FIR Creator, change the “Design sample rate” to 96 kHz, then export and import the FIR filter again.

                              Best regards,
                              EA Support

                              BTW Thank you for providing clear screenshots and a very clear description. This really helps.

                              • This reply was modified 4 years ago by EA Support.
                                5 February 2022 at 8:03 am #406

                                >> Why no Auto Mag and Phase?

                                If Auto Mag and/or Auto Phase are enabled, then when the measurement is loaded, the Auto tabs change the filtering to push the measurement towards target. At which point you’re no longer looking at your FIR filter applied to the measurement; rather you are looking at the measurement pushed towards your FIR filter which is interpreted as a Target.

                                By approximating the FIR filter first, using the Mag Adjust and Phase Adjust, before loading the measurement, the filtering doesn’t change when the measurement is loaded.

                                These steps are only a crude approximation for what you want. Ideally we need to implement a view that shows a FIR filter directly applied to a measurement.

                                Best,
                                EA Support

                                  12 January 2022 at 11:15 am #397

                                  Hi Lukas,

                                  To the right of “Auto Mag Correction” and “Auto Phase Correction” there are “Enable” checkboxes. Unchecking these will save you having to turn off each individual frequency band, however these enable checkboxes are per-channel, and would need to be toggled for each channel.

                                  We understand what you are describing w.r.t. performance, especially if you are using mouse control of filters (which triggers continual updating of everything). We’ll consider a global enable/disable idea. Thanks.

                                  Shortcuts, also a great idea. We’ll look into it.

                                  Best regards,
                                  EA Support

                                Viewing 15 posts - 256 through 270 (of 345 total)