We used AWE Designer to generate an awb file, used AWELib's API (AWE 6.0) method LoadAwbMem() to load the awb file from memory to AWE. The error returned is -95 (awb file content is invalid). However, if we use the awb file from DSPC's sample project, it works fine. Why the awb file generated by AWE Designer is invalid? I compare the size of awb file generated by AWE designer vs. awb file from DSPC sample project, they are dramatically different. Ours is 640 bytes and the sample project's one is 1540. They both come from the same diagram flow. How did DSPC generate their awb files? other than AWE Designer we used? I used binary viewer to look at the patterns of two files, they are totally different.
I can't attach awb files. Every time I tried, the chrome would crash. I have attached png files to show the binary format/pattern of two awb files.
11:18am
11:24am
The above file is the binary format viewed with hex viewer for awb file from DSPC's sample project.
11:26am
Here is the binary format of awb file generated from AWE designer.
12:25pm
Hi Harry,
Which version of AWE Designer did you use to generate your .awb file? AWE Lib is compatible with .awbs generated by versions 6.X of AWE Designer, whereas aweb.s from versions 8.X are compatible with AWE Core OS (see this discussed in our video on AWE Lib vs AWE Core OS at 9:07 https://www.youtube.com/watch?v=5qUtd9-ktpI). AWE Lib is outdated by several years, so I definitely recommend checking out our documentation on the migration to the latest and greatest version of Audio Weaver: https://dspconcepts.gitbook.io/dsp-concepts/application-notes/awe-6-to-a...
Thanks,
Michael
1:25pm
We used AWE Designer 8.C.2.6 Standard version to generate .awb files. These files are fed into AWELib (or AWE 6.0) library used in our audio_hal. When we debugged the code, found that these awb files are invalid. Does that means the AWELib has ignored our .awb files, we in fact has no ops for our DSPC integration? Thanks you so much for your quick analysis and response!
2:05pm
Hi Harry,
You will either need to follow the documentation and video on updating from AWE Lib to AWE Core OS (highly recommended), or try to rebuild the .awb using a version of AWE Designer 6.X.X.X (highly discouraged).
Thanks,
Michael
2:34pm
After watching the video Migrating from AWELib to AWECore OS, I downloaded the source sample conversion project. The passthrough.awb file is 584 bytes. I used the sample.cpp file to call LoadAwbMem for this .awb, it showed the same error as -95. The awb file attached to the video for AWELib is not working either. So there are two possibilities: (1). the vui_10x6_passthru.awb in DSPC's sample project probably was generated by AWE designer earlier than AWE 6; (2). the AWELib used (libaudiopreprocessing.so built from PreProcessing.cpp + AWELib.a in the sample project) is the wrong version for AWELib 6.0. We need one consistent set of AWELib, AWE designer so that AWE designer generated .awb can be validated by its AWELib.
3:58pm
The AWELib we used is AWELib V1.5 - Build 55. How old is it? What is the last version of AWELib? v6.0? When was the v1.5 released? that is why I see the big discrepancy between .awb generated by AWE Designer 8.* (560 bytes) and .awb file from DSPC sample project (1540 bytes).
4:48pm
Hi Harry,
Let me email you on the side for support.
Thanks,
Michael