275 replies to this topic

[WanWizard]

1. the same as with any other hardware (like a PC), with a warm start you have a pre-initialized box, with a cold start you don't. Not sure why it would have a relation to this topic.

 

2. this was the initial implementation, on which other had the same commit. @littlesat has already confirmed the two will be separated.

[littlesat]

1. Restart is different then cold boot... no pli specific different. You have shutdown or reboot... we already use it for startup to standby which only is effective after cold boot...
2. We can give different urls for the import and the fallback tuner but the for now all users needs to enter two ips or we need an extra option to be able to enter a second op... while most times it is the same. So for know we did not choose to do this... (do you know a real reason?) actually fallback might work later via Avahi then no ip required... but that needs more extra work... I’m considering to add an option to give a different ip when both fallback and import are enabled.. so please hold on! It takes some times...

Edited by littlesat, 17 March 2018 - 22:37.

[Huevos]

1) I know what it is, I am asking what is different in the handling of the start up.

 

@Littlesat, in OpenViX fallback is a choice of Network peer (Avahi), IP, or domain. If you are interest I could send a patch.

[littlesat]

How did they made the choise beterrn avahi and ip? When the patch is good it is fine... I know with avahi you can show a list of local boxes, but some prefer an external adress with transcode port. So we need tei extra configs then?
With avahi you can also not use the setup.xml you have to go for custom code and avahi was meant to do it completeert automatically... in fact this is already working and pli currently takes te lowest ip automatically... we ‘just’ need to have a proper can stream or does not stream try another box for avahi and the ip is not required at all...
In addition due to 6.2 I prefer to leave it as is for know... better to think above real improvements here for 6.3 or 7.0.

Edited by littlesat, 18 March 2018 - 08:25.

[littlesat]

B.t.w.  already prepared a separate URL for import. I just committed it. Adding Avahi selection must be made 'smart'... I think a selection/text combination config type might be preferable here... So with left right you can select, but you can still somehow type... Iguess openvix did not made such an óbject'... I'm not sure it is right byt it was something I was thinking off...

Edited by littlesat, 18 March 2018 - 09:20.

[WanWizard]

Ahavi is probably best implemented with a select with the boxes found that advertise a streaming service, and when you select one, copy the info to the URL field.

 

I think it's simpler, and a lot easier for end-users to understand. Alternatively you could also add a "manual" value to that select, that will show the URL field if selected?

[Abu Baniaz]

It will be a lot easier for you to flash openvix and see how it works. You can then tweak/adjust code as you see fit.

[littlesat]

I even cannot find it in vix code... sounds it is somehow included in a plugin?
We could add manually add url to the avahi list...
But as avahi is dynamic we need a separate fallback tuners setup screen...

Edited by littlesat, 19 March 2018 - 07:11.

[Abu Baniaz]

Its not a plugin. I'm sure Huevos will post link to it later.

As ppsted above, you can choose which method to use.

Avahi, IP or url.

[littlesat]

That is bad... the better when ni streaming boxes show manual ip,
When there are boxes add an option to the list for manual entrance...

[littlesat]

Found... Indeed a separate screen pything to retrieve the dynamic getPeerStreamingBoxes() list...

 

And they add a separate parameter for the port and use config IP as we use a text where by default http:// ... and :8001 is added...

 

https://github.com/O...ckTunerSetup.py

Edited by littlesat, 19 March 2018 - 10:26.

[Huevos]

No. If an avahi server is detected that is selected by default. User can choose between avahi servers if there are multiple servers on the LAN. If no avahi server is detected or you user chooses, fallback can be input by IP or URL.

 

Whatever method is used, the user input is stored in "config.usage.remote_fallback.value", same as OpenPLi.

 

 1.jpg   70.02KB   3 downloads

 

 2.jpg   65.86KB   3 downloads

 

 

[Huevos]

Port number is there as an option when entering IP as this is much faster than the ConfigText method. But the ConfigText method is also available.

 

Also virtual keyboard is available when using the ConfigText method.

 

 3.jpg   56.73KB   3 downloads

 

 4.jpg   77.43KB   3 downloads

 

 

 

 

[littlesat]

only for avahi we need a separate screen...
I was thinking about to creatie a special config class/object where you can select an avahi ip -and- as last option go to the normal ip ‘edit’ and go for a separate streaming port. So you have it in one config and also swig the port and ip to cpp...

Just go left right through avahi and then through the four manually entered ips... just call it ConfigAvahi. I have no
Idea yet how I might made It. Or at least add a config avahi then no extra screen is required...

Due to the settings import we cannot simply do url/ip/avahi for the fallback setting... as fallback can be off and import on... then we always need an extra config for it...

Edited by littlesat, 20 March 2018 - 07:36.

[WanWizard]

Why so complicated? Why not simply a select with "manual entry,box1,box2,box3", and when "manual entry" is selected, show a second input for the IP or DNS name? 

 

That will be a total of 6 lines:

- fallback on/off

- avahi select for fallback

- manual fallback input

- import on/off

- avahi select for import

- manual import input

 

Or am I misunderstanding you?

[Tech]

The story continues here .

 

Gaarne hier verder gaan met berichten welke gerelateerd zijn aan het originele onderwerp.