Replies: 6 comments 49 replies
-
Pi 3 is barely powerful enough to send streams from one Pro HD. Per Gerry, Pro HD requires extra processing. |
Beta Was this translation helpful? Give feedback.
-
For those who wants the easier way .I was able do the same thing by installing mx player pro on echo show 15 and streaming from slinger(side loading the apk). I followed youtube video (How to sideload apps on echo show 15). |
Beta Was this translation helpful? Give feedback.
-
Another (almost) pleasant news to finish ...for those who might be interested. I have now bought a ThinClient "HP t620" (AMD G-Series GX-415GA SOC: Quad-Core APU 1.5 GHz) for 30 euros on eBay after the tip from @Toei79. It runs quietly without a fan and has a just acceptable energy consumption of about 11 watts. Installed a Debian Linux distribution (openmediavault, because I want to use the device in parallel as a NAS). I have taken down the RTSP server together with the FFMPEG transcoding from Pi in the architecture described at the beginning and installed it on the "HP t620". As a result, I can now stream (but only one stream) "stutter-free" via the RTSP server with transcoding. The CPU load is 50..80 %. A second stream with transcoding is not possible...for that it needs even more computing power. I will "play" a bit with the video bitrate. Maybe then two streams with transcoding are possible in parallel. |
Beta Was this translation helpful? Give feedback.
-
Hello @lehmbarsingh, ... stream6: all: A few more notes:
I hope it helped and wish you good luck. In the preview, the indentations disappear. Therefore I attach the code snippet here: |
Beta Was this translation helpful? Give feedback.
-
Who can help? As I wrote before I bought a "HP t620" (AMD G-Series GX-415GA SOC: Quad-Core APU 1.5 GHz) and installed openmediavault (OMV, openmediavault.org) as NAS operating system based on Debian. I also installed slinger and the RTSP server to connect to the Echo Show 15. Now the problem. When I install Flask because of the remote control function, suddenly configuration changes and SW installations using apt/apt-get no longer works. It throws an error message ""ImportError: cannot import name 'Markup' from 'jinja2′". This is due to an incompatibility between Flask and Jinja2. There is an extensive discussion about this in the relevant forums on the Internet. However, I did not manage to fix the error. To make the NAS function(s) of OMV work completely, the only possibility was to uninstall Flask again. |
Beta Was this translation helpful? Give feedback.
-
Hello@RocketAlf , Seems like I am missing on something because I haven't been able to get it working .I followed all your steps or directions .I have disabled all protocols you mentioned not being used ( rtmpDisable, hlsDisable, webrtcDisable to "yes" ) .I have installed ffmpeg properly . I have created bat files to run the server automatically .so 1st I run the server then I open ffmpeg . now if I try opening the stream6 using vlc (rtsp://127.0.0.1:8554/stream6) it should start streaming but it never happens. Can you share your config file at [email protected] .Also if you can give me step by step how to run this properly would be appreciated .when I give the command in ffmpeg (ffmpeg -loglevel quiet -i http://192.168.1.233:64642/mytv/slingm1med -vcodec libx264 -f rtsp -rtsp_transport tcp rtsp://localhost:8554/stream6) manually it connects to my slinger but after few seconds it cuts off. If I understand correctly when anyone whether echo show 15 or vlc player try to connect to stream6 it suppose to start basically start converting hls stream to rtsp . Thanks |
Beta Was this translation helpful? Give feedback.
-
I have an application here that may be of interest to others.
I run several Amazon Echo devices (Echo Show 1st Gen and Echo Show 15). I have long been looking for a way to display the Slingbox output on the Echo Show. Now I have found a solution ...monoclecam.com. The service is still in beta and therefore (still) free. The service is actually used to display local IP cameras with RTSP interface on Echo Show devices. The Slingbox is then a kind of "camera".
On the Echo side, this requires the smart home skill "Monocle RTSP/RTP IP cameras".
The cameras can then be set up on the monoclecam.com website. There is good documentation on how to proceed with the setup.
Additional SW components are required for the setup.
Via the "monocle-gatway" the local IP address of the stream source (IP camera) is passed to Echo Show, which then establishes the connection to the stream source.
Unfortunately, there seems to be so much "freedom" in the implementation of the RTSP protocol, and Echo Show only accepts a very specific protocol variant. Therefore, direct connection with the IP camera is often not possible and certainly not with the Slinger server. Additional SW components are needed. I have had success with the "rtsp-simple-server" (https://github.com/aler9/rtsp-simple-server). Echo Show, even the newer Echo Show 15, accept the interface provided by this RTSP server.
According to the configuration rules of the server, all stream sources can then be configured as input. On the output side, the IP address of the RTSP server and the respective stream name are set as source on monoclecam.com.
But there is still a "small problem". Slinger does not deliver an RTSP stream. Therefore the HTTP stream from Slinger has to be converted into a RTSP stream. For this I use FFMPEG. In my case the corresponding entry in the configuration file of the RTSP server looks like this:
paths:
stream6:
source: publisher
runOnDemand: ffmpeg -loglevel quiet -i http://192.168.2.252:9090/Slingbox/M1tv -vcodec libx264 -f rtsp -rtsp_transport tcp rtsp://localhost:8554/stream6
runOnDemandStartTimeout: 20s
runOnDemandCloseAfter: 10s
#runOnDemandRestart: yes
Note: The stream names (in the example "stream6") in the should always be chosen the same.
On monoclecam.com the following was entered:
Name: Slingbox TV
Stream Url: rtsp://192.168.2.140:8554/stream6
Video Codec: H264
Audio Codec: AAC
Video Resolution640*480
Tags: @tunnel
The command "Alexa, show Slingbox TV" will then display the stream of the Slingbox "M1tv" on the screen of the Echo Show. The Slingbox "M1tv" is connected to a TV that cannot be controlled by the Slingbox remote. This is not a big deal for me, because I just want to have the same TV program available in several rooms at the same time (living room, kitchen, winter garden, ...).
This works very well when the RTSP server (along with the FFMPEG conversion) is running on my Windows PC. But when the RTSP server is running on a Raspberry Pi, there are constant interruptions for "loading" :-(. I have tried different variations of the settings, but without success. The Raspi seems to be not powerful enough for this task. I have tested Raspberry 2 and 3.
Maybe one or the other already had this idea and got similar results (?).
Because of the performance problem with the Raspi the question @gerry: Could Slinger also provide an RTSP interface?
@ALL the question: Do you have experiences to bring the Slingbox to the Echo Show? Maybe also with completely different approaches (?).
I am grateful for any hint and help to make my project a success :-).
Translated with www.DeepL.com/Translator (free version) :-o
Beta Was this translation helpful? Give feedback.
All reactions