Hierachy boards and indirect parameter access table
I have a design in SigmaStudio 4.5 using the ADAU1452 with hierachy boards where, for instance I have 4 output channels which have the same processing map.
So each channel has an identical Hierachy board except that the name of each board is Out1, Out2, OUt3, Out4.
As expected, the PARAM.h file generated has the full hierachical name of each control ie Out1_Gain, Out2_Gan etc...
However, if I add one of these to the Indirect Parameter access table, it doesn't have the hierachy board title to go with it, as if the indirect parameter access table ignores the hierachy.
Is this a bug/oversight, or "by design"
And, aside from avoiding hierachy and indirect param access table, is there a way around it?
Cheers
Alex
Edit Notes
addded tags
[edited by: alexsconway at 9:03 PM (GMT 0) on 5 May 2020]
Audio Signal Processors
adau1452
sigmastudio
SigmaDSP Audio Processors
indirect parameter access table
hierarchy
Show More
Hello Alex,
I think I may understand what is happening. Do you have a project you can zip up and share on the forum? I would like to look at it exactly how you have it setup.
Dave T
hierarchy indirect naming problem.zip
Here you go: two hierarchy boards that are identical apart from name, each with a filter.
only one filter appears in the indirect parameter table.
(perhaps not a useful example - should be using safeload - but it illustrates the problem)
Cheers
Alex
Thanks a lot Alex,
This helps a lot. It clearly shows the problem. I tried to do a workaround for loading this into the Indirect Parameter Access Table by loading it from the cell itself and no luck. It only sets up one of the filters and not the other. So I do not know a work-around yet.
In case you do not know this trick, you can right-click on the cell itself and you see a selection for the indirect parameter access table and you can place the parameters into the table right from the object itself.
So I reported the problem to the programming team so it is in their queue.
At this point I do not think it will be fixed soon. I know the team is busy with other priorities but I will push to get this fixed.
Thanks,
Dave T
Please log in to reply.