TOPIC:

I have a workflow where I need to transcode many files to H265 but need to keep the original file timecode of each one, the only way I found to do so is exporting straight from Final Cut mas master in ProRes or H264, FC doesnt have the H265 option unless I set a preset from Compressor, but them the timecode is OK displayed in the Compressor windows, but the file transcoded has a zero timecode.

I dont know what to do...

Do your original files actually have a timecode track in them? You could use MediaInfo or Invisor to look at the specs. of the original files.

You might want to check out EditReady, which can batch transcode files to H.265/HEVC. You might want to also look at QTCHANGE.

 hedge.video/editready/benefits

 www.videotoolshed.com/product/qtchange/

Hi Dave, thanks for your prompt response. I asume the clips have timecode as FCPX shows it, and sharing/rendering/exporting/transcoding it as ProRes master from FCPX also keeps the TC. But I cant export it to H265 as FCPX doesnt show that option ...
I tried exporting a XML from Mediainfo and rewrap it with EditReady but I couldnt find the right way, I'm missing something or it doesnt work as I imagine....

So I have edited the clip in FCPX so I need to transcode from them and there are a ot, so batch exporting with Compressor will be optimal, but I dont care in the last scenario going one by one from FCPX as long as I could export them to H265.

Compressor also shows the right TC but it dont keep it either ProRess or H265

cocoua wrote:

I need to transcode many files to H265 but need to keep the original file timecode of each one...

In Compressor create a Quicktime preset and set the codec to H.265. Send the entire batch of clips from FCP to Compressor and apply that preset. It should export H265 and also preserve the file timecode. Test it on a few clips before you do the entire batch.

In the Compressor video inspector (right panel), you can also select output resolution, bit rate, bit depth and chroma sub-sampling.

Hi Joema, that's what I'm doing but as you can see in the screenshots, the TC is shown, but it isn't in the transcoded files.

Only way to do that is straight from FCPX to ProRes or H264 in the default "export file", as soon as I add any other preset, the TC isnt included

cocoua wrote:

Hi Joema, that's what I'm doing but as you can see in the screenshots, the TC is shown, but it isn't in the transcoded files.

Only way to do that is straight from FCPX to ProRes or H264 in the default "export file", as soon as I add any other preset, the TC isnt included

What camera and codec are these files from? Can you upload me a sample file? You can drop it on this secure write-only location: www.dropbox.com/request/CiqDfFZwqO9GcHCvsifF

I've uploaded 2 formats we use, one is from Mavis.app (iPhone) and the other is a rewrapped Mp4 from sony A6600.

both shows daytime TC either in FCPX, Compressor or Mediainfo.

But only way to transcode a file with it is trough FCPX master file (Prores and H264)

Try making a duplicate of the H264 proxy format in Compressor. Change the size to Automatic and codec to HEVC. That should pass through the timecode.

Basically, what you want to do is choose a format (setting) in Compressor that is "QuickTime" (it will preserve the timecode — QuickTime-based settings should show a file extension of ".mov").

Tom's suggestion of using one of the Proxy presets will work. I just recorded a clip with the Mavis app (with timecode turned on) and the half size HEVC Proxy preset in Compressor does pass through the timecode to the ouput file. You just need to go into the Video tab and change the frame size to "Automatic" (as Tom suggests). You can change other encoder settings there, as well.

If you need to process a bunch of files, what you should probably do is create a new preset in Compressor, which will make it easier to apply to a bunch of files at once. Joe suggested this in a previous post.

In the main Compressor window, click the "+" icon at the lower left corner and choose "New Setting...". In the resulting dialog window, choose QuickTime movie for the Format and provide a descriptive Name, plus any description, and click OK. You can then go through the settings in the Inspector and make appropriate changes.

A bit easier approach would be to right-click on the "HEVC Proxy half size" setting under the Proxy category in the left sidebar and choose "Duplicate". Rename the new setting as you wish and make the changes mentioned above.

cocoua wrote:

I've uploaded 2 formats we use, one is from Mavis.app (iPhone) and the other is a rewrapped Mp4 from sony A6600.

both shows daytime TC either in FCPX, Compressor or Mediainfo.

But only way to transcode a file with it is trough FCPX master file (Prores and H264)

This is the procedure I recommended above. I tested it on your files and it works OK. On the graphic I forgot to add a step to press the "Start Batch" button in Compressor, but that should be obvious.
joema.smugmug.com/FCP-Batch-Export-HEVC-...n-SfSFfw/i-xC3xbGC/A

❤︎ thank you all so much for your time and help ❤︎

All this suggestion works with some of the clips, but not for all. weird...

I was doing this test with the 2 shorter clips of the 12 I'm working with, and I found out those clips dont pass the TC to compressor (well, they do, but nto in the transcoded file, what is even more weird), and there are 2 other clips that dont do that, I dont know why because is same camera and specs, but they do though FCPX to h264/prores.

so clips 1,4,5 and 9 have this problem, the way I could solve it in order to to pass the TC to Compressor is creating a new project for each of this clips and copy paste the TC in the dialog. So the transcoded projects of clips 1,4,5 and 9 now have the TC in H265.

The big problem with this method is 120fps clips are forced to be 60 fps as FCPX doesn't have option beyond 60fps, so I had to slow time x2 in order to keep all the frames, so in next step the editor can do slow motion or normal speed as he will.

❤︎ thank you all so much for your time and help ❤︎

All this suggestion works with some of the clips, but not for all. weird...

I was doing this test with the 2 shorter clips of the 12 I'm working with, and I found out those clips dont pass the TC to compressor (well, they do, but nto in the transcoded file, what is even more weird), and there are 2 other clips that dont do that, I dont know why because is same camera and specs, but they do though FCPX to h264/prores.

so clips 1,4,5 and 9 have this problem, the way I could solve it in order to to pass the TC to Compressor is creating a new project for each of this clips and copy paste the TC in the dialog. So the transcoded projects of clips 1,4,5 and 9 now have the TC in H265.

The big problem with this method is 120fps clips are forced to be 60 fps as FCPX doesn't have option beyond 60fps, so I had to slow time x2 in order to keep all the frames, so in next step the editor can do slow motion or normal speed as he will.

cocoua wrote:

...I was doing this test with the 2 shorter clips of the 12 I'm working with, and I found out those clips dont pass the TC to compressor (well, they do, but nto in the transcoded file, what is even more weird), and there are 2 other clips that dont do that, I dont know why because is same camera and specs, but they do though FCPX to h264/prores...

Upload to me a couple of the problem clips and I will examine them. Also state where each clip came from. Is each a camera file with no changes or has it been modified or transcoded in some way? If so, how?

Each time a clip is modified or transcoded by some other utility, there is a chance that utility did not handle timecode correctly and the result file no longer has accessible file timecode.

thanks Joema for your further interest, files are several GB and I think is not worth invest more time in this, the TC is there, Compressor shows it in the window, but it doesnt transcode the file with it for any reason.
Files are recorded consecutively and no other app has been involved, sent by Airdrop with "include all data" ON.

Given the high ratio of random problems cameras and clips create, I think beyond this point I just need to check TC after transcoding, and when the problem shows again, then just make a new project with modified TC and transcode again, this seems to work.

Understood. Some things that might help if further investigation is needed: The 3rd-party tool Invisor can inspect and compare metadata on video files and show clips which have timecode in Quicktime format. See attached.
Invisor: apps.apple.com/us/app/invisor-media-file...or/id442947586?mt=12

The 3rd-party tool QTChange can fix timecode in various situations. E.g, for a Sony A7SIII XAVC-S, XAVC-I or XAVC-HS clip, it can read the Sony timecode and rewrite the metadata in Quicktime format so that FCP or Compressor can read it. If the original Sony timecode is wrong, and if you know what starting timecode is needed, QTChange can rewrite the timecode based on the starting value you supply. It is inexpensive but a professional tool and assumes you know what you're doing. It's good to always have backups.

QTChange: www.videotoolshed.com/handcrafted-timecode-tools/qtchange/

If you've got a few minutes to spare, one more thing you could try is the Compressor droplet linked below. You could download, unzip, and try it out with one of your "problem" files.

H.265 QuickTime Movie.app.zip

(And, then, let us know if the resulting file has timecode.)

HI!

well I found out the problem, FCPX show 120fps clips as 60fps in info panel. So I thought all videos were 60 fps, BUT the 4 didnt got the TC are 120fps!

So Compressor shows TC for 120fps clips but it doesnt transcode it.

FCPX, even if it doesnt shows 120fps in the info panel, can transcode files to 120fps AND TC if you do it trough Proress or H264 (H265 also would work since 60fps clips get TC, but for any reason, FCPX doesnt give you that option native, and as soon you add ANY other preset, no matter which one, this wont get the TC)

This super mess comes because FCPX lacks for real support beyond 60fps (120, 240... nah).

Something I cant understand, since the cornerstone of Apple's ecosystem is the iPhone and they put so much effort in the video aspect. iPhone supports 240fps, but Apple's Pro solution for video editing lacks real support yet in 2023...

cocoua wrote:

HI!

well I found out the problem, FCPX show 120fps clips as 60fps in info panel. So I thought all videos were 60 fps, BUT the 4 didnt got the TC are 120fps!

So Compressor shows TC for 120fps clips but it doesnt transcode it.

Okay, I shot some sample clips on my iPhone. It shoots 120 FPS clips in either H.264 or HEVC format. It shoots 240 FPS clips in HEVC only.

If I use the Mavis app, it adds timecode to all clips I recorded. I shot both formats at 120 FPS and HEVC at 240 FPS. The iPhone's built-in Camera app doesn't add timecode.

So, if things are shot in HEVC, no transcoding is needed and the clips/files all have timecode.

Using Compressor on the H.264 clip (120 FPS) (via my Droplet), the resulting HEVC clip/file has timecode.

cocoua wrote:

FCPX, even if it doesnt shows 120fps in the info panel, can transcode files to 120fps AND TC if you do it trough Proress or H264 (H265 also would work since 60fps clips get TC, but for any reason, FCPX doesnt give you that option native, and as soon you add ANY other preset, no matter which one, this wont get the TC)

This super mess comes because FCPX lacks for real support beyond 60fps (120, 240... nah).

Something I cant understand, since the cornerstone of Apple's ecosystem is the iPhone and they put so much effort in the video aspect. iPhone supports 240fps, but Apple's Pro solution for video editing lacks real support yet in 2023...

Actually, I imported the 120 FPS clip that was shot in H.264 and transcoded to HEVC with the Compressor Droplet into FCP. Timecode is there and in the Inspector the file info shows 120 FPS.

FCP does support these higher frame rate clips. You must be missing something, etc. Criticizing FCP or Apple for your lack of understanding is not helpful (especially since it isn't warranted in this case). And, if you would have answered early questions in the thread and been more concise with the issue, as well as following suggestions and clearly reporting back, this could have been easily resolved a few days ago.

Mmm, sure I must be missing something! I'm on FCPX 10.6.5 and I cant choose new project at 120fps
I'm checking this with either 120fps Mavis and A6600 120fps clips. This is the only option I get:
60 is the maximum, I'm trying to find more about this in Google but I can't find how to add 120fps...

And I still get 60fps for 120 fps A6600 clips, Mediainfo and Quicktime X shows 120fps, but FCPX keep showing 60fps. I'm sharing you the files, one imported to library straight from the SD, the MP4 rewrapped with Editready (so both keep the TC, as FCPX dont get the TC from MP4) and  the orignal from the SD with the XML from the camera.

I'm adding the Mediainfo xml with the 119,880 frame rate info and a screenshot of my FCPX with one of the 3 clips opened.

The problem then could be with 120fps clips from the A6600 + Timecode as MP4 does not officially support TC (but somehow Sony adds it...) (60fps or less works great)

https://we.tl/t-JzWOuXXR5D

Okay, cool, thanks for the additional info.

FYI, there isn't any current "delivery" standard for video that has a higher frame rate than 60 FPS. That's why it isn't an option in FCP. If you look at the Inspector file info for the imported clip (not the timeline/Project), it should show 120 FPS, or whatever the framerate is in the original file.

There is no reason to use FCP if you are trying to batch transcode camera files to HEVC. It's a very inefficient way to do so.

Okay, thanks for providing the link to the archive.

If I drag and drop "C0081.MP4" from the folder "ORIGINAL FILE from SD" onto EditReady's main window and choose the "H.265 (HEVC) Output preset, then "Convert All", EditReady produces an HEVC file with timecode, the same as in the original.

If you use Compressor it doesn't keep the original timecode. EditReady uses the non-standard Sony timecode from the source file.

So, it seems that the best bet might be to use EditReady to transcode whatever isn't already HEVC into HEVC. If you want to tweak the HEVC encoding settings, you can edit the "Additional Options" and turn on the Framerate Adjustment or the Encoder Advanced Options, for example.

Hope this helps.