Serious “Error retrieving frame / Frame substitution recursion” issue in Premiere Pro with Nikon ZR N-RAW
Premiere Pro – “Error retrieving frame / Frame substitution recursion” causing severe stalls with Nikon ZR N-RAW
I’m experiencing a persistent frame decoding issue in Premiere Pro with Nikon ZR N-RAW (.NEV), mainly 4K 50p.
Premiere repeatedly reports:
Error retrieving frame [number] at time [timecode] from the file ZR1_xxxx.NEV, substituting frame [number].
Followed by:
Frame substitution recursion attempt aborting after multiple attempts.
This happens across many different clips and frames.
The most noticeable behavior is that Premiere is actually extremely fast between the errors. Timeline scrubbing is perfectly smooth, then an error occurs and Premiere completely stalls for approximately 1–2 seconds. After that it suddenly recovers and scrubbing is fast again until the next error.
Exactly the same happens during export: the export runs very fast, suddenly the percentage completely stops for a few seconds, then it continues at full speed again. This repeats throughout the export and makes the total export time extremely slow.
It looks like a repeated decode → stall → recover → decode → stall → recover cycle.
I have reproduced this across:
- Premiere Pro 25.x
- Premiere Pro 26.x
- Premiere Pro 26.5.1 Build 1 (latest)
- Multiple macOS versions, including older versions and macOS 17, 18, 20, and latest Golden gate 27
- MacBook Pro m2 pro
- Mac mini m1
- Brand-new Mac Studio m5 max
- Multiple different external SSDs (mutiple brands)
- Multiple original Nikon ZR .NEV files
- Brand-new Premiere projects
- Brand-new Mac/Premiere installation
- No third-party Premiere plugins
- No existing preview/render files
- Latest Nikon ZR firmware
- High Quality Playback disabled
The behavior remains essentially identical across all these systems and versions.
Because performance is excellent between the errors, and because I can reproduce the same issue across different Macs, macOS versions, Premiere versions and SSDs, this does not appear to be a general CPU/GPU or storage performance issue. It appears that Premiere’s decoding/frame-retrieval pipeline temporarily stalls whenever it fails to retrieve a frame.
This is a serious issue for a professional workflow because it makes both editing and especially exporting unnecessarily slow and unreliable.
Adobe, could this please be investigated by the Premiere engineering team?
