<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Webex obj start_time accuracy in Webex for Developers</title>
    <link>https://community.cisco.com/t5/webex-for-developers/webex-obj-start-time-accuracy/m-p/4612626#M854</link>
    <description>&lt;BLOCKQUOTE&gt;
&lt;DIV&gt;
&lt;DIV&gt;
&lt;DIV&gt;how accurate is the following data?&lt;/DIV&gt;
&lt;DIV&gt;&amp;nbsp;&lt;/DIV&gt;
&lt;DIV&gt;1. Meeting.start —&amp;gt; to when meeting starts&lt;/DIV&gt;
&lt;DIV&gt;2. Transcription.statTime —&amp;gt; to when transcription is created and accordingly the&amp;nbsp;&lt;SPAN&gt;offsetMillisecond&lt;/SPAN&gt;&lt;SPAN&gt;&amp;nbsp;mentioned in the&amp;nbsp;&lt;/SPAN&gt;&lt;FONT&gt;&lt;SPAN&gt;transcription&amp;nbsp;snippet.&lt;/SPAN&gt;&lt;/FONT&gt;&lt;/DIV&gt;
&lt;DIV&gt;&lt;FONT&gt;3. Recording.timeRecorded&amp;nbsp;—&amp;gt; to when recording has started.&lt;/FONT&gt;&lt;/DIV&gt;
&lt;DIV&gt;&lt;FONT&gt;&amp;nbsp;&lt;/FONT&gt;&lt;/DIV&gt;
&lt;DIV&gt;&lt;FONT&gt;So far What we have noticed is&amp;nbsp;&lt;SPAN&gt;Recording.timeRecorded is 1 sec behind from what the actual recording&amp;nbsp;suggests while for&amp;nbsp;&lt;/SPAN&gt;&lt;/FONT&gt;&lt;SPAN&gt;Transcription.statTime is 2-3 sec.&lt;/SPAN&gt;&lt;/DIV&gt;
&lt;/DIV&gt;
&lt;/DIV&gt;
&lt;/BLOCKQUOTE&gt;</description>
    <pubDate>Wed, 18 May 2022 20:15:26 GMT</pubDate>
    <dc:creator>jozanini</dc:creator>
    <dc:date>2022-05-18T20:15:26Z</dc:date>
    <item>
      <title>Webex obj start_time accuracy</title>
      <link>https://community.cisco.com/t5/webex-for-developers/webex-obj-start-time-accuracy/m-p/4612626#M854</link>
      <description>&lt;BLOCKQUOTE&gt;
&lt;DIV&gt;
&lt;DIV&gt;
&lt;DIV&gt;how accurate is the following data?&lt;/DIV&gt;
&lt;DIV&gt;&amp;nbsp;&lt;/DIV&gt;
&lt;DIV&gt;1. Meeting.start —&amp;gt; to when meeting starts&lt;/DIV&gt;
&lt;DIV&gt;2. Transcription.statTime —&amp;gt; to when transcription is created and accordingly the&amp;nbsp;&lt;SPAN&gt;offsetMillisecond&lt;/SPAN&gt;&lt;SPAN&gt;&amp;nbsp;mentioned in the&amp;nbsp;&lt;/SPAN&gt;&lt;FONT&gt;&lt;SPAN&gt;transcription&amp;nbsp;snippet.&lt;/SPAN&gt;&lt;/FONT&gt;&lt;/DIV&gt;
&lt;DIV&gt;&lt;FONT&gt;3. Recording.timeRecorded&amp;nbsp;—&amp;gt; to when recording has started.&lt;/FONT&gt;&lt;/DIV&gt;
&lt;DIV&gt;&lt;FONT&gt;&amp;nbsp;&lt;/FONT&gt;&lt;/DIV&gt;
&lt;DIV&gt;&lt;FONT&gt;So far What we have noticed is&amp;nbsp;&lt;SPAN&gt;Recording.timeRecorded is 1 sec behind from what the actual recording&amp;nbsp;suggests while for&amp;nbsp;&lt;/SPAN&gt;&lt;/FONT&gt;&lt;SPAN&gt;Transcription.statTime is 2-3 sec.&lt;/SPAN&gt;&lt;/DIV&gt;
&lt;/DIV&gt;
&lt;/DIV&gt;
&lt;/BLOCKQUOTE&gt;</description>
      <pubDate>Wed, 18 May 2022 20:15:26 GMT</pubDate>
      <guid>https://community.cisco.com/t5/webex-for-developers/webex-obj-start-time-accuracy/m-p/4612626#M854</guid>
      <dc:creator>jozanini</dc:creator>
      <dc:date>2022-05-18T20:15:26Z</dc:date>
    </item>
    <item>
      <title>Re: Webex obj start_time accuracy</title>
      <link>https://community.cisco.com/t5/webex-for-developers/webex-obj-start-time-accuracy/m-p/4612893#M859</link>
      <description>&lt;P&gt;For all the above we always recommend going to the nearest minute. We do provide the seconds too, but as you have already figured out, it may not be accurate to the second. The services that record this information might have a second or two delay to actually write this to the DB as there are a number of backend services that get hit, before final write occurs.&lt;/P&gt;</description>
      <pubDate>Thu, 19 May 2022 09:22:25 GMT</pubDate>
      <guid>https://community.cisco.com/t5/webex-for-developers/webex-obj-start-time-accuracy/m-p/4612893#M859</guid>
      <dc:creator>Raffaele Lagana</dc:creator>
      <dc:date>2022-05-19T09:22:25Z</dc:date>
    </item>
  </channel>
</rss>

