Media Encoder Crashing my Mac whilst creating proxies

@Dakin30017592v3kg do you have Apple's Pro Video Formats installed? I'm trying to think of why some people with the exact same computer specs have continued to have this issue and others don't, and some people probably don't have this installed.

It might not affect anything in Premiere or AME, but I was updating it the other day and saw that it adds support for AVC-Intra 50 / 100 / 200, so could be worth a shot if you haven't installed already: https://support.apple.com/kb/DL2100

Hi, I'm circling back to this thread to provide an update. @lazylizzie and @Michael Grenadier thanks again for your responses. FCP works — I am now able to create large batches of proxies using the trial version of FCP. The workflow still isn't ideal because I have to remake the folders in FCP and move the proxy folders manually, since FCP doesn't seem to allow custom destinations for the proxies. My FCP trial expires in 1 month and I'm genuinely considering switching for future projects because of this.

Hi @Dakin30017592v3kg , it's sounds like you're having the exact same issue with the Sony files that I thought Adobe had already solved, so apart from trying the Beta version of Premiere/AME, I'm not sure what else you could do besides using a different program to generate the proxies.

I have heard people say their workaround was to create the proxies in Davinci Resolve, and the free version could do this fine. If you're not familiar then you can easily do the proxies by getting all your files in a Premiere timeline, exporting an XML of that timeline, then in Davinci right click the "Master" bin window on the Edit page and go Import > XML, and in the options on import the main thing is to have have it set the project settings and import the media, but having the use sizing checked may not be good if the clips were scaled in the Premiere timeline (Davinci should be default set to scale image to fit, so if you don't use scaling info then it should default scaling the clips to fill the frame). Then open that imported timeline and go to the Deliver page where you need to render "individual clips" and select ProRes proxy and 1280x720 (or whatever settings you want) then under "file" make sure it's "source name" but don't worry about unique names, and then set to export in a new folder called "Proxies" or anything different from the source folder. And above the timeline it should be set to render the entire timeline already, but if not make sure that's set. Then add it to the render queue and render.

If it manages to get past the 50 clip limit, then select all the clips in Finder and right click > rename > change to "add text" and "after name" and add _Proxy (in case you weren't aware of the built in renamer).

And I believe Adobe has fixed the issue of attaching stereo proxies to multichannel media, but I haven't tried myself, so might be worth making sure that's possible before rendering 500 clips!

Looks like there's a free trial of FCPX which may include compressor...  worth some digging

https://www.apple.com/final-cut-pro/trial/

and my workaround when this occured was to unlink the camera original and relink to the "proxies" and then when I finished editing, unlink the proxies and relink to the camera origina.  

Revmilo, I don't think this is the case anymore.  A few years ago, this was true that you could generate proxies from sony footage with 8 channels of audio but no matter what you did, the proxies would not attach to the camera original in Premiere, but lately, it does seem like you can generate proxies from premiere via AME without issues...   Working on a complex 4k documentary mostly shot on sony cameras and proxies (once we got over the color space issue) were generated and attached without issues.  

I understand your reluctance to waste the $50 however it's a very useful program and does a great job deinterlacing and upscaling...  If you want to send me a sample camera original file, I'll make a proxy using compressor that you can test...  The fact is that apple software often works better on macs than other companies software... wonder why?    Didn't mean to include my contact info in my previous reply but google or adobe has changed something as I replied from my phone directly from the post rather than going to the adobe forum to reply...    And not sure if this is actually adobe's fault or Sony's...  Sony has a history of changing things under the hood of their camera original files which cause serious problems years ago...  Took me a couple of long, painful days figuring out that adobe spanned files could no longer be handled by finalcutpro7...  Just crashed fcp...  Not that it's about assigning blame... or is it?   And wondering whether shutterencoder might work to make your proxies

https://www.shutterencoder.com/en/

It's free (although contributions are appreciated) and probably can do this for you.  Certainly worth a shot.  

Post back if you have any questions, or feel free to email me directly.

Depending on the rushes - you will need to have exactly the same amount of audio tracks as the master clip for the Proxies to work in Pr. Therefore Me is the only work for things like Sony FX6 footage with 4 or 8 tracks. I think its the magic 50 - I have managed to encode proxies 48 at a time and it doesn't crash. Having said that - i bit the bullet and got a MacStudio which is fine but ironically now doesn't really need the proxies...what version of Pr are you on? Tried updating? Also, i think the fan is a red herring....

If you are still super stuck - you might need to encode proxies - via Me but not as Proxies - basically compressed versions of OG footage - cut with those - then relink to the master clips at the end... massive ball ache as audio stuff could be a problem - but worth a test?...or roll back to an earlier version of Pr for proxies - then open latest version to cut. There are lots of roll back - forward web based tools to help you open new Pr projects in old Pr versions...good luck!

http://joshcluderay.com/downgrade-premiere-project-converter/

I don't have Apple Compressor, and it looks like it costs $50. I'll consider buying it, but I'd like to exhaust other options before doing so. If I spend the $50 on Compressor, and if it works, I may just use FCP for my next project... I appreciate any other suggestions in the meantime.