View Issue Details

IDProjectCategoryView StatusLast Update
0004802ardourbugspublic2020-04-19 20:16
Reportermikehihz Assigned Tocth103  
PrioritynormalSeverityminorReproducibilityalways
Status closedResolutionfixed 
Target Version3.0 
Summary0004802: Ardour does not correctly handle Audio Unit custom views that change size
DescriptionSUMMARY
Ardour does not display custom views correctly that change their size. Examples of Apple Audio Units that will fail are AUSampler, Dynamics Processor, AUMultibandCompressor, AURoundTripAAC, or any AU that publishes the AUGenericView as its custom view (and has clumps which are collapsable).

To fix this issue, the host must listen to NSView notifications for NSViewBoundsDidChangeNotification and NSViewFrameDidChangeNotification and respond appropriately.
TagsNo tags attached.

Activities

2012-03-30 19:02

 

paul

2012-04-19 20:00

administrator   ~0013143

Thanks so much for the information. I was trying to catch size notifications, but was using the wrong notification event to do so. Should have this fixed soon.

mikehihz

2012-04-19 21:10

reporter   ~0013144

Thanks. Looking forward to a resolution.

paul

2012-04-19 21:56

administrator   ~0013145

It seems trickier than either of us suspect. I'm testing on Snow Leopard with NSViewFrameDidChangeNotification & NSViewBoundsDidChangeNotification and ardour doesn't appear to receive either. Continuing on ....

paul

2012-04-20 12:37

administrator   ~0013149

it seems more complex than meets the eye. i now catch frame size changes from the plugin's NSView, but when i resize the window in response, the dynamics processor resizes its "main" display area to fit the new window size, rather than leaving that the same size and making the "Details" section visible.

paul

2012-06-02 16:15

administrator   ~0013355

This has been fixed in Ardour3 and Ardour2 in SVN, and will appear in the next release(s) of both version.

As a footnote, the actual solution to this is FAR, far more complex than just listening to a notification, and was indicated thus all the way back in 2005 when Apple first "approved" this sort of GUI behaviour.

system

2020-04-19 20:16

developer   ~0023014

Issue has been closed automatically, by Trigger Close Plugin.
Feel free to re-open with additional information if you think the issue is not resolved.

Issue History

Date Modified Username Field Change
2012-03-30 19:02 mikehihz New Issue
2012-03-30 19:02 mikehihz File Added: Screen Shot 2012-03-19 at 11.20.pdf
2012-03-31 23:39 cth103 cost => 0.00
2012-03-31 23:39 cth103 Target Version => 3.0 beta4
2012-04-19 20:00 paul Note Added: 0013143
2012-04-19 21:10 mikehihz Note Added: 0013144
2012-04-19 21:56 paul Note Added: 0013145
2012-04-20 12:37 paul Note Added: 0013149
2012-05-23 15:08 cth103 Target Version 3.0 beta4 => 3.0
2012-06-02 16:15 paul Note Added: 0013355
2012-06-02 16:15 paul Status new => feedback
2012-06-02 16:49 cth103 Status feedback => resolved
2012-06-02 16:49 cth103 Resolution open => fixed
2012-06-02 16:49 cth103 Assigned To => cth103
2020-04-19 20:16 system Note Added: 0023014
2020-04-19 20:16 system Status resolved => closed