Resolve 19.1.2 Fusion Transitions does

All my transitions appear on Effects panel but when I try to use it on timeline only black frames are rendered.
If I open the transition in Fusion panel no media_in or media_out in node view.

Uninstall 19.1.2 and re-install 19.1.1 now the Transitions templates are ok.

So, if you have on your projects many fusion based transitions DO NOT UPGRADE TO 19.1.2!

Not seeing this on my MacBook (Resolve Studio 19.1.2, Sequoia 15.2). Which transitions are you seeing this with?

.settings is not useful in 19.1.2.
.drfx is ok in 19.1.2.

Well, I cannot check anything right now, but excuse me : if the .setting. files are completely invalidated now, that's a huge change which has to be spread widely... Is it what you're writing about ?

The Fusion transitions included with Resolve are working fine for me in Studio 19.1.2 for Windows.

Are you referring to those, or to plug-ins, Santi?

What's New in DaVinci Resolve 19.1.2

• Addressed Fusion comp being disabled when disabling a macro.
• Addressed potential DRFX naming conflicts.
• General performance and stability improvements.

Somewhere in those fixes they seem to have broken way many use templates and presets. But they don't share much more than bullet points, although on blackmagic forum there are few threads people reporting issues. Drag them to actual clip or make a .drfx, but settings probably won't work unless they are applied to existing clip or saved as .drfx with proper naming. Also it seems reactor deploy folder allows it to work as before if you place them there, probably because of correct naming. I don't know the naming method in that one, just that is works.

That's because the ones that are included are all saved in a *.drfx file.
The ones that people create themselves (macros, settings etc) according to the manual all of a sudden don't get recognized anymore.

Uh...
That's kinda a big deal and should not be covered under "General performance and stability improvements."

Considering how many ".setting" files people use, this would be the biggest fu to fu users since the redesign.

There's no way this is on purpose.

For example:

settings everywhere

Screenshot 2024-12-19 105636.png (249.97 KiB) Viewed 8605 times

That's because the ones that are included are all saved in a *.drfx file.
The ones that people create themselves (macros, settings etc) according to the manual all of a sudden don't get recognized anymore.

Whaaaat ?
So that's what I feared before actually . That's a huge change into WFs, are you guys quite ok and quiet with that ? Like "well... this has changed.. ok..."

Uh...That's kinda a big deal

Ah, no **** ! Sure it is !

Please, is there - sorry for my awakening here - ANY official communication about we're supposed to turn .settings into .drfx for them to work again, or stuff ?

Considering how many ".setting" files people use, this would be the biggest fu to fu users since the redesign.

.setting was indeed just a lua code in a file and depending on where and in what folder it was placed it would execute the code and in fusion it was the same as copy and paste from clipboard. So not much restrictions other than folder structure. I guess people used it quite freely, and than probably I would assume something broke or people started to copy .settings that would need to be placed in a particular folder to work correctly, and they would place it in another folder where same name .setting exists but cannot function. Edit page vs fusion page for example.

And I would assume with more and more people sharing their "presets" with no proper code of conduct, some users just place them in wrong folders. This was probably reported as "bug" and BMD "fix it". "Addressed potential DRFX naming conflicts." sounds pretty vague to me, so maybe someone knows and can explain what exactly does it do, when and why. I can only speculate. I would assume they made it so that only .DRFX work on edit page and .settings no longer function in that capacity so they can't be as easily used and abused. Which is why they seem to work when you put them on a clip, the pass it along to fusion.

I wish Blackmagic would be more forthcoming with explanation about changes in the release notes, because " General performance and stability improvements." has reached a meme status.

And they really need to make some kind of export function so people can save settings as DRFX automatically and in correct folders. With more and more people sharing their macros and more and more use of it as it was not indented, it was about to become a mess sooner or later.

Like when Luts were meant to be sued for technical conversions and on set look management, and now everyone just shares them online with no regard to what the input or output devices were. Similar seem to have happened with presets from fusion being shared for edit page. Look, how we can make this cool title and than post it online, someone downloads it and just sees .setting and puts it in wrong folder. Something breaks or is in conflict. And Bug report is on the way. lol I've seen the same with luts. Why is my lut not working, I want my refund. Don't bother me with fine print.

