Home Theater Forum and Systems banner
1 - 16 of 16 Posts

· Premium Member
Joined
·
15,060 Posts
If I remember correctly, There are still some compatibility issues running REW on a Mac even in windows emulation mode.
 

· Premium Member
Joined
·
15,060 Posts
They were working on a mac version but I am not sure where that stands at the moment.
 

· Premium Member
Joined
·
15,060 Posts
Have a look at this file I do believe that it should work on your mac
 

· Registered
Joined
·
31 Posts
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.
 

· Registered
Joined
·
31 Posts
If it tells you that, it is not running fine, just because there is a curve doesn't mean it reflects reality...
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.
 

· Premium Member
Joined
·
6,709 Posts
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.
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.
 

· Registered
Joined
·
31 Posts
I think the problem may have been my calibration was done at 48k instead of 44.1k with my previous soundcard. When I did my calibration for my new us-122 there was a very noticeable improvement in frequency response when I did it at 44.1, so there may be an issue with 48k on my computer. Either way I did some measurements today and am no longer getting impulse response warnings. I'm also noticing that my measurements are mirroring what I'm getting with my XTZ Room Analyzer system.



 

· Premium Member
Joined
·
6,709 Posts
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.
 

· Registered
Joined
·
31 Posts
I did the 'Make Cal' process five times now with my new Tascam us-122, but every time I open REW it says it can't find the UCA202/Xenyx 802 cal file (which was my previous setup). I always have to manually load the new cal file for my soundcard, the mic cal still loads by itself.

Anyway here's the difference between my calibrations when I do it as 48k vs the much flatter 44.1




The 48k one drops of before 20hz
 
1 - 16 of 16 Posts
This is an older thread, you may not receive a response, and could be reviving an old thread. Please consider creating a new thread.
Top