[FFmpeg-user] How can I burn-in the timestamp from AVCHD/MTS video?

[Jesse Gordon]

Good Day,

I got an older Sony handycam that makes 0.MTS type files. It does 
record the date and time in them, which it can optionally display during 
playback.


And ffplay also displays the correct date and time as a text overlay 
while vlc does not and youtube does not show the timestamp.


I would like to simply burn in the timestamps to each frame so the date 
and time shows on youtube.


I tried this:

ffmpeg -i 0.MTS -vf 
"drawtext=fontsize=60:fontcolor=black:text='%{pts\:gmtime}':x=(w-text_w):y=(h-text_h)" 
-acodec mp3 -y output.mp4


And that almost works, but it starts the date at "1970-01-01 00:00:00" 
and counts up.


Below is a couple of frames from ffprobe -- the first 117 output lines 
from ffprobe -show_frames 0.MTS


I know ffmpeg can do this because ffplay displays it correctly. I just 
cannot for the life of me figure out how to make it burn it into the 
frame images!


I notice that timecode is always 00:00:00:00 in the output of ffprobe:

[TIMECODE]
value=00:00:00:00
[/TIMECODE]

And in: TAG:timecode=00:00:00:00

Those fields are always the same.

Thank you very much for any ideas for me to try!

~Jesse

[SUBTITLE]
media_type=subtitle
pts=1016689
pts_time=1.016689
format=0
start_display_time=0
end_display_time=4294967295
num_rects=1
[/SUBTITLE]
[FRAME]
media_type=audio
stream_index=1
key_frame=1
pkt_pts=91502
pkt_pts_time=1.016689
pkt_dts=91502
pkt_dts_time=1.016689
best_effort_timestamp=91502
best_effort_timestamp_time=1.016689
pkt_duration=2880
pkt_duration_time=0.032000
pkt_pos=59520
pkt_size=1024
sample_fmt=fltp
nb_samples=1536
channels=2
channel_layout=stereo
[SIDE_DATA]
side_data_type=AVMatrixEncoding
[/SIDE_DATA]
[SIDE_DATA]
side_data_type=Metadata relevant to a downmix procedure
[/SIDE_DATA]
[/FRAME]
[FRAME]
media_type=video
stream_index=0
key_frame=1
pkt_pts=91502
pkt_pts_time=1.016689
pkt_dts=91501
pkt_dts_time=1.016678
best_effort_timestamp=91502
best_effort_timestamp_time=1.016689
pkt_duration=1501
pkt_duration_time=0.016678
pkt_pos=768
pkt_size=214628
width=1920
height=1080
pix_fmt=yuv420p
sample_aspect_ratio=1:1
pict_type=I
coded_picture_number=0
display_picture_number=0
interlaced_frame=0
top_field_first=0
repeat_pict=0
color_range=unknown
color_space=unknown
color_primaries=unknown
color_transfer=unknown
chroma_location=left
TAG:timecode=00:00:00:00
[SIDE_DATA]
side_data_type=H.26[45] User Data Unregistered SEI message
[/SIDE_DATA]
[SIDE_DATA]
side_data_type=H.26[45] User Data Unregistered SEI message
[/SIDE_DATA]
[SIDE_DATA]
side_data_type=H.26[45] User Data Unregistered SEI message
[/SIDE_DATA]
[SIDE_DATA]
side_data_type=SMPTE 12-1 timecode
[TIMECODE]
value=00:00:00:00
[/TIMECODE]
[/SIDE_DATA]
[/FRAME]
[FRAME]
media_type=video
stream_index=0
key_frame=0
pkt_pts=93003
pkt_pts_time=1.033367
pkt_dts=93003
pkt_dts_time=1.033367
best_effort_timestamp=93003
best_effort_timestamp_time=1.033367
pkt_duration=1501
pkt_duration_time=0.016678
pkt_pos=232320
pkt_size=30575
width=1920
height=1080
pix_fmt=yuv420p
sample_aspect_ratio=1:1
pict_type=P
coded_picture_number=1
display_picture_number=0
interlaced_frame=0
top_field_first=0
repeat_pict=0
color_range=unknown
color_space=unknown
color_primaries=unknown
color_transfer=unknown
chroma_location=left
TAG:timecode=00:00:00:00
[SIDE_DATA]
side_data_type=SMPTE 12-1 timecode
[TIMECODE]
value=00:00:00:00
[/TIMECODE]
[/SIDE_DATA]
[/FRAME]


___
ffmpeg-user mailing list
ffmpeg-user@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-user

To unsubscribe, visit link above, or email
ffmpeg-user-requ...@ffmpeg.org with subject "unsubscribe".

[FFmpeg-user] "Competitors" or do we want to stay alive?

[Andrew Randrianasulu]

Sorry for being frustrated lately.

Realities of all this "modern development" vs me tend to be not in favor of
our project.

I looked up two "other" projects in video editing.

MLT is well-known and going on for nearly two decades.

In this year release notes we see:

https://github.com/mltframework/mlt/releases


=

https://github.com/mltframework/mlt/releases/tag/v7.30.0


Added support for mlt_image_yuv420p10, mlt_image_yuv444p10, and
mlt_image_yuv422p16 in avfilter, swscale, and rescale filters.
This facilitates using these pixel formats end-to-end when using only
FFmpeg producers, certain avfilters, and avformat consumer. This means it
is possible to do 10-bit end-to-end on the CPU when being careful to select
compatible components and options to avoid conversions. One can
pass-through HDR; however, you must set the color_trc and pix_fmt
properties on the avformat consumer (see ffmpeg -h full for these values).
The avformat consumer automatically converts MLT colorspace (integer value)
to FFmpeg's colorspace and color_primaries (unless explicit) options.



I take this as "floating point pipeline still not here".

Olive branch is even more depressing:

https://github.com/olive-editor/olive/issues

Last non-CI commit was in ... september 2023?

May be developing moved somewhere, but this mean all exiting new bugs and
state of being incomplete for  few more years, given that even with most of
hard work done by OpenGL, OCIO, ffmpeg etc remaining NLE core is not that
simple, as it turned out to be.

Natron does not do audio, as far as I know, and also hanging on a thread
(single developer).

Blender is a Big Shot now, with predictably big requirements both in
software (try to build it on Slackware) and in hardware. Driven by higher
end!

And whole "Oh lol X is deprecated, everyone rewrite themselves to Wayland"
push. I bet there might be way to resistance say Intel's or Nvidia "HDR on
X" proposals in Xwayland but who will do all this work for single
application? It took Valve's money effectively to get anything at all done
in this area.

https://www.phoronix.com/news/X11-DeepColor-Visual-RFC

from 2017 

https://lists.freedesktop.org/archives/wayland-devel/2017-December/036403.html

It took whole 8 years to get into "usable in mpv" state, and producing
video usually have higher demands than playing back.

I am fairly sure someone will write something in Rust (so it will break in
6 months time because Rust is for Big D Developers who have no problems
with such churn) or c++ 25 because c+11 is too archaic and all new courses
are about $latest (double meaning of $ here).

Again, I do not think this is only individual developers fault, just more
complex issue with constant stream of *new*  hardware we supposed to fix in
field by writing software, somehow (HDR displays are all or nothing, so
HD(R), SD and GUI all must be mixed on host side). And general "culture" of
individualism (because Silicon Valley, bebe!)  and effectively social
darwinism (where are XDTV and libquicktime? killed by constant API churn
).

I see no escape from this, at larger scale. And this makes me even more
frustrated.

cc ffmpeg-user/libav user because otherwise no one from "outside" will ever
read this.
___
ffmpeg-user mailing list
ffmpeg-user@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-user

To unsubscribe, visit link above, or email
ffmpeg-user-requ...@ffmpeg.org with subject "unsubscribe".

Re: [FFmpeg-user] How can I burn-in the timestamp from AVCHD/MTS video?

[Reino Wijnsma]

Hello Jesse,

On 2025-04-04T06:15:40+0200, Jesse Gordon  wrote:
ffmpeg -i 0.MTS -vf 
"drawtext=fontsize=60:fontcolor=black:text='%{pts\:gmtime}':x=(w-text_w):y=(h-text_h)" 
-acodec mp3 -y output.mp4


And that almost works, but it starts the date at "1970-01-01 00:00:00" 
and counts up.
I think https://stackoverflow.com/a/67409424/2703456 can help you out on 
this one.


--
Reino
___
ffmpeg-user mailing list
ffmpeg-user@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-user

To unsubscribe, visit link above, or email
ffmpeg-user-requ...@ffmpeg.org with subject "unsubscribe".

Re: [FFmpeg-user] V210 to MKV transcoding issue

[Kieran O Leary]

Hi,

On Fri 4 Apr 2025 at 15:29, Sherbini, Leila  wrote:

> Hey folks!
>
> I’ve been having issues with transcoding v210 mov files into mkv using
> ffmpeg.


Are other export formats available working correctly for these same v210s
or is it just ffv1/mkv that you’re seeing the issue with?


