error with manual audio annotation add-on

Hello,

I used matlab to install this add-on: http://www.mathworks.com/matlabcentral/fileexchange/18378-manual-audio-annotation

When I run it, it fails since its using an older api call (waveread) which has been replaced with the new api call (audioread) which can read multiple types of audio files and not just .wav files.

So, when I run the add-on it breaks in the matlab.m code for this add-on when it tries to perform waveread(). I modified the code in the add-on to use audioinfo and audioread, however when I now run the code it says it can not find audioinfo.m in path. Also, at the command line in the debugger when it fails, I can not type the audioinfo() routine either. It also has the same error message.

So, do add-ons have a seperate path from the normal matlab installation? How do I solve this problem? I am using the 2017 version of matlab on osx.

JOhn

Answer 1

[David Ding]

Hi John,

Your best bet is to ask the owner of the "Manual Audio Annotation" add-on to update the API and incorporate "audioread" instead of "wavread" and make it up-to-date with MATLAB R2017a. For now, editing the downloaded API would not yield the desired result because add-ons indeed have a different path from that of the MATLAB installation. The add-ons are typically stored at:

/matlabroot/../SupportPackages

Where ".." indicates the parent directory. Thus, the files of a downloaded support package is outside the directory of the MATLAB root directory. Hence, when you change the API from "wavread" to "audioread", the dependent functions are not going to be found on the path.

You can type

which audioinfo
which audioread
matlabroot

in the MATLAB command prompt to confirm that these functions are within the MATLAB root. Then, type

path

to view the list of paths recognized by MATLAB. You will see that the support package lies outside of MATLAB root. Essentially, it means that this particular third-party add-on is currently not compatible with MATLAB R2017a.

Thanks,

David

[John Davis]

Doesn't the add on provide the source? Could I not modify this source as I have done so it works with addons? Perhaps include the path in matlab variable or something?