220 26309 <2943c5c2-2c46-4447-b8f6-7647fc34d52c@isocpp.org> 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 20:40:46 -0700 (PDT) Lines: 249 Approved: news@gmane.org Message-ID: <2943c5c2-2c46-4447-b8f6-7647fc34d52c@isocpp.org> 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/mixed; boundary="----=_Part_743_64243900.1465789247040" X-Trace: ger.gmane.org 1465789255 24815 80.91.229.3 (13 Jun 2016 03:40:55 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Mon, 13 Jun 2016 03:40:55 +0000 (UTC) Cc: alexander.zywicki@gmail.com To: ISO C++ Standard - Future Proposals Original-X-From: std-proposals+bncBCS7TY6DTQOBBQGW7C5AKGQEZHPLSNQ@isocpp.org Mon Jun 13 05:40:50 2016 Return-path: Envelope-to: gclcip-std-proposals@m.gmane.org Original-Received: from mail-io0-f198.google.com ([209.85.223.198]) by plane.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1bCIk6-0007Lb-6F for gclcip-std-proposals@m.gmane.org; Mon, 13 Jun 2016 05:40:50 +0200 Original-Received: by mail-io0-f198.google.com with SMTP id 5sf193541168ioy.2 for ; Sun, 12 Jun 2016 20:40:49 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=isocpp-org.20150623.gappssmtp.com; s=20150623; h=date:from:to:cc:message-id:in-reply-to:references:subject :mime-version:x-original-sender:reply-to:precedence:mailing-list :list-id:x-spam-checked-in-group:list-post:list-help:list-archive :list-subscribe:list-unsubscribe; bh=sC2s6/jt9RCimKK7IVzeYDL9RfAsRcmWYAhJH8yuZF0=; b=D+rWH8QeOT3VfiXW9JWMxA36D65zNeglZ3s+cwoswQOXEx+qH8OvL5TLElvt0lYRRS EaU7P4ZJvIRFpqAN6CAvMomV2uQ5YPpDFJa/E4iEbtP1ImmacPLW5SBy7CU6qvx/+y5f Y7uuvWDpZJaf5/wId6+UO2EZgQD2EAUvY8eo9mcGNcwqZoWEA/7h/Ad4qpU1GJwEq+9y xnoHSOFSEw1FuUHWR7KX/fxbXh+DnGLMgfjjh0vl7f8XGWgdJWYycmz140UhEprWlMtb CSU5hB06J09nuWeK0uUsCKfT4UBgMgyOOpKjsKp+QxLqRjl7gmuLLFEZJdXzGQa7bdnJ WIew== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=date:from:to:cc:message-id:in-reply-to:references:subject :mime-version:x-original-sender:reply-to:precedence:mailing-list :list-id:x-spam-checked-in-group:list-post:list-help:list-archive :list-subscribe:list-unsubscribe; bh=sC2s6/jt9RCimKK7IVzeYDL9RfAsRcmWYAhJH8yuZF0=; b=09nDQRtHJU1UXzCTIx0MTfTWaf8yAR2YeS2tHK5QElkQFdv0DgscNrioYLzmZjdQSF 0+5Nrvz5Z9C462dgc9Z9mg/p05eS6p9xphxNwtOq8FZWeKFJgRjvBz8SQodLnOH39IsL wV9HnQ44trQzY2yUj0q/32hbCE7Y4zLhb3odLD2fI7sip8Tp0/wREW/Lfavz12mWUMQp uC+40T4IFIweEEMKv0oF4HhFChNiCMbJE5VU5ppK0BW0aQ/BmBOIEkibStJl+9YOvNyP +4lN0MezxFD9a3n7iYGicHlAphCS7/0FE/SpKAxK6kv5EFDRR9nRYo2UEOnyJjGIQh/I tpQA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:date:from:to:cc:message-id:in-reply-to :references:subject:mime-version:x-original-sender:reply-to :precedence:mailing-list:list-id:x-spam-checked-in-group:list-post :list-help:list-archive:list-subscribe:list-unsubscribe; bh=sC2s6/jt9RCimKK7IVzeYDL9RfAsRcmWYAhJH8yuZF0=; b=lSKXgt+6lYfvOaYRBM+bgysYKOK5NEWF+rzzIiVuK1tya7elm4Zm753qZaUa3W0H29 FtLngtbGCTADO+d191ux72pbxwdS0Q7PfTslyAC74ybTszyB0YJcFibpdl7chVknfVbM b2WUc79txt3o5x3iFwh7y6sUCD0kxT7grEl0kl5G1yboFDFEzTltVaaysyHGp97p1CqK Bmapgcw8HjFmo/hZqmalRAxq6IA3gNUxl5PLYs8ovW/0onRKp4RNwY1QkcUziBGsmi8J U7LdzZdv9I+An8CR+B9d6jvWX6etH+8yGN/zenE8k7pGKWJPjHTAIvXWOHtYpRK9w1dL c7Vg== X-Gm-Message-State: ALyK8tKDhuNKWdEhFhhrZCvDVGtVW7ybrUDUcY7J/8pvWdwCFC11uglec7hgJ0NqvTdI4Q== X-Received: by 10.157.6.3 with SMTP id 3mr11112047otn.47.1465789249148; Sun, 12 Jun 2016 20:40:49 -0700 (PDT) X-BeenThere: std-proposals@isocpp.org Original-Received: by 10.36.33.70 with SMTP id e67ls420433ita.15.gmail; Sun, 12 Jun 2016 20:40:48 -0700 (PDT) X-Received: by 10.36.1.15 with SMTP id 15mr121698itk.6.1465789248269; Sun, 12 Jun 2016 20:40:48 -0700 (PDT) In-Reply-To: <8AB38C1F-590D-4F81-9839-D7A4604E1831@gmail.com> X-Original-Sender: alexander.zywicki@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:26309 Archived-At: ------=_Part_743_64243900.1465789247040 Content-Type: multipart/alternative; boundary="----=_Part_744_99390176.1465789247040" ------=_Part_744_99390176.1465789247040 Content-Type: text/plain; charset=UTF-8 How do you all feel about this definition for a clock? #include #include //define audio_clock as high_resolution clock if high_resolution clock is_steady==true else use steady_clock //conditional will result in a clock that is monotonic either way //but can result in using a high_resolution_clock on certain platforms using audio_clock = typename std::conditional:: type; On Sunday, June 12, 2016 at 4:09:44 PM UTC-5, alexande...@gmail.com wrote: > > 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/2943c5c2-2c46-4447-b8f6-7647fc34d52c%40isocpp.org. ------=_Part_744_99390176.1465789247040 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
How do you all feel about this definition for a clock?
=
#include= <chrono>
#include <type_traits>

//define audio_clock as h= igh_resolution clock if high_resolution clock is_steady=3D=3Dtrue else use = steady_clock
//co= nditional will result in a clock that is monotonic either way
//but can result in using a = high_resolution_clock on certain platforms
using audio_clock =3D typename std= ::conditio= nal<std::chrono::high_resolution_clock::is_steady,
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 = =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2= =A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 std::chrono::high_resolution_clock,
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 = =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2= =A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 std::chrono::steady_clock>::type;



On Sunday, June 12, 2016 at 4:09= :44 PM UTC-5, alexande...@gmail.com wrote:
In that case I would argue fo= r the use of the "std::chrono::steady_clock" based on the fact th= at it is specified to be a monotonic clock.=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 &q= uot;is_steady" always be true?


On Jun 11,= 2016, at 4:09 AM, Andrey Semashev <andrey.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 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://grou= ps.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.o= rg.
To view this discussion on the web visit h= ttps://groups.google.com/a/isocpp.org/d/msgid/std-proposals/35608= 28.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.= com/a/isocpp.org/d/msgid/std-proposals/2943c5c2-2c46-4447-b8f6-7647fc34d52c= %40isocpp.org.
------=_Part_744_99390176.1465789247040-- ------=_Part_743_64243900.1465789247040-- .