Recent content by 3ll3d00d

the measurement signal is attached ok I didn't know that but it still doesn't explain how simply opening in audacity and exporting as a wav with the same channel mapping makes it import ok. The only apparent difference is the original is 32bit float while the exported is 24bit pcm.

my usual audio device is out of action so have fallen back to my RME Fireface 800 which I've never been able to get working in a REW -> RME -> JRiver -> RME multiclient chain I don't see how it can be the timing ref causing an issue when simply opening it in audacity and saving to a new wav...

another oddity, I can't upload the file, it uploads and gets stuck at 100% but won't actually accept it (but doesn't error). file can be downloaded via this link

actually it's not a gain issue, I ramped up the gain in the playback system all the way so that the captured trace peaks at 0dBFS I then imported this into audacity and exported it straight back out as a wav, this version is read fine by REW so it's some file format issue perhaps? attached...

I was about to post the recorded data but had pruned some unnecessary channels to reduce the size, I had also amplified the signal somewhat (as I was trimming it in audacity and wanted to see the waveform). I imported that back into REW to check it was ok and saw the channel was imported...

I'm recording the output of a system to a multichannel wav file then importing into REW (latest beta) using the "import Sweep" option. The system does have some inherent delay because it's a multiway setup with a matched delay subtractive crossover, I think the total system delay is in the 20ms...

sure

not sure if it's an issue with these builds or an existing issue but impulse > limits > fit to data doesn't work if the offset is massive e.g. the measurement reports this Delay -42,391.1745 ms (-14,540.173 m, -(47704 ft)) relative to Loopback from 25: Computer 3 to 3: Computer 25 with no...

OK, like i say it's a bit surprising behaviour to see a legend not match the chart but this is why I said bug? as I thought it might be by design taking a step back, what I was trying to do was quickly normalise some set of curves to the same magnitude at a certain frequency and eyeballing...

to reproduce open the SPL view use the SPL offset option to add/remove some dB legend does not update to show the visible magnitude click "Add offset to data" legend updates for me, this is a bug as the legend describes the graph so it should agree with the displayed data not the stored data

thanks, that's much quicker though moving a cursor is a bit fiddly compared to just entering a number. It would be nice to have the same options in this view as in the single measurement IR view.

This behaviour seems a little odd to me, probably undesirable but also probably not commonly encountered & perhaps there is a different way to fix this. Situation is a set of measurements taken on and off axis with a timing reference for speaker design. I forgot to set the offset in the...

Who said anything about a single measurement? Not me at least, regardless the point is to add a potentially useful tool, if the user wants to abuse that them that's up them.

the above would be nice as a feed into EQ i.e. make the +/- x dB boundary user configurable and allow the user to adjust the target slope then ask the EQ to generate filters to make it fit

nothing in the logs roomeq_wizard0.log.txt says Apr 14, 2020 4:26:22 PM roomeqwizard.RoomEQ_Wizard main INFO: REW V5.20 Beta 47 running JRE 1.8.0_201 64-bit on linux 5.4.0-4-amd64, en, UTF-8 rew_output.txt just has REW V5.20 Beta 47 startup on 14-Apr-2020 16:26:22