Copy link to clipboard
I've got a problem that I think others have had, I'm trying to use MXF video files in a project I'm working on, the quality of the video is the main priority (Audio has been recorded separately so there's no audio on the MXF video files). I've already tried using MP4 but the quality has reduced significantly so that's a no-go. After importing the MXF files, the error sign lights up, and 'Frame substitution recursion attempt aborting after multiple attempts on file' is the issue every time. I've imported it under different Video rendering and playback options but no luck there. Each time I've tried importing the MXF files, the number of errors alternates, sometimes there are loads, other times there are less. Does anyone know what to do to fix it?
How did you import the files? Did you use the Media Browser? Did you keep the folder structure intact?
Assuming "yes" to the above, try not interpreting them to 23.976. Instead, leave them as is (60 fps) and edit them in a 24 fps sequence.
Does that get rid of the recursion errors?
Thanks for the response. I used media browser to import and interpret footage to 23.976.
The reason they're interpreted is for playback to be in slow motion.
I tried your solution and currently no errors.. but this error didn't start to occur until days after culling footage and beginning the editing process. So it may reoccur in the future?
I've done it this way hundreds of times with no issues. Same files, same sequence settings, interpreting footage, everything..
It didn't start happening to me until the update.
which is why you should always think twice before updating. And I strongly advise creating a bootable clone of your startup drive before doing an update so you can revert to the previous setup relatively quickly... (I use something called Carbon Copy Cloner) And never have previous versions deleted when doing the update so if issues arise, you can just work in the earlier version... Don't mean to sound like a know-it-all (well maybe a little bit) but I've been doing this for a very long time and things can go south after an update... And you can always reinstall the previous version if necessary... That's one of Creative Clouds strong points...
Do I understand that you tried the same physical files on disk that you had used in earlier versions without issue?
If so, please try deleting *all* your media cache files. Do it before opening a project, which means you'll have to launch Pr from a shortcut, not by double-clicking a project file.
Then start a brand-new project. Do your normal import/interpret thing and see if you get errors in the new project.
If no errors occur, then you may be able to import your old project into a new one and proceed from there.
Wanted to circle back on this with some unfortunate news. I did as you suggested and it was working fine for about 24 hours. I moved all the footage over to another hard drive. From a Samsung t5 to a t7. I saw in another post about this same issue saying maybe the external drive wasn't reading quick enough..
Today I came across the same error again in Premiere 2022. Nothings has changed. Its so random and there seems to be no ryhme or reason at this point. Extremely frustrating to be putting in hours of work for this issue to keep popping up out of now where.
Not sure what else to do at this point with this project.
I'm sorry the good news was only temporary.
If it is data throughput related, maybe take a look at the bus; what else is on the bus? Are there any open programs or background tasks that might start activity just when you don't want them to?
Just figured I'd mention you're not alone. I've been in this same scenario for probably a year now. Same camera, file types, frame rates, resolutions, etc. I've searched all over the internet to no avail as to why this is actually happening and how to resolve. I assume there aren't enough of us in this exact scenario to cause anyone smart enough to figure it out.
I've used all different kind of import processes, drives, computers, PP versions, and nothing has helped and still it seems random on when it pops up. Since I'm using a proxy workflow the only thing I can do to make it bareable is use my proxies for everything till I color grade (last step for me) and then struggle through if it pops up. Once I get to the end, make all media offline, relink all media, then without going back to my timeline (at all, since when i do I start getting the error again and black chunks), export.
It's obviously something primarily with the mxf files (I get a random similiar error with some braw files, but like 1:100 vs the c70). If you ever figure out your issue, I'd love to know how you resolved it.
Any updates on this? I'm scrubbing through the timeline with C70 footage and I get that with almost every clip. What is going on???
I've had no progress on resolving this issue. I typically use a proxy workflow and switch to source files when color grading and even then I typically render timeline as I work and that way I typically get less errors so that's it's workable.
I really wish Adobe and Canon could sit down and smarter minds could work this out, but there's no road to fixing it if we can't figure out what the issue is to begin with.
I will say, I did have one project small enough to keep on my local drive and move my footage there and had a lot less of these errors, but they didn't disappear. However typically keep all footage on 10-40Gbps connection, so pipe speed shouldn't be the main issue. My projects are typically 2TB+ so I can't keep my current projects on my local drive even if I wanted to.
Sorry none of that is very helpful, but I've yet to come across and info that really is anyways.
That's a bummer.
I'm editing directly off my M1Max SSD. Not sure if I can get any faster. I think it's a software bug.
Yeah that's what I was saying, it doesn't seem like a speed issue since my NAS has a 10-40Gbps connection ... but for whatever reason I still got less errors working off the local drive. Normally I just stick with my proxy workflow and always render out sections I'm working on.
Hi Marand Media,
Sorry about this. Is this an updated file from an earlier version or a brand new project? If you have not tested a new project, could you try it? Please also try importing these card based files via the Media Browser and not File > Import or by dragging into the Project panel.
Let us know what happens.
If the error still occurs, please upload a sample file and I'll test it on my end. FWIW, I would definitely take the NAS out of the chain while you are troubleshooting, then add it back in after you have solved the issue.
I just tried with a new project and also importing at Kevin suggested and it did not solve the issue. As soon as I start scrubbing on the footage I get the error message.
Seeing that it didn't work for you @scottwild, you should probably upload a sample file for Kevin to test ... maybe that'll get us somewhere.
Honestly for me when it happens @Kevin-Monahan, it's so random that it's hard to recreate to troubleshoot. I did as you said with a brand new project and imported only like 40 files and went through my normal workflow and didn't get any errors, however I've done this before and I always eventually do. I can't keep fake editing so, on the next project I'll start as you suggested and at least keep some of the footage on the local drive and reply back with my findings.
But while I have you Kevin, can you explain what this error actually means? I'm not asking what issue it points to is, but like specifically what the error is. Like is it trying to pull a frame from somewhere specific and it's unavailable due to many possible reasons? Or does PP go through some specific process when you play or scrub that constantly is referencing specific data that is somehow unavailable? Everywhere I look online they just say try this and try that without actually explaining the meaning behind this error.
Sorry about this. I am not an engineer nor am I on the Premiere Pro team. I'd have to ask what the error is all about. I'm in support, by the way. I try and gather intelligence on some of these cases, but it is not easy and a lot of variables are involved.
All I know is that we started seeing stuff like this since MAX when the team changed the requirement for importing card-based media. Are you working with media that was captured to a CF card? That could be at the heart of it.
To be clear of it, I'd simply transcode camera originals to an editing codec on ingest and move forward with a workflow that avoids issues that occur in working with raw camera files and can offer a smart rendering workflow (XDCAM might be an exception since you can smart render it).
That said, it should be OK to work with camera originals. I just prefer to leave that component out of my workflow since I am not pressed for time, nor does losing one generation of "visually lossless" video bother me. For some, that bit of time and fraction of quality IS important. So, for those folks, I'd advise filing a bug here: https://adobe-video.uservoice.com/forums/911233-premiere-pro
Not sure if the advice helps. I do hope the bug does get fixed. I'll see if I can find out more. Sounds quite annoying.
What are your computer specs, Scott?
I'm using a brand new M1 Max Macbook Pro with 64GB RAM and an 8TB SSD.
Alright. Thanks for the info. How are you importing your C70 footage? Are you using the Media Browser after copying the contents of your CF card to the Mac HD?
Those cameras are very cool, by the way. I hope I can help you.
I tried using both methods to import the footage.
Niether made a difference in the error.
Yep, C70 is an amazing little package.
Dood, it is ALWAYS the same thing with you guys, update after update, year after year. Admins come on here and suggest work-around after work-around, like the software just couldn't be the problem, but it always is!?!
So of course, I am having the same problem. First I thought it was because my laptop powered down, so I left it on... same thing. Every time I open the only project I've started since the 2022 update, I get a laundry list of red triangles saying 'frame substitution' blah blah, or some other bs.
The new update wasn't even worth putting out anyway, you just changed things that people have gotten used to (as usual!), so they have to practically re-learn basic things that we've been doing for years (i.e. the 'new' start-up screen, etc.).
I just don't get it, if it ain't broke, don't fix it... but you do, and the whole time, people such as the O.P. are losing money while you guys keep raking it in - without even offering any sort of reparation or refund for lost functioning of a product already paid for by us?!!
As of 5/29/22 I have EXACT Same issue. NOTHING in my workflow has changed (6+ years of doing exact same) EXCEPT Version of Premier (2022 22.4.0 build 57). Further I have both Mac & PC. Timelines respond SAME on both platforms. WTF!!!!!!!!! What is solution?
Bump. Same problem. Brand new out of the box m1max 64GB Ram, samsung 8TB SSD. C70 footage 60/23.98.
Adobe, please. This codec and processor are both must be very very common with your users.
Had some luck on my less powerful M1 13" by reverting to a 2021 version of Premiere (you can install two versions at once.) Not the worst thing to try. Might try a few versions on this new Macbook Pro if I have time to run tests between delivery deadlines because these are tools I use for my job... which is all the more reason I wish I didn't feel like I was live beta testing the latest version.
Yeah I don't think the issue is hardware capabilities. Sucks that there has been no progress on this issue from Adobe.
I actually tried troubleshooting again today with some files in a new project right on my internal drive in my M1 MacMini with multiple later versions of PP CC and still had the same errors.
Sucks because there are some definite benefits to later versions of PP, but I did have less of these errors with older versions.
Adobe (@Kevin-Monahan), can you just recreate the issue on your end and start troubleshooting the issue? I'd be willing to send some files if needed. if you can't recreate the issue, I'd like to repeat the process on my side and see when/if the issue pops up.
YUPPPPP! That's what we are all doing - LIVE TESTING A FREAKING BETA VERSION - while THEY get paid for it!!! What do we get? Lost money and clients, while they get paid. Do they offer us a discount or anything of the sort... NOPE! Thanks again Adobe, appreciate it!