A solution for making Client Profile changes stay applied

General discussion about the media server. Feature requests. Hints, tips and tricks.
Locked
User avatar
phibertron
Posts: 1566
Joined: Sun Jan 30, 2011 5:52 pm
AV Hardware: Hardware
========
WHS - HP Ex495
PS3
XBOX 360
iTouch - Gen 2 and Gen 3
PSP - 3000

Encoders
========
Handbrake
x264
ffmpeg
mencoder

Tagging
======
mp3tag

A solution for making Client Profile changes stay applied

Post by phibertron » Tue Sep 04, 2012 7:25 pm

Have you ever had the need to change the client profile for a device
and noticed that when the server is restarted that those changes are no longer there
Well so did I

To further complicate the issue, this was not always true, sometimes they did stick

I discovered something about client profiles that I had never thought about before
that does effect why some survive changes and some do not
It all has to do with the mapping policy

Here is the definition of the mapping policy taken from the clients.db

Code: Select all

AUTO, FIX, FIXPC 
set to auto if a different client identify string can overrule this entry
set to FIX if the entry can only be overruled by manual user interaction
set to FIXPC for PC software clients, 
Currently in 7.x the MappingUpdatePolicy entry is used for the mapping policy

Code: Select all

<MappingUpdatePolicy>AUTO</MappingUpdatePolicy>
<MappingUpdatePolicy>FIX</MappingUpdatePolicy>
<MappingUpdatePolicy>FIXPC</MappingUpdatePolicy>
Prior to 7.x the DB entry was used for the mapping policy

Code: Select all

DB:AUTO
DB:FIX
DB:FIXPC

In a nutshell, if a client profile has a mapping policy of AUTO
and you assign it to a client that is not made for that profile
on a server reboot, that client will not get that profile
It needs to be FIX or FIXPC for it to be sticky
and get written to the clients.db or clients.data7

Dont change the following client profiles, bad things will happen

Code: Select all

devicedb\default.xml
devicedb\Generic_DLNA_1.0.xml
devicedb\Generic_Media_Receiver.xml
devicedb\Generic_Music_Only_Receiver.xml
devicedb\PacketVideo\PV_Player.xml
devicedb\PacketVideo\Twonky_Aggregation_Server.xml
devicedb\PacketVideo\Twonky_NMC.xml
devicedb\PacketVideo\TwonkyManager.xml
devicedb\PacketVideo\TwonkyMobile.xml
devicedb\PacketVideo\TwonkyPlayer.xml
devicedb\PacketVideo\TwonkyRenderer.xml
All of these have MappingUpdatePolicy set to AUTO
And are the ones that will not survive a server reboot
if they were not auto assigned by the server to the client

Code: Select all

devicedb\Android.xml
devicedb\Apple_iPhone.xml
devicedb\IOMegaNAS.xml
devicedb\Linn\Linn_DS_Music_Player.xml
devicedb\Nokia\Nokia_N95_Phone.xml
devicedb\Nokia\Nokia_Phone.xml
devicedb\Sony\Sony_Blu-Ray_Home_Theater.xml
devicedb\Sony\Sony_Blu-Ray_Player.xml
devicedb\Syabas_Firmware_based.xml
Note:
Why the above are set to AUTO, is anyones guess
As every other client profile is set to either FIX or FIXPC, why not these?

I would add, that those who are creating custom profiles
this info might help you better create a profile that stays applied to a client
viewtopic.php?f=2&t=10627
viewtopic.php?f=2&t=9353
viewtopic.php?f=2&t=9408
viewtopic.php?f=2&t=9416
viewtopic.php?f=2&t=9424
viewtopic.php?f=2&t=9364
viewtopic.php?f=2&t=9497

User avatar
phibertron
Posts: 1566
Joined: Sun Jan 30, 2011 5:52 pm
AV Hardware: Hardware
========
WHS - HP Ex495
PS3
XBOX 360
iTouch - Gen 2 and Gen 3
PSP - 3000

Encoders
========
Handbrake
x264
ffmpeg
mencoder

Tagging
======
mp3tag

Re: A solution for making Client Profile changes stay applie

Post by phibertron » Tue Sep 04, 2012 7:28 pm

To add to this further
Say you wanted to assign the Generic Media Receiver client profile
to clients that were getting assigned some other profile for whatever reason

DO NOT edit or change the Generic_Media_Receiver.xml

Make a copy of it and for example call it Custom_Client_Profile.xml
and change the MappingUpdatePolicy ti FIX
restart the server so that it will be an available choice
now you can apply it to clients and have it stay assigned

Code: Select all

<Client>
     <DeviceId>
          <DisplayName>Custom Client Profile</DisplayName>
          <MappingUpdatePolicy>FIX</MappingUpdatePolicy>
     </DeviceId>
     <Adaptations>
          <DLNA>
               <Version>DLNA15</Version>
          </DLNA>
          </Adaptations>
</Client>


The above is just a starting example that can be leveraged
to create additional custom profiles or additional changes to them
as needed for you client
Creating custom profiles makes it easier to carry them over to newer versions
twonky server, without losing changes if they were made to existing client profiles
just backup your custom client profile and add it to the new version
and adjust if needed
viewtopic.php?f=2&t=10627
viewtopic.php?f=2&t=9353
viewtopic.php?f=2&t=9408
viewtopic.php?f=2&t=9416
viewtopic.php?f=2&t=9424
viewtopic.php?f=2&t=9364
viewtopic.php?f=2&t=9497

Locked