Page 1 of 1

These Features Needed Mandatory

PostPosted: Thu Aug 06, 2015 3:22 am
by sploit
Hi. These featured need to be added and can be added easily.

1) Custom Profile Injection. (Add Remove Profiles)
You should Inject profiles by splitting them into separate xml files and then serviio loads each one in the directory one by one if its in the list database.
2) Custom Movie Folders for Browser
3) Custom Skins Folder.
4) Popcorn dispenser (Optional flavors)

Re: These Features Needed Mandatory

PostPosted: Thu Aug 20, 2015 10:58 am
by Milkshake
+1 to popcorn dispenser, with one caveat. Needs frozen coke dispenser also...

Re: These Features Needed Mandatory

PostPosted: Thu Aug 20, 2015 1:05 pm
by atc98092
I think the issue with separate XML files for each profile would be maintaining the ability to inherent portions of another profile. I personally don't have an issue with the single profiles XML file, but I do wish it could be reloaded without restarting the service.

Re: These Features Needed Mandatory

PostPosted: Fri Aug 28, 2015 5:24 am
by sploit
Well. Normally I would Agree on a single file not being an issue. But when you dont need all the devices in the list and you constantly have to see thosands of other lines of code then I say split each device into its own profile. Have Serviio look for:
\profiles\
Defaultprofile.xml would only be default.
All other profiles would be seperate .xml
Sony_Bravia.xml
Sony_BlurayS5000.xml

Have Serviio allow which profiles are used and not with checkboxes within a control or something. I dunno. I could write something in VB in seconds that could do that.

Have Serviio Compile a master.xml based on the rule of starting with Default.xml and all the rest in the list.

This would actually fix the need to restart.
In all reality I edit the profile.xml live and just save it in notepad and its updates without needing a restart.

Seems Serviio Loads the Profile from scratch on each Video that is streamed.

Re: These Features Needed Mandatory

PostPosted: Tue Sep 01, 2015 3:09 am
by tstrike
Serviio Features:

Allowing Serviio to use proxies... Given the amount of metadata being collected worldwide, probably best to channel Serviio to use proxying services like Tor or some other service.

If someone knows how to have the feedreader go to a proxy, I would grateful for an explanation.

Re: These Features Needed Mandatory

PostPosted: Tue Sep 01, 2015 11:32 am
by zip
tstrike wrote:Serviio Features:

Allowing Serviio to use proxies... Given the amount of metadata being collected worldwide, probably best to channel Serviio to use proxying services like Tor or some other service.

If someone knows how to have the feedreader go to a proxy, I would grateful for an explanation.

No idea if it'll work, but you could try to set these system properties:

  Code:
-Dhttp.proxyHost=10.0.0.100 -Dhttp.proxyPort=8800

Re: These Features Needed Mandatory

PostPosted: Wed Sep 02, 2015 6:49 am
by tstrike
zip wrote:
tstrike wrote:Serviio Features:

Allowing Serviio to use proxies... Given the amount of metadata being collected worldwide, probably best to channel Serviio to use proxying services like Tor or some other service.

If someone knows how to have the feedreader go to a proxy, I would grateful for an explanation.

No idea if it'll work, but you could try to set these system properties:

  Code:
-Dhttp.proxyHost=10.0.0.100 -Dhttp.proxyPort=8800


That actually worked, but due to the nature of Tor, you really cant pull any streams... Its late here in the US (1:48am CDT), but I want to see if Tor will respond to UDP packet streaming...

So Tor streaming via TCP really doesn't work for anonymity's sake.

Re: These Features Needed Mandatory

PostPosted: Mon Dec 28, 2015 10:30 pm
by josch.hh
+1 for the single xml profiles.

Much easier to maintain.

And if it come to inheritance one could give the different files numbers as filename prefix like you do for udev to define a load order.