3 replies to this topic

[mort1234]

Originally posted in the release candidate 8.0 thread. But the problem is still there, so I will post here again:
https://forums.openp...dpost&p=1289026

Streamproxy doesn't recognize the Vu+ Duo 4K SE:

 

Checking manufacturer/model: VU+/Ultimo4k

Checking id: /proc/stb/info/chipset = 7444s

Checking id: /proc/stb/info/vumodel = ultimo4k

Checking manufacturer/model: VU+/Duo4k

Checking id: /proc/stb/info/chipset = 7278

Checking manufacturer/model: GigaBlue/UE 4k

....

Checking manufacturer/model: generic/non-transcoding settopbox

model identified as: generic non-transcoding settopbox (unknown)

 

These are the values for the Duo 4K SE box:

/proc/stb/info/chipset = 7444s

/proc/stb/info/vumodel = duo4kse

 

Hope this can be fixed :-)

 

[Erik Slagter]

Transcoding is in the process of being included in enigma itself (just like transcoding for xtrend/hd digital/zgemma models already was). The duo4kse is the model I am primarily developing on, so that will receive plenty of attention from me  Last time I checked it worked.

 

If you're using an app to make use of transcodig you can simply choose "xtrend style" transconding and/or use port 8001 instead of 8002. If you're using the OWIF (OpenWebInterFace) you will have to edit the m8u file you receive, to point to poort 8001 instead of 8002. This is planned to be "fixed" with the next release where we will update the OWIF for this and remove the streamproxy.

Edited by Erik Slagter, 8 January 2021 - 13:53.

[mort1234]

I have checked and you are right, it works on port 8001. Great to hear you are actively working to implement directly in enigma. 

I can't get the transcoding of recorded files to work though. Is it one of those features that is still under development?

 

I must say that Openpli 8.0 is very stable on Duo 4K SE.

[Erik Slagter]

I have been working on this for a few months now, it's quite hard because both enigma is not designed for the way the Broadcom encoder needs to be operated and because I have to guess a lot, we don't have any official documentation. What works for one manufacturer may break for another.

 

File transcoding had been working before but I can confirm it's broken now. Or, actually it was broken, I've fixed it today. In develop images it should be working again. Most of the time, I must say. Every now and time it just doesn't work, the encoder refuses to start. Then if you start again, it will work. Also before the first picture is shown, it takes a very long time, it can take up to 30 seconds. I don't know why that is, because the encoder is being fed with valid data immediately, I don't know why the encoder starts giving picture after so long. This is probably as good as it will get.

 

I am still working on various things, a.o.

- transcoding on VU+ pre-ARM models, which don't have the "encoder" proc entry, they are now not recognised as being able to transcode

- transcoding on GB models, where we now get a driver crash (similarly as what happens on streamproxy, starting from a major driver upgrade some time ago). I am not sure if I will be able to get that to work, but on the "transtreamproxy" (from VU+) it seems to work, so I will try.

Edited by Erik Slagter, 11 January 2021 - 19:38.