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 5CB2548407 for ; Tue, 2 Jan 2024 22:09:18 +0000 (UTC) Received: from [127.0.1.1] (localhost [127.0.0.1]) by ffbox0-bg.mplayerhq.hu (Postfix) with ESMTP id BE3FE68CA1F; Wed, 3 Jan 2024 00:09:15 +0200 (EET) Received: from mail-pj1-f46.google.com (mail-pj1-f46.google.com [209.85.216.46]) by ffbox0-bg.mplayerhq.hu (Postfix) with ESMTPS id C549C68BDB0 for ; Wed, 3 Jan 2024 00:09:08 +0200 (EET) Received: by mail-pj1-f46.google.com with SMTP id 98e67ed59e1d1-28c0536806fso7208403a91.0 for ; Tue, 02 Jan 2024 14:09:08 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ob-encoder-com.20230601.gappssmtp.com; s=20230601; t=1704233346; x=1704838146; darn=ffmpeg.org; h=to:subject:message-id:date:from:in-reply-to:references:mime-version :from:to:cc:subject:date:message-id:reply-to; bh=2Y9Ra37NT5eoCiK5lI7c1Wr+ZE4ojMshN8mkjlmj7/4=; b=cFyi1Dwmryh9tiPeplEOjAlpIn8UAhaowWkFrSEzEai2uAKmei/mDEsLSeQThUxdBh zTBwg0VDS+6elxXRdb2Iz+lTi7qr1zSLML1rSIgWuWI7nGPSptq/C0rVfqtXmZhyGmP3 VaxdOPq50cqs+d7rj4CBtETvGC9IWB/M6PhKYHc0BORTnO/LU0CNo/CqP323Mp2aukxY tc0ZviV5L21VFfr4FPsj9oA9yD4/dj2xLOOW0OeEo9iKVvspxTsBqloqqZM7TskUUzQu lWFG+qv3LNctu9Q7LaUyYr0xtapdNm7SuNhteF8uV2EXMcY9MECYDHcxrlO+kdGDdvSM RkUA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1704233346; x=1704838146; h=to:subject:message-id:date:from:in-reply-to:references:mime-version :x-gm-message-state:from:to:cc:subject:date:message-id:reply-to; bh=2Y9Ra37NT5eoCiK5lI7c1Wr+ZE4ojMshN8mkjlmj7/4=; b=vhasS47AkMP3eajt4/MRXBtjMAQGJ18KmwOw5wc62aS3weVCbsVcNyOMlmL8LlqjLz Z465kzzF3oYZFyYaO71EelSfYwrW+iwqJXuYjEDK3akKJhQrZfGsTM1zNULNFCQe0hSD xMQv/5tOMlvIKQxUrg9pXS1UOIbEzkgKA3e+RWPf13+JANk+v2/WtHIqXgBkLxCvxZVB uzH0EemP98dIlcSvIAlsRauLmcfJzjFpoTs4Sy2Zb+NAlj6AG0F5pt8FmrAjMPW02VrA n8ymXaoKafX56grSfoLK4cWzpikncxEvbmupbWceNOBZsKum8BipkyAwyxB2xRa21TaX PElw== X-Gm-Message-State: AOJu0YwGmsyP2cNvlvZfMJNavbi/ycuo+wU6RLCQ4ZwsHlau3xewUZJr 67jByKlAgApFPOllezS0sWMHSDm/JJU3b2CzlNiFhdNvEwSvGI0R5C/KRm8xoBA= X-Google-Smtp-Source: AGHT+IFvvM33bHxcWuPAeTdP4FtXekjYFECUlUH5Sk7ziJ8zfVtB0xE+C1jU8liZpGz9ZIp86qHNxomGfzsW9duePF8= X-Received: by 2002:a17:90a:c295:b0:28b:e7c4:46d with SMTP id f21-20020a17090ac29500b0028be7c4046dmr9931808pjt.15.1704233345863; Tue, 02 Jan 2024 14:09:05 -0800 (PST) MIME-Version: 1.0 References: <20231218145859.1162669-1-petr.matousek@comprimato.com> In-Reply-To: From: Kieran Kunhya Date: Tue, 2 Jan 2024 22:08:54 +0000 Message-ID: To: FFmpeg development discussions and patches , Petr Matousek X-Content-Filtered-By: Mailman/MimeDel 2.1.29 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 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: > > My point is that we might opt-out the verbose dump if we have a clear > criterion for opting-in/out. For example -show_data is off by default, > and we could mark special side-data fields with some flags to opt them > out by default. Again, for unregistered SEI you don't have a choice. Some encoders put tons of private data in there. Some of the stuff is human readable, some of it isn't. > > Again, this is something that should either be parsed by FFmpeg or done > via > > the API. > > I still don't understand. The CLI exposes what the API does, so if the > API can't do it, the CLI cannot do either. The OP wants to test an implementation they have and they should do it using the API, not using ffprobe to test their third party implementation of something. "Parsed by FFmpeg" sounds like you are proposing to extend the FFmpeg > API to parse some more information (about the SEI subtype?) and make > it available through some more specific SEI side data? > As the OP says, this SEI data is from "MISB ST 0604" which is something that could be implemented in FFmpeg and parsed properly like all the other side data instead of just writing random binary data to the terminal. I don't understand why any of this is hard to comprehend. Kieran _______________________________________________ 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".