Reply to thread

Message

<blockquote data-quote="FreakyJ" data-source="post: 1150796" data-attributes="member: 106003">I agree here. We need to extend this function.And that is what we need more information for. So now my question is how to extend the media library in the best way to give us these extra information?I would probably port the function from miniDLNA (with credits) and maybe adjust it for our purpose.For the first step I would also do it without transcoding support.Once it is working more or less I would create another plugin which is responsible for transcoding (it can transcode everything MP wants to transcode) and basically a process plugin without any gui or so.Than we can also create profiles for client devices and advertise the protocol info on the basis of our profiles. If the profile in the DB doesn't match one of the supported profiles it gets transcoded.What do you think? But this is more of a long term plan.Another question is: Do we store the final DLNA profile in the DB or do we store all the needed information to dervice the profile from that.Basically move ConfigureProfile() to the importer side or leave it like it is now.I would be in favor of the later option because these informations like codecs etc. might be useful also for other plugins in the future.</blockquote>

[QUOTE="FreakyJ, post: 1150796, member: 106003"] I agree here. We need to extend this function. And that is what we need more information for. So now my question is how to extend the media library in the best way to give us these extra information? I would probably port the function from miniDLNA (with credits) and maybe adjust it for our purpose. For the first step I would also do it without transcoding support. Once it is working more or less I would create another plugin which is responsible for transcoding (it can transcode everything MP wants to transcode) and basically a process plugin without any gui or so. Than we can also create profiles for client devices and advertise the protocol info on the basis of our profiles. If the profile in the DB doesn't match one of the supported profiles it gets transcoded. What do you think? But this is more of a long term plan. Another question is: Do we store the final DLNA profile in the DB or do we store all the needed information to dervice the profile from that. Basically move ConfigureProfile() to the importer side or leave it like it is now. I would be in favor of the later option because these informations like codecs etc. might be useful also for other plugins in the future. [/QUOTE]

Verification