I AM SO SICK OF VIDEO 17 CRASHING

MutantBlondy wrote on 7/20/2011, 7:30 AM

I am so sick of re installing, re formatting and wasting my time with a freezing and crashing program.

My Sony/Adobe Cubase/Reason/Live all work and never crash.

This is my 4th version of Video (14, 15, 16, 17) I have bought that crashes like the others.

After re installing it on another Notebook/PC, new/old XP/Wind 7 32/64, it freezes & crashes after a few days.

I have had their search program scan and the solution does not fix the problem. By reading others on forums, the same problem seems to be very common. (It seems odd that such a huge problem that hasn't been resolved in the past few years requires a buyer to pay extra money too make it work !!!)

The only solution that I can come up with is the VSTi somewhere in my system are clashing with magix.

My Hard Drive at the moment is a 2 Gig Via eSATA to a i7 Dell, 8G, Win 7 64.

Is there a problem with Movie EdPro using an external HD? I have set the settings correctly and no matter what drivers are changed etc., it still crashes.

Sorry for the frustration. I like the program and use it every few days.

This is my typical work on Movie EdPro.

Has anyone mastered this problem.

Cheers

Akash

Comments

john-auvil wrote on 7/20/2011, 10:34 AM

I think it is safe to say other Movie Edit Pro users have had crashing problems, but that is true for any software. Adobe Premiere crashes on my laptop, even their crash report system crashes on me, yet runs fine on desktop. I do not think the Movie Edit Pro has a huge problem in terms of the number of users having a crashing issue... but cetainly if I was affected, I would believe it was monumental. I think Magix has been very responsive to fixing issues (NTSC sync issues) that have been reported.

I do not think the software is the issue itself, as Movie Edit Pro has run flawless for me (and a number of friends) for a long time, and I have used the program since it was created in 2001 (Video Deluxe). It very well could be an issue with the other software you have installed. Have you checked out your startup tab in the MSCONFIG? It could be that parts of other editors are running from the startup and therefore are in conflict. Since Startup automatically starts these when you boot up, they are always on, and could be a culprit.

I would never use a external drive for the editing process, HD video and audio are far too demanding for such a transfer rate. You really need to use a internal drive for the editing (project creation) and burning. Once you have completed the project, then you can archive it to a external. How do these eSATA drives connect to the computer?

I do not have the best laptop available, it's not horrible, but still its not the best.

HP Pavilion dv6 Notebook PC
Microsoft Windows 7 Home Premium
AMD Turion II Ultra Dual-Core Mobile M640 2x2600 Mhz
4.00 GB System RAM
ATI Mobility Radeon HD 4650 Series (2.00 GB)

I use 2 AVCHD camera both capturing 1920x1080 @ 29.97fps. This footage runs staggered when I playback within Movie Edit Pro 17 Plus, but the export results have been flawless, I edit in a 1/2 resolution so I get as smooth as possible editing phase.

That isn't a program error either, its a resource issue and the fact that HD video is very much a resource hog.

I do not run any other video editors anymore, so perhaps you are on to something, maybe one of these other editors are using a protocol that is in direct conflict with Movie Edit Pro. I cannot remember the last time that I had a crash, I actually have more power outages than crashes.

When you crash, does it give you an error?

Do the crashes happen on a certain feature or does it seem random?

MutantBlondy wrote on 7/20/2011, 3:45 PM

Howdy John,

thank you for your quick reply.

I have checked my msconfig and twiddled with start drives on an off. Mt eSATA is direct into the notebook. When it crashes it comes up with a windows error on all notebooks.

When I am editing, I use/need a big chunk of 2T from my HD (eSATA). But going through what you have said, I think the problem is that I have the 'Projects, Imports, Exports'., on my E (eSATA) rather than the C drive. It usually goes fine, but thinking about what you have said, the data between the 2 are different speeds and this is causing it to crash.

The bugger with the C drive is the typical notebook slow speed.

The crashes usually happen when I have been using the program for a long time and import something new from the eSATA hard drive. When it reboots either from a system dumb, or by itself, it will crash again.

I'll change the hard drives to the one and have the external just as a storage.

Thank you again for your help.

Cheers

Akash

johnebaker wrote on 7/20/2011, 5:43 PM

Hi Akash

You do not say at what tasks you are doing at the time the notebook crashes.

I suspect that part of your problem may be due to overheating of the notebook. Video editing is very processor intensive particularly when rendering.

The eSATA drive should be fine unless the connectors are showing any signs of wear or sloppiness - in which case you may experience intermittent loss of connection.

For john-auvil eSATA is the same as the internal SATA connections except the bus is brought out to an external connector. on the computer.

I would agree with John about not editing to external USB drives, eSATA should be no problem.

John

MutantBlondy wrote on 7/20/2011, 6:15 PM

Thank you John.

The notebook actually doesn't get hot, I have the fans and odds and ends to keep it cool. Most of my work is composing and arranging; this uses up much more processing power than video (Cubse/reason/soft synths etc).

It crashes literally anywhere. The PC doesn't have a problem, the program freezes. The main thing is when I import. If it is even a new project and I am importing a simple .avi/.jpg; it freezes the program. I could start up any other program while it is frozen and there isn't a problem.

Some part of me questions the VST drivers on Magix. The VST/i that I use are as new as, Magix use older VST/DX. I was thinking that the new cubase VST3 plugings may be clashing with Magix's old VST(1) plug ins.

But I think you and John have the right solution.

Cheers

Akash

MutantBlondy wrote on 7/21/2011, 12:29 AM

Howdy again John and John,

back to the drawing board. I am just running all of the main drive, all other progs off and it still crashes.

Besides the definitions from google, how does this relate to my mess

Serious Program Error has occurred
Error in module 'ntdll.dll" (load address : 0x7730000) to address 0x7740e39e
Exception 0x0c00000005 "Access Violation"

Thank you for your time on this.

Cheers

Akash

johnebaker wrote on 7/21/2011, 6:55 AM

Try following these steps as a process of elimination. Once booted to windows in each of the steps, try running MEP and see if you can crash it. If it wont run in Safe Mode try the next step - drivers may be required which are not available in Safe Mode.

John

Scenestealer wrote on 7/25/2011, 7:41 PM

Nice work there.

It is always recommended by editing software makers that the program and project files reside on the same disc as the Operating system. Definitely keep all your captures and encodes on the Esata drive though.

I have found MEP17+ the most stable version of MEP yet and very rarely have a crash.

MutantBlondy wrote on 7/26/2011, 5:47 PM

Thank you all for your help with this. The problem is still there, but isn't as consistent as before.

Much appreciated for your time and assistance.

Cheers

Akash

caracasDGA wrote on 3/16/2014, 11:39 PM

aki tienes mi video espero que te sirva