0236ab8d64
It's a start. It can display several streams at once, which is nice. There are lots of opportunities for improvement: * it doesn't keep the videos approximately in sync. * it accumulates extra buffering, drifting behind live. This is particularly noticeable when it's paused and played again; it can be several seconds before it jumps to after the break. * it always uses the sub stream rather main. I'd prefer it support "auto" (use main if the viewport is larger than the sub stream and there's sufficient bandwidth), "main", or "sub". * it has a kludgy heuristic where it throws away everything buffered 5 seconds before the current timestamp. It should throw away everything before the current GOP instead, but I need to alter the API so it can easily know when that is. * it can't tell you when a camera connection is down. This needs an API change also. * it'd be nice to quickly double-click on a stream to view only it, then double-click again to go back to the multi-pane view. * it doesn't allow you to zoom in on part of the video. This would be nice particularly when viewing 4k video streams on small screens. * it has only four preconfigured layouts that subdivide a 16x9 viewport. You have to choose every camera every time. It'd be nice to both allow more flexibility and have more memory. React prototype: #111 live stream: #59 |
||
---|---|---|
.. | ||
public | ||
src | ||
.gitignore | ||
package-lock.json | ||
package.json | ||
README.md | ||
tsconfig.json |
Getting Started with Create React App
This project was bootstrapped with Create React App.
Available Scripts
In the project directory, you can run:
npm start
Runs the app in the development mode.
Open http://localhost:3000 to view it in the browser.
The page will reload if you make edits.
You will also see any lint errors in the console.
npm test
Launches the test runner in the interactive watch mode.
See the section about running tests for more information.
npm run build
Builds the app for production to the build
folder.
It correctly bundles React in production mode and optimizes the build for the best performance.
The build is minified and the filenames include the hashes.
Your app is ready to be deployed!
See the section about deployment for more information.
npm run eject
Note: this is a one-way operation. Once you eject
, you can’t go back!
If you aren’t satisfied with the build tool and configuration choices, you can eject
at any time. This command will remove the single build dependency from your project.
Instead, it will copy all the configuration files and the transitive dependencies (webpack, Babel, ESLint, etc) right into your project so you have full control over them. All of the commands except eject
will still work, but they will point to the copied scripts so you can tweak them. At this point you’re on your own.
You don’t have to ever use eject
. The curated feature set is suitable for small and middle deployments, and you shouldn’t feel obligated to use this feature. However we understand that this tool wouldn’t be useful if you couldn’t customize it when you are ready for it.
Learn More
You can learn more in the Create React App documentation.
To learn React, check out the React documentation.
Code Splitting
This section has moved here: https://facebook.github.io/create-react-app/docs/code-splitting
Analyzing the Bundle Size
This section has moved here: https://facebook.github.io/create-react-app/docs/analyzing-the-bundle-size
Making a Progressive Web App
This section has moved here: https://facebook.github.io/create-react-app/docs/making-a-progressive-web-app
Advanced Configuration
This section has moved here: https://facebook.github.io/create-react-app/docs/advanced-configuration
Deployment
This section has moved here: https://facebook.github.io/create-react-app/docs/deployment
npm run build
fails to minify
This section has moved here: https://facebook.github.io/create-react-app/docs/troubleshooting#npm-run-build-fails-to-minify