I had to re-start my New-Telerising API docker yesterday and Netstream stopped working.
Has someone else experienced the same?
Checking the box "Disable ffmpeg -re option" did the trick. I had to manually re-assign each channel in my TVH.
I had to re-start my New-Telerising API docker yesterday and Netstream stopped working.
Has someone else experienced the same?
Checking the box "Disable ffmpeg -re option" did the trick. I had to manually re-assign each channel in my TVH.
I had to re-start my New-Telerising API docker yesterday and Netstream stopped working.
Has someone else experienced the same?
Moin Ihr fleißigen Helfer,
Woran ich hänge ist das automatische Zusammenspiel, der DREI.
D.h. TVHeadend, Telerising-Api sowie NEW-Easyepg.Alle DREI laufen hier bereits im Docker unter OpenMediaVault und funktionieren auch.
Was ich noch nicht hin bekomme, ist; Das Verständnis, wie TVHeadend sich die fertige EPG.XML holt bzw. benutzt, wo sie liegen muss und wie ich das dann am Ende automatisiere.Puhh, was braucht Ihr von mir?
Sorry. I have to answer in English. I've just registered in order to answer to your question that, if I understood correctly, you want to know how to import the generated .XML into TVHeadend.
My setup is all three (TVHeadend, Telerising-Api and NEW-Easyepg) running in Docker containers similarly to you but in an UnRAID server (thank you @DeBaschdi for your amazing work!)
For me the easiest way is to "cat" the .XML and pipe it via "socat" to the XMLTV socket. In my case I run twice a day a full script that updates the .XML via NEW-EasyEPG, downloads some Rytec EPGs and update all of them to TVHeadend. The command I use is like this: (Change the paths accordingly and make sure socat is installed in your server)