search

Robert904 / mumblerecbot

Mumble audio recorder, based on pymumble module
GNU General Public License v3.0
23 stars 10 forks source link

Popping sounds after ~40 minutes #3

Open DavidVentura opened 10 years ago

DavidVentura commented 10 years ago

I'm piping the output to ENCODER = "ffmpeg -loglevel quiet -f s16le -ar 48000 -ac 2 -i - -c:a libmp3lame -ab 96k -ac 1 -ar 44100 -f flv rtmp://localhost:1935//"

After about 40 minutes, the sound starts 'popping', I don't know if you have ever used a badly configured alsa server, but it's just like that. I'll try changing the output -ar to 48k and see if it changes something

DavidVentura commented 10 years ago

can't output at 48k, rtmp doesn't support it

Robert904 commented 10 years ago

I don't remember having this issue. Do you have some constant audio coming on your channel (music or some player with a badly configured voice activation) or is it standard speech with a lot of blanks in the conversations ? Could you try to save it in WAV (perhaps starting another instance in parallel) to see if the issue is the same ?

DavidVentura commented 10 years ago

it's one or two people talking constantly (almost no blanks at all), it's for some online classes and using mumble proved best/easiest so teachers overseas can join the dissertations quickly and the audio keeps working.

I'll test tonight in wav

DavidVentura commented 10 years ago

Running /stop and /start doesn't help, I have to stop the recording process and start it again. Couldn't test a wav. Will test tonight

Robert904 commented 10 years ago

In the mumble protocol, they have a very specific way of encoding sequence numbers, and every 10ms audio packet has a sequence number that is resetted only if there is a +/-10s blank (where mumble stop emitting, lips turn gray)... it could be a bug in my library for large numbers (40min almost continuous sound ~= sequence 240000)... In my use case, I never have such a long continuous emission...

I'll try to check on that. ASAP

DavidVentura commented 10 years ago

At least I can tell you that mumble works OK (I can listen to mumble or to the RTMP stream), but the stream gets broken. Today I'll cut two parts of the audio, a broken one and a working one (The classes are in spanish but you can get the 'broken' audio anyway)

Thanks.

On 19 May 2014 11:43, Robert904 notifications@github.com wrote:

In the mumble protocol, they have a very specific way of encoding sequence numbers, and every 10ms audio packet has a sequence number that is resetted only if there is a +/-10s blank (where mumble stop emitting, lips turn gray)... it could be a bug in my library for large numbers (40min almost continuous sound ~= sequence 240000)... In my use case, I never have such a long continuous emission...

I'll try to check on that. ASAP

— Reply to this email directly or view it on GitHubhttps://github.com/Robert904/mumblerecbot/issues/3#issuecomment-43512739 .

We need only a little more code,and little more money,and little more time, and little more sleep but the world needs a lot more freedom

DavidVentura commented 10 years ago

https://www.youtube.com/watch?v=rf4H459CeaY

check at about 40 minutes the popping sound. it starts at 30-35, and keeps getting worse until i restart the recorder, running /stop and /start does NOT work

Robert904 commented 10 years ago

I'll see what I can find... I did some testing but I was not able to reproduce it...