Working DLNA Profiles

@KenEisman said:
Okay, I feel really stupid. But I’ve searched and searched both here and across the whole web.

How the heck do I install one of these profiles AND then get Plex to use it?!?!

I’m sure the answer must be painfully obvious, but I just can’t find it. I’m trying to use the built-in DLNA client on my Vizio Smart TV. (Apparently, mine is too old to use the Plex client built for the Vizio).

Thanks for your help.

It is described here: https://forums.plex.tv/discussion/73702/writing-profiles-for-dlna-devices

User profiles
User profiles are authored by individual users and are never changed by the server. User profile files are located in the Plex Media Server user directory, in a directory called Profiles. If you have never authored a user profile before, this directory will not exist.

If you have a profile you want to use, just drop it in the user profiles directory and restart PMS. If the information it gets from the device matches the information in the DeviceDescription section of the profile, it will be used.

Jeff

@jdc0730 said:

Hey Jeff!

Do you think this profile would work with my Yamaha RX-V479?

Just to clarify, when applying this profile to my PMS does this enable the receiver to be visible to PMS and play audio?

Thanks!
Joe

@joefog ,

What this profile allows you to do is to use the “Server” function to browse your PMS server for music to play. Where this profile would be helpful is if you can already see your server but are having trouble playing back audio. That happens because PMS is sending audio to the receiver that it doesn’t understand. If the networking is set up properly, you should be able to see and browse your PMS server from the unit and possibly play certain types of audio (for example, MP3’s may play but others don’t) without any changes. If you can’t even see the server, the profile won’t help.

It looks like your particular unit may support more types than mine, so the result of using the profile would be that items are transcoded that should not be. In particular, it looks like your unit natively supports ALAC and AIFF. RX-V479 - Overview - AV Receivers - Audio & Visual - Products - Yamaha - United States This profile would cause those types to be transcoded. Given the breadth of codec’s supported by your unit, I’m surprised the default isn’t working.

All that being said, the profile will not work unmodified because I wrote it specifically for my receiver. That being said, you can easily modify the “Device Description” section to test it out. You can probably just remove the ModelName and ModelNumber items and it should be picked up.

Hope that helps.
Jeff

@jdc0730

Thank you for your reply! Makes sense now… Yes, I can ‘see’ my NAS drive from my receiver and play files fine but what I hoped I could do was be able to ‘see’ the receiver from Plex (on one of my IOS devices or laptop) and use Plex to control my audio - instead of using the Yamaha Musiccast app. Do you know if this is possible? I thought that being a DLNA receiver this would be fairly easy but it seems I was wrong!

@joefog said:

@jdc0730 said:

Hey Jeff!

Do you think this profile would work with my Yamaha RX-V479?

Just to clarify, when applying this profile to my PMS does this enable the receiver to be visible to PMS and play audio?

Thanks!
Joe

@joefog ,

What this profile allows you to do is to use the “Server” function to browse your PMS server for music to play. Where this profile would be helpful is if you can already see your server but are having trouble playing back audio. That happens because PMS is sending audio to the receiver that it doesn’t understand. If the networking is set up properly, you should be able to see and browse your PMS server from the unit and possibly play certain types of audio (for example, MP3’s may play but others don’t) without any changes. If you can’t even see the server, the profile won’t help.

It looks like your particular unit may support more types than mine, so the result of using the profile would be that items are transcoded that should not be. In particular, it looks like your unit natively supports ALAC and AIFF. RX-V479 - Overview - AV Receivers - Audio & Visual - Products - Yamaha - United States This profile would cause those types to be transcoded. Given the breadth of codec’s supported by your unit, I’m surprised the default isn’t working.

All that being said, the profile will not work unmodified because I wrote it specifically for my receiver. That being said, you can easily modify the “Device Description” section to test it out. You can probably just remove the ModelName and ModelNumber items and it should be picked up.

Hope that helps.
Jeff

@jdc0730

Thank you for your reply! Makes sense now… Yes, I can ‘see’ my NAS drive from my receiver and play files fine but what I hoped I could do was be able to ‘see’ the receiver from Plex (on one of my IOS devices or laptop) and use Plex to control my audio - instead of using the Yamaha Musiccast app. Do you know if this is possible? I thought that being a DLNA receiver this would be fairly easy but it seems I was wrong!

@joefog
I don’t believe there is any way to do that. If I am understanding what you are wanting, that’s really not what DLNA is for. What I am hearing you looking for is a casting protocol. I am not aware of anything on the Plex server side that does that. I do believe the iOS Plex client can connect to the amplifier (at least mine does) via AirPlay. You are using the phone as an intermediate. That’s the only thing I am aware of.

