![]() ![]() I know I am probably rambling now but I hope this helps. However as I said, it has no correlation to the FCP XML because one uses pixels and the other uses a screen ratio. This will show you the pixel value matching what was entered in the text editor. To discuss the offset in the actual text setup file, you need to look for the Channel Translation. This new value in the XML gave me the correct colour but in a 16 bit colour space as opposed to FCP 8-bit. To fix this, I multiplied the 8-bit colour value by 16. At launch, new licenses were priced from US129,000 excluding hardware, with upgrades from existing Flame licenses priced from US10,000. But Smoke/Flame defaults to 16-bit colour so the mapped value from the XML gives you the wrong colour in Smoke/Flame. Autodesk Flame Premium - Creative Grading & Visual Effects - CinePostproduction - 'In Darkness' Autodesk Video. In September 2010, Autodesk introduced Flame Premium 2011, a single license for running Flame, Smoke Advanced and Lustre together on a single workstation. So any colours are represented between 0 and 256. However FCP 7 has always worked on an 8-bit colour platform. When I looked at the colour values, there was actually something there. In terms of colour, I found that my text always came in black in Flame or Smoke. Bear in mind that each text set up may be different but keep an eye on this. So I set my leading value to 15 and that matched the auto-leading in FCP. I don't know why but it matched up.Īlso, if you use AUTO-KERN/LEADING in FCP, they will not come across into Smoke/Flame because it is just an auto switch in the XML and not an actual value. I found that ARIAL 18 in FCP is matched to ARIAL 50 in Smoke. What's New in Flame 2023 Release Notes Flame Family 2023 UI Overview Projects and Users Organizing Media in the Workspace Importing and Exporting Media Create HDR Content Playing Back Media Editing Clips and Sequences Audio Rendering Timeline FX and Transitions Batch Action Tools Tab Workflow Chroma Keying and Working. When I import this into Smoke/Flame, it is almost identical but I adjusted the origin to 0.35 and it lined up correctly.Īs mentioned earlier, the font sizes are interpreted differently. So a lower third alignment is represented as 0.33333. This is displayed in a ratio rather than an actual pixel value. The positioning of the text in the XML is based on the origin parameter. So I am assuming the behaviour will be the same. The XML importer should be the same in concurrent versions of Smoke and Flame.Ĭurrent Flame is 2015 EXT 1 and Smoke is 2015 SP1 … So I suspect there are some improvements in the extension but it should not impact on this workflow.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |