Hi.
Sorry, but this is a stupid question.
You provided very little information. You could have at least stated what you were trying to do, how you did it or what you did before before it still worked correctly for you.
In addition, this error message can represent many different errors in Oscam.
Hi.
Simply use the unofficial online shell-script from the creators of OpenATV. It installs the necessary feed according to the detection of which Enigma2 core you use in ATV and according to the detected architecture.
Page 16 / Post #312:
I don't know this Qviart Dual 4K either, but according to the specification, it also only has HDMI 2.0a version.
So far there is OpenPLi and also OpenATV for this set-top box:
OpenPLi: https://openpli.org/download/qviart/Dual+4K
OpenATV: http://images.mynonpublic.com/…rrent/index.php?open=dual
Of course Qviart, as I already wrote, gives bad support to the creators of Enigma2. So it can happen, for example, in 1-3 more years that a new version of OpenPLi or OpenATV will no longer be available for this set-top box. However, this does not mean that the set-top box will not continue to be used. Everything will work for at least 5 years :).
However, Qviart Lunix has very poor software support for Enigma2 development. This manufacturer ignores the development teams of various Enigma2 distributions (firmware) and does not supply / update new drivers that are necessary to run the new Linux kernel. And this means that there is a problem with updates to newer firmware (which, paradoxically, always contains a newer Linux OS kernel).
Otherwise, these Qviart Lunix are very cheap and also good set-top boxes.
https://satelity.ellano.sk/qviart-lunix-4k_38417.html - it can even be compared to Vu+ Zero 4K... although, of course, Vu+ uses better semiconductor components and a better type of DVB tuner
Vu + Zero 4K
Note, it can be bought with a DVB-C tuner but also with DVB-S2X --- so... choose the right one !
However, this Vu+ only includes HDMI v2.0.
Vu+ are more expensive, but after Dreambox, these Vu+ are the second best Linux set-top boxes.
If you want something cheaper, choose from others listed above, such as Gigablue, Zgemma, Octagon, etc. .
Has the OE "5.3" folder been added to the server ? How fast was that, uhm. In the case of Python3 test versions a year ago, it took a very long time to add another folder for the new OE :-).
BTW, guys like Captain SpaceRat Space-Rat Nicker etc. ... please ... who in the OpenATV team has access to the "feed" shell-script ? SpaceRat ?
Earlier I suggested modifying the code in the "feed" shell script, specifically in the get_oever() function. This was a case of the POSIX syntax of the "sed" tool, which was not written correctly and did not work well in all cases of Linux-Shell interpreters... but in the meantime, I have an even better suggestion, to modify the code of the mentioned function to remove it redundant text, already directly in the Python code and not in the Linux-Shell:
- from original:
get_oever() {
OEVER=$($PY - <<END
import sys
sys.path.append('/usr/lib/enigma2/python')
try:
from boxbranding import getOEVersion
oever = getOEVersion()
print(oever)
except:
print("unknown")
END
)
OEVER=$(echo $OEVER | sed "s/OE-Alliance //")
if [ "x$OEVER" == "xunknown" ]; then- to this new code:
get_oever() {
OEVER=$($PY - <<END
import sys
sys.path.append("/usr/lib/enigma2/python")
try:
from boxbranding import getOEVersion
print(getOEVersion().replace("OE-Alliance ", ""))
except:
print("unknown")
END
)
if [ "x$OEVER" == "xunknown" ]; thenWhy don't you read what I write ?
POST No. #325 - However, it is only a temporary solution !
I also wrote that the NEWEST version does not mean a good version. This version 7.3 is a test version. Not officially released. Only version 7.2 is available for download on the official website of OpenATV. But not 7.3. This test version 7.3 can only be downloaded via the modified link.
Many softcams do not have many dependencies on the Linux system (system libraries) used in set-top boxes. Of course... sometimes the dependencies (on system libraries such as SSL, CRYTPO, USB, etc.) also change... but not very often. So the softcams for OE 5.2 from the current OpenATV 7.2 should also work in the test version of OpenATV 7.3.
Do it by commandline and it will get the correct one for your version of image.
Codewget -O - -q http://updates.mynonpublic.com/oea/feed | bash
Or just open OpenWebif and look at the information, in the left column click on info: "About device". And the "OE-Alliance ?.?" version will be also listed there.
OE is version 5.3 in the new OAtv 7.3
Exactly so.
And that's why this unofficial softcam feed server, designed for OpenATV, doesn't work yet. Namely, the server has not yet added a folder intended for OE 5.3 (OpenATV 7.3).
Your link is bad. It is intended for developers, beta-testers or experienced users who know that the standard softcam feed extension will not work yet ! They can also deal with problems, and even report these problems or propose their own correction (on Github).
The official http link for downloading OpenATV is here:
And there you will only find version 7.2 - as the last stable released version of OpenATV.
If you edit the http link manually to download version 7.3, it does not mean that it is the official version !
The last stable OpenATV version is 7.2 and not 7.3. Why are you downloading the test (beta/alpha) version 7.3?
There is probably another OE version and that's why it doesn't work. You can try this as a temporary solution:
wget -O /tmp/feed --no-check-certificate "http://updates.mynonpublic.com/oea/feed"
chmod a+x /tmp/feed
sed -i '133iOEVER="5.2"' /tmp/feed
/tmp/feedThat should help. The OE 5.2 feed will also be used in OpenATV 7.3. This means that the softcam feed intended for OpenATV 7.2 will be used in OpenATV 7.3.
However, I warn you... that after the release of the official version 7.3, it would be a good idea to uninstall this softcam-feed again and install the original one again (it will then be modified so that it works for the 7.3 version as well).
Hi.
I don't understand exactly. Does the normal softcam feed for OpenATV not work ?
In my opinion, it should also work in 7.3 or not ? Is there a different OE version ?
Direct web installation not working? That is, running the original softcam feed installation shell-script from the web:
LOL. Why later ?
You probably just needed a different version of CCcam or rather the latest OScam, which in most cases (in most coding systems) always works correctly.
So what ? Did you solve it ? Or not yet ? :-) Or why are you already thanking us ? .-)
Hi.
The millionth question: What is different after flashing the firmware ?
Is there a new version of Enigma2 OpenATV ? Is there a new version of CCCAM softcam? Or what is different ?
If the new version of Enigma2 is OpenATV or vice versa the CCCAM version has changed, then in both cases a problem can occur.
I assume that you backed up the CCCAM configuration and then restored it.
You can also try replacing CCCAM with OSCAM. After that, you will set everything necessary for connecting to the CCCAM server in OSCAM.
You can also try changing CCCAM to another version. However, it depends on what DVB coding is involved. Unfortunately, most SoftCAMs are very dependent on this and even modular - i.e. for some types of DVB coding, you need a special SoftCAM such as OscamICAM or OscamEMU. I think that even in the case of CCCAM softcam there is already a version to support German ICAMs.
biko :
Hi.
My python script for converting ".png" picon (image) to ".tpl" format (web-template) can process "oscam.srvid2" but also "oscam.srvid". Just run the ".py" script without arguments to display the help:
/usr/script/oscam-picons-converter.py
The shell script ".sh" is intended only for execution directly inside OscamWebif. But you don't have to do it that way. Anyway, it is advisable to modify this ".sh" script according to what arguments you need to use for the converter itself (for the ".py" script).
Srvid file generators:
If you want, you can also find ".srvid" or ".srvid2" generators among my scripts. However, they are not reliable. It's basically just a parser of data from websites with databases of satellite transponders (and their channels). However, this is never 100% reliable. So the ".srvid" or ".srvid2" output may not be reliable. Unfortunately. But you can try it if you want :).
Just on a side note... :
Also, there is a known problem with TPL-picons for OscamWebif and that is the fact that with a huge number of channels, some ServiceID (SID) match. But that's a problem if the CAID also sometimes coincide. The result is two exactly identical filenames "IC_xxxx_xxxx.tpl" which unfortunately get overwritten (one over the other... because there can only be one). Unfortunately, the names of the ".tpl" files do not contain the whole or at least the final and important service reference code (such as is used, for example, in userbouquet files). Unfortunately, the names of the ".tpl" files are composed only of the CAID + SID code. And that is a very indirect way of determining the correct icon.
Hi.
If you want to disable reshare in Oscam, on the CCCAM protocol, it's more complicated. As far as I know, you have to limit the CCCAM protocol to a certain version, but I don't remember which one exactly. Furthermore, reshare can be prevented by setting and activating cascading. But even that, I suspect, can be circumvented in some way.
For me personally, the best way is to set up multiple methods at the same time. For example, that only 1x login is allowed for a specific user (always only from a maximum of one IP address):
OSCam/en/Config/oscam.user – Streamboard Wiki
And also activate cccreshare:
OSCam/en/Config/oscam.user – Streamboard Wiki
OSCam/en/Config/oscam.user – Streamboard Wiki
OSCam/en/Config/oscam.conf – Streamboard Wiki
OSCam/en/Config/oscam.conf – Streamboard Wiki
As for cascading, setting it up is a bit more complicated and involves more things (which you also have to set up).
5.0.230403
Fix for compiling "*.py" files:
Due to problems between PY2 and PY3, in conjunction with the correct Enigma core version,
the IPK / DEB installation packages will contain only "*.py" files and not "*.pyc|*.pyo" files.
Of course, some files may not exist at all, because not all files are necessary. For example, only the following files are relevant:
oscam.server (card readers / proxies)
oscam.conf (oscam basic configuration + your own server configuration)
oscam.user (accounts for your oscam... dvbapi is "special" account... but... you need some basic config files either way when you are a novice user)
Yes... as you can see, the configuration directory is set quite differently... and that's some "pcsc"... I don't know for what reason. As far as I know, pscs is a special version of Oscam, designed to support external USB card readers. As you can see, the configuration folder for Oscam, in your case, is this:
/etc/tuxbox/config/oscam-pcsc-latest/
I've already written to you X times... but for the German provider's HD04, you'll probably need an Oscam-Icam and not a standard Oscam. It is best to start a new topic under the Softcams thread. I have no experience with Oscam-Icam (I don't use it). Unfortunately.
