TNAP-7 Image Discussion

It's the same for me, except the top half of the TNAP7 icon also shows up.
I also tried it with the Cobalt skin—it's the same...
 

Attachments

  • Screenshot 2026-11-16 14-56-05.webp
    Screenshot 2026-11-16 14-56-05.webp
    50.2 KB · Views: 7
I just noticed that on the MIO4K Edition, the DAB+ plugin isn't working properly—the audio is choppy.
Whereas with the Ustym 4K Pro, it works perfectly (obviously with TNAP7, and also TNAP6.1 on the MIO4K Edition).
I don't know who to contact—you or pantasat (I'm sending this to both of you).
Here's a very short recording to illustrate what I mean, along with all the logs I've found.
 

Attachments

Contact pantasat who is the author of the plugin. We cannot have two cooks in the kitchen! If pantasat points to a specific image problem with TNAP where it works on other images but not TNAP then I will try to fix it. Thanks.
 
Hello, this is the TNAP-7-dreamone-20261114_mmc image you sent for the Dreambox One.
Could you also send the same image for the Dreambox Two? I have a Dreambox Two.
Is that possible?
 
Hello, this is the TNAP-7-dreamone-20261114_mmc image you sent for the Dreambox One.
Could you also send the same image for the Dreambox Two? I have a Dreambox Two.
Is that possible?
The 4:2:2 files are customized for dreamone. I have no idea what would happen if I tried to add the dreamtwo. I do not have a dreamtwo and do not want to add something without knowing if it works. Then if there are dreamtwo problems or issues, how do I fix them?
This is why a 4:2:2 dreamtwo image does not exist in TNAP. Thanks
 
Hello, to put it plainly, how can we install the software on a working OpenPLI image? How can we install the TNAP plugin files? How can we install the IPK plugins on the OpenPLI image?
I currently have a working OpenPLI image. If you don’t provide an image, I’ll test the TNAP installations on OpenPLI myself. I’ll find a way to test this. I’ll try to create an image that isn’t currently available. Best regards.
 
Let me give you one more piece of information: Your access from Turkey is already blocked. Unfortunately, the usual download method doesn't work.
Do you have any idea what kind of image I'm dealing with?
Best regards
 
Let me give you one more piece of information: Your access from Turkey is already blocked. Unfortunately, the usual download method doesn't work.
Do you have any idea what kind of image I'm dealing with?
Best regards
The 4:2:2 decoder core has nine C++ source/header files, totaling approximately 3,439 lines. The complete system also includes Enigma2 integration patches, FFmpeg optimizations, driver and kernel changes, recovery logic, settings, channel labels, and tests. Those supporting pieces matter when porting it.

For another distro on DreamOne, we would need to:
Adapt the Enigma2 hooks to its source version.
Integrate compatible FFmpeg libraries and our optimizations.
Match its kernel, frame-injection driver, and audio/clock interfaces.
Test live playback, recordings, timeshift, channel changes, deinterlacing, and audio synchronization.

That is a practical port. Supporting different receiver hardware could require a new video-output backend—the decoder alone cannot provide hardware frame injection.


DreamTwo is a reasonable next target. Both machine definitions use the common AArch64/meson64 configuration. However, our important changes currently use :dreamone overrides, so they will not automatically apply to DreamTwo

May I suggest asking OpenATV if they are interested in adding 4:2:2 to their dreamone dreamtwo image? That sir would be the best way to get a 4:2:2 image for the dreamtwo. OpenATV has more resources and test receivers than I do. The worst they can say is "No". Thanks
 
If possible, just send me the IPK plugins you used with the TNAP-7-dreamone-20261114_mmc image—that’s all I need.
Here’s what I see on this system:

TNAPATSC3
TNAPHelp
TNAPNowPlaying
TNAPVideoRecovery
WireGuardTNAP

If there are any other changes, these are the ones I see in the image.
 
That is what you do not understand or what we are not communicating. The 4:2:2 is built into the image in a custom way. If it were as simple as a 4:2:2 plugin, I would have posted it! C++ files and other edits are needed. Lots of other edits and overrides are needed.
 
There is no ready-to-use image for the device.
Since there is no image, it's of no use to us at all.
That's my understanding of the situation.
Goodbye, and best regards.
 
Back
Top