• 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: AU outIsPlaying parameter problems
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: AU outIsPlaying parameter problems


  • Subject: Re: AU outIsPlaying parameter problems
  • From: Stefan Gretscher <email@hidden>
  • Date: Mon, 5 May 2008 10:41:45 +0200

Hi Brett,

(taking this back to CoreAudio-API so others can follow)
Thanks for the sample project. I can confirm you're not calling the callbacks outside render, and I also checked
the project in the debugger and confirmed that if your plug-in is rendered in stop mode, it receives proper
playback state information (and outputs it correctly to the console).


I think your problem originates in the expectation that Logic will always render your plug-in, even if there's no
input. This is not the case - not in stop and not in playback either. If there's silence coming in and the tail time
has elapsed, rendering is stopped. This happens in stop as well as in playback - you can place two audio
regions on the same track with a long gap inbetween, then rendering will be paused inbetween.
In stop the same thing is happening: there's no input for the playback tracks, so rendering is stopped after the
tail time(s) have elapsed.
You can go ahead and place your plug-in in an insert slot behind a software instrument plug-in. If you now
play that software instrument in stop mode through a keyboard (you can use the Caps Lock keyboard in Logic
for testing this), you'll see that rendering is done while notes are sounding and stopped if the instrument
becomes silent.



Best, Stefan


Am 30.04.2008 um 11:50 schrieb Stefan Gretscher:
I just had a brief look at this in the debugger and as far as I can tell there are correct values returned by Logic.
I wonder if you may be calling the host callback out of context - you may only call these from inside rendering.
If you're calling it outside render, Logic will just bail out, not touching any of the pointers you've passed.
That would explain the behavior you're reporting. If you're calling from inside rendering and still not getting
proper values please contact me off-list how to get a build of your AU so I can debug this.


Am 29.04.2008 um 05:06 schrieb Brett Takacs:
I am writing an AU plugin which requires the plugin to know when playback from the host's transport starts and stops. Using Logic 8, I have tried *HostCallback_GetTransportState parameters such as *outIsPlaying and *outTransportStateChanged, but through debugging (using printf and Console view) the value of these parameters is always 1 (TRUE), never showing 0 (FALSE). Also, they never show output values when playback is stopped. Therefore, when transport stops, the plugin doesn't detect the stop and doesn't know when transport starts again. Do these parameters work correctly in Logic?





------------------------------------ Stefan Gretscher plug-in development & 3rd party developer support

phone: (+49)-4101-495-586 (Central European Time)
AU developer support: email@hidden
TDM developer support: email@hidden

Apple GmbH
Geschäftsführung: Georges Guyon de Chemilly
Sitz der Gesellschaft: München
Amtsgericht München, HRB 66158



_______________________________________________
Do not post admin requests to the list. They will be ignored.
Coreaudio-api mailing list      (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden


  • Prev by Date: Re: Producing Redbook-compliant data
  • Next by Date: Getting AU to produce sound output
  • Previous by thread: Re: Producing Redbook-compliant data
  • Next by thread: Getting AU to produce sound output
  • Index(es):
    • Date
    • Thread