Reply to thread

Message

<blockquote data-quote="tourettes" data-source="post: 416221" data-attributes="member: 10858">Seems that XBMC guys have something against me <img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite7" alt=":p" title="Stick Out Tongue&nbsp; &nbsp; :p" loading="lazy" data-shortname=":p" /> Idea is pretty nice one, but &quot;Direct tie in to XBMC's SQLite database&quot; sounds like a artificial limitation to me, or is it the business idea behind the application? i.e. to allow other applications to benefit as good features as XBMC is able to benefit.For example Meedio &amp; MeediOS have really customizable media library (with custom tags etc.), how would the Unified Media Manager work on such situation where user wants to add what ever extra metadata to the media items? Would using XBMC's limitations block this? If yes then it would be much more beneficial to other open source projects if Unified Media Manager's database wouldn't use XBMC style database, but much more flexible approach (maybe even borrow the code directly from MeediOS project, after all it is open source <img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite1" alt=":)" title="Smile&nbsp; &nbsp; :)" loading="lazy" data-shortname=":)" />) and then write adapters to push the data to MediaPortal, MeediOS, Meedio &amp; XBMC direction. Those adapters would then take care of the &quot;target platform&quot; limitations in media handling.As we all know, Meedio / MeediOS is miles ahead in the Media Library side (but lacking on many other aspects <img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite7" alt=":p" title="Stick Out Tongue&nbsp; &nbsp; :p" loading="lazy" data-shortname=":p" />) when it comes to XBMC (or even MediaPortal). MPII will close the Media Library gap between Meedio / MeediOS and MediaPortal so that's why I'm really interested in the limitations that XBMC's media management might bring to such project.</blockquote>

[QUOTE="tourettes, post: 416221, member: 10858"] Seems that XBMC guys have something against me :P Idea is pretty nice one, but "Direct tie in to XBMC's SQLite database" sounds like a artificial limitation to me, or is it the business idea behind the application? i.e. to allow other applications to benefit as good features as XBMC is able to benefit. For example Meedio & MeediOS have really customizable media library (with custom tags etc.), how would the Unified Media Manager work on such situation where user wants to add what ever extra metadata to the media items? Would using XBMC's limitations block this? If yes then it would be much more beneficial to other open source projects if Unified Media Manager's database wouldn't use XBMC style database, but much more flexible approach (maybe even borrow the code directly from MeediOS project, after all it is open source :)) and then write adapters to push the data to MediaPortal, MeediOS, Meedio & XBMC direction. Those adapters would then take care of the "target platform" limitations in media handling. As we all know, Meedio / MeediOS is miles ahead in the Media Library side (but lacking on many other aspects :P) when it comes to XBMC (or even MediaPortal). MPII will close the Media Library gap between Meedio / MeediOS and MediaPortal so that's why I'm really interested in the limitations that XBMC's media management might bring to such project. [/QUOTE]

Verification