- Posts: 150
- Thank you received: 2
3 Post Moderation Rule for New Boarders (25 Jan 2021)
New boarders will have their posts moderated - Don't worry if you cannot see your post immediately.
Create optimiza media,agrees or not?
Can you work on projects with native AVCHD MTS files to create 1-hour videos without converting to pro-res?
or your pc struggling and making effort with shots and the non-fluid timeline you have to convert to 422 pro?
thanks to those who will answer me, and happy new year 2018 to all of you.
:woohoo:
Please Log in to join the conversation.
- Tom Wolsky
-
- Offline
- Moderator
-
Please Log in to join the conversation.
while in prores no problem everything runs smoothly but I create flie with many gb, so I ask you to know if you happen to the same thing.
otherwise what should I take a pc with I7 6 cores?
thank you
Please Log in to join the conversation.
- Tom Wolsky
-
- Offline
- Moderator
-
Why on earth are you doing that? If you import AVCHD correctly from the camera card or an archive, the files are rewrapped to QuickTime and work perfectly well.
Please Log in to join the conversation.
Please Log in to join the conversation.
I unload the SDHC card on the PC and then with I take the mts files in the avchd / BDMW / Stream folder and the amount with fcpx.
:blink:
Please Log in to join the conversation.
- Tom Wolsky
-
- Offline
- Moderator
-
Please Log in to join the conversation.
do not give me of you we are in forum of friends and therefore let's give of you I say well?
thanks and just finished my test with the method described by you I will let you know how it went.
Please Log in to join the conversation.
click wrote: ....Can you work on projects with native AVCHD MTS files to create 1-hour videos without converting to pro-res?...
You have two possible problems:
(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.
AVCHD material should *always* be imported from the folder tree, in which case you normally don't see the bare .MTS files. 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. Usually performance is good when using that method, although it takes more space due to the file copy.
If all you have left are the bare MTS files I'd suggest re-wrapping them externally before import using EditReady: www.divergentmedia.com/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. 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.
(2) You are using a Hackintosh which usually do not have Quick Sync capability -- regardless of CPU. This is because Hackintoshes can normally not switch dynamically from the on-chip GPU (where Quick Sync is implemented) to the external GPU. Thus the on-chip GPU must normally be disabled in the BIOS which also disables Quick Sync.
AVCHD is a form of H264 and without Quick Sync all encode/decode must be done in software. 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.
Please Log in to join the conversation.
what do you say?
thanks again and good 2018 from an Italian.
Please Log in to join the conversation.
click wrote: ... 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....
If used to re-wrap AVCHD, EditReady does not convert this to ProRes. 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. It simply puts the existing .MTS files in a compatible wrapper so FCPX can properly handle those. This includes the ability to properly import them 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.
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". It is vastly faster to import and takes much less disk space.
Please Log in to join the conversation.
I took edit ready today since the cost is not high, but I open it and ask me in what format to convert, what should I set?
Thanks again
Please Log in to join the conversation.
in this way I have the lighter files of the 422 prores but the quality of the image is the same, right?
thank you
Please Log in to join the conversation.
do clips made with edit rerady in rewrap have the same quality as the original MTS clips?
thank you
Please Log in to join the conversation.
click wrote: I tried to use edit ready and I must say that it works well, but a single doubt assails me!
do clips made with edit rerady in rewrap have the same quality as the original MTS clips?
If by "native MTS clips" you mean naked clips, isolated from the original card structure: the correctly rewrapped clips - from card! - have much better quality! In theory, rewrapped originals also have better quality than ProRes copies, because ProRes is visually lossless but a copy nonetheless.
In the real world, there is indeed a chance that by using EditReady (or any other third-party-app) to transcode clips to ProRes for editing you seriously damage your footage. Camera manufacturers implement important metadata within their proprietary codecs, and when an app decodes the underlying Mpeg4 this doesn't mean that those data are respected. At least you should compare the externally encoded ProRes clips to the originals in FCP. Any idea what's going on here:
???
Please Log in to join the conversation.
- Tom Wolsky
-
- Offline
- Moderator
-
Please Log in to join the conversation.
thank you all for helping me
:lol:
Please Log in to join the conversation.
Tom Wolsky wrote: AVCHD doesn’t use a proprietary codec. EditReady doesn’t transcode unless you want it to. Looks like FCP is automatically applying VLog. 10-bit H.264 or HEVC from the G5 needs to be optimized in FCP.
Well, those are MOVs ("H.264 Level 10") of which QT player X says: unsupported file type, unable to play video. Because being HLG, FCP does not apply a V-Log LUT. You can change the appearance dramatically by going to >inspector >info >settings >override color space. Set to "none" by default. You can manually set it to "rec_709". If you choose "rec_2020HLG" manually, it's the same as none.
Since Kyno doesn't support the HLG, I can't test an external ProRes transcoding (don't have EditReady). If I transcode GH5 or S7rii LOG clips using Kyno and look at them and the originals side by side in Browser or Timeline, I immediately see differences (no LUT, no color space conversion), I'd say slightly different gamma. If I duplicate and re-import the internally encoded Transcoded Media >High Quality Media and put them beside the originals, they appear ab-so-lutely identical.
Obviously I can't trust Kyno in encoding ProRes (or do I have to be wary about FCP???). I'd test this same thing with EditReady, just to know if there is a potential problem. My explanation ("proprietary codec" or some specific flags as to how the data are to be interpreted) may be naive or faulty. But I'm aware there is something wrong.
Please Log in to join the conversation.
- Tom Wolsky
-
- Offline
- Moderator
-
Please Log in to join the conversation.



