Hi John,
this seems a bit far fetched, but it happened to me just like that yesterday and led to some confusion:
First I set a filter on the measured IR (1/1 octave, 63 Hz, if that matters).
Then I changed to the Impulse tab and inverted the filtered impulse. The IR was displayed inverted accordingly.
Then I went back to the Filtered IR tab. The filtered IR was displayed inverted there as well.
I disabled the filter.
The display changed back to the unfiltered but suddenly NON INVERTED IR!
In the impulse tab, the 'Invert impulse' checkbox was still active, but the IR was displayed non-inverted there as well.
The phase graph also shows that it is non inverted, so it does not seem to be a matter of the display but of the data.
I tried that now on two different Windows 10 machines and with REW V5.30... and V5.31.2 and now the update V5.31.3.
It occurs every time.
My guess is that maybe the IR filtering is saving an image of the unfiltered IR data which is recovered when the filtering is disabled and it 'forgets' that in between the impulse was inverted?
I just wanted to give you a little bug report.
If you need any more information, please let me know.
Thank you for your nice work!
Eike
this seems a bit far fetched, but it happened to me just like that yesterday and led to some confusion:
First I set a filter on the measured IR (1/1 octave, 63 Hz, if that matters).
Then I changed to the Impulse tab and inverted the filtered impulse. The IR was displayed inverted accordingly.
Then I went back to the Filtered IR tab. The filtered IR was displayed inverted there as well.
I disabled the filter.
The display changed back to the unfiltered but suddenly NON INVERTED IR!
In the impulse tab, the 'Invert impulse' checkbox was still active, but the IR was displayed non-inverted there as well.
The phase graph also shows that it is non inverted, so it does not seem to be a matter of the display but of the data.
I tried that now on two different Windows 10 machines and with REW V5.30... and V5.31.2 and now the update V5.31.3.
It occurs every time.
My guess is that maybe the IR filtering is saving an image of the unfiltered IR data which is recovered when the filtering is disabled and it 'forgets' that in between the impulse was inverted?
I just wanted to give you a little bug report.
If you need any more information, please let me know.
Thank you for your nice work!
Eike