kevingodell / mse-live-player

Testing ground for various video streaming techniques.

mse-live-player

install files with git

git clone https://github.com/kevinGodell/mse-live-player.git

move into directory

cd mse-live-player

install node module dependencies

npm install

start the example server

npm start

open compatible browser to localhost:3000

mse-live-player's Issues

Action required: Greenkeeper could not be activated 🚨

🚨 You need to enable Continuous Integration on all branches of this repository. 🚨

To enable Greenkeeper, you need to make sure that a commit status is reported on all branches. This is required by Greenkeeper because it uses your CI build statuses to figure out when to notify you about breaking changes.

Since we didn’t receive a CI status on the greenkeeper/initial branch, it’s possible that you don’t have CI set up yet. We recommend using Travis CI, but Greenkeeper will work with every other CI service as well.

If you have already set up a CI for this repository, you might need to check how it’s configured. Make sure it is set to run on all new branches. If you don’t want it to run on absolutely every branch, you can whitelist branches starting with greenkeeper/.

Once you have installed and configured CI on this repository correctly, you’ll need to re-trigger Greenkeeper’s initial pull request. To do this, please delete the greenkeeper/initial branch in this repository, and then remove and re-add this repository to the Greenkeeper App’s white list on Github. You'll find this list on your repo or organization’s settings page, under Installed GitHub Apps.

How can reduce live video latency?

Not working on mobile

It works perfect on desktop, but not working on mobile.
Any advice?

添加更多的介绍

Broken on windows?

Hi,
first of all; great work!
I am trying out your application on two different systems, macOS and Windows 10. From my mac I am able to stream the image from my display to both the Windows and mac client, but from the Windows machine I have had less luck. I have tried the ffmepg command used on its own and it spits out data just fine. My theory is that something in the forking of a new process is broken in windows maybe? I am running it in cmd, which should be no problem as both node and ffmpeg runs on their own.

My ffmpeg command (mac):
ffmpeg -f avfoundation -probesize 32 -analyzeduration 10000 -i 1 -an -r 30 -c:v libx264 -f mp4 -g 5 -keyint_min 1 -pix_fmt yuv420p -profile:v baseline -level 3 -movflags +frag_keyframe+empty_moov+default_base_moof+omit_tfhd_offset -metadata title="ip 192.168.1.4" -reset_timestamps 1 pipe:1

Windows runs the same command, but the dshow filter is used instead and with my input set to my capture card (worked with ffmepg before).

Besides the different ffmepg commands I can't figure out that anything else is different, even tried turning off the Windows firewall..

Video won't play immediately on Internet Explorer.

Hi I really appreciate you sharing this project.

I was having a lot of trouble trying to stream a rtsp input to HTML and this project helped a lot.

One problem I found was that when I try to stream to Internet Explorer, the video won't play right away. The time on the controls would keep ticking but the video is all blank.

I have to wait about 1~5 minutes until the video feed shows up. The video however is not in sync with the others and it is delayed by the amount I had to wait.

Is it an I.E thing that I has to buffer that much before it plays? or would there be a fix for it?

I haven't changed much of your code except the compare.js's database and the app.get part.

Also I am trying to not use the media source extensions but only playing with mp4 and m3u8.

Thanks in advance!

Error: mdatLength less than chunkLength in sometime

Hi, your sharing is very valuable.
I got some issue when I try to test 3 external rtsp stream for a couple minutes, nodeJs service was stopped in sometime.
The error message and log are below.
Thank you in advance for any help.

E:\Sources\Testing\mseLivePlayer\node_modules\mp4frag\index.js:438
                throw new Error('mdatLength less than chunkLength');
                ^

Error: mdatLength less than chunkLength
    at Mp4Frag._findMdat (E:\Sources\Testing\mseLivePlayer\node_modules\mp4frag\index.js:438:23)
    at Mp4Frag._findMoof (E:\Sources\Testing\mseLivePlayer\node_modules\mp4frag\index.js:333:18)
    at Mp4Frag._transform (E:\Sources\Testing\mseLivePlayer\node_modules\mp4frag\index.js:448:14)
    at Mp4Frag.Transform._read (_stream_transform.js:186:10)
    at Mp4Frag.Transform._write (_stream_transform.js:174:12)
    at doWrite (_stream_writable.js:387:12)
    at writeOrBuffer (_stream_writable.js:373:5)
    at Mp4Frag.Writable.write (_stream_writable.js:290:11)
    at Socket.ondata (_stream_readable.js:639:20)
    at emitOne (events.js:116:13)
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! [email protected] start: `node compare.js`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the [email protected] start script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

