218 replies to this topic

[littlesat]

As our sources are available... that should be no issue at all... But please please please let Dream Elite then also be open!!!

[vgi]

I just use DE 2.1.
How can I get your skin please?
(I cannot flash my DM 800 with PLi .Always stops in the middle of process. The null modem cable I bought, doesn't work with Dream up either, so I gave up)

[Jahu]

Flash with browser, why null modem cable?

[littlesat]

How can I get your skin please?

I think not... DE should adapt to some PLi-specific skin features first... I suggest DE does not recognize <panel...

[vgi]

How can I get your skin please?

I think not... DE should adapt to some PLi-specific skin features first... I suggest DE does not recognize <panel...

Thank you anyway...

Edited by vgi, 12 December 2011 - 13:53.

[macnuts]

Three issues regarding your lovely skin (all observed on DM8000):[list=1]
[*]Blue button menu: please consider reverting back to standard menu, as most skins have. Rationale: the menu "picture preview" feature "conflicts" a little bit with PiP. Note that all PiP functions are activated via this menu (PiP on/off/switch with main). On other skins pressing the PiP action keys one by one fast ends up with the PiP action being performed without the menu itself being displayed. Maybe it is a side effect, but it is very nice - it looks like “a key combination assigned action”, not a menu choice. Your skin adds the intermediate state, in which a PiP is positioned at its menu position and the empty menu template is displayed. It is for a very short time, still noticeable. The overall effect is like PiP “flickering”. Can live with this but it is not nice.
[*]Another one concerning "picture preview" on skin screens when PiP is active: the PiP is not "filtered out" and may obscure the "picture preview" if their positions overlap one another. My suggestion would be to move the PiP out of the display area while the skin element is being displayed. I have no idea if it is doable though…
[*]"Next event" info on "single event" view is fixed to the next event on current channel being viewed. It should be linked to the event next to event which information is being displayed.
[/list]
Regards.

[littlesat]

In 1 + 2 I do not get the issue - as doing the blue botton as PIG screen is a kind of taste.... and 3 I do not understand which screen you mean...

[macnuts]

1.: Just pointing this.
2.: Activate PiP. Move PiP so it occupies some of the screen area where the preview is also presented (By "preview" I mean the current channel content, part of the skin screens). Activate any of the skin screens with the preview. The preview is scaled, but the PiP is presented on it "as it is".
3.: Sorry not be clear enough... "Single event" view is displayed after you press the Info key while watching some channel. This view is used in other places as well. This view contains a field "Next". And this field displays static information, regardless which event information is displayed.
Here it goes by example:
A bouquet with the services: Serv_1, Serv_2, events for Serv_1: S1_Ev_Now, S1_Ev_Next, S1_Ev_NextNext... Service Serv_2 has corresponding events which names start with S2_
One is watching the S1_Ev_Now on Serv_1.
Press Info key. The S1_Ev_Now detailed information (from EPG) is displayed. You can observe the S1_Ev_Next as the next event. This is OK.
Press Right arrow. Now both event information and next are the same.
Exit EPG window. Press Down to open bouquet entries list.
Highlight the Serv_1, press Info, navigate to the S1_Ev_NextNext (by pressing Right arrow 2 times). The EPG is shown for S1_Ev_NextNext but the next event field shows S1_Ev_Next (should be S1_EV_NextNextNext in my opinion).
Like above, but for the Serv_2. Whichever event (S2_Ev_Now/Next/NextNext/...) information you are watching, the Next field states the S1_Ev_Next.

Regards.

Edited by Orzes72, 12 December 2011 - 19:06.

[macnuts]

Corrected example, as I had problems editing the existing one:

Here it goes by example:
A bouquet with the services: Serv_1, Serv_2, events for Serv_1: S1_Ev_Now, S1_Ev_Next, S1_Ev_NextNext... Service Serv_2 has corresponding events which names start with S2_
One is watching the S1_Ev_Now on Serv_1.
Press Info key. The S1_Ev_Now detailed information (from EPG) is displayed. You can observe the S1_Ev_Next as the next event. This is OK.
Press Right arrow. Now both event information and next are the same.
Exit EPG window. Press Down to open bouquet entries list.
Highlight the Serv_1, press Info, navigate to the S1_Ev_NextNext (by pressing Right arrow 2 times). The EPG is shown for S1_Ev_NextNext but the next event field shows S1_Ev_Next (should be S1_EV_NextNextNext in my opinion).
Like above, but for the Serv_2. Whichever event (S2_Ev_Now/Next/NextNext/...) information you are watching, the Next field states the S1_Ev_Next.

[littlesat]

I think regards the PIP that first including it to the blue addon screen is absurt... and not logically in E2... So this is the main cause why the skin misleads you with the PIP... and I still do not understand this: The preview is scaled, but the PiP is presented on it "as it is".???

The next info on the channel EPG needs more patches in python to solve it the way you want it...

[macnuts]

I think regards the PIP that first including it to the blue addon screen is absurt... and not logically in E2... So this is the main cause why the skin misleads you with the PIP...

OK, still I do not know another way to get the PiP working... But it is not that bad after all (the "fickering" I mean...)

and I still do not understand this: The preview is scaled, but the PiP is presented on it "as it is".???

Preview is scaled so whole screen fits the rectangle designated to display the preview (this part is clear I hope). The PiP is displayed exactly in the same place with the same dimensions when the skin screen is presented as it (PiP) is displayed when no skin element is displayed. Like in: 1. Blank screen. 1. Show preview. 2. Show PiP. 3. Show skin screen.

The next info on the channel EPG needs more patches in python to solve it the way you want it...

OK...

[Pr2]

Hi,

I don't know if it is skin or E2 related but here is the "bug":

- Watch channel #2 (or any other one)
- Set a timer to zap automatically to channel #8 (or any other one).
- Watch channel #6 (or any other one)
- Wait that the STB zap automatically to channel #8
- Press the left button, the STB will zap to channel #5 (so in fact it zap to channel #6 -1 = #5) when according to me it should zap to channel #7 (#8 -1)

Same bug apply with the 0 key to switch back to the previous channel, after the time zap it will zap to channel #2 and not channel #6 has expected since channel #6 was the last one before the timer zapping.

I use Cool TV Guide to schedule the timer zap, I don't know if this point matter or not.

Pr2

Edited by Pr2, 18 December 2011 - 16:32.

[Pike_Bishop]

Hi PLI Team,

here i have a little cosmetic problem with this skin you can see in the picture which i attached
it's on a CT ET9x00 Box

regards
Biki3

Attached Files

•  cutlist-editor.JPG   74.01KB   125 downloads

[littlesat]

Which screen/plugin???

[ims]

this is temporary problem with title versus text label...

I stoped adding text label therefore into next screens.

Edited by ims, 21 December 2011 - 19:34.

[Pike_Bishop]

Hi,

thanks for reply.

@littlesat

Which screen/plugin???

this screen is coming if i mark a record and then i press the menu button to select as example the cutlist-editor.
in the tuner settings i have the same problem -> i attached a picture to this.

@ims

this is temporary problem with title versus text label...

I stoped adding text label therefore into next screens.

ok.

regards
Biki3

Attached Files

•  tuner-einstellungen.jpg   52.33KB   79 downloads

Edited by Biki3, 22 December 2011 - 17:58.

[littlesat]

Fix from the next builds....

With the cutlist editor I do not get this issue...?? Please describe exactly how you get there...

Edited by littlesat, 22 December 2011 - 19:24.

[ims]

About Info (multiplex-blue, yellow) - it works on 800se

Can be switched into english before screenshots for better looking screens in skin ?

[Pike_Bishop]

Hi,

@littlesat,

Fix from the next builds....

thanks.

With the cutlist editor I do not get this issue...?? Please describe exactly how you get there...

it comes exactly in the screen if i marked a record and then i press the menu button.

@ims,

About Info (multiplex-blue, yellow) - it works on 800se

at ct et9x00 with lava skin it works also but with PLI-HD Skin it doesn't work.

Can be switched into english before screenshots for better looking screens in skin ?

yes ok , if i post again problems with PLI-HD Skin with pictures then i switch bevor to english language in menu.

regards
Biki3

[littlesat]

at ct et9x00 with lava skin it works also but with PLI-HD Skin it doesn't work.

Here with CT ET9x00 it works also??????