Quick Question - Project Filesize Limitations

Madgix wrote on 9/1/2014, 4:34 AM

Is it unrealistic to expect Movie Edit Pro 2013 Plus to be capable of coping with a 63MB project file ?

I have one which takes about 5-10 minutes to load. The tracks eventually display but the visualisation in the preview window does not appear because the software crashes.

My crash log says --->

----------------------------------------------------------------------
MAGIX Movie Edit Pro 2013 Plus  01.09.2014  09:36
----------------------------------------------------------------------
CrashDump 20140901_093648_v12.0.4.2.dmp successfully written

CrashDump 20140901_093648_v12.0.4.2.dmp successfully written

Unknown Thread   (ThreadID: 00001868)
  eax=00000a2c  ebx=0018edb0  ecx=371a0020  edx=0018ed68
  esi=371a3004  edi=000005fd  ebp=3543ff0c  esp=3543fec0
  eip=5f5b2821  Flags=00010202

  5f5b2819   10 80 3d 8c 64 5c 5f 00
  5f5b2821 > 89 46 fc 74 0a dd d9 d9
  5f5b2829   e8 de e1 d9 1e eb 16 dc

Main Thread
  eax=00000000  ebx=00000000  ecx=00000000  edx=00000000
  esi=00000000  edi=00000000  ebp=00000000  esp=00000000
  eip=00000000  Flags=00000000

  fffffff8   ?? ?? ?? ?? ?? ?? ?? ??
  00000000 > ?? ?? ?? ?? ?? ?? ?? ??
  00000008   ?? ?? ?? ?? ?? ?? ?? ??

videodeluxe.exe 17.10.2013  08:16   687a8a53

Memory Allocation
Base:  1.096
PE:  512
Pages:  262.144

PI:  16.100.448
PI_TEMP_DATA: 50.208
SI:  23.719.336
SI_TEMP_DATA: 1.192.944
FSI:  44.180

Blocks:  23.194
Temporary: 42
BE:  1.032.000
PLE:  47.520.000
BE Pool:  27.916
PLE Pool:  0
wHdr/inst: 0
B.cache inproc: 0
B.cache outproc: 0(0)
B.cache mapped: 23.039.040(3)
V.cache outproc: 0(0)
V.cache mapped: 0(3)
Video:  1.036.840(1.036.840/0)
Bitmap:  0

Video thumbs: 0(0)
SI Display Cache: 4.158.336
PLE Display Cache: 1.064.600

Buffer:  0
Pointer:  0

Title:  0

My content is mostly lots of layers of animated still pngs.

Sometimes Magix MEP gets stuck and can't display an individual picture. Often a re-boot can fix this. Frequently it will show black or white backgrounds to transparent pngs that I am moving and rotating.

I don't know if these are widespread bugs/memory issues.

I don't know if I am asking too much of the software.

I don't know if the program's inability to load my current project is due to me having recently requested a particular picture to move in a manner that it can't display.

I have a Project File from yesterday that WILL load.

I am wondering whether I should chop that FULL project in half in order to reduce the filesize and, following that compromise,  would then be able to carry on - only losing this morning's efforts - I would, however, ideally like to NOT forfeit anything and it would be MUCH better to keep my single film in ONE file.

Maybe this year's version of the program will be better. My machine has 16GB of memory and a 64 Bit OS.

 

 

 

 

 

 

 

 

 

 

 

Comments

terrypin wrote on 9/1/2014, 8:54 AM

That's a staggeringly large MVP file!

How long is the video? How many tracks in use? If you experimentally cut it roughly into halves and delete the second, is that about 30 MB in size? Will that export? Taking how long? Or, if that fails, ditto with say a tenth of the project.

I'd be interested to see a (high res) screenshot of a typical section of timeline..

Terry, East Grinstead, UK 

Last changed by terrypin on 9/1/2014, 8:54 AM, changed a total of 1 times.

Terry, East Grinstead, UK. PC: i7 6700K, 4.0 GHz, 32GB with Win 10 pro. Used many earlier versions of MEPP, currently mainly MEPP 2016 & 2017 (Using scores of macro scripts to add functionality, tailored to these versions.)

Madgix wrote on 9/1/2014, 12:01 PM

Thank you for replying about the size of my MVP file. I never noticed any warnings in the Magix documentation about keeping these down. I have been progressing (over the last TWO YEARS (!!)) with a presentation that is likely to run to a total duration of 90 minutes. I thought that would be okay and I did really want to be able to scroll along the whole thing in a SINGLE project and - ultimately render 1 file from 1 file in an environment where I could see and access everything at once.

