Since Kyno doesn't support the HLG, I can't test an external ProRes transcoding (don't have EditReady). If you choose "rec_2020HLG" manually, it's the same as none. You can change the appearance dramatically by going to >inspector >info >settings >override color space. Because being HLG, FCP does not apply a V-Log LUT. Well, those are MOVs ("H.264 Level 10") of which QT player X says: unsupported file type, unable to play video. 10-bit H.264 or HEVC from the G5 needs to be optimized in FCP. Looks like FCP is automatically applying VLog. EditReady doesn’t transcode unless you want it to. It is vastly faster to import and takes much less disk space.ĪVCHD doesn’t use a proprietary codec. However if you will be dealing with more AVCHD content in the future, I suggest you re-wrap that with EdityReady then import with "leave files in place". If you have plenty of disk space, and don't mind waiting to create optimized media for your already-imported MTS files, then it would probably work to select all the MTS files in your library, right-click and select Transcode>Create Optimized Media. This includes the ability to properly import them with "leave files in place". MTS files in a compatible wrapper so FCPX can properly handle those. It does not take six times the original space like ProRes does, and does not take long periods to transcode - like creating ProRes optimized media does. If used to re-wrap AVCHD, EditReady does not convert this to ProRes. I wonder, at this point instead of converting in mores 422 files with edit ready I should do as before, ie with final cut pro x tick the "create optimize media" option and let it come also copied to the library, although I will have many GB in the end no matter since I use a 1Tb HD. However AVCHD is only 1080 resolution and normally 1080p is not that difficult but lack of Quick Sync due to using a Hackintosh could be an additional slowdown factor. Thus the on-chip GPU must normally be disabled in the BIOS which also disables Quick Sync.ĪVCHD is a form of H264 and without Quick Sync all encode/decode must be done in software. This is because Hackintoshes can normally not switch dynamically from the on-chip GPU (where Quick Sync is implemented) to the external GPU. (2) You are using a Hackintosh which usually do not have Quick Sync capability - regardless of CPU. The performance issue scales upward with library size so with small libraries it might not be noticed but with increasing size it rapidly becomes apparent. If all you have left are the bare MTS files I'd suggest re-wrapping them externally before import using EditReady: If you have already imported bare MTS files with "leave files in place" those must be removed and properly re-imported, otherwise it will always be slow, even if the MTS files are only a small % of the overall content. Usually performance is good when using that method, although it takes more space due to the file copy. When importing that way, it will not allow "leave files in place" but will copy and re-wrap (not transcode) those those files to the library. (1) If you are dealing with bare MTS files, IOW files which have been removed from the AVCHD package and imported with "leave files in place", that may cause severe performance problems due to how FCPX handles the I/O.ĪVCHD material should *always* be imported from the folder tree, in which case you normally don't see the bare. Can you work on projects with native AVCHD MTS files to create 1-hour videos without converting to pro-res?.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |