Odd 2016/MEPP compatibility puzzle

terrypin wrote on 6/29/2017, 10:44 AM

I started a small project in MEP 2016 P last night. To check a forum user's query, which I suspected was about MEPP behaviour, I opened it in that this morning. Made a trivial change, lengthening an image duration etc. Closed MEPP and opened it to continue my work in MEP 2016. Gave me an error message "A memory allocation request failed...".

Went back to MEPP and tried saving it as MVD. When I imported that in MEP 2016 I got this:

Also tried making backup of project and media in MEPP, but still got same message about memory on attempting MEP 2016 import .

I tried a completely fresh project in MEP 2016 (a single JPG), saved it, opened it in MEPP, reduced length, saved. But that opened OK in MEP 2016.

Some weird project corruption that 2016 rejects but MEPP accepts?

Terry, East Grinstead, UK

 

Comments

johnebaker wrote on 6/29/2017, 11:58 AM

Hi Terry

Just tried it here following your steps - no issue with opening the MEPP project or importing MVD into MEP2016.

MEPP was patched to latest 16.0.4.102 yesterday.

John EB

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.

terrypin wrote on 6/29/2017, 2:28 PM

Hi John,

That was in MEP 2016?

If you get time, could you try the actual project please? Here's the 314 MB backup.

https://www.dropbox.com/s/5tlxgftsqlrs7p0/USA2016-Day01.zip?dl=0

Unzip and open USA2016-Day01-11th-2.MVP in MEP 2016.

Opens fine in MEPP 16.0.4.102. But here in MEP 2016 I get that memory error. Hope it's not a h/w issue.

Terry, East Grinstead, UK

 

Last changed by terrypin on 6/29/2017, 2:29 PM, 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.)

johnebaker wrote on 6/29/2017, 4:38 PM

Hi Terry

I get the same error message when opening the project in MEP 2016.

After some elimination, the issue is caused by the Taxi to Ibis title, save the project without that title in MEPP, opens in MEP 2016 fine.

Replacing the dodgy title with a new title in MMMP in the original project does not help - it still crashes in MEP 2016. This leads me to conclude that the project is corrupted.

HTH

John EB

Last changed by johnebaker on 6/29/2017, 4:38 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.

terrypin wrote on 6/29/2017, 4:52 PM

Hi John,

Well done, many thanks!

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.)