Reply to thread

Message

<blockquote data-quote="offbyone" data-source="post: 834554" data-attributes="member: 73415">Time for me to say a few things I guess <img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite2" alt=";)" title="Wink&nbsp; &nbsp; ;)" loading="lazy" data-shortname=";)" />a) OnlineVideos is already implemented as API -&gt; we have one dll that can be used by any application, and another one that does all MediaPortal1 related GUI stuff ('and another one for MP2, ... <img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite1" alt=":)" title="Smile&nbsp; &nbsp; :)" loading="lazy" data-shortname=":)" /> )b) In order to get the sites, categories and videos you definitely need to use the API meaning the calls inside the dll, the only things stored in a DB are Favorites.But if you wire the paths right this is not very hard, proven by the fact that we already have 3 front-ends using the API.c) Since you already use vlc or ffmpeg for transcoding, the video types are not a problem, but the access (protocols). I am especially thinking of RTMP here. We now use our own directshow filter for those connections, and I do not know if VLC/ffmpeg supports all rtmp features yet (meaning encrypted streams).I'd be happy to help out with this and make required changes inside OnlineVideos, as long as they won't break current sites.</blockquote>

[QUOTE="offbyone, post: 834554, member: 73415"] Time for me to say a few things I guess ;) a) OnlineVideos is already implemented as API -> we have one dll that can be used by any application, and another one that does all MediaPortal1 related GUI stuff ('and another one for MP2, ... :-) ) b) In order to get the sites, categories and videos you definitely need to use the API meaning the calls inside the dll, the only things stored in a DB are Favorites. But if you wire the paths right this is not very hard, proven by the fact that we already have 3 front-ends using the API. c) Since you already use vlc or ffmpeg for transcoding, the video types are not a problem, but the access (protocols). I am especially thinking of RTMP here. We now use our own directshow filter for those connections, and I do not know if VLC/ffmpeg supports all rtmp features yet (meaning encrypted streams). I'd be happy to help out with this and make required changes inside OnlineVideos, as long as they won't break current sites. [/QUOTE]

Verification