Resolve BLG clone

[finnjaeger]

@finnjaeger

… file and thats it.tracked/animated masks are aligned to the first frame, so timeline IN in resolve and flame have to matchbetter workflow would be a sources-sequence thats graded and then we apply the DRX/OFX in batch for each comp, or apply in sources sequence and hardcommit? this is a fun one as it has no relationship to the source TC (idk if OFX can) .Can you change OFX parameters using python?

check this

[philm]

When we developed the tool at Company3 there was no understanding on the part of BlackMagic of temporal or spatial correlation.
I quit before the project was complete.

[ALan]

Do you have to export a DRX from Resolve, and re-load that file in the Flame OFX everytime a change is made?

[finnjaeger]

not 100% sure but i think it soft links against a .drx so you can overwrite … but not 100% certain

[ALan]

I think that is where the BLG paradigm is better. I believe it is a “live” link to the Baselight database.

[finnjaeger]

yes absolutely.

Also i dont really understand why they didnt somehow launch a full resolve in the background so thay it could render anything … and there was some link between clips

but then probably @philm knows that

[philm]

The initial conversations were what I told you about at dinner:
Local work regardless of location, send the setup data to the base of operations, render on a farm.
That way the artist could grade in hawaii and the job would be ready in LA in a very short space of time.

At that point in time there was a large nuke renderfarm.
At that point in time there was an absence of a reliable nuke renderfarm controller.

At that point in time there was a 999,999 license for burn per day.

Many decisions were made before my involvement.
I just mentioned that we could probably spin up a virtual burn farm and do the job a little faster and cheaper than an enormous CPU farm (not to mention spawning frames and distributing those over whatever network).
At that time there was no such thing as an internet burn farm.
A few months after we started development on this OFX tool, flame on AWS actually became a supported product. (I had no involvement in that initiative)

The decision to not launch resolve is that free resolve is resolution crippled, whereas burn was limited to 16,384 x 16,384 and we had a lot of burn licenses.

Spatial and temporal correlation was hard in the drx file.
Getting a dialog box and a file chooser took a while.
(Having scratched away at python for a while now, i have a different appreciation of that)

Timewarps were not even in the conversation.
Also
this was two and a half years ago.

[finnjaeger]

interesting with the resolution max looking at free resolve as the ofx requires a studio license regardless