I don't think so. Local features of the responses near the chosen merge frequency would shift the average, taking away your ability to choose a point in the response that has the correct level, whatever that may be. The responses may also be curved near the merge, so again the average would be incorrect.Wouldn't it make sense for the reference level to also be calculated from an average over that same span?
That's a fault of the driver, not REW. When devices disappear REW does revert to default.When using HDMI as output device and AVR is shut off REW hangs and needs to be killed because it gets irresponsive.
Hi John,I don't think so. Local features of the responses near the chosen merge frequency would shift the average, taking away your ability to choose a point in the response that has the correct level, whatever that may be. The responses may also be curved near the merge, so again the average would be incorrect.
There is no equivalence. In the 5.31 builds all measurements are selected all the time, each new measurement is selected as it is generated or loaded. You are only changing whether or not the corresponding trace is plotted. In the 5.40 builds traces are generated when measurements are selected. If you want 5.31-style behaviour select all and use the graph legend checkboxes to turn traces on or off.Is it only me or is the API version of REW slower and more demanding on the pc than the regular "non beta version"? Especially when selecting multiple measurements in the ALL SPL tab?
Is there anything I can do about it and "increase the speed"?
Rew seems to "think" alot when selecting/deselecting(highlighting) multiple measuremente
When I say multiple I mean more than 100.
Ok. Thank you i understand now.There is no equivalence. In the 5.31 builds all measurements are selected all the time, each new measurement is selected as it is generated or loaded. You are only changing whether or not the corresponding trace is plotted. In the 5.40 builds traces are generated when measurements are selected. If you want 5.31-style behaviour select all and use the graph legend checkboxes to turn traces on or off.
Okay, perfect, thank you.That is not a bug. Per the notes:
- The result of arithmetic on measurements that have compatible impulse responses is smoothed using the measurement A smoothing, unsmoothed data is used during the calculations. Other measurements use whatever smoothing they already had applied during the calculations and the result is treated as unsmoothed (or 1/48 octave smoothed if data is 96 PPO).
If you want to ignore the measurement impulse responses you could make magnitude-only copies and do arithmetic on those copies.
Thanks, looks like that happens if the measurement being deleted is the currently selected measurement. I have fixed it for the next build.When you remove a measurement from REW, the measurement BEFORE the deleted measurement will go back to REW's default EQ target type even if it's target type is set to "None" before the deletion of the measurement after it.
Builds updated today (beta 41) with these changes:
- Fixed: Ctrl+TAB in overlay measurements list popup could skip some measurements
Yes.Is this how this new function is supposed to work?
Maybe, happy to hear opinions on that.Wouldn't it be interesting if the selected measurement were to be skipped one by one along with the floating panel?
If by "response time" you mean the delay between sending a signal to the interface and getting a signal back from it then no, that isn't possible due to the various buffers between data generation and the interface receiving data from the OS. The only useable references are the inputs from the interface, timing is relative to the signals on an input.Is it possible to measure the response time of an the audio interface like the Steinberg UR22C,using the loopback cable
Thank for the quick response.If by "response time" you mean the delay between sending a signal to the interface and getting a signal back from it then no, that isn't possible due to the various buffers between data generation and the interface receiving data from the OS. The only useable references are the inputs from the interface, timing is relative to the signals on an input.
Yes.Would a phono cable from line output to line input represent a valid loopback setup
Are you referring to the graph legend area? I can tab back and forth through that. Focus has to be on the legend first, e.g. by clicking on a trace checkbox. Seems to behave the same as a few earlier builds I have tried.In All SPL tab when selecting measurements its no longer possible to use the TAB or SHIFT+TAB key to "scroll" between measurements in the lowest part of the screen to then "activate/deactivate" with the SPACE key.
False alarm. Its working now. Yes i was referring to the grapgh legend area. Sorry.Are you referring to the graph legend area? I can tab back and forth through that. Focus has to be on the legend first, e.g. by clicking on a trace checkbox. Seems to behave the same as a few earlier builds I have tried.