|
04-16-2016, 05:18 PM
|
#1
|
Human being with feelings
Join Date: Feb 2014
Posts: 63
|
AAX !plugInAlgContextContainsEmptyFields
I'm getting a !plugInAlgContextContainsEmptyFields assertion in ProTools 12.3 dev build.
Anyone else seen this and been able to fix it?
|
|
|
04-17-2016, 10:40 AM
|
#2
|
Human being with feelings
Join Date: Dec 2015
Posts: 331
|
That would be a question for the Avid developer's forum, I think—you'd need to know what the assertion means, to start. Yeah, I get it, and ignore it. (But it's just a warning that is unlikely to matter for you. The dev build version that was out when I started my plugin erroneously had this raised to a critical error and would force a quit, but they fixed it in the next build.)
|
|
|
04-17-2016, 12:18 PM
|
#3
|
Human being with feelings
Join Date: Feb 2014
Posts: 63
|
I think its reasonable to ask here if someone has found a fix here for an AAX related problem with iPlug's implementation, no need to go into any detail, or PM is necessary. It's dangerous to assume these types of warnings have no side effects
|
|
|
04-17-2016, 03:21 PM
|
#4
|
Human being with feelings
Join Date: Dec 2015
Posts: 331
|
Quote:
Originally Posted by gstuff
I think its reasonable to ask here if someone has found a fix here for an AAX related problem with iPlug's implementation, no need to go into any detail, or PM is necessary. It's dangerous to assume these types of warnings have no side effects
|
I think you misunderstand.
First, I'm assuming, from what you've said so far, that you don't know what it means. That's why I suggested trying the Avid forum. It might be hard to get traction here for a warning returned internally by PT.
Second, I didn't say that I was assuming that this (not "these types"—this) warning has no side effects. I've been told it's not a problem for me by someone at Avid who should know (because I asked him). He only knows that I'm working on effects plugins. I have no details of what the warning implies.
Now, I can't say that it won't be a problem for you. The warning may be more significant for certain types of plugins—which is also why I suggested the developer forum.
|
|
|
04-17-2016, 03:37 PM
|
#5
|
Human being with feelings
Join Date: Feb 2014
Posts: 63
|
I know what the problem pertains to, as I checked first on the Avid forum, this is an iPlug implementation detail, hence why it's more likely someone like Oli may have it on his radar. But thanks anyway.
|
|
|
04-18-2016, 04:31 AM
|
#6
|
Human being with feelings
Join Date: Apr 2009
Location: Berlin, Germany
Posts: 1,248
|
Quote:
Originally Posted by gstuff
I know what the problem pertains to, as I checked first on the Avid forum, this is an iPlug implementation detail, hence why it's more likely someone like Oli may have it on his radar. But thanks anyway.
|
yes i am aware of it and need to update WDL-OL on github with a fix. I posted about it on the avid forum.
|
|
|
08-21-2016, 01:25 PM
|
#7
|
Human being with feelings
Join Date: Feb 2014
Posts: 63
|
FWIW: The !plugInAlgContextContainsEmptyFields assertion goes away here if I add a PageTable resource, by uncommenting the following line in IPlugAAX_Describe.cpp:
err |= effectDescriptor->AddResourceInfo (AAX_eResourceType_PageTable, PLUG_NAME ".xml" );
Last edited by gstuff; 08-21-2016 at 01:40 PM.
|
|
|
08-28-2016, 07:28 AM
|
#8
|
Human being with feelings
Join Date: Nov 2014
Location: Leiden, the Netherlands
Posts: 36
|
Hi gstuff,
Thanks for this update! I ran into the same issue a few days ago. Hopefully this works without unexpected side effects I'll do some testing the coming week.
JD
|
|
|
09-02-2016, 01:10 AM
|
#9
|
Human being with feelings
Join Date: Nov 2014
Location: Leiden, the Netherlands
Posts: 36
|
Hi all,
With respect to the Avid NDA, as this seems to be Iplug specific: in the meantime I tried uncommenting the line like gstuff proposed, but both on PC and Mac the !plugInAlgContextContainsEmptyFields assertion still comes up on loading the IPlugEffect plug-in. Besides that I’m also getting a build error regarding OTHER_CPLUSPLUSFLAGS in resource.h; but only on Mac. It doesn’t seem to find it. If I uncommented it, ’m able to build a debug version of IPlugEffect on Mac, but I get new build errors in the release version.
Is there anybody who can lend a hand? Thanks in advance!
JD
|
|
|
12-13-2016, 06:10 PM
|
#10
|
Human being with feelings
Join Date: Dec 2015
Posts: 331
|
As mentioned in a previous post, I'm not concerned with making the developer warning go away. But for what it's worth, uncommenting that line does not make it go away for me—the same as JD noted. Unlike JD's experience, though, no additional errors popped up in my release build.
|
|
|
12-13-2017, 10:24 AM
|
#11
|
Human being with feelings
Join Date: Apr 2012
Posts: 279
|
I just ran into that issue too. The mentioned workaround doesn't work on my side either...
Somebody got some more info about this because the warning is still persistent in dev build 12.8 which makes me a bit nervous...?
Does it only appear in the dev builds?
|
|
|
12-23-2017, 03:28 AM
|
#12
|
Human being with feelings
Join Date: Dec 2015
Posts: 331
|
Like I said long ago, I was told it’s not a problem, and my AAX plug-in has been shipping for nine months on Mac OS and Windows with no reported issues. Don’t sweat it.
|
|
|
12-23-2017, 03:45 AM
|
#13
|
Human being with feelings
Join Date: Apr 2012
Posts: 279
|
Quote:
Originally Posted by earlevel
Like I said long ago, I was told it’s not a problem, and my AAX plug-in has been shipping for nine months on Mac OS and Windows with no reported issues. Don’t sweat it.
|
Ok, thanks for answering. Will ignore it then.
I guess you've been told in the old avid board, which isn't available for getting infos anymore ?
|
|
|
12-24-2017, 12:19 AM
|
#14
|
Human being with feelings
Join Date: Dec 2015
Posts: 331
|
Quote:
Originally Posted by stw
Ok, thanks for answering. Will ignore it then.
I guess you've been told in the old avid board, which isn't available for getting infos anymore ?
|
I was told privately by Avid that it was not a problem. Apparently, it’s just a sanity check that a structure is completely initialized, even if some fields aren’t needed.
|
|
|
08-02-2019, 08:37 AM
|
#15
|
Human being with feelings
Join Date: Feb 2014
Posts: 63
|
Resurrecting this thread as I found a fix for this today.
In IPlugAAX_CIPlugParameters.h -> AAX_SIPlugRenderInfo struct, comment out:
AAX_IMIDINode* mOutputNode;
AAX_CTimestamp *mClock;
The error was due to these fields not being set (they aren't referenced either).
See moderator's post in the new Avid dev forum for an instance where this can cause 'bad' problems.
Last edited by gstuff; 08-02-2019 at 08:57 AM.
|
|
|
08-31-2019, 10:53 AM
|
#16
|
Human being with feelings
Join Date: Dec 2015
Posts: 331
|
Can be ignored if you're supporting only macOS 10.8 and up (PT 11 and up). Problem with early PT 10.
|
|
|
Thread Tools |
|
Display Modes |
Linear Mode
|
Posting Rules
|
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts
HTML code is Off
|
|
|
All times are GMT -7. The time now is 04:53 PM.
|