hope this is the right category to post this.
Would it be possible to forward a video feed that we have viewing over the mesh network from a tower site 15 miles away to the internet where the nation weather service and the emergency manager can log into over the internet? I am being to it can but its not simple since they are on 2 different IP networks.
Would it be possible to forward a video feed that we have viewing over the mesh network from a tower site 15 miles away to the internet where the nation weather service and the emergency manager can log into over the internet? I am being to it can but its not simple since they are on 2 different IP networks.
Bob W8ERD
I setup a mesh with Ubiquity Bullet 5HP consisting of 7 nodes. One of the nodes is located up a hill where my radio club has also a DVB-T ATV repeater.
I would like to stream the live DVB-T signal over the mesh. To this purpose I prepared a TV server with a DVB-T Tuner, Rpi and tvheadend app, a GPU transcoder from MPEG2 to h264 . All is going well locally and can watch the TV in a PC connected to the lan of the node where also the server tv is attached. The protocol used to stream down the mesh is http and the bandwith on the WiFi has been set to 10 MHz . When I access to the server tv from a remote station over the mesh the video is freezing and interrupts.
Which is the cause and how to work it around?
Tnx for help and regards.
Hello, tnx for prompt reply.
Here below the caracteristics of my transcoder:
Source video codec: MPEG2VIDEO
Codec video: h264_omx: OpenMAX IL H.264 video encoder
Bitrate video: 1200Kb/s
Codec audio: aac: AAC (Advanced Audio Coding)
Bitrate audio: 128Kb/s
if usefull this is my mesh
I3RKE-1 mesh status
Quit
I am operating from italy holding also the callsign: I3RKE
In a well designed mesh with links separated on different channels, the latency can be very and be consistent <20ms over many hops and 100miles+. With lots of channel sharing, the latency can vary between 20ms and over 1 sec -- high range. voip and video streams drop out and can get to the point of being unusable.
All the other nodes pass through the nodes on the hill. I understand that this isn't ideal but at the moment this is the only way to connect the nodes.
I3RKE-1 mesh status
Quit
We've had to set this up to stream video of recent brushfires from hilltop webcams to a YouTube channel for viewing by the public and some public safety agencies. One example is here.
In order to stream successfully we had to set each camera resolution to 720p, and frame rate down to about 10 frames per second. A standard 1920 x 1080 x 30 fps video stream is about 4.2 Megabits/second. By making the adjustments above the video stream can be held to 600-800 kbps.
To stream those streams out to YouTube, we followed this instructional page: http://www.georgetimmermans.com/blog/streaming-rtsp-to-youtube-live It took some research and loading of software, but it works very well.
Since each camera has a different RTSP URL, I've copied all of them into a text file and can copy and paste them to stream any of our cameras at a moment's notice.
Good luck!
73
Orv W6BI
May be K5DLQ or AE6XE can suggest some solutions !
73 de Leo I3RKE / AC2OG
Orv W6BI
ffmpeg -i input.avi -r 10 output.avi
got the message:
tvserver:~ # input.avi: No such file or directory
help in using ffmpeg tools.needed.
Orv W6BI
ffmpeg -i rtsp://@k5dlq-dv-stream-device:62159 ........ (other options)
ffmpeg -i rtsp://10.133.133.254:9981/dev/dvb/DVB-T #0 -r 10 rtsp://10.133.
133.254:9981/dev/dvb/DVB-T #0
and got this message:
rtsp://10.133.133.254:9981/dev/dvb/DVB-T: Server returned 400 Bad Request
If not, your URL will have to be something like this:
rtsp://10.133.133.254:9981//user=<a user name you set up>_password=<password for that user_channel=0_stream=dev/dvb/DVB-T:
iSpy has a great listing of cameras and the URLs they present via RTSP. Try looking there for your camera: https://www.ispyconnect.com/sources.aspx
I'm trying to stream down the mesh a DVB-T signal from a tuner (Sony CX2880) installed on the Rpi where a tvheadend app (TV server) is running.
tvheadend is viewing the tuner as : adapter # 0 or DVB-T #0.
It seems to me that the TVserver is not refusing the connection (as if username and password were missing), but is asking for a different request. Anyway I'll try also the script as you suggested.
So, it sounds like the tuner is sending to an application called tvheadend on the pi. It sounds like you need to determine if tvheadend can OUTPUT an RTSP or HTTP stream with downconversion settings to limit the size/framerate of the OUTPUT stream (so no ffmpeg needed).
Sorry. Not familiar with tvheadend.
you understood well! Tvheadend is a TV webserver application. Just now I discovered that there is an add on of tvheadend that allow to transcode the DVB-T (mpeg2 coded) stream to one coded h264 using the GPU of the Rpi. The output stream is HTTP ; the add on allow to configure a profile of the stream with lowered down speed to 500Kb/s for the video component and 32Kb/s for the audio. In this way the stream is passing well from the node where the TV server is connected to a PC connected to the LAN of an neighbor node. Unfortunately not to a remote node where it is freezed and interrupted. Too big latency?
I would like to understand if this is a limit of the mesh or of the way I am streaming .