Burnins: Refactored burnins script

[iLLiCiTiT]

Changelog Description

Refactored list value for burnins and fixed command length limit by using temp file for filters string.

Additional info

Burnin script does not print irrelevant warning about not supported subdictionary formattings (it is supported). List values can have multiple list keys in single template and can expect other keys to fill (except timecode). FFmpeg filters are not passed to cli but through temp file and using -filter_script command to the file which should fix possible limit of command length.

Testing notes:

1. Burnins should work with templates using dictionary subkeys (e.g. {project[name]})
2. Burnins should work as expected with list values (currently supported only in focal length in maya)
   • make sure one of the burnin templates has {focalLength}
   • set keys for camera focal lenght in scene
   • publish
   • validate the burnin has right focal lenght values

[LiborBatek]

It works with dictionary subkeys {project[name]} as seen in the bottom center burnin "Libor_Tests"
but When adding those burnins for focalLength it gets too many decimals/digits. and when trying to limit those via OP Burnins settings focalLength:2f it gets N/A mm in the burnins.

Not sure if somehow connected to this PR but I guess yes when in the testing steps...

[iLLiCiTiT]

When adding those burnins for focalLength it gets too many decimals/digits. and when trying to limit those via OP Burnins settings focalLength:2f it gets N/A mm in the burnins.

Should be resolved

[64qam]

Looks good in Nuke

[LiborBatek]

The focalLength values differ from maya scene.

For example on frame #1046 instead being 120.11mm it is 122.64mm

The same is valid for startframe and endframe. Values being off.

[iLLiCiTiT]

The focalLength values differ from maya scene.

Not an issue of this PR. Only if it does work in develop...

[BigRoy]

That does sound like an issue of this PR since it's likely due to a time/frame mismatch of the data. It works fine in develop as far as I know.

[LiborBatek]

When tested in develop focal length is correct.

So its an issue within this PR and need to be addressed.

[LiborBatek]

start frame being correct

focalLength being 50

but

endframe does not match (should be 125mm)

and the same endframe in the review mov

[iLLiCiTiT]

So it was found out that there are some differences in fps, which cause that seconds are calculated wrong (24 vs 25 fps). Tried to fix it.

[LiborBatek]

Now all works as expected and
startframe and endframe values of focalLength matches with maya

50mm and 125mm both set correctly in burnins.