[Message Prev][Message
Next][Thread Prev][Thread Next][Message
Index][Thread Index]
RE: Audio Control schema changes
- Subject: RE: Audio Control schema changes
- From: Edward Pearson
- Date: Mon, 16 Feb 2004 23:34:00 +0000
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0
Transitional//EN">
<TITLE>Message</TITLE>
<DIV><SPAN class="583110723-16022004"><FONT
face="Arial" color="#0000ff" size="2">I
vote for option 4 - option of both time and % based. But I'd like to
include hours too. I quite often rip cd's as disc at once when they are
mixed from track to track (can't stand those annoying pauses) - also, with
my DJ hat on, I sometimes prepare my own mixes and these can run for a few
hours.</FONT></SPAN></DIV>
<DIV><SPAN class="583110723-16022004"><FONT
face="Arial" color="#0000ff"
size="2"></FONT></SPAN> </DIV>
<DIV><SPAN class="583110723-16022004"><FONT
face="Arial" color="#0000ff" size="2">With
my professional audio engineer hat on, I'd suggest hh:mm:ss:ff where ff is
frames as used in SMPTE time code format - there's normally 24 frames in a
second for audio (slight simplification). While I don't think this is
useful for the duration and current position fields, it might be useful for
the seek command (good enough resolution to cue a track starting 'on the
beat'). I'd be happy for current implementations to leave the 'ff' part
always equal to zero '00' but I do think we should standardise on the four
field hh:mm:ss:ff format for any reference to time for audio applications
since this is absolutely standard across the music, film and broadcast
industries and will serve us well in the
future.</FONT></SPAN></DIV>
<BLOCKQUOTE>
<DIV></DIV>
<DIV class="OutlookMessageHeader" lang="en-us"
dir="ltr" align="left"><FONT
face="Tahoma" size="2">-----Original
Message-----<B>From:</B> Stuart Booth [mailto:lists@xxxxxxx]
<B>Sent:</B> 14 February 2004 18:17<B>To:</B>
xAP_developer@xxxxxxx<B>Subject:</B> Re: [xAP_developer] Audio
Control schema changes</FONT></DIV><TT>On Sat, 14 Feb
2004 16:30:05 +0000, James <James@xxxxxxx> wrote:>I vote for using
0-100%.And not for having both absolute time-based and
percentage-basedvalues possible?The options as I see them are:1. Position
in bytes2. As a percentage3. Time-based (mm:ss) [NOT supported by the
Exstreamer]4. Time-based (mm:ss) *or* percentage acceptable;
distinguishable bylength of field/character content.Any other
possibilities?I'd prefer time-based (mm:ss) or percentage being possible in
the samefield.Since this information c
omes only from the device it could supportwhichever it can deal with. Oh,
then again Audio.Seek positions thedevice if it supports that.If I have a
song playing I might want to skip past the intro, so I'dalways want to work
in mins/secs. I for one personally hate spokenintro's in most cases and
like to skip past them. I wouldn't want tohave to guestimate percentage
through the track in this sort of casebecause I never know how long a song
is. "Skip forward 50s" is mucheasier.S-- Stuart Booth
<stuart@xxxxxxx>xAPFramework.net - a xAP software development
framework for .net<A href="http://www.xapautomation.org/";>http://www.xapautomation.org/</A>
<A href="http://www.xapframework.net/";>http://www.xapframework.net/<
;/A></TT>
xAP_Development Main Index |
xAP_Development Thread Index |
xAP_Development Home |
Archives Home
|