Hi everyone,
I would like to share M3U Player E2, a standalone Enigma2 plugin for IPTV playlists supplied through an HTTP/HTTPS M3U URL.
Main features:
- Channel and mov*ie categories, with persistent category ordering.
- Search across the loaded playlist, Favorites, recently watched items and mov*ie resume.
- CH+/CH- channel switching and return to the previous IPTV channel.
- Live playback using Enigma2 (4097) or optional exteplayer3 (5002); mov*ies use 4097.
- mov*ie pause/resume, 10-second and 5-minute jumps, and repeated forward jumps while holding the remote button.
- Available audio and subtitle track selection, plus a volume indicator.
- Grid EPG, now/next information, mov*ie details, channel logos and posters when supplied by the source.
- Stream resolution and receiver CPU/RAM display.
- Romanian, English and German interface, with Automatic, HD and Full HD layout settings.
Separate packages are included for OpenPLi 9.1, OpenATV 8.0.1 and OpenBH 6.0.004. Python 3.9 or newer and Twisted are required. These packages are not for Python 2.7 images.
Development and receiver testing were carried out on a Vu+ Solo 4K. The plugin is stable in my tested configuration. OpenBH is provided for testing; other receivers and image builds need individual verification. A total of 274 local automated tests passed using simulated Enigma2 components.
The download contains the full English installation guide, source code, MIT license and an optional 5002 installer. The 5002 installer obtains ServiceApp and exteplayer3 from the receiver's configured image feeds; universal player binaries are not bundled.
No IPTV subscription, personal playlist, account credentials or receiver configuration is included. Supply your own playlist URL. EPG, seeking, subtitles and artwork depend on the source and playback engine.
Please extract the outer archive, choose the package for your running image and follow HOWTO_INSTALL_EN.txt. Install only one image-specific package on each receiver.
For bug reports, please include receiver model, image/build date, plugin version, playback engine, skin/OSD resolution and the action that caused the issue. Redact private URLs and credentials before posting logs.
Reply With Quote