• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: Transport State?
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Transport State?


  • Subject: Re: Transport State?
  • From: William Stewart <email@hidden>
  • Date: Fri, 26 Mar 2004 10:53:00 -0800

On 26/03/2004, at 7:48 AM, Jeremy Sagan wrote:

> The new SDK says "a third callback to provide additional information
> that is not currently available". It is very hard for hosts to
> implement this if it is not available. If hosts cannot implement it,
> then obviously plug-ins also cannot. When will this be available?

Its "available" now, in the sense that the API is described and is able
to be implemented. The property mechanism in AUBase implementations
will safeguard against using this with existing AU's (ie. shouldn't
cause you any problems)...

The text here isn't as clear as it should be obviously.

>
> The new SDK says " Transport State Has Changed
> - indicates that some state of the host's transport has changed. For
> instance, the time-line has started or stopped, the position within the
> time-line has changed (for eg. the SPL has been moved to a new
> location, or the transport is in cycle mode, and has jumped from the
> end back to the start of the cycle)."
>
> I think this is a mistake. The transport changed should reflect changes
> in the transport buttons themselves. If cycling back is a change in the
> transport then normal forward movement during play is also.

outTransportStateChanged

Is described to indicate a discontinuity in the time line... Whilst
this can be inferred by the AU making calculations and comparisons, it
was thought that there should be a clear indication from *one* place
that the current buffer in AU is being asked to render is from some
different position in the time line than its previous one. Whether this
occurs from intervention by the user (clicking on a "start" button), a
jump in the position of the song (from *whatever* source).

Bill

>
> Jeremy
> _______________________________________________
> coreaudio-api mailing list | email@hidden
> Help/Unsubscribe/Archives:
> http://www.lists.apple.com/mailman/listinfo/coreaudio-api
> Do not post admin requests to the list. They will be ignored.
>
>
--
mailto:email@hidden
tel: +1 408 974 4056

________________________________________________________________________
__
Culture Ship Names:
Ravished By The Sheer Implausibility Of That Last Statement
I said, I've Got A Big Stick [OU]
Inappropiate Response [OU]
Far Over The Borders Of Insanity And Still Accelerating [Eccentric]
________________________________________________________________________
__
_______________________________________________
coreaudio-api mailing list | email@hidden
Help/Unsubscribe/Archives: http://www.lists.apple.com/mailman/listinfo/coreaudio-api
Do not post admin requests to the list. They will be ignored.


References: 
 >Transport State? (From: Jeremy Sagan <email@hidden>)

  • Prev by Date: Re: Stuck Notes
  • Next by Date: Re: Stuck Notes
  • Previous by thread: Transport State?
  • Next by thread: midi librarian OSX
  • Index(es):
    • Date
    • Thread