REW Beta Release REW API beta releases

[armagedon]

thank you sir, is this list can be viewed somewhere?

 

[dcibel]

Builds updated today (beta 66) with these changes:

• Fixed: FSAF file selector was disabled after making a sweep measurement

Hi John,
While the fix here has resolved the file selector, the file selected is processed for FSAF on opening the measurement window, even though sweep is the default measurement selection. It makes for 5-10s delay to measure for file processing whether you wanted a sweep or FSAF measurement. I'm sure it would be more convenient if the file was processed when the FSAF tab was selected, making for a snappy experience for sweep measurements.

 

[John Mulcahy]

the file selected is processed for FSAF on opening the measurement window, even though sweep is the default measurement selection

Not for me, only processed when FSAF is selected.

 

[dcibel]

Ok, not everytime. Let me clarify. In FSAF, file is the selected signal type. Close REW. On first open, measurement will pause to process the FSAF file, whether FSAF or sweep was the last operation.

 

[John Mulcahy]

It should only do that if FSAF was the last method used before closing. In that case it selects FSAF when next opened, restoring the last method used.

 

[sm52]

When I launch REW, I have the same window that Dcibel showed, regardless of the last method before closing REW. Waiting, while it works, 10-15 seconds. For example, I made an impedance measurement, closed REW, after launch there is a window for preparing FSAF.

 

[John Mulcahy]

For example, I made an impedance measurement, closed REW, after launch there is a window for preparing FSAF.

Whether the FSAF file signal is updated when the dialog opens depends on the last SPL measurement mode.

 

[sm52]

Thanks for the information. The delay of 10-15 seconds when starting REW does not bother me. With my message I wanted to confirm what Dcibel showed. So, if the last measurement before the closing of REW was FSAF, REW should open on the FSAF tab. At the same time, there is some delay in preparing FSAF measurement. But, my last measurement was Sweep, and when opening REW opened on the Sweep tab. But during the opening of REW, the same delay occurs as when opening the FSAF tab. I checked it now. I did FSAF measurements a month ago, after it there were a lot of Sweep measurements. But you still have to wait 10-15 seconds with each launch of REW. Sorry for the long explanations. It seems to me that Dcibel wrote about this.

 

[dcibel]

It should only do that if FSAF was the last method used before closing. In that case it selects FSAF when next opened, restoring the last method used.

I fully agree, it should do that.

Please try the following steps.
1. In measurement window, select FSAF, signal type = file, select a file to process.
2. Go to sweep tab, run a sweep measurement.
3. Close REW, then open REW.
4. Open measurement window.

Measurement type should be set to Sweep, and REW stalls for some time while FSAF file is processed. What I am trying to highlight, is that the FSAF file should be processed when FSAF measurement type is selected, not when the measurement window is opened. Minor details, but will make for a better user experience.

 

[dcibel]

As a feature request, I really like the ability to group measurements, but it would be great if selecting the group title in ALL SPL or the Overlays section would select or de-select all measurements within the group. Currently you can select the group title, but it doesn't have any effect on the measurement selection.

 

[sm52]

John, in the 'Measurement' window there is a parameter of the number of repetitions, at the top right. I am making an impedance measurement. I installed this parameter by 2. After that, I expect it to be 2 when I will return to the impedance measurement window. But if I make a SPL measurement in the Acoustic Timing Reference mode, this parameter will become 1. After that, it will also become 1 in the impedance measurement window. It seems to me that the number of repetitions in the Impedance window should not depend on the number of repetitions In the SPL window.

 

[John Mulcahy]

I fully agree, it should do that.

Please try the following steps.
1. In measurement window, select FSAF, signal type = file, select a file to process.
2. Go to sweep tab, run a sweep measurement.
3. Close REW, then open REW.
4. Open measurement window.

Measurement type should be set to Sweep, and REW stalls for some time while FSAF file is processed. What I am trying to highlight, is that the FSAF file should be processed when FSAF measurement type is selected, not when the measurement window is opened. Minor details, but will make for a better user experience.

Works as expected for me, no delay for FSAF file processing. When REW starts up there is an immediate background task that loads the FSAF file if one has been specified, if your file takes a long time to load that task might still be running but it is unrelated to the display of the Measure dialog.

 

[John Mulcahy]

As a feature request, I really like the ability to group measurements, but it would be great if selecting the group title in ALL SPL or the Overlays section would select or de-select all measurements within the group. Currently you can select the group title, but it doesn't have any effect on the measurement selection.

