Quoting Ralf Jung (2016-03-26 13:07:43) > Hi, > > > If VLC fails to properly handle the odd URI+space+options ffmpeg syntax, > > then that is a bug in VLC. Please check if that is the case, or (now > > that you know what to look for) it perhaps is instead an issue of you > > needing to feed the "live" option in a different way than you have tried > > already. If VLC ignores the live option or has no way of being told the > > live option, then please open a new bug against vlc, pointing to this > > one for background info. > > That's not what I meant. I meant the following: There are websites > embedding rtmp:// links (e.g. <https://2016.revision-party.net/live>). > Of course, these links do not contain "live=1"; no implementation > besides librtmp needs that. Clicking such a link and opening it in an > ffmpeg-backed application will result in an error on Debian, but nowhere > else (people reported on IRC that the link works fine both on Windows > and on Arch Linux). > > Adding " live=1" works with VLC jut as well as MPV. But that's besides > the point. We cannot expect users to know this, things should Just Work > (TM).
Ok, I think I understand your point now. Makes sense, even though I do not agree with it. If you believe that all consumers of librtmp should by default work in "live" mode then I suggest you file a bugreport against librtmp to request patching it (or convince upstream to change) accordingly. If you believe that - no matter what librtmp does by default - ffmpeg and all its consumers should by default work in "live" mode then I suggest you to file a bugreport against ffmpeg to request patching that. If you believe that - no matter the defaults of librtmp or ffmpeg - VLC should by default work in live mode... etc. Kind regards, - Jonas -- * Jonas Smedegaard - idealist & Internet-arkitekt * Tlf.: +45 40843136 Website: http://dr.jones.dk/ [x] quote me freely [ ] ask before reusing [ ] keep private
signature.asc
Description: signature