Logic guys- YIKES. Can I haz DP bug in Logic 8? :P
Logic guys- YIKES. Can I haz DP bug in Logic 8? :P
- Subject: Logic guys- YIKES. Can I haz DP bug in Logic 8? :P
- From: Chris Johnson <email@hidden>
- Date: Mon, 24 Sep 2007 00:08:40 -0400
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
I shouldn't say that- a major major host (Logic) has just had a
major major revision. Of COURSE my life could have become update
hell. I just thought Santa Claus existed, fixed all host bugs with my
plugins, and didn't bring any new ones to replace them :D
Chris Johnson
airwindows
_______________________________________________
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