Changes between Version 2 and Version 3 of Ticket #6718, comment 10


Ignore:
Timestamp:
Nov 2, 2017, 6:00:43 AM (9 years ago)
Author:
ttdww

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #6718, comment 10

    v2 v3  
    33I only know that when a program (in this case FFmpeg) writes a Quicktime file from a string of 32bit images (.EXR, .TGA, or .PNG in this case), the alpha channel in the input image string may be labeled or unlabeled (as to how to use the alpha) and then can be labeled or set to unlabeled when a Quicktime file is written.  There needs to be an option when writing the QT file (in this case a 32bit PNG) to leave the alpha 'unlabeled'.  Currently FFmpeg sets the alpha in the QT file to 'straight' which many companies don't use when compositing for movies, games, TV, etc - or at least they need it to be 'unlabeled'.
    44
    5 The problem is that when a company like ours supplies them with hundreds of QT files, after they import of the first QT file, as long as the alpha is unlabeled they can choose the method they want: 'ignore alpha, straight, or premultiplied'.  Then the rest of the QT files will grab that default as they import.  If the alpha is already labeled (in the case of how FFmpeg currently writes them, it forces it to 'straight'), then the client will have to manually set each and every QT file to their preference, hence making the QT files not very usable.
     5The problem is that when a company like ours supplies them with hundreds of QT files, after the import of the first QT file, as long as the alpha is unlabeled they can choose the method they want: 'ignore alpha, straight, or premultiplied'.  Then the rest of the QT files will grab that default as they import.  If the alpha is already labeled (in the case of how FFmpeg currently writes them, it forces it to 'straight'), then the client will have to manually set each and every QT file to their preference, hence making the QT files not very usable.
    66
    77Thanks again!  Sorry, hope all that makes sense.  We're really hoping to ditch After Effects command-line processing and solely use FFmpeg if we could just get this resolved.