You are going through the list in numeric order, but each time a measurement is deleted the list gets shorter so you may end up trying to delete indices that are no longer where they were or no longer present at all
10ms is quite a short timeout for a measurement deletion to complete, so you are probably sending deletion requests before the previous request has completed. I'll make the API reject requests while one is already in progress.
You don't appear to be looking at the API responses. If the response isn't a 200 (OK) you need to decide what to do about it. Some API commands return a 202 (Accepted), meaning what you have asked for is being worked on and you either need to wait for it to complete or register a webhook url to be notified when it has completed. If a 400 (Bad request) is returned you need to look at the message to understand why the API isn't happy with what you asked it to do. The measurements service will return a 404 (Not found) if you try and do something with a measurement index that doesn't exist, likely because you have already shortened the list by deletions so the index is now past the end.
You are going through the list in numeric order, but each time a measurement is deleted the list gets shorter so you may end up trying to delete indices that are no longer where they were or no longer present at all
10ms is quite a short timeout for a measurement deletion to complete, so you are probably sending deletion requests before the previous request has completed. I'll make the API reject requests while one is already in progress.
You don't appear to be looking at the API responses. If the response isn't a 200 (OK) you need to decide what to do about it. Some API commands return a 202 (Accepted), meaning what you have asked for is being worked on and you either need to wait for it to complete or register a webhook url to be notified when it has completed. If a 400 (Bad request) is returned you need to look at the message to understand why the API isn't happy with what you asked it to do. The measurements service will return a 404 (Not found) if you try and do something with a measurement index that doesn't exist, likely because you have already shortened the list by deletions so the index is now past the end.
I fixed the code now reversing the loop and adjusting delays but still it works fine when SPL & Phase window is open in REW but fails when All SPL or Overlays window is open. So checking properly for response codes is a must. Automatic rejection will be great though. Also, I can't find a workaround for passing a file path from Explorer to the API due to browser security settings and importing measurements will have to stay manual. Well, so much with my limited programming skills but thanks a million for this fab work, it really opens up infinite possibilities.
I fixed the code now reversing the loop and adjusting delays but still it works fine when SPL & Phase window is open in REW but fails when All SPL or Overlays window is open. So checking properly for response codes is a must. Automatic rejection will be great though. Also, I can't find a workaround for passing a file path from Explorer to the API due to browser security settings and importing measurements will have to stay manual. Well, so much with my limited programming skills but thanks a million for this fab work, it really opens up infinite possibilities.
Builds updated today (beta 12) with these changes:
Added: All SPL graph actions has an IACC button to calculate Inter-Aural Cross Correlation coefficients
Changed: Clarity calculation uses zero phase filters
Changed: When importing multi-channel impulse response WAV files preserve their relative alignment even if the import mode is "For imports set t=0 at impulse peak"
Changed: Allow clock corrections up to 1500 ppm to be applied, with a warning
Changed: When plotting harmonics at the harmonic frequency make sure the start of each harmonic trace reflects the data start scaled by the harmonic order
Changed: Measurements API will reject delete requests while a deletion is in progress
Fixed: API documentation errors for /measurements/{id}/target-settings, target-level and room-curve-settings
Fixed: Image capture options were missing "Include timestamp"
Fixed: Fade in for two tone and three tone signals did not work properly
I received a Java exception as below with Beta 11 while "remove measurements loaded from". I had manually saved one of the loaded measurements before doing that which I am guessing might be the reason for the null point exception:
REW V5.40 Beta 11 running Azul Systems, Inc. JRE 1.8.0_402 64-bit on Windows 10 Locale: language en, keyboard GB, windows-1252 at 96 DPI Running in C:\Program Files\REW
I received a Java exception as below with Beta 11 while "remove measurements loaded from". I had manually saved one of the loaded measurements before doing that which I am guessing might be the reason for the null point exception
Changed: When importing multi-channel impulse response WAV files preserve their relative alignment even if the import mode is "For imports set t=0 at impulse peak"
Any version, though there aren't many sources of multi-channel WAV files of impulse responses. It was prompted by having to import a file of binaural responses.
well, my request is to add a dotted black line representing the maximum "possible" sum, considering only SPL, disregarding the phase, so that we can compare what we are doing with the maximum sum that the system can eventually offer
something like this
EDIT
and maybe add some shortcuts via right click on the measurement, such as flip phase, duplicate and SPL offset
and CTRL+left click to select more than one measurement and enable group movement between all measurements
The actions panels already have controls to invert polarity, add SPL offset and make a response copy. There are also invert polarity check boxes on the alignment tool.
You'll have to explain in more detail what you mean by that, particularly "enable group movement". Shift + left click can be used to select multiple traces in the graph legend.
Builds updated today (beta 13) with these changes:
Added: The /measurements/{id}/command endpoint now accepts an Add SPL offset command
Added: The /application API has a command to clear any command in progress
Changed: The /measurements/ API command endpoints will reject posted commands if a command is already in progress
Changed: The /alignment-tool/command API endpoint will reject posted commands if a command is already in progress
Changed: The /input-levels/command API returns OK rather than Accepted
Changed: Added a dotted trace to the alignment tool showing a magnitude-only summation of the measurements
Changed: When the alignment tool is opened the All SPL selections change to show only the traces being aligned. Other traces may be selected in the graph legend if desired. The original trace selections are restored when the alignment tool is closed.
Builds updated today (beta 14) with these changes:
Added: The Preferences menu has an entry to load preferences from a file, which requires a restart
Added: The measurements/{id}/eq/command endpoint accepts "Generate target measurement"
Changed: Updated CEA-2010 distortion limits to align with ANSI/CTA-2010-B R-2020
Changed: Using "Generate minimum phase" on a measurement imported from a text file which included phase will generate an IR for the measurement using the original phase data
Changed: Improved RTA fundamental lobe tracking for noisy fundamentals when not using the AES17-2015 standard notch
Fixed: When FDW unit preference changes update the IR windows dialog FDW spinners and the IR accordingly
John, good afternoon. I imported a wav file with music into the RTA window in RTA 1/48 mode. After analysis, REW saved the peaks as a measurement. But in thumbnails, the appearance of the graphs is similar to the Spectrum mode. Or is it seems to me?
The actions panels already have controls to invert polarity, add SPL offset and make a response copy. There are also invert polarity check boxes on the alignment tool.
You'll have to explain in more detail what you mean by that, particularly "enable group movement". Shift + left click can be used to select multiple traces in the graph legend.
A "move measurement to top" mouse right click option would also be quite useful. When you want to cross corr align some measurements to a measurement at the bottom, it can become dreadful to move a measurement all the way to the top even when "animate measurement list" is unticked in preferences especially if "All SPL" or Overlays windows are open.
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.
