Serviio

Hi

When are we going to see the development on the plugins section get up to date? I bought and used serviio originally not just for media located at home but also for web resources. The forum now shows that pretty much all plugins are dead and all of them which were popular have reached a dead end as no developers can use the streams available.

The improvements made to serviio over the last year are good, but for me, it's got to a point where the things that are broken are not being fixed / updated. There are many alternatives to serviio which offer the same current working functionality. I just don't understand why the plugins area isn't one area being looked at when surely it was one of its main selling points.

in order to keep some plugin working, author need constant time for it, he had once that time (and made it) but now not, can you accept it?
time=money (he need for living)

I'm trying to look at those written by me, but otherwise plugins are a community effort, so if someone wants to pick up fixing then, it's obviously encouraged.

Sure, understood. But a look at each thread, most of them have a comment from JHB50 to say that in order to work, they "requires a modified version of librtmp that Serviio's ffmpeg does not include." So what I'm requesting is that this is included so that we can start looking at these plugins. To be honest, I've looked at the guidance and I struggle with writing groovy files.

AFAIK, the updated librtmp might have some code, that is not entirely legal (copyright), so I cannot distribute it.

Fair enough - is the any way we could do this as users without you distributing it? I've had a look and can't see anywhere where it is stated is copyrighted but in addition, software like XBMC are using these files without any issues as far as I can tell.

this below is ffmpeg from fedora 20, is this version capable to receive rtmp://address:port from internet?

It's more the file from here I believe.

http://www.ffmpeg.org/doxygen/trunk/lib ... ource.html

Zip - I've hunted high and low and cannot find anything to back up your claims of it breaching copyright or being illegal in any way. Is this just a route you do not want to look at?

Perhaps it's a different issue. There is a build of librtmp around that has some dodgy code in it, but is not a part of the main librtmp repository. Not sure if this is the case here or it's actually completely different code.

Are you happy to look at including this then?

Theres an unnoffical build thats makes Handshake 10 work but Adobe have deemed it to be not legal and have taken down most download repo/sources with it.
Its been covered here - viewtopic.php?f=22&t=3995&start=40#p44729

The legal source can be found here git://git.ffmpeg.org/rtmpdump

Using a modified version of librtmp will not fix the problem. Most of the webpages providing these streams, fund their stream capture servers with advertising revenue, which they lose when plugins hijack the streams and circumvent the webpages. As a result when they see such activity they make changes to further hide their streams causing the plugins to break again. Many of these changes require further changes to librtmp, or the use of other utilities to determine new algorithms or keys. The plugin maintenance load is never ending so many authors have simply been unable to keep up, or have evolved solutions for their own use that are simply to complex to explain and support for the average Serviio user.

The solution for the average user is to use the wiki method http://wiki.serviio.org/doku.php?id=stream_pc and stream the web page to via Serviio to your TV. That way, you get the stream, they get the revenue, and the plugin author can take a break. Of course you can always put in a bit of effort and learn to write your own plugins, and maintain them each day, for the benefit of all the other users