You can use our official uninstaller! More information here If it didn't work here's the manual process to do so : 1. Exit All adobe softwares 2. Delete this folder : (Windows) C:\Program Files\Adobe\Common\Plug-ins\7.0\MediaCore\BRAW Studio (Mac OSX) /Library/Application Support/Adobe/Common/Plug-ins/7.0/MediaCore/Autokroma BRAW Studio 3. Delete folder named com.autokroma.brawStudioPanelVisible in this folder (delete also com.autokroma.brawStudioPanelHidden if you find it !) : (Windows) C:\Program Files (x86)\Common Files\Adobe\CEP\extensions (Mac OSX) /Library/Application Support/Adobe/CEP/extensions 4. Relaunch your Adobe softwares If you performed a manual installation of BRAW Studio yourself you need to look for "BRAW_Studio" and delete all related files !
Please double check you entered a BRAW Studio license and not an AfterCodecs one read our article here for more details. Once licensed, please empty your media cache (How to clean (delete or trash) media cache files?) and restart your Adobe applications. If you converted some .braw files for proxies or into another codec (or exported a Premiere Pro project containing .braw) before entering the license, you'll need to reconvert them again with the plugin licensed because the trial image is burned forever in them (BRAW Studio is not used anymore to make the proxies!)
One license is for the same user on up to two computers not used at the same time. For example you can do OSX + Windows not at the same time, or your professional computer and your personal laptop not used at the same time.
Yes : BRAW Studio used to be available in two different licenses for different uses, but it was recently merged into the same license in Version 2 so now you'll get access to BRAW Studio on all Adobe applications. Don't forget to updateto get the latest version.
If you're on Mac OSX Catalina or higher (10.15+) sometimes Apple notarization system doesn't work so you can't open easily our installer .pkg. Please allow opening unnotarized applications in your Security Preferences, see this article : Safely open apps on your Mac on Apple.com
Could you try to delete BRAW_Studio.app in this folder : /Library/Application Support/Adobe/Common/Plug-ins/7.0/MediaCore/Autokroma BRAW Studio/; also delete if it exists the same for AfterCodecs : /Library/Application Support/Adobe/Common/Plug-ins/7.0/MediaCore/Autokroma AfterCodecs/AfterCodecs.app In any case, contact us !
On Windows you should run your cmd.exe or Powershell in Administrator Mode, then run BRAW Studio installer executable with the /S argument, for example in Powershell : ./"BRAW Studio v2.1.2 Installer.exe" /S if you're in the extracted folder from the downloaded zip. WARNING : if you have Blackmagic RAW Adobe plugins installed, it will uninstall them without asking you for confirmation (since there is no GUI here) and will redirect you to a webpage explaining the incompatibility between the two plugins
You can export proxies and convert (Right click -> Export Media) your .BRAW directly from Adobe Premiere Pro and it will open up Media Encoder for conversion. If you converted your proxies before entering the license, you'll need to reconvert them again with the plugin licensed because the trial image is burned forever in them (BRAW Studio is not used anymore to make the proxies!)
.BRAW imported into Adobe Media Encoder are decoded by default with the "Camera Metadata" setting, like on DaVinci Resolve. This means that it will try to read the .sidecar next to your .braw to apply the color grade. If it can't find it, it will use the settings from your Camera when you shot the footage. If you changed the .sidecar after importing the footage, it will keep the same old .sidecar values until your restart Media Encoder / Premiere Pro.
When you send a project or a .braw clip from Premiere Pro to Media Encoder's render queue, it will act as a dynamic link between the two softwares; this means the render will look exactly the same as it looked like on Premiere Pro (i.e. it will take Exposure, ISO, Color Balance, Contrast etc. from the Source Settings). See previous answer if you import your .braw from Media Encoder's UI
No, you need to click "Update Sidecar" in order to create or update the .sidecar files. Please note that you might need Administrator Rights for some folders where you don't have permissions to write !
No they are fully incompatible. More information here : BlackmagicRaw Plugin and BRAW Studio - What's the difference ?. Please note we are only talking about the Adobe plugins from Blackmagic RAW. You can use Blackmagic RAW Player and the thumbnail previewer along with BRAW Studio there's no incompatibility. We even have a checkbox in our installer to install them automatically !
This error message means that you opened a Premiere Pro project that was using Blackmagic's Adobe plugins for Blackmagic RAW, and now you don't have that plugin installed anymore so it cannot find the Source Settings effect linked to each .BRAW in your Premiere Pro project. The simplest to fix this issue to install again Blackmagic Design's Adobe plugin. If you're now using BRAW Studio you will have a missing Source Settings filter in the Master tab of your .BRAW and won't be able to retrieve your Source Settings color grade.
This error message means that you opened a Premiere Pro project that was using Autokroma BRAW Studio plugins, and now you don't have our plugin installed anymore so it cannot find the Source Settings effect linked to each .BRAW in your Premiere Pro project. The simplest to fix this issue to install again BRAW Studio.
The way Source Settings works in Premiere Pro is to modify all instances of the same clips on all timelines, so any change will affect all instance of the same .braw imported. This is only an issue on Premiere Pro because on After Effects you have the Layer Settings filter that is applying the RAW parameters on the current layer and not the source.The best way to apply different RAW settings on the same footage on Premiere Pro is to use the BRAW Studio Panel feature : "Set New Source". You just need to select a clip and click on the button in the BRAW Studio Panel !More information here !If you want to do it manually, you have 2 choices : 1. Import the same footage many times (as much as you need different color corrections on this footage) and change each Source Settings 2. Or Use the "SubClip" feature, see this article :
Import your braw footage
In the "Source Monitor" panel, choose the bounds to your first "Sub Clip"
Right click in the Project panel in your footage and select "Make Subclip"
After this : you will have a new source in the project (the subclip) with different RAW Parameters.
Please restart Premiere Pro by holding the SHIFT key and press OK to the popup that's asking you if you want to clean the plugin cache, then Premiere Pro will start by having the plugin cache cleaned and the error should disappear. Please contact us if you still get this error!
Please read this Adobe Blog post : Red, yellow, and green render bars and what they mean. We noticed that with .braw you can't add other effects on top (like Lumetri) without cancelling any cache renders, it will always go back to the Red color when you relaunch Premiere Pro.
You need to select "DecodeUsing" -> "Custom A" (or "Custom B") to be able to set the other parameters below. Gamma Controls like Saturation, Constrast, ... are only available if Gamma is set to Blackmagic Design Film, Blackmagic Design Extended Video or Blackmagic Design Custom.
The panel could be not well initialized. At the bottom of the Panel, please try to hit the "Reload Panel" button. Note that for Premiere Pro CC 2018 12.0 it's normal, you will need to click inside the Panel to update its content. If you still have the problem, please send us some logs !
After some tests in our side, "Floating point" could be displayed but then After Effects would always ask for 32bits to be rendered, even if "8bits" or "16bits" is selected in Project Settings. This would involve performance issues because 32bits takes more time to be rendered. Same for "Trillion of Colors" : 16bits would be always asked for 8bits and 16bits and that would also involve performance issues.
For us, the current behavior is the best : if you configure your project in 8bits, then After Effects will ask 8bits to our importer, and same respectively for 16bits and 32bits. Sadly, the description will stay as "Million of Colors" even if it's true only in 8bits.