From: Nomis101 <Nomis101@web.de>
To: ffmpeg-devel@ffmpeg.org
Subject: Re: [FFmpeg-devel] [PATCH] avformat/movenc: Remove experimental status of TrueHD-in-MP4 muxing (mlpa)
Date: Wed, 9 Nov 2022 19:15:36 +0000
Message-ID: <129dce56-74eb-fcb1-d9ce-db47dd197665@web.de> (raw)
In-Reply-To: <CAB0OVGq+3vSuF7iNZMj2pwsbxQxd2m-aq_p_D=RSP7A6Bf8GKw@mail.gmail.com>
Am 06.11.22 um 21:57 schrieb Carl Eugen Hoyos:
> Am Sa., 5. Nov. 2022 um 22:31 Uhr schrieb Nomis101 <Nomis101@web.de>:
>>
>> Support for mlpa muxing was added back in 2019:
>> http://git.videolan.org/?p=ffmpeg.git;a=commitdiff;h=808a6717e0c584738c60a109afd6d47f4973d619
>> But it was hidden back then behind FF_COMPLIANCE_EXPERIMENTAL, because it was new and there was no
>> support from other applications.
>>
>> In the meantime there is support in MediaInfo: MediaArea/MediaInfoLib#1258
>> For VLC: videolan/vlc@9c49f40
>> Since version 7.3.4 for Infuse: https://community.firecore.com/t/dolby-mlp-mlpa-codec-support/26100/31
>> And mpv does support this as well.
>
> If there was ever a good reason to make this feature experimental,
> I don't think these applications change the situation.
The reason to make this experimental was, because there was no implementation from others at this time.
http://ffmpeg.org/pipermail/ffmpeg-devel/2019-August/248435.html
Now, there is implementation from others. How many implementation from others will be needed to
change the situation?
>
> Carl Eugen
> _______________________________________________
> ffmpeg-devel mailing list
> ffmpeg-devel@ffmpeg.org
> https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
>
> To unsubscribe, visit link above, or email
> ffmpeg-devel-request@ffmpeg.org with subject "unsubscribe".
_______________________________________________
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
To unsubscribe, visit link above, or email
ffmpeg-devel-request@ffmpeg.org with subject "unsubscribe".
next prev parent reply other threads:[~2022-11-09 19:15 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-05 21:31 Nomis101
2022-11-06 21:40 ` Nomis101
2022-11-06 21:44 ` James Almer
2022-11-06 21:48 ` James Almer
2022-11-06 21:57 ` Carl Eugen Hoyos
2022-11-09 19:15 ` Nomis101 [this message]
2022-11-11 14:05 ` Jan Ekström
2022-11-11 14:48 ` Nomis101
2022-11-11 15:05 ` Nomis101
2022-11-11 16:16 ` Gijs Peskens
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=129dce56-74eb-fcb1-d9ce-db47dd197665@web.de \
--to=nomis101@web.de \
--cc=ffmpeg-devel@ffmpeg.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
This inbox may be cloned and mirrored by anyone:
git clone --mirror https://master.gitmailbox.com/ffmpegdev/0 ffmpegdev/git/0.git
# If you have public-inbox 1.1+ installed, you may
# initialize and index your mirror using the following commands:
public-inbox-init -V2 ffmpegdev ffmpegdev/ https://master.gitmailbox.com/ffmpegdev \
ffmpegdev@gitmailbox.com
public-inbox-index ffmpegdev
Example config snippet for mirrors.
AGPL code for this site: git clone https://public-inbox.org/public-inbox.git