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 37FE048B16 for ; Tue, 2 Jan 2024 20:01:16 +0000 (UTC) Received: from [127.0.1.1] (localhost [127.0.0.1]) by ffbox0-bg.mplayerhq.hu (Postfix) with ESMTP id 202C568CA03; Tue, 2 Jan 2024 22:01:14 +0200 (EET) Received: from mail-lf1-f47.google.com (mail-lf1-f47.google.com [209.85.167.47]) by ffbox0-bg.mplayerhq.hu (Postfix) with ESMTPS id 9822F68B1FF for ; Tue, 2 Jan 2024 22:01:06 +0200 (EET) Received: by mail-lf1-f47.google.com with SMTP id 2adb3069b0e04-50e9e5c97e1so1309787e87.0 for ; Tue, 02 Jan 2024 12:01:06 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1704225666; x=1704830466; darn=ffmpeg.org; h=user-agent:in-reply-to:content-disposition:mime-version:references :mail-followup-to:message-id:subject:cc:to:from:date:from:to:cc :subject:date:message-id:reply-to; bh=yaXI+7Z7gaa1dnGaY9IMqWL9T5WJrn7vFgRZerTjyZg=; b=atKMvHOsjgyi7LyRBaPeWsYmiu2T6GRMgqyNYaKU/8vp72LCUv/Lx5tzYfe2jaoKZG /sJG/+NB2h2wgAubNI56aOvfhazGZdEyqGDjyYgCjsNUur4SE+3DlstNcIbMqoMWVXUr l7ZFfvdlBnvDO1hy/R+LP76F2sMmVahZrAi2nhOnxnm3kof4EjTslOAc0NKTIpUkXCS+ SuIAGNXdfizae/oTLN+/CBD9E0T2wj0AzLd2V4skA997lcS/Ug807HSeAnPPaBKi06yK Pzdn+uiRprL0g4Kirkb5nttLd4eEUHMmIlimjleWRl2YR7BGq0G+SzTzGnOIC8o2eZJZ R5Qw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1704225666; x=1704830466; h=user-agent:in-reply-to:content-disposition:mime-version:references :mail-followup-to:message-id:subject:cc:to:from:date :x-gm-message-state:from:to:cc:subject:date:message-id:reply-to; bh=yaXI+7Z7gaa1dnGaY9IMqWL9T5WJrn7vFgRZerTjyZg=; b=KbvvraMRoxX5L2y2mK5QD3ZVZBNelv7MI/uctoMOMVxlem8Hi6pa8xebf6ddv74Iy0 sHj4i1A5XpdfpJvZ5/gLqknWFsl3hp8fw1rMf32w/3fHEnI/6oRwZFXZ4Mkg+Ns+l5/P 85k+dH2ArVFzOABhXDPM36IuMXWrTu85BVUmEKcCCChSW2CFlL58bGL4wyyFtTIHwnbp vftkcD0zT9EexBXiVkjsnzg+v+OsQA32QpkHC9NYP1nXMWJd+2prj3Q69/usyxMdM2x2 v+oOFm8tXu9jbNh7uuLfrwA/aHmNt8Zuo3586B6LpG8aLWKGPRIGFXa5vI2Z3NR9DusT puPA== X-Gm-Message-State: AOJu0YxEWTWhftvdyE+9xuSNlU1u2mFk3zUQE8U5Pwx+3i0N1J0Hbr3o gtUg6zYv1lgzouc4o8qYKjA= X-Google-Smtp-Source: AGHT+IECptGBnrc8BlMVEmmjoAu3VgU+Y49kCjAb3js5UKZOgLPuJ41oZYJ4VsvWUo8Um6+wy/DwFw== X-Received: by 2002:a05:6512:144:b0:50e:3e3d:217c with SMTP id m4-20020a056512014400b0050e3e3d217cmr6603381lfo.84.1704225665347; Tue, 02 Jan 2024 12:01:05 -0800 (PST) Received: from mariano (dynamic-adsl-84-220-189-10.clienti.tiscali.it. [84.220.189.10]) by smtp.gmail.com with ESMTPSA id x17-20020a170906659100b00a282c5a3143sm1289964ejn.88.2024.01.02.12.01.04 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Tue, 02 Jan 2024 12:01:05 -0800 (PST) Received: by mariano (Postfix, from userid 1000) id 0CE5BBFCDC; Tue, 2 Jan 2024 21:01:04 +0100 (CET) Date: Tue, 2 Jan 2024 21:01:03 +0100 From: Stefano Sabatini To: FFmpeg development discussions and patches Message-ID: Mail-Followup-To: FFmpeg development discussions and patches , Petr Matousek References: <20231218145859.1162669-1-petr.matousek@comprimato.com> MIME-Version: 1.0 Content-Disposition: inline In-Reply-To: User-Agent: Mutt/2.1.4 (2021-12-11) Subject: Re: [FFmpeg-devel] [PATCH 0/1] fftools/ffprobe: dump contents of the AV_FRAME_DATA_SEI_UNREGISTERED 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 Cc: Petr Matousek Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Errors-To: ffmpeg-devel-bounces@ffmpeg.org Sender: "ffmpeg-devel" Archived-At: List-Archive: List-Post: On date Tuesday 2024-01-02 11:34:40 +0000, Kieran Kunhya wrote: > On Tue, 2 Jan 2024 at 11:27, Stefano Sabatini wrote: > > > On date Monday 2023-12-18 19:06:10 +0000, Kieran Kunhya wrote: > > > On Mon, 18 Dec 2023 at 14:59, Petr Matousek < > > petr.matousek@comprimato.com> > > > wrote: > > > > > > > Before this patch being applied the ffprobe just tells the user whether > > > > the H.26[45] User Data Unregistered SEI message is present in the frame > > > > side data > > > > or not. After the patch being appliend it also dumps the contents of > > the > > > > data > > > > similar way as for the other already supported frame side data types. > > > > > > > > Petr Matousek (1): > > > > fftools/ffprobe: dump contents of the AV_FRAME_DATA_SEI_UNREGISTERED > > > > > > > > > > > > I don't think ffprobe should be dumping potentially large amounts of > > random > > > SEI data to the terminal. Some encoders use this space for their own data > > > and it's annoying to see it spam the terminal. > > > > I'm not super concerned by this, since you can filter out the required > > information. Also I don't see other viable alternatives to show this > > information (moving this to metadata would require decoding). > > > > How are you able to filter between different types of unregistered SEI? At the moment you can opt-in what must be shown (opt-out is not an option). But from the point of view of the side data, probably there is no way to filter that out depending on the type. But this can be done later by processing the data (which is mostly the point of the output generated by ffprobe). This is the OP use case after all: |We needed to verify that our implementation of the MISB ST 0604 produces |correct contents of the SEI data. Using ffprobe for that was very useful as we |were able to pair the SEI data with other frame data like the PTS etc. > This is yet another thing that needs to be done with the API I don't understand what you mean by "the API". Provided that the API exposes the information about the side data type, but not much else at this level, you still would probably need to postprocess the data. > and not the CLI (something this project is unable to understand). What is exposed by the API is exercised by the CLI (which is a good thing for scripting and for testing). _______________________________________________ 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".