RTMP support removed
#1
The latest nightlies have removed support for RTMP, because this is available via the inputstream.rtmp addon, however this addon is not included in the default addons. Nor is it buildable via the inputstream.rtmp git repository (at least on windows). How can I provide support for RTMP streams within Kodi?
Reply
#2
I am curious if inputstream.rtmp for windows is available in any form yet - been doing testing with nightly builds and we should be seeing 17 alpha 3 snapshot here soon

thanks for info/update
Reply
#3
I am also interested in knowing the status of rtmp on windows. On Linux it is included by default and works great.
HTPC Server - Windows 8.1 + XBMC Helix | Intel QuadCore, 4GB RAM, 4 TB SATA
Intel NUC D54250WYK - Windows 8.1 + XBMC Helix | Logitech Harmony 750
Samsung UE8005 | Bluetooth keyboard & mousepad
Reply
#4
The information I have is that Windows uses ffmpeg for rtmp support as provided by https://github.com/xbmc/xbmc/pull/10015 since inputstream.rtmp only works for osx/linux.

From what I hear ffmpeg is not as capable on some streams but should be ok for the vast majorit,y hence why it was thought to be an acceptable fallback for those platforms that don't use inputstream.rtmp so you could just be unlucky in using streams ffmpeg doesn't like. However there was a fix to the ffmpeg rtmp support that was pushed about a week ago so please test a again, if you still have problems then a debug log will be needed.
Reply
#5
Sorry for hijacking this thread but I have problems with rtmp streams in Kodi 17. My wife uses an addon which streams files from the official website of a local tv station using a rtmp protocol. It works with no problems on Linux but doesn't work on Windows.
This badly influences my wife acceptance factor. Smile Is there anything we can do to make it work or are we out of luck?
Thank you very much for any info.

http://pastebin.com/RqHWjY70
Reply
#6
(2016-08-17, 18:20)jjd-uk Wrote: The information I have is that Windows uses ffmpeg for rtmp support as provided by https://github.com/xbmc/xbmc/pull/10015 since inputstream.rtmp only works for osx/linux.

From what I hear ffmpeg is not as capable on some streams but should be ok for the vast majorit,y hence why it was thought to be an acceptable fallback for those platforms that don't use inputstream.rtmp so you could just be unlucky in using streams ffmpeg doesn't like. However there was a fix to the ffmpeg rtmp support that was pushed about a week ago so please test a again, if you still have problems then a debug log will be needed.

is inputstream.rtmp for windows coming? or will Windows users just be SOL when they happen upon one of non "vast majority" that used to work but now does not?

What I am seeing is Authentication errors and App rejection from the server side due to various things like handshake, no matching rules

Funny enough for a laugh I decided to test some "banned" addons to see how they fared - not good - most fail at this point but if I set up an external player and pass to ffplay - the stream comes up just fine.

So I am curious - how ffmpeg that kodi is using is less capable then the ffmpeg 3.0.1 for windows using ffplay?

personally - i would just love to have windows be on par with linux,etc with support for rtmp, etc.

thanks folks for the hard work and I understand its a beta and WIP :-)

M
Reply
#7
(2016-08-24, 09:47)mgonzales Wrote: is inputstream.rtmp for windows coming? or will Windows users just be SOL when they happen upon one of non "vast majority" that used to work but now does not?
I'm not sure if it's on the agenda to get inputstream.rtmp working for Windows, I'm guessing for v17 it's been simply lack of time from the Windows dev's so I'll see if I can get someone to comment.
(2016-08-24, 09:47)mgonzales Wrote: So I am curious - how ffmpeg that kodi is using is less capable then the ffmpeg 3.0.1 for windows using ffplay?

When I said ffmpeg was less capable I meant in comparison to librtmp, there should be no difference in capability between how Kodi uses ffmpeg (which is 3.1.2 currently I believe) and ffmpeg using ffplay, if there is a difference then this is definitely something that needs to be fixed.

So if you have legal examples of freely available streams (not geo-locked) that a dev can use then please file a trac ticket using the bugtracker link at top of forum and include the following:
  • A explantion of the problem
  • A link to a stream or streams that don't work
  • A debug log_file (wiki)
  • How you tested using ffplay

Make sure you have tested with the current Nightly version of Kodi from http://mirrors.kodi.tv/nightlies/win32/ as I see there was an additional rtmp fix 5 days ago and there may have been other fixes since then.
Reply
#8
What are the ffmpeg rtmp flags incomparison to rtmpdump for use with
this new inputstream impletmentation?

https://rtmpdump.mplayerhq.hu/rtmpdump.1.html

Even Jarvis didn't seem to fully understand them with librtmp, links that did work
always showed the last part of the url in favourites / bookmarks where as more complex ones
that didn't showed the last parts of pageURL and playpath.

Example

rtmp://blah.blah.co:1935/blah/blah app=bla/ swfUrl=https://blah/swf/player.swf pageURL=https://www.blahv/blah playpath=blah

would just play rtmp://blah.blah.co:1935/blah/blah regardless as if you only entered that as a url,
ignoring all the set flags.
It also seemed to being seeing the user agent as a mobile browser instead of desktop
browser which causes links not work properly on Kodi for Android.
Reply
#9
Hi,
Final version is out and still no inputstream.rtmp for windows :\
legit addons doesnt work and unfortunatelly this makes me stay on 16.1.

are you planning to release some kind of a solution for windows users?
Reply

Logout Mark Read Team Forum Stats Members Help
RTMP support removed0