Recent content by navid0308

  1. N

    REW Beta Release REW API beta releases

    With this mdat - 21AUG2025_REW -12.00dBFS_AVR MV -16.0dB_7 POSITIONS SEAT DOWN_Base.mdat When you hit sort, it only partially sorts. You have to click the sort button a second time for it to finish sorting it properly.
  2. N

    REW Beta Release REW API beta releases

    You should be able to right click on the measurement on the left and select offset t=0 directly for that measurement. Right clicking on the graph and selecting offset t=0 seems to automatically select the last selected measurement.
  3. N

    REW Beta Release REW API beta releases

    I should've clarified, the target is the response that's called "final". In the mdat it's leveled to 75db but here's the text file I have been using. But the last section of your message is very helpful. Seems like I will need to play around with the speaker type parameters before asking REW to...
  4. N

    REW Beta Release REW API beta releases

    Yeah those are also being kept the same. The script creates a b&k like room curve if user provides no house curve. If it gets a house curve, it disables the room curve. I think I know what the issue is…since the speaker type is none, I think it’s expecting the target and the SW response to line...
  5. N

    REW Beta Release REW API beta releases

    So the speaker type is set as None instead of “Full Range” or “Bass Limited” or “Subwoofer”. The equalizer type is also “Generic”. At the beginning of my code, these values are set to both the default EQ and the measurements/id/eq. Here’s the part of the code that’s doing it -...
  6. N

    REW Beta Release REW API beta releases

    Getting a strange EQ result for this particular subwoofer. I used the -3dB points as the start and end freq, allowed minimal boost. Speaker type is set as none since I am trying to EQ via the API. Also, I don't always get the same results between API and EQ tab. In my code I allow narrow filters...
  7. N

    REW Beta Release REW API beta releases

    Oh, I know REW sorts when importing, Here's a use case - if someone takes a bunch of measurements for spatial averaging, and then wants to group the channels together and order by position, the easiest approach is exporting impulse responses to text and then re-importing, which loses some...
  8. N

    REW Beta Release REW API beta releases

    Feature request: This is gonna sound dumb considering all the complex stuff REW can do, but can we get an option to just sort the measurements how they're sorted when dragging and dropping data?
  9. N

    REW Beta Release REW API beta releases

    This is a windows defender issue. Right click on the zip file > properties > unblock.
  10. N

    REW Beta Release REW API beta releases

    Can confirm it's behaving more predictably with the high shelf. Thank you for this update!
  11. N

    REW Beta Release REW API beta releases

    Thanks for the prompt response! Here you go. Just as a FYI, the responses are aligned to the target @ 75db, however, after FDW with 15 cycles, the level drops by about 0.5db, that's why in my screenshots you saw the level @ 74.5db.
  12. N

    REW Beta Release REW API beta releases

    With everything maxed out, it still settles on a negative shelf that drops it below target. The main issue is that the other atmos channels have similar responses but they don't get a shelf like this, so it's introducing somewhat of an imbalance between TRL and TRR speaker pair. For reference...
  13. N

    REW Beta Release REW API beta releases

    What would cause the EQ to apply such an aggressive negative high shelf? You can see in the screenshots that the equalized response is well below the target after the shelf. Is it because I am using FDW? These are the settings I used-
  14. N

    REW Beta Release REW API beta releases

    Using beta 86, Overlays > Impulse seems to be crashing using older saved measurements.
  15. N

    REW Beta Release REW API beta releases

    One issue I have been fighting with REW with is EQ. Using API, REW refuses to EQ some areas, however if I use the "Match response to target" from the EQ tab, it correctly EQs the response. Is this a known issue or are there any workarounds? This is an example but it happens in other cases as...
Back
Top