2041 replies to this topic

[littlesat]

On Server box should not be that issue since you have the original reference stored in Navigation.

On the remote box you dont know what was the original because the box doesnt understand that this is stream relayed service

Good point... then I need to revert one of my commits from today..... I thought I could simplify some code....

[DimitarCC]

For the delay when we have to keep it I prefer to have a SystemInfo.... and not bother the user with it... when it is really sometimes needed to get a higher value for some hardware then we can arrange that..,. Or even start just with a fix 100 and see if a config is really needed.

 

I think a setting of '0' is not really a valid added value... 0 and 100 ms almost nobody does notice and even when you have a FBC tuner when more tuners are occupied it may still go wrong...

 

A configuration of 0 is suitable for multi tuner systems (with independent dish connections) where you have a free tuners most of the time. Then a delay is not needed.

 

The current value of 100ms is proved to not work with DVB-S USB tuners. They require delay of about 1000. Also some tuner/boxes like qviart dual 4K require about 500ms. It is a matter of try and guess and will never be able to get the correct value for all tuner models out there imho.

[littlesat]

This fully described that this is a work-a-round and not a structural solution. Then you always get these kind ticky tricks. It would be nicer to find a way that a 'trigger' could be made that detected when the tuner becomes free...  But for the time being this is it... And indeed doing it per box when it also depends on USB tuners etc is not helpful. Till timer related stuff and then retry still drops a red flag....

 

My question here is it possible to detect when the tuner becomes free and then try again.... First we need to detect of course which tuner is in use for the stream and even I could not find it yet (I can find recordings, PIGs, live TV but not tuners used by which stream).

 

A configuration of 0 is suitable for multi tuner systems (with independent dish connections) where you have a free tuners most of the time. Then a delay is not needed.

 

The current value of 100ms is proved to not work with DVB-S USB tuners. They require delay of about 1000. Also some tuner/boxes like qviart dual 4K require about 500ms. It is a matter of try and guess and will never be able to get the correct value for all tuner models out there imho.

Edited by littlesat, 30 November 2023 - 17:15.

[Huevos]

For the delay when we have to keep it I prefer to have a SystemInfo.... and not bother the user with it... when it is really sometimes needed to get a higher value for some hardware then we can arrange that..,. Or even start just with a fix 100 and see if a config is really needed..

....

Edited by Huevos, 30 November 2023 - 23:51.

[littlesat]

Does not work this idea indeed -> usb tuners
That is also why such solutions should rise a red flag…. So at least put a remark in the code as this is something that should be resolved maybe later.

Edited by littlesat, 1 December 2023 - 05:58.

[littlesat]

In the skin eg the about screen looks nicer with a pager instead of slider and in the infobar I miss the streaming indicator. In the original skin this was a yellow dot. In addition Indo not prefer blinking. I think the recoding icon in the infobar(s) look better when they do not blink as it feels nervous.
In the detailed second infobar we usually show detailed information. It is in a different format as it is now. In the simple second infobar we usually show only epg. Is there still place to show the info we are used to. Of course it might be in a better format and the pliexpertinfo could be extend (how did I ever named it like that and special other teams kept it as is)

Edited by littlesat, 1 December 2023 - 07:55.

[DimitarCC]

I think the recoding icon in the infobar(s) look better when they do not blink as it feels nervous.

 

Thats good but have to be user setting. Because some people prefer it blinking. I suggest put an option in the User interface settings about that and adjust the converter/renderer.

 

 

In the skin eg the about screen looks nicer with a pager instead of slider 

 

I agree. Have to be changed.

 

 

in the infobar I miss the streaming indicator. In the original skin this was a yellow dot.

 

Yes...Well there is no space for that in main infobar. maybe at the second infobar i can put it.

 

 

In the detailed second infobar we usually show detailed information. It is in a different format as it is now. In the simple second infobar we usually show only epg. Is there still place to show the info we are used to. 

 

Well maybe but it will be difficult to design that since seems to be PLi specific. Maybe if you propose a design for that......

[DimitarCC]

P.S. A pager was added to about screens. You can find it in the skin repo or in next build.

[littlesat]

Thats good but have to be user setting. Because some people prefer it blinking. I suggest put an option in the User interface settings about that and adjust the converter/renderer.

 

Very sensitive...as usually I do not prefer adding user configs.... why not let users get used that it is not blinking ... Next discussion is the default

It is always that users were used to it that is was blinking... but the blinking does totally not have any added value... It just makes users nervous... We had this discussion years and years ago... we decide to ban this kind of blanking. You have to be courageous to do this I agree... So please consider to abandon the blanking and avoid another setting.

 

Yes...Well there is no space for that in main infobar. maybe at the second infobar i can put it.

 

You can make a big larger icon then the record marker and put it on the same location. When both are displayed the recording icon has a yellow border... (and when the recording icon is blinking you can see it alternating), 

 

For the standard skin I had long time ago already the idea to make a larger yellow circle for it and put it behind the red circle for recording (this skin had simple circles). In addition we might add something that for stream relay 'locally' this stream icon will not me shown.

 

