From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from ffbox0-bg.mplayerhq.hu (ffbox0-bg.ffmpeg.org [79.124.17.100]) by master.gitmailbox.com (Postfix) with ESMTP id 3C12849697 for ; Sat, 17 Feb 2024 13:16:12 +0000 (UTC) Received: from [127.0.1.1] (localhost [127.0.0.1]) by ffbox0-bg.mplayerhq.hu (Postfix) with ESMTP id 0693568D291; Sat, 17 Feb 2024 15:16:10 +0200 (EET) Received: from mout-p-202.mailbox.org (mout-p-202.mailbox.org [80.241.56.172]) by ffbox0-bg.mplayerhq.hu (Postfix) with ESMTPS id EDBF968CE11 for ; Sat, 17 Feb 2024 15:16:02 +0200 (EET) Received: from smtp202.mailbox.org (smtp202.mailbox.org [IPv6:2001:67c:2050:b231:465::202]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (No client certificate requested) by mout-p-202.mailbox.org (Postfix) with ESMTPS id 4TcTnq737bz9sTJ for ; Sat, 17 Feb 2024 14:15:59 +0100 (CET) Message-ID: <153dfd89-aedd-4704-aef4-15cca7cc541d@gyani.pro> Date: Sat, 17 Feb 2024 18:45:57 +0530 MIME-Version: 1.0 Content-Language: en-US To: ffmpeg-devel@ffmpeg.org References: <9be400cf-949f-4eb1-93a1-b352a1b807e6@gyani.pro> From: Gyan Doshi In-Reply-To: X-Rspamd-Queue-Id: 4TcTnq737bz9sTJ X-Content-Filtered-By: Mailman/MimeDel 2.1.29 Subject: Re: [FFmpeg-devel] FFmpeg TC input needed X-BeenThere: ffmpeg-devel@ffmpeg.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: FFmpeg development discussions and patches List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Reply-To: FFmpeg development discussions and patches Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset="us-ascii"; Format="flowed" Errors-To: ffmpeg-devel-bounces@ffmpeg.org Sender: "ffmpeg-devel" Archived-At: List-Archive: List-Post: On 2024-02-17 05:31 pm, Kieran Kunhya wrote: > On Sat, 17 Feb 2024, 11:46 Gyan Doshi, wrote: > >> Issue: >> >> Patch: avcodec/s302m: enable non-PCM decoding >> URL: >> >> https://patchwork.ffmpeg.org/project/ffmpeg/patch/20240127103854.9971-1-ffmpeg@gyani.pro/ >> >> The issue needing resolution is whether the patch should be added to the >> existing s302m decoder or should that decoder >> be removed and all old and new patched features inlined into the mpeg-ts >> demuxer. >> > Additional comments: > > Dolby E can exist in any PCM container (wav, MP4). S302M just happens to be > a tricky one. > > Whilst s302m multiple substreams I haven't seen, Dolby E streams internally > contain multiple programs, often 5.1 and a 2.0 downmix. That is downstream of the Dolby-E decoder and user will have to use a filter like channelsplit to bifurcate those channels irrespective of where the s302m code resides. > There is a 3x3 matrix of flavours between coded Dolby E and the carriage > PCM (16-bit, 20-bit, 24-bit). Have you seen a larger non-PCM word size inside a smaller AES3 word? Regards, Gyan _______________________________________________ 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".