@jdc0730 said:

@joefog said:

@jdc0730 said:

Hey Jeff!

Do you think this profile would work with my Yamaha RX-V479?

Just to clarify, when applying this profile to my PMS does this enable the receiver to be visible to PMS and play audio?

Thanks!
Joe

@joefog ,

What this profile allows you to do is to use the “Server” function to browse your PMS server for music to play. Where this profile would be helpful is if you can already see your server but are having trouble playing back audio. That happens because PMS is sending audio to the receiver that it doesn’t understand. If the networking is set up properly, you should be able to see and browse your PMS server from the unit and possibly play certain types of audio (for example, MP3’s may play but others don’t) without any changes. If you can’t even see the server, the profile won’t help.

It looks like your particular unit may support more types than mine, so the result of using the profile would be that items are transcoded that should not be. In particular, it looks like your unit natively supports ALAC and AIFF. RX-V479 - Overview - AV Receivers - Audio & Visual - Products - Yamaha - United States This profile would cause those types to be transcoded. Given the breadth of codec’s supported by your unit, I’m surprised the default isn’t working.

All that being said, the profile will not work unmodified because I wrote it specifically for my receiver. That being said, you can easily modify the “Device Description” section to test it out. You can probably just remove the ModelName and ModelNumber items and it should be picked up.

Hope that helps.
Jeff

@jdc0730

Thank you for your reply! Makes sense now… Yes, I can ‘see’ my NAS drive from my receiver and play files fine but what I hoped I could do was be able to ‘see’ the receiver from Plex (on one of my IOS devices or laptop) and use Plex to control my audio - instead of using the Yamaha Musiccast app. Do you know if this is possible? I thought that being a DLNA receiver this would be fairly easy but it seems I was wrong!

@joefog
I don’t believe there is any way to do that. If I am understanding what you are wanting, that’s really not what DLNA is for. What I am hearing you looking for is a casting protocol. I am not aware of anything on the Plex server side that does that. I do believe the iOS Plex client can connect to the amplifier (at least mine does) via AirPlay. You are using the phone as an intermediate. That’s the only thing I am aware of.

Cool, thanks for your response Jeff. I’ve managed a workaround by having the Plex app running on the Apple Tv and casting to it from my IOS Plex app, switching the TV off and keeping the receiver on.

OK… It would be much easier if there was on the DLNA client preferences a drop down list to choose your TV/Player (Profile)

That’s very easy to do for Plex DEVS me thinks…

Plex on the 2017 Nvidia Shield Pro now does dlna but for some reason my 4k mkv are listed as mpg and cause the plex server to restart when you try to play a movie. What is a working profile for Samsung UN65KS9500? It can direct play all my movies but plex wants to transcode them. I agree with purelondon.

Working profile for Yamaha RX-V3900. Transcodes everything except MP3 and AAC to uncompressed PCM.
Has so far played everything in my music library without a glitch.

Anyone Got a profile for Samsung Qled 2017? 8 series. DNLA is very unstable on my tv .

Thanks :slight_smile:

Wanted to share my working profile for my Panasonic Viera ST50.
Had some issues playing some shows that were working fine with Twonky.
Should stream mkv h264 and x264 shows fine now :slight_smile:

Do you have working DLNA profile

for Sony Bravia TV KDL-24W605A (2013 model year) and

for Panasonic Viera TX-LR42D25 (2010 model year)?

Does anyone have a profile for a Pure Evoke C-F6 internet radio?

GetProtocolInfo reports

