1. Community Forum
  2. AWE Designer
  3. Routing error due to blocksize mismatch on custom module development.

Routing error due to blocksize mismatch on custom module development.

5 posts / 0 new
Log in or register to post comments
Last post
Fri, 03/21/2025
6:14am
Monika
#1
Top
#1
Routing error due to blocksize mismatch on custom module development.

Hi DSPC Community,

I'm working on custom module development in Audio Weaver, where I need my module to accept an input block size of 1532 x 1 and produce an output block size of 1536 x 4. I used the preBuild function in MATLAB to declare the input and output properties of the module . However, I'm encountering the following error during the build process:

MATLAB Script:

% ----------------------------------------------------------------------
% Prebuild Function 
% ----------------------------------------------------------------------

function M=custom_module_prebuild_func(M)

M.inputPin{1}.type.numChannels=1;
M.inputPin{1}.type.blockSize=1532;

M.outputPin{1}.type.sampleRate=48000;
M.outputPin{1}.type.numChannels=4;
M.outputPin{1}.type.dataType=M.inputPin{1}.type.dataType;
M.outputPin{1}.type.blockSize=1536;

return;

Fri, 03/21/2025
11:12am
DSPC_Gary
Top

Hi Monika,

Generally speaking, if the input and output block sizes are fixed, I would simply put those code lines in the body of the main matlab function rather than the prebuild function.

In addition, you have to make sure to declare your prebuild function in the main part of your code.

M.name=NAME;

M.preBuildFunc=@custom_module_prebuild_func;

Have you put a breakpoint on your prebuild function to make sure it is getting executed?

Gary

 

Mon, 03/24/2025
5:07am
Monika
Top

Hi Gary , 

Thank you for the response. 

We tried the steps which you mentioned above. 

Please find the output behaviour : 

Q - Have you put a breakpoint on your prebuild function to make sure it is getting executed?

A - yes it executed and the output block-size value updated in the instance properties but not reflected in the output wire properties in the AWE design( block-size remains as same as input). Please find the updated output pin type properties. screenshot_from_2025-03-24_14-07-27.png

Note: Output block-size needs to be different from input block-size. 

 

Thanks, 

Monika 

Mon, 03/24/2025
1:58pm
DSPC_Gary
Top

Hi Monika,

I created a new custom module and added the prebuild function as shown below.  This changes the module's output blocksize to 67.  Let me know if this works for you.

function M= BlockSize_module(NAME)

% M = BlockSize_module(NAME)

% Copies input pin data to the output pin.

%

% Arguments:

% NAME - name of the module

%

% AudioWeaverModule [This tag makes it appear under awe_help]

M=awe_module('BlockSize', 'Copies input wire to output wire');

if (nargin == 0)

return;

end

M.name=NAME;

M.defaultName='BlockSize';

M.preBuildFunc = @blockSize_prebuild;

% Add input and output pins with no data or size restrictions

PT=new_pin_type([], [], [], '*32', []);

add_pin(M, 'input', 'in', 'Input signal', PT);

add_pin(M, 'output', 'out', 'Output signal', PT);

% ----------------------------------------------------------------------

% Code generation details

% ----------------------------------------------------------------------

awe_addcodemarker(M, 'processFunction', 'Insert:\InnerBlockSize_Process.c');

awe_addcodemarker(M, 'discussion', {'Copies the input to the output. '});

% ----------------------------------------------------------------------

% Module browser information

% ----------------------------------------------------------------------

M.moduleBrowser.path = 'Third Party';

M.moduleBrowser.image = '../images/BlockSize.bmp';

M.moduleBrowser.searchTags = 'pass thru through copy';

return;

function M = blockSize_prebuild(M)

numPins = length(M.outputPin);

for i = 1:numPins

M.outputPin{i}.type.blockSize = 67;

end

return;

Thanks,

 

Gary

Thu, 03/27/2025
4:13pm
DSPC_Gary
Top

Hi Monika,

Please also see this forum post.  If you use a blank prebuild function, then your output pins should behave as they were declared.  Without a prebuild function (even a blank one), they are inheriting the values from the corresponding input pins.

Incorrect Output Pin Channel Count | DSP Concepts

Thanks,

Gary