How Blackmagic deal with this mess, will be interesting to see.

I just tripped over this myself. I have ways to work around it, but it's pretty nasty.

To be honest, though, I suspect it is completely unintentional, as in, it is a bug. There is zero chance BMD would disable this functionality without making it very clear they intended to do so, deprecation announcements, etc.

I guess we just need to be patient for now.

This problem on two machine running windows 10 and windows 11.
.setting are inside all .drfx files....

[Dwaine Maggart]

The change was not intentional. I assume it will be addressed in the next release.

For now, either revert to 19.1.1, or put your current .setting files into a .drfx file.

A .drfx file is just a .zip file.

So find your .setting files. Wherever they are, use your favorite zip utility to put the .setting files into a .zip file, with a name of your choice. Do this in whatever folder the .setting files are in. Then rename the .zip file to .drfx. Then ideally remove the .setting files from the folder. You don't HAVE to remove them, but if you leave them there, you'll see 2 entries for each item. One will work and one will have the current behavior.

And when I say "remove" the .setting files, don't delete them. Just move them to a different location, in case you need them later.

Man... Dwaine, thx a lot to pop up here with your suggestions, because that was so clearly outside the boundaries of classic fundamentals that it was frightening (at least for those who had some settings stuffed there)

I understand it would be a super bad idea to add side or off topics things here and now, but I suspect things slowly drifted since v19 or 19.1, especially in the field of having a graphic involved in a .setting macro; maybe we'll take time to evoke it later I hope

So let's keep it short and positive : what a beautiful coincidence, I aborted a surprisingly slow download of the version which is finally a better idea to avoid... XMas coming probably

Anyway thx a lot Dwaine, highly appreciated input here...

how can I revert to 19.1.1 without losing data?

The change was not intentional. I assume it will be addressed in the next release.

For now, either revert to 19.1.1, or put your current .setting files into a .drfx file.

A .drfx file is just a .zip file.

So find your .setting files. Wherever they are, use your favorite zip utility to put the .setting files into a .zip file, with a name of your choice. Do this in whatever folder the .setting files are in. Then rename the .zip file to .drfx. Then ideally remove the .setting files from the folder. You don't HAVE to remove them, but if you leave them there, you'll see 2 entries for each item. One will work and one will have the current behavior.

And when I say "remove" the .setting files, don't delete them. Just move them to a different location, in case you need them later.

How can I revert to 19.1.1 without losing any data?

I've just come across this problem as well - none of my downloaded .setting files work anymore. I have a stack of titles downloaded from Envato Elements used across multiple projects and timelines.

I'm on W11. Solution is to uninstall Resolve Studio and all components from Control Panel and reinstall 19.1.1 - worked for me with no problems at all.

Phew.

[Dwaine Maggart]

@Dvir: There is no database change from 19.1.1 to 19.1.2, so reverting to 19.1.1 will not cause data loss.

If you are on Mac or Linux, just run the 19.1.1 installer and install over 19.1.2.

If you are on Windows, you'll need to use the Windows Add or remove programs Control Panel and uninstall DaVinci Resolve. This will not affect your project or user data. Then run the 19.1.1 installer.

I had the same problem, I have a few transitions that had a black screen.

I uninstalled v19.1.2 and re-installed v19.1.1 and the transitions work again.

It is easy to go back to older version, this is why I always keep and archive the last 3 versions on my computer.

Will wait for 19.1.3 to come out and try it again.

Thanks Blackmagic.

It might be prudent to put a note regarding this issue in the "announcements" thread on the release of 19.1.2 for those who have not yet upgraded but may be affected if they do.

Having the exact same issue. Reverting now to 19.1.1. Thank you all for commenting on this bug.

I did Exactely what Dwaine From BM suggested and worked!!

just created a .zip file withe the folder containing the .settings files, than rename the extension from .zip to .drfx !!

NOTE:

The .drfx must be at SAME location where the .settings was:
AppData\Roaming\Blackmagic Design\DaVinci Resolve\Support\Fusion\Templates\Edit\Transitions

