Quote:
Originally Posted by Jimmy James
For me, 5 or 6 years on a HDD is a long time, but more on that later. Are you running Windows 7, 8, or 10?
edit: what is your Mobo, and interface, just so we know. You can never give to many specs
|
Don't know the MOBO offhand, I'll take a look a bit later. This whole thing is actually happening right when I'm about to upgrade my little 120GB system SSD to a brand new 500GB one, so I'll be pulling the side off the case pretty quick here.
Interface is a Steinberg UR44. It's been great since I got it a few years back, but I haven't checked for new drivers for a while, guess I should probably do that.
Oh, and I'm running Windows 7 64 bit.
Quote:
Originally Posted by karbomusic
I'd be curious if CPU bound during the issue, what the disk throughput in Reapers perf window shows and what the System event log says in relation to disk errors (Start > run > Eventvwr.msc) and, how long is the file and/or how large is the final file in MB/GB? I know some of this is after the fact but the curiosity is there.
|
Hooboy. That would all be pretty difficult. You see, I was under a pretty tight deadline for finishing this audiobook when I noticed these problems, but I didn't have time to do anything about them. I would just record another take and keep going. THEN, tens of thousands of words spoken later, I would edit them for timing and to remove mistakes and whatnot. To make this easier, I used Reaper to dynamically split all these transients and silences and automatically delete the silences, so say ten or so larger files that added up to a half hour long chapter reading became several hundred very small files spaced apart where silences between them used to be.
THEN, the company has standards for their audiobooks that must be met, and one of them is that the finished product must be rendered as a 192khz .mp3. So the size of the finished files doesn't reflect what they would be if they had been kept as .wav or FLAC files and mixed down that way, like we might usually do. A half hour chapter .mp3 would come out to about 30 to 35 MB.
So basically what I'm saying is that I noticed the problem but I was in a time crunch and I recorded over the problem parts and did a dozen or so more hours of work before the project was done, and the kind of detailed data you're talking about is buried so deep by now I wouldn't even know where to begin.
Quote:
Originally Posted by serr
I'd still shotgun the drive.
Got a backup clone of a known good OS? Boot into it and test any corrupt OS theories.
|
Okay, now I know this might make me look uncool, but is 'shotgunning' the drive a slang term for some technical procedure I don't know about, or are you just suggesting I get a new drive and destroy the one I have?
I mentioned above that I have a new SSD to replace the one that's in there. I was just going to clone everything from the old drive to the new one and just keep on groovin'. Should I do something different with it? I use AOMEI Backupper and there's a full backup a couple months ago with weekly incremental backups since. I'm not sure if I understand what you mean. Are you saying I should restore from one of those backups then run CHKDSK and such from within Windows?
Thank you very much for the advice. I promise, I'm not thick in the head, I just haven't had to do this sort of thing for a while and I need to shift gears and warm up.