I have had the same problem myself and I'm using SP2. I have had this problem twice within the past month. One should not have to be burdened with the added concern of having to make multiple copies for backup when working with multi-track multi-file editing, especially for these prices. The work is enough to have to juggle in your head. I have witnessed nothing extraordinary about any procedures that I have been performing at the time or saving, rendering or opening prior to experiencing this problem.
So far I have read of no solution, nor any response on this issue from ULEAD.
tavideos wrote:I upgraded from VS8 to MSP8 several weeks ago. I’ve been using VS since version 6 and have been very pleased with the results. I needed to upgrade because I’m doing more multi-camera editing now. I like the layout and ease of use of MSP8 but can’t tolerate it’s behavior. Over the past month I’ve worked on 6 or 7 projects and MSP8 crashed at least once on all of them. On two of the projects, it couldn’t even open the project, “File Reading Error”. Lost 4 hours of work. I tried everything to get it to open including searching on here and elsewhere for help. The other time I got the file reading error, which was this morning, it did finally open one of the older project files, scared me into posting this to see if anyone has any answers as to why this is happening.
If I can’t get this solved, I don’t think I can ever trust MSP8. I do wedding’s and basketball games for the local high school and college. I can’t afford to lose possibly 8 to 10 hours of work. I can tolerate the crashes, I’m sure some of them are related to something I did, usually trying to work to fast. What I can’t tolerate, is a NLE that can’t open a file that it created. Unacceptable!
I have emailed Ulead support, I don't expect any results from them any time soon. I had to contact support about a damaged setup file, that took 2 weeks to get resolved.
My setup XP sp1
P4 2.53 Ghz
1 gig ram
Software Only what I need for editing
Reinstalled MSP8 twice, installed hot fix. MSP8 seemed to
crash less before the hot fix.
Primekid wrote:...... One should not have to be burdened with the added concern of having to make multiple copies for backup when working with multi-track multi-file editing, especially for these prices......
My suggestion for saving under different names (2-3 should be sufficient) is nothing to do with the reliability of the software.
it is
1. A safety measure in case of a computer malfunction or power cut.
2. The ability to be able to change ones mind and go back to a previous point in time.
My comment on the issue of making back-up copies was particularly in regards to the issue of software reliability as was the thread originators particular issue.
I am otherwise fully aware of their general purpose and practicality.
Thank you nonetheless.
sjj1805 wrote:
My suggestion for saving under different names (2-3 should be sufficient) is nothing to do with the reliability of the software.
it is
1. A safety measure in case of a computer malfunction or power cut.
2. The ability to be able to change ones mind and go back to a previous point in time.
[quote="Primekid"] One should not have to be burdened with the added concern of having to make multiple copies for backup when working with multi-track multi-file editing, especially for these prices. The work is enough to have to juggle in your head.
Well said, I agree. I'm not convinced this would even help with this issue. The first time this happened to me I had multiple copies, none would open.
tavideos
When you save under a new name it is then a good idea to close the program and re-open it to ensure your files haven't become corrupted. Otherwise the auto save every x minutes will simply be saving already corrupted files.
This applies to anything you do with a computer not just Ulead programs.
If its any consolation I too learned the hard way over the years. I thought I had a good back up system with my Home Accounts program, regularly saving onto 3 different floppy disks using a rotational method only to discover after a serious crash that all 3 floppies saved a week apart from each other contained the same gliche!
Now why are you so intent upon attacking users who are trying to pass on advice gained from years of experience of resolving their own past errors.
Now why are you so intent upon attacking users who are trying to pass on advice gained from years of experience of resolving their own past errors.
Steve J
Steve, I do not understand why you feel like your being attacked. I very much appreaciate advice from more experienced users. I am just very diappointed that users would have to make multiple copies of a project (and make sure there not corrupt) with an NLE program as good as MSP8. Even if MSP8 does open one of the saved projects when this happens, the user stands a chance of losing 30 minute's or hour's of work. How often are you saying to make a back up, close and re-open?
Like I said, I have been using VS for 6 years and have never had this sort of problem. I have never used any program that would not open a project that it created for no reason.
Thanks for clearing that point up, perhaps I am just getting old and edgy
I would save under a different filename when I get to a point where I am happy with my work so far so that I get the added feeling of security knowing I can always revert to this particular point. It is a matter of where the project has reached and not after a specific interval of time.
The best time to close and re-open is when you save under that different name, again to satisfy yourself that you have reached a point to which you can return.
This is the response that I have received from Ulead.
We have some reports from some users that they are having problems in saving the project file in MSP 8. Some have said that their projects become corrupted after editing it and some said that their project file can't be used again after encountering a system hang while editing or encoding it.
Currently, the problem is not yet encountered in our systems after a series of simulations in our office computers. However, we are still gathering some information to find a fix for this problem that we could possibly add in the upcoming patch for MediaStudio Pro 8.
Temporaraily, we suggest disabling the auto-save feature in the program's Preferences (press F6) and creating a backup file whenever you save your project as a countermeasure for this problem.
Please visit our website regularly for any updates.
I received the same this morning. Look's like they won't be able to correct this issue until it occurs on there systems. At least we know they Ulead is aware of it and there are more reports of this error.
Not sure I understand why there saying to disable the auto-save. One of those "auto-save" copies is the one that I finally got to open the last time this happened.
Working normally in the software it appears to crash for some reason. Restarting the program it won't open the main dvp or any of the backup dvp files.
Restarting the computer it now has no backup files, instead there are two files in the backup folder that refuse to delete. One a 0KB file named Z then 2 asian looking characters and another 6MB .lan file with a title that looks like a section of one of my avi file names. The main dvp still won't open, gives "file reading error".
And now my external hard drive is behaving extremely strangely (that's where I keep all my avi and project files). If I lose the files on that I'll really have to start again, reimporting the avi files of the dv tapes and everything. Plus everything else on there will be lost. This isn't just annoying anymore. I shouldn't have a virus, I have an up to date checker and I scanned only a couple days ago. If the software has corrupted the drive it was saving to then I don't know what I'm going to do.
Off to do some serious fixing work and get ulead the hell off my system.
I can now confirm that the corrupt files mediastudio created on crashing have utterly destroyed my external hard drive. It can no longer be accessed in any way and will have to be sent off for file recovery meaning I have at least temporarily and possibly forever lost all my video files as well as several other folders of personal data some of which is irreplaceable.
I suspect this is a result of the existing problem in connection with the fact that I was writing direct to an external hard drive rather than a regular one. But if this is a potential consequence of the current software issue then I think ulead need to take it a lot more seriously. If they can tell me how to do it I will give them my system and application logs for today, there's a lot of errors and warnings in there from during the time everything went wrong.
I think you may be putting the cart before the horse. It's far more likely that a fault in the HDD was causing the software problems than vice-versa.
To that point: I have MS8 on 10 systems. These are a mix of Opteron, Athlon64, Intel and AthlonXP. All are WinXP Pro SP2 or Home SP2.
I have had one, just one, file corruption and that was associated with a WD 30g that suffered a hardware failure. I've had two of that model HDD fail the same way and one wasn't in a video system; it was in the audio workstation which usually runs Cubase.
Anecdote on h/w vs. s/w failures:
I recently had a series of problems with an ATI All in Wonder's drivers crashing at unpredictable intervals. Weeks of trying a fix with ATI tech support got us nowhere.
Just as we were preparing an RMA the system halted at bootup showing corrupted info for the primary slave HDD. I removed the drive, put it into a USB case & plugged it into another system; it worked fine. Put it back in and it again failed.
The lights went on; bad cable. After replacing the cable the All in Wonders drivers all of a sudden were stable. The cable was causing the ATI's drivers to crash if/when they accessed the system swapfile.
A fault in my brand new well reviewed external hard drive just happened to cause the same problem everyone else on the board is already talking about?
It's possible, if the fault wasn't already well reported I might consider it, but an awful lot of people have had the same fault completely unrelated to their hard drives.
That it crashed and burned my external drive is probably related to write speeds, according to my techy flatmate, cause the write speed for an external hard drive is slower than an internal one and so apparantly you shouldn't use them for live stuff or something.
But I really don't think the hard drive caused the original break down.
It's highly unlikely that a software fault would cause hardware failure. Period.
A brand new, highly decorated HDD can fail if (for example) your PC case has inadequate cooling.
Don't get me wrong - I'd be the first to blame MSP if the only problem were a corrupted project file, but a knackered set of data on the drive points to a problem with the drive or the system in which it was installed. If you really want to blame it on something other than the hardware, the operating system comes next. Last is the application (MSP). User comes somewhere in the list, the position in the list varying by competence.
The fact of having to do it, not the method. 