Skip to main content
Participant
September 11, 2013
Answered

Recording duration

  • September 11, 2013
  • 1 reply
  • 669 views

Hi,

I'm using the API call:

/api/xml?action=sco-contents&sco-id=XXXXXXX&filter-icon=archive&sort-date-created=desc

to get a list of recordings for a particular meeting room.  In the results I see this kind of thing:

<sco sco-id="X" source-sco-id="" folder-id="X" type="content" icon="archive" display-seq="0" duration="7596" is-folder="0">

<name>Tuesday</name>

<url-path>/X/</url-path>

<date-begin>2013-09-10T10:06:21.357-05:00</date-begin>

<date-end>2013-09-10T12:12:57.910-05:00</date-end>

<date-created>2013-09-10T10:06:21.357-05:00</date-created>

<date-modified>2013-09-10T12:12:57.910-05:00</date-modified>

<is-seminar>false</is-seminar>

</sco>

Now, I thought the "duration" attribute was the duration of the recording, but can't figure out how 7596 relates to the 2:06 actual running time (see "date-begin", "date-end" fields).  Does anyone know what the duration attribute means?  Is it useful for getting the duration of the recording, or do I need to diff the two dates? 

-Jim

    This topic has been closed for replies.
    Correct answer Jorma_at_Knox

    The duration field is in seconds 2:06:36 = ~126 min 36 seconds = 7596 seconds.

    Just be glad that it isn't displayed in milliseconds (7596000)!

    1 reply

    Jorma_at_Knox
    Jorma_at_KnoxCorrect answer
    Legend
    September 11, 2013

    The duration field is in seconds 2:06:36 = ~126 min 36 seconds = 7596 seconds.

    Just be glad that it isn't displayed in milliseconds (7596000)!

    jimr452Author
    Participant
    September 11, 2013

    Ooops - sorry for the silly question.  I had done the math quickly and I guess messed up.  That makes sense, though milliseconds would be more accurate