Taperssection.com
Gear / Technical Help => Recording Gear => Topic started by: Rick on April 23, 2005, 09:51:44 AM
-
http://www.sounddevices.com/download/download-722.htm
It dosn't look like they've done anything about the "media too slow" problem, so keep bugging them. :)
-
sd says that 1.32 repairs a bug that "may" have caused the "media too slow" problem.
also 1.32 supposedly fixes the repeated segment failure (garbage looping) problem.
-
I've noticed that some of the info available in the support forum posts is not presented in the public release notes on the SD site.
While we're on the topic, anyone seen the media sense problem since installing 1.32?
-
I'll let you all know tonight. I'll also see if I can get a clean transfer off the unit with the new firmware. To date, transfers have been my only issue with the 722.
-
FWIW-
I ran md5's on the files I moved off the drive last night and they veirfied on the first attempt. This was on v1.24 firmware.
-
FWIW-
I ran md5's on the files I moved off the drive last night and they veirfied on the first attempt. This was on v1.24 firmware.
were these shows you didnt get the hard drive slowness error on?
-
FWIW-
I ran md5's on the files I moved off the drive last night and they veirfied on the first attempt. This was on v1.24 firmware.
were these shows you didnt get the hard drive slowness error on?
I only pulled off one show from the weekend and yes, the first file got the media too slow error. The resulting file loops the recorded data for about 2 hours before starting a new folder, which conviently begins with the second song of the show. The rest of the show is fine. Also, the md5's checked out for the trashed first file, not that it really matters...
-
very odd...sounds like as expected, this really wasnt a HD error, but more one of a SW issue
-
very odd...sounds like as expected, this really wasnt a HD error, but more one of a SW issue
Exactly. In effect, the machine simultaneously wrote the repeating garbage file for 1+ hours and the "good" file containing the rest of the set for another 1+ hours. Obviously, the drive was able to keep up.