New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Differentiate between Media Renderers and Control Points #4474
Comments
Hi there, I think this is the right idea. One addition to what is said, since we have at least two ecosystems:
The current solution UMS uses for doing the right transcoding by configuration is actually a pretty good idea. Otherwise, all control points must be as smart as UMS now is. Another idea: The change wouldn't be that huge, if a control point get's always the raw resource (original file format). In a later step, when the The change would be to distinguish between From UPnP Architectrure 2.0 docs:
Another way to identify a |
About distinguish between MediaRenderer and control points.
Yes we can
Most control point apps are not using this, and maybe some TV will. Hard do distinguish.
Most control point apps are advising for other services. Or the apps is on a computer/device that will. I think we should not care if the control point is the end-renderer or not. The thing is that the user rights are done on the UUID, but it should be done on the control point, that may or not have an UUID, so we cannot rely on it. And IP address may change. About the another idea :
That what I propose, with an addition.
Then the control point (TV or not) will choose the right readable format for the renderer. It may also be a good things for renderers that do not have any conf file, as it can take the raw format by itself. |
Are you sure? Maybe we can try to log some CPUUID (in debug mode) if available and share the results here. I can try a few control points that I use, just to see, what is send by the device. We can also check, if in a 2-box setup (television) a CPUUID is send by the internal CP of the TV, and if it differs from the UUID send by the embedded renderer device.
I've tried another media server named At home I used static IP address for the devices I wanted to protect. I think giving DNS names like IMHO, in any case, the "right renderer" has to be picked/identified by UMS ( |
From UPnP :
Control Point
discover content (e.g. video, music, images, etc) on theMediaServer
thruContentDirectory
service.Each content item that is referenced by the
ContentDirectory
service includes various information about that content including the transfer protocol(s) and file format(s) that theMediaServer
can use to transfer the content to theMediaRenderer
.After the desired content has been identified, the
Control Point
needs to determine which transfer protocol and data format should be used to transfer the content from theMediaServer
to theMediaRenderer
.The actual transfer of the content is performed directly by the
MediaServer
andMediaRenderer
.The content transfer happens independently from the
Control Point
and does not involve UPnP itself at all.In short :
Control Point
discover content and give an URI toMediaRenderer
.MediaRenderer
then ask for this URI toMediaServer
.Facts :
Most devices mix
Control Point
andMediaRenderer
.But sometime user have a device
Control Point
that send content to another deviceMediaRenderer
.Solution :
The URI from
ContentDirectory
should include everything the server will need to serve content back (without knowing theMediaRenderer
).That include the media asked, the user that created the link to check the right on media, the transcoder if any, all the transcoding settings if any.
Content item referenced by the
ContentDirectory
may (should) have multipleres
with ideally :Control Point
is aMediaRenderer
and it cannot play the original file format, the adapted file format.The text was updated successfully, but these errors were encountered: