![]() When migrating a project with proxies conditional to bit-depth, the existing (variable bit depth) proxies are used. Restoring a Project: When restoring a project archive with variable bit-depth proxies, proxies are regenerated at the bit depth of the original media. ![]() ![]() Migrating a Project: When migrating a project with variable bit-depth proxies, the existing (variable bit depth) proxies are used.Restoring a Project: When restoring a project archive with fixed width proxies, proxies are regenerated at 1:2 resolution.Supported proxies can be generated in the new project. To workaround this limitation, you can create a new project in Flame 2016 and wire your media from the old project to the new. This is because unsupported proxies have already been generated for that project. When migrating a project with fixed width proxies, the migration is aborted. In each case, a message detailing the application's behaviour is displayed, and you are prompted to confirm. The following scenarios apply if you migrate or restore a pre-2016 project which uses: fixed width, variable bit-depth proxies, proxies conditional to bit-depth, a non-standard proxy size, or a combination of these.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |