• Global community
    • Language:
      • Deutsch
      • English
      • Español
      • Français
      • Português
  • 日本語コミュニティ
    Dedicated community for Japanese speakers
  • 한국 커뮤니티
    Dedicated community for Korean speakers

Media Encoder Crashing my Mac whilst creating proxies

Community Beginner ,
Jul 13, 2022 Jul 13, 2022

Copy link to clipboard

Copied

I am currently in the process of creating proxies for a doco using Premiere's create proxies workflow and once in media encoder it will get about 30 or so clips in before it compeltely crashes my entire computer.

Step by Step: 
- I import MXF footage from FX6
- Select all the footage in Card 1 and 'create proxies' 
- I choose Quicktime ProRes (high bitrate) and begin proxy process
- It opens up Media encoder and begins creating proxies without issue and will randomly drop out no matter which proxy settings I choose

I have used this workflow multiple times for other cameras and never had an issue. Does anyone know if this is an update issue? an MXF issue? Or my computer? How do I fix this? 

Specs: 
iMac Pro (2017)
Processor: 3.2 GHz 8-Core INtel Xeon W
Memory: 32 GB 2666 MHz DDR4
Graphics Radeon Pro Vega 56 8 GG

Media Encoder v22.5
Premiere Pro v22.5

TOPICS
Crash , Editing , Error or problem , Export

Views

1.4K

Likes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Adobe Employee ,
Jul 13, 2022 Jul 13, 2022

Copy link to clipboard

Copied

Hey matiasb75700424,

 

Sorry about the issue. Do you also get this issue while creating h.264 proxies? Do you also see this issue while creating proxies for other media types? Can you share your source file properties (Project Panel > Right-click on media > Properties)? Let us know. We're here to help.

 

Regards,

Ishan

Likes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Community Beginner ,
Jul 13, 2022 Jul 13, 2022

Copy link to clipboard

Copied

Hi Ishan, 

I recently completed another project using the exact same workflow using C300 mk2 footage and had absolutely no issues. The only things that has changed this time is that I have updated both Premiere and Media Encoder, and the different camera / file types. 

It's very strange because if I do small batches of about 10 clips at a time, it's absolutely fine, it's when I set off an entire card or 20+ clips to media encoder that it without fail will crash my computer at some point during the queue.

I have also tested the clips that it crashes on to see if there are specific clips crashing it, but it seems like they're fine also. When I set them to proxy in small batches they proxy completely fine. 

I haven't had a chance to test if it also happens with h.264 proxies yet as i'd need to set off a large batch and wait a while to see if it happens and I'm trying to get through the ProRes proxies atm. The small batches is only a temporary fix however as I've got about 82 hours of footage to get through! 

I've tried creating the proxies in other programs and attaching them but because they're not 16x9 aspect ratio when I create 1920x1080 proxies they don't match. 

Attached below is the properties panel of one of the clips, all clips are all the same.

Screen Shot 2022-07-14 at 8.04.11 am.png
And just for reference when I create the proxies in another program and bring them in here's what they look like because they don't match the aspect ratio:

Screen Shot 2022-07-12 at 3.04.07 pm.pngScreen Shot 2022-07-12 at 3.04.16 pm.png

Thanks for helping out, let me know if you have any other questions Ishan.


Likes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Community Beginner ,
Jul 13, 2022 Jul 13, 2022

Copy link to clipboard

Copied

I should also mention that I thought this might be a problem with 'productions' so I tried it in a normal Premiere project outside of the production and still had the exact same problem.

I have also cleared my media cache on both programs just incase, but also no luck. 

Likes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Adobe Employee ,
Jul 28, 2022 Jul 28, 2022

Copy link to clipboard

Copied

Thanks for sharing the info. For testing purposes, could you roll back to 22.4 and let us know if you still see the issue? Here's how: https://helpx.adobe.com/in/download-install/using/install-previous-version.html

Likes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
New Here ,
Dec 06, 2022 Dec 06, 2022

Copy link to clipboard

Copied

Hi,

 

Has this issue been resolved because I am having the same problem and it is damn infuriating for a project with 1000s of clips? The remote support has been not helpful at all--looked at permissions, reinstalled, launched AME from terminal etc.

 

I am on a iMac 2019 with 24 GB RAM so the specs aren't an issue. And yes the AME, Premiere Pro, and the OS all are updated. I am thinking of stopping my subscription and shifting to Resolve if this doesn't get sorted! Any suggestions?

 

 

Likes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Community Expert ,
Dec 06, 2022 Dec 06, 2022

Copy link to clipboard

Copied

What are your source properties? Are they mxf files shot on a sony camera?

