Re: octave not detecting waveread.m again...

[malik martin]

hi, finaly got the chance to try this out:

octave:1> which waveread
which: `waveread' is undefined
octave:2>

Quentin Spencer said that he didn't think that octave couldn't detect
waveread. but that waveread couldnt find tone.wav.

but that says waveread is undefined. and it's in the   /m/audio/directory.

On 6/22/07, malik martin <address@hidden> wrote:
> it's in the same folder as the .m file i loaded. hmm i'll have to try
> again when i get home from school. thanks. i'll let you know what
> happens
>
>
> On 6/22/07, Quentin Spencer <address@hidden> wrote:
> > malik martin wrote:
> > > what do you mean by the output of which waveread? and path is
> > > different in linux  :P when i type it in terminal it just turns out to
> > > be a bad command.
> >
> > The "which" command tells you where a particular command it located on
> > the system. For example, in octave I get:
> >
> > octave:1> which wavread
> > wavread is the user-defined function from the file
> > /usr/share/octave/2.9.9/m/audio/wavread.m
> >
> > When I look at your original output again, it looks to me like the
> > problem is not that octave doesn't see wavread.m, but that wavread.m
> > can't find your file "ton2.wav".
> >
> > Quentin
> >
> >