[ZeChico]

Originally Posted by homah

I've pretty much gone with the github one, but thanks to your one I've made it so I can see who is being recorded without going on the web client (can't say I'm a fan of the web client, I'd rather surf mfc and make any changes directly to the config). Also used your timestamp layout, just seems easier to read, as well as changing it from blue to yellow (dark blue on black, ewww)

Any idea whats with this code though

        '-c',
        'copy',
        '-vsync',
        '2',
        '-r',
        '60',
        '-b:v',
        '500k',

Seems to me it's trying to make the fps 60 and reduce the bitrate? bizarre. Doesn't seem to happen on the recordings anyway.

Maybe they found that with those ffmpeg parameters it could be more stable or something, don't know, my old main.js just have:
'-c',
'copy',

and seems to record fine.

EDIT: "-c copy" forces to copy the stream without re encode, it should ignore "-b:v 500k"

I know that MFC uses 2 streams when models are streaming at 640x480 or higher, one the original the other a low quality 320x240.

This change can be seem on a mobile device that supports multi bandwidth stream. This can be seem many times when you start loading a high quality stream and then a low quality kicks in and it can jump from one to other... Very infuriating actually that most mobile browser doesn't give you the option to force a high quality bitrate.