Hi John,
That's a fair point. REW can't know the intent behind a rename.
Two possible approaches come to mind:
Keep a fixed "LFE" entry in the dropdown that cannot be renamed — only remapped to a hardware channel. This preserves the semantic meaning regardless of the label.
Add a dedicated...
Hi @John Mulcahy ,
I'd like to report a small bug I've reproduced in the current beta.
When the LFE channel is renamed to a custom name, the -10 dB option during measurement stops working. It seems the feature relies on the hardcoded "LFE" channel name rather than the user-defined one.
Would it...
having a not urgent request.
would like to be able to tune the "Configurable PEQ" equaliser settings via the api if it's possible.
currently the POST "/measurements/{id}/equaliser" do not allow it.
hello,
the measurement was imported from API via "/import/frequency-response-data"
tried to call "/measurements/{id}/equaliser" after the error occurred, it returns HTTP 500.
I'm using blocking API mode, is some extra delay required before calling "match target" after the import ?
hello,
just want to signal a bug with the api function "match target'.
this is not happening all the times. sometimes I get a NullPointerException after calling "/measurements/{UUID}/eq/command" with "{"command":"Match target"}"
but the command via the application interface work well and after...
hello,
at high frequency the filters in the target settings and the eq filters panel do not produce same results for equals filter.
the generate measurement from filter and generate measurement from target shape are different.
If you can verify please, it would be great.
Currently, to generate a measurement from the target shape, we’re forced to use an existing measurement in order to send the command:
POST /measurements/{id}/eq/command → "Generate target measurement"
Sometimes, no measurement exists yet. That’s why I’d like to be able to trigger this command...
hello,
having troubles with API to set ir windows.
if I try to set addMTW to true, the entire app freeze and no other choice to kill the task.
no log to rew_output.txt file.
your help is very appreciated.
thank you for your response. I can see 128,2 ppm for the bad one:
The good one have -34 ppm.
This problem occur more frequently. What can you recommend to prevent this ?
Hello,
I’m not sure if I’m the only one seeing this, but when I run a measurement the impulse response is sometimes correct and sometimes not. All the other graphs look fine. only the impulse response is affected. I’ve attached screenshots to illustrate the issue:
this is ok:
this is not...
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.