Why does Magix Movie Edit Pro Plus 2015 have incorrect defaults, also Error 5???

clement5 wrote on 3/19/2015, 2:00 PM

If the video is at frame rate 29.x frame rate why on earth does it default to PAL when the movie is obviously NTSC? After all the Western hemisphere and Japan as well as some other Asian countries used NTSC and have old home movies in that format. If they wish to be an alternative to Adobe, who supports NTSC well, they need to do the same.

Then when NTSC is selected in the burning menu it defaults to bottom field first when NTSC is almost always top field first. They hid this item in an advanced menu when it used to be on the regular menu. So one must always check the advanced menus. This is a consistent problem all the time.

Incidentally the Error 5 DBK "error in BurnProject: 10 - movie encoding failed" is NOT solved by just updating. However by diddling the burn parameters and in particular decreasing the amount of space it went away. I can not guarantee that this is the fix because I went back and selected NTSC, then AC3 256, progressive, high accuracy, and then decreased the output size a bit.

Windows 7 Pro 64bit, Amd Athlon II

Comments

johnebaker wrote on 3/19/2015, 4:48 PM

Easily fixed:-

. . . . If the video is at frame rate 29.x frame rate why on earth does it default to PAL when the movie is obviously NTSC?. . . .

Set the project settings (1) as you require and then check the tick box (2) as shown in the example below - all new projects will start with these settings.

. . . . Then when NTSC is selected in the burning menu it defaults to bottom field first when NTSC is almost always top field first . . . .

Open the Advanced button and change the parameters to those you require. Close the advanced window adjust the Bitrate if required then click the Disc icon (3) - save the settings in the default folder giving the preset a meaningful name which will appear in the list of presets (4).

. . . . Error 5 DBK "error in BurnProject: 10 - movie encoding failed" is NOT solved by just updating . . . .

Updating the Burn Routines and the program are and should always be the first steps of several remedial actions to be taken.

There are several other potential causes, however updating does fix a lot of the problems users have.

HTH

John EB

browj2 wrote on 3/19/2015, 6:08 PM

Hi,

Did you update to the latest patch?

clement5 wrote on 3/19/2015, 7:27 PM

Yes, I have updated to the latest path, but when selecting NTSC as the burn option it is still stupid to use the PAL convention of bottom field first. I am aware of the problem so I do check to see if things are correct.

Thanks, I know about the project default settings, but there are times which I want to burn a PAL disc. The developers need to set the defaults correctly, and finally get rid or error 5 which is not fixed by the most recent patch. It would also be nice if they can fix the Virtualdub plug in problem. If I save a project with VD plugins, it gags and crashes when I try to restart it. VD has a documented method of saving and restoring filters which should be implementable.

I was not aware of the preset naming, so that will make things a wee bit easier.

johnebaker wrote on 3/20/2015, 1:35 PM

. . . . If I save a project with VD plugins, it gags and crashes when I try to restart it. VD has a documented method of saving and restoring filters which should be implementable. . . . .

MEP accepts Virtual Dub plugins, but it is not Virtual Dub, so does not have to use VD methods.

Some VD Plugins do not work with MEP because they are not compatible eg any plug-in that tries to alter aspect ratio, cropping, image sizing etc.

Others such as Histogram, Curves Sharpness and Colour correction and many others work perfectly well without problems.

Check if incompatible ones are causing the issue - unfortunately there is no definitive list of whch are / are not compatible.

For future use you would be better off looking at Pixelan who have worked with Magix to develop modern improved filters / plugins for MEP.

HTH

John