You can achieve that by expanding or collapsing the group if you have the "Select group measurements on expand" option selected in the Groups menu.

 

[John Mulcahy]

It seems to me that the number of repetitions in the Impedance window should not depend on the number of repetitions In the SPL window.

It is the same control for both. An acoustic timing ref measurement cannot use multiple sweeps so that resets it.

 

[sm52]

When REW starts up there is an immediate background task that loads the FSAF file if one has been specified

Thanks for the clarification. On the FSAF tab, I switched the Signal parameter from the 'File' to the 'Pink noise', after which the window 'Measure' began to load quickly.

 

[JoinUs]

Hello everyone, I asked John about this via PM, but I also wanted to ask you all.
I am currently using REW V5.4 Beta58.
Could you download the attached Mdat file and check Test, Result and A plus B, A minus B in the Overlay → Impulse view?

Test and Result were obtained using the Align Tool.
That part should not be affected, but changes occur.

And A plus B and A minus B follow the exact operation of the Align Tool, including the time offset.
Their results are the same, which is what I intended.

Even Test (Align) and A+B have different results.
The results of A+B or A-B match my expectations, and I believe the Align Tool should produce the same result as A+B (or A-B). But they are different.

Could you also download my Mdat file, open the overlay, and check it? (You just need to zoom in a lot.)
I don’t think this is an issue with my settings.

The Mdat file suddenly can't be attached, so I'm providing it via a link instead.

issuereport3.mdat

drive.google.com

 

[John Mulcahy]

Builds updated today (beta 68) with these changes:

• Added: Graph image capture has an option to add a border
• Changed: Graph image capture comments are retained for next use of the dialog, a button has been added to clear the comment
• Changed: Rearranged the View preferences
• Changed: When the "Vary max Q above 200 Hz" EQ option is selected the max Q of boost filters is also affected
• Fixed: Prevent FSAF background file load task from locking the signal generator or Measure dialog if FSAF is not being used
• Fixed: Capture noise floor checkbox on Measure dialog was sometimes not visible for sweep measurements
• Fixed: The Q figure shown for graphic filter edit was the RBJ-equivalent Q instead of the Q or bandwidth format for the equaliser selection
• Fixed: Opening and then cancelling the stepped sine dialog would re-initialise the RTA and clear any current capture
• Fixed: Large alignment tool delays could produce low level artefacts when the aligned sum was generated using the "Aligned sum" button
• Fixed: Alignment tool "Remove time delay" affected any measurement generated using the "Aligned sum" button

 

[dcibel]

Builds updated today (beta 68) with these changes:

• Fixed: Prevent FSAF background file load task from locking the signal generator or Measure dialog if FSAF is not being used

Thank you, however I don't believe this to be resolved. It appears the background task still occurs, but the grey loading graphic is no longer displayed. It makes for a delay in response from any buttons on the measurement window.

 

[JoinUs]

Fixed: Large alignment tool delays could produce low level artefacts when the aligned sum was generated using the "Aligned sum" button

A plus B (trace arithmetic) 50ms delay

Align Sum (Beta 58) 50ms delay

Align Sum (Beta 68, latest version) 50ms delay

Now, the results of A plus B and Align Sum match.
Thank you, John.

 

[keantoken]

With the latest beta, the "use harmonic frequency as ref" button is broken. Also, sometimes this button and the button above it is greyed out when it shouldn't be.

Here is a measurement file in case it is needed.

 

[dcibel]

Deleted.

 

[keantoken]

This may just be something I forgot about. "Use harmonic frequency as ref" button only works on relative db and % modes. On SPL or dbFS it does nothing. I would still like to be able to use it with these settings so I can see the normalized THD at the same time as the frequency response which helps with identifying distortion mechanisms. However I think this is intended behavior.

However the buttons being greyed out inconsistency does seem to be a bug.

 

[John Mulcahy]

As you noted, the option to use the harmonic frequency as the reference has no effect on the graph if the axis is not relative and no effect on the legend if the legend figures are not relative. The option to limit normalisation to 30 dB is disabled for stepped level measurements. The option to use the harmonic frequency as reference is disabled if harmonics are plotted at the harmonic frequency as it is always applied in that case.

 

[yanni]

Hi all,

I started the optimization process but then it stops at the following stage. What am i doing wrong?

I also got two errors when starting the REW for the first time but i'm not sure that it's connect to the problem i'm having.

 

[John Mulcahy]

I started the optimization process but then it stops at the following stage. What am i doing wrong?

That's not REW code, try posting on one of the @serko70 threads for his features.