REW Beta Release REW API beta releases

Yes, the Linux builds support the API. You can check the rew_output.txt and roomeq_wizardx.log.txt files for any errors logged (their location is shown in the About REW dialog), or use the Help menu option to generate a diagnostic file and attach that.
Thx for the respond I didn't see any relevant error in the .log.txt. Here is the Diagnostic.

Thx for your help !
 

Attachments

Ok so for some reason I indeed install the wrong one... Sry for this post.

Thanks for the fast respond.

Continue the good work !
 
Last edited:
John, I was not able to select "Copy target settings" in EQ window today and during my attempts a Java exception popped up but I couldn't save it. If the way to copy/paste EQ target settings changed recently I might have been doing it wrong (mouse right click) but wanted to report anyways.
 
John, I was not able to select "Copy target settings" in EQ window today and during my attempts a Java exception popped up but I couldn't save it. If the way to copy/paste EQ target settings changed recently I might have been doing it wrong (mouse right click) but wanted to report anyways.
Looks like it got broken in beta 75 as part of an attempt to tackle the reports of popups staying visible when they shouldn't. I have fixed that for the next build. If you attach the diagnostic file whatever error occurred should be in the log captures.
 
Here you go...
 

Attachments

Hi John,
Sometimes when working with filters in the EQ window, the filters values can obscore the effect of the filter on the predicted graph when one is busy dragging the filters on screen, see below. I would be great if there could be an option to disabled these values while dragging or toggle them on or off.
Snap1.png
 
Request :
In the room simulation, the delay for each subwoofer can currently only be set to values like 8 or 9 ms.
Would it be possible to request more precise control, down to decimal values? (e.g., 8.75 ms, 1.32 ms)
 
Builds updated today (beta 77) with these changes:
  • Added: Overlay RT60 graph has a "Copy the average to the clipboard" action
  • Added: The STI panel has a "Calculate Leq at" button to calculate octave band speech signal levels for a given overall dBA level at the measurement point
  • Added: The filter adjust graph has an option to choose whether the filter settings are shown when editing filters graphically
  • Changed: The Speech PN signal spectrum is cut below the 125 Hz octave band edge and above the 8 kHz octave band edge
  • Fixed: StormAudio equaliser shelf filters have adjustable Q
  • Fixed: Some right click popups on Windows could disappear as soon as they were opened
 
1744690701438.png


Even when the same values are entered, the 1/A value differs between REW 5.30.9 and the Beta version.
(What I was expecting was the result from 5.30.9.)


Could you check this for me?
I've attached the mdat file in the Google Drive link.

 
Even when the same values are entered, the 1/A value differs between REW 5.30.9 and the Beta version.
If you select the Max gain checkbox the result will be the same (before V5.40 there was no max gain checkbox). I'll look into why that changes the result.
 
Here's the relevant part of the help:

The division operations have an optional maximum gain parameter parameter which limits the boost which occurs when the divisor becomes very small (or zero), such as where the divisor has notches in its response, and so produces a more stable and manageable result. Division may also be constrained to operate within a desired frequency span, with an upper and/or lower frequency limit. Outside those limits the behaviour depends on whether gain limiting is selected. If the gain limit is being used REW treats the operation as an attempt to produce a band limited correction filter and division reverts to unity gain, blended over a 1 octave span centred on the limit frequency. If the gain limit is not being used division reverts to the numerator, offset to align with the result within the band limit.
 
Hi!

The color of the phase traces when using the Alignment Tool in Linux seems to be fixed to RED only. Works perfectly fine in Windows...
 

Attachments

  • align.png
    align.png
    94.5 KB · Views: 6
The color of the phase traces when using the Alignment Tool in Linux seems to be fixed to RED only. Works perfectly fine in Windows...
It's the same code on all platforms. The phase trace colour comes from the measurement colour, so that's pretty strange. What build is running on the Linux machine?
 
Here's the relevant part of the help:

The division operations have an optional maximum gain parameter parameter which limits the boost which occurs when the divisor becomes very small (or zero), such as where the divisor has notches in its response, and so produces a more stable and manageable result. Division may also be constrained to operate within a desired frequency span, with an upper and/or lower frequency limit. Outside those limits the behaviour depends on whether gain limiting is selected. If the gain limit is being used REW treats the operation as an attempt to produce a band limited correction filter and division reverts to unity gain, blended over a 1 octave span centred on the limit frequency. If the gain limit is not being used division reverts to the numerator, offset to align with the result within the band limit.

Yes, just as you said, after setting the max gain and checking, I confirmed that the offset doesn't change and the result is the same as in 5.30.
I didn’t know about this, so whenever I needed the 1/A result, I kept using the older version of REW.
 
No. She was not chosen. I noted her now. On measurements that are already saved, will it not work when they are opened now?
It shouldn't make any difference. I'm trying to work out how it is possible for the phase traces to be red instead of the measurement colour. They always plot as the measurement colour for me.
 
The 'Save trace colors with measurement' option is checked. I opened a previously saved measurement, saved it under a different name. Closed the REW. Opened the saved measurement. But all the phase colors are still red.
 
It's the same code on all platforms. The phase trace colour comes from the measurement colour, so that's pretty strange. What build is running on the Linux machine?

I just updated to the latest beta 77 and the color is fixed to red in Windows 11 also now. Tested Linux on Mint debian edition and KDE neon -- same fixed red phase traces.
 
Back
Top