2041 replies to this topic

[WanWizard]

English !!!

 

And it is about time those functions are decoupled from the fallback tuner code, as they have NO relattion whatsoever with a fallback tuner (same for channel and EPG import), which is very confusing for users.

[littlesat]

Actually they still have a connection…. Eg the ip address can be taken over from the fallbacktuner and by design it was part of the project I did at that time years ago. The same for epg import and channel import. So really decoupled it isn’t… and by config it is also not easy to split it….
It was also the idea that time you config the fallback, arrange import epg and channel list from that fallback and arrange the tuners from that feedback in one config screen…. The exceptions to do some stuff on different boxes was not included in the orriginally idea.

Edited by littlesat, 6 April 2024 - 17:23.

[WanWizard]

That is implementation and legacy. My point is that it SHOULD be decoupled.

 

Functionally, there is no relation to tuners or tuning. I use remote timer, and import of channels and EPG on all my boxes. None of them use or need any fallback functionality.

 

If, as a user, I have a need for remote timer functionality (to bring it back on topic), the last place I would look for it is in the tuner menu...

[Snoete]

Main reason for still using Partnerbox is the option to use remote timers as default.

Important to us because we use one receiver for recording only, the other three are always free for watching TV or a recorded movie.

 

If you could implement that "Default remotetimer" option into Fallbacktuner there is no reason to use Partnerbox any more. 

 

My receivers only have a 100Mb/s network adapter so watching a recorded program (NAS) and streaming to record at the same time is not possible.

That's why we don't use the fallback functionality.

Edited by Snoete, 6 April 2024 - 19:15.

[WanWizard]

Main reason for still using Partnerbox is the option to use remote timers as default.

Important to us because we use one receiver for recording only, the other three are always free for watching TV or a recorded movie.

 

I do the same, my recording box is in the attic, without a TV attached.

 

And indeed, if the box has local tuners, local timers will be the default, which I find annoying too (but is also legacy functionality, the idea that remote timers are only relevant for when you use a fallback tuner).
 

[Snoete]

Maybe a good reason to add the "default remotetimer" option to the Fallback option-menu?!

 

If that is not possible, it's good to have a simple Default remotetimer option as a backup like Partnerbox or the remoteTimer Plugin.

Wich always works for Wife and kids . 

 

Does someone know how to make the Partnerbox Timer-list readable in this beautiful skin?

--> https://forums.openp...84#entry1616321

 

 Partnerbox Timerlist.jpg   67.21KB   2 downloads

Edited by Snoete, 6 April 2024 - 20:14.

[littlesat]

With that option the fallback tuner’s timer is default…. So again no partnerbox needed… so again no need to adapt that screen as the functionality is totally migrated. And the option is there at the fallback tuner (where wanwizard is considering to put it somewhere else)

Edited by littlesat, 7 April 2024 - 07:38.

[Snoete]

OK that would be nice! And putting it somewhere else is in the local timermenu when the Fallback tuner is activated ?

[WanWizard]

With that option the fallback tuner’s timer is default…. So again no partnerbox needed… so again no need to adapt that screen as the functionality is totally migrated. And the option is there at the fallback tuner (where wanwizard is considering to put it somewhere else)

 

Not sure what you mean, but the fallback timer is ONLY default if there are no local tuners.

 

So in my case it is NEVER default, and I always have to remember to change it when I create a new timer. Pretty annoying, so I understand @Snoete.

[Snoete]

OK now i understand what you mean, in that case you would need an option in the Fallback optionsmenu to make the Fallback timer default...

Because how many receivers have no tuners?!

Edited by Snoete, 7 April 2024 - 11:49.

[WanWizard]

It is not about physical tuners, but about enabled tuners. So receivers that only use streams from another box.

 

It is all related to the original narrow scope of the reason a fallback tuner was implemented. The scope has widened, the code needs to be adapted, and remote timer, channels and EPG needs to be decoupled from the streaming functionality.

[Snoete]

At the moment we already have a choice in the Timermenu for a standard local timer, OR a optional remote timer when the Fallbacktuner is enabled.

U can't make an option to change that and setting the remote timer as default, so without adapting the code for remote timer, channels and EPG?

[Snoete]

So adding an option in the Fallback options menu to make the Fallback timer default instead of the local timer.

 

 Fallback options.jpg   78.76KB   1 downloads

 

 Timermenu.jpg   66.2KB   1 downloads

[WanWizard]

No,

 

At least not here. In the timer screen, the default for "Fallback Timer" is "No" (or red in your case). The default only changes if I disable all tuners in the box.

 

It is quite annoying, as it sometimes goes wrong, and most of my boxes don't have the network bandwidth to record, so all those local timers will fail.

Attached Files

•  1_0_1_1966_7E6_2_11A0000_0_0_0_20240407124524.jpg   116.42KB   2 downloads
•  1_0_1_1966_7E6_2_11A0000_0_0_0_20240407124544.jpg   62.83KB   2 downloads

[littlesat]

Sounds we need to add an option for the fallback tuner in case we have an active tuner in a client box. Makes a big sense!!! Please send me an reminder when I do not implement it somewhere next week.

 

and maybe split this out of this tread as it is not related to this skin.

 

Regarding the wrong skinning it could be that oe-a uses a modified version from partnerbox… and then it is not easy to adjust.

Edited by littlesat, 7 April 2024 - 12:58.

[WanWizard]

And we need to remove remote timer, import epg and import channels from the fallback tuner screen, it doesn't belong there.

[Snoete]

That's exactly what I meant.

Thank you littlesat and WanWizard!

Edited by Snoete, 7 April 2024 - 12:59.

[littlesat]

To move it to a different place is something I do not agree as it is somehow related and also in the way the code is made now. But I think we need to discuss it offline. I also think this is part for the complete menu structure. There are multiple points where we can add more logics… then I would prefer to see a complete new menu mapping first before implement something. Please note that behind all the options in fallback tuner there is code behind the configs… also for the fallback timer and it are no straight forward configs. So there are some dependencies

Edited by littlesat, 7 April 2024 - 13:07.

[Snoete]

Changing the itemHeight to 120 in skin_plugins.xml did the trick.

</screen>
	<screen name="RemoteTimer" position="fill" flags="wfNoBorder" backgroundColor="transparent">
		<panel name="Screen_1_1" />
		<widget name="timerlist" position="135,160" size="1650,6*90" scrollbarMode="showNever" itemHeight="120" iconMargin="30" rowSplit="45" setEventNameFont="Regular;32" setServiceNameFont="Regular;28" setFont="Regular;28" satPosLeft="250" sidesMargin="20" />
		<widget addon="Pager" connection="timerlist" position="145,915" size="1630,25" transparent="1" backgroundColor="background" />
		<eLabel position="135,720" size="1650,2" backgroundColor="background5" zPosition="-7" />
		<widget name="text" position="145,730" size="1620,150" backgroundColor="background" font="Regular;30" halign="center" valign="center"/>
	</screen>

 Partnerbox remote timerlist.jpg   84KB   2 downloads

 

[littlesat]

On the bottom of each line the ‘g’-s are still cut off.