• 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: Logic guys- YIKES. Can I haz DP bug in Logic 8? :P
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Logic guys- YIKES. Can I haz DP bug in Logic 8? :P


  • Subject: Re: Logic guys- YIKES. Can I haz DP bug in Logic 8? :P
  • From: "Sophia Poirier [dfx]" <email@hidden>
  • Date: Mon, 24 Sep 2007 16:40:26 -0400

On Sep 24, 2007, at 8:40 AM, Chris Johnson wrote:

Hi guys. I've just got this email and I am most alarmed.

I've run into this behavior before- on Digital Performer- and it
seemed to indicate the plugin was not being initialized and was
starting up with garbage data. I've found that this can screw things
up so bad the whole channel or buss is blown away for some time-
similarly if you make a coding bug and produce impossibly big output,
the same thing can happen. The plugin being referred to, 'Logical',
works on my machine and does not produce unusual output there.

On Sep 23, 2007, at 7:58 PM, tony brown wrote:
hi chris,
i've recently installed logic studio on a new hard disk with a new
operating system 10.4.10
and yesterday added the new pro app updates from apple.

i have also re-installed 'logical' and it is the sole plug in my
component folder.

when i called up an instance on a master fader of a song i was mixing
then there were two short popping noises followed by silence.

as you can see by the screenshot the right side appears to be gone.

I'm investigating a workaround in which I try to do the Apple- prescribed initialization, but also set a special value that probably wouldn't be there if there's garbage data, and check every control update to see if that value is what I gave it in initialization. If it's not, I know the host failed to start the plugin correctly and I'd blank all data there. I'm concerned because this still allows for bad data, 'pops' and blasts of white noise between control updates, for however many sample frames there are, but balk at the idea of checking every sample to see if the initialization was bad- what a waste.

	Guys, what's the deal with this? I refuse on principle to blame the
host developer and take no responsibility, but my hands are pretty
tied IF the host isn't actually working the plugin correctly, and I
depend on both me and the host doing things as intended. I wasn't
thrilled with this happening on DP, but to have it happening on Logic
8- if that IS what's happening- is a catastrophe.

	In your opinions as fellow developers and coreaudio mavens, do I
need to drop everything and start to build in explicit checks to see
whether the plugin is operating without having been initialized? I
have upwards of FIFTY plugins, the majority of which could possibly
be subject to bad behavior if they're not having 'kernel:reset()'
called. Either I don't take responsibility for handling this- or my
life is about to become update hell with no warning at all :P


Are you possibly getting Initialize and Reset mixed up? I get the sense that you might be throwing them around interchangeably in what you write, and if so, I think the problem here is that you need to realize that they are separate and distinct.

Logic 8 definitely Initializes AUs before rendering with them. If it didn't, there would be widespread massive problems across pretty much all AUs (in most cases, with them all producing silent output). However, I'm not sure whether it calls Reset between the first call to Initialize and the start of rendering. And a host doesn't have to do this, either. I'm thinking that the problem here may be that you are making that assumption. If not, then sorry, I might be off-base with my suggestions and not understanding your message correctly.

Here's an old thread about this issue:
http://lists.apple.com/archives/Coreaudio-api/2002/Sep/msg00354.html

For my AUs that utilize kernels, I generally do something like this:

ComponentResult FabulousEffect::Initialize()
{
    ComponentResult result = AUEffectBase::Initialize();
    if (result == noErr)
        Reset(kAudioUnitScope_Global, 0);
    return result;
}


Sophia _______________________________________________ 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
  • Follow-Ups:
    • Re: Logic guys- YIKES. Can I haz DP bug in Logic 8? :P
      • From: Chris Johnson <email@hidden>
  • Prev by Date: Re: Logic guys- YIKES. Can I haz DP bug in Logic 8? :P
  • Next by Date: Re: Logic guys- YIKES. Can I haz DP bug in Logic 8? :P
  • Previous by thread: Re: Logic guys- YIKES. Can I haz DP bug in Logic 8? :P
  • Next by thread: Re: Logic guys- YIKES. Can I haz DP bug in Logic 8? :P
  • Index(es):
    • Date
    • Thread