On Thu, Jan 28, 2021 at 02:41:46PM +0100, Tomas Härdin wrote:
> tor 2021-01-28 klockan 21:08 +0800 skrev lance.lmw...@gmail.com:
> > On Thu, Jan 28, 2021 at 10:26:03AM +0100, emco...@ffastrans.com wrote:
> > > Am 2021-01-28 02:21, schrieb lance.lmw...@gmail.com:
> > > > I haven't found the s337m fr
tor 2021-01-28 klockan 21:08 +0800 skrev lance.lmw...@gmail.com:
> On Thu, Jan 28, 2021 at 10:26:03AM +0100, emco...@ffastrans.com wrote:
> > Am 2021-01-28 02:21, schrieb lance.lmw...@gmail.com:
> > > I haven't found the s337m freely, so I'm not sure about the Platforma
> > > metadata.
> > > I thin
On Thu, Jan 28, 2021 at 10:26:03AM +0100, emco...@ffastrans.com wrote:
> Am 2021-01-28 02:21, schrieb lance.lmw...@gmail.com:
> > I haven't found the s337m freely, so I'm not sure about the Platforma
> > metadata.
> > I think we haven't support the field yet, I guess it's 0x3C08 tag, but I
> > have
Am 2021-01-28 02:21, schrieb lance.lmw...@gmail.com:
I haven't found the s337m freely, so I'm not sure about the Platforma
metadata.
I think we haven't support the field yet, I guess it's 0x3C08 tag, but
I haven't
the document in hand so it's not OK to add it by me.
Yeah the SMPTE are unfortu
On Wed, Jan 27, 2021 at 08:42:40AM +0100, Tobias Rapp wrote:
> On 26.01.2021 16:39, Tomas Härdin wrote:
> > tis 2021-01-26 klockan 00:34 +0100 skrev Marton Balint:
> > > Maybe they should post patches instead of having workarounds? And I
> > > explained, libavformat MXF muxer will still be identifi
On 26.01.2021 16:39, Tomas Härdin wrote:
tis 2021-01-26 klockan 00:34 +0100 skrev Marton Balint:
Maybe they should post patches instead of having workarounds? And I
explained, libavformat MXF muxer will still be identifiable, but the
proper field will be used for identifying the SDK used, not
Co
tis 2021-01-26 klockan 00:34 +0100 skrev Marton Balint:
> On Mon, 25 Jan 2021, emco...@ffastrans.com wrote:
> > Uhm guys, it is very bad practice: if you just insert a different
> > manufacturer name then you just cheat. SMPTE 377 has a clear statement
> > about what goes to the identification, y
Am 2021-01-26 00:34, schrieb Marton Balint:
Uhm guys, it is very bad practice: if you just insert a different
manufacturer name then you just cheat. SMPTE 377 has a clear statement
about what goes to the identification, you cannot just write the infos
from a different program there.
Libavfor
On 25.01.2021 20:40, emco...@ffastrans.com wrote:
[...]
What you can do instead is to push both identifications, the old one and
the one from the current program into the identification array, this way
the processing chain can be reconstructed. Unforutnately i have never
seen anyone doing thi
On Mon, 25 Jan 2021, emco...@ffastrans.com wrote:
Am 2021-01-20 16:41, schrieb Tomas Härdin:
ons 2021-01-20 klockan 00:27 +0100 skrev Marton Balint:
On Tue, 19 Jan 2021, Tobias Rapp wrote:
> On 18.01.2021 23:53, Tomas Härdin wrote:
> > lör 2021-01-16 klockan 08:43 +0800 skrev lance.lmw...@
Am 2021-01-20 16:41, schrieb Tomas Härdin:
ons 2021-01-20 klockan 00:27 +0100 skrev Marton Balint:
On Tue, 19 Jan 2021, Tobias Rapp wrote:
> On 18.01.2021 23:53, Tomas Härdin wrote:
> > lör 2021-01-16 klockan 08:43 +0800 skrev lance.lmw...@gmail.com:
> > > On Fri, Jan 15, 2021 at 09:43:58PM +0
ons 2021-01-20 klockan 00:27 +0100 skrev Marton Balint:
>
> On Tue, 19 Jan 2021, Tobias Rapp wrote:
>
> > On 18.01.2021 23:53, Tomas Härdin wrote:
> > > lör 2021-01-16 klockan 08:43 +0800 skrev lance.lmw...@gmail.com:
> > > > On Fri, Jan 15, 2021 at 09:43:58PM +0100, Marton Balint wrote:
> > > >
On Tue, 19 Jan 2021, Tobias Rapp wrote:
On 18.01.2021 23:53, Tomas Härdin wrote:
lör 2021-01-16 klockan 08:43 +0800 skrev lance.lmw...@gmail.com:
On Fri, Jan 15, 2021 at 09:43:58PM +0100, Marton Balint wrote:
On Fri, 15 Jan 2021, Tomas Härdin wrote:
Again, why? If you have a company that
On 18.01.2021 23:53, Tomas Härdin wrote:
lör 2021-01-16 klockan 08:43 +0800 skrev lance.lmw...@gmail.com:
On Fri, Jan 15, 2021 at 09:43:58PM +0100, Marton Balint wrote:
On Fri, 15 Jan 2021, Tomas Härdin wrote:
Again, why? If you have a company that maintains a fork of FFmpeg then
compile that
lör 2021-01-16 klockan 08:43 +0800 skrev lance.lmw...@gmail.com:
> On Fri, Jan 15, 2021 at 09:43:58PM +0100, Marton Balint wrote:
> >
> > On Fri, 15 Jan 2021, Tomas Härdin wrote:
> > > Again, why? If you have a company that maintains a fork of FFmpeg then
> > > compile that info in here instead. C
On Fri, Jan 15, 2021 at 09:43:58PM +0100, Marton Balint wrote:
>
>
> On Fri, 15 Jan 2021, Tomas Härdin wrote:
>
> > lör 2021-01-09 klockan 13:07 +0800 skrev lance.lmw...@gmail.com:
> > > From: Limin Wang
> > >
> > > The metadata company_name, product_name, product_version from input
> > > file
On Fri, 15 Jan 2021, Tomas Härdin wrote:
lör 2021-01-09 klockan 13:07 +0800 skrev lance.lmw...@gmail.com:
From: Limin Wang
The metadata company_name, product_name, product_version from input
file will be deleted to avoid overwriting information
Please to test with below command:
./ffmpeg -i
lör 2021-01-09 klockan 13:07 +0800 skrev lance.lmw...@gmail.com:
> From: Limin Wang
>
> The metadata company_name, product_name, product_version from input
> file will be deleted to avoid overwriting information
> Please to test with below command:
> ./ffmpeg -i ../fate-suite/mxf/Sony-1.mxf -
From: Limin Wang
The metadata company_name, product_name, product_version from input
file will be deleted to avoid overwriting information
Please to test with below command:
./ffmpeg -i ../fate-suite/mxf/Sony-1.mxf -c:v copy -c:a copy out.mxf
and
./ffmpeg -i ../fate-suite/mxf/Sony-1.mxf -
19 matches
Mail list logo