Skip to content

Sir Ros

My feedback

2 results found

  1. 8 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    5 comments  ·  Premiere Pro » Export  ·  Flag idea as inappropriate…  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    An error occurred while saving the comment
    Sir Ros commented  · 

    I indeed tried to launch in Intel mode Antoine, unfortunately it didn't make a difference. When exporting with software-only settings Premiere simply just crashes after a couple of minutes and Media Encoder stops encoding. The encode cannot be resumed. If I tell Media Encoder to use Metal (GPU Encoding) and run in Intel mode, I get the same issues I get with the native Apple Silicon code regardless of whether I'm using CPU or GPU encoding.

    Sir Ros supported this idea  · 
    An error occurred while saving the comment
    Sir Ros commented  · 

    This isn't just an issue with interlaced broadcast exports. I'm literally having what sounds like the exact same issue on progressive scan ProRes files (regardless of which "flavor" of ProRes I choose at that,) when encoding from source material stored on a NAS. It does not matter if I render back to the NAS, directly to my M1 iMac's internal storage, or to a directly attached HDD/SSD connected to my iMac. If the source material is stored on a NAS, I will have a file that yield's everything that you're describing ranging from green or pink "macroblocks" to repeated/skipped frames, to white or black screens where video should be. Even worse, these occur somewhat randomly, so the first encode attempt might be fine in one spot but have a glitch in another, while the second encode attempt will have a glitch in the spot that was previously fine, and look great where the first encode glitched. I have tried duplicating this issue on Intel–based Macs running macOS Big Sur with the same point upgrades as the Apple Silicon Macs, ranging from a 2013 Mac Pro, to 2014 and 2018 Mac Minis, to various MacBook Pros from 2014-2017, and the same glitches do not occur on Intel–based Macs, nor do they occur on Windows PCs running Intel chips; this issue only occurs on Macs running Apple Silicon. I have tried using both Adobe CC 2021 and Adobe CC 2022, running both the Intel version of Premiere Pro through Rosetta 2 and the "Universal" version of Premiere Pro that runs natively on Apple Silicon, and I run into the same issue regardless of which version of Premiere Pro is in use. I have tried using CPU encoding only, using GPU (Metal) encoding, only encoding via Premiere Pro without Adobe Media Encoder, and exporting to Adobe Media Encoder to handle the encoding process, and the result is the same regardless. Normally I'm wired in over a 10GB ethernet connection attached via Thunderbolt, but I've also tried a standard gigabit ethernet connection and even WiFi; nothing makes a difference, the result on Apple Silicon Macs is always the same. This is a serious issue that has rendered all Macs that I've worked with that utilize M1 chips unsuitable for encoding.

  2. 23 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    2 comments  ·  Premiere Pro » Playback  ·  Flag idea as inappropriate…  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    An error occurred while saving the comment
    Sir Ros commented  · 

    This is a serious issue that needs to be addressed swiftly, at present I and my colleagues are working largely on M1 iMacs and it is simply impossible to encode a video from them when the source material is on a NAS and receive a usable output. We've had to have editors who are normally on Intel based Macs and Windows PCs move around whenever someone needs to actually encode a video because of this.

    I would be curious to know if your source material is typically stored on a NAS, and if so, does this issue only occur when working with source material that is on a NAS and isn't stored locally? Likewise, do you run into this issue running both the native Apple Silicon versions of Adobe's apps, or do you run into them when running Adobe under Rosetta 2 as well? In my experience the glitches only occur when my source material is on a NAS rather than some form of directly attached storage, and the glitches occur whether or not I'm using the native Apple Silicon version of Adobe's apps or running them via Rosetta 2.

    Sir Ros supported this idea  · 

Feedback and Knowledge Base