npm ERR! A complete log of this run can be found in:
npm ERR!     C:\Users\User\AppData\Roaming\npm-cache\_logs\2018-01-16T05_53_22_622Z-debug.log

2018-01-16T05_53_22_622Z-debug.log

0 info it worked if it ends with ok
1 verbose cli [ 'C:\\Program Files\\nodejs\\node.exe',
1 verbose cli   'C:\\Program Files\\nodejs\\node_modules\\npm\\bin\\npm-cli.js',
1 verbose cli   'start' ]
2 info using [email protected]
3 info using [email protected]
4 verbose run-script [ 'prestart', 'start', 'poststart' ]
5 info lifecycle [email protected]~prestart: [email protected]
6 info lifecycle [email protected]~start: [email protected]
7 verbose lifecycle [email protected]~start: unsafe-perm in lifecycle true
8 verbose lifecycle [email protected]~start: PATH: C:\Program Files\nodejs\node_modules\npm\bin\node-gyp-bin;E:\Sources\Testing\mseLivePlayer\node_modules\.bin;C:\Program Files\Microsoft MPI\Bin\;C:\ProgramData\Oracle\Java\javapath;C:\Program Files (x86)\Intel\iCLS Client\;C:\Program Files\Intel\iCLS Client\;C:\windows\system32;C:\windows;C:\windows\System32\Wbem;C:\windows\System32\WindowsPowerShell\v1.0\;C:\Program Files (x86)\NVIDIA Corporation\PhysX\Common;C:\Program Files (x86)\Intel\Intel(R) Management Engine Components\DAL;C:\Program Files\Intel\Intel(R) Management Engine Components\DAL;C:\Program Files (x86)\Intel\Intel(R) Management Engine Components\IPT;C:\Program Files\Intel\Intel(R) Management Engine Components\IPT;C:\Users\User\.dnx\bin;C:\Program Files\Microsoft DNX\Dnvm\;C:\Program Files\Intel\WiFi\bin\;C:\Program Files\Common Files\Intel\WirelessCommon\;C:\Program Files\nodejs\;C:\Program Files\Git\cmd;C:\Users\User\AppData\Local\Programs\Python\Python36\Scripts\;C:\Users\User\AppData\Local\Programs\Python\Python36\;C:\Program Files\Microsoft VS Code\bin;C:\Users\User\AppData\Roaming\npm;C:\Program Files\Docker Toolbox;E:\3)Installers\ffmpeg\bin;
9 verbose lifecycle [email protected]~start: CWD: E:\Sources\Testing\mseLivePlayer
10 silly lifecycle [email protected]~start: Args: [ '/d /s /c', 'node compare.js' ]
11 silly lifecycle [email protected]~start: Returned: code: 1  signal: null
12 info lifecycle [email protected]~start: Failed to exec start script
13 verbose stack Error: [email protected] start: `node compare.js`
13 verbose stack Exit status 1
13 verbose stack     at EventEmitter.<anonymous> (C:\Program Files\nodejs\node_modules\npm\node_modules\npm-lifecycle\index.js:280:16)
13 verbose stack     at emitTwo (events.js:126:13)
13 verbose stack     at EventEmitter.emit (events.js:214:7)
13 verbose stack     at ChildProcess.<anonymous> (C:\Program Files\nodejs\node_modules\npm\node_modules\npm-lifecycle\lib\spawn.js:55:14)
13 verbose stack     at emitTwo (events.js:126:13)
13 verbose stack     at ChildProcess.emit (events.js:214:7)
13 verbose stack     at maybeClose (internal/child_process.js:925:16)
13 verbose stack     at Process.ChildProcess._handle.onexit (internal/child_process.js:209:5)
14 verbose pkgid [email protected]
15 verbose cwd E:\Sources\Testing\mseLivePlayer
16 verbose Windows_NT 10.0.15063
17 verbose argv "C:\\Program Files\\nodejs\\node.exe" "C:\\Program Files\\nodejs\\node_modules\\npm\\bin\\npm-cli.js" "start"
18 verbose node v8.9.3
19 verbose npm  v5.5.1
20 error code ELIFECYCLE
21 error errno 1
22 error [email protected] start: `node compare.js`
22 error Exit status 1
23 error Failed at the [email protected] start script.
23 error This is probably not a problem with npm. There is likely additional logging output above.
24 verbose exit [ 1, true ]