Home Theater Forum and Systems banner

1 - 3 of 3 Posts

·
Premium Member
Joined
·
3 Posts
Discussion Starter #1
In general, V5.01 is well behaved and I have not encountered major bugs but there are a few areas that could be improved. I am running under Win7 x64.

1) When you launch the program it does not always open as a full window; sometimes it just appears as an icon in the task bar.

2) The legend in the RT60 tab is not always updated: sometimes the name of the previous measurement will remain instead of the latest measurement. Sometimes different curves like EDT, T20, or T30 will appear even though they are not selected.

3) The biggest problem for me, right now, is a bug that prevents taking successive measurements using a TASCAM US-144 MKII. The problem may be in the Tascam ASIO driver but I cannot take more than one measurement at a time (I take 4 samples per measurement). I have found that saving the data and restarting REW is faster than the suggested procedure of switching to the Java driver and then back to ASIO. Incidentallly, if I cancel the measurement, even during the fourth sweep, the buffers are cleared and it is possible to take another series of measurements.
 

·
REW Author
Joined
·
6,711 Posts
1) When you launch the program it does not always open as a full window; sometimes it just appears as an icon in the task bar.
Thanks, fixed that (occurred if window was maximised, then iconified, then REW shut down from the icon).

2) The legend in the RT60 tab is not always updated: sometimes the name of the previous measurement will remain instead of the latest measurement. Sometimes different curves like EDT, T20, or T30 will appear even though they are not selected.
The first trace should always be "Topt" rather than the measurement name, I've fixed that.

3) The biggest problem for me, right now, is a bug that prevents taking successive measurements using a TASCAM US-144 MKII. The problem may be in the Tascam ASIO driver but I cannot take more than one measurement at a time (I take 4 samples per measurement). I have found that saving the data and restarting REW is faster than the suggested procedure of switching to the Java driver and then back to ASIO. Incidentallly, if I cancel the measurement, even during the fourth sweep, the buffers are cleared and it is possible to take another series of measurements.
I haven't been able to replicate that, works well for me. What do you have the Tascam driver latency set to? A higher latency setting might help. Failing that, please start REW, take a measurement, try a second measurement (which presumably will not work) then exit REW. Look at the newest log file roomeq_wizard0.log.txt in the REW folder of your home directory (you can see the full path in REW's Help -> About box) and post the contents here (or attach the file).
 

·
Premium Member
Joined
·
3 Posts
Discussion Starter #3
Thanks John for fixing the minor bugs. With regards to my problem with the Tascam US-144 MKII, the problem is intermittent but frequent and occurs even when the latency is set to maximum.
As you sugested, I am including a log file. Here are the conditions most likely to cause the problem:
- take a set of measurements: 4 scans from 20 to 20K Hz.
- wait a minute or two (the time I take to go to the other room and reposition the microphone)
- reopen the Measure window and do a Check Levels (it seems to generate the error more often than a new measurement) but Measure also causes the problem.

Ther ReadStereo timout suggests to me a scheduling problem but:
- no other program is running in the foreground
- wireless networking is turned off
- the computer has 4GB of RAM
- the same error did not occur when I was using a SoundBlaster X-Fi external audio card.

I hope this help. I will continue to experiment to isolate the conditions under which the error occurs.

Thanks.
 

Attachments

1 - 3 of 3 Posts
Top