|
I have noticed the same problem. It happens when KeyRite tries to access a file with 0 byte length. It just hangs and only Task Manager can shut it down. I found this because I was using a CD ripper that accesses the CDDB to assign names to the tracks. These names are long and of course have spaces. When I used KeyRite on one of these files, is would play the file OK except for the wobble (other thread). Next I would attempt to save the output file using the same name but adding a -1 or +1 before .wav and presto, KeyRite would wipe out the input file and the byte length would be 0 bytes. Any new attempt to access the file would give the lock-up you suggest. This always happens! An example file name is "test file.wav" = input "test file-1.wav" = output. I know that long file names are supposed to be supported, but I think the spaces are giving KeyRite fits. If you remove the spaces, no more file trashing.
|