Every time I try I get the following error:
>
> [in#0/mov,mp4,3gp,3pg2,mj2 @ 0x60b5cd00] Error during demuxing :
> Device not configured
> [[in#0/mov,mp4,3gp,3pg2,mj2 @ 0x60b5cd00] Error retrieving a packet
> from demuxer: Device not configured
> [out#0/matroska @ 0x6025c780] Error closing file: Bad file descriptor


Can you post the complete terminal output including the actual command
used? Perhaps there’s other issues further up. I’m not able to figure this
out but it looks to me like there could be an issue with the command or the
input files? Weird that it works fine on an older Mac though.

Best,

Kieran O’Leary
National Library of Ireland




>
> This is issue has been happening on an iMac with an OS of Sequoia 15.3.2
> and the same error has occurred with ffmpeg versions 7.1.1 and 6.1.2. On a
> different iMac running Mojave 10.14.6 OS and ffmpeg version 5.0 the
> transcode goes through fine.





>
>  This is the script I’m using:
>
> ffmpeg -i input_file -map 0 -dn -c:v ffv1 -level 3 -g 1 -slicecrc 1
> -slices 16 -c:a copy output_file.mkv -f framemd5 -an framemd5_output_file
>
> Any ideas as to what the issue is and how to fix it? Any insight is
> appreciated!
>
> Best,
> Leila
>
> --
> Leila Sherbini | Media Preservation Resident Librarian
> Michigan State University Libraries
> sherb...@msu.edu
> she / her / hers What’s this? >
> ___
> ffmpeg-user mailing list
> ffmpeg-user@ffmpeg.org
> https://ffmpeg.org/mailman/listinfo/ffmpeg-user
>
> To unsubscribe, visit link above, or email
> ffmpeg-user-requ...@ffmpeg.org with subject "unsubscribe".
>
___
ffmpeg-user mailing list
ffmpeg-user@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-user

To unsubscribe, visit link above, or email
ffmpeg-user-requ...@ffmpeg.org with subject "unsubscribe".

Re: [FFmpeg-user] "Competitors" or do we want to stay alive?

[Paul B Mahol]

On Fri, Apr 4, 2025 at 10:06 AM Andrew Randrianasulu <
randrianas...@gmail.com> wrote:

> Sorry for being frustrated lately.
>
> Realities of all this "modern development" vs me tend to be not in favor of
> our project.
>
> I looked up two "other" projects in video editing.
>
> MLT is well-known and going on for nearly two decades.
>
> In this year release notes we see:
>
> https://github.com/mltframework/mlt/releases
>
>
> =
>
> https://github.com/mltframework/mlt/releases/tag/v7.30.0
>
>
> Added support for mlt_image_yuv420p10, mlt_image_yuv444p10, and
> mlt_image_yuv422p16 in avfilter, swscale, and rescale filters.
> This facilitates using these pixel formats end-to-end when using only
> FFmpeg producers, certain avfilters, and avformat consumer. This means it
> is possible to do 10-bit end-to-end on the CPU when being careful to select
> compatible components and options to avoid conversions. One can
> pass-through HDR; however, you must set the color_trc and pix_fmt
> properties on the avformat consumer (see ffmpeg -h full for these values).
> The avformat consumer automatically converts MLT colorspace (integer value)
> to FFmpeg's colorspace and color_primaries (unless explicit) options.
>
> 
>
> I take this as "floating point pipeline still not here".
>
> Olive branch is even more depressing:
>
> https://github.com/olive-editor/olive/issues
>
> Last non-CI commit was in ... september 2023?
>
> May be developing moved somewhere, but this mean all exiting new bugs and
> state of being incomplete for  few more years, given that even with most of
> hard work done by OpenGL, OCIO, ffmpeg etc remaining NLE core is not that
> simple, as it turned out to be.
>
> Natron does not do audio, as far as I know, and also hanging on a thread
> (single developer).
>
> Blender is a Big Shot now, with predictably big requirements both in
> software (try to build it on Slackware) and in hardware. Driven by higher
> end!
>
> And whole "Oh lol X is deprecated, everyone rewrite themselves to Wayland"
> push. I bet there might be way to resistance say Intel's or Nvidia "HDR on
> X" proposals in Xwayland but who will do all this work for single
> application? It took Valve's money effectively to get anything at all done
> in this area.
>
> https://www.phoronix.com/news/X11-DeepColor-Visual-RFC
>
> from 2017 
>
>
> https://lists.freedesktop.org/archives/wayland-devel/2017-December/036403.html
>
> It took whole 8 years to get into "usable in mpv" state, and producing
> video usually have higher demands than playing back.
>
> I am fairly sure someone will write something in Rust (so it will break in
> 6 months time because Rust is for Big D Developers who have no problems
> with such churn) or c++ 25 because c+11 is too archaic and all new courses
> are about $latest (double meaning of $ here).
>
> Again, I do not think this is only individual developers fault, just more
> complex issue with constant stream of *new*  hardware we supposed to fix in
> field by writing software, somehow (HDR displays are all or nothing, so
> HD(R), SD and GUI all must be mixed on host side). And general "culture" of
> individualism (because Silicon Valley, bebe!)  and effectively social
> darwinism (where are XDTV and libquicktime? killed by constant API churn
> ).
>
> I see no escape from this, at larger scale. And this makes me even more
> frustrated.
>
> cc ffmpeg-user/libav user because otherwise no one from "outside" will ever
> read this.
>

I think you should use this: https://github.com/richardpl/lavfi-preview

It is fast and small, and make work done. No monthly subscriptions, no
trials, no usb dongle needed.


> ___
> ffmpeg-user mailing list
> ffmpeg-user@ffmpeg.org
> https://ffmpeg.org/mailman/listinfo/ffmpeg-user
>
> To unsubscribe, visit link above, or email
> ffmpeg-user-requ...@ffmpeg.org with subject "unsubscribe".
>
___
ffmpeg-user mailing list
ffmpeg-user@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-user

To unsubscribe, visit link above, or email
ffmpeg-user-requ...@ffmpeg.org with subject "unsubscribe".

Re: [FFmpeg-user] [Cin] "Competitors" or do we want to stay alive?

[Andrew Randrianasulu]

пт, 4 апр. 2025 г., 18:32 Phyllis Smith :

> Yes, thanks for a good summary.  I think Cinelerra has its place and still
> serves as a learning tool also..
> If the Olive NLE Matt had corroborated with CinGG, he would have been
> welcome and could have made major changes to update it instead of trying to
> write from scratch.
>

https://github.com/olive-editor/olive/issues/2383

lets see ..




>
> On Fri, Apr 4, 2025 at 4:06 AM Andrew Randrianasulu via Cin <
> c...@lists.cinelerra-gg.org> wrote:
>
>> Sorry for being frustrated lately.
>>
>> Realities of all this "modern development" vs me tend to be not in favor
>> of our project.
>>
>> I looked up two "other" projects in video editing.
>>
>> MLT is well-known and going on for nearly two decades.
>>
>> In this year release notes we see:
>>
>> https://github.com/mltframework/mlt/releases
>>
>>
>> =
>>
>> https://github.com/mltframework/mlt/releases/tag/v7.30.0
>>
>>
>> Added support for mlt_image_yuv420p10, mlt_image_yuv444p10, and
>> mlt_image_yuv422p16 in avfilter, swscale, and rescale filters.
>> This facilitates using these pixel formats end-to-end when using only
>> FFmpeg producers, certain avfilters, and avformat consumer. This means
>> it is possible to do 10-bit end-to-end on the CPU when being careful to
>> select compatible components and options to avoid conversions. One can
>> pass-through HDR; however, you must set the color_trc and pix_fmt
>> properties on the avformat consumer (see ffmpeg -h full for these
>> values). The avformat consumer automatically converts MLT colorspace
>> (integer value) to FFmpeg's colorspace and color_primaries (unless
>> explicit) options.
>>
>> 
>>
>> I take this as "floating point pipeline still not here".
>>
>> Olive branch is even more depressing:
>>
>> https://github.com/olive-editor/olive/issues
>>
>> Last non-CI commit was in ... september 2023?
>>
>> May be developing moved somewhere, but this mean all exiting new bugs and
>> state of being incomplete for  few more years, given that even with most of
>> hard work done by OpenGL, OCIO, ffmpeg etc remaining NLE core is not that
>> simple, as it turned out to be.
>>
>> Natron does not do audio, as far as I know, and also hanging on a thread
>> (single developer).
>>
>> Blender is a Big Shot now, with predictably big requirements both in
>> software (try to build it on Slackware) and in hardware. Driven by higher
>> end!
>>
>> And whole "Oh lol X is deprecated, everyone rewrite themselves to
>> Wayland"  push. I bet there might be way to resistance say Intel's or
>> Nvidia "HDR on X" proposals in Xwayland but who will do all this work for
>> single application? It took Valve's money effectively to get anything at
>> all done in this area.
>>
>> https://www.phoronix.com/news/X11-DeepColor-Visual-RFC
>>
>> from 2017 
>>
>>
>> https://lists.freedesktop.org/archives/wayland-devel/2017-December/036403.html
>>
>> It took whole 8 years to get into "usable in mpv" state, and producing
>> video usually have higher demands than playing back.
>>
>> I am fairly sure someone will write something in Rust (so it will break
>> in 6 months time because Rust is for Big D Developers who have no problems
>> with such churn) or c++ 25 because c+11 is too archaic and all new courses
>> are about $latest (double meaning of $ here).
>>
>> Again, I do not think this is only individual developers fault, just more
>> complex issue with constant stream of *new*  hardware we supposed to fix in
>> field by writing software, somehow (HDR displays are all or nothing, so
>> HD(R), SD and GUI all must be mixed on host side). And general "culture" of
>> individualism (because Silicon Valley, bebe!)  and effectively social
>> darwinism (where are XDTV and libquicktime? killed by constant API churn
>> ).
>>
>> I see no escape from this, at larger scale. And this makes me even more
>> frustrated.
>>
>> cc ffmpeg-user/libav user because otherwise no one from "outside" will
>> ever read this.
>> --
>> Cin mailing list
>> c...@lists.cinelerra-gg.org
>> https://lists.cinelerra-gg.org/mailman/listinfo/cin
>>
>
___
ffmpeg-user mailing list
ffmpeg-user@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-user

To unsubscribe, visit link above, or email
ffmpeg-user-requ...@ffmpeg.org with subject "unsubscribe".

[FFmpeg-user] Subtitle Timing: Clock Timestamps vs. Frame Timestamps

[jeremie bergeron]

Hi,

This is not strictly an FFmpeg question but rather a general video
processing question regarding when subtitles should be rendered.

In this discussion, we are debating whether subtitles should be displayed
based on *clock timestamps* or *frame timestamps (PTS)*.
Let's say I have a video with those timestamps:

   -

   Frame 0: 0 ms
   -

   Frame 1: 42 ms
   -

   Frame 2: 83 ms
   -

   Frame 3: 125 ms
   -

   Frame 4: 167 ms
   -

   Frame 5: 209 ms
   -

   Frame 6: 250 ms
   -

   Frame 7: 292 ms
   -

   Frame 8: 334 ms
   -

   Frame 9: 375 ms
   -

   Frame 10: 417 ms
   -

   Frame 11: 459 ms
   -

   Frame 12: 500 ms
   -

   Frame 13: 542 ms
   -

   Frame 14: 584 ms
   -

   Frame 15: 626 ms
   -

   Frame 16: 667 ms
   -

   Frame 17: 709 ms
   -

   Frame 18: 751 ms
   -

   Frame 19: 792 ms
   -

   Frame 20: 834 ms
   -

   Frame 21: 876 ms

Now, let's consider a subtitle that starts at *400 ms* and ends at *860 ms*.

   -

   Using frame timestamps (PTS):
   The subtitle would align with Frame 10 (417 ms) to Frame 20 (834 ms).
   -

   Using clock timestamps:
   The subtitle would attempt to display exactly at 400 ms. However, since
   Frame 9 covers the interval [375 ms, 417 ms[, the subtitle would
   effectively appear in the middle of Frame 9 rather than at the start of a
   frame.

Given this discrepancy, which method should be used for accurate subtitle
rendering? Should we prioritize aligning with frame timestamps (PTS), or
should subtitles be placed at the exact clock timestamps, even if that
means appearing mid-frame?

Also, does it depend on the subtitle format?

I need this information to try to convince the developer of Media3 in this
issue .
___
ffmpeg-user mailing list
ffmpeg-user@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-user

To unsubscribe, visit link above, or email
ffmpeg-user-requ...@ffmpeg.org with subject "unsubscribe".

Re: [FFmpeg-user] How can I burn-in the TRUE TIME timestamp from AVCHD/MTS video?

[Jesse Gordon]

Hello Reino, and Everybody, (Still unsolved)

I think https://stackoverflow.com/a/67409424/2703456 can help you out 
on this one. 


Thank you so much for the quick response! I have updated the subject line:

I'm trying to burn-in the TRUE time that the video was actually recorded 
-- i.e. "2025-04-03 12:45:32.123" -- the camera records the true date 
and time and both the camera AND ffplay display it during playback as a 
text overlay.


The very fine Stack Overflow link you give is related - but it's showing 
what I already tried - it shows Elapsed Time since beginning of clip - 
I'm looking for real date and time the video was filmed.


I know the information is in the file, because ffplay displays it! (But 
other players/video editors do not.)


(And ffplay even displays the absolute date/time when reading from 
stdin/pipe, so I know it's not relying on any file name creation date. 
The information is fully contained within the media stream itself.)


Thank you all for any clues you might think of!

~Jesse

___
ffmpeg-user mailing list
ffmpeg-user@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-user

To unsubscribe, visit link above, or email
ffmpeg-user-requ...@ffmpeg.org with subject "unsubscribe".

Re: [FFmpeg-user] V210 to MKV transcoding issue

[Sherbini, Leila]

Hi Kieran (& everyone)

This is the full output from terminal. This is using a macbook pro with OS 
Sequoia 15.3.2 and an updated script:

Sherbini@LIBLY207RGH60 ~ % ffmpeg -i 
/Volumes/Preservationworking/Work/Preservation\ \(FFV1\,\ mkv\)\ \(96kHz\,\ 
24-bit\)/UA-F003035_pres.mov -c:v ffv1 -level 3 -g 1 -slices 16 -slicecrc 1 
-color_primaries smpte170m -color_trc bt709 -colorspace smpte170m -color_range 
mpeg -metadata:s:v:0 "encoder= FFV1 version 3" -c:a copy -vf 
setfield=bff,setsar=10/11 -metadata creation_time=now -f matroska 
/Volumes/Preservationworking/Work/Preservation\ \(FFV1\,\ mkv\)\ \(96kHz\,\ 
24-bit\)/UA-F003035_pres.mkv
ffmpeg version 7.1.1 Copyright (c) 2000-2025 the FFmpeg developers
  built with Apple clang version 16.0.0 (clang-1600.0.26.6)
  configuration: --prefix=/opt/homebrew/Cellar/ffmpeg/7.1.1_1 --enable-shared 
--enable-pthreads --enable-version3 --cc=clang --host-cflags= 
--host-ldflags='-Wl,-ld_classic' --enable-ffplay --enable-gnutls --enable-gpl 
--enable-libaom --enable-libaribb24 --enable-libbluray --enable-libdav1d 
--enable-libharfbuzz --enable-libjxl --enable-libmp3lame --enable-libopus 
--enable-librav1e --enable-librist --enable-librubberband --enable-libsnappy 
--enable-libsrt --enable-libssh --enable-libsvtav1 --enable-libtesseract 
--enable-libtheora --enable-libvidstab --enable-libvmaf --enable-libvorbis 
--enable-libvpx --enable-libwebp --enable-libx264 --enable-libx265 
--enable-libxml2 --enable-libxvid --enable-lzma --enable-libfontconfig 
--enable-libfreetype --enable-frei0r --enable-libass --enable-libopencore-amrnb 
--enable-libopencore-amrwb --enable-libopenjpeg --enable-libspeex 
--enable-libsoxr --enable-libzmq --enable-libzimg --disable-libjack 
--disable-indev=jack --enable-videotoolbox --enable-audi
 otoolbox --enable-neon
  libavutil  59. 39.100 / 59. 39.100
  libavcodec 61. 19.101 / 61. 19.101
  libavformat61.  7.100 / 61.  7.100
  libavdevice61.  3.100 / 61.  3.100
  libavfilter10.  4.100 / 10.  4.100
  libswscale  8.  3.100 /  8.  3.100
  libswresample   5.  3.100 /  5.  3.100
  libpostproc58.  3.100 / 58.  3.100
[aist#0:1/pcm_s16le @ 0x106e04240] Guessed Channel Layout: stereo
Input #0, mov,mp4,m4a,3gp,3g2,mj2, from 
'/Volumes/Preservationworking/Work/Preservation (FFV1, mkv) (96kHz, 
24-bit)/UA-F003035_pres.mov':
  Metadata:
major_brand : qt
minor_version   : 0
compatible_brands: qt
creation_time   : 2025-03-28T18:51:05.00Z
  Duration: 00:26:46.04, start: 0.00, bitrate: 1063221 kb/s
  Stream #0:0[0x1](und): Video: v210 (v210 / 0x30313276), yuv422p10le(bt709, 
progressive), 1920x1080, 1061683 kb/s, SAR 1:1 DAR 16:9, 24 fps, 24 tbr, 24 tbn 
(default)
  Metadata:
creation_time   : 2025-03-28T18:51:05.00Z
handler_name: Core Media Video
vendor_id   : [0][0][0][0]
encoder : Uncompressed YUV 422 10-bit
timecode: 01:00:00:00
  Stream #0:1[0x2](und): Audio: pcm_s16le (lpcm / 0x6D63706C), 48000 Hz, 
stereo, s16, 1536 kb/s (default)
  Metadata:
creation_time   : 2025-03-28T18:51:05.00Z
handler_name: Core Media Audio
vendor_id   : [0][0][0][0]
  Stream #0:2[0x3](und): Data: none (tmcd / 0x64636D74) (default)
  Metadata:
creation_time   : 2025-03-28T18:51:05.00Z
handler_name: Core Media Time Code
timecode: 01:00:00:00
Stream mapping:
  Stream #0:0 -> #0:0 (v210 (native) -> ffv1 (native))
  Stream #0:1 -> #0:1 (copy)
Press [q] to stop, [?] for help
[ffv1 @ 0x106e05060] bits_per_raw_sample > 8, forcing range coder
Output #0, matroska, to '/Volumes/Preservationworking/Work/Preservation (FFV1, 
mkv) (96kHz, 24-bit)/UA-F003035_pres.mkv':
  Metadata:
major_brand : qt
minor_version   : 0
compatible_brands: qt
creation_time   : now
encoder : Lavf61.7.100
  Stream #0:0(und): Video: ffv1 (FFV1 / 0x31564646), yuv422p10le(tv, 
smpte170m/bt709/bt709, bottom coded first (swapped)), 1920x1080 [SAR 10:11 DAR 
160:99], q=2-31, 200 kb/s, 24 fps, 1k tbn (default)
  Metadata:
creation_time   : 2025-03-28T18:51:05.00Z
handler_name: Core Media Video
vendor_id   : [0][0][0][0]
timecode: 01:00:00:00
encoder :  FFV1 version 3
  Stream #0:1(und): Audio: pcm_s16le ([1][0][0][0] / 0x0001), 48000 Hz, stereo, 
s16, 1536 kb/s (default)
  Metadata:
creation_time   : 2025-03-28T18:51:05.00Z
handler_name: Core Media Audio
vendor_id   : [0][0][0][0]
frame=2 fps=0.3 q=-0.0 size=   1KiB time=00:00:00.08 bitrate= 
113.3kbitsframe=3 fps=0.5 q=-0.0 size=1536KiB time=00:00:00.12 
bitrate=100663.3kbiframe=4 fps=0.6 q=-0.0 size=3072KiB time=00:00:00.16 
bitrate=150994.6kbiframe=5 fps=0.7 q=-0.0 size=4864KiB time=00:00:00.20 
bitrate=191260.6kbiframe=6 fps=0.7 q=-0.0 size=6400KiB time=00:00:00.25 
bitrate=209715.

Re: [FFmpeg-user] How can I burn-in the TRUE TIME timestamp from AVCHD/MTS video?

[BloodMan]

Good morning Jesse,

W dniu 2025-04-04 o 18:37, Jesse Gordon pisze:
I'm trying to burn-in the TRUE time that the video was actually recorded 
-- i.e. "2025-04-03 12:45:32.123" -- the camera records the true date 
and time and both the camera AND ffplay display it during playback as a 
text overlay.

[...]


https://video.stackexchange.com/questions/35917/ffmpeg-how-to-burn-in-the-timecode-from-a-streams-metadata

you can also want to keep timecode in output file:
https://stackoverflow.com/questions/18253340/keep-timecode-in-ffmpeg

Have fun.


--
Pozdrawiam,
blood...@gmail.com
___
ffmpeg-user mailing list
ffmpeg-user@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-user

To unsubscribe, visit link above, or email
ffmpeg-user-requ...@ffmpeg.org with subject "unsubscribe".

[FFmpeg-user] V210 to MKV transcoding issue

[Sherbini, Leila]

Hey folks!

I’ve been having issues with transcoding v210 mov files into mkv using ffmpeg. 
Every time I try I get the following error:

[in#0/mov,mp4,3gp,3pg2,mj2 @ 0x60b5cd00] Error during demuxing : Device not 
configured
[[in#0/mov,mp4,3gp,3pg2,mj2 @ 0x60b5cd00] Error retrieving a packet from 
demuxer: Device not configured
[out#0/matroska @ 0x6025c780] Error closing file: Bad file descriptor

This is issue has been happening on an iMac with an OS of Sequoia 15.3.2 and 
the same error has occurred with ffmpeg versions 7.1.1 and 6.1.2. On a 
different iMac running Mojave 10.14.6 OS and ffmpeg version 5.0 the transcode 
goes through fine.

This is the script I’m using:

ffmpeg -i input_file -map 0 -dn -c:v ffv1 -level 3 -g 1 -slicecrc 1 -slices 16 
-c:a copy output_file.mkv -f framemd5 -an framemd5_output_file

Any ideas as to what the issue is and how to fix it? Any insight is appreciated!

Best,
Leila

--
Leila Sherbini | Media Preservation Resident Librarian
Michigan State University Libraries
sherb...@msu.edu
she / her / hers What’s this?
___
ffmpeg-user mailing list
ffmpeg-user@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-user

To unsubscribe, visit link above, or email
ffmpeg-user-requ...@ffmpeg.org with subject "unsubscribe".

Re: [FFmpeg-user] How can I burn-in the TRUE TIME timestamp OR SUBTITLES? from AVCHD/MTS video?

[Jesse Gordon]

Good Morning BloodMan and Everybody! (Not yet solved, getting closer!)

https://video.stackexchange.com/questions/35917/ffmpeg-how-to-burn-in-the-timecode-from-a-streams-metadata 



Thank you for the tips! This is getting close, but in my case it always 
just displays "00:00:00:00" because, according to ffprobe:


TAG:timecode=00:00:00:00  For EVERY frame

and

[TIMECODE]
value=00:00:00:00
[/TIMECODE]

Also, for EVERY frame... (Shame  shame Sony...)

However, I do notice that there is a [SUBTITLE] section for every 30 
video frames:


Below are the first three  SUBTITLE sections. Is it possible that this 
is what ffplay is using to display the real date/time?


Or is it calculating it from the pkt_pts or best_effort_timestamp stuff 
in the actual video frames? (Also see one video frame below, the fourth 
video frame.)



Also of interest,

Input #0, mpegts, from '0.MTS':
  Duration: 00:00:37.06, start: 1.016689, bitrate: 26570 kb/s
  Program 1
  Stream #0:0[0x1011]: Video: h264 (High) (HDPR / 0x52504448), 
yuv420p(progressive), 1920x1080 [SAR 1:1 DAR 16:9], 59.94 fps, 59.94 
tbr, 90k tbn, 119.88 tbc
  Stream #0:1[0x1100]: Audio: ac3 (AC-3 / 0x332D4341), 48000 Hz, 
stereo, fltp, 256 kb/s
  Stream #0:2[0x1200]: Subtitle: hdmv_pgs_subtitle ([144][0][0][0] / 
0x0090), 1920x1080



I did try a few sample commands to extract subtitles but those just gave 
an empty .srt file.  It looks to me like the subtitle entries are time 
stamped but empty.



But somehow ffplay is correctly decoding the real time date and time and 
displaying it.


maybe it's a question for the devs?


I would just say that Sony hadn't implemented it in any understandable 
way and throw in the towel if FFPLAY didn't decode it correctly!



Thank you all very much, I will continue rooting around, definitely let 
me know if any ideas come to mind!


~Jesse


[SUBTITLE]
media_type=subtitle
pts=1016689
pts_time=1.016689
format=0
start_display_time=0
end_display_time=4294967295
num_rects=1
[/SUBTITLE]

[SUBTITLE]
media_type=subtitle
pts=1517189
pts_time=1.517189
format=0
start_display_time=0
end_display_time=4294967295
num_rects=1
[/SUBTITLE]

[SUBTITLE]
media_type=subtitle
pts=2017689
pts_time=2.017689
format=0
start_display_time=0
end_display_time=4294967295
num_rects=1
[/SUBTITLE]

[FRAME]
media_type=video
stream_index=0
key_frame=0
pkt_pts=94505
pkt_pts_time=1.050056
pkt_dts=94504
pkt_dts_time=1.050044
best_effort_timestamp=94505
best_effort_timestamp_time=1.050056
pkt_duration=1501
pkt_duration_time=0.016678
pkt_pos=264768
pkt_size=69453
width=1920
height=1080
pix_fmt=yuv420p
sample_aspect_ratio=1:1
pict_type=P
coded_picture_number=2
display_picture_number=0
interlaced_frame=0
top_field_first=0
repeat_pict=0
color_range=unknown
color_space=unknown
color_primaries=unknown
color_transfer=unknown
chroma_location=left
TAG:timecode=00:00:00:00
[SIDE_DATA]
side_data_type=SMPTE 12-1 timecode
[TIMECODE]
value=00:00:00:00
[/TIMECODE]
[/SIDE_DATA]
[/FRAME]




___
ffmpeg-user mailing list
ffmpeg-user@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-user

To unsubscribe, visit link above, or email
ffmpeg-user-requ...@ffmpeg.org with subject "unsubscribe".

Re: [FFmpeg-user] V210 to MKV transcoding issue

[Kieran O Leary]

What is the output of

ffmpeg -i /Volumes/Preservationworking/Work/Preservation\ \(FFV1\,\ mkv\)\
\(96kHz\,\ 24-bit\)/UA-F003035_pres.mov -f null -

This will just decode the input file. Curious if it fails the same way.
Does the input file play correctly in VLC?

K
___
ffmpeg-user mailing list
ffmpeg-user@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-user

To unsubscribe, visit link above, or email
ffmpeg-user-requ...@ffmpeg.org with subject "unsubscribe".

Re: [FFmpeg-user] Subtitle Timing: Clock Timestamps vs. Frame Timestamps

[Mark Filipak]

On 04/04/2025 10.16, jeremie bergeron wrote:

Hi,

This is not strictly an FFmpeg question but rather a general video
processing question regarding when subtitles should be rendered.

In this discussion, we are debating whether subtitles should be displayed
based on *clock timestamps* or *frame timestamps (PTS)*.
Let's say I have a video with those timestamps:

-

Frame 0: 0 ms
-

Frame 1: 42 ms
-

Frame 2: 83 ms


... continues


Frame 9: 375 ms


... continues


Frame 20: 834 ms



Now, let's consider a subtitle that starts at *400 ms* and ends at *860 ms*.


Subtitle Edit (https://www.nikse.dk/subtitleedit) has a tool called "Beautify time codes". The tool 
snaps subtitle times to the elapsed-time equivalents of frame PTSes. So your 0:0.400..0:0.860 
subtitle would snap to 0:0.375..0:0.834.


Hope this helps.
___
ffmpeg-user mailing list
ffmpeg-user@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-user

To unsubscribe, visit link above, or email
ffmpeg-user-requ...@ffmpeg.org with subject "unsubscribe".

Re: [FFmpeg-user] How can I burn-in the TRUE TIME timestamp OR SUBTITLES? from AVCHD/MTS video?

[BloodMan]

Hi Jesse,

W dniu 2025-04-04 o 20:11, Jesse Gordon pisze:

Good Morning BloodMan and Everybody! (Not yet solved, getting closer!)
https://video.stackexchange.com/questions/35917/ffmpeg-how-to-burn-in-the-timecode-from-a-streams-metadata 
Thank you for the tips! This is getting close, but in my case it always 
just displays "00:00:00:00" because, according to ffprobe:

TAG:timecode=00:00:00:00  For EVERY frame
and
[TIMECODE]
value=00:00:00:00
[/TIMECODE]
Also, for EVERY frame... (Shame  shame Sony...)


Yup, fckd probably...
Hm, tip?

tip 1:
maybe... what with -copyts before and/or after -i ?
(single and multiple combinations)

btw. I know, this is probably not the solution, but if you don't check 
you won't know.



tip 2:
you can also... fix that - get start timecode via ffprobe and insert 
your OWN timecode - something like that:

https://stackoverflow.com/questions/65027118/ffmpeg-change-timecode-metadata-inside-video-file
(probably answer 2 is closer)

MAYBE inserting tc is done before rendering via filter
(not checked, small chances but just thinking)

Have fun :)


--
Pozdrawiam,
blood...@gmail.com
___
ffmpeg-user mailing list
ffmpeg-user@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-user

To unsubscribe, visit link above, or email
ffmpeg-user-requ...@ffmpeg.org with subject "unsubscribe".

Re: [FFmpeg-user] Subtitle Timing: Clock Timestamps vs. Frame Timestamps

[jeremie bergeron]

I'm not trying to edit the subtitle, so no, it doesn't really help me.

I want to know if the player must use the Clock Timestamps or Frame
Timestamps to know when to display the subtitle.

Le ven. 4 avr. 2025 à 14:10, Mark Filipak  a
écrit :

> On 04/04/2025 10.16, jeremie bergeron wrote:
> > Hi,
> >
> > This is not strictly an FFmpeg question but rather a general video
> > processing question regarding when subtitles should be rendered.
> >
> > In this discussion, we are debating whether subtitles should be displayed
> > based on *clock timestamps* or *frame timestamps (PTS)*.
> > Let's say I have a video with those timestamps:
> >
> > -
> >
> > Frame 0: 0 ms
> > -
> >
> > Frame 1: 42 ms
> > -
> >
> > Frame 2: 83 ms
>
> ... continues
>
> > Frame 9: 375 ms
>
> ... continues
>
> > Frame 20: 834 ms
>
> > Now, let's consider a subtitle that starts at *400 ms* and ends at *860
> ms*.
>
> Subtitle Edit (https://www.nikse.dk/subtitleedit) has a tool called
> "Beautify time codes". The tool
> snaps subtitle times to the elapsed-time equivalents of frame PTSes. So
> your 0:0.400..0:0.860
> subtitle would snap to 0:0.375..0:0.834.
>
> Hope this helps.
> ___
> ffmpeg-user mailing list
> ffmpeg-user@ffmpeg.org
> https://ffmpeg.org/mailman/listinfo/ffmpeg-user
>
> To unsubscribe, visit link above, or email
> ffmpeg-user-requ...@ffmpeg.org with subject "unsubscribe".
>
___
ffmpeg-user mailing list
ffmpeg-user@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-user

To unsubscribe, visit link above, or email
ffmpeg-user-requ...@ffmpeg.org with subject "unsubscribe".

Re: [FFmpeg-user] Subtitle Timing: Clock Timestamps vs. Frame Timestamps

[Mark Filipak]

On 04/04/2025 15.36, jeremie bergeron wrote:

I'm not trying to edit the subtitle, so no, it doesn't really help me.

I want to know if the player must use the Clock Timestamps or Frame
Timestamps to know when to display the subtitle.


I never gave it a thought before. Thanks for this opportunity.

If you connect to the TV via component cables or HDMI, then the TV gets television, CEA-861 (NTSC or 
PAL), and CC (closed captioning), and that's all. Since the video _must_ be in television frames, 
I'd say that the subtitles must already be rendered and superimposed over frame images -- except for 
CC, television displays content solely in frames.


So I'd say that subtitles must have elapsed-time timestamps that fit them into their intended 
frames. Subtitle Edit's Beautify time stamps does that.



Le ven. 4 avr. 2025 à 14:10, Mark Filipak  a
écrit :


On 04/04/2025 10.16, jeremie bergeron wrote:

Hi,

This is not strictly an FFmpeg question but rather a general video
processing question regarding when subtitles should be rendered.

In this discussion, we are debating whether subtitles should be displayed
based on *clock timestamps* or *frame timestamps (PTS)*.
Let's say I have a video with those timestamps:

 -

 Frame 0: 0 ms
 -

 Frame 1: 42 ms
 -

 Frame 2: 83 ms


... continues


 Frame 9: 375 ms


... continues


 Frame 20: 834 ms



Now, let's consider a subtitle that starts at *400 ms* and ends at *860

ms*.

Subtitle Edit (https://www.nikse.dk/subtitleedit) has a tool called
"Beautify time codes". The tool
snaps subtitle times to the elapsed-time equivalents of frame PTSes. So
your 0:0.400..0:0.860
subtitle would snap to 0:0.375..0:0.834.

Hope this helps.


___
ffmpeg-user mailing list
ffmpeg-user@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-user

To unsubscribe, visit link above, or email
ffmpeg-user-requ...@ffmpeg.org with subject "unsubscribe".