Sudden stop encoding or exporting film using Movie Edit Pro 16 Plus.

arnoudje50 wrote on 10/5/2014, 5:22 AM

Encoding proces (or also when exporting film) stops suddenly at a certain point in the movie (wich is not a heavy or complex part) every time again. I tried a couple of things. I checked the settings, the range of the film and I even replaced the movie scene's (re-edited it), but after 18 mins of my movie (wich should have a length of 53 mins) the enocding proces stops like nothing happened. The exported movie is fine and playable untill 18mins. There it stops and the rest of the movie is being ignored by the programm... In the editing screens everything works fine... Does anyone know what I could try and do to fix this? I'm using MAGIX Movie Edit Pro 16 Plus on a computer that runs on Vista. I have made several movies and succeeded before. Never had a problem like this.

Comments

terrypin wrote on 10/5/2014, 9:23 AM

Hi,

One thing you could try is to load the project then open a new, empty movie via File > Manage movies

 

Then copy the original movie in its entirety to the new one and try the export or burn from there.

 

--
Terry, East Grinstead, UK

Last changed by terrypin on 10/5/2014, 9:23 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.)

johnebaker wrote on 10/5/2014, 12:42 PM

Hi

In addition to what Terry said - what is on the timeline at the exact time that the export suddenly stops - my guess would be a transition, a change of source material type eg a change of video, audio or image format.

I used to have problems with an earlier version where the audio, in this case music, on the timeline changed from mp3 to wav.  In the end I made sure all additional audio was the same format.

HTH

John

Last changed by johnebaker on 10/5/2014, 12:42 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.

Scenestealer wrote on 10/5/2014, 5:31 PM

Hi

Something else to try - make sure Smart Rendering is not activated in the export settings.

Ss

Last changed by Scenestealer on 10/5/2014, 5:31 PM, changed a total of 1 times.

System Specs: Intel 6th Gen i7 6700K 4Ghz O.C.4.6GHz, Asus Z170 Pro Gaming MoBo, 16GB DDR4 2133Mhz RAM, Samsung 850 EVO 512GB SSD system disc WD Black 4TB HDD Video Storage, Nvidia GTX1060 OC 6GB, Win10 Pro 2004, MEP2016, 2022 (V21.0.1.92) Premium and prior, VPX7, VPX12 (V18.0.1.85). Microsoft Surface Pro3 i5 4300U 1.9GHz Max 2.6Ghz, HDGraphics 4400, 4GB Ram 128GB SSD + 64GB Strontium Micro SD card, Win 10Pro 2004, MEP2015 Premium.

terrypin wrote on 10/6/2014, 9:08 AM

 

Hi

Something else to try - make sure Smart Rendering is not activated in the export settings.

Ss

Hi Peter,

I'm curious about that interesting suggestion. Can you amplify please? Is Smart Rendering iffy/buggy?

--
Terry, East Grinstead, UK

 

Last changed by terrypin on 10/6/2014, 9:08 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.)

johnebaker wrote on 10/6/2014, 12:59 PM

Hi Terry

A long while ago (2yrs+)  I reported a possible bug where there was a conflict between Hardware acceleration being turned on in the programs settings and using the Calculate video effects on GPU option in MEP - IIRC MX - using CUDA

With both turned on exporting would cause a crash.

John

 

Last changed by johnebaker on 10/6/2014, 1:00 PM, changed a total of 2 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.

Scenestealer wrote on 10/6/2014, 3:22 PM

Hi Terry

Disabling SR was the thing that worked for me when I had the same problem in MEP16 back in 2010. German forum members have advised similar action over the years too.

Below is Ralf from Support's advice back at the time.

The problem would be hard to reconstruct from here and the causes won't be easy to pinpoint. This might be something related to a specific problem in this particular project, especially if it always cuts out at the same position. You could play back the part of the file that was rendered and see whether you can connect that time makr to something specific in your project's time line, e.g. a problematic transition effect or something similar. Maybe eliminating that problem will help you work around the matter.

Here's something else that you could also try, as it might be related to the isseu:

Disable the hardware acceleration for MPEG video material in the program, as this can be problematic under certain circumstances. In order to do this, open the program and access the program settings (e.g. by pressing the "Y" key). Switch to the "Display options" tab and find the checkbox "Acceleration for high-resolution MPEG files". Make sure this box is not ticked. Confirm the settings by presing OK and try (smart)-rendering again.

If none of this helps, I can only recommend disabling the smart-rendering in the MPEG encoder settings when mixing down the project.

I hope this helps.
 

Cheers

Peter

Last changed by Scenestealer on 10/6/2014, 3:22 PM, changed a total of 1 times.

System Specs: Intel 6th Gen i7 6700K 4Ghz O.C.4.6GHz, Asus Z170 Pro Gaming MoBo, 16GB DDR4 2133Mhz RAM, Samsung 850 EVO 512GB SSD system disc WD Black 4TB HDD Video Storage, Nvidia GTX1060 OC 6GB, Win10 Pro 2004, MEP2016, 2022 (V21.0.1.92) Premium and prior, VPX7, VPX12 (V18.0.1.85). Microsoft Surface Pro3 i5 4300U 1.9GHz Max 2.6Ghz, HDGraphics 4400, 4GB Ram 128GB SSD + 64GB Strontium Micro SD card, Win 10Pro 2004, MEP2015 Premium.

terrypin wrote on 10/7/2014, 7:24 AM

Very odd.

1. I'm a bit puzzled re your comment about checking the range. When you do a full export, have you unchecked the box 'Only export selected range' , just in case there is a badly behaving range set somewhere?

2. To make fault isolation easier, create a tiny new project consisting of everything (in all tracks) say 5 seconds before and after the transition point.:
Select the whole original project then carefully deselect the wanted part by left clicking while pressing the Control key, then press the Delete key to remove the bulk. Move the 10 seconds or so of material to the start of the timeline, check there's nothing beyond it, and save the project with a new name. Working now with that should be easier. Start by exporting it and tell us what happens.

3. If the exported fie still excludes the second part, use File > Backup > Copy project and media into a folder, zip it up and upload it somewhere (I use Dropbox) so that we can see what you mean and maybe try to reproduce it. Naturally, ensure there's no confidential material included.

Last changed by terrypin on 10/13/2014, 3:32 PM, 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.)

terrypin wrote on 10/13/2014, 3:29 PM

Well done!  Pleased to hear you finally found what proved a pretty obscure problem!

Last changed by terrypin on 10/13/2014, 3:30 PM, 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.)