220 26322 article Path: news.gmane.org!not-for-mail From: Robert Bielik Newsgroups: gmane.comp.lang.c++.isocpp.proposals Subject: Re: Any interest to adding audio support to the std library? Date: Mon, 13 Jun 2016 18:48:29 +0200 Lines: 191 Approved: news@gmane.org Message-ID: References: <5751B06A.4080501@mail1.stofanet.dk> <485D94E9-3386-4C2E-8C90-2AE821C3B7E6@gmail.com> <31D8D875-9842-4CC4-98C6-F75FD20155DE@gmail.com> <3560828.vAATzG8HgS@lastique-pc> <8AB38C1F-590D-4F81-9839-D7A4604E1831@gmail.com> Reply-To: std-proposals@isocpp.org NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: multipart/alternative; boundary=001a113ad4c277b76205352ba8a4 X-Trace: ger.gmane.org 1465836517 17548 80.91.229.3 (13 Jun 2016 16:48:37 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Mon, 13 Jun 2016 16:48:37 +0000 (UTC) To: std-proposals@isocpp.org Original-X-From: std-proposals+bncBDRJHJGV3EDBBXWH7O5AKGQE6JN5DDI@isocpp.org Mon Jun 13 18:48:33 2016 Return-path: Envelope-to: gclcip-std-proposals@m.gmane.org Original-Received: from mail-qt0-f199.google.com ([209.85.216.199]) by plane.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1bCV2O-0007dg-0E for gclcip-std-proposals@m.gmane.org; Mon, 13 Jun 2016 18:48:32 +0200 Original-Received: by mail-qt0-f199.google.com with SMTP id v18sf176784747qtv.0 for ; Mon, 13 Jun 2016 09:48:31 -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:date:message-id:subject:from: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=LBoHeK636FQMUcEpx+ZR4u88tWzGybFmZJKc81tysWU=; b=LkOx93diPRndM8I1t2KNzAvTOdiwHXQ49/ebtb1LoOK1uc/x/fns0vpO+AKxy7BZr7 XnZI9N62wrNWyG8MVVhI9lRIYSLrOaGU7btnyOKsluUaQ3D/mb21zUspdiZXjuzLLNMM fegWN66F1Gyq6Yxr8AmzjPWku/AhOGAtoVJ4lvj/GAJ4PZwqvzkURYlhB0Hb6XtXnVl7 oBYnPgPIXCqPzrgtYE+NL+vFvFfOVbkddqL4mS0QX+Po7TxvLqoNMrJlMYm1e/6SKjuA nnR/0Zy2DoOSMWw9OaQKODdYTT9Qg66b5rL/rOIg+qUevi9MDiKJOZKo3SLGif04Miqw zy6A== 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:date :message-id:subject:from: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=LBoHeK636FQMUcEpx+ZR4u88tWzGybFmZJKc81tysWU=; b=jXlmCGzhptc1YGc8DTpVXldOBUXSCV0Tqtw18aWbimDZlEezBWFrvzDCUFPB7TiGP+ n3/Esh6d83+0x60YFCOSCCvZ9GVLIe81WFTPiuMGJ4gWathxzN7ZWGoJQKbDg10ROL8S 7jvsFOhLMymph7Rsrg3uXdSXNEbQ/2kIh75eCVPL8omNaihRJLMnZbD3qSD1z69NNzZo 6jCpvzIEg+8kZKsERmLVqQfYAjj0HZfrtBKYT+cEb6g/68hLZ26sursc1ZFKlRc472/j lhacOW9XOCfnKlJzUU7RX8RYlIcjFmwbKZJb/lWH2r91mcsKx52yTD0lHEgfc9WOBA8V OxMA== X-Gm-Message-State: ALyK8tJ4dwdcWRi+CUcfxAzFvID/9Gg5b+iB0xmvXoYvP3wNg5y20Lusg+bShBuvDAf9og== X-Received: by 10.237.32.140 with SMTP id 12mr12557061qtb.6.1465836511241; Mon, 13 Jun 2016 09:48:31 -0700 (PDT) X-BeenThere: std-proposals@isocpp.org Original-Received: by 10.157.5.244 with SMTP id 107ls361745otd.44.gmail; Mon, 13 Jun 2016 09:48:30 -0700 (PDT) X-Received: by 10.202.206.7 with SMTP id e7mr6657773oig.161.1465836510126; Mon, 13 Jun 2016 09:48:30 -0700 (PDT) Original-Received: from mail-oi0-x22d.google.com (mail-oi0-x22d.google.com. [2607:f8b0:4003:c06::22d]) by mx.google.com with ESMTPS id l37si4803915otb.16.2016.06.13.09.48.30 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Mon, 13 Jun 2016 09:48:30 -0700 (PDT) Received-SPF: pass (google.com: domain of robert.bielik@gmail.com designates 2607:f8b0:4003:c06::22d as permitted sender) client-ip=2607:f8b0:4003:c06::22d; Original-Received: by mail-oi0-x22d.google.com with SMTP id p204so216500776oih.3 for ; Mon, 13 Jun 2016 09:48:30 -0700 (PDT) X-Received: by 10.202.87.209 with SMTP id l200mr3134144oib.172.1465836509835; Mon, 13 Jun 2016 09:48:29 -0700 (PDT) Original-Received: by 10.157.22.215 with HTTP; Mon, 13 Jun 2016 09:48:29 -0700 (PDT) Original-Received: by 10.157.22.215 with HTTP; Mon, 13 Jun 2016 09:48:29 -0700 (PDT) In-Reply-To: <8AB38C1F-590D-4F81-9839-D7A4604E1831@gmail.com> X-Original-Sender: robert.bielik@gmail.com X-Original-Authentication-Results: mx.google.com; dkim=pass header.i=@gmail.com; spf=pass (google.com: domain of robert.bielik@gmail.com designates 2607:f8b0:4003:c06::22d as permitted sender) smtp.mailfrom=robert.bielik@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:26322 Archived-At: --001a113ad4c277b76205352ba8a4 Content-Type: text/plain; charset=UTF-8 Since ultimately, the timing of audio frames could be used to synchronize audio from sources not sharing a clock, the resolution of the timestamp must be substantially larger than "number of samples ", I propose what was mentioned earlier, a steady clock with nanosecond resolution. /R Den 12 jun 2016 23:09 skrev : > 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 > > . > -- 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/CAEvHzA0emfwFJxzU%2BYyKog0H52MLnq6BnyuOzC27QVNUA_8Thw%40mail.gmail.com. --001a113ad4c277b76205352ba8a4 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

Since ultimately, the timing of audio frames could be used t= o synchronize audio from sources not sharing a clock, the resolution of the= timestamp must be substantially larger than "number of samples "= , I propose what was mentioned earlier, a steady clock with nanosecond reso= lution.

/R

Den 12 jun 2016 23:09 skrev <alexander.zywicki@gmail.com>:
In that case I would argue for the use of the "std::chrono::st= eady_clock" based on the fact that it is specified to be a monotonic c= lock.=C2=A0

Or a clock defined in a similar manor = that counts in samples.=C2=A0

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 <= ;andrey.sema= shev@gmail.com> wrote:

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

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

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

> time that the stream has been active and have mean= ingful measurements of

> time within the stream.

=C2=A0

There is no need to have the epoch bound to the beginni= ng 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.

=C2=A0

A fixed epoch becomes important when you try to synchro= nize multiple streams together. But even then it's not important what e= xactly is the epoch; what is important is that it has to be the same for al= l streams you are processing.

=C2=A0

--
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.
To unsubscribe from this group and all its topics, send an email to std-prop= osals+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.go= ogle.com/a/isocpp.org/d/msgid/std-proposals/3560828.vAATzG8HgS%40lastique-p= c.

--
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-proposals+unsubscribe@isocpp.org.
To post to this group, send email to std-proposals@isocpp.org.
To view this discussion on the web visit h= ttps://groups.google.com/a/isocpp.org/d/msgid/std-proposals/8AB38C1F-590D-4= F81-9839-D7A4604E1831%40gmail.com.

--
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 h= ttps://groups.google.com/a/isocpp.org/d/msgid/std-proposals/CAEvHzA0emfwFJx= zU%2BYyKog0H52MLnq6BnyuOzC27QVNUA_8Thw%40mail.gmail.com.
--001a113ad4c277b76205352ba8a4-- .