Welcome Dialog

Welcome to the Community!

We have a brand new look! Take a tour with us and explore the latest updates on Adobe Support Community.


"The file is busy, and couldn't be updated"

New Here ,
May 01, 2018 May 01, 2018

Copy link to clipboard

Copied

There is a very common error I am receiving while logging footage: "The file is busy, and couldn't be updated".

This happens to random R3D and sometimes entire folders while trying to write data to the xmp.

I can't be sure if it is only a RED file problem or not at this moment.

If the data is written with the error message, it will no longer be there the next time the project is opened.

Adobe Customer Support says that this is common problem and it will be fixed in the next update. Somehow I highly doubt that.

Screen Shot 2018-05-01 at 1.59.56 PM.pngScreen Shot 2018-05-01 at 1.59.47 PM.png

Anyone else experiencing this problem that could help? Adobe is no use.

Views

7.2K

Likes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
LEGEND ,
May 01, 2018 May 01, 2018

Copy link to clipboard

Copied

Likes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Community Beginner ,
Jun 11, 2018 Jun 11, 2018

Copy link to clipboard

Copied

I am having this exact same issue and it is very problematic to my workflow.

Likes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
New Here ,
Jul 22, 2018 Jul 22, 2018

Copy link to clipboard

Copied

Turning off "Write clip markers to XMP" in Preferences -> Media enables the setting of markers without the error, but the markers are only set within the same project.

I'm having this issue with R3D files - had it in cc 2017 too but it was inconsistent. Now in 2018 markers in R3D simply don't work unless you turn off writing markers to XMP

Likes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
New Here ,
Aug 06, 2018 Aug 06, 2018

Copy link to clipboard

Copied

I concur with TaintedGray, Using R3D media, I just opened up a recent cc 2018 project that I marked the hell out of, none of my markers exist. There goes a good 4 hours of work...In the past cc 2017 was hit or miss sometimes I'd loose huge chunks of Marker notes, sometimes it would all be fine.

What's strange is, I just finished another project in cc 2018 and I believe all my notes and markers remained.

Likes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Adobe Community Professional ,
Aug 07, 2018 Aug 07, 2018

Copy link to clipboard

Copied

There was an important fix for sequence markers in 2018.1.2, and my best understanding is that some clip marker issues remain. I don't have good test files for r3d. If can send me one, I'll test.

Likes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Community Beginner ,
Feb 26, 2021 Feb 26, 2021

Copy link to clipboard

Copied

Thanks for the tip. Once again the solution to a Premiere problem is to limit the software's functionality. Adobe is a joke, Resolve is looking better and better every day

Likes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Community Beginner ,
Dec 11, 2018 Dec 11, 2018

Copy link to clipboard

Copied

Did you anyone figure out this issue out? My workflow was in CC 2018 but since updating to CC 2019, this error issue has surfaced for me. With this too, i'm wondering if this an issue with comment markers I made in Prelude on my r3d clips, which don't show up in Premiere now when i open up the clips there. Usually the markers carry over perfectly. I've since updated to 13.0.2 on premiere and still the same problems. Very frustrating.

Anyone else encounter this issue?

Likes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Explorer ,
Nov 14, 2019 Nov 14, 2019

Copy link to clipboard

Copied

I've got the same one using PP 2020 - I'm using Canon .MXFs and AIFFs for audio but gonna try disabling marker to XMP as the R3D peeps suggest above and report back...

Likes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
New Here ,
Jan 28, 2021 Jan 28, 2021

Copy link to clipboard

Copied

It seems that the problem hasn't been fixed 😞 working with canon .MOV footage.

The turning off "Write clip markers to XMP" tip seems to be a workoaround meanwhile.

Likes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
New Here ,
Feb 28, 2021 Feb 28, 2021

Copy link to clipboard

Copied

LATEST

great, this was posted on the 28th, yeah im having this issue as well i have transition presets and i cannot apply them to my adjustment layer because they wont playback.

Likes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines