On 26/05/2024 14.18, Bart Westenenk wrote:
Hello all,
I want to alter the motion vectors of B and P frames in a H.264 video. The point of doing this is
watermarking / steganography, the goal is to change the motion vectors' width / height based on the
watermark.
Motion vectors don't work
On 24/05/2024 13.19, Andrew Randrianasulu wrote:
пт, 24 мая 2024 г., 20:16 Mark Filipak :
This is from H.262.
___
| |
| field_sequence – A 3-bit integer which
This is from H.262.
___
| |
| field_sequence – A 3-bit integer which defines the number of the |
| field in the eight field sequence used in PAL systems or the four
from success than from failure, and
you made it happen.
--Mark.
On 21/05/2024 16.04, Paul B Mahol wrote:
On Tue, May 21, 2024 at 10:52 AM Mark Filipak
wrote:
Attachments:
1. original ebur128.jpg
2. loudnorm-thresh=-85 pan ebur128.jpg
3. what I want ebur128.jpg
___1. The original
has a 'shelf
Attachments:
1. original ebur128.jpg
2. loudnorm-thresh=-85 pan ebur128.jpg
3. what I want ebur128.jpg
___1. The original
has a 'shelf' just below LU = -13. That's soft speech.
The peak is at LU = +9. That's shouting.
So the transform I want goes like this:
LU = -18..-14 gets no boost.
LU =
On 21/05/2024 01.19, Anne Wu via ffmpeg-user wrote:
-snip-
... Also, I'd like the
timestamps of the output video to remain the same as the original,
so essentially preserving the edit-lists from the original, which I
don't think the above would accomplish. Is there a way to do that?
Try
I've attached ebur128.jpg. It's only 37 k-bytes.
Do you see that first 'shelf' just below LU = -13? I want to boost that the most by percent, maybe
double the power (3 dB). I want to boost LU = 9 not at all, and I want to boost everything below LU
= -14 not at all.
So the transform I want
On 20/05/2024 14.09, Moritz Barsnick via ffmpeg-user wrote:
On Mon, May 20, 2024 at 13:14:43 -0400, Mark Filipak wrote:
Doesn't work:
ffmpeg -i c:\source.mp4 -map 0 -af abitscope -c:v libx265 -x265-params
crf=18 -c:a ac3 -sn -dn "c:\abitscope.mp4"
[...]
[vf#0:0 @ 0053e
Howdy,
Maybe I don't need 'abitscope'. It's just an experiment when I found that 'oscilloscope' didn't
display audio levels.
I have a 5.1 channel DTS soundtrack. It's the only soundtrack. I want to mux in a new, 2 channel AC3
soundtrack with soft dialog emphasized. I'm using 'loudnorm' &
On 20/05/2024 14.09, Moritz Barsnick via ffmpeg-user wrote:
On Mon, May 20, 2024 at 13:14:43 -0400, Mark Filipak wrote:
Doesn't work:
ffmpeg -i c:\source.mp4 -map 0 -af abitscope -c:v libx265 -x265-params
crf=18 -c:a ac3 -sn -dn "c:\abitscope.mp4"
[...]
[vf#0:0 @ 0053e
Howdy,
Doesn't work:
ffmpeg -i c:\source.mp4 -map 0 -af abitscope -c:v libx265 -x265-params crf=18 -c:a ac3 -sn -dn
"c:\abitscope.mp4"
Doesn't work:
ffmpeg -i c:\source.mp4 -map 0 -vf abitscope -c:v libx265 -x265-params crf=18 -c:a ac3 -sn -dn
"c:\abitscope.mp4"
The reports are below. Does
On 09/05/2024 06.07, Yann Cainjo wrote:
Hi Mark
Hey Yann
DTSes & PTSes only exist in MPEG PESes for I-frames
Where did you get this information ?
By parsing actual presentation streams. Start reading 24 lines down in this message. Note that email
will wrap long sentences but its easy
DTSes & PTSes only exist in MPEG PESes for I-frames. So, where/how is FFmpeg getting the DTSes &
PTSes that it shows for B- & P-frames?
--Mark.
___
ffmpeg-user mailing list
ffmpeg-user@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-user
To
Hi All,
I'm still investigating why cuts & concats sometimes don't work. I've found that sometimes open GOPs
are physically in PTS order & sometimes in DTS order. I reckon that's part/all of the problem.
I have some questions.
Command #1:
ffmpeg -i y:\VIDEO_TS\VTS_03_2.VOB -map 0 -copyts -c
On 13/04/2024 17.27, Jim Worrall wrote:
On Apr 13, 2024, at 01:57, bbb wrote:
Sorry for bothering you. It only behaves like this when I use "-codec copy".
Without that option it accepts the exact time I've specified.
On 4/13/24 13:47, bbb wrote:
I want to cut off the start of a video.
Does anyone see what I'm doing wrong?
BEFORE.
0, 503945955, 503957216, 3753, 640646, 0x90f222e3
0, 503957216, 503964723, 3753, 125904, 0x3f60a4e2
0, 503960970, 503960970, 3753, 106426, 0xe5c85d36
0, 503964723, 503975985, 3753, 126806, 0x9c5d46c5
COMMAND to change
Does FFmpeg provide any way to write packet SCR (System Clock Reference) (i.e., at PS_PACKET_HEADER
+ 4 bytes)? I will need to rewrite SCRs for all ps packets via a math eval.
I searched but could not find.
Thanks,
--Mark.
___
ffmpeg-user mailing
Is there more to this? If there is, it's not evident to me.
If there are several B-frames in a row, then adjust your mind to 'see' larger shifts across the
multiple B-frames and adjust PTSs & DTSs to match.
Cutting off a leading open GOP:
<—closed
On 03/04/2024 04.05, Paul B Mahol wrote:
On Wed, Apr 3, 2024 at 6:10 AM Mark Filipak
wrote:
Dear Developers,
Thank you for adding 'pkt_dts' and 'pict_type' to '-show_frames'. Those
will make things easier.
Now, could you fix it?
'-show_frames' shows pts < dts.
frames.frame.133975.
Dear Developers,
Thank you for adding 'pkt_dts' and 'pict_type' to '-show_frames'. Those will
make things easier.
Now, could you fix it?
'-show_frames' shows pts < dts.
frames.frame.133975.pts=503957216 <-+ These are actually 3 frames
frames.frame.133975.pkt_dts=503968477 <-+ apart in
Thank you, Mark.
On 25/03/2024 16.45, Mark Thompson wrote:
On 24/03/2024 15:48, Mark Filipak wrote:
I cut at the end of an open GOP. When I did that, FFmpeg did not set the MPEG 'broken_link' flag
to '1'.
The frame following the cut has to be flagged:
'closed_gop' = '0' because it's an open
I cut at the end of an open GOP. When I did that, FFmpeg did not set the MPEG
'broken_link' flag to '1'.
The frame following the cut has to be flagged:
'closed_gop' = '0' because it's an open GOP, also, and
'broken_link' = '1'.
How do I do that? I searched but did not find.
Thanks
--Mark.
I have new content for anyone interested in what I hope will be the future of
FFmpeg.
New
Digital_Camera_'SAR'-v-Film_Scanner_SAR
https://markfilipak.github.io/Video-Object-Notation/OFFmpeg.Digital_Camera_'SAR'-v-Film_Scanner_SAR.html
Stride-Match With Decombing Examples
I have new content for anyone interested in what I hope will be the future of
FFmpeg.
New
Stride-Match With Decombing Examples
https://markfilipak.github.io/Video-Object-Notation/OFFmpeg.Stride-Match_With_Decombing_Examples.html
Six Element Objects & 12 Stream Objects
I have new content for anyone interested in what I hope will be the future of
FFmpeg.
New
Six Element Objects & 12 Stream Objects
https://markfilipak.github.io/Video-Object-Notation/OFFmpeg.Six_Element_Objects_&_12_Stream_Objects.html
Streams
On 04/03/2024 06.25, Rob Hallam wrote:
The visuals look good! Nice work. I don't want to detract from that, but:
Thank you, Rob. You're right about style inheritance but that's not the issue. Firefox doesn't scale
font-size linearly or consistently whereas other browsers do. You can see that
On 03/03/2024 18.33, Jim DeLaHunt wrote:
Mark:
On 2024-03-02 19:51, Mark Filipak wrote:
I have a couple of things to look at.
https://markfilipak.github.io/Video-Object-Notation/Streams.html
https://markfilipak.github.io/Video-Object-Notation/GOP%20%26%20Frame%20Reordering.html
Comments
I have a couple of things to look at.
https://markfilipak.github.io/Video-Object-Notation/Streams.html
https://markfilipak.github.io/Video-Object-Notation/GOP%20%26%20Frame%20Reordering.html
Comments are welcome. Please be brutal. 'Streams' is crucial.
I have little knowledge of transport
Hi All,
I'm taking a break from my "errors in trimming and concatenation" pursuits.
Here is a single-page HTML about streams.
https://markfilipak.github.io/Video-Object-Notation/Streams.html
...this will eventually be FFmpeg documentation if possible, _not_ a book...
If you see anything wrong
Well, the attachment, which was only 50kB, got stripped off. I'm trying again.
Hi All,
I'm taking a break from my "errors in trimming and concatenation" pursuits.
I've attached a single-page HTML about streams.
...this will eventually be FFmpeg documentation if possible, _not_ a book...
If
Hi All,
I'm taking a break from my "errors in trimming and concatenation" pursuits.
I've attached a single-page HTML about streams.
...this will eventually be FFmpeg documentation if possible, _not_ a book...
If you see anything wrong or questionable about it -- anything at all, no matter how
On 29/02/2024 17.40, Ferdi Scholten wrote:
Hi, Ferdi,
Thank you for the tip. I checked it against what I'm doing.
The 'pts_time's that it returns do not correlate with the exact times that are computed from frame
counts. For example, pts_time=760.607200 should be exactly 760.3[364635..]
On 29/02/2024 12.19, Ferdi Scholten wrote:
The following command will show all key frames and they're time in the video.
ffprobe -loglevel error -skip_frame nokey -select_streams v:0 -show_entries frame=pts_time
sourcevideo.mkv
Hi, Ferdi,
Thank you for the tip. I checked it against what
On 21/02/2024 05.20, Paul B Mahol wrote:
On Wed, Feb 21, 2024 at 10:12 AM Mark Filipak
wrote:
Gyan, Paul, Devin, Jim, anyone. Help!
You folks have been following my trim+concat adventure. I think I may have
found the problem, not just for me. It's a general problem.
"N" signifies
Gyan, Paul, Devin, Jim, anyone. Help!
You folks have been following my trim+concat adventure. I think I may have found the problem, not
just for me. It's a general problem.
"N" signifies one frame time. All times are relative to ptsA.
__DTS__ _PTS__
ptsA-2N ptsAI-frame with
I don't know how "DTS" became "000". Sorry. It's 3AM and I'm a little punchy.
I found the problem. FFmpeg is corrupting the last B-frame at the end of cuts. It shows up during
subsequent concatenation. Why it's happening is unknown of course.
There is no workaround that I can conceive of.
I found the problem. FFmpeg is corrupting the last B-frame at the end of cuts. It shows up during
subsequent concatenation. Why it's happening is unknown of course.
There is no workaround that I can conceive of.
--Mark.
000 PTS video 1 video 2
< 504197456
On 15/02/2024 13.55, Diederick C. Niehorster wrote:
Hi Mark,
On Thu, Feb 15, 2024, 19:42 Mark Filipak wrote:
Here is my first finding.
Can someone who reads 'C' code locate the code and investigate?
As told to you many times now, you need to provide a complete command line
Here is my first finding.
Can someone who reads 'C' code locate the code and investigate?
It looks suspicious to me because everywhere else, timestamps appear to be truncated in the usual
way. Here, to make a PTS, FFmpeg is truncating _up_.
If N*3753.75 is an integer, it's used as PTS. But
if
On 14/02/2024 11.42, Gyan Doshi wrote:
Like the noise bsf. But it does not compute or look at payload CRC.
https://ffmpeg.org//ffmpeg-bitstream-filters.html#noise
Regards,
Gyan
Thank you, Gyan!
ffmpeg -copyts -i this.m2ts -map 0 -bsf:v noise=drop='lt(pts\,2854113)+gt(pts\,504223732)'
Can anyone suggest a way to delete the marked packets?
0: video, 1: audio
/ DTS PTSticksbytes packet_CRC
1,2798640,2798640, 960, 60, 0xec16103f <==
: 48 more <==
1,2845680,2845680, 960,
A , I apologize for highjacking your topic. I thought it was related to mine.
My fault.
Please start a new topic with a new subject and I'll butt out. -- Mark.
___
ffmpeg-user mailing list
ffmpeg-user@ffmpeg.org
On 14/02/2024 02.47, Paul B Mahol wrote:
Your response is off topic.
___
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
I'm top posting and if someone doesn't like it, that's your problem.
A, this is why some of the code needs to be dynamic 'build up-tear down' code. Static code just
can't do the job. --Mark.
On 13/02/2024 20.37, A wrote:
Let's say I have a video with I, P and B frames. My understanding is
On 13/02/2024 20.27, amindfv--- via ffmpeg-user wrote:
params *before* "-i" are *input params*
params *after* "-i" are *output params*
that has *always* been the case at least for 15 years and so it's
logical that you can't place a param at a random position by common
sense and expect the same
On 13/02/2024 14.13, Reindl Harald wrote:
Am 13.02.24 um 19:39 schrieb Paul B Mahol:
On Tue, Feb 13, 2024 at 7:21 PM Mark Filipak
wrote:
On 13/02/2024 03.24, Paul B Mahol wrote:
On Tue, Feb 13, 2024 at 12:37 AM Carl Zwanzig wrote:
Paul, Carl, I assume you are both familiar
On 13/02/2024 03.24, Paul B Mahol wrote:
On Tue, Feb 13, 2024 at 12:37 AM Carl Zwanzig wrote:
Paul, Carl, I assume you are both familiar with the source code. I'm not.
Fact: '-ss'-before-'-i' and '-i'-before-'-ss' _do_ give different results. I suggested that the
difference might result
On 12/02/2024 11.30, Paul B Mahol wrote:
On Mon, Feb 12, 2024 at 9:48 AM Mark Filipak
wrote:
Does FFmpeg do any internal scripting or dynamic code building/linking?
Please define what you mean by these concepts.
Happy to, Paul.
Internal scripting is when a task is built using a scripting
On 12/02/2024 03.21, Paul B Mahol wrote:
Mark wants single command example to work 100% correct in 100% situations
and that output is 100% correct 100% of time.
Yes. Of course.
That is possible only for very trivial containers only currently. And
because libs are very low level it can not be
On 11/02/2024 17.39, Paul B Mahol wrote:
On Sun, Feb 11, 2024 at 11:08 PM Mark Filipak
wrote:
On 11/02/2024 16.42, Paul B Mahol wrote:
Codec copy with -ss before -i and after -i is not documented that it gives
different results
Does that make sense? I think it's not documented because
On 11/02/2024 16.42, Paul B Mahol wrote:
Codec copy with -ss before -i and after -i is not documented that it gives
different results
Does that make sense? I think it's not documented because no one knows how to
explain the results.
because once you do not decode everything from start you
-- Forgive me if this is a duplicate (trouble with email client, again) --
I think I can help out here, Vincent.
On 11/02/2024 14.53, Vincent Deconinck wrote:
Hi,
I will probably get flamed because I'm for jumping into this conversation
while being a complete newbie :-), but I think nobody
I think I can help out here, Vincent.
On 11/02/2024 14.53, Vincent Deconinck wrote:
Hi,
I will probably get flamed because I'm for jumping into this conversation
while being a complete newbie :-), but I think nobody replied with an
answer to Mark's question "why".
Before "why" there's the
On 11/02/2024 14.28, Paul B Mahol wrote:
On Sun, Feb 11, 2024 at 7:12 PM Mark Filipak
wrote:
On 11/02/2024 13.09, Bouke / Videotoolshed wrote:
So do you, so why ask the question?
Now go away!
I do not know the answer.
In most cases you will get in most times different results for those
On 11/02/2024 13.09, Bouke / Videotoolshed wrote:
So do you, so why ask the question?
Now go away!
I do not know the answer.
___
ffmpeg-user mailing list
ffmpeg-user@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-user
To unsubscribe, visit
On 11/02/2024 13.00, Bouke / Videotoolshed wrote:
Stop trolling.
Read in on the subject. You want to write a FFmpeg manual?
Go away, don’t spam the rest of us.
On 11 Feb 2024, at 18:47, Mark Filipak wrote:
Command 1:
ffmpeg -ss 10 -copyts -i this.m2ts -map 0 -c copy -sn -dn -muxdelay 0
Command 1:
ffmpeg -ss 10 -copyts -i this.m2ts -map 0 -c copy -sn -dn -muxdelay 0 that.m2ts
Command 2:
ffmpeg -copyts -i this.m2ts -map 0 -ss 10 -c copy -sn -dn -muxdelay 0 that.m2ts
Let's ignore all the errors both make. And let's ignore the individual errors that they make
individually.
On 08/02/2024 15.16, Paul B Mahol wrote:
I think, that one of variant use seeking (in container via demuxer) and
other one use frame seeking by decoding everything from start using trim
filters.
Nope. Neither is decoding -- too fast -- as though decoding would/should make a
difference.
On 08/02/2024 05.40, Paul B Mahol wrote:
Read logs and compare, use common sense, brain cells, logic and
intelligence.
Thank you, Vladimir Vladimirovich. I'd do that if I had a brain.
Why are they different?
--Mark.
___
ffmpeg-user mailing list
On 07/02/2024 16.53, Paul B Mahol wrote:
On Wed, Feb 7, 2024 at 10:28 PM Mark Filipak
wrote:
Hi Carl,
On 07/02/2024 13.56, Carl Zwanzig wrote:
On 2/7/2024 10:34 AM, Mark Filipak wrote:
Okay. Why are they different?
Because the containers are different? An mp4 container is not the same
On 07/02/2024 16.53, Paul B Mahol wrote:
On Wed, Feb 7, 2024 at 10:28 PM Mark Filipak
wrote:
Hi Carl,
On 07/02/2024 13.56, Carl Zwanzig wrote:
On 2/7/2024 10:34 AM, Mark Filipak wrote:
Okay. Why are they different?
Because the containers are different? An mp4 container is not the same
Hi Carl,
On 07/02/2024 13.56, Carl Zwanzig wrote:
On 2/7/2024 10:34 AM, Mark Filipak wrote:
Okay. Why are they different?
Because the containers are different? An mp4 container is not the same as an mkv (or avi or mpeg),
they must have different demuxers.
They are the same source, same
On 07/02/2024 10.06, Paul B Mahol wrote:
On Wed, Feb 7, 2024 at 2:43 AM Mark Filipak
wrote:
Why are these different?
This is all about seeking, and that depends 10% on internal demuxer
implementation of container.
Okay. Why are they different
Why are these different?
Looking only at the first 5 video frames:
ffmpeg -ss 20.061708333 -copyts -i %SOURCE% -map 0 -c copy -sn -dn -muxdelay 0
%TARGET%
produces this:
0,2846606,2854113, 3753, 640646, 0x3a5a0c45
0,2850360,2850360, 3753, 640646, 0xfed1d09a <==
Why are these different?
ffmpeg -ss 20.061708333 -copyts -i %SOURCE% -map 0 -c copy -sn -dn -muxdelay 0
%TARGET%
ffmpeg -copyts -i %SOURCE% -map 0 -ss 20.061708333 -c copy -sn -dn -muxdelay 0
%TARGET%
The DTSs are different. The PTSs are different. The cuts are at different running times. The
ffmpeg -ss 20.061708333 -copyts -i %SOURCE% -map 0 -c copy -sn -dn -muxdelay 0
"%TARGET%"
left behind 59 PES packets that should have been trimmed off.
Short of researching the number of 2048 byte sectors in each offending PES and then deleting the
sectors, can anyone suggest a better/easier
On 01/02/2024 16.08, Reindl Harald wrote:
Am 01.02.24 um 21:58 schrieb Mark Filipak:
On 01/02/2024 15.48, Reindl Harald wrote:
Am 01.02.24 um 20:49 schrieb Mark Filipak:
On 01/02/2024 14.41, Carl Zwanzig wrote:
On 2/1/2024 11:26 AM, Mark Filipak wrote:
There needs to be an FFmpeg Guild
On 01/02/2024 16.09, Devin Heitmueller wrote:
On Thu, Feb 1, 2024 at 1:55 PM Mark Filipak wrote:
On 01/02/2024 09.54, Devin Heitmueller wrote:
On Thu, Feb 1, 2024 at 1:15 AM Mark Filipak wrote:
FFmpeg assigns DTSs & PTSs to P-frames and B-frames in MPEG2-TS streams. How
does it deter
On 01/02/2024 14.41, Carl Zwanzig wrote:
On 2/1/2024 11:26 AM, Mark Filipak wrote:
There needs to be an FFmpeg Guild and there needs to be an FFmpeg industry. You guys/gals need to
make a living. How can we make that happen?
Why does there need to be a "guild"?
Because FFmpeg
The reader and the book would be copyrighted.
--Mark.
___
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
On 01/02/2024 14.15, Bouke / edit 'B wrote:
I'd pay $25/month to belong.
I pay 25 bucks for each troll head.
(Or 50 per ball, makes for more fun)
Bouke
Stop playing the Vladimir Putin role. This isn't a movie.
There needs to be an FFmpeg Guild and there needs to be an FFmpeg industry.
On 01/02/2024 13.58, Paul B Mahol wrote:
Yes ffmpeg is sole problem here.
Go use something better and non-free.
What's better?
Paul, you're trapped, aren't you? You need to make a living but you can't make a living working on
FFmpeg.
Shall we discuss how the FFmpeg Guild members can make
Hey Devin,
On 01/02/2024 09.54, Devin Heitmueller wrote:
Hi Mark,
On Thu, Feb 1, 2024 at 1:15 AM Mark Filipak wrote:
FFmpeg assigns DTSs & PTSs to P-frames and B-frames in MPEG2-TS streams. How
does it determine those
DTSs & PTSs?
Since DTSs & PTSs don't actually exist for
FFmpeg assigns DTSs & PTSs to P-frames and B-frames in MPEG2-TS streams. How does it determine those
DTSs & PTSs?
Since DTSs & PTSs don't actually exist for P-/B-frames in MPEG2-TS streams, FFmpeg must have a way
that's unknown to me.
I'm seeing some strange things. They can't be as strange
I made an inconsequential mistake:
: (5590.835 sec)*(24/1.001 fps) = 134045.[994005..] frames, i.e., 481..134046
should be
: (5590.835 sec)*(24/1.001 fps) = 134045.[994005..] frames, i.e., 0..134045
It does not change the '-to' argument.
Please excuse my error. --Mark.
Interested and knowledgeable folks, please confirm my results prior to trac submission. I'd like to
know what happens in other use-cases. If you want this video, I could make a shortened version that
would allow testing of the front trim, and we could figure out how to get it to you.
Thanks
PS: Actually, I think '-framespan' would be a better name for such a function.
-framespan 481..134046
On 13/01/2024 22.57, Carl Zwanzig wrote:
On 1/13/2024 7:37 PM, DEF wrote:
...other times you want to trim,..
...(I prefer frame numbers, myself.)
I wholeheartedly agree with you, Carl. For
On 13/01/2024 22.57, Carl Zwanzig wrote:
On 1/13/2024 7:37 PM, DEF wrote:
...other times you want to trim,..
...(I prefer frame numbers, myself.)
I wholeheartedly agree with you, Carl. For example:
-ss 20.061708 -to 5570.815250
would be
-frametrim 481..134046
meaning frame 481 thru frame
concerns here and try to gain help/confirmation/clarification here.
--Mark.
On 13/01/2024 22.11, Andrew Randrianasulu wrote:
On Sat, Jan 13, 2024 at 10:27 PM Mark Filipak
wrote:
On 13/01/2024 12.50, Andrew Randrianasulu wrote:
On Sat, Jan 13, 2024 at 8:57 PM Def Etienne wrote:
-snip
On 13/01/2024 22.58, Andrew Randrianasulu wrote:
вс, 14 янв. 2024 г., 06:51 Mark Filipak :
On 13/01/2024 22.11, Andrew Randrianasulu wrote:
-snip-
I added ticket about ffprobe/vf_showinfo displaying truncated duration:
https://trac.ffmpeg.org/ticket/10799#ticket
Andrew, please remove
On 13/01/2024 22.11, Andrew Randrianasulu wrote:
-snip-
I added ticket about ffprobe/vf_showinfo displaying truncated duration:
https://trac.ffmpeg.org/ticket/10799#ticket
Andrew, please remove that ticket. It is too early.
Your "How to reproduce" command line is incomplete and it doesn't
What's the difference?
-t duration (input/output)
When used as an input option (before -i), limit the duration of data read
from the input file.
When used as an output option (before an output url),
stop writing the output after its duration reaches duration.
duration must be a
On 13/01/2024 13.22, DEF wrote:
As long as you are not encoding the video, ffmpeg will cut at the
nearest iframes.
That appears to be not true. ffmpeg appears to cut at the next frame, not the
nearest frame.
If you are particular then you need to re-encode the video.
That is not true.
On 13/01/2024 12.50, Andrew Randrianasulu wrote:
On Sat, Jan 13, 2024 at 8:57 PM Def Etienne wrote:
-snip-
ffmpeg -i ~/6029.mp4 -copyts c:v copy -c:acopy -t 64.600 dev/shm/6029_cut.mp4
According to Devon Heitmueller -- thanks again, Devon -- '-copyts' and
'-muxdelay 0' are _both_ needed.
On 1/10/24 16:50, Devin Heitmueller wrote:
On Wed, Jan 10, 2024 at 4:26 PM Mark Filipak wrote:
The change from 1048560 to 1174560 has to be happening inside the muxer,
wouldn't you say? We now
know that what's going into the muxer is right. Here is what went to the target
file in the last
On 1/10/24 16:50, Devin Heitmueller wrote:
On Wed, Jan 10, 2024 at 4:26 PM Mark Filipak wrote:
The change from 1048560 to 1174560 has to be happening inside the muxer,
wouldn't you say? We now
know that what's going into the muxer is right. Here is what went to the target
file in the last
On 1/10/24 15:46, Mark Filipak wrote:
On 1/10/24 13:55, Devin Heitmueller wrote:
On Wed, Jan 10, 2024 at 1:42 PM Mark Filipak wrote:
Thanks, Devin, but nope, they're a lot closer but they're still not the same.
set FORCE=-bsf:v setts=dts=DTS:pts=PTS
set SOURCE=h:\BDMV\STREAM\00305.m2ts
On 1/10/24 13:55, Devin Heitmueller wrote:
On Wed, Jan 10, 2024 at 1:42 PM Mark Filipak wrote:
Thanks, Devin, but nope, they're a lot closer but they're still not the same.
set FORCE=-bsf:v setts=dts=DTS:pts=PTS
set SOURCE=h:\BDMV\STREAM\00305.m2ts
: IS: 0,1044806,1048560
Correction...
On 1/10/24 13:21, Devin Heitmueller wrote:
On Wed, Jan 10, 2024 at 12:50 PM Mark Filipak
wrote:
Question: How can I force the target's DTS to be the source's DTS?
Add "-copyts" to the front of the command-line as a global option.
The ffmpeg application will aut
On 1/10/24 13:21, Devin Heitmueller wrote:
On Wed, Jan 10, 2024 at 12:50 PM Mark Filipak
wrote:
Question: How can I force the target's DTS to be the source's DTS?
Add "-copyts" to the front of the command-line as a global option.
The ffmpeg application will automatically rebase
Question: How can I force the target's DTS to be the source's DTS?
I'm simply demuxing and remuxing.
To make the targets:
set FORCE=-bsf:v setts=dts=DTS:pts=PTS
set SOURCE=h:\BDMV\STREAM\00305.m2ts
: IS: 0,1044806,1048560, 3753, 640646, 0x900a1a7a, S=1, 1
ffmpeg -to 39.122
On 1/9/24 07:04, Rob Hallam wrote:
On Mon, 8 Jan 2024 at 23:02, Mark Filipak wrote:
[explanation snipped]
Oh, I think I see why your difficulty, Rob.
Thank you for taking the time to write the explanations, they are much
appreciated.
My difficulty, as you guessed, is I don't know about
On 1/8/24 01:46, Andrew Randrianasulu wrote:
пн, 8 янв. 2024 г., 09:13 Mark Filipak :
On 1/8/24 00:26, Andrew Randrianasulu wrote:
пн, 8 янв. 2024 г., 05:14 Mark Filipak :
What is it that you want to know?
I think I like to try and see bigger picture behind acronyms.
What acronyms?
SAR
On 1/8/24 08:08, Rob Hallam wrote:
On Mon, 8 Jan 2024 at 12:37, Mark Filipak wrote:
On 1/8/24 07:16, Rob Hallam wrote:
On Mon, 8 Jan 2024 at 12:07, Mark Filipak wrote:
For example, if 'v' (video) and 'a' (audio) packets go from
v-a-a-a-a-v-a-a-a-a-v... to
a-a-a-a-a-a-a-a-v-v-v
On 1/8/24 08:23, Bouke / Videotoolshed wrote:
For clarity, I wasn't accusing you of lying and it certainly wasn't my
intention to imply that; my apologies if it sounded that way!
Don’t feed the trolls
Bouke, are you calling me a troll?
-- Mark.
On 1/8/24 07:16, Rob Hallam wrote:
On Mon, 8 Jan 2024 at 12:07, Mark Filipak wrote:
For example, if 'v' (video) and 'a' (audio) packets go from
v-a-a-a-a-v-a-a-a-a-v... to
a-a-a-a-a-a-a-a-v-v-v..., then somethings wrong, eh? That's the kind of
difference I'm seeing
between the two versions
On 1/8/24 00:34, Andrew Randrianasulu wrote:
пн, 8 янв. 2024 г., 07:02 Mark Filipak :
I think some of Mark's problems might steam from fact he apparently cuts
blu-ray transport stream, not something commonly cut with ffmpeg.
Yes, but not quite true. I'm cutting, '-ss 20.062', but remuxing
On 1/8/24 01:46, Andrew Randrianasulu wrote:
Well, here lies the problem for us!
Ffmpeg (command line utility) encodes those files straight away, so for
example VLC displays them correctly. But our software (cinelerra-gg) so far
was not setting st->sample_aspect_ratio so say webm encodes were
On 1/8/24 00:26, Andrew Randrianasulu wrote:
пн, 8 янв. 2024 г., 05:14 Mark Filipak :
What is it that you want to know?
I think I like to try and see bigger picture behind acronyms.
What acronyms?
At least this page explains how some 640*480 files might be born (it
should be 486
On 1/7/24 22:12, Jim DeLaHunt wrote:
For instance, this command:
> ffmpeg -f lavfi -i "testsrc" -to 1:00 testpat.m2ts
generates a 60-second video with a test pattern. Anyone with recent FFmpeg can generate a video like
this, though perhaps not identical. If you use this as your "mother"
1 - 100 of 955 matches
Mail list logo
