A low-level exception occurred in: Red Source Settings (AEVideoFilter:29)
What usually triggers this error is 'Ripple Trim Previous (or Next) To ********' or 'Ripple Delete', which are the functions I use most often, in concert with 'Add Edit' (add edit doesn't cause the error).
This starts to happen anywhere from one, to a few hours into a session. Once it starts, it repeats every time one of the "triggers" mentioned above is used.
As you can see in the attached screenshot, the error happens many times (max 99 listed?) at once. I suspect this could be one error for every instance of RED footage used in the sequence, but that's just a guess.
One thing to note is that the "trigger" doesn't necessarily need to be performed on the *** footage itself. RED footage needs only to be present in the sequence, and the error can be triggered when editing other footage.
I've attached detailed System and nVidia information in case an Adobe engineer wants to take this issue seriousely.
Cheers.
Anonymous
shared this idea
7 comments
-
Antoine Autokroma
commented
If anyone has workflow issues with REDRAW R3D / Source Settings in Premiere Pro / Media Encoder / After Effects please tell us about it here https://www.autokroma.com/contact !
-
Anonymous
commented
David, how do you locate the "duplicate files"?
-
David Solbjørg
commented
I had some duplicate files (two exports of R3D files with different ISO settings) in my timeline which ended up being a conflict after updating to most recent version of Premiere (13.1.4 (build 2))
That caused the error you're describing.
The fix:
Deleted the "duplicates" from the project.
Renamed the files and folder containing them and re-imported them into project.Good luck.
David S. -
John VonMutius
commented
Same thing happening to me. I'm working in a large project with about 10000 clips. Sometimes I can edit for a couple hours, sometimes only for 10 minutes, but the error always appears. Usually, it pops up a few times intermittently before overwhelming the system and causing Premiere Pro to shut down. Also, possibly related, once I start getting these errors, the Save dialog behaves strangely. It pops up saying that it's saving the project, but the progress bar will never complete. If I click cancel and check Windows Explorer, it shows that the file has indeed been saved. I've even worked from project files saved that way, so it seems to actually be saving them.
-
Michael Gyori
commented
Happening to me too.... while editing a feature film shot on Red. Making manipulation of the complete rough cut very difficult.... laggy.... hanging.... and eventual crash.... sometimes can't save the project.
-
[Deleted User]
commented
Moving clips with the Select Forward tool triggers it as well. All these triggers have something in common - they usually involve moving a large number of clips at once, but the *** clips don't necessarily sit in the group of clips being moved.
-
[Deleted User]
commented
In addition to the three "triggers" mentioned above, inserting clips from the source monitor and swapping the order of clips while holding Ctrl+Alt can also cause the error.