Frameserving to MEP 2013?

cpc000cpc wrote on 3/20/2013, 5:46 PM

Greetings,

I've regularly used and have often recommended frame serving to Magix video editors using the free VirtualDub http://www.virtualdub.org/. For those new to this it is a technique that was useful to overcome earlier limitations of video file size and also for doing some preprocessing using Vdub 'filters'. I use it now mostly for single frame animations -- frameserving rather than loading the MEP timeline with say three thousand 1920x10808 .bmp files!

My problem: The technique has worked with every version of MEP but it's not working with MEP 2013! :-( This is the error using the same latest version of Vdub, the same video file, and on the same computer which works with MEP 17 and MEP MX:

Any one able to get (or avoid) this error? Seems the Magix programs are set up the same. It's obviously not the immediate end of the world for me as I can if necessary frameserve to an older MEP and export a clip for MEP 2013. I'd rather do everything in one place if possible.

Regards,

Carl

Comments

johnebaker wrote on 3/20/2013, 7:04 PM

Hi Carl

This could be a Security permissions issue on the folder were the 'avi' file os located - easiest thing is to set the folder permissions so that Everyone has Full Control.

Also check that System and Administrators have full control as well.

John

cpc000cpc wrote on 3/21/2013, 12:59 AM

John,

Thanks for that. I've checked and done some re-sets to be sure of full control at 'Public' level down to the individual files. I remain mystified why MEP 17 & MX work as they should using the same source material from the very same folder, whether it's public or my own. I've even tried starting 2013 with the 'Run as administrator' option -- no luck.

I might try repeating the question on the other forum...

Regards,

Carl

Scenestealer wrote on 3/21/2013, 1:09 AM

Hi Carl

I was getting that exact same message with 2013 (not with MX) when I tried to drag and drop Xara X3d title presets from the media pool onto the timeline. I tried all that permissions stuff to no avail then decided to "reset MEP program defaults" and Presto, everything worked.......go figure??

Peter