117 replies to this topic

[WanWizard]

My sentiments exactly.

 

Yes, it is initially quite a bit of work, but once the foundations are laid, the possibilities are endless.

 

You could for example have multiple boxes share (parts of) the same database, no more internal syncing of boquet files (fallback import or manually using tools) and EPG (fallback import or import on multiple boxes).

 

It is a job than can (and imho should) be shared between multiple developers, once the decision on design has been made, as there are lots of unrelated tasks than can be done in parallel (settings, bouquets, EPG, database engine, etc).

[DimitarCC]

 

Properly fixing the enigma storage (lamedb) will result to incompatibility to every service editor tools that exists. That's why its better to not touch it imho.

 

That is the age-old excuse, and not really the case.

 

How do all external editors work: they ftp files in, and then call enigma using the webif to force a reload.

 

If instead of memory, E2 would have a proper database for storage, this process could remain the same, but the enigma call could be rewritten from "reload" to "import external files".

 

All that is needed for editors to work like normal is an additional enigma call, to export the database data to lamedb / bouquetfiles, so they have the current version to work with.

 

Not that complex (at least a lot less complex than implementing the database).

 

And that is off course only if no API to this database is created, and if the author of the editors are not willing to implement that API (history has shown that they have followed developments).

 

 

The problem is that these tools have a UI that represents the data stored in lamedb in user friendly way. That will stop working if the tools are not adapted to the new entries. That is what going to be broken.

You can not force the developers of that tools to adapt...And some of them are even not supported anymore...

 

So in my opinion its better to have a "lame" solution with keeping the current compatibility instead to have no solution at all or to break existing setting editors...

[DimitarCC]

Can you describe the format of the lines, what does each value represent?

 

That is not easy task to be described but i will try ....

1:0:19:403:3FA:1:1:0:0:0|1091|1096|-1|-1|-1|-1|-1|-1|71762177
-----------1------------|-2 -|--3-|-4|-5|-6|-7|-8|-9|---10---

1 - Service reference

2 - video pid

3 - mpeg audio pid

4 - ac3 audio pid

5 - ac4 audio pid

6 - ddp pid

7 - aac-he audio pid

8 - aac audio pid

9 - dra audio pid

10 - composite subtitles pid this is special composite pid that contains all subtitle parameters

[WanWizard]

The problem is that these tools have a UI that represents the data stored in lamedb in user friendly way. That will stop working if the tools are not adapted to the new entries. That is what going to be broken.
You can not force the developers of that tools to adapt...And some of them are even not supported anymore...

 

That's why I said that if the tools can't/won't support the new API, E2 needs a function to export the database to bouquet files / lamedb, so it can be edited externally.

 

Not too complicated to make.
 

imho the benefits by far outway the drawbacks. But it seems, as always, there is always time to hack in more workarounds, but never time to do things properly...

[DimitarCC]

 

Not too complicated to make.

 

 

Not till you start doing it...I am a developer more than 15 years and every time i start a new task i figure out is not what was initially expected. Thats why usually there is reserved always a spare time. But event that is not enough in some cases.

When look from the side it always looks easy but when start developing it is not like that.

Such a convertors that you suggesting is not easy thing...There are underwater stones in this...Developing such requires a lot of testing and adapting...

If a developer/s can be found that have that time OK but i doubt you can find them. Nowdays we live in a busy environment that the time shared for opensource things is not much since people have to be able to eat so they prefer their regular job.

So there is not so easy anyway...

[littlesat]

When you define a good sql database... and it is correctly and smart formatted... you do not need these editors anymore....And other tools based on a real standard will 'popup'

All those available settings editors for example have a slow response due to the current 'hacky/lame' design.

And also due to all the hacks that teams did add to the whole stuff.... adapting (=making it really good) is even more a hell of a job...

Edited by littlesat, 8 May 2024 - 14:19.

[Stan]

@WanWizard

 

Why not set up a survey for devs and contributors about the future of Enigma? (what would they prefer)

a ) stay on Enigma2 with current situation (hacks are rejected for the sake of stability and code simplicity)

b ) stay on Enigma2 but usefull hacks with no negative impact are accepted

c ) commit to redesign a completely new Enigma3

Edited by Stan, 8 May 2024 - 15:10.

[WanWizard]

@Stan,

 

Don't need to, I already now the answer, as I've been fighting this windmill for many years now .

 

The anwers are always the same: complex, time consuming, compatibility. But at the same time, there seems to be always time to add more complexity.

 

Big problem is that virtually all developers are "einzelgangers", they work alone, don't discuss what their doing, don't work with a plan (or planning) or towards a common goal, and throw what they make over the fence when they're done.

 

This makes running a project as a team impossible, no appetite for long(er) running multi-disciplinary work. Which is why E2 will sadly die out, as it basically hasn't improved much functionally since it was concieved almost 20 years ago...

 

This is not OpenPLi specific, all others have the same problem.

 

Which also leads to enormous waste of development time, from making sure everything stays compatible cross-image, to constantly chasing each others changes to maintain compatibility, often reinventing wheels or redoing work.

 

If only everyone could put their ego's aside and pull together to design and build the next generation software...

To quote John Lennon: "You may say I'm a dreamer ... "

[Stan]

Something is not quite right yet. Selecting a subtitle or audio track now causes a green screen:

[eDVBRecordFileThread] wait: aio_return returned failure: Interrupted system call
Traceback (most recent call last):
  File "/usr/lib/enigma2/python/Components/ActionMap.py", line 77, in action
  File "/usr/lib/enigma2/python/Components/ActionMap.py", line 57, in action
  File "/usr/lib/enigma2/python/Screens/AudioSelection.py", line 394, in keyOk
  File "/usr/lib/enigma2/python/Screens/AudioSelection.py", line 293, in changeAudio
NameError: name 'ref' is not defined
[ePyObject] (CallObject(<bound method NumberActionMap.action of <Components.ActionMap.NumberActionMap object at 0xb1977d60>>,('SetupActions', 'ok')) failed)

Edited by Stan, 9 May 2024 - 10:41.

[DimitarCC]

indeed...Seems the merge didnt go well....

Fixed with https://github.com/O...igma2/pull/3971

 

For those that cant wait for next build use the attached file.

Attached Files

•  AudioSelection.py   20.4KB   1 downloads

Edited by DimitarCC, 9 May 2024 - 10:57.

[Stan]

Now I am getting this:

Traceback (most recent call last):
  File "/usr/lib/enigma2/python/Components/ActionMap.py", line 77, in action
  File "/usr/lib/enigma2/python/Components/ActionMap.py", line 57, in action
  File "/usr/lib/enigma2/python/Screens/AudioSelection.py", line 397, in keyOk
    self.changeAudio(cur[0])
  File "/usr/lib/enigma2/python/Screens/AudioSelection.py", line 293, in changeAudio
    ref = ref and eServiceReference(ref)
  File "/usr/lib/enigma2/python/enigma.py", line 283, in __init__
TypeError: in method 'new_eServiceReference', argument 1 of type 'std::string const &'
[ePyObject] (CallObject(<bound method NumberActionMap.action of <Components.ActionMap.NumberActionMap object at 0xb1983fa0>>,('SetupActions', 'ok')) failed)

 

[DimitarCC]

hmmm try with this (attached)

 

Attached Files

•  AudioSelection.py   20.42KB   2 downloads

[Stan]

It does not crash any more.

 

I have now tested with a streamrelay channel. It seems to remember the selected audio track, but it does not save it. There is no file config_av.

Edited by Stan, 9 May 2024 - 11:35.

[DimitarCC]

And if you restart enigma is it forgotten?

[Stan]

Exactly.

 

Normally, settings should be written to file when Enigma stops, right?

Edited by Stan, 9 May 2024 - 11:45.

[DimitarCC]

Hmmm it works on my side....interesting...

[DimitarCC]

It should be file created when you change the audio or subtitle track...

[Stan]

Maybe you should install a clean nightly build and test it yourself...

[DimitarCC]

My testing box with PLi have no access to stream relay services...
Testing it on my other box it works but that box is with openvix...
Maybe i can test iptv service...

Edited by DimitarCC, 9 May 2024 - 11:55.

[DimitarCC]

So i have tested with iptv streams and it is successfully generates config_av and all is there.

So it must be SR related or something on your side.

Edited by DimitarCC, 9 May 2024 - 16:55.