Hi;
Been a while since I submitted something.
Attached patch enabled D3D11 input for the MF encoder.
Regards
Erik
0001-Allow-the-h264_mf-encoder-to-use-ID3D11Texture2D-fra.patch
Description: Binary data
___
ffmpeg-devel mailing list
ffmpeg-devel
-= (1LL<<32)*(221/100)*(1080/1920)
is smaller than
error -= (1LL<<32)*(16/9)*(1080/1920)
thus picking aspect index value 4 rather than 3.
Proposed fix in attached patch.
--
Erik Johansson
mpeg2_aspect.patch
Description: Binary data
___
On Thu, Dec 4, 2014 at 5:27 PM, Michael Niedermayer wrote:
>
> On Thu, Dec 04, 2014 at 01:11:08PM +0100, Erik Johansson wrote:
> > Hi,
> >
> > Setting setting sample_aspect_ratio in AVContext does not produce the
> > expected aspect index value in the MPEG2 sequence
Spec: https://developers.google.com/streetview/publish/camm-spec
The Lenovo Mirage camera launched recently and outputs this metadata track
in its videos.
From 937a49d00139edfc8cc5eda9234c2b8afbaa4773 Mon Sep 17 00:00:00 2001
From: Erik Ackermann
Date: Mon, 21 May 2018 11:42:04 -0700
Subject
during the copy (but tmcd track is not).
On Mon, May 21, 2018 at 12:58 PM, Rostislav Pehlivanov
wrote:
> On 21 May 2018 at 19:52, Erik Ackermann
> wrote:
>
> > Spec: https://developers.google.com/streetview/publish/camm-spec
> >
> > The Lenovo Mirage camera launched recen
According to the format specification (3GPP TS 26.245, section 5.2) "storage
lengths are specified as byte-counts, wheras highlighting is specified using
character offsets." This patch replaces byte counting with character counting
for highlighting. See the following page for a link to the specific
Character offsets were interpreted as byte offsets, resulting in misplaced
styling tags where multibyte characters were involved. The entire subtitle
stream would even be rendered invalid if such a misplaced tag happened to
split a multibyte character. This patch fixes this for UTF-8; UTF-16 was an
According to the format specification (3GPP TS 26.245, section 5.2) "storage
lengths are specified as byte-counts, wheras highlighting is specified using
character offsets." This patch replaces byte counting with character counting
for highlighting. See the following page for a link to the specific
Yes, it was supposed to be box_types, not ox_types. I must have removed the b
by mistake after I tested the code. Should I resubmit the patch?
___
ffmpeg-devel mailing list
[email protected]
http://ffmpeg.org/mailman/listinfo/ffmpeg-devel
Good question. Since text_pos_chars never exceeds the existing
variable text_pos, I did not think about this.
No, there are no checks. The spec says that "Authors should limit the
string in each text sample to not more than 2048 bytes, for maximum
terminal interoperability", but the code does not
Between testing and patch generation a character was deleted by mistake, which
broke the patch. This updated version fixes this.
Original patch description:
Character offsets were interpreted as byte offsets, resulting in misplaced
styling tags where multibyte characters were involved. The entire
Done. It was assigned its own patch number (1860), so I am changing the state
of this one to "Superseded".
___
ffmpeg-devel mailing list
[email protected]
http://ffmpeg.org/mailman/listinfo/ffmpeg-devel
Accidental duplicate of patch 1818.
___
ffmpeg-devel mailing list
[email protected]
http://ffmpeg.org/mailman/listinfo/ffmpeg-devel
The 3GPP Timed Text (TTXT / tx3g / mov_text) specification counts multibyte
UTF-8 characters as one single character, ffmpeg currently counts bytes. This
produces files where style boxes have incorrect offsets. This patch introduces:
1. a separate variable that keeps track of the byte count
2. a
The 3GPP Timed Text (TTXT / tx3g / mov_text) specification counts multibyte
UTF-8 characters as one single character, ffmpeg currently counts bytes. This
patch inserts an if test such that:
1. continuation bytes are not counted during decoding
2. style boxes will not split these characters
Fixes
Signed-off-by: Erik Bråthen Solem
---
libavdevice/avfoundation.m | 4
1 file changed, 4 insertions(+)
diff --git a/libavdevice/avfoundation.m b/libavdevice/avfoundation.m
index c5a09c6563..779bc767d6 100644
--- a/libavdevice/avfoundation.m
+++ b/libavdevice/avfoundation.m
@@ -763,6 +763,10 @@
I have very little experience with mailing lists, my apologies if this
reply does not end up where it is supposed to be.
The Apple developer docs say that AVMediaType is a struct, but it looks
seems that in reality it is typedef-ed to NSString*, just with an extra
specifier NS_EXTENSIBLE_STRING_EN
th iOS 11. The AVMediaType alias is itself typedef-ed to NSString* with
an extra specifier in the newer SDKs.
Signed-off-by: Erik Bråthen Solem
---
libavdevice/avfoundation.m | 4
1 file changed, 4 insertions(+)
diff --git a/libavdevice/avfoundation.m b/libavdevice/avfoundation.m
index c5a0
18 matches
Mail list logo
