2041 replies to this topic

[WanWizard]

Ok. Don't have a problem with that, just thought i'd better report it .

[WanWizard]

This doesn't seem ok?

 

This is a channel for which streamrelay is activated.

Attached Files

•  screenshot_20240321211728.jpg   44.79KB   5 downloads
•  screenshot_20240321211716.jpg   89.66KB   5 downloads

[littlesat]

Could also be your userbouquet it not correct?

[Pr2]

I have just updated my Solo4K and I cannot reproduce your problem, so I also think of an error in your userbouquet file.

[DimitarCC]

This doesn't seem ok?

 

This is a channel for which streamrelay is activated.

 

 

Could also be your userbouquet it not correct?

 

 

I have just updated my Solo4K and I cannot reproduce your problem, so I also think of an error in your userbouquet file.

 

Yes i also not get that behavior....

[littlesat]

How did you activate stream relay?

[WanWizard]

In the channel menu. And I am 100% sure it is not in my bouquets.

 

I only had it with that one channel btw, can't reproduce it with others, so it could very well be it is one of the million race conditions in enigma (you can get it to crash simply by pressing keys fast enough).

[littlesat]

It looks more that there is something deviated in a userbouquet... so in the name somehow a 0part of the URL is added by accident..... The same happened to me also in the past while I was 'playing' with these bouquets... and also on the WWW there are userbouquets specially made for StreamRelay and there is a lot of rubish between them.... So you can better arrange normal bouquets and mark them that they need to use streamrelay via our menu option or add the references to the whitelist for streamrelay.

Edited by littlesat, 22 March 2024 - 15:31.

[WanWizard]

Again, there is NOTHING of the sort in my bouquets.

 

Even more, all my bouquets are "read-only", they get copied from another box every time I take it out of standby, overwriting any changes that might be made locally.

[kamaxx]

Good morning everyone ;

 

I wish Have a nice weekend

 

@DimitarCC,

 

I tried E2-DarkOS skin on openpli-9.0 but You know Its not compatible with stable image.

Is there any good news in near future for your skin works on stable image?

 

and I am looking forward to seeing new 9.1 image.

 

Greetings,

Edited by kamaxx, 24 March 2024 - 09:26.

[littlesat]

Once develop get’s stable it will happen… why not try develop?

Edited by littlesat, 24 March 2024 - 09:29.

[Tech]

The develop (=nightly) is also stable, but it can very occasionally happen that after an update you are faced with something that may not work, but it is usually fixed within an hour, it's our playground

If you can live with that, nothing will stop you from using development images.

[DimitarCC]

Good morning everyone ;

 

I wish Have a nice weekend

 

@DimitarCC,

 

I tried E2-DarkOS skin on openpli-9.0 but You know Its not compatible with stable image.

Is there any good news in near future for your skin works on stable image?

 

and I am looking forward to seeing new 9.1 image.

 

Greetings,

 

There is no chance the skin to work with 9.0 release. There are too many changes under the hood that can not be (not need to be) backported.

[40H3X]

@kamaxx I moved your question to https://forums.openp...on-development/ as it has nothing to do with this topic.

[WanWizard]

Again, there is NOTHING of the sort in my bouquets.

 

Even more, all my bouquets are "read-only", they get copied from another box every time I take it out of standby, overwriting any changes that might be made locally.

 

I think I may have found the issue.

 

If you have renamed a channel, it also writes the channel name to whitelist_streamrelay, so you get

1:0:1:1650:7E7:2:11A0000:0:0:0:
1:0:1:C78B:815:2:11A0000:0:0:0::ComedyCentral +1
1:0:1:C4C0:811:2:11A0000:0:0:0:

If I manually remote the name, the issue in the GUI is gone as well.

 

So it is not a skin issue, it looks like a streamrelay implementation issue.
 

[40H3X]

In noticed that in the Mountpoints management, there are no buttons there, so there should be Red=Close and Yellow=Delete mount and a Press OK to edit settings

[littlesat]

If you have renamed a channel, it also writes the channel name to whitelist_streamrelay, so you get

 

 

You see an URL and not something renamed on the user interface which shouldn't be there.... the whitelist only defines what is going via stream relay or not. It does not change what should be shown on the UI... that is all in the userbouquet...

 

But can you give me something more concreate like the bouquet as example and the whitelist?

Edited by littlesat, 26 March 2024 - 12:02.

[WanWizard]

There is nothing mysterious about it, the relevant bouquet entry is

#SERVICE 1:0:1:C78B:815:2:11A0000:0:0:0::ComedyCentral +1
#DESCRIPTION ComedyCentral +1

and when I press menu, and select "play via streamrelay", the whitelist_streamrelay file contains the entire service string, not just the service reference:

1:0:1:C78B:815:2:11A0000:0:0:0::ComedyCentral +1

and what is and is not displayed, I don't know, I just reported what I have seen, including screenshot.
 

To double check, I manually imported my bouquets again to prove to you it is not my bouquets, but the problem doesn't go away. It goes away when I fix the contents of whitelist_streamrelay.

 

And it is not only DarkOS, the standard skin does the same:

 

 

 

Attached Files

•  screenshot_20240326121106.jpg   113.98KB   2 downloads

[littlesat]

Now I get it and I fully understand why it presented like this....

 

Actually it is a kind of design flow far back by those DMM engineers.... 

 

That renaming stuff is also strange coding back that time... you add : then the name + you can add it below it in a different 'field'.

 

Needs a ton of work-a-rounds...

 

1st. we do not need to whitelist the renaming stuff

2nd when we check for the service reference we should not include the renaming stuff

3rd when we add the URL then we need to put it between the renaming stuff and the reference

Edited by littlesat, 26 March 2024 - 13:52.

[WanWizard]

That renaming stuff is also strange coding back that time... you add : then the name + you can add it below it in a different 'field'.

 

This is what the menu option "rename channel" creates.