REW Beta Release REW API beta releases

[sm52]

I tried all the measurements one by one. Now there is no mistake.

 

[John Mulcahy]

OK. I have added an extra check anyway.

 

[yobuntu]

Hello dear REW developer John Malcahy, dear users!
Just a question ... here on iMac the typo / fonts in REW are really hard to read and thin, somehow unsharp too.

Is it the Mac version only or is my installation not ideal?

KR
yo

 

[John Mulcahy]

here on iMac the typo / fonts in REW are really hard to read and thin, somehow unsharp too.

Odd. You can try changing the font size in the View preferences.

 

[yobuntu]

Unfortunately, this doesn't change the appearance; I wonder if other Mac users have the same problem.

Update:
Did a completely new installation, nothing changed. If I rise the font size to 22 or bigger the typo is OKish, but huge even on the 27", and yes, it's the fine Retina screen.
There's no other app that looks this way.

 

[John Mulcahy]

Looks crisp on my Mac, retina display though.

 

[navid0308]

Running into a strange issue with 105 - delays are not being applied to measurements when they are being summed.

In this example SW20 was delayed by -1ms, and the predicted graph shows a lot more output. However, clicking on "Aligned sum" produces the purple graph which does not match. When right clicking on the "Aligned sum" measurement, it shows that it was generated by applying -1ms delay to measurement B, which is correct. Mdat file is attached as well.

Edit: To add another data point, if I Offset t=0 for SW20 by +1ms and then do a "Vector sum" of SW10 and SW20, I still get the same result as the purple "Aligned sum" graph.

 

[John Mulcahy]

Running into a strange issue with 105 - delays are not being applied to measurements when they are being summed.

The problem is that the result gets the window settings from the first measurement, but its left window is too narrow to span to the start of the aligned sum IR. I have fixed it for the next build, in the meantime you can manually increase the left window.

 

[navid0308]

The problem is that the result gets the window settings from the first measurement, but its left window is too narrow to span to the start of the aligned sum IR. I have fixed it for the next build, in the meantime you can manually increase the left window.

That's exactly the answer I needed. I adjusted the code to cycle through the SW responses being combined and use the aggregate max IR window for the combined response. Solved the issue I was having.

 

[HD MOVIE SOURCE]

Just checking that this functionality is intended here. Typically, when I smooth a response to psychoacoustic and export it, it would be exported as text with that smoothing even if none was applied at the export level. When exporting as text now it exports with no smoothing even if smoothing has been applied on the measurement screen.

I'm just checking that this is normal, and that if you want any smoothing to be applied to your text export it can only be done on the export screen, right?

 

[John Mulcahy]

On the export dialog you can either check the box "Use smoothing of measurement" or select the smoothing you want.

 

[HD MOVIE SOURCE]

On the export dialog you can either check the box "Use smoothing of measurement" or select the smoothing you want.

Thank you, makes sense,

 

[jackyshu]

Retina Display Rendering Issue in REW on MacBook M1 Pro
Hi there,

I’ve been experiencing an issue with REW on my MacBook M1 Pro 16-inch, running macOS Tahoe 26.1. The problem is that REW doesn’t render properly on my Retina display — everything looks blurry, including fonts and lines.

At first, I thought it might be an issue with my operating system. So, I did the following:

1. I installed a fresh version of macOS Tahoe 26.1.
2. I reinstalled REW on this clean setup.
3. Unfortunately, the problem is still there, and REW continues to display poorly.

I’ve attached a screenshot for reference.

I would appreciate any help or advice on how to fix this!

Thanks in advance!

 

[John Mulcahy]

Retina Display Rendering Issue in REW on MacBook M1 Pro

This seems to be a Tahoe "feature", I'm looking for a way to resolve it.

 

[MinhPT]

This seems to be a Tahoe "feature", I'm looking for a way to resolve it.

I had the same issue after upgraded to Tahoe
I love to use REW.
Big thank to you.

 

[John Mulcahy]

Builds updated today (beta 106) with these changes:

• Changed: Java runtime updated to Java 11
• Changed: Installer uninstalls the previous version
• Changed: "Scale fonts for display DPI" View preference has been removed, font scaling is now automatic
• Changed: Add support for UMM-6 with a device name of UMM6
• Changed: The menu.properties file has entries for SELECT_DESTINATION_TITLE and SELECT_DESTINATION_TEXT, used when trying to save a file without a destination
• Fixed: Aligned sum notes showed additional delays if remove time delay was selected
• Fixed: Aligned sum window settings were from the first measurement, which might not span the result
• Fixed: Null pointer exception could occur in RT60 decay calculation if the measurement did not have valid T20 data at some frequencies

The big change is the Java runtime update to Java 11, made necessary by macOS Tahoe breaking display scaling for Java 8 applications. That required quite a lot of internal modification, particularly around icon handling. If you notice any odd appearance or behaviours please let me know here.

 

[serko70]

Builds updated today (beta 106) with these changes:

• Changed: Java runtime updated to Java 11
• Changed: Installer uninstalls the previous version
• Changed: "Scale fonts for display DPI" View preference has been removed, font scaling is now automatic
• Changed: Add support for UMM-6 with a device name of UMM6
• Changed: The menu.properties file has entries for SELECT_DESTINATION_TITLE and SELECT_DESTINATION_TEXT, used when trying to save a file without a destination
• Fixed: Aligned sum notes showed additional delays if remove time delay was selected
• Fixed: Aligned sum window settings were from the first measurement, which might not span the result
• Fixed: Null pointer exception could occur in RT60 decay calculation if the measurement did not have valid T20 data at some frequencies

The big change is the Java runtime update to Java 11, made necessary by macOS Tahoe breaking display scaling for Java 8 applications. That required quite a lot of internal modification, particularly around icon handling. If you notice any odd appearance or behaviours please let me know here.

Most API calls are throwing 500 error with Beta 106. Java 11 engine seems not to like fetch() function.Can you think of an easy fix?

 

[John Mulcahy]

Please attach the diagnostic file generated from the help menu. The runtime distribution may be missing a class, it's all modular with Java 11 so another module may be needed.

 

[serko70]

Here you go...

 

[John Mulcahy]

I have updated the Windows-x64 build to add an extra module GSON requires, please try it now.

 

[serko70]

I confirm the problem is now fixed. Thanks John.

 

[John Mulcahy]

All the builds have now been updated with additional runtime modules for the API.

 

[navid0308]

If you low pass a response, the IR peak "Ref" flag does not update in the low passed measurement, it just carries over from the original measurement. Is this expected behavior?

 

[John Mulcahy]

If you low pass a response, the IR peak "Ref" flag does not update in the low passed measurement, it just carries over from the original measurement. Is this expected behavior?

Yes, the equalised measurement inherits its window settings from the source measurement.

 

[Fabsen]

Getting this error during installation on Windows 11, latest Version: