Jump to content


Photo

Remotefallback - copy channels


  • Please log in to reply
17 replies to this topic

#1 littlesat

  • PLi® Core member
  • 56,123 posts

+685
Excellent

Posted 20 March 2018 - 09:24

[modbreak=topic splitted]The original topic starts from here I made a selection and splitted it from the dutch section.

[/modbreak]

 

Hammer!!! Thanks it is a good idea to do it that way...!!!

 

The avahi select for import can also have the option same as fallback.... so same as fallback, box1, box2, ... , manual... (I suggest to put manual at the end...)

 

But still when we add avaji we need in Screen a SetupFallbacktuner.py, just due to Avahi... And for Avahi we need to enter a port... (So I'm considering to change the URL to IP aswell as this is easier)....

 

Is it OK we do this for 6.3 or 7 and leave it as is for 6.2?


Edited by Tech, 20 March 2018 - 20:38.
split from the dutch section

WaveFrontier 28.2E | 23.5E | 19.2E | 16E | 13E | 10/9E | 7E | 5E | 1W | 4/5W | 15W


Re: Remotefallback - copy channels #2 WanWizard

  • PLi® Core member
  • 68,309 posts

+1,719
Excellent

Posted 20 March 2018 - 09:32

Avahi can broadcast the port too, but that probably isn't implemented yet. Also, in case of transcoding you may have two ports. Or one port + transcoding parameters in the URL...

 

I'd say do not implement anything that would delay the release of 6.2, that is already overdue...


Currently in use: VU+ Duo 4K (2xFBC S2), VU+ Solo 4K (1xFBC S2), uClan Usytm 4K Pro (S2+T2), Octagon SF8008 (S2+T2), Zgemma H9.2H (S2+T2)

Due to my bad health, I will not be very active at times and may be slow to respond. I will not read the forum or PM on a regular basis.

Many answers to your question can be found in our new and improved wiki.


Re: Remotefallback - copy channels #3 littlesat

  • PLi® Core member
  • 56,123 posts

+685
Excellent

Posted 20 March 2018 - 09:59

Yep.. what wanwizard suggested is clear. When we have a saperate screen we can also import the channels as soon you leave the config the first time

Edited by littlesat, 20 March 2018 - 10:00.

WaveFrontier 28.2E | 23.5E | 19.2E | 16E | 13E | 10/9E | 7E | 5E | 1W | 4/5W | 15W


Re: Remotefallback - copy channels #4 WanWizard

  • PLi® Core member
  • 68,309 posts

+1,719
Excellent

Posted 20 March 2018 - 10:12

@littlesat:

 

https://github.com/O...server.cpp#L305

 

So the port is available as well. Ideally also _e2transcode._tcp should be announced somewhere, but I don't think it's implemented yet.


Currently in use: VU+ Duo 4K (2xFBC S2), VU+ Solo 4K (1xFBC S2), uClan Usytm 4K Pro (S2+T2), Octagon SF8008 (S2+T2), Zgemma H9.2H (S2+T2)

Due to my bad health, I will not be very active at times and may be slow to respond. I will not read the forum or PM on a regular basis.

Many answers to your question can be found in our new and improved wiki.


Re: Remotefallback - copy channels #5 littlesat

  • PLi® Core member
  • 56,123 posts

+685
Excellent

Posted 20 March 2018 - 11:24

Isn’t smarter just to add a port setting with having it default to 8001?

WaveFrontier 28.2E | 23.5E | 19.2E | 16E | 13E | 10/9E | 7E | 5E | 1W | 4/5W | 15W


Re: Remotefallback - copy channels #6 WanWizard

  • PLi® Core member
  • 68,309 posts

+1,719
Excellent

Posted 20 March 2018 - 11:38

Why? Avahi tells you want it is, so you don't have to enter it. It is configurable at the server end, it doesn't have to be 8001.

 

Note that it does require updates to enigma, currently the 8001 in e2avahi_announce is hardcoded, but the port is user configurable. I think MiLo never got this far...


Currently in use: VU+ Duo 4K (2xFBC S2), VU+ Solo 4K (1xFBC S2), uClan Usytm 4K Pro (S2+T2), Octagon SF8008 (S2+T2), Zgemma H9.2H (S2+T2)

Due to my bad health, I will not be very active at times and may be slow to respond. I will not read the forum or PM on a regular basis.

Many answers to your question can be found in our new and improved wiki.


Re: Remotefallback - copy channels #7 Huevos

  • PLi® Contributor
  • 4,231 posts

+158
Excellent

Posted 20 March 2018 - 12:00

Manual by domain and manual by IP. Sorry if you think mine is complicated. But all you do is open the screen, select fallback enabled and then press green, and setup is complete. Is that so complicated? Everything else is just icing for manual data entry.

 

I could update mine so Avahi servers and manual URL and manual IP are all in one ConfigSelection.



Re: Remotefallback - copy channels #8 WanWizard

  • PLi® Core member
  • 68,309 posts

+1,719
Excellent

Posted 20 March 2018 - 12:42

Are you replying to me or Littlesat?


Currently in use: VU+ Duo 4K (2xFBC S2), VU+ Solo 4K (1xFBC S2), uClan Usytm 4K Pro (S2+T2), Octagon SF8008 (S2+T2), Zgemma H9.2H (S2+T2)

Due to my bad health, I will not be very active at times and may be slow to respond. I will not read the forum or PM on a regular basis.

Many answers to your question can be found in our new and improved wiki.


Re: Remotefallback - copy channels #9 Huevos

  • PLi® Contributor
  • 4,231 posts

+158
Excellent

Posted 20 March 2018 - 13:35

Are you replying to me or Littlesat?

 

You said "Why so complicated?". That was just below the grabs of my fallback setup patch. But if OpenPLi want to write a patch from scratch that's fine too. It's just that a few days you were suggesting in the other thread that we pool resources.


Edited by Huevos, 20 March 2018 - 13:36.


Re: Remotefallback - copy channels #10 WanWizard

  • PLi® Core member
  • 68,309 posts

+1,719
Excellent

Posted 20 March 2018 - 14:05

Yes, to Littlesat, the post directly above my reply. ;) Sorry for the misunderstanding, I need to quote more...


