Re: AUSampler view

Subject: Re: AUSampler view
From: Paul Davis <email@hidden>
Date: Thu, 02 May 2013 14:13:06 -0400

Well, filed as Bug ID# 13793712 anyway.

On Thu, May 2, 2013 at 1:48 PM, Paul Davis <email@hidden> wrote:

Thanks for your reply.

The view for AUSampler (and on ML, other plugins) works normally in Reaper (for example). From past experience (I have been working on Ardour on OS X for more than 7 years), I have this strong feeling that Apple's response is likely to be "your host is wrong".

To be honest, I'm even moderately sure that this is true - the problem is, how/why is it wrong? Your plugins (AUSampler and the new auviews on ML) are violating your own technical notes about plugin GUI behaviour (TN2207) (*), which makes me suspicious, but at the same time I have no idea how I would find out what I should correct.

I am happy to file a radar if you think that is the best way to tackle it, but realistically, when you test them in any of the apps that you're likely to try, they will work. Why would an apple dev not just mark the bug report as "no fix required" and move on?

thanks,
--p

(*) "For even better user interface integration, custom Audio Unit Views should refrain from using overlay windows and from opening sheets or auxiliary windows other than for file browsing. All user interface elements should be presented inside the root Audio Unit View by laying out its content dynamically and resizing as necessary."

On Thu, May 2, 2013 at 12:51 PM, Douglas Scott <email@hidden> wrote:

It is never the host's responsibility to handle child windows opened by the plugin view. If you are experiencing a problem, please file a radar so we can track this, thanks.

-DS

On May 1, 2013, at 3:18 PM, Paul Davis <email@hidden> wrote:

> I've mentioned this before, but now after some investigation, I need to ask again.
>
> AUSampler is one of the few examples of Apple-provided AU's on Lion that feature new controls which pop up a new window when manipulated. I recall that many of the standard plugins in Mountain Lion now have these controls in their views.
>
> I've verified that these windows exist as NSWindows, not just NSViews, that they have no parent window, and no title.
>
> What is the relationship of these windows to the window containing the AU View, and how is a host supposed to ensure that they are removed from the screen when the AU View-containing window is removed? In addition, how is the host supposed to ensure that they move with the AU View-containing window when it is moved, since currently they do not ...
>
> As a side note, I've also verified that the view for AUSampler resets its origin within its superview when the "Show Editor" control is clicked. I have no idea what this behaviour is supposed to accomplish, since it also resizes its frame to accomodate the new controls it wants to display.
>
> I'd really, really appreciate a comment on this from someone inside Apple who can comment on what these new control windows do and how a host is intended to handle them.
>
> thanks,
> --p
>

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

_______________________________________________
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

 _______________________________________________
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:
	>AUSampler view (From: Paul Davis <email@hidden>)
	>Re: AUSampler view (From: Douglas Scott <email@hidden>)
	>Re: AUSampler view (From: Paul Davis <email@hidden>)

Prev by Date: Re: AUSampler view
Next by Date: Re: Alternative way to load Audio Units?
Previous by thread: Re: AUSampler view
Next by thread: Can ACCodec support more than one input / one output?
Index(es):
- Date
- Thread