On 2/29/20 12:36 PM, Paul B Mahol wrote:
None, just use recent ffmpeg version, and it will decode full
DTS-HD-MA just fine.
On 2/29/20 12:36 PM, Carl Eugen Hoyos wrote:
> No, FFmpeg by default decides the lossless DTS HD Master stream.
Thanks!
--
=
Is this a showinfo bug, or am I misinterpreting the results?
For VOBs that are known to be 23.976 FPS, soft-telecined, this command:
'ffprobe -f lavfi movie=VTS_01_1.VOB,showinfo'
reports that they're 59.94 FPS.
The first & last lines of output show this:
"[Parsed_showinfo_1 @ 01d381f6dc80]
On 04/03/2020, Ulf Zibis wrote:
>
> Am 04.03.20 um 00:52 schrieb Carl Eugen Hoyos:
>> Am Mi., 4. März 2020 um 00:50 Uhr schrieb Ulf Zibis :
>>> Am 01.03.20 um 18:13 schrieb Carl Eugen Hoyos:
Both the level and the profile options are mentioned in the
documentation.
>>> But not it's possi
Am 04.03.20 um 00:34 schrieb James Darnley:
On 2020-03-04 00:16, James Darnley wrote:
It is clearly present in the input file's metadata so how is it not
copied into the output file?
Even with normal transcoding "creation_time" is listed in the OUTPUT
metadata, but in the resulting output fil
On 2020-03-04 00:16, James Darnley wrote:
> On 2020-03-03 23:07, Ulf Zibis wrote:
>> $ ~/Projects/ffmpeg/ffmpeg-git-20200211-amd64-static/ffmpeg -i
>> 20200205_165401.mp4 -f ffmetadata 20200205_165401.meta
>
>> Input #0, mov,mp4,m4a,3gp,3g2,mj2, from '20200205_165401.mp4':
>> Metadata:
>> m
Kindly disregard the last message. I don't know how 'metadata' got left
out of the command line...
To me, metadata is such MPEG settings as 'progressive_sequence',
'top_field_first', 'frame_pred_frame_dct', 'concealment_motion_vectors',
'q_scale_type',
'intra_vlc_format', 'alternate_scan', 're
Am 04.03.20 um 00:52 schrieb Carl Eugen Hoyos:
Am Mi., 4. März 2020 um 00:50 Uhr schrieb Ulf Zibis :
Am 01.03.20 um 18:13 schrieb Carl Eugen Hoyos:
Both the level and the profile options are mentioned in the
documentation.
But not it's possible values :-(
As you found out (I didn't know), th
To me, metadata is such MPEG settings as 'progressive_sequence',
'top_field_first', 'frame_pred_frame_dct', 'concealment_motion_vectors',
'q_scale_type',
'intra_vlc_format', 'alternate_scan', 'repeat_first_field',
'chroma_420_type', 'progressive_frame'.
What does ffmpeg consider metadata? I as
Am Mi., 4. März 2020 um 00:50 Uhr schrieb Ulf Zibis :
>
> Am 01.03.20 um 18:13 schrieb Carl Eugen Hoyos:
> > Both the level and the profile options are mentioned in the
> > documentation.
> But not it's possible values :-(
As you found out (I didn't know), the ones that are related to
FFmpeg are m
Am 01.03.20 um 18:13 schrieb Carl Eugen Hoyos:
Both the level and the profile options are mentioned in the
documentation.
But not it's possible values :-(
People knowing how h264 works know about "levels" and "profiles"
May be.
The FFmpeg documentation should not explain what levels and pr
Am Mi., 4. März 2020 um 00:16 Uhr schrieb James Darnley
:
>
> On 2020-03-03 23:07, Ulf Zibis wrote:
> > $ ~/Projects/ffmpeg/ffmpeg-git-20200211-amd64-static/ffmpeg -i
> > 20200205_165401.mp4 -f ffmetadata 20200205_165401.meta
>
> > Input #0, mov,mp4,m4a,3gp,3g2,mj2, from '20200205_165401.mp4':
> >
On 2020-03-03 23:07, Ulf Zibis wrote:
> $ ~/Projects/ffmpeg/ffmpeg-git-20200211-amd64-static/ffmpeg -i
> 20200205_165401.mp4 -f ffmetadata 20200205_165401.meta
> Input #0, mov,mp4,m4a,3gp,3g2,mj2, from '20200205_165401.mp4':
> Metadata:
> major_brand : mp42
> minor_version : 0
>
Am 03.03.20 um 23:16 schrieb Carl Eugen Hoyos:
Am Di., 3. März 2020 um 18:27 Uhr schrieb Ulf Zibis :
ffmpeg -i input.mp4 -f ffmetadata input.meta
This command outputs a new file, ffmpeg does not
copy the creation time of the input file into the
output file.
Yes, exactly that I experienced.
Am 03.03.20 um 21:06 schrieb Paul B Mahol:
http://ffmpeg.org/ffmpeg-formats.html#Metadata-1
I meant, that it is not listed in
https://ffmpeg.org/ffmpeg-formats.html#toc-Muxers as value of option "-f".
Because of this I didn't find "ffmetadata" in the first time.
-Ulf
___
Am Di., 3. März 2020 um 18:27 Uhr schrieb Ulf Zibis :
> ffmpeg -i input.mp4 -f ffmetadata input.meta
This command outputs a new file, ffmpeg does not
copy the creation time of the input file into the
output file.
Carl Eugen
___
ffmpeg-user mailing list
Am 03.03.20 um 21:48 schrieb Nicolas George:
Ulf Zibis (12020-03-03):
Does it have some options to make it output *all* metadata?
It does output all metadata.
No, it misses the creation_time.
See the output from using the example from:
https://ffmpeg.org/ffmpeg-formats.html#Metadata-1
$ ~/
On Tue, 3 Mar 2020 at 21:43, Mohammed Bey Ahmed Khernache
wrote:
>
> Hello,
> which API or plug-in does ffmpeg use to decode HEVC-coded content?
> Is HEVC-Tiles-based parallelism supported by ffmpeg?
>
> Best regards
Hello Ahmed,
There's a native (software-based) HEVC decoder in FFmpeg with the
Am 03.03.20 um 21:48 schrieb Nicolas George:
Ulf Zibis (12020-03-03):
Does it have some options to make it output *all* metadata?
It does output all metadata. Your issue is before.
before what?
-Ulf
___
ffmpeg-user mailing list
ffmpeg-user@ffmpeg
Ulf Zibis (12020-03-03):
> Does it have some options to make it output *all* metadata?
It does output all metadata. Your issue is before.
Regards,
--
Nicolas George
signature.asc
Description: PGP signature
___
ffmpeg-user mailing list
ffmpeg-user@
FFMPEG is written in C and I believe it doesn’t use plug-ins or APIs to decode
HEVC.
Paul
> On Mar 3, 2020, at 1:43 PM, Mohammed Bey Ahmed Khernache
> wrote:
>
Hello,
which API or plug-in does ffmpeg use to decode HEVC-coded content?
Is HEVC-Tiles-based parallelism supported by ffmpeg?
B
http://ffmpeg.org/ffmpeg-formats.html#Metadata-1
On 3/3/20, Ulf Zibis wrote:
>
> Am 03.03.20 um 19:00 schrieb Paul B Mahol:
>> ffmetadata is not filter
>
> Sorry, yes, it's a format, but it's missing in documentation either,
> it's only used in an example.
>
> Does it have some options to make it
Am 03.03.20 um 19:00 schrieb Paul B Mahol:
ffmetadata is not filter
Sorry, yes, it's a format, but it's missing in documentation either,
it's only used in an example.
Does it have some options to make it output *all* metadata?
Remember on not top posting. ;-)
-Ulf
_
Hello,
which API or plug-in does ffmpeg use to decode HEVC-coded content?
Is HEVC-Tiles-based parallelism supported by ffmpeg?
Best regards
___
ffmpeg-user mailing list
ffmpeg-user@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-user
To unsubscrib
ffmetadata is not filter
On 3/3/20, Ulf Zibis wrote:
> Hi,
>
> with
> ffmpeg -i input.mp4 -f ffmetadata input.meta
> I get only:
> ;FFMETADATA1
> major_brand=mp42
> minor_version=0
> compatible_brands=isommp42
> com.android.version=8.0.0
> location=-00.7655-047.1715/
> location-eng=-00.7655-047.1
Hi,
with
ffmpeg -i input.mp4 -f ffmetadata input.meta
I get only:
;FFMETADATA1
major_brand=mp42
minor_version=0
compatible_brands=isommp42
com.android.version=8.0.0
location=-00.7655-047.1715/
location-eng=-00.7655-047.1715/
encoder=Lavf58.38.100
So I'm missing "creation_time".
ffprobe lists:
cr
Am 01.03.20 um 14:55 schrieb Reino Wijnsma:
On 2020-02-27T13:23:02+0100, Ulf Zibis wrote:
unfortunately I now see, that there is a problem with that. Some other
tags were completely removed, e.g. creation time, geo tags, etc
What must I do to preserve all tags?
I believe the -map_metadata op
Am 03.03.2020 um 10:52 schrieb Paul B Mahol:
Hi,
On 3/3/20, Michael Koch wrote:
I'd like to stitch two fisheye videos together to an equirectangular
video. The input videos have larger than 180° field of view, so that
there is an overlap region and I want to use the maskedmerge filter for
merg
Hi,
On 3/3/20, Michael Koch wrote:
> I'd like to stitch two fisheye videos together to an equirectangular
> video. The input videos have larger than 180° field of view, so that
> there is an overlap region and I want to use the maskedmerge filter for
> merging the videos.
> My first (successful)
I'd like to stitch two fisheye videos together to an equirectangular
video. The input videos have larger than 180° field of view, so that
there is an overlap region and I want to use the maskedmerge filter for
merging the videos.
My first (successful) test is with png images:
First create the
Or am I misinterpreting the results?
Regards,
Mark.
This command:
'ffprobe -f lavfi movie=VTS_01_1.VOB,showinfo'
claims that the VOBs (which definitely contain 24/1001 FPS,
soft-telecined video) are 59.94 FPS.
The first & last lines of output show this:
"[Parsed_showinfo_1 @ 01d381f6dc80]
30 matches
Mail list logo