73 replies to this topic

[Dimitrij]

-fix for true parsing for display it in OpenWebIf

-update transtreamproxy

Attached Files

•  enigma2-plugin-systemplugins-advancedtranscodingsetup_openpli8.x_armv7ahf-vfp.ipk   60.24KB   27 downloads

[Erik Slagter]

How will we communicate that this is only required for Gigablue and Qviart?

[Dimitrij]

sync py3

Attached Files

•  enigma2-plugin-systemplugins-advancedtranscodingsetup_openpli8.x.develop_armv7ahf-vfp.ipk   60.68KB   14 downloads

[luisteraar]

Tnx works great on openpli develop.

Is it possible to add it to the feed from 

openpli to replace the bagger transcode

[Tech]

Well, that sounds really great to hear OpenPLi created ‘bagger’ code, if I was the developer of this plugin I wouldn’t take any effort in fixing issues anymore…..

[littlesat]

Why not just offering a merge request to our ‘bagger’ code…

Edited by littlesat, 23 July 2023 - 08:50.

[Dimitrij]

This plugin use same as TransCodingSetup

+

filestreamproxy

 

 

And all necessary parameter for streamproxy available

Edited by Dimitrij, 23 July 2023 - 11:04.

[luisteraar]

I'am not able now to port it to openpli.

Mij openpli build enviroment is empty and am now

develop a app for samsung tizen tv player for enigma.

 

It is not difficult to rewrite the oe-aliance bb file to openpli

and fork the package to a openpli github account

[XRayhTec]

Well, that sounds really great to hear OpenPLi created ‘bagger’ code, if I was the developer of this plugin I wouldn’t take any effort in fixing issues
anymore…..

Because of the opinion of 1 person?

[luisteraar]

stick to the truth.
i just said transcode doesn't work on gigablue .
If it doesn't work, it's crap
oe-aliance has a good working .
my question was can it get into the feed.

No more and no less.

[Tech]

Well, that sounds really great to hear OpenPLi created ‘bagger’ code, if I was the developer of this plugin I wouldn’t take any effort in fixing issues
anymore…..

Because of the opinion of 1 person?

No offcoarse not but in my opinion it is not polite to the creator/maintainer…..

[luisteraar]

The transcode util that good works is a verry old

one from 8 years ago it use the special transcode

io controls from the broadcom arm7 soc.

I see no problem to add it to the openpli feed.

[WanWizard]

It is probably better to figure out what is different between Gigablue's implementation and the old VU+ implementation, and deal with that.

 

It would we a big step backwards to reintroduce this old proxy setup, after we've removed it from all other models...

[luisteraar]

I do not have all sources on mij system at the moment .

Can you give me a link to the new transcode c(++) file .

I think it is a vergotten bit in the bcm i/o control .

Then i wil compare it.

[WanWizard]

It is integrated in the standard streamserver: https://github.com/O...treamserver.cpp

 

Erik can probably assist if you have questions, as he's worked on it.

[luisteraar]

tnx i found where to look

encoderFd = eEncoder::getInstance()->allocateEncoder(serviceref, buffersize, bitrate, width, height, framerate, !!interlaced, aspectratio,
vcodec, acodec);

[luisteraar]

@Dimitrij can you give me te correct link to the

working transcode for GB ?

 

In the mirrors can i only found the old proxy for vu+ with

 

std::string path = "/dev/bcm_enc" + Util::ultostr(encoder_id);

fd = ::open(path.c_str(), O_RDWR, 0);

 

 

the GB don't have bcm_enc only bcm_enc0

 

it's possible that a dev wil create at runtime of de proxy with file append encoder_id 

 

In that case the problem in openpli is that it use a fix device name /dev/bcm0

[luisteraar]

write error

 

in that case the problem in openpli is that it use a fix device name /dev/bcm0

is

in that case the problem in openpli is that it use a fix device name /dev/bcm_enc0

[luisteraar]

I was to quick in openpli

 

snprintf(filename, sizeof(filename), "/dev/%s%d", bcm_encoder ? "bcm_enc" : "encoder", encoder_index);

[Dimitrij]

https://github.com/O...encoder.cpp#L39