Likes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
New Here ,
Dec 06, 2022 Dec 06, 2022

Copy link to clipboard

Copied

Yes, XAVC-I footage in MXF, shot on Sony FX6. It is on an external HDD. Tried different hard drives, clearing cache. I have the crash dump files but not allowed to upload them here. I have a case ticket that's been open for a few days and 3 remote attempts at fixing this with no solution in sight...

Likes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Community Expert ,
Dec 06, 2022 Dec 06, 2022

Copy link to clipboard

Copied

Have you tried changing the color space to rec 709?

Likes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
New Here ,
Dec 06, 2022 Dec 06, 2022

Copy link to clipboard

Copied

No I haven't done that but not sure why it would make the queue crash randomly. It happens after 30 or so mins of transcoding. The footage is both in log and rec709 space depending on the lighting conditions...Appreciate any suggestions!

Likes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Community Expert ,
Dec 06, 2022 Dec 06, 2022

Copy link to clipboard

Copied

LATEST
well I was having a somewhat similar problem and going in to premiere and
selecting the clips and right click and choose modify: interpret and reset
the color space for log clips to rec709. I had a few clips that changing
the color space didn't help and I changed the extension from .mxf to .mpg
(thanks Ann) and that did the trick...

--
Michael Grenadier
917-362-3396
*www.michaelgrenadier.com <>*
mgrenadier@gmail.com

Likes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Community Expert ,
Jul 13, 2022 Jul 13, 2022

Copy link to clipboard

Copied

Am I correct that you upload the card contents to a local computer drive, and are accessing the file on disc from there?

 

Neil

Likes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Community Beginner ,
Jul 13, 2022 Jul 13, 2022

Copy link to clipboard

Copied

Hi Neil, 

The footage is located on a Lacie Rugged 5tb USB-C drive, which is the main drive I am editing off as well. 

So I have moved all of the content from the cards onto the drive, set it out like this: 
Day01 > Card01 > A001
DAy02 > Card02 > A002 etc.

I then create the proxies within the card folders using the following settings: 

Screen Shot 2022-07-14 at 7.52.55 am.png

 Let me know if you have any other questions. Thanks Neil



Likes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
New Here ,
Oct 04, 2022 Oct 04, 2022

Copy link to clipboard

Copied

I'm having the exact same issue with native Pro Res footage.  My computer powers itself off and then re-boots itself. Very frustrating.

Likes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Adobe Employee ,
Oct 04, 2022 Oct 04, 2022

Copy link to clipboard

Copied

Hi christopher,

Sorry! Computers typically shut down on their own if they get too hot. Kindly check out the cooling of your case. Is it overheating? I believe you can download cooling info apps for free. Can you check?

 

Thanks,
Kevin

Likes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Community Expert ,
Oct 04, 2022 Oct 04, 2022

Copy link to clipboard

Copied

had a lot of problems generating proxy files from mxf files recently on a very large doc project.  Proxy creation would intermittently fail in media encoder, and proxies would not stay attached.  We also saw intermittent flashing when playing both camera original and proxies . What solved the problem is resetting the color space to rec709.  Certainly worth a shot...  select a clip in the project and right click and choose modify: interpret and go down to color management and if the color space is anything other than rec709 turn on color space override and set it to rec709.    And what's good is that changing the color space of the camera original also fixed preexisting proxies...  

Likes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Explorer ,
Oct 13, 2022 Oct 13, 2022

Copy link to clipboard

Copied

@matiasb75700424  did you find a solution?

 

I'm have a terrible time trying to proxy FX6 footage that's AVCI 100 in an MXF container, as AME constantly freezes after about 50 clips are proxied (this project has 500 clips) and this problem has occured on every project with this kind of footage. 

 

Running AME v 22.6.1 on MacOS 12.6 and this issue has occured on multiple Mac Studios with M1 Max chips as well as a 2020 iMac, and only with the that footage, even other Sony footage has been fine.

 

I tried the suggestion of changing the clips to Rec 709 colour space before proxying but it made no difference and continued to crash after converting 50 or so proxies.

 

If anyone has a work around we are desperate to know as a lot of people use this codec!

Likes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Community Expert ,
Oct 13, 2022 Oct 13, 2022

Copy link to clipboard

Copied

well maybe just do 50 clips at a time?  don't mean to be snarky, but it might be a reasonable workaround.  

 

Are you "creating proxies" from within Premiere which sends them to AME?  If so, maybe just bring the camera original into AME directly and transcode to your desired format and settings for proxies and then attach them back in Premiere.

 

