home
products
contribute
download
documentation
forum
Home
Forums
New posts
Search forums
What's new
New posts
All posts
Latest activity
Members
Registered members
Current visitors
Donate
Log in
Register
What's new
Search
Search
Search titles only
By:
New posts
Search forums
Search titles only
By:
Menu
Log in
Register
Navigation
Install the app
Install
More options
Contact us
Close Menu
Forums
General Forums
News and Announcements
MediaPortal 2 progress report
Contact us
RSS
JavaScript is disabled. For a better experience, please enable JavaScript in your browser before proceeding.
You are using an out of date browser. It may not display this or other websites correctly.
You should upgrade or use an
alternative browser
.
Reply to thread
Message
<blockquote data-quote="Albert" data-source="post: 631894" data-attributes="member: 67886"><p>Hi guys and gals,</p><p></p><p>The last progress report for the MediaPortal 2 system was long ago and since then, many things were done.</p><p>And I guess I have to apologize because I didn't write more progress reports although I promised it. I was too much involved in development tasks. But we don't sleep; we're doing heavy development.</p><p>In the mean time, the team has decided to change the name of the project from MediaPortal-II to MediaPortal 2.</p><p></p><p>In the last months, many parts of the system have been developed/revised:</p><p></p><p><strong>UPnP library</strong></p><p>The MediaPortal 2 system uses the UPnP protocol to communicate. Since the only public available UPnP library for .net was the library from Intel and that one was quite old, buggy and not available as source code when we started, we decided to develop our own library. Now, we can proudly present our fully functional, well-designed and stable UPnP library.</p><p>In the meantime, Intel has reworked their library to a new version which also supports the UPnP 1.1 protocol, but our library is still better <img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite1" alt=":)" title="Smile :)" loading="lazy" data-shortname=":)" /></p><p></p><p></p><p><strong>Importer worker</strong></p><p>The importer worker component provides an API to schedule import jobs. Import jobs can run on the client and on the server. Jobs that run at the client are automatically executed when the MediaPortal 2 server is connected and they are automatically suspended when the server connection goes down. The next time when the server connection is established again, suspended client import jobs are continued.</p><p></p><p></p><p><strong>MediaLibrary</strong></p><p>The MediaPortal 2 MediaLibrary provides a flexible database to store all kinds of metadata of media items like information from ID3 tags, video metainformation about movies, TV channels and EPG data, for example. It also stores metadata to all shares which are available in the system.</p><p></p><p>The access to the media library is done on a high-level abstraction layer. We use an abstraction concept called „media item aspects“ throughout the application to flexibly store metadata for videos, music files and other media items.</p><p></p><p></p><p><strong>Database engine</strong></p><p>To store the contents of the media library and other data from plugins, the MediaPortal 2 server provides a database interface where each plugin can install its own subschema. The system automatically tracks database schema scripts, schema updates and uninstallation of subschemas. Furthermore, it is possible to exchange the database engine by another one.</p><p></p><p></p><p><strong>SkinEngine</strong></p><p>Many improvements were done in the SkinEngine. The code was simplified and the DirectX access code was reworked.</p><p></p><p></p><p>This was a small extract of the work amound which was done the last months.</p><p>The development of MediaPortal 2 remains exciting!</p><p></p><p>Cheers,</p><p>Daniel</p></blockquote><p></p>
[QUOTE="Albert, post: 631894, member: 67886"] Hi guys and gals, The last progress report for the MediaPortal 2 system was long ago and since then, many things were done. And I guess I have to apologize because I didn't write more progress reports although I promised it. I was too much involved in development tasks. But we don't sleep; we're doing heavy development. In the mean time, the team has decided to change the name of the project from MediaPortal-II to MediaPortal 2. In the last months, many parts of the system have been developed/revised: [B]UPnP library[/B] The MediaPortal 2 system uses the UPnP protocol to communicate. Since the only public available UPnP library for .net was the library from Intel and that one was quite old, buggy and not available as source code when we started, we decided to develop our own library. Now, we can proudly present our fully functional, well-designed and stable UPnP library. In the meantime, Intel has reworked their library to a new version which also supports the UPnP 1.1 protocol, but our library is still better :-) [B]Importer worker[/B] The importer worker component provides an API to schedule import jobs. Import jobs can run on the client and on the server. Jobs that run at the client are automatically executed when the MediaPortal 2 server is connected and they are automatically suspended when the server connection goes down. The next time when the server connection is established again, suspended client import jobs are continued. [B]MediaLibrary[/B] The MediaPortal 2 MediaLibrary provides a flexible database to store all kinds of metadata of media items like information from ID3 tags, video metainformation about movies, TV channels and EPG data, for example. It also stores metadata to all shares which are available in the system. The access to the media library is done on a high-level abstraction layer. We use an abstraction concept called „media item aspects“ throughout the application to flexibly store metadata for videos, music files and other media items. [B]Database engine[/B] To store the contents of the media library and other data from plugins, the MediaPortal 2 server provides a database interface where each plugin can install its own subschema. The system automatically tracks database schema scripts, schema updates and uninstallation of subschemas. Furthermore, it is possible to exchange the database engine by another one. [B]SkinEngine[/B] Many improvements were done in the SkinEngine. The code was simplified and the DirectX access code was reworked. This was a small extract of the work amound which was done the last months. The development of MediaPortal 2 remains exciting! Cheers, Daniel [/QUOTE]
Insert quotes…
Verification
Post reply
Forums
General Forums
News and Announcements
MediaPortal 2 progress report
Contact us
RSS
Top
Bottom