Auch neu im ServiceInfo Converter

Dre und ich haben im ServiceInfo Converter folgende Skin Optionen hinzugefügt:

    Information for skin developers for TPDATA:
    ===================================

    Format: TpData,<information>

    Possible values for <information>:
    =====================================================================================================
    | information           | example values                 |    Sat     | Cable | Terrestrial | Code  |
    =====================================================================================================
    | tuner_type            | Satellite, Cable, Terrestrial  |     X      |   X   |      X      |  %T   |
    | tuner_state           | IDLE, TUNING, FAILED           |     X      |   X   |      X      |       |
    | modulation            | QAM256                         |     X      |   X   |             |  %M   |
    | inversion             | Auto, On, Off                  |     X      |   X   |      X      |  %I   |
    | fec_inner             | Auto, 2/3, 5/6                 |     X      |   X   |      X (T2) |  %F   |
    | frequency             | 11111.75 MHz                   |     X      |   X   |      X      |  %FR  |
    | orbital_position      | Name of Satellite              |     X      |       |             |  %O   |
    | polarization          | Horizontal                     |     X      |       |             |  %P   |
    | polarization (short)  | H                              |     X      |       |             |  %PS  |
    | system                | DVB-S2                         |     X      |       |      X      |  %S   |
    | symbol_rate           | 22000                          |     X      |   X   |             |  %SR  |
    | rolloff               | 0.35                           |     X (S2) |       |             |  %R   |
    | pilot                 | Auto, On, Off                  |     X (S2) |       |             |  %p   |
    | is_id                 | ?                              |     X (S2) |       |             |  %i   |
    | pls_mode              | Root, Gold, Combo              |     X (S2) |       |             |       |
    | pls_code              | ?                              |     X (S2) |       |             |       |
    | bandwidth             | 8 Mhz, Auto                    |            |       |      X      |  %B   |
    | constellation         | QPSK, QAM16                    |            |       |      X      |  %C   |
    | transmission_mode     | 2k, 4k, 8k                     |            |       |      X      |  %TM  |
    | guard_interval        | 1/32, 1/16                     |            |       |      X      |  %G   |
    | code_rate_lp          | 1/2, 2/3                       |            |       |      X (T)  |  %L   |
    | code_rate_hp          | 1/2, 2/3                       |            |       |      X (T)  |  %H   |
    | hierarchy_information | 1, 2, 4                        |            |       |      X (T)  |  %HI  |
    | plp_id                | ?                              |            |       |      X (T2) |       |
    =====================================================================================================

    Information for skin developers for MULTI:
    ==================================

    Format: Multi,%T %m

    Possible codes see table above. Each code must be separated by a space. Do NOT add quotes.
    """

Das Ziel war den ServiceName2 Converter zu ersetzen. Dieser sollte nicht mehr verwendet werden.

Beispiel für eine kombinierte Zeile:

<widget backgroundColor="bg2" font="Regular; 30" halign="left" noWrap="1" position="1360,820" render="Label" size="520,40" source="session.CurrentService" transparent="1" valign="center" foregroundColor="darkevent">
  <convert type="ServiceInfo">Multi,%FR %PS %SR %F %M</convert>
</widget>

oder für einzelne Einträge:

<widget backgroundColor="bg2" font="Regular; 30" halign="left" noWrap="1" position="1175,820" render="Label" size="180,40" source="session.CurrentService" transparent="1" valign="center" foregroundColor="orange">
  <convert type="ServiceInfo">TpData,orbital_position</convert>
</widget>

Danke dre

I've made some modifications to the "EventList" converter. Could you give it a try and let me know what you think?!

Soll jetzt jeder den Source-Code selbst studieren, um zu wissen, was du da modifiziert hast ?

Erkläre es mit widget-Code und Screenshots, so dass jeder sofort sieht, was du da modifiziert hast und wozu.

Sonst wirst du vermutlich nicht viele Rückmeldungen bekommen.

Everything is explained in the code for developers and is currently being tested.

Once testing is complete and everything is working properly, I'll add a clear explanation with screenshots for users.

@Andro1

I'm not a developer, but I tested the modified code for a change!

- Channels with out‑of‑sequence EPG timings didn’t show up in the upcoming events list before, after the modification, they now show up correctly.

- Also, the duration was shown only in minutes, now it's shown in both hours and minutes.

Well done!

Max11

It seems that my changes are working well with your small box.

Thanks for your feedback!

Here's my feedback:

srvRef = eServiceReference(ref.toString())

No added value compared to Dr.Best's implementation.

        epgcache = self.epgcache
        getEvent = self.getEventTuple

You just assign a function/instance to a variable with no added value.

        max_offset = self.max_search_offset  # Step size for searching
        max_limit = self.max_search_limit    # Maximum total search range

No added value to assign to variable known to this function only.

while len(contentList) < self.eventcount and total_offset < max_limit:

Just a simple example: Skinner sets event count to 10 and maxSearchOffset to 1 hour. You have 2 events within the timespan.

len(contentlist) will never reach 10 and you'll loop forever. As you have two limits introduced (quantity and time), you have to be more careful.

Either you have to ensure that only one of the two can be provided or you must cover the cases properly.

                    next_event = epgcache.lookupEventTime(srvRef, next_time + offset)
                    if next_event:
                        found_event = next_event
                        break

why do you assign next_event to found_event? you can work with next_event the whole time.

And last one: I'm not a fan of try/except. There are cases where it makes sense but here I don't see why it should be required.

Thanks for your feedback! I've revised the code based on your comments:

Removed unnecessary assignments.

Fixed the loop issue by adding no_event_counter to exit when no more events are found.

Removed try-except and enhanced explicit checks for error cases.

The code is now simpler.

After testing the codes EventList Converter and EventList Converter_2, I reused srvRef as follows:

• Reusing "srvRef" improves memory usage and speed for intensive lookups

  By creating the service reference a single time and reusing it, you minimize per-iteration memory allocations and benefit from better cache locality, leading to faster, more memory-efficient EPG searches.

Final Changes:

• Improved Performance: Enhanced event searching using Coarse and Fine steps to reduce delays and boost performance.

• Prevented Duplicates: Tracked event IDs to ensure no duplicates occur.

• Avoided Infinite Loops: Added a break to stop the loop when no further events are detected.
  

• Added Clear Comments: Included code comments to explain the logic and highlight the changes made.

More optimization!

less information ...

Changes Added to Version 5 (Compared to Version 4)

1. Addition of no_event_counter Variable:
   • The variable no_event_counter was added to track the number of consecutive failed attempts to find an event.
   • Purpose: To monitor how many times the search fails to find an event within the specified time range.
2. Addition of max_no_event_attempts Variable:
   • The variable max_no_event_attempts (default value: 10) was added to set the maximum number of failed attempts before stopping the search.
   • Purpose: To prevent infinite searching in cases of large gaps in the event schedule.
3. Modified Behavior When No Event Is Found:
   • In version 4, the search stopped immediately upon failure using a break statement.
   • In version 5, the behavior is enhanced:
     • total_offset is increased by self.max_search_offset (default: 4 hours) to advance to the next time period.
     • no_event_counter is incremented by one.
     • If no_event_counter reaches max_no_event_attempts, the loop exits using break.
4. Resetting no_event_counter:
   • When an event is found, no_event_counter is reset to zero.
   • Purpose: To ensure that previous failed attempts do not affect subsequent searches, enabling fresh attempts.
5. Improved Handling of Event Schedule Gaps:
   • These changes enhance the effectiveness of the event search logic, particularly for channels with periods of no events (e.g., downtime or gaps).
   • The search now spans multiple time periods (up to 10 attempts by default) instead of stopping at the first failure, improving performance for sparse event schedules.

Is it possible to fix Arabic letters in aio (All IN ONE)?