Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[doug.ca]

A question:

I have a couple of DLNA renderers on my home network: a Denon AVR and a AverMedia mediaplayer. I have different DLNA profiles set up for each of these devices, plus an additional profile specific to my PS3. These profiles are used to handle differences in the supported features of each device. For example, the Denon supports unconverted FLAC audio, the AM does not.

Everything works fine if I use the device itself as the controller and access the specific profile. However, I'm having problems sending from my main server, which is a WHS to the AM. Interestingly, it works fine sending from the MC installed on my office computer. The only difference I can see is the order of the profiles configured on each machine. I haven't had a chance to try changing the order of these profiles yet, but this did get me thinking. When you use the Send to/Play to feature from within MC (17.0.62 in my case) to a particular DLNA device when there are multiple profiles, how do you ensure that the correct profile is being used for that device or otherwise tie a specific profile to a specific type of renderer?

[MrC]

See bob's response here:

   http://yabb.jriver.com/interact/index.php?topic=68453.msg463924#msg463924

[doug.ca]

Thanks MrC. That answers my question.

Given this, does it make sense to ask for this as a new feature to give MC the ability to push to a device using a specific profile?

I assume this could be done by either tying a configuration to a discovered device, which I think would be the best method. Or, by using a Sent to <device> using <DLNA profile> command. The problem with the former is that DLNA devices are discovered devices and may come and go. The problem with the latter is how does this get implemented when using a controller to initiate the push? Nevertheless, this would be useful for people that have a range of DLNA devices on their network.

Cheers

[MrC]

I think devices should be tied to a configuration / server profile.  Once a device is seen, it can be associated with a chosen profile.  Since users may want to push various formats to different devices, a configuration list attached to each profile seems like a good idea.

I ran into this problem once, and had to remove and reconfigure the DNLA servers list to get the order correct so that I could push lossless audio to some devices, but pull using a different server.  And figuring this out was just trial and error and some packet tracing.  As an aside, it would be helpful if the servers could be reordered.

This said, I have little knowledge regarding the technical issues this may present.

[doug.ca]

That's certainly the way I'd like to see this implemented. Also, I agree, that as a bear minimum, it would be nice to be able to reorder the profiles without having to delete them and start all over again.

[Mediahome]

Yes, given the variety of DLNA devices out there, and the quirks that they have, you really need to be able to assign a DLNA profile to each discovered device.  Having the ability to re-arrange the list would be nice.  I would also like to be able to hide a discovered device.  I don't think that my "Roku Streaming Player" is ever going to be a full fledged DLNA renderer even though it gets discovered as a DLNA device. 

Mediahome

[doug.ca]

Under a DLNA device's advanced options there are a number of options that can be selected. Some seem self explanatory others are not as seemingly obvious. Is there any documentation as to specially what each of these options does? Other than the built in profiles, is there any documentation that lists the attributes that should be used in conjunction with specific hardware?

[mbagge]

Actually MC should create a profile itself when it discovers a new dlna device. Then we could make the necessary adjustments to it. If we then plays to a specific zone, MC would know which dlna profile to use.

[bob]

Yes, given the variety of DLNA devices out there, and the quirks that they have, you really need to be able to assign a DLNA profile to each discovered device.  Having the ability to re-arrange the list would be nice.  I would also like to be able to hide a discovered device.  I don't think that my "Roku Streaming Player" is ever going to be a full fledged DLNA renderer even though it gets discovered as a DLNA device. 

Mediahome

Association is currently in beta.

[bob]

Under a DLNA device's advanced options there are a number of options that can be selected. Some seem self explanatory others are not as seemingly obvious. Is there any documentation as to specially what each of these options does? Other than the built in profiles, is there any documentation that lists the attributes that should be used in conjunction with specific hardware?

Other than DLNAExtra, logging and the video mimetype/DLNA flag overrides you should leave the options alone. They are mainly for supporting older uPnP devices.
The PS3 and WMC compat settings are done by the template selection. They fine tune the conditions under which transcode when necessary invokes transcoding.
Also WMC compat makes the server act as a Windows Media Connect server which makes it xbox 360 compatible (and not compatible with everything else).

 

[DWAnderson]

Association is currently in beta.

I just came across this topic in trying to play to my Roku Soundbridges. I was pleased to discover that this feature was implemented and all I needed to do to get this to work was to right click on the Soundbridges in the Playing Now list of devices and select Associate with DLNA Server (choosing the DLNA server that I had been using for years when using the Soundbridges' menu system to select tracks to play).

Thanks for creating a great DLNA server!