You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I've purchased an Amiko Viper Single which is based on the Hisilicon 3716MV410. From what I've found online, this is a relatively new and pretty low-end chip that has not yet been polished to work fine with Enigma2. (If it's even possible)
I've tried two images, and both had these issues, which suggests that these are driver related problems, but I wanted to highlight them, as there are very little information about regarding this online.
Recording of encrypted channels starts scrambled
Either a timed recording or a live recording on the box both have a small bit of encrypted segment at the very beginning of them. It's usually around 1 to 2 seconds long, but after that, the recording continues without an error. Is this something that can be fixed in the image by adding a bit of delay to the recording somehow?
Tuner locks up after channel switches via streaming
This issue was reported before at #2197 , but it was marked as solved, even though it still persists in the latest images. I've tried using SatPI and minisatip as a workaround hoping that it would not cause kernel errors that way, but it ended up doing that unfortunately. I've attached a log below for further information.
Hi,
I've purchased an Amiko Viper Single which is based on the Hisilicon 3716MV410. From what I've found online, this is a relatively new and pretty low-end chip that has not yet been polished to work fine with Enigma2. (If it's even possible)
I've tried two images, and both had these issues, which suggests that these are driver related problems, but I wanted to highlight them, as there are very little information about regarding this online.
Either a timed recording or a live recording on the box both have a small bit of encrypted segment at the very beginning of them. It's usually around 1 to 2 seconds long, but after that, the recording continues without an error. Is this something that can be fixed in the image by adding a bit of delay to the recording somehow?
https://www.satellites.co.uk/forums/threads/hisilicon-based-receivers-bug.178178/
This issue was reported before at #2197 , but it was marked as solved, even though it still persists in the latest images. I've tried using SatPI and minisatip as a workaround hoping that it would not cause kernel errors that way, but it ended up doing that unfortunately. I've attached a log below for further information.
messages.log
The text was updated successfully, but these errors were encountered: