Mutley Eugenius
09-01-2010, 04:19 PM
Minor Breakthrough on Open Project Crashes.
I had a project that has a bad element in it somewhere (suspected VST Plugin) which routinely crashed SE every time I opened it. The latest save, all the previous saves in the folder would crash on opening. This didn't make any sense as the program had the project open all the time throughout the saving of those backup versions, so why wouldn't it be able to open it now?
After hours of mindnumbing open-crash-open-crash cyclic redundancy, I had an idea. I noticed that SE will fire up with the timeline zoomed at the last scale that it had, and will also open projects at the size of the last zoom setting.
So I re-scaled the timeline before I tried to open the project (zooming out a long way). Then the project magically opened. This is probably because every time SE tried to access the bad element, it had to draw an icon of it, and this drawing process caused the crash. By zooming out, I reduced the clip to smaller than icon size, bypassing SE's requirement to display the icon for that bad element. This enabled me to go to the beginning of the project & then zoom in really close, then pan forward through the project, and when it gets to the bad part it will crash. Then I could open it again the same way & delete the chunk of bad data, and re-do it, thus saving me from having to re-do the whole project.
You can also delete chunks of the timeline one by one & find the area that was causing the crash till you can narrow it down to a bad plug-in.
If you're having diffficulties, most likely the problem is not the application, not the ptoject file, or any of its sub saves, but a corrupted media file or a 3rd Party plug-in.
Another trick (in the wall) that has proven workable for opening a project with bad elements is to rename the folder that the project's elements are contained in. The project will load, slowly, but will not be able to find any of the source files, so they will all be highlighted in red. (Hopefully none of them are targa files, because loss of a targa file has also been known to cause SE to crash.)
Once it opens, sections of it can be copied out and saved into new projects. Then the source file directories can be renamed correctly and opening the project should restore connection to the source elements so that it will load. Then the sections can be re-rendered & reassembled in another project.
It can prove to be a very useful workaround, and I hope these tips help others solve difficulties.
I had a project that has a bad element in it somewhere (suspected VST Plugin) which routinely crashed SE every time I opened it. The latest save, all the previous saves in the folder would crash on opening. This didn't make any sense as the program had the project open all the time throughout the saving of those backup versions, so why wouldn't it be able to open it now?
After hours of mindnumbing open-crash-open-crash cyclic redundancy, I had an idea. I noticed that SE will fire up with the timeline zoomed at the last scale that it had, and will also open projects at the size of the last zoom setting.
So I re-scaled the timeline before I tried to open the project (zooming out a long way). Then the project magically opened. This is probably because every time SE tried to access the bad element, it had to draw an icon of it, and this drawing process caused the crash. By zooming out, I reduced the clip to smaller than icon size, bypassing SE's requirement to display the icon for that bad element. This enabled me to go to the beginning of the project & then zoom in really close, then pan forward through the project, and when it gets to the bad part it will crash. Then I could open it again the same way & delete the chunk of bad data, and re-do it, thus saving me from having to re-do the whole project.
You can also delete chunks of the timeline one by one & find the area that was causing the crash till you can narrow it down to a bad plug-in.
If you're having diffficulties, most likely the problem is not the application, not the ptoject file, or any of its sub saves, but a corrupted media file or a 3rd Party plug-in.
Another trick (in the wall) that has proven workable for opening a project with bad elements is to rename the folder that the project's elements are contained in. The project will load, slowly, but will not be able to find any of the source files, so they will all be highlighted in red. (Hopefully none of them are targa files, because loss of a targa file has also been known to cause SE to crash.)
Once it opens, sections of it can be copied out and saved into new projects. Then the source file directories can be renamed correctly and opening the project should restore connection to the source elements so that it will load. Then the sections can be re-rendered & reassembled in another project.
It can prove to be a very useful workaround, and I hope these tips help others solve difficulties.