Movie Maker crashes everything when exporting to MOV

stinkweed007 wrote on 1/16/2019, 4:07 AM

Movie Edit Pro Plus 17.0.3.178 (UDP3)

Windows 10 Pro 64 1803 17134.523

Intel i7-2600 3.4Ghz

16GB RAM

Whenever I attempt to export to MOV format, the program seems to suck every bit of ram and resource from my computer rendering my computer completely useless and crashing any other program I have running such as Internet browser.. Yet performing the exact same export to MOV format from Movie Edit Pro 2013.. no issues.. on the same computer..

Can someone give me assistance as to what causes this?

 

Comments

johnebaker wrote on 1/16/2019, 12:24 PM

@stinkweed007

Do you have Quicktime installed or are you using one of the 'all in one codec packs' such as K-Lite?

Note if you have one of the 'all in one codec packs' installed these can mess up the correct codecs used by MEP causing issues with exporting.

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.

stinkweed007 wrote on 1/17/2019, 3:21 AM

Quicktime installed. I know what you mean with the CODEC packs.. but I have not used one of those since XP and never on this machine :)

and like I said. I have Magix Movie Edit Pro 2013 Plus also installed on this machine and it sails through Quicktime just like any other format. The only thing I can say is that after installing Movie Edit Pro Plus 17.x I had to enable 'legacy codec support' in quicktime before Movie Edit Pro Plus 17.x would recognize the Sorenson codec which was the go-to codec in 2013.

Scenestealer wrote on 1/17/2019, 4:28 AM

Yet performing the exact same export to MOV format from Movie Edit Pro 2013.. no issues.. on the same computer..

Maybe this is because MEP2013 is a 32bit program that can not access any more than 4GB of RAM leaving plenty for the other applications.

the program seems to suck every bit of ram and resource from my computer

Unusual. What is the nature of the material that you have on the timeline?

Peter

 

 

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.

stinkweed007 wrote on 1/17/2019, 5:13 AM

I would totally agree with the 64 vs 32 comment but even then, the new MEP shouldnt yank everything and crash other programs.. And right now as I am making this post I am rendering a full HD video to MOV with 2013 and Magix is only utilizing a steady 487.7 MB..

As far as material, I typically assemble clips which are either MP4 (exported from Powerpoint or a video camera) or MOV exported from 3DS MAX. Then WAVs from MMM.. No change in my material sources from that which I use in 2013.

stinkweed007 wrote on 1/29/2019, 8:58 AM

so nobody has any recommendations or fixes?..

emmrecs wrote on 1/29/2019, 9:12 AM

@stinkweed007

so nobody has any recommendations or fixes?..

I rather suspect that is the case, unfortunately.

I suppose one inevitable question is: why are you exporting to .mov format? What happens if you export to, say, mp4, which is a much more "common" format today?

Jeff

Win 11 Pro 64 bit, Intel i7 14700, 32 GB RAM, NVidia RTX 4060 and Intel UHD770 Graphics, Audient EVO 16 audio interface, VPX, MEP, Music Maker, Vegas Pro, PhotoStory Deluxe, Xara 3D Maker 7, Samplitude Pro X7 Suite, Reaper, Adobe Audition CC, 2 x Canon HG10 cameras, 1 x Canon EOS 600D, Akaso EK7000 Pro Action Cam

stinkweed007 wrote on 1/29/2019, 9:31 AM

I export to MOV for quality reasons. I have not seen (or just maybe dont know the most efficient settings) for any other format when I am looking for a crisp result in YouTube and Vimeo.. I'm a little frustrated because the stuff works perfectly in Movie 2103.. and I want to use the new options in the newer version.. and I don't want to upgrade to the version that just came out (only months after the one that is messing with me now) unless I know that the stuff works..

johnebaker wrote on 1/29/2019, 12:43 PM

@stinkweed007

Hi

. . . . I am looking for a crisp result in YouTube and Vimeo . . .

The YT preferred settings and file container format are here and Vimeo here.

Do note that the viewed quality and resolution depends on the viewers Internet connection speeds, both sites will re-encode your video into various resolutions to meet the viewers need for smooth playback, this can be as low as 240p and you have no control over this.

HTH

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.

stinkweed007 wrote on 1/29/2019, 4:02 PM

I understand the user resolution thing..

and as far as the preferred resolutions accepted by YT.. I have been uploading MOV in the sorrenson codec from movie 2013 getting absolutely beautiful results.. and that is not even listed there..

emmrecs wrote on 1/30/2019, 3:47 AM

@stinkweed007

I have been uploading MOV in the sorrenson codec

Could that be the reason for your problems in the later version of MEP (I assume you are wanting to use this codec still)? Generally speaking, the use of any "non-Magix" codec is unnecessary and has been known to cause problems!

Jeff

Win 11 Pro 64 bit, Intel i7 14700, 32 GB RAM, NVidia RTX 4060 and Intel UHD770 Graphics, Audient EVO 16 audio interface, VPX, MEP, Music Maker, Vegas Pro, PhotoStory Deluxe, Xara 3D Maker 7, Samplitude Pro X7 Suite, Reaper, Adobe Audition CC, 2 x Canon HG10 cameras, 1 x Canon EOS 600D, Akaso EK7000 Pro Action Cam

johnebaker wrote on 1/30/2019, 4:27 AM

@stinkweed007

Hi

. . . . MOV in the sorrenson codec . . . .

The Sorenson codec is an old, ~ 20 yrs, codec that has been superseded by the 'industry standard' h.264 which YT and Vimeo will be re-encoding your uploaded video to.

I recommend that you encode your video using the settings recommended by YT and/or Vimeo - while you may see 'absolutely beautiful results' on your computer, other viewers will see the video differently depending on their Internet connection speed as I have said previously.

John EB

 

 

Last changed by johnebaker on 1/30/2019, 4:28 AM, 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.