http-get:*:audio/L16;rate=44100;channels=1:DLNA.ORG_PN=LPCM,
http-get:*:audio/L16;rate=44100;channels=2:DLNA.ORG_PN=LPCM,
http-get:*:audio/L16;rate=48000;channels=1:DLNA.ORG_PN=LPCM,
http-get:*:audio/L16;rate=48000;channels=2:DLNA.ORG_PN=LPCM,
http-get:*:audio/x-ms-wma:DLNA.ORG_PN=WMABASE,
http-get:*:audio/x-ms-wma:DLNA.ORG_PN=WMAFULL,
http-get:*:audio/mpeg:DLNA.ORG_PN=MP3,
http-get:*:audio/mpeg:DLNA.ORG_PN=MP3X,
http-get:*:audio/mp4:DLNA.ORG_PN=AAC_ISO_320,
http-get:*:audio/3gpp:DLNA.ORG_PN=AAC_ISO_320,
http-get:*:audio/L16:*,
http-get:*:audio/L16;rate=11000;channels=1:*,
http-get:*:audio/L16;rate=11000;channels=2:*,
http-get:*:audio/L16;rate=11025;channels=1:*,
http-get:*:audio/L16;rate=11025;channels=2:*,
http-get:*:audio/L16;rate=22000;channels=1:*,
http-get:*:audio/L16;rate=22000;channels=2:*,
http-get:*:audio/L16;rate=22050;channels=1:*,
http-get:*:audio/L16;rate=22050;channels=2:*,
http-get:*:audio/L16;rate=44100;channels=4:*,
http-get:*:audio/L16;rate=44100;channels=6:*,
http-get:*:audio/L16;rate=44100;channels=8:*,
http-get:*:audio/L16;rate=8000;channels=1:*,
http-get:*:audio/L16;rate=8000;channels=2:*,
http-get:*:audio/L8:*,
http-get:*:audio/L8;rate=11000;channels=1:*,
http-get:*:audio/L8;rate=11000;channels=2:*,
http-get:*:audio/L8;rate=11025;channels=1:*,
http-get:*:audio/L8;rate=11025;channels=2:*,
http-get:*:audio/L8;rate=22000;channels=1:*,
http-get:*:audio/L8;rate=22000;channels=2:*,
http-get:*:audio/L8;rate=22050;channels=1:*,
http-get:*:audio/L8;rate=22050;channels=2:*,
http-get:*:audio/L8;rate=44100;channels=1:*,
http-get:*:audio/L8;rate=44100;channels=2:*,
http-get:*:audio/L8;rate=48000;channels=1:*,
http-get:*:audio/L8;rate=48000;channels=2:*,
http-get:*:audio/L8;rate=8000;channels=1:*,
http-get:*:audio/L8;rate=8000;channels=2:*,
http-get:*:audio/flac:*,
http-get:*:audio/x-flac:*,
http-get:*:audio/wav:*,
http-get:*:audio/x-wav:*,
http-get:*:audio/x-ms-wma:*,
http-get:*:audio/mpeg:*,
http-get:*:audio/mp4:*,
http-get:*:audio/m4a:*,
http-get:*:audio/x-m4a:*,
http-get:*:audio/m4b:*,
http-get:*:audio/x-m4b:*,
http-get:*:audio/x-aac:*,
http-get:*:audio/3gpp:*

This is what I’ve got for the Pure Evoke C-F6 internet radio:

<?xml version="1.0" encoding="utf-8"?>
<Client name="Pure Evoke C-F6">
	<!-- Author: Westyfield2 -->
	<Identification>
		<!-- Have observed the radio use the first user-agent for browsing and the second user-agent for playing -->
		<Header name="User-Agent" substring="FSL DLNADOC/1.50 UPnP Stack/1.0" />
		<Header name="User-Agent" substring="NSPlayer/8.0.0.3801" />
		<!-- Device description as seen from Device Spy -->
		<DeviceDescription type="urn:schemas-upnp-org:device:MediaRenderer:1">
			<FriendlyName substring="Evoke C-F6" />
			<ModelName substring="Evoke C-F6" />
			<ModelNumber substring="Evoke C-F6" />
			<ModelUrl substring="http://www.pure.com/digital-radio" />
			<ModelDescription substring="Digital Radio with CD" />
			<Manufacturer substring="PURE" />
			<ManufacturerUrl substring="http://www.pure.com" />
			<SerialNumber substring="zzz_removed_my_serial_number" />
		</DeviceDescription>
	</Identification>
	<TranscodeTargets>
		<!-- Transcode all unsupported audio to FLAC.  Could alternatively use MP3 for lossy playback -->
		<MusicProfile container="flac" codec="flac" />
	</TranscodeTargets>
	<DirectPlayProfiles>
		<!-- Define the formats that the device understand natively -->
		<!-- User manual lists WMA, AAC, MP3, FLAC and GetProtocolInfo returns the full details -->
		<MusicProfile container="mp4" codec="aac" />
		<MusicProfile container="mp3" codec="mp3" />
		<MusicProfile container="mp3" codec="mp3x" />
		<MusicProfile container="mpeg" codec="mp3" />
		<MusicProfile container="mpeg" codec="mp3x" />
		<MusicProfile container="3gpp" codec="aac" />
		<!-- The Music Profile just below indicates that flac files will be directly played on the radio -->
		<MusicProfile container="flac" codec="flac" />
	</DirectPlayProfiles>
</Client>

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.