I did not imagine, by keeping everything in ONE file,  I was going to get LOCKED OUT of my Project.

I understand NOW that I need to cut it down into chunks - but to do that I need to be able to open it again.

I am sure the content is not corrupt. It loads, I can see the blocks in the tracks but then the program chokes and forces closure. I think it is falling over at the point where it should be gathering the images for the section that I am looking at. The film frame in the Preview window never gets populated - the program just says it has to close.

I don't want to lose my work. I wonder if I could send the Project File to Magix and they would cut it in half for me.

Someone at Amazon told me that the 2014 version uses "Control" files not mvps any longer. Perhaps there was some optimisation between the versions.

I wonder if I could wait a month or so for MEP 2015 to be released and if that would just have the POWER to get my Project open as it is.

It doesn't make sense that a program can write a file that will be too big for it to open. It would help if there was a coded mechanism to prevent that happening. I had NO IDEA of the danger I was in.

As an aside, in which I clutch at straws.....

After I saved my 61.53MB Project File this morning, I uninstalled the Chrome Browser and then reinstalled it - THEN I came back to Magix Movie Edit and THEN I had my first problem with the crashing.

Could the uninstallation and reinstallation of my browser have interfered with the .dll files that are needed by the Magix program ? Might something have been deleted ?

I wonder if reinstalling MEP 2013 would "Magix"ly solve my problem.

 

 

 

 

 

terrypin wrote on 9/1/2014, 12:20 PM

Presumably you have been taking automatic backups?

Have you tried loading a suitably old and therefore smaller one of those MV_ files?

Succesively older System Restores would also be worth trying.

You might also see what happens if you deliberately prevent MEP from accessing the bulk of those PNGs. Temporarily move them to another folder. Then 'Skip All' in response to the message you'll get - if it gets that far. Then progressively return them to the original locations.

 

--
Terry, East Grinstead, UK

 

Last changed by terrypin on 9/1/2014, 12:25 PM, changed a total of 3 times.

Terry, East Grinstead, UK. PC: i7 6700K, 4.0 GHz, 32GB with Win 10 pro. Used many earlier versions of MEPP, currently mainly MEPP 2016 & 2017 (Using scores of macro scripts to add functionality, tailored to these versions.)

johnebaker wrote on 9/1/2014, 1:41 PM

Hi

At 63 MB that is one huge project - how many png files are in it?

I have a project with 3400 images in it and it is only 900KB in size.

I suspect the crashes is because Windows is running out of resources to handle the number of png's in the project.

In this situation I think you may have to start again and break it down into much more manageable chunks.

John

 

Last changed by johnebaker on 9/1/2014, 1:41 PM, changed a total of 1 times.

VPX 16, Movie Studio 2025, and earlier versions 2015 and 2016, Music Maker Premium 2024.

PC - running Windows 11 23H2 Professional on Intel i7-8700K 3.2 GHz, 16GB RAM, RTX 2060 6GB 192-bit GDDR6, 1 x 1Tb Sabrent NVME SSD (OS and programs), 2 x 4TB (Data) internal HDD + 1TB internal SSD (Work disc), + 6 ext backup HDDs.

Laptop - Lenovo Legion 5i Phantom - running Windows 11 24H2 on Intel Core i7-10750H, 16GB DDR4-SDRAM, 512GB SSD, 43.9 cm screen Full HD 1920 x 1080, Intel UHD 630 iGPU and NVIDIA GeForce RTX 2060 (6GB GDDR6)

Sony FDR-AX53e Video camera, DJI Osmo Action 3 and Sony HDR-AS30V Sports cams.

Madgix wrote on 9/1/2014, 4:49 PM

Thank you, Terry, for the brilliant suggestion about moving my content and using the "Skip All" command. I really thought that that would work and get me back into the project so that I could delete all the material from the earliest sections of the presentation and reclaim the later animations I had added between last Wednesday and this morning.

The Project loaded faster than usual, as it didn't have 7363 media items to collect, but the program closed just as it has been doing all day.

Previously, I thought there was no data corruption with this latest "most complete" version of the Project - the 61.53MB file - but I may be wrong about that.

The version from last Wednesday that still works has a larger filesize of 63MB. It is shorter and has less content which maybe points to the possibility that nothing post-midweek  was saving properly. I just assumed that everything was fine. I spent several days with the program open all the time, saving to the same filename and not knowing anything was wrong.

