Closed dudleyjosh closed 8 years ago
Ah, there is a chicken and egg problem at the moment. I released this update but madplay
still needs to be added to the packages for openwrt and a new build needs to be released. Basically, I forgot to do that :\
If you want a head start, ssh to the board do this:
opkg update; opkg install madplay
Sorry about that!
I did the opkg update
and opkg install madplay
and that took care of the error, bur I still don't seem get any sound output?
Do you have a .tesselinclude
file with major_malfunction.mp3
in it?
Yes, and I verified that it was getting loaded in /tmp/remote-script
when I ssh'd into the T2.
I took a quick glance at speaker.js
and I don't see/understand where it ever loads the mp3 file from the filesystem? The path gets passed in as a string, but how does it actually load the mp3 file to play it? Does it happen at line 111 state.process = cp.spawn('madplay', args);
with the args parameter?
Is there anything related to controlling volume? If not, what volume level does it default to?
where it ever loads the mp3 file from the filesystem?
Because it doesn't ;)
Does it happen at line 111 state.process = cp.spawn('madplay', args); with the args parameter?
That's correct.
Is there anything related to controlling volume? If not, what volume level does it default to?
Possibly? I've used headphones, earbuds, desktop speakers and one of those fancy bluetooth things that had a 3.5mm jack on it. What do you have plugged in for outputs? Since you're familiar with ssh'ing now, you could go directly to /tmp/remote-script/
and run madplay major_malfunction.mp3
. Also, could you put that mp3 on a dropbox (or similar), so I can give it a try as well? Thanks for being patient, we'll work through this :)
Well the good news is that it was just because I'm an idiot and I can't spell... I had the filename spelled 'major_malfuntion.mp3' and the reason it ended up in the /tmp/remote-script
area was because I had used the --full
option. So, it does work, but it might be handy if it would throw an error (and console.log) if the filename path was invalid.
Thanks for the help.
it might be handy if it would throw an error (and console.log) if the filename path was invalid.
Where was it misspelled? In the .tesselinclude
? Unfortunately there is no way to determine if a glob expression in the .tesselinclude
file is invalid. No matches doesn't mean invalid :|
The actual file itself was misspelled. I would think that if the path to the filename doesn't exist it could be detected when play()
is called and error when the file doesn't exist.
The actual file itself was misspelled. I would think that if the path to the filename doesn't exist it could be detected when play() is called and error when the file doesn't exist.
I will see if I can make this useful :)
I get the following error when I try to play audio using the example provided. Also, the
var path = require('path');
statement is missing from the sample code in the README.md file?See my code below. The error occurs at
sound.play()
.