Comments

Markus73 wrote on 1/9/2016, 1:56 PM

processor Pentium R dual core T4300, 2.1 GHz 64 bit

This ist much too slow for editing HD videos. See minimum system requirements!

Regards,

Markus

 

Last changed by Markus73 on 1/9/2016, 1:56 PM, changed a total of 1 times.

Intel Core i5-8400, MSI H310M Pro-VD, 8 GB RAM, Win 10 Home 21H1

Video deluxe Premium, Video ProX, Web Designer Premium, Foto & Grafik Designer, Xara Designer ProX

Amos wrote on 1/10/2016, 5:33 AM

Test reply

Amos wrote on 1/10/2016, 5:58 AM

Thanks for your reply which helps. I would like to re-frame my question.

I have been using MEP on the above computer for 3 years and as I have progressed onto higher definition MEP playback has often become jerky... But not always jerky. I have always produced the output.

I do not want to change computer as it is mobile and in perfect working order.

So my question is at what point does MEP Start to struggle on the above PC size. IE at what definition level eg 720 1080 etc?

Also are there any settings which I can check to optimise? example is MEP definitely working at 64 bit or is it defaulting to 32 bit? or any other playback settings which can be tweaked to enhance playback?

I am sportsman first, cameraman second and editor, third. So hopefully not too in-depth reply would be appreciated. Does anybody have a view on this?

Thanks...

 

emmrecs wrote on 1/10/2016, 7:09 AM

Amos, are you using proxy files to view/edit your AVCHD footage?  I have a considerably faster CPU (Intel Core 2 Quad @ 3GHz) and I need to use proxy (=lower resolution) files for editing of my mt2s files.

When creating a new project you should have the option on the initial screen to "Create proxy files" for the video as you import it.  Creation of these files can take some time- you need to be patient - but once completed you should be able to edit/view your footage without the jerkiness.  When you have finished the editing and want to export the final version MEP will use the original (high definition) files, not the lower resolution proxies, so your output can be as "good" as possible.

Jeff

Last changed by emmrecs on 1/10/2016, 7:09 AM, changed a total of 1 times.

Win 11 Pro 64 bit, Intel i7 14700, 32 GB RAM, NVidia RTX 4060 and Intel UHD770 Graphics, MOTU 8-Pre f/w audio interface, VPX, MEP, Music Maker, Vegas Pro, PhotoStory Deluxe, Photo Manager Deluxe, Xara 3D Maker 7, Samplitude Pro X7 Suite, Reaper, Adobe Audition 3, CS6 and CC, 2 x Canon HG10 cameras, 1 x Canon EOS 600D, Akaso EK7000 Pro Action Cam

Amos wrote on 1/10/2016, 7:56 AM

Ah Proxy Files. I haven't come across them, or just didn't understand. That makes sense. So they're a smaller graphical representation which uses less ?? RAM/Processing space so you get smoother playback during editing, then the proper file gets used in the final rendering? So there's a time delay but at least I keep the high def.

Great solution

By the way I've just converted one of the .m2ts files to an MP4 720 HD file and it plays on the editing screen without stuttering. So the processor I'm using should handle the proxy file size I guess?. Life in the old PC yet!

Thanks for the reply