Re: (semi-OT) hosting plugins that use PACE copy protection
Re: (semi-OT) hosting plugins that use PACE copy protection
- Subject: Re: (semi-OT) hosting plugins that use PACE copy protection
- From: "Ross Bencina" <email@hidden>
- Date: Fri, 16 Jul 2010 00:59:59 +1000
Ok, here's some facts:
- I'm instantiating from the main thread (everything except audio proc
happens in the main thread)
- I get the same problem whether doing it at startup or when my App is fully
loaded with full GUI running
- in AULab the PACE dialog displays correctly -- the buttons (which, by the
way say somthing like "Authorise" and "Quit") are active and you can click
them (in my app they are greyed out and you can't click them).
This reminds me a bit of a problem I have hosting Pluggo VSTs (Which I've
pretty much given up on)-- their GUIs display (sometimes), but they don't
accept any mouse clicks. I wonder if it's possible that my GUI framework is
somehow intercepting or filtering windowing events for alien (plugin)
windows (Pluggo uses overlays) or whether I need to do something special to
get the events to dispatch correctly.
So perhaps this is not a PACE problem afterall, but a more general event
dispatch problem. Anyone seen anything like this? Any clues how to debug it?
Is there a tool to dump a trace of all Carbon GUI events and their traversal
of the Control hierarchy?
Thanks
Ross.
Bill wrote:
I think you have to instantiate the plugin first from the main app thread?
If you try this plugin in AULab, does it work ok there, or does it have the
same problems (we instatiate and initialise the plugin on the main thread)
Bill
On Jul 14, 2010, at 4:16 AM, Ross Bencina wrote:
Hi Everyone
I have a problem with my AU hosting: any plugins which uses PACE copy
protection (paceap.com) display an iLok or PACE dialog when I instantiate
them and then hang with all of the buttons on the PACE dialog disabled. I
have only tested this with demo versions but my users are reporting
similar problems with their licenced versions. If I try to use gdb
naturally PACE exits immediatly. I see similar issues with VST and AU
plugins.
I am guessing that I'm doing something with my event processing (which is
going to be fun, since I'm using the Qt framework) but I wonder whether
anyone has encountered this before and has any ideas how I might solve it.
Or whether PACE provides developer support to plugin hosts for this kind
of thing (thier dev. website seems to require you to buy a licence to
enter).
Any and all thoughts and help appreciated.
Many thanks
Ross.
_______________________________________________
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