It's a good thing that I closed MEP today and came back to find the loss at THIS STAGE. If I hadn't closed it to reinstall my browser I would have kept going and going and going and would have had far more to re-do when I finally did discover the problem.

I now have an 18MB Project File for the 8 minute section that I am currently creating. I now understand that that is still considered a big file - but hope that my up-to-60MB experiences can promise that I have some headroom.

I had suspected that the crashing was to do with an individual element such as one really big png file I had made, with lots of blank space, so that I could control the centre point of rotation.

I will have to test that first thing tomorrow in my cut down file and probably just "get over" my wish to have a 90 minute 99 track project file. It's just not going to be realistic in any version of the software, is it ?

I use a LOT of tracks with a LOT of graphical elements so suppose THAT is why my files are so large.

You might also see what happens if you deliberately prevent MEP from accessing the bulk of those PNGs. Temporarily move them to another folder. Then 'Skip All' in response to the message you'll get - if it gets that far. Then progressively return them to the original locations.

 

--
Terry, East Grinstead, UK

 

 

terrypin wrote on 9/2/2014, 3:18 AM

Glad to hear your making some progress anyway.

You didn't answer my question about automatic backups.

"I spent several days with the program open all the time, saving to the same filename and not knowing anything was wrong."

I'm amazed that you didn't get a single crash or lockup in that long period of editing. I'm lucky if I don't get several every day (in MEP 2014, but previous versions have been similar). Normally I allow MEP to restore the project that it assures me it was able to backup directly before the crash (a very welcome feature BTW). And I always take its advice to then re-save immediately with a new name, just in case. But if you've neither been

- getting any crashes anyway

- regularly saving yourself with new names

- regularly closing and re-starting MEP

- taking automatic backups and maintaining their 10-step roll-over carefully

then your predicament is hardly too surprising!

 

--
Terry, East Grinstead, UK

Last changed by terrypin on 9/2/2014, 3:19 AM, changed a total of 2 times.

Terry, East Grinstead, UK. PC: i7 6700K, 4.0 GHz, 32GB with Win 10 pro. Used many earlier versions of MEPP, currently mainly MEPP 2016 & 2017 (Using scores of macro scripts to add functionality, tailored to these versions.)

Madgix wrote on 9/2/2014, 7:59 AM

I *do* maintain automatic backups - but trying to restore from those is very much a last resort. I tried yesterday and it took 5 hours to restore and then the program closed in the same manner as it did with the 61.53MB MVP.

I don't like the "no promises" disclaimer than comes with the "Restore" feature. My Project is too big for me to manually check through it all.

I prefer to go back to older versions of the proper MVP.

I use cloud storage and that has versioning. That's how come I was able to test a 61.53MB MVP and a 61.51MB version of my most up-to-date filename.

When they didn't work I hopped back to the last good file - the 63MB one with a different filename.

I don't know why the 63MB file reduced in size after I had re-named it. I don't think I had deleted any material between the crossover - and then, when I got going I was just ADDING more media so I can't account for the drop from 63MB to 61ish - unless Magix performs some "tidying up" when you save with a fresh name.

Does it?

Perhaps, in future I will be able to monitor filesizes and make sure that whenever I add something their size INCREASES.

Perhaps EVERY save should be given a new name.

You said you were surprised I didn't get any lock ups or crashes. I haven't had those.

The program always has some trouble breaking the playhead bar so that it can be in two different positions - until you alter the view zoom level so it can correct itself. I never need to CLOSE the program because of that.
It's an issue that was in the MEP MX version too.

Generally, I would only close MEP 2013 when a new graphic won't display. This sometimes happens when I have brought in a new transparent png and have applied some motion to it. I try to scrub the action to add/test the keyframed motions - but I can't see anything or DO anything to an INVISIBLE ELEMENT so I am forced to save and leave the program.

When I return (after the 5-10 minute load) the picture is generally visible, scrubbable, animated and I can carry on.

Is the difference between 2013 Project Files and 2014 Control Files that 2013 makes its own copies of the media that you add ?

I came to Magix after using (a VERY old version of) Adobe Premiere Pro and had assumed that MEP also just POINTED to external files. I've noticed that MEP 2013 doesn't  update my graphics when I edit them so suppose it must be using its own captures prior to the final render.

I can't scrub through in Magix MEP 2013 the way I did in Premiere Pro 6, the pre-rendering doesn't work for me. Premiere used to make GIANT temporary films. Something of a mixed blessing - but I wonder if these features are available in 2014 or 2015 - giving reasons to upgrade.

