220 26151 article Path: news.gmane.org!not-for-mail From: Andrey Semashev Newsgroups: gmane.comp.lang.c++.isocpp.proposals Subject: Re: Any interest to adding audio support to the std library? Date: Sat, 4 Jun 2016 01:54:55 +0300 Lines: 46 Approved: news@gmane.org Message-ID: References: <5751B06A.4080501@mail1.stofanet.dk> <4539123.eWIb3U4yhc@lastique-pc> <2028636.MhYnudsMAW@tjmaciei-mobl1> Reply-To: std-proposals@isocpp.org NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 X-Trace: ger.gmane.org 1464994501 7276 80.91.229.3 (3 Jun 2016 22:55:01 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Fri, 3 Jun 2016 22:55:01 +0000 (UTC) To: "ISO C++ Standard - Future Proposals" Original-X-From: std-proposals+bncBCXY5TXHWYJRBQEVZC5AKGQELJ2PGZY@isocpp.org Sat Jun 04 00:55:00 2016 Return-path: Envelope-to: gclcip-std-proposals@m.gmane.org Original-Received: from mail-io0-f200.google.com ([209.85.223.200]) by plane.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1b8xzW-0000Ln-8E for gclcip-std-proposals@m.gmane.org; Sat, 04 Jun 2016 00:54:58 +0200 Original-Received: by mail-io0-f200.google.com with SMTP id p194sf136823539iod.2 for ; Fri, 03 Jun 2016 15:54:57 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=isocpp-org.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :x-original-sender:x-original-authentication-results:reply-to :precedence:mailing-list:list-id:x-spam-checked-in-group:list-post :list-help:list-archive:list-subscribe:list-unsubscribe; bh=lEI5/g7vBDgPt8JiiLPqNHD4Y+NASNdkwGRS14N/hps=; b=lbp7sHgiRITNjrKRFzp9V/dv8ItObn77F7rXgxK5qN01FiJFUGOIPQzjdJrQDzxXxF UtaForccKbHQbBRqN371D0MaRzTI8lifJDAn6Hg3fQSEajb/k37YciqBv4/2KFLXSI9X DlXvzbxosrB8COkAm0TGRlhhsrjFBgJOYhawOpppu9RHV/IxLyJGnutkJDOyAwN3Dw5z Zzt1mGyBoEpTB23AbV/AYahSW6O8xwSQhFzxPyMq60U0BM6dxJwkQKYqQ4Tw8t2WNlXW RzAlqpobA5/VC3eGGF2uuodKFg91UV5QaD5bhEEAsJD5WPLA0y09RdTsx8WZyW5mSA2L uHtw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:x-original-sender :x-original-authentication-results:reply-to:precedence:mailing-list :list-id:x-spam-checked-in-group:list-post:list-help:list-archive :list-subscribe:list-unsubscribe; bh=lEI5/g7vBDgPt8JiiLPqNHD4Y+NASNdkwGRS14N/hps=; b=ECoU3v7EHnnd3gRR3crA+MoOGJRFxy+cApO5Jt5FY0ShnWeMv6LoPshLCjgIqs/ZeT uHwwOgKnWcWZHSzpElScK+jhOGgfmF/+chjHvSn11CqD1ULWw8FaanKMiS0JECdugbF2 3wfKqfZmxZzCtcecoFBawDiTjVJaPnNZYcBnmdYhbTwe2p+8/dEJ3EU1bkB40PEg9vzs KhgQGKNIOPeeahwaRoY1kKyJuulqW/H199aCHIKbOdTgVZz1ognwhzg75OhAC2ocx8mY igmFWX3D7eogUNBFo475XYnKVwMCM+Or3hFyFzBGGRR3biadHrVNcAR8+vMfHmnizFKg JOSA== X-Gm-Message-State: ALyK8tJau1NFG/ipvvpizUl4cbQKwlMkOVtGbwfCqHb8WAWGA8BQv7+jwSvWXdI9XrlNpw== X-Received: by 10.157.35.77 with SMTP id k13mr1140360otd.17.1464994497269; Fri, 03 Jun 2016 15:54:57 -0700 (PDT) X-BeenThere: std-proposals@isocpp.org Original-Received: by 10.36.131.5 with SMTP id d5ls110005ite.13.canary; Fri, 03 Jun 2016 15:54:56 -0700 (PDT) X-Received: by 10.36.1.198 with SMTP id 189mr2986167itk.40.1464994496558; Fri, 03 Jun 2016 15:54:56 -0700 (PDT) Original-Received: from mail-io0-x229.google.com (mail-io0-x229.google.com. [2607:f8b0:4001:c06::229]) by mx.google.com with ESMTPS id u123si1608746itb.41.2016.06.03.15.54.56 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Fri, 03 Jun 2016 15:54:56 -0700 (PDT) Received-SPF: pass (google.com: domain of andrey.semashev@gmail.com designates 2607:f8b0:4001:c06::229 as permitted sender) client-ip=2607:f8b0:4001:c06::229; Original-Received: by mail-io0-x229.google.com with SMTP id t40so93534550ioi.0 for ; Fri, 03 Jun 2016 15:54:56 -0700 (PDT) X-Received: by 10.36.130.130 with SMTP id t124mr2940274itd.42.1464994496374; Fri, 03 Jun 2016 15:54:56 -0700 (PDT) Original-Received: by 10.79.12.23 with HTTP; Fri, 3 Jun 2016 15:54:55 -0700 (PDT) In-Reply-To: <2028636.MhYnudsMAW@tjmaciei-mobl1> X-Original-Sender: andrey.semashev@gmail.com X-Original-Authentication-Results: mx.google.com; dkim=pass header.i=@gmail.com; spf=pass (google.com: domain of andrey.semashev@gmail.com designates 2607:f8b0:4001:c06::229 as permitted sender) smtp.mailfrom=andrey.semashev@gmail.com; dmarc=pass (p=NONE dis=NONE) header.from=gmail.com Precedence: list Mailing-list: list std-proposals@isocpp.org; contact std-proposals+owners@isocpp.org List-ID: X-Spam-Checked-In-Group: std-proposals@isocpp.org X-Google-Group-Id: 399137483710 List-Post: , List-Help: , List-Archive: List-Subscribe: , List-Unsubscribe: , Xref: news.gmane.org gmane.comp.lang.c++.isocpp.proposals:26151 Archived-At: On Sat, Jun 4, 2016 at 12:58 AM, Thiago Macieira wrote: > On sexta-feira, 3 de junho de 2016 20:10:05 BRT Andrey Semashev wrote: >> On Friday, 3 June 2016 20:04:59 MSK Bjorn Reese wrote: >> > I would approach an audio API differently. >> > >> > The basic audio primitives are playing and recording. >> >> I disagree. I would say the basic primitives are a sample and a >> frame. Samples can be obtained and processed in different ways, >> including recording, reading from file or generating algorithmically. >> >> The processing is often represented as a pipeline or graph with >> producer, filter and consumer nodes. This is a higher level >> framework that builds upon the basic blocks of frames and digital >> signal processing algorithms. > > Considering the domain of media codecs is a patent minefield, the API should be > designed around never having access to the actual contents of the frames, only > that they exist. Well, regarding codecs, there are different ones, including the unencumbered ones. But the point of the proposal is not so much aimed at codecs but rather at raw media processing. > More than likely, just "here's a file or URL, go play it", plus some time-sync > API and some hints on what type of audio it is, so system can route it to the > correct speaker (headphones? bluetooth? loudspeaker?). Plus the converse > recording. > > IMHO, just like the 2D graphics proposal, I think this is ill-advised as > content for the C++ Standard Library. The way you described it - it would be a proposal of a fairly limited use. And if that was the case I would agree it's not suitable for the standard library. However, what the OP described is different and something like what I implemented to a certain degree in a closed project. I would really have liked if something like that was in the standard library. -- You received this message because you are subscribed to the Google Groups "ISO C++ Standard - Future Proposals" group. To unsubscribe from this group and stop receiving emails from it, send an email to std-proposals+unsubscribe@isocpp.org. To post to this group, send email to std-proposals@isocpp.org. To view this discussion on the web visit https://groups.google.com/a/isocpp.org/d/msgid/std-proposals/CAEhD%2B6DbXNRm030MSycRhAxUk2Ji2saDJBv-np32TbseZNDnVw%40mail.gmail.com. .