From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <ffmpeg-devel-bounces@ffmpeg.org>
Received: from ffbox0-bg.mplayerhq.hu (ffbox0-bg.ffmpeg.org [79.124.17.100])
	by master.gitmailbox.com (Postfix) with ESMTP id 0CAAF4969A
	for <ffmpegdev@gitmailbox.com>; Sat, 17 Feb 2024 13:42:21 +0000 (UTC)
Received: from [127.0.1.1] (localhost [127.0.0.1])
	by ffbox0-bg.mplayerhq.hu (Postfix) with ESMTP id 104A968D292;
	Sat, 17 Feb 2024 15:42:19 +0200 (EET)
Received: from haasn.dev (haasn.dev [78.46.187.166])
 by ffbox0-bg.mplayerhq.hu (Postfix) with ESMTP id 1EB4668D1DB
 for <ffmpeg-devel@ffmpeg.org>; Sat, 17 Feb 2024 15:42:12 +0200 (EET)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=haasn.xyz; s=mail;
 t=1708177331; bh=sfuMxkWWNLwPEoZDN0cZRNw7yURxLJkO8iieC5qZBgk=;
 h=Date:From:To:Subject:In-Reply-To:References:From;
 b=vG4nxrNSvziqSYJe6tdijr9x8KxDWPCxFkn1RUzR9Rm4oyKLL6uPPoUVr8uL+beN+
 W4J+vDcWNcwVG0Dwrf5F3VjTGerW4wWGxSBxD0VzuLwhEoxJFI74xzkt6BTzC57bJl
 A25NG88jCsV0cDxJ5NiDfnKP9xycWEeuZtbxmbUs=
Received: from haasn.dev (unknown [10.30.0.2])
 by haasn.dev (Postfix) with ESMTP id 76EF340247
 for <ffmpeg-devel@ffmpeg.org>; Sat, 17 Feb 2024 14:42:11 +0100 (CET)
Date: Sat, 17 Feb 2024 14:42:11 +0100
Message-ID: <20240217144211.GC32178@haasn.xyz>
From: Niklas Haas <ffmpeg@haasn.xyz>
To: ffmpeg-devel@ffmpeg.org
In-Reply-To: <153dfd89-aedd-4704-aef4-15cca7cc541d@gyani.pro>
References: <9be400cf-949f-4eb1-93a1-b352a1b807e6@gyani.pro>
 <CAK+ULv6_5ARo_ZCo_vGWEXVqE9RgsCfEKFOBcvJA5EyAPkU0tA@mail.gmail.com>
 <153dfd89-aedd-4704-aef4-15cca7cc541d@gyani.pro>
MIME-Version: 1.0
Content-Disposition: inline
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 <ffmpeg-devel.ffmpeg.org>
List-Unsubscribe: <https://ffmpeg.org/mailman/options/ffmpeg-devel>,
 <mailto:ffmpeg-devel-request@ffmpeg.org?subject=unsubscribe>
List-Archive: <https://ffmpeg.org/pipermail/ffmpeg-devel>
List-Post: <mailto:ffmpeg-devel@ffmpeg.org>
List-Help: <mailto:ffmpeg-devel-request@ffmpeg.org?subject=help>
List-Subscribe: <https://ffmpeg.org/mailman/listinfo/ffmpeg-devel>,
 <mailto:ffmpeg-devel-request@ffmpeg.org?subject=subscribe>
Reply-To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Errors-To: ffmpeg-devel-bounces@ffmpeg.org
Sender: "ffmpeg-devel" <ffmpeg-devel-bounces@ffmpeg.org>
Archived-At: <https://master.gitmailbox.com/ffmpegdev/20240217144211.GC32178@haasn.xyz/>
List-Archive: <https://master.gitmailbox.com/ffmpegdev/>
List-Post: <mailto:ffmpegdev@gitmailbox.com>

On Sat, 17 Feb 2024 18:45:57 +0530 Gyan Doshi <ffmpeg@gyani.pro> wrote:
> > 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.

Is there metadata in Dolby E that tells you which channels belong
together (and what attributes they might have)? Is it always 5.1+2.0, or
could you have e.g. four different 2.0 programs encoded into a single
S302M/AES3 stream?
_______________________________________________
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".