• 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: reminder for AU View compatability
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: reminder for AU View compatability


  • Subject: Re: reminder for AU View compatability
  • From: Brian Willoughby <email@hidden>
  • Date: Thu, 23 Oct 2008 00:37:41 -0700

Hi Bill. It seems that you misunderstood me. I only singled out Logic in the first paragraph because Apple develops it. I should have mentioned AULab, too. But you'll note in the second paragraph that I encouraged *all* host app developers to help by reporting any instances of these problems to the specific AU developers, at least where contact information is available.

I don't have any issue with your asking AU developers to look out for this problem and fix it, I merely suggested that host app developers who note the problem should point it out to the specific AU developer, because they may not have noticed, and may not even have certain host apps or configurations.

Brian Willoughby
Sound Consulting


On Oct 22, 2008, at 18:00, William Stewart wrote:
Why do you assume this is Logic? This is causing a number of problems with *different* and *more than one* host app.

Bill

On Oct 21, 2008, at 1:43 PM, Brian Willoughby wrote:
Thanks for the reminder. However, wouldn't it be great if the Logic team also sent specific notices to vendors with violating AUs? I suppose that could be rather limited, since reliable contact information is not available for every AU, and the list would not be complete. At the very least, I hope the Logic team passes on bug reports whenever possible.

Another way to look at the situation is this: If you're reading this on the CoreAudio Mailing List, and you are a host application developer, then please pass on any bug reports from offending AUs that cause the problems Bill is referring to. That would help - at least somewhat - in stamping out this crusty code.


On Oct 21, 2008, at 12:28, William Stewart wrote:
Some time ago we described an intention to have those audio units that provide carbon views to support the composited windowing mode (HIView) that Carbon supports. We also added a checkbox in AULab that would enable developers to make AULab use compositing carbon windows for the audio unit views.

We've seen many au fix problems with compositing windows since that time - so thanks for that effort. However, there are still some audio unit's views that are not compatible with compositing windows. This is affecting some host applications as the move in general is toward this style of windowing, but if the AU view doesn't support it, serious drawing and UI control problems arise.

So, this is a reminder to everyone to please look at all of their audio unit views and make sure that they work with compositing windows. AULab has compositing enabled by default, so it could be as simple as running your audio units in AULab (just check to make sure that compositing is turned on).

Thanks

Bill
_______________________________________________
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


References: 
 >reminder for AU View compatability (From: William Stewart <email@hidden>)
 >Re: reminder for AU View compatability (From: Brian Willoughby <email@hidden>)
 >Re: reminder for AU View compatability (From: William Stewart <email@hidden>)

  • Prev by Date: Re: coremidi virtual endpoint problem
  • Next by Date: Re: using AUMatrixMixer & format conversions
  • Previous by thread: Re: reminder for AU View compatability
  • Next by thread: Multi-input bus (sidechain) configuration
  • Index(es):
    • Date
    • Thread