- Posts: 514
- Joined: Thu Jul 08, 2021 8:31 pm
- Real Name: Bart
Version 18.6.6
Create a custom macro by
- on Edit Page import a fusion composition
- open it into Fusion
- Add whatever stuff you want. I added a Text node
- Added versions
- Exported (saved) the macro in Title
- Imported it into Edit Page
NO VERSIONING AVAILABLE
Repeat the same BUT in the first step, instead to create a custom macro by fusion composition, just import ANY standard stuff. I just imported a text+ from Effects > Title
Then do all the same things
- open it into Fusion
- Add whatever stuff you want. I added a Text node
- Added versions
- Exported (saved) the macro in Title
- Imported it into Edit Page
VERSIONING -- IS NOW -- AVAILABLE
I did compare the 2 .setting files
i discovered that in the "custom one" the line code after each
where starting with the name of the block
in my custom macro case:
Ma changing it into
Is that normal? No it isn't. It should be automatically correctly setup when exported.
Guys I do hope in the version 19.0.0 you fix these bugs because are really a pain in the a***s
Create a custom macro by
- on Edit Page import a fusion composition
- open it into Fusion
- Add whatever stuff you want. I added a Text node
- Added versions
- Exported (saved) the macro in Title
- Imported it into Edit Page
NO VERSIONING AVAILABLE
Repeat the same BUT in the first step, instead to create a custom macro by fusion composition, just import ANY standard stuff. I just imported a text+ from Effects > Title
Then do all the same things
- open it into Fusion
- Add whatever stuff you want. I added a Text node
- Added versions
- Exported (saved) the macro in Title
- Imported it into Edit Page
VERSIONING -- IS NOW -- AVAILABLE
I did compare the 2 .setting files
i discovered that in the "custom one" the line code after each
- Code: Select all
Tools = ordered() {
where starting with the name of the block
in my custom macro case:
- Code: Select all
Text1 =
Ma changing it into
- Code: Select all
Template =
Is that normal? No it isn't. It should be automatically correctly setup when exported.
Guys I do hope in the version 19.0.0 you fix these bugs because are really a pain in the a***s
Bart
________
DaVinci Resolve Studio 18.6.6 on Windows 11 Pro 23H2
Prod. Machine: Ryzen 7 64GB 3.54 GHz
Video: MSI GeForce 4060Ti 16GB
Monitors: 1 x 3840x1440 widescreen, 2 x 1920 x 1080 16:9
Audio: Behringer UMC1820
Blackmagic Speed Editor
________
DaVinci Resolve Studio 18.6.6 on Windows 11 Pro 23H2
Prod. Machine: Ryzen 7 64GB 3.54 GHz
Video: MSI GeForce 4060Ti 16GB
Monitors: 1 x 3840x1440 widescreen, 2 x 1920 x 1080 16:9
Audio: Behringer UMC1820
Blackmagic Speed Editor