Skip to main content
kevind92386150
Participant
December 14, 2021
Question

ARRIRAW files play back choppy, despite working fine in other apps

  • December 14, 2021
  • 1 reply
  • 680 views

I'm not sure if this is a common issue everyone has, or if there's a setting that I'm missing, but whenever I try to play back RAW footage from an ARRI camera (specifically the Alexa Mini and the Alexa Mini LF) in Premiere it always plays back choppy.  The same files play fine in other programs, like Davinci Resolve or the ARRIRAW Converter, but for some reason Premiere is always dropping frames.  I've spoken to editor friends of mine and they have the same issues, so it's not just me (but that doesn't rule out that we're just all doing something wrong I suppose).  I know I can just make proxies, which I do, but it's strange that the other programs have no issues with the files.

 

I have the issues on both my Windows desktop and brand new top-of-the-line MacBook Pro.  Here are my specs:

 

OS: Windows 10 Pro 64-bit

CPU: AMD Ryzen 3950X

GPU: NVIDIA 2080 TI

RAM: 128GB Corsair Vengeance LPX (4x32GB) DDR4 3200MHz

The issue happens even when playing files from an internal SSD (less-than-a-third-full 1TB M.2 NVMe PCIe Gen4) that's normally capable of reading over 4000MB/s, so I doubt it's an SSD bandwidth issue.

 

MacBook Pro 2021 16":

OS: macOS 12.0.1 (12.1 just came out today so I haven't updated yet)

CPU: M1 Max 10-Core

GPU: 32-Core (I'm not sure this has a name)

RAM: 64GB

The issue happens even when playing back from the internal SSD (normally capable of over 5000MB/s) using the latest version of Premiere for Apple Silicon, as well as the Intel/Rosetta version.

 

So does everyone else have these issues as well?  Or is there a fix/something I'm doing wrong?  Again, I'm asking if there's a way to not use Proxies, but just playback the original RAW files without dropping frames--something several other apps are able to do on the same computers.

This topic has been closed for replies.

1 reply

kevind92386150
Participant
December 14, 2021

I should note that I tried setting the Audio Hardware > Default Input to "No Input" and that didn't fix the issue.  In case someone was going to suggest that.