sound ac3+ not working on VU+4K
please see setup
could you make/createted option for AC+3 please
That is actually a bug in Vu+ drivers.
If you go to another AC3+ channel, then back again I think you will get audio
sound ac3+ not working on VU+4K
please see setup
could you make/createted option for AC+3 please
That is actually a bug in Vu+ drivers.
If you go to another AC3+ channel, then back again I think you will get audio
Trio 4K Pro, has Bluetooth remote and 1200mb's Wi-Fi, otherwise it's pretty much the same.
If you don't pair the BT, then the remote works as a normal IR remote.
This thread is now open again. Regards.
make ya mind up lol
And does the remote already work for them in bluetooth mode ? Because it didn't work for them and they only promised that it would work.
BT remote works fine
The Trio 4K pro has faster wi-fi and a BT remote.
Otherwise not alot between them.
They are pretty much the same box, except octagon has option of twin tuner and also comes with built in wi-fi.
Trio is also discontinued now and replaced with the Trio 4K Pro
It is also in OpenAtv 7.3 now
Then the image doesn't have the changes in it
Did you restart Enigma2 after adding the whitelist ?
but the result is the same as in whitelist_streamrelay, that is, the namespace is C00000
It is still not clear to me exactly what is wrong and what needs to be changed or what is fake...
So again I ask what should be changed in oscam-emu if everything works fine?
If you don't use a dummy namespace with an SR channel, then oscam never gets the request, thus it doesn't even attempt to decode anything.
It's the namespace that is faked
It is time to resolve the reason why the modified service reference work a round is mandatory. The oscam-emu needs a change so this is not mandatory anymore.
The oscam-emu code is public
You're right I dont really... But I dont think you do either.
Ok
Display MoreBefore those changes iCAM channels didnt clear.
I dont know if it was specifically that patch, but it was around a year or so ago.
My point is its not OScam or Ncams fault that e2 users require that stream relay crap.
Other dvb-s software made changes to support iCAM without issue.
With e2 being able to descramble iCAM using a custom oscam binary with streamrelay proves that the hardware and drivers are capable.
It seems to me that the core e2 libraries need to be updated to support iCAM since it breaks the dvb standard.
Clearly you have no idea what you are talking about, so maybe stop posting rubbish and causing confusion ?
The patch above, as I said was purely to allow cards to reply to ecm requests for icam channels, as before that any request for an icam channel was blocked, so the card never recevied the info, thus it could not reply.
E2 requires the drivers to support icam, without that the only current option is to patch ffdecsa in oscam with icam, so that it can be used by Stream Relay. As the box drivers don't support icam, enigma2 can not pass the info directly to oscam, like it does with CSA and DES encrypted channels.
Enigma2 does not use libdvbcsa by default, it can be implemented when using minisatip, but as already said above, what is the point there is no gain as it will still end up being converted to a stream internally as the box drivers still won't support icam.
iCAM support was added in or around here: https://trac.streamboard.tv/oscam/changeset/11712
Its not just TVHeadend that was patched to support iCAM, other software has been too... Just not e2.
lol that was just to allow the cards to reply to an icam request
And what is wrong with it?
No idea i've never seen one.
But we don't have samples of those boxes and we are not looking to add support for more older boxes that we don't own.
Display Moreexactly
BlackHole 9.8 build by fairbird for DM920 it based openpli source
Okay then ask fairbird Im sure he will be able to help.
Display MoreBlackhole was based on Vu+ git (now dead), OpenBh is based on oe-a git
i think he talk about Blackhole build by fairbird for dream box it based opli
https://github.com/fairbird/openpli-dreambox-oe-core
not original Blackhole for vu stb
exactly
BlackHole 9.8 build by fairbird for DM920 it based openpli source
My BlackHole Image for Dreambox:
1- The image was built 40% of the image construction was based on openpli sources regarding enigma2 + meta-openpli
2- The image was built 30% from OpenATV sources regarding enigma2 + some meta files from oe-alliance.
3- The image was built with 10% of patches taken from the BlackPole team’s source before it turned into BlackHole + Only Panel from BlackHole image.
4- The image was built with 20% of codes from my side to make enigma2 compatible with all dreambox devices.
About My source code (Just for Dreambox). And a lot of features in e2 can not be find in BlackHole (VU+) Not openBH. Even openpli image also.
(source mixed between openATV + OpenPLI enigma2 features)
https://github.com/fairbird/openpli-dreambox-oe-core
Well if it's only 10% Blackpole / Blackhole, then it really shouldn't be called Blackhole should it
Will Amiko Viper 4K get official 5.3?
Unlikely
Can wE know what the new feature is in 6.4.009.001 ?
It is the same image as 6.4.008