![]() ![]() I guess doing so would enable the config files to be easily stored in a directory hierarchy, which might be useful, if eventually you end-up with a lot of config files. Note: You could perhaps avoid always loading all of the profiles too (instead just lazy loading what you need) by having a kind of list.xml in each subdirectory, which for each profile contains a name, the search pattern(s), and path to its config file. For example, that root profiles.xml could contain the default profile, and reference three other directories: Series Based Profiles (Low Priority), Device Based Profiles (Medium Priority) and User Defined Profiles (Highest Priority). There could be a root profiles.xml, which has some XML nodes in that define the subdirectories (with a priority level) to look in for profiles. ![]() Perhaps this could be achieved using a directory based approach. the Serviio installer can add/delete/update its own, and leave the rest alone. You can select the appropriate profile in the Status section. Look here for a short guide on how to add a new profile. If your device is not supported yet we encourage the users to try writing their own profile and submitting it back to us so that we can include it in a future release of Serviio. It would allow people to put their own profiles into separate files, so that they are easy to keep/migrate when upgrading Serviio, e.g. Serviio comes with a predefined set of profiles.the default profile could be in a file that should never be edited. AVI files (even H264 encoded) which play fine with Serviio/BDP-S570 fail on Serviio/PS4 (media not supported). I did test it on my usual collection that played fine with my Sony BDP-S570 Bluray Player (profile is in Serviio base profiles.xml), transcoding disabled. Serviio developer / Site Admin Posts: 17207. These devices support very little video formats and its neccessary to do transcoding for avi, etc, etc. It could provide a nicer way of separating what people should and shouldn't edit, e.g. Thanks so much for the effort in making PS4 profile. There are some DLNA clients for these devices, for example Media Link Player, Plug Player o Media::Connect.At the minute, the built-in profiles seem to be more series rather than device based, and I'm guessing (in part) that's because of concerns around an explosion of profiles making the profiles.xml file huge!.The current config is already pretty long, which makes it hard to read/find stuff, hence by being able to put profiles into their own files, it would make life that bit easier - for those editing them at least! I played around with my DLNA server (Serviio) and I realized that the PS4 CAN play xvid (and I guess divx) encoded videos after all Theres no PS4 profile.Funnily enough, I just came to post a feature request about splitting-up the Profiles.xml for a few reasons: ![]()
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |