Braw not working in Premiere

No idea what is going on. Yesterday everything worked fine and nothing has changed with my system.

I use Blackmagic cameras and today opened a project I have been working on.

I got a pink alert on the bottom of the screen: "premiere braw error 1 metadata editing unavailable for this clip"

All of the Braw settings were reset on my clips.

I can not go in a change the settings, the entire interface is different and not accessible.

This is what the Braw interface looks like in Premiere for clips currently on the timeline, I can not change these settings at all

Settings for Clips in Timelines.png (52.92 KiB) Viewed 1876 times

If I import a new Braw clip into the project, that clip has NO braw settings at all

If I import a new clip, this is what the interface looks like - there is nothing in the drop down

New Imported Clips.png (9.89 KiB) Viewed 1876 times

ONLY if I create a NEW project can I import clips and make changes as normal.

The issue doesn't seem to effect NEW projects, this is what it looks like if I do that (how it SHOULD look)

How it's supposed to look.png (43.8 KiB) Viewed 1876 times

So I will have to do the ENTIRE project over again and rebuild all of the sequences.

I opened other projects I am working on: same thing. Every project I have EVER DONE using Braw is effected.

I tried uninstalling/re-installing Premiere, using previous versions, updating Blackmagic Raw plugin, tried previous versions of that...

I can not figure out what the problem is... not sure if it's the plug-in or Premiere

But I was just editing stuff yesterday and all was normal. To my knowledge nothing has changed in my set-up.

Try the Autokroma plug-in.

Sent from my SM-S908U using Tapatalk

Try the Autokroma plug-in.

Sent from my SM-S908U using Tapatalk

I'll still have to do all the settings for all of my work though? I've got a lot of projects going I'd like to resolve this and pick up where i left off if possible.

Maybe, yea.

Also check the Autokroma site and support for your issueswiththe BM plug-in. They give better support for the BM plug-in in Premiere than BM does.

Sent from my SM-S908U using Tapatalk

Flaky behavior in Premiere, regardless of which plugin gets used, is a real and massively annoying problem. It's Adobe's issue.

One safety step for future work is, after editing the BRAW settings of any clip, click the "update sidecar" button for it. This will ensure there is a copy of your settings saved with the clip in case the plugin goes wonky again. It also has the benefit that you could move your BRAW files to Resolve or Avid and maintain the setting for all BRAW clips that have sidecar files.

The BM plug-in has flaky behavior.

The Autokroma one does not. Ever.

But that's Adobe's problem?

Sent from my SM-S908U using Tapatalk

Autokroma, on their own website, list a series of bugs affecting their BRAW plugin for which they put responsibility squarely on Adobe.
https://www.autokroma.com/BRAW_Studio/User_Guide

C6FA1CC0-3AA4-41FC-A2CF-EA1FB3ACF48D.jpeg (795.65 KiB) Viewed 1514 times

If you think Autokroma is wrong about that, best to take it up with them directly.

I've had only two minor issues in using the Autokroma plug-in daily. Easily fixed on checking their site, which does a great job of posting every possible glitch or bug.

Excellent support, and I've had numerous emails with them over those things. And on other bugs they've posted that other Premiere users have experienced but I haven't so I could assist users on the Adobe forum.

I use BRAW as my main media. Have for quite awhile. When I started, I used the BM plug-in with constant issues. Doubt I ever went a full week without having to uninstall/reinstall the plug-in, update it, something.

Since getting the Autokroma plug-in I've had 2 minor glitches, both after installing updates of Premiere. And both fixed immediately by installing the appropriately updated Autokroma BRAW version.

Probably 2 years now on the Autokroma plug-in. Twice I had to update it after updating Premiere.

Pretty clean operation to me.

Sent from my SM-S908U using Tapatalk

The BM plug-in has flaky behavior.

The Autokroma one does not. Ever.

I've had only two minor issues in using the Autokroma plug-in daily.

Since getting the Autokroma plug-in I've had 2 minor glitches, both after installing updates of Premiere.

In other words, what Jamie said.

Update Resolve, most of your plug-ins may need updating.

So is that also a Resolve problem?

And as noted, to have an issue with the Autokroma plug-in required an update to Premiere to initiate. And was instantly resolved with an updated plug-in.

Which to me is totally different than the CONSTANT failures of the BM plug-in just day to day. Works fine Monday. Tuesday it shanks. Had to uninstall/reinstall sometimes a couple times to get it working.

No update of Premiere or Windows. NEVER had that happen with the Autokroma plug-in.

And when there was an update in Premiere that did cause an issue with the BM plug-in, it could be 1-3 weeks before an updated plug-in was published by BM.

Sorry, but that's very different behavior between the two plug-ins.

Sent from my SM-S908U using Tapatalk

Update Resolve, most of your plug-ins may need updating.

Which OFX plug-ins are you referring to? The only one I ever had to update once in step with a Resolve update was Film Convert. Besides that one, the rest I use have simply worked after updates. Same thing with macOS updates.

In any case, there is a significant difference in between an OFX effects plug-in (something optional in a workflow as a creative choice) versus a source codec plugin. It is the latter that has been more prone to bugs in Premiere and which is the topic here.

Resolve isn't relying on a plugin architecture to support codecs. In the case of raw codecs like Red's .r3d, for example, BMD uses Red's SDK to decode it natively in Resolve. And it's the same for Canon's raw codecs and Sony's XOCN, and ARRIRAW. It is what Premiere could have done for BRAW, but instead has left to third parties relying on Premiere's source codec plugin architecture that has suffered from consistently documented problems, such as that nasty drop frame timecode bug. That is how we end up with the issues described in this thread.