Then, you can add the ffmpeg filter to that command line between the input and output filenames like -vf lut3d="name_of_lut_file". Then, use View > Application Log and go to the end to see the command line it generated. As for the command line, you can make some experimental transcodes in Shotcut that uses ffmpeg in the background by choosing Properties > Convert on any video. I suggest to use ffmpeg (which Shotcut includes) and its lut3d filter for that. You will need to transcode footage, and you can apply a LUT while doing that. However, I can tell you that Shotcut will accept most common video color spaces such as Rec. I do not have experience working with camera log video. It may, initially, be difficult for our studio to work in Shotcut, but we’d like to make the switch. We want to put our energies into supporting an open-source solution. The reason is that it has become clear that the manufacturing-ethics and politics of these two companies are no longer aligned with our studio’s values. You may well ask why we are quitting DaVinci Resolve / Apple FCPX etc in a professional post-production environment. Would we have to do a primary-grade of the S-Log3 footage in non-open-source software before transcoding, or can Shotcut plausibly grade an S-Log3 gamma-curve when transcoded? This, assuming that we can first transcode our footage into something Shotcut can ingest. My question is this: What workflow does the community suggest in order to retain the maximum quality from S-Log3 footage, and then to edit this footage in Shotcut? The solution is, presumably, to transcode. We will be shooting Sony S-Log3 XAVC footage which, apparently, Shotcut (ffmpeg) does not natively support. I am a major feature-filmmaker (remaining anonymous) interested in making the switch to open-source software ( Shotcut) for my next project.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |