On 03/11/2020 09:32 PM, Carl Zwanzig wrote:
On 3/11/2020 6:21 PM, Mark Filipak wrote:
Thunderbird, for example, wraps text at 70 chars when sent. I believe the 70 chars cannot be changed.
In Options, Advanced, General, Config editor-
set mailnews.wraplength to the desired wrap distance.
Hi,
Glad you were able to figure out how to filter/remap to get the desired effect.
> ...
>
> Probably, but that’s beside the issue, it’s not up to me what end users want
> to map to where :-)
>
Oh right! I thought this was a personal project for some reason, that you were
the one making the
On 03/11/2020 09:32 PM, Carl Zwanzig wrote:
On 3/11/2020 6:21 PM, Mark Filipak wrote:
Thunderbird, for example, wraps text at 70 chars when sent. I believe the 70 chars cannot be changed.
In Options, Advanced, General, Config editor-
set mailnews.wraplength to the desired wrap distance.
On 3/11/2020 6:21 PM, Mark Filipak wrote:
Thunderbird, for example, wraps text at 70 chars when sent. I believe the 70
chars cannot be changed.
In Options, Advanced, General, Config editor-
set mailnews.wraplength to the desired wrap distance.
OTOH, it's probably not a good idea to make this
Hi,
> ... and how can I avoid this, or which argument should I pass to
> -video_track_timescale ?
Passing the timescale to that option would work I think.
> frame= 32 fps=0.0 q=0.0 size= 0kB time=00:00:01.42 bitrate=
> 0.2kbits/sframe= 47 fps= 40 q=0.0 size= 0kB
On 03/11/2020 09:04 PM, Ulf Zibis wrote:
Am 12.03.20 um 01:40 schrieb Ted Park:
This particular error is because it parsed as video_track_timescale =
-map_metadata and output file named “0”.
... and how can I avoid this, or which argument should I pass to
-video_track_timescale ?
Did you
Am 12.03.20 um 01:40 schrieb Ted Park:
This particular error is because it parsed as video_track_timescale =
-map_metadata and output file named “0”.
... and how can I avoid this, or which argument should I pass to
-video_track_timescale ?
Did you upload a working sample file already? I
Hi,
> [NULL @ 0x56293d1e4d80] Unable to find a suitable output format for '0'
> 0: Invalid argument
This particular error is because it parsed as video_track_timescale =
-map_metadata and output file named “0”.
Did you upload a working sample file already? I want to see how basic the
camera
Am 12.03.20 um 00:07 schrieb Carl Eugen Hoyos:
You can also try -video_track_timescale, this often was the
reason for incompatibilities.
This results in an error (and I too can't find video_track_timescale in
the docs :-( ):
$ ffmpeg -i MVI_1324.MOV -c:a copy -profile:v baseline -level 4.1
Am 12.03.20 um 00:07 schrieb Carl Eugen Hoyos:
Am Mi., 11. März 2020 um 23:56 Uhr schrieb Ulf Zibis :
compatible_brands: qt CAEP
What happens if you remove CAEP with a binary editor?
When I replace CAEP in the original video with 4 0x00 it is still playable.
Here are the first 32
Am 12.03.20 um 00:23 schrieb Carl Eugen Hoyos:
> Am Do., 12. März 2020 um 00:17 Uhr schrieb Reindl Harald
> :
>>
>> Am 11.03.20 um 22:48 schrieb Carl Eugen Hoyos:
>>> Am Mi., 11. März 2020 um 22:44 Uhr schrieb Reindl Harald
>>> :
Am 11.03.20 um 20:02 schrieb Carl Eugen Hoyos:
> Why
Am Do., 12. März 2020 um 00:17 Uhr schrieb Reindl Harald
:
>
>
>
> Am 11.03.20 um 22:48 schrieb Carl Eugen Hoyos:
> > Am Mi., 11. März 2020 um 22:44 Uhr schrieb Reindl Harald
> > :
> >>
> >> Am 11.03.20 um 20:02 schrieb Carl Eugen Hoyos:
> >>> Why do you want to use a newer x264?
> >>>
> >> why do
Am 11.03.20 um 22:48 schrieb Carl Eugen Hoyos:
> Am Mi., 11. März 2020 um 22:44 Uhr schrieb Reindl Harald
> :
>>
>> Am 11.03.20 um 20:02 schrieb Carl Eugen Hoyos:
>>> Why do you want to use a newer x264?
>>>
>> why do you always answer "only current GIT of ffmpeg is supported here"
>
> Because
Am Mi., 11. März 2020 um 23:56 Uhr schrieb Ulf Zibis :
> compatible_brands: qt CAEP
What happens if you remove CAEP with a binary editor?
You can also try -video_track_timescale, this often was the
reason for incompatibilities.
Carl Eugen
___
Am 11.03.20 um 21:04 schrieb Ted Park:
Hi,
Is it thinkable that libx264 could encode with constrained_baseline
profile some day? Currently it only can decode it.
IIRC, contained baseline is no different from the original baseline bitstream
profile, except it has a flag set (or unset). Does
On 03/11/2020 06:45 PM, Carl Eugen Hoyos wrote:
Am Mi., 11. März 2020 um 23:15 Uhr schrieb Mark Filipak
:
On 03/11/2020 06:09 PM, Carl Eugen Hoyos wrote:
Am Mi., 11. März 2020 um 23:05 Uhr schrieb Mark Filipak
:
For what it's worth, though the MPEG encoder specs support full, 16-bit
Am 11.03.20 um 17:28 schrieb Ulf Zibis:
Am 11.03.20 um 13:50 schrieb Moritz Barsnick:
On Wed, Mar 11, 2020 at 13:25:45 +0100, Ulf Zibis wrote:
Anyway, does my command line have the right syntax?
ffmpeg -i MVI_1324.MOV -c:a copy -c:v h264_vaapi -profile:v
constrained_baseline -level 4.1
On 03/11/2020 06:45 PM, Carl Eugen Hoyos wrote:
Am Mi., 11. März 2020 um 23:15 Uhr schrieb Mark Filipak
:
On 03/11/2020 06:09 PM, Carl Eugen Hoyos wrote:
Am Mi., 11. März 2020 um 23:05 Uhr schrieb Mark Filipak
:
For what it's worth, though the MPEG encoder specs support full, 16-bit
Am Mi., 11. März 2020 um 23:17 Uhr schrieb Ted Park :
> > All features specific to "baseline" (which do not exist in main and
> > high) are neither
> > supported by any available H.264 encoder nor decoder (including libavcodec).
> > All this features were removed for "constrained baseline" which
On 03/11/2020 06:41 PM, Ted Park wrote>> haven't spent the $5-thousand
for the DVD spec
Isn’t that just to be a subscriber/member?? I think it’s a bit more than that
if you want the whole DVD specs… DVD has been reverse engineered pretty
extensively though, shouldn’t be too difficult to find
Am Mi., 11. März 2020 um 23:15 Uhr schrieb Mark Filipak
:
>
> On 03/11/2020 06:09 PM, Carl Eugen Hoyos wrote:
> > Am Mi., 11. März 2020 um 23:05 Uhr schrieb Mark Filipak
> > :
> >> For what it's worth, though the MPEG encoder specs support full, 16-bit
> >> monochrome (black-&-white) that,
Hello,
>> Because that is what the DVD specification requires.
>> Carl Eugen
>
> Ah! Well, that explains it. Thanks Carl Eugen. I haven't spent the
> $5-thousand for the DVD spec.
>
> By the way, of course, I made a silly mistake. I should have written "full,
> 24-bit monochrome". Ooops.
Hi,
> All features specific to "baseline" (which do not exist in main and
> high) are neither
> supported by any available H.264 encoder nor decoder (including libavcodec).
> All this features were removed for "constrained baseline" which is supported
> by
> all H.264 encoders and all H.264
On 03/11/2020 06:09 PM, Carl Eugen Hoyos wrote:
Am Mi., 11. März 2020 um 23:05 Uhr schrieb Mark Filipak
:
On 03/11/2020 05:48 PM, Carl Eugen Hoyos wrote:
Am Mi., 11. März 2020 um 22:44 Uhr schrieb Reindl Harald
:
Am 11.03.20 um 20:02 schrieb Carl Eugen Hoyos:
Why do you want to use a newer
Am Mi., 11. März 2020 um 23:05 Uhr schrieb Mark Filipak
:
>
> On 03/11/2020 05:48 PM, Carl Eugen Hoyos wrote:
> > Am Mi., 11. März 2020 um 22:44 Uhr schrieb Reindl Harald
> > :
> >>
> >> Am 11.03.20 um 20:02 schrieb Carl Eugen Hoyos:
> >>> Why do you want to use a newer x264?
> >>>
> >> why do you
On 03/11/2020 05:48 PM, Carl Eugen Hoyos wrote:
Am Mi., 11. März 2020 um 22:44 Uhr schrieb Reindl Harald
:
Am 11.03.20 um 20:02 schrieb Carl Eugen Hoyos:
Why do you want to use a newer x264?
why do you always answer "only current GIT of ffmpeg is supported here"
Because the development of
Am Mi., 11. März 2020 um 22:44 Uhr schrieb Reindl Harald
:
>
> Am 11.03.20 um 20:02 schrieb Carl Eugen Hoyos:
> > Why do you want to use a newer x264?
> >
> why do you always answer "only current GIT of ffmpeg is supported here"
Because the development of the two projects is nowadays very
Am 11.03.20 um 20:02 schrieb Carl Eugen Hoyos:
> Why do you want to use a newer x264?
>
> Carl Eugen
why do you always answer "only current GIT of ffmpeg is supported here"
to *any* question on this and then come up with a dumb "why to you want
to use a recent dependency of ffmpeg"
you have
On 03/11/2020 03:21 PM, Lou Logan wrote:
On Wed, Mar 11, 2020, at 10:51 AM, Ulf Zibis wrote:
Does John van Sickle's binary use a current version?
See the build info / readme for a list of external library versions:
https://johnvansickle.com/ffmpeg/git-readme.txt
How can I use a more
Hello,
ffmpeg -loglevel verbose -i
"concat:VTS_06_1.VOB|VTS_06_2.VOB|VTS_06_3.VOB|VTS_06_4.VOB|VTS_06_5.VOB"
-map 0:v -map 0:a -c:v copy -c:a copy "OUT.mkv"
(1st listing below) provokes a "Can't write packet with unknown
timestamp" error.
Adding '-fflags +genpts', thusly:
ffmpeg
Am Mi., 11. März 2020 um 21:27 Uhr schrieb Ted Park :
>
> Hi,
>
> > Is it thinkable that libx264 could encode with constrained_baseline
> > profile some day? Currently it only can decode it.
>
> IIRC, contained baseline is no different from the original baseline bitstream
> profile
All features
Hi,
> Is it thinkable that libx264 could encode with constrained_baseline
> profile some day? Currently it only can decode it.
IIRC, contained baseline is no different from the original baseline bitstream
profile, except it has a flag set (or unset). Does your decoder refuse to
decode
On Wed, Mar 11, 2020, at 11:50 AM, Ulf Zibis wrote:
>
> Is it thinkable that libx264 could encode with constrained_baseline
> profile some day?
"-profile:v baseline" is Constrained Baseline. You can always refer to
the output of the ffmpeg command to see which profile is being used.
> Currently
Am 11.03.20 um 20:13 schrieb Carl Eugen Hoyos:
To elaborate:
The main differences are:
Unified support for >8 bit
Monochrome encoding
XAVC encoding
The first is really useful but only if you need 10 bit support,
the others should have less relevance.
x264 development has slowed down over time
On Wed, Mar 11, 2020, at 10:51 AM, Ulf Zibis wrote:
>
> Does John van Sickle's binary use a current version?
See the build info / readme for a list of external library versions:
https://johnvansickle.com/ffmpeg/git-readme.txt
> How can I use a more current version with the ffmpeg git version?
Am Mi., 11. März 2020 um 20:02 Uhr schrieb Carl Eugen Hoyos
:
>
> Am Mi., 11. März 2020 um 19:52 Uhr schrieb Ulf Zibis :
> > It seems I'm using a very old version of libx264:
>
> Why do you think so?
To elaborate:
The main differences are:
Unified support for >8 bit
Monochrome encoding
XAVC
Am Mi., 11. März 2020 um 19:52 Uhr schrieb Ulf Zibis :
> $ sudo apt policy libx264*
> libx264-148:
>Installiert: (keine)
>Installationskandidat: (keine)
>Versionstabelle:
> libx264-152:
>Installiert: 2:0.152.2854+gite9a5903-2
>Installationskandidat:
Am 11.03.20 um 18:55 schrieb Carl Eugen Hoyos:
mov defaults to mpeg4 if no h264 encoder is present (you did not specify
--enable-libx264), for mpeg4 "profile baseline" is not defined.
Thanks, it works with:
$ sudo apt install libx264-dev
$ ./configure --enable-libx264 --enable-gpl
$ make
Hi,
> -r 50:1 -vf scale=1920:1080 -pix_fmt yuv420p -c:v prores_ks -profile:v 2
> -c:a pcm_s24le
ProRes doesn’t have a 4:2:0 subsampling profile. There might be other problems,
but try choosing yuv422p10le to start.
Regards,
Ted Park
___
Am Mi., 11. März 2020 um 18:32 Uhr schrieb Ulf Zibis :
> I have build ffmpeg from the latest sources and get this warning and error:
>
> $ ~/Projects/ffmpeg/dev_2/ffmpeg -i MVI_1324.MOV -c:a copy -profile:v
> baseline -level 4.1 -map_metadata 0 -movflags +faststart MVI_1324.mov
> ffmpeg version
Hello,
> I have build ffmpeg from the latest sources and get this warning and error:
>
> $ ~/Projects/ffmpeg/dev_2/ffmpeg -i MVI_1324.MOV -c:a copy -profile:v
> baseline -level 4.1 -map_metadata 0 -movflags +faststart MVI_1324.mov
...
> File 'MVI_1324.mov' already exists. Overwrite? [y/N] y
>
Hi,
I have build ffmpeg from the latest sources and get this warning and error:
$ ~/Projects/ffmpeg/dev_2/ffmpeg -i MVI_1324.MOV -c:a copy -profile:v
baseline -level 4.1 -map_metadata 0 -movflags +faststart MVI_1324.mov
ffmpeg version N-96935-g34d7c8d942 Copyright (c) 2000-2020 the FFmpeg
Am 11.03.20 um 13:50 schrieb Moritz Barsnick:
On Wed, Mar 11, 2020 at 13:25:45 +0100, Ulf Zibis wrote:
Anyway, does my command line have the right syntax?
ffmpeg -i MVI_1324.MOV -c:a copy -c:v h264_vaapi -profile:v
constrained_baseline -level 4.1 MVI_1324.mov
It's syntactically correct, but
On 3/11/2020 9:06 AM, Carl Eugen Hoyos wrote:
They sued because no source code was provided, the question was if
you are allowed to charge money for providing a binary of free software.
IIRC, the issue of charging for the s/w was discussed in those suits (which
weighed on the award of money
Am Mi., 11. März 2020 um 17:05 Uhr schrieb Carl Zwanzig :
>
> On 3/11/2020 8:40 AM, Ted Park wrote:
> > I’m just curious, but if this kind of question was posed to a
> > less-than-scrupulous party, and they sell the querier a compatible binary
> > and source with the GPL license, is there any way
On 3/11/2020 8:40 AM, Ted Park wrote:
I’m just curious, but if this kind of question was posed to a
less-than-scrupulous party, and they sell the querier a compatible binary
and source with the GPL license, is there any way to be recompensed if
he/she finds out it could have been obtained for
Am Mi., 11. März 2020 um 16:46 Uhr schrieb Laurent ROCHER
:
> ffmpeg run well for many videos (Thanks !) but for some I had an error
> message which make me think that I would need a ffmpeg version running
> the 57.56.100 version of libavformat.
>
> On your page https://ffmpeg.org/download.html
Hi,
> > mencoder Cyrano.wmv -ofps 23.976 -ovc lavc -oac copy -o Cyrano.avi
> > MEncoder 1.3.0 (Debian), built with gcc-6.2.1 (C) 2000-2016 MPlayer Team
> > success: format: 0 data: 0x0 - 0x75b09ffa
> > *libavformat version 57.56.101* (external)
> > *Mismatching header version 57.56.100*
>
Did
Hello,
ffmpeg run well for many videos (Thanks !) but for some I had an error
message which make me think that I would need a ffmpeg version running
the 57.56.100 version of libavformat.
On your page https://ffmpeg.org/download.html the version of libavformat
of ffmpeg 3.2.14 is said to be
Am Mi., 11. März 2020 um 16:40 Uhr schrieb Ted Park :
> > You are only allowed to distribute binaries based on FFmpeg source
> > code if you follow the requirements of the GPL or the LGPL depending
> > on compile time options.
> >
> > Since you are using the word "use" three times in your
Hi,
> You are only allowed to distribute binaries based on FFmpeg source
> code if you follow the requirements of the GPL or the LGPL depending
> on compile time options.
>
> Since you are using the word "use" three times in your question:
> Usage of FFmpeg is not restricted as long as you agree
Am Mi., 11. März 2020 um 15:26 Uhr schrieb Ted Park :
> ffmpeg is largely based on free software
Sorry but this is imo misleading:
FFmpeg is 100% free software
Note that for many companies, the (L)GPL version 3 is not usable.
Carl Eugen
___
Am Mi., 11. März 2020 um 14:50 Uhr schrieb Viktoria Zh. :
> Can anyone help me with a license information for commercial use, please?
> We would like to use the FFmpeg for our social network, and I need to
> discuss the terms of such use with someone.
You are only allowed to distribute binaries
On 3/11/2020 8:04 AM, Dennis Mungai wrote:
This response should be a wiki entry. We’ve seen multiple queries on the
same topic on this list, and this response summarizes it perfectly.
Definitely. Now if people would only read it (and the FAQ).
z!
On Wed, 11 Mar 2020 at 17:58, Moritz Barsnick wrote:
> On Wed, Mar 11, 2020 at 10:26:27 -0400, Ted Park wrote:
> > > Where can I find out the cost of a license? Who can I talk to about
> signing
> > > documents?
>
> > I think you misunderstood, ffmpeg is largely based on free software, and
> you
On Wed, Mar 11, 2020 at 10:26:27 -0400, Ted Park wrote:
> > Where can I find out the cost of a license? Who can I talk to about signing
> > documents?
> I think you misunderstood, ffmpeg is largely based on free software, and you
> are granted the license you see when you run ffmpeg -L.
> That
Hi,
> Ted, thank you very much for your answer!
>
> We want to use the FFmpeg solution to let our users recording stories. At
> the same time, the application has a donation function and cryptocurrency.
> We now have about 500,000 users.
> So tell me please.
> Where can I find out the cost of a
Hi,
I'm currently trying to solve this problem: I have a Blackmagic Design
Hyperdeck Studio Mini device, which is both a recorder and player for
professional video (TV studio). But impolite, as the device is, it is
playing only those videos it has recorded itself, and completely
ignoring
Ted, thank you very much for your answer!
We want to use the FFmpeg solution to let our users recording stories. At
the same time, the application has a donation function and cryptocurrency.
We now have about 500,000 users.
So tell me please.
Where can I find out the cost of a license? Who can I
Hi,
> Hello.
>
> Can anyone help me with a license information for commercial use, please?
> We would like to use the FFmpeg for our social network, and I need to
> discuss the terms of such use with someone. Who can I talk about it with?
>
> Many thanks, Victoria Zhuravishkina
>
Depending on
Hello.
Can anyone help me with a license information for commercial use, please?
We would like to use the FFmpeg for our social network, and I need to
discuss the terms of such use with someone. Who can I talk about it with?
Many thanks, Victoria Zhuravishkina
On Wed, Mar 11, 2020 at 13:25:45 +0100, Ulf Zibis wrote:
> Anyway, does my command line have the right syntax?
> ffmpeg -i MVI_1324.MOV -c:a copy -c:v h264_vaapi -profile:v
> constrained_baseline -level 4.1 MVI_1324.mov
It's syntactically correct, but it won't suffice. You need some more
Am 11.03.20 um 13:05 schrieb Moritz Barsnick:
On Wed, Mar 11, 2020 at 00:47:42 +0100, Ulf Zibis wrote:
It looks like it was built without support?
What is the difference, if I build it myself concerning support?
When configuring and building, you need the (development support for)
libva
On Wed, Mar 11, 2020 at 00:47:42 +0100, Ulf Zibis wrote:
> > It looks like it was built without support?
> What is the difference, if I build it myself concerning support?
When configuring and building, you need the (development support for)
libva present. ./configure has this check:
> enabled
On 10.03.20 23:25, Reindl Harald wrote:
Am 10.03.20 um 18:37 schrieb bbb:
On 10.03.20 18:11, Ulf Zibis wrote:
Am 10.03.20 um 17:10 schrieb bbb:
Hi,
I was using ffmpeg from official ubuntu-xenial repositories and was
unable to convert a bunch of files with subtitles ("invalid, non
65 matches
Mail list logo
