|
Microeditor Help - Versions 5.0-5.5 Discussions for Microeditor versions that use Krystal DSP Engine audio card |
|
Thread Tools | Display Modes |
#1
|
|||
|
|||
Medit 5.5 crashes XP Pro
Symptom:
When attempting to open an Medit project, a dialog box appears stating that file sizes have changed. When clicking "no" to allow the project to load, Medit crashes with a dialog box stating "Micro Editor has encountered a problem and must shut down". Same thing occurs when clicking "yes" to delete files in the loaded project. The crash is inconsistent and appears to only happen with certain projects (all of which were working fine earlier). Background: System is a Dell workstation running XP-Pro. Medit has experienced no problems on this system to date. Medit projects are on a 10GB drive. Several projects are being used as sub-projects for a larger project. (ie: project 1 is used in project 2 via "copy segments from ..."). There are 3-5 sub-projects being used in a larger project. Individual project sizes are relatively small - largest having an SF1 file around 130,000 KB in size. All projects were working fine. Krystal was removed in order to install ProTools Digi 002. Problem appears to have started after re-installing Krystal. Krystal was re-seated after problem initially occured. Protools is completely removed. I don't think it's a Krystal seating issue since other Medit projects work fine. Troubleshooting: 1)This problem is NOT consistent with all projects on the drive, so it appears to be related to the .mix file (other projects on the same drive will open just fine). Could there be a header corruption in the .mix or .sf file? 2) Moving all project folders to a different drive has same result. (original folder re-named so there is no valid file reference to the old project or drive). Attempting to open a project at the new location results in the "locate files" dialog. When files are located on the new drive, Medit crashes. 3) None of the projects or files have been compacted. An Error Check was run on the original drive, with no errors reported. 4) I can create a new project and import the original project via "append project" - and the new project will work just fine UNTIL it is closed. When attempting to re-open the newly created project, Medit crashes. Workaround: The only workaround that I've come up with so far is to create a new project, append the original project, and copy all segments into the new project. Doing this appears to result in a functioning project. Please advise ASAP if there is a better way to correct this problem. Questions: 1) Why would Medit suddenly begin to report changes in SF file size for most projects on the drive (but not all)? 2) Why is it that the SF1 files appear to be OK when opened in a different project, but indicate they have changed when attempting to open the original project in which they were created? 3) What options do I have to recover these projects?
__________________
James R. Alburger |
Currently Active Users Viewing This Thread: 1 (0 members and 1 guests) | |
|
|