NOT in the same location as the NEW DR .drfx plugins are:
AppData\Roaming\Blackmagic Design\DaVinci Resolve\Support\Fusion\Templates

for me this way old settings came to work again in 19.1.2.

BUT some ones still has the message "No frame available for media output"
The workarround for it is:

-right click the transition in your timeline, open in fusion page
-disable the line to the mediaout node that is in the left little square conector in the node before mediaout
-do the conection again using the little square connector that is at the botton of the node before mediaout into the input of the mediaout.

AND another issue I had in one specific transition is that it becames duplicated - with a mediain and mediaout conectors outside the macro group that I was unable to connect it... so i just deleted it and leave only the macro group in fusion page and it worked like a charm lol

Well so these are some possible problems and their possible workarounds i found here for now.

Good luck guys!
See ya in 19.1.3 lol

The change was not intentional. I assume it will be addressed in the next release.

For now, either revert to 19.1.1, or put your current .setting files into a .drfx file.

A .drfx file is just a .zip file.

So find your .setting files. Wherever they are, use your favorite zip utility to put the .setting files into a .zip file, with a name of your choice. Do this in whatever folder the .setting files are in. Then rename the .zip file to .drfx. Then ideally remove the .setting files from the folder. You don't HAVE to remove them, but if you leave them there, you'll see 2 entries for each item. One will work and one will have the current behavior.

And when I say "remove" the .setting files, don't delete them. Just move them to a different location, in case you need them later.

Is doing that will mess with the fix in the next update?

[Dwaine Maggart]

No.

I'd rather ask : is the next release fix going to prevent us from doing the .setting -> .drfx and finally find our .settings working as before "from their previous locations" (like, for guys like me who chose to stay on 19.1.1) ?

[Dwaine Maggart]

Yes.

Edit: Re-reading your question, I may not have answered correctly.

The next release will fix the current issue with Fusion titles and transitions using .setting files.

If you put your .setting files into a .drfx file, that will not affect the next release fix of the current issue.

.drfx files will continue to work correctly with the next release and if you've chosen to revert to 19.1.1 and not mess with your .setting files, those will also work with the next release, same as they do in 19.1.1.

To summarize, whether you put your .setting files into a .drfx file, so they work with 19.1.2, or you don't, it will all work with the next release, same as it does in 19.1.1.

Thx Dwaine... Have a nice NYEve

Edit as well :

.drfx files will continue to work correctly with the next release and if you've chosen to revert to 19.1.1 and not mess with your .setting files, those will also work with the next release, same as they do in 19.1.1.

Ok Dwaine, thx (a lot) to take time to answer and be specific, i (and no doubt a lot of others) really appreciate.
I'll keep a bookmark of this very answer to help if needed.

Thank you for helping with this. I had updated and checked a couple of previous projects to make sure everything was working. Then today at a filming I was putting together the project and none of my graphics were working. Thankfully I was able to find this before the client could see the trouble.

So thank you.

Is it fixed on the 19.1.3 update?

[Dwaine Maggart]

Yes, this is addressed in 19.1.3.

Hey guys!
It doesn't seem to have been fixed for me in the newest DR 19.1.4 version.
When I use a text animation from a .settings file, all I get in the Inspector panel at the Edit tab is blank, no controllers.

Hey guys!
It doesn't seem to have been fixed for me in the newest DR 19.1.4 version.
When I use a text animation from a .settings file, all I get in the Inspector panel at the Edit tab is blank, no controllers.

I'm having the exact same issue. I just updated to Resolve Studio 20 and all my existing Fusion titles can't be edited in the edit page. Edit tab is just blank... How do I fix this?

[Dwaine Maggart]

Please provide screen shots showing this issue.

Mac or Windows? Free or Studio? If Mac, Apple App Store Mac, or Mac from the BMD site?

Please provide screen shots showing this issue.

Mac or Windows? Free or Studio? If Mac, Apple App Store Mac, or Mac from the BMD site?

Studio, Mac BMD site version. The panel is blank for all the existing fusion titles (that I made prior to the update). Clicking on it does nothing, so the panel is not collapsed as it might look like. And since most project DBs were already updated to the new version, I can't downgrade to 1.9.4.