RoomEQWizard Crashes When Opened - Intel Mac - OSX Leopard 10.5.8

If I remember correctly, There are still some compatibility issues running REW on a Mac even in windows emulation mode.

tonyvdb said:

If I remember correctly, There are still some compatibility issues running REW on a Mac even in windows emulation mode.

Click to expand...

Does this app get updated often? Is there any other software that's similar and free?

They were working on a mac version but I am not sure where that stands at the moment.

Have a look at this file I do believe that it should work on your mac

If not, try an install V3.29.

Not sure what the problem is because I have an Intel Core 2 Duo Macbook running 10.5.8 and I just redid my calibration file for my soundcard because I got a new one. Other than it always telling me something about my impulse responses not being where they should be when I do a measurement REW runs fine for me.

fsrenduro said:

Other than it always telling me something about my impulse responses not being where they should be when I do a measurement REW runs fine for me.

Click to expand...

If it tells you that, it is not running fine, just because there is a curve doesn't mean it reflects reality...

PeteJames said:

Is there any other software that's similar and free?

Click to expand...

FuzzMeasure (Mac only) has a free trial version, not sure what the restrictions are compared to the paid version.

JohnM said:

If it tells you that, it is not running fine, just because there is a curve doesn't mean it reflects reality...

Click to expand...

What does it mean when I get this message? Since it had always done this to me but ultimately gave me measurements I assumed it was just a quirk.

Another potentially related issue on Macs is a workaround I stumbled on a while back to get the measurement process going. Steps below:

Hit Measure -> Next -> Next (again)
Change buffer from 32k to 64k and then back to 32k
Hit Cancel
Then hit Measure and continue as normal.

Someone in a thread maybe a year back posted this series of moves to get REW to work on his Mac and it worked for me as well. If I don't do this I don't get any levels.

I guess I'll have to try using XP in Boot Camp and see if it works for me.

fsrenduro said:

I guess I'll have to try using XP in Boot Camp and see if it works for me.

Click to expand...

That's how I run it on my Core 2 Duo Macbook Pro. Works great.

fsrenduro said:

What does it mean when I get this message? Since it had always done this to me but ultimately gave me measurements I assumed it was just a quirk.

Click to expand...

There can be a few causes, from not getting any input at all (so the peak position is random depending on the input noise pickup) to large delays in input or output (so the peak is shifted well outside the expected location) to gaps in the generated (which would be audible) or captured signals (not audible but visible on the scope plot as flat portions in the captured trace). It generally means something has gone wrong though, so next steps would be to check the scope plot to see if the input is OK and the impulse plot to see if the recovered impulse looks sensible.

John,

Now that I've done a new calibration file how do I make REW stop looking for my old one upon startup and just load the new one?

When you make a new calibration file from a loopback measurement (using the Make Cal... button) REW will automatically load that file next time, but you can also manually browse to the file you want using the Browse... button in the soundcard settings.