or make a combined recording stream icon.... so we have three, stream only, recording only, stream and recording...

 

 

Well maybe but it will be difficult to design that since seems to be PLi specific.   Maybe if you propose a design for that......

 

I'll do.. but here it would be helpfull when other image adapt to the simply/full second infobar as well... This time we have a feature others do not have or did not merged in yet.

Edited by littlesat, 1 December 2023 - 12:12.

[DimitarCC]

It seems OpenViX have extended second infobar but no quick toggle. Will look.

Edited by DimitarCC, 1 December 2023 - 12:16.

[DimitarCC]

 

Thats good but have to be user setting. Because some people prefer it blinking. I suggest put an option in the User interface settings about that and adjust the converter/renderer.

 

Very sensitive...as usually I do not prefer adding user configs.... why not let users get used that it is not blinking ... Next discussion is the default

It is always that users were used to it that is was blinking... but the blinking does totally not have any added value... It just makes users nervous... We had this discussion years and years ago... we decide to ban this kind of blanking. You have to be courageous to do this I agree... So please consider to abandon the blanking and avoid another setting.

 

 

Well but i also prefer it blinking. So the only option is user setting. Maybe with default false (no blinking) and if somebody like me want it to just enable it.

[littlesat]

Disable it and you noticed you'll not miss it at all... and the skin give a look with more rest... especially when a recording is running..... But I'm afraid I cannot convince you - as you are one of those that get used to it and never tried without blinking (LOL).

 

Maybe we should (simply)enable/disable the complete blinking... but ensure it is always shown when disabled....

Edited by littlesat, 1 December 2023 - 13:54.

[DimitarCC]

It is designer choice...And personal preference. People are different and can not be the same. They have different wished and preferences.

Its not a matter of only my preference but to all.

Thats why i suggest setting indeed to disable the whole blinking functionality and fix the conditionalshowhide to behave like normal when blink is selected.

 

On the other hand as i said its a designer preference so people that want to use the skin have to adjust to it (if a user setting is not provided).

 

So in my opinion there is 2 options:

 

1. Provide user setting to disable the blinking even if it is defined in the skin. In that way users can overwrite the skin designer preference.

2. Not provide user setting but stick what is defined in the skin. In this case users have to adjust/get used to the blinking.

[DimitarCC]

I propose that handling....

 

https://github.com/O...igma2/pull/3853

 

Its simple and i don't see a reason to not be used like that. In that way will satisfy all users.

[littlesat]

The name of the config is not correct... is says disable_blanking... while it actually does enable_blanking.

 

I discovered it after I merged it....

 

I also saw we have a config that can blink the clock for a recording (in the front display).... the config is there but you cannot reach it by a setting. This can also be added with the condition the enable_blanking thing is enabled/True.

 

When changing the name the default should be default disabled as this is openPLi's standard we decided to go for years ago... (and I remember that time it was a long discussion as we also decided that time not to go for a config and now it is in.... there was a big part of the team that did not want to get it blinked...)

Edited by littlesat, 1 December 2023 - 16:39.

[DimitarCC]

OK. I will change the name....

 

And where is that for that clock?

 

Update:

 

Here is the pull

 

https://github.com/O...igma2/pull/3854

 

Now it states enable blinking....

 

For that clock anyway it will not blink with the new setting....

But you decide should that be enabled or not.

Edited by DimitarCC, 1 December 2023 - 16:48.

[Pr2]

Hi,

 

I give a try to your skin and here are a few comments:

 

- the icon used to represent the cable (DVB-C) channels in the the service list looks like an umbrella rather than a cable  (can I advice you to use the same icon has the default openpli skin and turn it white).

- the icon for the IPTV channels is colored while SAT and CABLE are not. I think that it will be better to use a pure white icon like then other rather than a coloured one (I would also suggest to use the same one as the OpenPLi default skin).

- the GMEPG doesn't look very nice, I miss the program separator (I really think that the OpenPLi default one look better). The currently watching channels line is full green for the whole EPG but are using the same color for the current program on other channels, this choice is a bit strange to me to use the same color to display different thinks. OpenPLi use blue for the current time program and green to highlight the line this is a better approach I think.

- I also prefer to have the Picture-In-Graphic as big as possible, in your skin the PiG window is always very small. I am wondering if it is useful to display in big the channel picon?

- in the second info bar and when browsing the menus, is it possible to customise the background transparency level? Would be a "nice to have" option if possible.

[catastrofus]

After updaten OpenPLi today (using DarkOS) I'm stuck in a bootloop.

Switching back to FullNightHD it's up & running again.

Today, after reinstalling DarkOS and switching to it, another GS.

Attached Files

•  enigma2_crash_1701445569.log   3.09KB   2 downloads

[littlesat]

The blinking clock for recoding (on display) is a config but this config is not available anymore on the setup.xml…. Somehow it is missing.

[littlesat]

@catastrofis, I’m afraid you need to reflash or update again. As far I know what I see in your crashlog was resolved.