Exporting Quicktime .mov without video always results in a 29,97 DF timecode stream

[Smushkan]

When exporting a Quicktime .mov file with video disabled (so audio only), the embedded timecode track is always 29,97 DF regardless of sequence framerate settings.

Steps to reproduce:

1. Create a multichannel sequence at any framerate other than 29.97, so for example 25fps
2. Export to Quicktime with the 'video' option disabled
3. The resulting file will have 29,97 DF timecode rather than 25fps as expected

[Sumeet Kumar Choubey]

Hi there,

Sorry about the poor experience. I am unable to repro this at my end. Would you mind sharing a detailed screenshot of the export settings that you have used? Let us know the version of Premiere Pro & the OS that you are using. It will help us diagnose the issue properly.

Thanks,

Sumeet

[Smushkan]

Ah, sorry, knew I was forgetting something!

I'm on Windows 11 23H3, Premiere is version 25.1.0.

I am able to reproduce this issue when using an 8-channel 25fps 1080p progressive sequence with the following export settings:

All other settings are default other than bit depth, and the discrete 8-channel multichannel configuration.

the resulting exported file has a TSC metadata tag of 2997, and a 29,97 timecode stream according to Media Info, and also Premiere if the file is reimported:

Please also find here a download for the project file and exported file I used to replicate the bug:

https://drive.google.com/file/d/1HDu1e1nNCKajR5dRhXZFC_DF2weafA4h/view?usp=sharing

Exporting the file with video results in a 25fps TSC tag and timecode stream as expected.

[MyerPj]

So, it looks like a video file? .mov and mediainfo seems to say it's a video file?

Maybe put a  25fps black video (generated) over the top and export it that way?

You can use https://www.shutterencoder.com/en/ to extract the audio or video from a clip.

[Smushkan]

I'm trying to create a Quicktime .mov file with 8 channel discrete mono audio, a 25fps timecode stream, and no video stream. The media info readout and QuickTime sample is what I get when I try to create that using Premiere - the timecode and framerate metadata is incorrect.

Appreciate that's a bit weird but trying to help someone out who have received that as a delivery requirement from their client.

[R Neil Haugen]

I've heard some weird deliverables specs over the years, but that one is right up there  ... wow.

Some clients  ... lol

[Stan Jones]

@Smushkan,

I get your results in your sample, in a 2 minute extended sample, and when I changed the export to prores, turned off match source and set to 25fps, and then turned off video.

If I import it to PR and drag to the new icon, I get a 29.97 sequence (that is a little too short).

If I create a 25fps sequence and add the export, it is correct.

As @MyerPj says, I'd look for a workaround. I wonder if the file metadata can be edited. I've used exiftool for such things.

Stan

[Smushkan]

Thanks for the additional testing.

While I think it may be possible to edit the framerate metadata of the container (in another app,) the problem is the timecode stream is in the incorrect timebase and I don't think changing the metadata is going to affect the timebase of the timecode stream.

For the person I was helping out that wouldn't be enough - their file was being rejected automatically by QC software due to the incorrect timecode.

The workaround I came up with for the person I was helping was to export *with* video so the timecode was correct, then using FFmpeg to remux into a new Quicktime via:

ffmpeg -i "input.mov" -map 0 -vn "out.mov"

Though I haven't had confirmation from them that the workaround passes QC yet.

[Julien330288476mta]

Hello everyone,

I'm the guy Smushkan is trying to help, thanks a lot by the way.

we tried all we can to meet the requirements but we've never been able to.

at best, with ffmpeg, we've been able to force 25fps, start time 09:59:59:00 (which wasn't kept in the premier export ! It was reset to 00:00:00:00). But we've never been able to keep the discrete channel into the metadata.

Project is aimed for HBO

Client fixed it by using their MAM.

thanks again

[Stan Jones]

@Smushkan @Julien330288476mta,

Thanks to both of you for reporting back and sharing your real-world issues and workaround.

> the problem is the timecode stream is in the incorrect timebase

My curiosity (satisfaction of which is beyond my skills and available time!) is whether the audio streams themselves are set to the timecode or just to their sample rate. Mediainfo showed all the streams as the correct duration.

No matter; I'm sure you're right that the target system needs the base timecode to be reflected correctly.

Stan

[MyerPj]

Yes, an odd problem. I did try a few things on Shutter Encoder, but I wasn't able to get what seemed you we looking for. Glad you got it resolved. Cheers! 🙂

https://www.shutterencoder.com/en/