New keyframing and being able to do simple things like choose your point of rotation would be very welcome.

 

 

 

 

 

terrypin wrote on 9/3/2014, 2:58 AM

 

I *do* maintain automatic backups - but trying to restore from those is very much a last resort. I tried yesterday and it took 5 hours to restore and then the program closed in the same manner as it did with the 61.53MB MVP.

That's incredible! So you have had to do something else for 5 hours every time you start an editing session with this project?

I don't like the "no promises" disclaimer than comes with the "Restore" feature. My Project is too big for me to manually check through it all.

Don't follow you there. You can methodically restore and revert until you possibly get a status (weeks or months ago perhaps) where MEP is behaving properly. While that would, of couse, still leave you with a lot of reworking to do, it would probably reveal the cause of the issue.

I prefer to go back to older versions of the proper MVP.

I use cloud storage and that has versioning. That's how come I was able to test a 61.53MB MVP and a 61.51MB version of my most up-to-date filename.

When they didn't work I hopped back to the last good file - the 63MB one with a different filename.

I don't know why the 63MB file reduced in size after I had re-named it. I don't think I had deleted any material between the crossover - and then, when I got going I was just ADDING more media so I can't account for the drop from 63MB to 61ish - unless Magix performs some "tidying up" when you save with a fresh name.

Does it?

Perhaps, in future I will be able to monitor filesizes and make sure that whenever I add something their size INCREASES.

Perhaps EVERY save should be given a new name.

I periodically add a numeric suffix, typically after an especially 'heavy/complex' session of editing.

You said you were surprised I didn't get any lock ups or crashes. I haven't had those.

The program always has some trouble breaking the playhead bar so that it can be in two different positions - until you alter the view zoom level so it can correct itself. I never need to CLOSE the program because of that.
It's an issue that was in the MEP MX version too.

Generally, I would only close MEP 2013 when a new graphic won't display. This sometimes happens when I have brought in a new transparent png and have applied some motion to it. I try to scrub the action to add/test the keyframed motions - but I can't see anything or DO anything to an INVISIBLE ELEMENT so I am forced to save and leave the program.

When I return (after the 5-10 minute load) the picture is generally visible, scrubbable, animated and I can carry on.

5 minutes? But didn't you say that even earlier (and therefore smaller/less complex) auto-backup files took 5 hours?

Is the difference between 2013 Project Files and 2014 Control Files that 2013 makes its own copies of the media that you add ?

As John EB said (in another thread you're still using about the same subject!), MEP (any version) does not include actual content in project files.

I came to Magix after using (a VERY old version of) Adobe Premiere Pro and had assumed that MEP also just POINTED to external files.

It does.

 

I've noticed that MEP 2013 doesn't  update my graphics when I edit them so suppose it must be using its own captures prior to the final render.

 

You may have fallen victim to an obscure bug I've reported over the last couple of years. This may conceivably be one possible contributor to your corrupted project. Here are a few links:

http://www.magix.info/uk/more-examples-of-the-non-existent-objects-bug.forum.1042919.html

http://www.magix.info/uk/mep-2013-and-other-false-memory-bug-remains.forum.1041384.html

http://www.magix.info/uk/mep2013-invisible-track-contents.forum.878638.html

http://www.magix.info/uk/mep-2013-invisible-object-another-example..forum.879548.html

I can't scrub through in Magix MEP 2013 the way I did in Premiere Pro 6, the pre-rendering doesn't work for me. Premiere used to make GIANT temporary films. Something of a mixed blessing - but I wonder if these features are available in 2014 or 2015 - giving reasons to upgrade.

New keyframing and being able to do simple things like choose your point of rotation would be very welcome.


2014 added Proxy Files, which has significantly improved my previewing experience.

--------------------

As Peter has said (in another of your threads on this subject I think!), the bottom line is plainly that your project has somehow become badly corrupted.

Could you make a tiny non-confidential project that is typical of this huge one and use File > Backup > Copy project and media into a folder, zip it up and upload it so that we can see what you mean and maybe try to reproduce it? I for one remain unclear about its structure and content.

 

--
Terry, East Grinstead, UK

Last changed by terrypin on 9/3/2014, 2:59 AM, changed a total of 2 times.

Terry, East Grinstead, UK. PC: i7 6700K, 4.0 GHz, 32GB with Win 10 pro. Used many earlier versions of MEPP, currently mainly MEPP 2016 & 2017 (Using scores of macro scripts to add functionality, tailored to these versions.)