DrP
01-11-2006, 10:14 PM
I've attempted to edit a recording that got washed out half way due to rain fade (I didn't know it had a problem before I loaded it into VR). Up to the point of the rain fade, all is well, but after VR has popped up its warning about difficulty seeking into the fade affected area, its CPU use stays pegged at 100%, even though I can continue to edit the file once I'm past the bad bit.
Obviously, the ultimate solution is to QSF the file, but something is still a bit awry with the CPU use being pegged at 100%.
****
Well how odd is this, after sitting pegged at 100% for a few minutes (during which time I could move around and edit etc), its gone back to zero. Is VR doing a complete scan of the file in the background after it detected seeking problems?
Obviously, the ultimate solution is to QSF the file, but something is still a bit awry with the CPU use being pegged at 100%.
****
Well how odd is this, after sitting pegged at 100% for a few minutes (during which time I could move around and edit etc), its gone back to zero. Is VR doing a complete scan of the file in the background after it detected seeking problems?