You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The first problem was installing rabbitmq. That didn't work for me, so in the end I went and downloaded the deb directly.
Then there are all kinds of problems with the node.js - I'm not entirely sure I understand what the problem is, but it is something about the version.
So following the instructions, you have to
sudo apt-get install node.js
and sudo npm install -g npm@latest (need the sudo here)
Then you clone the folder
cd to the new folder
npm install
and if you are unlucky, the thing breaks. The problem when I did this step was with the rebuild of the node-gyp, it just threw up a whole load of errors. This appears to be the same as this issue JustinTulloss/zeromq.node#456
The solution for me was the one suggested there: apt-get install libzmq3 libzmq3-dev
Once I did that, closed down, restarted, and then went back to the folder, I went to the localhost:5000 and got the screen as stated at the end of the instructions. I can now click on the blue and red buttons.. but nothing happens. Something is happening but no audio.
Hello guys, just to say that I was attempting to get the skeleton working but it is missing some steps from the instructions here http://radiodan.net/help/tutorials/simplest-radio-laptop.html#linux
I'm on a linux box running Ubuntu 14.04
The first problem was installing rabbitmq. That didn't work for me, so in the end I went and downloaded the deb directly.
Then there are all kinds of problems with the node.js - I'm not entirely sure I understand what the problem is, but it is something about the version.
So following the instructions, you have to
sudo apt-get install node.js
and sudo npm install -g npm@latest (need the sudo here)
Then you clone the folder
cd to the new folder
npm install
and if you are unlucky, the thing breaks. The problem when I did this step was with the rebuild of the node-gyp, it just threw up a whole load of errors. This appears to be the same as this issue JustinTulloss/zeromq.node#456
The solution for me was the one suggested there: apt-get install libzmq3 libzmq3-dev
Once I did that, closed down, restarted, and then went back to the folder, I went to the localhost:5000 and got the screen as stated at the end of the instructions. I can now click on the blue and red buttons.. but nothing happens. Something is happening but no audio.
`joe@joe-X202EP:~/radiodan-skeleton$ npm start
[OKAY] Loaded ENV .env File as KEY=VALUE Format
[OKAY] Trimming display Output to 56 Columns
9:00:39 AM radiodan.1 | 2016-02-02T09:00:39.292Z - info: [server] Set logging to…
9:00:39 AM app.1 | Hello
9:00:39 AM app.1 | Listening on port 5000
9:00:39 AM radiodan.1 | 2016-02-02T09:00:39.416Z - error: [child-process] Error:…
9:00:39 AM radiodan.1 | at ChildProcess.exithandler (child_process.js:213:12…
9:00:39 AM radiodan.1 | at emitTwo (events.js:87:13)
9:00:39 AM radiodan.1 | at ChildProcess.emit (events.js:172:7)
9:00:39 AM radiodan.1 | at maybeClose (internal/child_process.js:821:16)
9:00:39 AM radiodan.1 | at Socket. (internal/child_process.js:319…
9:00:39 AM radiodan.1 | at emitOne (events.js:77:13)
9:00:39 AM radiodan.1 | at Socket.emit (events.js:169:7)
9:00:39 AM radiodan.1 | at Pipe._onclose (net.js:469:12)
9:00:39 AM radiodan.1 | 2016-02-02T09:00:39.417Z - error: [player] Error: Comman…
9:00:39 AM radiodan.1 | at ChildProcess.exithandler (child_process.js:213:12…
9:00:39 AM radiodan.1 | at emitTwo (events.js:87:13)
9:00:39 AM radiodan.1 | at ChildProcess.emit (events.js:172:7)
9:00:39 AM radiodan.1 | at maybeClose (internal/child_process.js:821:16)
9:00:39 AM radiodan.1 | at Socket. (internal/child_process.js:319…
9:00:39 AM radiodan.1 | at emitOne (events.js:77:13)
9:00:39 AM radiodan.1 | at Socket.emit (events.js:169:7)
9:00:39 AM radiodan.1 | at Pipe._onclose (net.js:469:12)
9:00:39 AM radiodan.1 | 2016-02-02T09:00:39.417Z - error: [radio-player] Error: …
9:00:39 AM radiodan.1 | at ChildProcess.exithandler (child_process.js:213:12…
9:00:39 AM radiodan.1 | at emitTwo (events.js:87:13)
9:00:39 AM radiodan.1 | at ChildProcess.emit (events.js:172:7)
9:00:39 AM radiodan.1 | at maybeClose (internal/child_process.js:821:16)
9:00:39 AM radiodan.1 | at Socket. (internal/child_process.js:319…
9:00:39 AM radiodan.1 | at emitOne (events.js:77:13)
9:00:39 AM radiodan.1 | at Socket.emit (events.js:169:7)
9:00:39 AM radiodan.1 | at Pipe._onclose (net.js:469:12)
9:00:44 AM app.1 | 2016-02-02T09:00:44.398Z - warn: [command-and-events] pl…
9:00:52 AM app.1 | 2016-02-02T09:00:52.406Z - warn: [command-and-events] pl…
9:01:00 AM app.1 | 2016-02-02T09:01:00.413Z - warn: [command-and-events] pl…
9:01:08 AM app.1 | 2016-02-02T09:01:08.419Z - warn: [command-and-events] pl…
9:01:08 AM app.1 | 2016-02-02T09:01:08.422Z - warn: [command-and-events] un…
9:01:08 AM app.1 | 2016-02-02T09:01:08.431Z - warn: [command-and-events] un…
9:03:43 AM app.1 | 2016-02-02T09:03:43.139Z - warn: [command-and-events] pl…
9:03:51 AM app.1 | 2016-02-02T09:03:51.147Z - warn: [command-and-events] pl…
9:03:59 AM app.1 | 2016-02-02T09:03:59.155Z - warn: [command-and-events] pl…
9:04:07 AM app.1 | 2016-02-02T09:04:07.165Z - warn: [command-and-events] pl…
9:04:07 AM app.1 | 2016-02-02T09:04:07.165Z - warn: [command-and-events] un…
9:04:21 AM app.1 | 2016-02-02T09:04:21.075Z - warn: [command-and-events] un…
9:04:21 AM app.1 | 2016-02-02T09:04:21.098Z - warn: [command-and-events] un…
9:04:22 AM app.1 | 2016-02-02T09:04:22.559Z - warn: [command-and-events] un…
9:04:22 AM app.1 | 2016-02-02T09:04:22.582Z - warn: [command-and-events] un…
9:04:23 AM app.1 | 2016-02-02T09:04:23.233Z - warn: [command-and-events] un…
9:04:23 AM app.1 | 2016-02-02T09:04:23.255Z - warn: [command-and-events] un…
9:04:23 AM app.1 | 2016-02-02T09:04:23.462Z - warn: [command-and-events] un…
9:04:23 AM app.1 | 2016-02-02T09:04:23.482Z - warn: [command-and-events] un…
9:04:43 AM app.1 | 2016-02-02T09:04:43.363Z - warn: [command-and-events] un…
9:04:43 AM app.1 | 2016-02-02T09:04:43.385Z - warn: [command-and-events] un…
9:04:44 AM app.1 | 2016-02-02T09:04:44.519Z - warn: [command-and-events] un…
9:04:44 AM app.1 | 2016-02-02T09:04:44.538Z - warn: [command-and-events] un…
`
The text was updated successfully, but these errors were encountered: