How to connect the Apple Pitch Shift Audio Unit plugin and the like

Question

How do you place the PitchShift Audio Unit plugin correctly in your own window?

I am developing a Mac application that hosts Apple Unit modules provided by the Apple system. With the new OSX 10.7 Lion, some of the plugins have updated the presentation. PitchShift is one of them.

PitchShift and some others have new buttons for changing parameters. When the handle is rotated with the mouse, a horizontal bar is displayed under the handle showing the value of the handle parameter.

This strip remains on the screen after releasing the handle and even after closing the window. If I click one of the buttons, creating a panel of rogue values ​​and moving the window where the PitchShift view is located, the panel remains where the window used to be. And if I press the knob again at this moment, a new bar appears, but both bands are actively updated with a change in the parameter parameter value. This happens every time I repeat this process with a large number of bars on the screen.

Several times with this case, my application exits with poor access in the NSApplicaionMain () call in the main.m file.

I checked in Logic 9 and this does not happen there. The bar seems to be tied directly to the handle, and thus disappears immediately after you allow the handle to move with the mouse.

I set the PitchSHift view as the contentView of a separate NSWindow.

How does Logic keep this aside, or how can I?

I tried to see if the parameter values ​​are showing where the subitems of the PitchShift view are, but they don't seem to look.

Any help would be greatly appreciated.

EDIT: When a value string appears, I get the following output in the console from my program: Circle and line do not intersect

So, I found that CALayers uses kernel animations. Now the problem is that value level layers are not part of the PitchShiftView level hierarchy. In other words, I can find all other layers that create pitchShiftView, but not layers for value bars. It seems like this could be the whole problem.

Answer 1

I finally figured it out. Parameter value strings are child windows of a window that looks like an audio device.

To solve the problem, I catch the mouse events for the window in my NSApplication subclass, and then close the child window (otherwise called the value bar) so that they do not remain on the screen.

This did not stop the exit with poor access. Now I think this is a separate issue, which seems to be related to these protracted child windows.