mido22/recordopus

option for recording videos server side using opus packets

recordopus's Issues

Socket.io connection getting aborted in Chrome

While everything works fine in Firefox, in Chrome I get
GET http://mydomain.com:8057/socket.io/?EIO=3&transport=polling&t=1435745877903-0
Aborted
GET http://mydomain.com:8057/socket.io/?EIO=3&trans...polling&t=1435745878278-1&sid=4XV5UPeAy3cmukYGAAAE
Aborted

Any idea what would be a problem?

Saving the .opus file in-browser?

Hey,

This is a really neat project! 👍

I've been playing around a bit with it, and I'm wondering if you have any idea how to save the opus encoded data in the browser, without uploading it to the server. I'm trying to produce a standalone .opus file without uploading, decoding to wav and then re-encoding. My goal is to output the same type of file as opusenc.js, but with streaming input.

Any thoughts?

Thanks!

bug start on server side, log included

0 info it worked if it ends with ok
1 verbose cli [ '/usr/bin/node', '/usr/bin/npm', 'start' ]
2 info using [email protected]
3 info using [email protected]
4 verbose node symlink /usr/bin/node
5 verbose run-script [ 'prestart', 'start', 'poststart' ]
6 info prestart [email protected]
7 info start [email protected]
8 verbose unsafe-perm in lifecycle true
9 info [email protected] Failed to exec start script
10 error [email protected] start: node server/app.js
10 error Exit status 8
11 error Failed at the [email protected] start script.
11 error This is most likely a problem with the recordOpus package,
11 error not with npm itself.
11 error Tell the author that this fails on your system:
11 error node server/app.js
11 error You can get their info via:
11 error npm owner ls recordOpus
11 error There is likely additional logging output above.
12 error System Linux 3.2.0-4-amd64
13 error command "/usr/bin/node" "/usr/bin/npm" "start"
14 error cwd /home/andrey/recordOpus-master
15 error node -v v0.10.38
16 error npm -v 1.4.28
17 error code ELIFECYCLE
18 verbose exit [ 1, true ]

Server emit to all users

When using server in multi user environment all users will receive each other emit events for finished recording.
problem is in

function returnLink(data, filepath){
    data.path = filepath;
    delete data.blob;
    io.emit('link', data);
} 

You are using io instance and it makes global emits, you should propagate each users socket instance and use it.

socket.io error in Chrome

I'm still getting a socket.io error in Chrome 50.0.2661.37 beta (64-bit). I don't see errors in Firefox, but I don't get a recording there either, and no on-screen messages. Do you have any suggestions, or a link to a working demo I could try?

Thank you!

My test is here: https://tokkers.com/recordOpus/client/index.html

No sound recorded

Files are written to file system and have expected length but they contain no sound record. Possible reason is that i had to change http port to 8080 in app.js, i did update socket.io to connect to same port.

Error: Cross-Origin Request Blocked in Firefox

On my local server (win 7, apache 2), it works nicely with Chrome.

In Firefox, I see in firebug in the polling:
Cross-Origin Request Blocked: The Same Origin Policy disallows reading the remote resource at http://file/socket.io/?EIO=3&transport=polling&t=1444902688790-0. (Reason: CORS request failed).

any idea?