Currently in use: VU+ Duo 4K (2xFBC S2), VU+ Solo 4K (1xFBC S2), uClan Usytm 4K Pro (S2+T2), Octagon SF8008 (S2+T2), Zgemma H9.2H (S2+T2)

Due to my bad health, I will not be very active at times and may be slow to respond. I will not read the forum or PM on a regular basis.

Many answers to your question can be found in our new and improved wiki.


Re: Remotefallback - copy channels #11 littlesat

  • PLi® Core member
  • 56,123 posts

+685
Excellent

Posted 20 March 2018 - 19:06

The port might be configurable, but the default for streaming is 8001... so the client box has to make some assumptions...

 

For 6.3/7.0 I'll made a SetupFallbacktuner.py with this stuff adapted.... For now I leave it as is...


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

WaveFrontier 28.2E | 23.5E | 19.2E | 16E | 13E | 10/9E | 7E | 5E | 1W | 4/5W | 15W


Re: Remotefallback - copy channels #12 Huevos

  • PLi® Contributor
  • 4,231 posts

+158
Excellent

Posted 20 March 2018 - 19:45

The port might be configurable, but the default for streaming is 8001... so the client box has to make some assumptions...

 

For 6.3/7.0 I'll made a SetupFallbacktuner.py with this stuff adapted.... For now I leave it as is...

The whole string that is needed comes direct from the server avahi. No need for the client to make any assumptions. The string can be used directly in config.usage.remote_fallback.value.



Re: Remotefallback - copy channels #13 littlesat

  • PLi® Core member
  • 56,123 posts

+685
Excellent

Posted 20 March 2018 - 19:51

Something in the avahi stuff checks for port 8001... when the server is configured for a different port it will not find it as box as far I understood...

WaveFrontier 28.2E | 23.5E | 19.2E | 16E | 13E | 10/9E | 7E | 5E | 1W | 4/5W | 15W


Re: Remotefallback - copy channels #14 WanWizard

  • PLi® Core member
  • 68,309 posts

+1,719
Excellent

Posted 20 March 2018 - 19:57

The port might be configurable, but the default for streaming is 8001... so the client box has to make some assumptions...

 

Why? The port is broadcasted, there is no assumption to be made.


Currently in use: VU+ Duo 4K (2xFBC S2), VU+ Solo 4K (1xFBC S2), uClan Usytm 4K Pro (S2+T2), Octagon SF8008 (S2+T2), Zgemma H9.2H (S2+T2)

Due to my bad health, I will not be very active at times and may be slow to respond. I will not read the forum or PM on a regular basis.

Many answers to your question can be found in our new and improved wiki.


Re: Remotefallback - copy channels #15 WanWizard

  • PLi® Core member
  • 68,309 posts

+1,719
Excellent

Posted 20 March 2018 - 19:57

Something in the avahi stuff checks for port 8001... when the server is configured for a different port it will not find it as box as far I understood...

 

It is currently hardcoded, I posted the link to the exact line.


Currently in use: VU+ Duo 4K (2xFBC S2), VU+ Solo 4K (1xFBC S2), uClan Usytm 4K Pro (S2+T2), Octagon SF8008 (S2+T2), Zgemma H9.2H (S2+T2)

Due to my bad health, I will not be very active at times and may be slow to respond. I will not read the forum or PM on a regular basis.

Many answers to your question can be found in our new and improved wiki.


Re: Remotefallback - copy channels #16 Huevos

  • PLi® Contributor
  • 4,231 posts

+158
Excellent

Posted 20 March 2018 - 21:23

Littlesat, why do you want to redesign this when I offered my screen?



Re: Remotefallback - copy channels #17 littlesat

  • PLi® Core member
  • 56,123 posts

+685
Excellent

Posted 20 March 2018 - 21:59

Because we would try to make it better with a step less and as import is integrated then vix patch does not really fit anymore... so hold on... i’m Thinking the suggestions from
Wanwizard are the way to go...

Edited by littlesat, 20 March 2018 - 22:00.

WaveFrontier 28.2E | 23.5E | 19.2E | 16E | 13E | 10/9E | 7E | 5E | 1W | 4/5W | 15W


Re: Remotefallback - copy channels #18 Huevos

  • PLi® Contributor
  • 4,231 posts

+158
Excellent

Posted 20 March 2018 - 22:06

I'm happy to adapt it.




1 user(s) are reading this topic

0 members, 1 guests, 0 anonymous users