On 2021-05-24 22:15, Andreas Rheinhardt wrote:
michael.di...@xaymar.com:
From: Michael Fabian 'Xaymar' Dirks
Adds "timestamp_precision" to the available options for Matroska muxing.
The option enables users and developers to change the precision of the
time stamps in the M
On 2021-05-21 02:45, James Almer wrote:
On 5/20/2021 9:29 PM, michael.di...@xaymar.com wrote:
From: Michael Fabian 'Xaymar' Dirks
Adds "timestamp_precision" to the available options for Matroska muxing.
The option enables users and developers to change the precision of th
On 2021-05-21 01:42, James Almer wrote:
On 5/20/2021 8:24 PM, michael.di...@xaymar.com wrote:
From: Michael Fabian 'Xaymar' Dirks
Adds "timestamp_precision" to the available option for Matroska muxing.
The option enables users and developers to change the precision of th
On 2021-05-21 00:37, James Almer wrote:
On 5/20/2021 7:33 PM, Michael Fabian 'Xaymar' Dirks wrote:
On 2021-05-21 00:30, Michael Fabian 'Xaymar' Dirks wrote:
On 2021-05-21 00:25, James Almer wrote:
On 5/20/2021 7:20 PM, Lynne wrote:
May 20, 2021, 20:08 by jamr...@gmail.c
On 2021-05-21 00:30, Michael Fabian 'Xaymar' Dirks wrote:
On 2021-05-21 00:25, James Almer wrote:
On 5/20/2021 7:20 PM, Lynne wrote:
May 20, 2021, 20:08 by jamr...@gmail.com:
On 5/20/2021 3:00 PM, Michael Fabian 'Xaymar' Dirks wrote:
On 2021-05-20 19:26, James Almer wro
On 2021-05-21 00:25, James Almer wrote:
On 5/20/2021 7:20 PM, Lynne wrote:
May 20, 2021, 20:08 by jamr...@gmail.com:
On 5/20/2021 3:00 PM, Michael Fabian 'Xaymar' Dirks wrote:
On 2021-05-20 19:26, James Almer wrote:
On 5/20/2021 2:18 PM, michael.di...@xaymar.com wrote:
Fro
On 2021-05-20 23:47, James Almer wrote:
On 5/20/2021 4:35 PM, Michael Fabian 'Xaymar' Dirks wrote:
On 2021-05-20 21:16, michael.di...@xaymar.com wrote:
From: Michael Fabian 'Xaymar' Dirks
Adds "timestamp_precision" to the available option for Matroska/WebM
mu
On 2021-05-20 21:20, Nicolas George wrote:
Michael Fabian 'Xaymar' Dirks (12021-05-20):
There are plenty of reasons to know the actual frame rate with high
precision.
Editing software needs to know this to initialize effects, timelines
and projects.
I doubt they do that without b
On 2021-05-20 21:16, michael.di...@xaymar.com wrote:
From: Michael Fabian 'Xaymar' Dirks
Adds "timestamp_precision" to the available option for Matroska/WebM
muxing. The option enables users and developers to change the precision
of the time stamps in the Matroska/We
On 2021-05-20 20:54, Nicolas George wrote:
Michael Fabian 'Xaymar' Dirks (12021-05-20):
Well, it's a combination of many things really, not bad math itself.
1ms works perfectly for the frame rates of 1, 2, 4, 5, 8, 10, 20, 25,
40, 50, 100, 125, 200, 250, 500, and 1000. For any
On 2021-05-20 20:23, James Almer wrote:
On 5/20/2021 2:59 PM, Nicolas George wrote:
Michael Fabian 'Xaymar' Dirks (12021-05-20):
The issue can't be fixed
Then you should not be hiding the warning. It means something.
It means that the container does not support values bigger
On 2021-05-20 20:14, Nicolas George wrote:
Michael Fabian 'Xaymar' Dirks (12021-05-20):
The default precision for Matroska is 1ms not 1µs. 1µs is plenty
enough, but 1ms is not.
I am not even convinced that most problems with 1ms are not caused by
bad math, but I am willing to see pro
On 2021-05-20 19:59, Nicolas George wrote:
Michael Fabian 'Xaymar' Dirks (12021-05-20):
The issue can't be fixed
Then you should not be hiding the warning. It means something.
I was asked to fix or remove it. Removing it breaks Matroska files entirely.
Fixing it is not possi
On 2021-05-20 19:26, James Almer wrote:
On 5/20/2021 2:18 PM, michael.di...@xaymar.com wrote:
From: Michael Fabian 'Xaymar' Dirks
Adds "timestamp_precision" to the available option for Matroska/WebM
muxing. The option enables users and developers to change the precision
o
On 2021-05-20 19:38, Nicolas George wrote:
Michael Fabian 'Xaymar' Dirks (12021-05-20):
Unfortunately I was not able to get rid of the new cluster spam, so I
moved it down a few logging levels into "verbose".
So you silenced the warning, but did not fix the issue it was wa
On 2021-05-20 19:18, michael.di...@xaymar.com wrote:
From: Michael Fabian 'Xaymar' Dirks
Adds "timestamp_precision" to the available option for Matroska/WebM
muxing. The option enables users and developers to change the precision
of the time stamps in the Matroska/We
On 2021-05-19 17:14, Lynne wrote:
May 19, 2021, 17:12 by d...@lynne.ee:
May 19, 2021, 03:44 by michael.di...@xaymar.com:
From: Michael Fabian 'Xaymar' Dirks
Adds the "timestamp_precision" option to matroskaenc, which allows users
to increase the time stamp precisio
On 2021-05-19 17:12, Lynne wrote:
May 19, 2021, 03:44 by michael.di...@xaymar.com:
From: Michael Fabian 'Xaymar' Dirks
Adds the "timestamp_precision" option to matroskaenc, which allows users
to increase the time stamp precision up to 1 nanosecond. This aids with
ce
On 2021-05-19 03:44, michael.di...@xaymar.com wrote:
From: Michael Fabian 'Xaymar' Dirks
Adds the "timestamp_precision" option to matroskaenc, which allows users
to increase the time stamp precision up to 1 nanosecond. This aids with
certain demuxers being unable to detect
failed to detect constant rate from FFmpeg
muxed MKV/WebM files.
--
Sincerely | Mit freundlichen Grüßen
Michael Fabian 'Xaymar' Dirks
Software Designer & Engineer
___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
https://ffmpeg.org/ma
On 2021-05-19 01:47, michael.di...@xaymar.com wrote:
From: Michael Fabian 'Xaymar' Dirks
Increases the time stamp precision to 1 microsecond, the same as
AV_TIME_BASE. This hopefully prevents demuxers from being confused on
the number of frames/samples we actually have per second,
On 2021-05-18 22:04, Michael Fabian 'Xaymar' Dirks wrote:
Hello,
while tracking some time stamp issues unique to FFmpeg I noticed
AV_Time_BASE(_Q) being present quite often, which appears to be a value to
define time stamps in milliseconds. Tracking it back to its origin I could
On 2021-05-18 22:09, Nicolas George wrote:
Michael Fabian 'Xaymar' Dirks (12021-05-18):
while tracking some time stamp issues unique to FFmpeg I noticed
AV_Time_BASE(_Q) being present quite often, which appears to be a
value to define time stamps in milliseconds. Tracking it back to
ork-around this issue on a muxer/demuxer level, the underlying
issue in FFmpeg would still be present. At the moment, most non-integer ms framerates and
sample rates end up performing weird without post-processing.
--
Sincerely | Mit freundlichen Grüßen
Michael Fabian
> Client should allocate output buffers according to this dimension for
dynamic resolution change. If set to 0, Encoder will not allow dynamic
resolution change.
--
Sincerely | Mit freundlichen Grüßen
Michael Fabian 'Xaymar' Dirks
PS: I apologize if I made any mistake replying
AV_PICTURE_TYPE_S for marking Skip frames, a special
type of frame in AVC, SVC and HEVC which is a flag for the decoder to repeat
the last frame.
Signed-off-by: Michael Fabian 'Xaymar' Dirks
---
libavcodec/amfenc.c | 46 +
1 file changed, 46
26 matches
Mail list logo
