220 26303 <8AB38C1F-590D-4F81-9839-D7A4604E1831@gmail.com> article Path: news.gmane.org!not-for-mail From: alexander.zywicki@gmail.com Newsgroups: gmane.comp.lang.c++.isocpp.proposals Subject: Re: Any interest to adding audio support to the std library? Date: Sun, 12 Jun 2016 17:09:39 -0400 Lines: 125 Approved: news@gmane.org Message-ID: <8AB38C1F-590D-4F81-9839-D7A4604E1831@gmail.com> References: <5751B06A.4080501@mail1.stofanet.dk> <485D94E9-3386-4C2E-8C90-2AE821C3B7E6@gmail.com> <31D8D875-9842-4CC4-98C6-F75FD20155DE@gmail.com> <3560828.vAATzG8HgS@lastique-pc> Reply-To: std-proposals@isocpp.org NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 (1.0) Content-Type: multipart/alternative; boundary=Apple-Mail-66A41169-1247-4481-A37C-8CC22BA8D3F4 Content-Transfer-Encoding: 7bit X-Trace: ger.gmane.org 1465765798 26420 80.91.229.3 (12 Jun 2016 21:09:58 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Sun, 12 Jun 2016 21:09:58 +0000 (UTC) To: std-proposals@isocpp.org Original-X-From: std-proposals+bncBCS7TY6DTQOBBF47665AKGQEWB6A46Q@isocpp.org Sun Jun 12 23:09:46 2016 Return-path: Envelope-to: gclcip-std-proposals@m.gmane.org Original-Received: from mail-it0-f72.google.com ([209.85.214.72]) by plane.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1bCCdd-0003Ol-8O for gclcip-std-proposals@m.gmane.org; Sun, 12 Jun 2016 23:09:45 +0200 Original-Received: by mail-it0-f72.google.com with SMTP id b126sf75614217ite.3 for ; Sun, 12 Jun 2016 14:09:44 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=isocpp-org.20150623.gappssmtp.com; s=20150623; h=mime-version:subject:from:in-reply-to:date :content-transfer-encoding:message-id:references: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=ljkXXbzxt5ZWVW3yZKwBqC8bBtPkj01yCT86ge32N30=; b=LXrD2K7HwRcl/eEgSctcSdL/mYZvj/9THmpFPETJj8YGcwam0aEsqvBdqYYCNbXgjT dPmg1a2sqGDk/Z5s2h/hZfULo7GK8dX6lCX6pYnHHImpZkhfW4Y0mkyIupx6DgyeZGns pzSkPS0iCvspyt1OyTrUD/OyA7pjkv6Re/m/E4QK3qAijUTiLBQniQ+K85QzMlWu63j7 5LwsXnjI1Sw3bn3c+PfeyZSHgwxMCjlds+HHhSd1hutNBFdQbhTUY825CsuQ2dmKIR1K T0LxV6IRwX3pcz8qHbNWsQomk9gO0AFgtocXI/In9RS3zfiPgUHwKqZmg3WxoeSONshK ChgQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:subject:from:in-reply-to:date :content-transfer-encoding:message-id:references: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=ljkXXbzxt5ZWVW3yZKwBqC8bBtPkj01yCT86ge32N30=; b=YKfflnaZadC0AywcyTrDzu491fejuoG7pcGlhvsPF10g+n6DHWu7QOWcIJ0iGEermt Ugjd3+qTsuqHMXDOGwGTxvDXrHwKuHDgqvmIh/5TxCEV+rAITMBspIZ2l6bCj+oYxZOS rSN8pJsQ93MV56mMo+/rEeyKYnNZ0PtruSW8Rv/tJCdTnI+BVPRnlse/T7Tdtplb8Ub3 VPbVDVPKdKNyiIIX0XnX2CAd8dbZ5mL/kpsQqL1oglVrAS/4PO3Q8Ay9gNfzkms8Wa+i UvyfPbW07r3J5Z3FibqrPi8HkL9JdRPF1HwamepLhpDapGGavvvM98CwRK13knukHQme sBN X-Gm-Message-State: ALyK8tJLifE32XETTxe1xbfoNfH6ugeTSaHHsPc46b+wuwAO5sZjHzzOrLln+0hMiV/glQ== X-Received: by 10.107.19.91 with SMTP id b88mr10205476ioj.32.1465765784136; Sun, 12 Jun 2016 14:09:44 -0700 (PDT) X-BeenThere: std-proposals@isocpp.org Original-Received: by 10.107.148.19 with SMTP id w19ls1532313iod.2.gmail; Sun, 12 Jun 2016 14:09:43 -0700 (PDT) X-Received: by 10.107.188.71 with SMTP id m68mr19138058iof.1.1465765783202; Sun, 12 Jun 2016 14:09:43 -0700 (PDT) Original-Received: from mail-io0-x236.google.com (mail-io0-x236.google.com. [2607:f8b0:4001:c06::236]) by mx.google.com with ESMTPS id j92si15376006ioo.156.2016.06.12.14.09.43 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Sun, 12 Jun 2016 14:09:43 -0700 (PDT) Received-SPF: pass (google.com: domain of alexander.zywicki@gmail.com designates 2607:f8b0:4001:c06::236 as permitted sender) client-ip=2607:f8b0:4001:c06::236; Original-Received: by mail-io0-x236.google.com with SMTP id d2so18353003iof.0 for ; Sun, 12 Jun 2016 14:09:43 -0700 (PDT) X-Received: by 10.107.139.200 with SMTP id n191mr20011546iod.159.1465765783005; Sun, 12 Jun 2016 14:09:43 -0700 (PDT) Original-Received: from [10.61.169.86] (mobile-107-92-123-222.mycingular.net. [107.92.123.222]) by smtp.gmail.com with ESMTPSA id c89sm10756895iod.1.2016.06.12.14.09.40 (version=TLSv1/SSLv3 cipher=OTHER); Sun, 12 Jun 2016 14:09:41 -0700 (PDT) X-Mailer: iPhone Mail (13F69) In-Reply-To: <3560828.vAATzG8HgS@lastique-pc> X-Original-Sender: alexander.zywicki@gmail.com X-Original-Authentication-Results: mx.google.com; dkim=pass header.i=@gmail.com; spf=pass (google.com: domain of alexander.zywicki@gmail.com designates 2607:f8b0:4001:c06::236 as permitted sender) smtp.mailfrom=alexander.zywicki@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:26303 Archived-At: --Apple-Mail-66A41169-1247-4481-A37C-8CC22BA8D3F4 Content-Type: text/plain; charset=UTF-8 In that case I would argue for the use of the "std::chrono::steady_clock" based on the fact that it is specified to be a monotonic clock. Or a clock defined in a similar manor that counts in samples. I also would imagine that our clock would need to have "is_steady" always be true? > On Jun 11, 2016, at 4:09 AM, Andrey Semashev wrote: > > On Saturday, 11 June 2016 11:03:41 MSK alexander.zywicki@gmail.com wrote: > > Or at least store a time point each time the stream is started using a clock > > with a well defined epoch, so that we might be able to find the length of > > time that the stream has been active and have meaningful measurements of > > time within the stream. > > There is no need to have the epoch bound to the beginning of the stream to calculate its duration. Or any particular epoch at all. All you need is the timestamp of its first and last frames. > > A fixed epoch becomes important when you try to synchronize multiple streams together. But even then it's not important what exactly is the epoch; what is important is that it has to be the same for all streams you are processing. > > -- > You received this message because you are subscribed to a topic in the Google Groups "ISO C++ Standard - Future Proposals" group. > To unsubscribe from this topic, visit https://groups.google.com/a/isocpp.org/d/topic/std-proposals/Hkdh02Ejx6s/unsubscribe. > To unsubscribe from this group and all its topics, 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/3560828.vAATzG8HgS%40lastique-pc. -- 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/8AB38C1F-590D-4F81-9839-D7A4604E1831%40gmail.com. --Apple-Mail-66A41169-1247-4481-A37C-8CC22BA8D3F4 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
In that case I would ar= gue for the use of the "std::chrono::steady_clock" based on the fact that i= t is specified to be a monotonic clock. 

Or a= clock defined in a similar manor that counts in samples. 
<= br>
I also would imagine that our clock would need to have "is_st= eady" always be true?


On Jun 11, 2016, at 4:09= AM, Andrey Semashev <andre= y.semashev@gmail.com> wrote:

=

On Saturday= , 11 June 2016 11:03:41 MSK = alexander.zywicki@gmail.com wrote:

> Or at = least store a time point each time the stream is started using a clock

> with a= well defined epoch, so that we might be able to find the length of

> time t= hat the stream has been active and have meaningful measurements of

> time w= ithin the stream.

&nb= sp;

There is no= need to have the epoch bound to the beginning of the stream to calculate i= ts duration. Or any particular epoch at all. All you need is the timestamp = of its first and last frames.

&nb= sp;

A fixed epo= ch becomes important when you try to synchronize multiple streams together.= But even then it's not important what exactly is the epoch; what is import= ant is that it has to be the same for all streams you are processing.

&nb= sp;

--
You received this message because you are subscribed to a topic in the Goog= le Groups "ISO C++ Standard - Future Proposals" group.
To unsubscribe from this topic, visit https://groups.= google.com/a/isocpp.org/d/topic/std-proposals/Hkdh02Ejx6s/unsubscribe.<= br> To unsubscribe from this group and all its topics, 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/3560828.vAATzG8HgS%40lastique-pc.

--
You received this message because you are subscribed to the Google Groups &= quot;ISO C++ Standard - Future Proposals" group.
To unsubscribe from this group and stop receiving emails from it, send an e= mail to std-proposa= ls+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.c= om/a/isocpp.org/d/msgid/std-proposals/8AB38C1F-590D-4F81-9839-D7A4604E1831%= 40gmail.com.
--Apple-Mail-66A41169-1247-4481-A37C-8CC22BA8D3F4-- .