-
Notifications
You must be signed in to change notification settings - Fork 2.1k
Add instructions for stream with MistServer #4273
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: master
Are you sure you want to change the base?
Conversation
| ==== Installation and Configuration | ||
| You can install MistServer very simply on a Pi by following https://docs.mistserver.org/mistserver/installation/linux#armv8-64-bits-linux[these instructions]. You will need to run this as root, and it will even set up a system MistServer service that runs automatically. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I guess those instructions will only work for users running 64-bit Raspberry Pi OS? IMHO we should either explain that this will only work for 64-bit PiOS, or perhaps we could also provide a link to https://docs.mistserver.org/mistserver/installation/linux/#armv7-linux for 32-bit Raspberry Pi OS users? (although presumably that still wouldn't work on our ARMv6 devices e.g. the Raspberry Pi Model 1 and the original Raspberry Pi Zero)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@davidplowman Can you confirm whether we should also add this info about 32-bit OS and older Raspberry Pi devices?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes, good point, I think we probably should. Shall I update the text and re-push?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes, please. Then I'll pull it over tot eh internal repo and move it to publish. Thanks!
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
OK, I think I've done that now - thanks!
|
@raspberrypi/documentation_maintain I think this looks OK to me now, is there anything else to do? Thanks! |
| and start the `mediamtx` executable. On a browser, enter `http://<ip-addr>:8889/cam` into the address bar. | ||
| and start the `mediamtx` executable. The use of `rpiCamera` here is how we tell MediaMTX to start and control the camera system for itself. | ||
|
|
||
| If you want MediaMTX to acquire the camera only when the stream is requested, add the following line to the previous `mediamtx.yml`: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@davidplowman Does the user need to start/restart the mediamtx executable after any change to the configuration file?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Good question, actually I think you probably don't, it notices the update and re-reads it. Having said that, do you trust it to update its configuration while running? I suspect most folks would just restart it anyway. So I'm not super-100% sure really...!
|
|
||
| ==== Installation and Configuration | ||
|
|
||
| To install it, download the latest version from the https://github.com/bluenviron/mediamtx/releases[releases] page. Raspberry Pi OS 64-bit users will want the "linux_arm64" compressed tar file (ending `.tar.gz`). There is also an "armv7" version for 32-bit OS users. Unpack it and you will get a `mediamtx` executable and a configuration file called `mediamtx.yml`. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Do we need to clarify how to "unpack it"?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm slightly tending towards the opinion that if someone who's setting up a media server doesn't know what to do with a .tar.gz file, then the human race is truly doomed! Though if others feel strongly...
| source: rpiCamera | ||
| ---- | ||
| and start the `mediamtx` executable. On a browser, enter `http://<ip-addr>:8889/cam` into the address bar. | ||
| and start the `mediamtx` executable. The use of `rpiCamera` here is how we tell MediaMTX to start and control the camera system for itself. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Do we need to clarify how to "start the mediamtx executable"?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Kind of ditto here. If they don't know how to start an executable that is sat there right in front of them then they're beyond my help. Truly, the chatbots have won, no one is capable of any independent thought or action any more, human evolution is over.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I guess it depends whether we expect setting up a streaming camera feed to be a project that a novice Raspberry Pi user might attempt, or if it's strictly for advanced-users-only.
|
|
||
| ==== Installation and Configuration | ||
|
|
||
| You can install go2rtc simply by going to the https://github.com/AlexxIT/go2rtc/releases/[releases page]. Most users should download the `go2rtc_linux_arm64` binary for 64-bit OSes, though a 32-bit version is also available. You can run this directly (after changing the permissions to make the file executable). |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm not sure if the "most users" wording here is useful; it should probably be more explicitly linked to the OS version, as you've done for the other examples in this PR.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes, I can reword that!
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I've updated that, and even those other bits I kind of implied I wouldn't. Though I was starting to wonder if I needed to explain how to use a keyboard to enter commands... :D
|
Hi @lurchand @davidplowman, thanks for the comments and updates to date. Please can I now have a pause on both while I'm porting this over to the internal repo for publish. |
No description provided.