And where are you saving the proxies?  I always save them to a folder next to the original media as that avoids any issue with duplicate file names...  but maybe try saving them to a common folder for the project to see if that makes any difference.

 

And when you successfully create the 50 or so proxies before AME freezes, are the proxies successfully attached to the camera original within Premiere?   

Likes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Explorer ,
Oct 13, 2022 Oct 13, 2022

Copy link to clipboard

Copied

As it's random as to when it freezes then only doing a small amount at a time isn't really a viable option as it still randomly freezes, but when doing a batch amount it usually gets through close to 50 clips depending on the size. And the issue is the amount of time spent on any project with this footage just to proxy is not okay, as it's not just one isolated project where this issue is occuring.

 

But the proxies connect and work completely fine after AME crashes except for the last two it created. It also crashes Premiere sometimes and if it isn't saved then for some reason it's making me connect each proxy individually and not batch automatically connecting the others as what is usual Premiere behaviour in all other projects.

 

I haven't tested if transcoding them directly in AME crashes it, but I've never found any settings in AME that allows a direct transcode with Sony clips that have 8-channel audio (which most Sony cams seem to have these days) and then attaches to the clips as proxies in Premiere without any issues (as in when trying to attach the proxy it pops up with an error about the audio channels or something). If you know what settings in AME allow a direct transcode to create compatible proxies with 8-channel audio then please post the details/link to an article as I've tried researching without success. 

Likes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Community Expert ,
Oct 13, 2022 Oct 13, 2022

Copy link to clipboard

Copied

I had exactly this problem a number of years ago with sony clips with 8 channels of audio and was totally unable to create proxies that would link to the camera original.  Seemed clear to me that there was something in the way Sony was formatting those 8 channels of audio that would not play nice with Premiere.  But I did work around the issue by transcoding to prores proxy files and then making the camera original offline and relinking to the prores proxy files and when we locked picture, doing the dance in reverse to relink to the camera original.   If you're willing to use this workflow, I'd suggest you test a few files before diving in to the deep end of the pool.  In my case, I didn't need any of the audio tracks except the first 2 (the rest were empty).  I don't remember exactly how I setup the transcode but don't think it was rocket science (sorry for the mixed metaphors).  

Likes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Explorer ,
Oct 13, 2022 Oct 13, 2022

Copy link to clipboard

Copied

Unfortunately that would only work if we were transcoding to the same resolution, but we need small proxies to run multiple computers from a server, so you'd have to transcode and replace and then proxy those transcodes. Again, the time to do that just isn't viable for us as it isn't just a one off situation with a few clips that have issues, is hundreds of clips per project across many projects.

Likes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Community Expert ,
Oct 13, 2022 Oct 13, 2022

Copy link to clipboard

Copied

just tried taking a short 4k clip and dropping it into media encoder and applying a prores proxy preset to it with 1080 pixel dimensions and then brought the 4k clip into premiere and attached the 1080 proxy clip to it and edited the clip into a 4k timeline switching proxy on and off seems to be working fine without any issues because of the smaller pixel dimensions...  or am I missing something?  wouldn't be the first time.

Likes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Explorer ,
Oct 13, 2022 Oct 13, 2022

Copy link to clipboard

Copied

Might have our wires crossed, but I understood your work around was to transcode the Sony footage, offline the orignal MXF files, and then link to your transcoded files. If that's correct then the process takes too long as we want to export drafts using the orignal files and not small proxy files.

 

Basically we need to be able to create proxies from these files without it crashing AME and still be able to switch between the proxies and orignal MXF files as with all other footage, so without having to go through a lengthy process.

Likes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Community Expert ,
Oct 13, 2022 Oct 13, 2022

Copy link to clipboard

Copied

that was my original thought, but if the problem is caused by creating the proxy in premiere which then queues them in Media Encoder, just loading the camera original into Media Encoder and then applying the custom preset with the correct codec and pixel dimensions might not crash Media Encoder and then you can just attach the proxy files back in Premiere...    Maybe worth a shot leaving a batch larger than 50 files cooking overnight...   And wondering if there could be some issue with your network...  assuming you're working in some sort of shared media environment.     Might be worth a test working with local drives...  Just throwing some ideas out...  No one else is piping up with any suggestions...   When I have this sort of issue, I keep banging my head against the wall til I figure out a solution or work-around...  

Likes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Explorer ,
Oct 13, 2022 Oct 13, 2022

Copy link to clipboard

Copied

As I said earlier, I've never been able to attach proxies of transcodes in AME without creating them in Premiere first when they're 8-channel audio Sony clips. I always get errors when trying to attach them no matter how I configure the encoding preset.

Likes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines