The UK Home Automation Archive

Archive Home
Group Home
Search Archive


Advanced Search

The UKHA-ARCHIVE IS CEASING OPERATIONS 31 DEC 2024


[Message Prev][Message Next][Thread Prev][Thread Next][Message Index][Thread Index]

RE: Time formats ( was TelCanto V1.1.3)




------=_NextPart_000_005F_01C504C3.2A95EE90
Content-Type: text/plain;
charset="US-ASCII"
Content-Transfer-Encoding: 7bit

Or how about SMPTE timecode format - or this a step too far?
This is what pro kit uses. It's quite cranky though being rooted in old
broadcast film/video standards.
I think I posted on this ages ago, might search the archive.

_____

From: Kevin Hawkins [mailto:lists@xxxxxxx]
Sent: 27 January 2005 19:33
To: xAP_developer@xxxxxxx
Subject: Re: [Fwd: Re: [xAP_developer] TelCanto V1.1.3]


Does anyone have a view (xap-audio schema)  on whether we should
represent elapsed time or track length in an HH:MM:SS or MM:SS or other
formatted way or whether we should just present times as one number - in
ms    - which is my current favourite.  Although using ms resolution is
a bit of a nonsense in the sense of delay times on udp delivery the  use
of seconds is defintely too granular so it's the next logical step...
Having formatted times allows for easier display in a more human
readable format but it can be determined from the ms time.  Having ms
allows easier maths for remaining etc. Or both ??  elapsed=83000
formatted_elapsed= 00:01:23

Kevin





_____


xAP_Development Main Index | xAP_Development Thread Index | xAP_Development Home | Archives Home

Comments to the Webmaster are always welcomed, please use this contact form . Note that as this site is a mailing list archive, the Webmaster has no control over the contents of the messages. Comments about message content should be directed to the relevant mailing list.