> On Feb 13, 2019, at 3:01 PM, Harvey Pikelberger wrote:
>
> BUT for some reason the time code changed. So a clip that had started at TC
> start/end of 12:31:20:13 / 12:31:42:16 converted to 12:30:35:12 / 12:30:57:15.
The 0.1% change makes me think the timecode was converted to/from drop
> On Feb 13, 2019, at 10:04 AM, Ted Park wrote:
>
> I wonder if adding -f mov to the output options, or just using mov extension
> makes it handle the timecode track?
Thanks Ted.
I'm not familiar with the -f option and didn't immediately find it in the
FFmpeg documentation
How does that
On 14-02-2019 12:27 AM, Gyan wrote:
On 13-02-2019 10:32 PM, Harvey Pikelberger wrote:
-i '/Path/To/ProRes/Source.mov' -map 0 -map -0:d -g 48 -c:v
libx264 -profile:v baseline -crf 16 -c:a aac -b:a 256k -vf
scale=1280:720 -pix_fmt yuv420p '/Path/To/Mp4/Dest.mp4'
Oops, removed the
On 13-02-2019 10:32 PM, Harvey Pikelberger wrote:
I've got a bunch of 4- and 5-audio-track ProRes sources.
I want to create h.264/mp4 proxies of each, matching the source audio assigns
The FFmpeg code I'm using is tripping up over time code and codec issues.
Here's the code:
-i
> On Feb 13, 2019, at 12:02 PM, Harvey Pikelberger wrote:
>
> [mp4 @ 0x7fe633006000] You requested a copy of the original timecode track so
> timecode metadata are now ignored
> [mp4 @ 0x7fe633006000] Could not find tag for codec none in stream #2, codec
> not currently supported in container
I've got a bunch of 4- and 5-audio-track ProRes sources.
I want to create h.264/mp4 proxies of each, matching the source audio assigns
The FFmpeg code I'm using is tripping up over time code and codec issues.
Here's the code:
-i '/Path/To/ProRes/Source.mov' -map 0 -g 48 -c:v libx264 -profile:v
