Reply to thread

Message

<blockquote data-quote="Albert" data-source="post: 580553" data-attributes="member: 67886">AW: MP-II development progressWell, we're taking a slightly different approach than the standard UPnP AV media server solution.The standard UPnP AV media server uses the UPnP protocol for the discovery of devices (so the client is able to find the server in the network without the need to configure hostname/port etc.) The &quot;AV&quot; part is basically a specification, how the interface looks like. If this standard type is implemented, this device can be used by each UPnP AV client with a defined semantics of all methods.Typically, implementors of UPnP AV write the AV server in a way that it is able to comply with the service specification(s) of the UPnP AV system, i.e. their data store and internal data structures follow the data structures defined by the UPnP AV specification.In our solution, the UPnP AV interface is not the basis of our development; we have our own interface which is used for the MP2 client-server communication. Thus, we also have own (much more flexible) data structures and own access techniques. And yes, our own system off course supports lossless media types. And that's not all; the system is easily extendible by additional plugins providing the ability to import more media types (we call it MetadataExtractors).The UPnP AV interface will be implemented in a later stage and it will be based on our own data structures. We will support as many of the optional parts of UPnP AV as we need to provide our flexibility to the UPnP AV world.Cheers,Daniel</blockquote>

[QUOTE="Albert, post: 580553, member: 67886"] [b]AW: MP-II development progress[/b] Well, we're taking a slightly different approach than the standard UPnP AV media server solution. The standard UPnP AV media server uses the UPnP protocol for the discovery of devices (so the client is able to find the server in the network without the need to configure hostname/port etc.) The "AV" part is basically a specification, how the interface looks like. If this standard type is implemented, this device can be used by each UPnP AV client with a defined semantics of all methods. Typically, implementors of UPnP AV write the AV server in a way that it is able to comply with the service specification(s) of the UPnP AV system, i.e. their data store and internal data structures follow the data structures defined by the UPnP AV specification. In our solution, the UPnP AV interface is not the basis of our development; we have our own interface which is used for the MP2 client-server communication. Thus, we also have own (much more flexible) data structures and own access techniques. And yes, our own system off course supports lossless media types. And that's not all; the system is easily extendible by additional plugins providing the ability to import more media types (we call it MetadataExtractors). The UPnP AV interface will be implemented in a later stage and it will be based on our own data structures. We will support as many of the optional parts of UPnP AV as we need to provide our flexibility to the UPnP AV world. Cheers, Daniel [/QUOTE]

Verification