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 E0E7544DD0 for ; Tue, 23 Jan 2024 11:18:21 +0000 (UTC) Received: from [127.0.1.1] (localhost [127.0.0.1]) by ffbox0-bg.mplayerhq.hu (Postfix) with ESMTP id 60F6A68CEE7; Tue, 23 Jan 2024 13:18:18 +0200 (EET) Received: from mout-p-201.mailbox.org (mout-p-201.mailbox.org [80.241.56.171]) by ffbox0-bg.mplayerhq.hu (Postfix) with ESMTPS id A033768CA86 for ; Tue, 23 Jan 2024 13:18:11 +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-201.mailbox.org (Postfix) with ESMTPS id 4TK4MP2YzYz9t33 for ; Tue, 23 Jan 2024 12:18:09 +0100 (CET) Message-ID: <0009fb2e-6544-4db4-a787-38367919e632@gyani.pro> Date: Tue, 23 Jan 2024 16:48:06 +0530 MIME-Version: 1.0 Content-Language: en-US To: ffmpeg-devel@ffmpeg.org References: <20240123064948.455-1-ffmpeg@gyani.pro> From: Gyan Doshi In-Reply-To: X-Rspamd-Queue-Id: 4TK4MP2YzYz9t33 Subject: Re: [FFmpeg-devel] [PATCH 1/2] avcodec/s302m: enable non-PCM decoding 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-01-23 03:58 pm, Nicolas Gaullier wrote: >> +#define IS_NONPCMSYNC_16(state) ((state & 0xFFFF0FFFF0) == NONPCMSYNC_16MARKER) > Is this single 32 bits marker enough to avoid a fake detection ? It will have to do. The modal number of payload packets expected in a single s302m packet is one, so there's no redundancy. And since the AES3 sync (time slots 0-3) is stripped off (in all samples I have), we can't identify byte 0 of the channel status word for a double-check. However, unlike s337m probe, which is dealing with data of unknown provenance, the context here is a PES packet emitted of a stream identified as s302m by the demuxer so the odds are low of a false positive. 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".