The example VST plugin is not working in VSTLord: it says “the plugin is not compatible with composited windows”
Doh! Thanks for spotting that one… Very stupid of me indeed. But as I say, this is all still work-in-progress! Many thanks for the help, folks!
Well it definitely is compatible. I wonder how it’s making that decision?
I just noticed that my “ApplicationProperties” instance saved its data in a folder located in the current directory and named
"UUUUUUUUUUUUUUUUUUUUUUUUUUUU^A/Library/Preferences" !?
[quote=“jpo”]I just noticed that my “ApplicationProperties” instance saved its data in a folder located in the current directory and named
“UUUUUUUUUUUUUUUUUUUUUUUUUUUU^A/Library/Preferences” !?[/quote]
Wow!
Well, that looks like the code that replaces the “~” with your home directory path is broken… But I’ve just tried it here and it seems completely fine. What OS version/etc are you using? And does your home path contain unicode chars or anything difficult?
Well, I can’t reproduce it anymore… very strange. Maybe it was just a side effect of the AudioSampleBuffer bug
Compiled juce ok: 10.4.11 / xcode 2.5
Tried the RTAS demo:
juce_RTASWrapper.o reference to undefined attachSubWindow(void*, juce::Component*)
Doesnt seem to be declared for osx anywhere only #if _MSC_VER
in juce_RTASUtilities.cpp
Yep, could well be just memory corruption.
[quote]
Tried the RTAS demo:
juce_RTASWrapper.o reference to undefined attachSubWindow(void*, juce::Component*)
Doesnt seem to be declared for osx anywhere only #if _MSC_VER
in juce_RTASUtilities.cpp[/quote]
You’ll need to make sure your project contains the juce_RTASUtilities.mm file. Did I forget to add it to the demo project?
juce_RTASUtilities.mm was missing, but my fault, its there by default. RTAS redraw problems now seem to be ok, well done!
I did notice that when resizing, the overlay window resizes but the parent window only updates to the new size when you release the mouse.
Nice work Jules.
Is there an official way to do an auto-release pool? I’m doing this now:
[code]#include “Synchromesh_AutoReleasePool.h”
#include <Cocoa/Cocoa.h>
ScopedAutoReleasePool::ScopedAutoReleasePool()
{
// According to QTCoreVideo101, when we get here there’s no Autoreleasepool so Obj-C is f’ed
NSAutoreleasePool* newPool = [[NSAutoreleasePool alloc] init];
pool = (void*)newPool;
}
ScopedAutoReleasePool::~ScopedAutoReleasePool()
{
NSAutoreleasePool* oldPool = (NSAutoreleasePool*)pool;
[oldPool release];
}
[/code]
Bruce
Ah ha! You made the exact same class. That’s why mine was getting confused.
Do I get a gold star for making a juce style class?
Bruce
[quote]I did notice that when resizing, the overlay window resizes but the parent window only updates to the new size when you release the mouse.
[/quote]
I think that was a deliberate tweak to stop it getting into a recursive loop or something. PT doesn’t really expect its windows to get resized, so isn’t really geared up for it.
[quote=“Bruce Wheaton”]Ah ha! You made the exact same class. That’s why mine was getting confused.
Do I get a gold star for making a juce style class?
Bruce[/quote]
Welcome to the Borg…
How do you specify a carbon UI when building AU, live 6.07 for instance
won’t display cocoa UI.
Seems i spoke too soon on RTAS, i still get the blank screens, if i click on the
desktop then click on the mix window, the juce gui goes blank, while typing this
in firefox the juce gui overlay window has redrawn itself over firefox - very odd.
I managed to recompile three AU audio plugins with Cocoa, everything’s cool except:
- the resizer doesn’t work (also not for JUCEDemoAU)
- the ‘close’ button on a DocumentWindow (child component of the main window) doesn’t work
- Ableton live doesn’t seem to support Cocoa, is that right?
But hey, thanks for the great work!
[quote=“eboy”]How do you specify a carbon UI when building AU, live 6.07 for instance
won’t display cocoa UI.
Seems i spoke too soon on RTAS, i still get the blank screens, if i click on the
desktop then click on the mix window, the juce gui goes blank, while typing this
in firefox the juce gui overlay window has redrawn itself over firefox - very odd.[/quote]
I took out the carbon UI stuff from the AU code because I was having problems building with it, though I guess it’d be possible to write a carbon wrapper class for it. I’d really rather avoid spending too much time working on a deprecated interface though - VSTs will still work in Live 6!
The window in front of firefox is probably because it’s using the old floating-window-in-front-of-the-host-window trick - I’ll have a play and see what I can do about that.
Very strange about the blank screens, but thanks for the heads-up, I’ll see if I can reproduce it…
Were you also able to reproduce the issues with the close button on document windows and with the resizer?
Haven’t tried yet. Are you sure the document window thing isn’t just because you’ve not implemented the closeButtonPressed() method?
Yes. It worked fine with the Carbon version. Now the button doesn’t seem to get any mouse signals (when the mouse enters its area, it doesn’t “light up”).
Didn’t you say this documentwindow is a child component? (i.e. not directly on the desktop?)
Maybe I used the wrong terminology… there’s the main plugin window, and the DocumentWindow in question is a child component of the main window (its content component is a colour selector which can be used to change the coulours of the main window). It appears by pressing a button in the main window; after that it can be dragged around in the plugin rectangle, but not closed (when using Cocoa, that is).
Right, so it’s just a lightweight juce component. Well, the fact that it’s using cocoa is irrelevent then, because a lightweight window is just like any other juce component, and far removed from any native code… Very odd. Can’t think of any reason it’d behave differently…?