I have no idea, but feel welcome to ask in the international section of the OpenATV forum.
The only things that can not be discussed on the OpenATV forum are:
- CI+ (No E2 box vendor has a valid license for CI+)
- SoftCAMs
- MediaPortal Gray Zone
and the presence of these things on a mysterious secret feed :)
That's what I'm here for, to assist with these things, as nobody on the OpenATV forum can.
All CAMs that can be built from source ...
... get built from source ... every night if necessary (if they got updated) and for every supported version of OpenATV and every supported architecture independently!
And the original oe-a build environment gets used for this, so all CAMs built from source perfectly fit the image they get build for.
If the image has OpenSSL 1.0.2m, oscam gets compiled against OpenSSL 1.0.2m and not 1.0.2q, 1.0.1, 1.0.0 or even 0.9.8 ... shit you will find in many IPKs from download sections on the net!
Also, if the image uses gcc-7 to compile, oscam will get compiled using gcc-7 too and not gcc-6 or whatever ...
Yes, that means oscam-emu alone would get configured, compiled and packaged fifty-four times (5 OpenATV versions mutiplied by 5 architectures since 5.3 plus one more in each of 6.2 and 6.3, multiplied by 2 for dual-stack on the one hand and ipv4only on the other hand) on any change inside its git.
And "oscam-trunk" is simply called that way, because it was always widely referred to as oscam-trunk. oscam-trunk is simply the development trunk of the original oscam on streamboard.tv
I omitted the "atv" inside the package names, because there has never been anything ATV specific (except the *.emu file) inside the ipk. It just mean it was for ATV and has ATV sample configs (More or less, read about different volunteers for different packages above).
The oscam versions on the feed are
The only addition is a patch to make it work on Venton/Sogno Uniboxes, because current oscam will not work on them (You will only get audio but no video or vice versa without the patch, not sure).
Set "boxtype = sogno" if you happen to own a Venton/Sogno Unibox.
Most of the times it will be latest trunk - but the oscam-emu team can also be behind one or two days - and it will always be latest emu.
It combines:
- latest trunk (But I can also be behind a day or so, as I'm not watching the trunk code 24/7)
- latest emu (But I can also be behind a day or so, as I'm not watching the trunk code 24/7)
- The webif of oscam-modern by gorgone
- Auto-detection of many cards (All Sky DE on Astra, Vodafone Cable and Unitymedia Cable that oscam can operate), Astra HD+, SRG/SRF (Swiss Television), ORF (Austrian Televion), TivuSat (Italy), Redlight (XXX), Ziggo NL (Dutch Cable), ...
If you want a card added, just let me know, I'm open to additions.
- The Venton/Sogno patch
- A patch to detect and block CWs for German Sky Sat that have been broken by misconfigured oscams or legacy CAMs that do not support latest CW CRC changes for Sky Germany
Select CCcams if not already selected.
Restart cam
Side note:
No need to manually restart the CAM.
As soon as you leave SoftCAM setup, it will automatically stop the old CAM and start the newly selected one as soon as you leave the dialog (Green button).
Do not do this for OpenViX. That is only for OpenATV
why ????
it worked ok with openvix...
Because OpenViX uses a method for starting CAMs that is different from that in OpenATV.
OpenViX has the scripts for starting CAMs in /usr/camscripts or something like that and probably starts them through Enigma2 (Late at start).
OpenATV now uses the regular init.d-System, that means the CAMs get started through Linux early at boot.
However:
The scheme for starting CAMs that gets used by OpenATV does work with most, if not all, Enigma2 distros, including OpenViX
So if you install a CAM from the OpenATV softcam/secret feed, it will definitely work in means of starting at boot, decrypting TV, and so on.
However you will not be able to control its start/stop from within E2 and OpenViX' E2 will not care about it when setting up different CAMs from their feeds, so you might get two CAMs (trying to) run at the same time.
The reason I use this plugin is because it shows you the ecm details like the original softcampanel
And so does the new softcam setup:
Going the hard way (Copy this or that to there, chmod 666, replace file bla with file foo, reboot, turn around standing on one leg, ...) will give nothing but hassle.
On OpenATV it's as easy as
1. Install the softcam feed (Hell, I wish you could skip this step, but for legal reasons you can't, OpenATV has to ship without).
2. Install a CAM of your choice from feed
3. Put your configs inside it
4. Enjoy
Am I missing something? Openatv 6.3 image is installed.
OpenATV has exactly this CCcam on the feed.
The only problem is, that the softcam feed is not pre-installed with the image for legal reasons, so you have to add the softcam feed yourself:
- or -
oscam-trunk is just that, plain oscam.
If you want emu, get oscam-smod or oscam-emu instead.
Well, as long as you know how to handle the CAMs without support inside the E2-GUI, the feed is perfectly ok for OpenViX.
But if you don't, you really shouldnt!
It would bring you into the same problems that forced OpenATV to remove the softcam panel with a smaller grace period for a soft migration ...
Or just get an existing package that is for OpenPLi, DreamSatGR, OpenVisionE2, teamblue ...
But be careful when you find "all images" ipks, as they might still treat OpenATV the old way.
Here are step by step instructions, written by users for users, plain and simple:
- or -
What am I up to? - My General Waffle Thread
Best choices IMHO are oscam-smod and oscam-stable:
My server and all the boxes that I have to set up and maintain (And that's more than two dozen) run oscam-smod and I'll most definitely notice problems within my mod (because I would get flooded in WhatsApp).
Alternatively, oscam-stable gets you a plain oscam.
Not the latest but neither an old version and definitely a version that's known inside the scene to work flawlessly.
So you won't get worse versions like svn11520 (introduced a bug), 11522 (First attempt to fix the bug from 11520, but not a good attempt, as it was reverted in 11523 and replaced by a different fix).
Currently oscam-stable is at 11518 , it might become 11523 in case 11523 proves to be a good version in like 2 weeks or so.
The specialty about oscams-smod is:
At the moment, oscam-smod can detect and configure (Incl. RSA-, DES-, Boxkeys and EMM blocking):
I'll add auto-detection and -configuration for any card where keys are known on demand, if the person who asks for it will also test it :)
CCcam 2.3.8 is a fake, it's an old - patched - 2.0.xx version, while 2.3.2 is really 2.3.2 with Sky patch.
At least for the moment we will only add the latest version of each cam.
- wicardd added to feed
- some minor improvements on existing packages
His answers are definently over techincal when people are just after simple answers.
That's probably correct, but the problem is, that some users appear to be desperate to go the hard way (Messing around with the E2 code for example) and expect simple answers to complex questions.
Joe Average is supposed to want good results quickly: Install feed, install cam, put config inside, be happy.
Just as you described in your how-to.
Those who want to go deeper, e.g. by replacing binaries, should know what they do and either have an understanding about what they do or at least take tje time to read and learn.
back to topic:
The crash in OSCamInfo has been fixed.
It has been fixed today, so it might take a day or two until it will be in updates or new images.
Your post is utter nonsense.
Re-read my post, especìally the last passage.
Q: Getting CAMs on OpenATV:
Q: What is a "softcam feed"?
A: For legal reasons (OpenATV is situated in Germany and everything can be traced back to the real project owner as natural person that could be taken to court ...), the OpenATV image does neither contain (obvious) SoftCAM support nor does it have SoftCAMs for download on the feed.
So unlike other images where you can download softcams right from their regular feeds, you need to add a feed for softcams (operated by 3rd persons entirely unrelated to the OpenATV team :) ) manually when flashing a fresh image and you want to be able to install softcams (and some other stuff not being clearly legal) from feed.
You can of course still install softcams from ipks downloaded from anywhere else on the net as well, without the feed.
The very only thing that has really changed is that those ipks now have to adhere to the way softcams are installed on OpenPLi and many other images (teamBlue, OpenEight, ...), rather than having a non-standard OpenATV specific way of installing cams.
Hello
I have a card on the box, how can a run cardserver?
I Have installed cccam and it working with no problem but cardserver no option:derpthink::derpthink:
This point is somewhat confusing, as I have to admit.
The option to select a cardserver in SoftCAM setup is rather historic and was just never removed (And I don't want to remove it either, as I want the code to be as similar to that in OpenPLi as possible).
The definition of "softcam" and "cardserver" as far as softcam setup is concerned is:
The "softcam" does the actual decryption for E2 and in order to do so uses the DVBAPI to hook to E2.
The "cardserver" handles your physical card inside the readers and delivers them to the "softcam", e.g. using "C-Lines".
Reading that, most people will want to respond:
"Uhm, my softcam does both of these tasks!" and they are right.
All softcams there are (oscam, ncam, cccam, mgcamd, ...) actually do both, they handle physical cards inside physical readers and they decrypt tv for E2 using the DVBAPI.
Historically though there were situations, where softcam A could handle card 1 while softcam B couldn't.
If you then didn't want to use softcam A for everything, you had to use softcam A as a pure "cardserver" for card 1 and install softcam B as plain softcam that gets the card shared from softcam A.
And yes, it was as hard to set up as it is to read and understand:
softcam A had to be configured not to hook to DVBAPI (Only one softcam is allowed to do that at any given time) and softcam B had to be configured not to touch the reader from which softcam A was supposed to read card 1.
So when would setting up two softcams, one as softcam and one as a cardserver make sense?
Only if you had a "wonder softcam" that could handle cards which other cams can not handle, e.g. paired Sky UK or Sky DE cards, and you want to keep the existing softcam for everything else.
In that case, you would need "wonder softcam" as cardserver.
Now currently there is no "wonder softcam" around - well, not publically - so currently there is no point in offering any "cardserver" packages on the feed.
And even if there was such a "wonder softcam", it would probably simply be an oscam with non-public patches and most users would simply use that as their only softcam.
But if you happen to know any such "wonder softcam", I can create a cardserver ipk for it.
The only thing that has disappeared in OpenATV 6.2 and 6.3 is the "SoftCAM-Panel", which was just a control plugin for SoftCAMs.
It was not needed anymore, as the new feed - and yes, you get that if you follow my instructions about getting the new feed - contains only SoftCAMs with a different startup method.
And the control screen for the new cams was added end of April already ...
Display Moreoscaminfo(6.3+git3321)
setup doesnt see oscam.conf
read user data from oscam.conf... no
use manual
ip 127.0.0.1
port 8888 or 83 or what writes in conf file
I'll fix that.
But please help me to understand your way of thinking:
Where is the beef in cumbersome typing in values into a plugin setup dialog that the plugin can auto-detect?
Sometimes I really want to be able to think overcomplicated like some of the users ...
All CAMs that can be built from source ...
... get built from source ... every night if necessary (if they got updated) and for every supported version of OpenATV and every supported architecture independently!
And the original oe-a build environment gets used for this, so all CAMs built from source perfectly fit the image they get build for.
If the image has OpenSSL 1.0.2m, oscam gets compiled against OpenSSL 1.0.2m and not 1.0.2q, 1.0.1, 1.0.0 or even 0.9.8 ... shit you will find in many IPKs from download sections on the net!
Also, if the image uses gcc-7 to compile, oscam will get compiled using gcc-7 too and not gcc-6 or whatever ...
Yes, that means oscam-emu alone would get configured, compiled and packaged fifty-four times (5 OpenATV versions mutiplied by 5 architectures since 5.3 plus one more in each of 6.2 and 6.3, multiplied by 2 for dual-stack on the one hand and ipv4only on the other hand) on any change inside its git.
And "oscam-trunk" is simply called that way, because it was always widely referred to as oscam-trunk. oscam-trunk is simply the development trunk of the original oscam on streamboard.tv
I omitted the "atv" inside the package names, because there has never been anything ATV specific (except the *.emu file) inside the ipk. It just mean it was for ATV and has ATV sample configs (More or less, read about different volunteers for different packages above).
The oscam versions on the feed are
The only addition is a patch to make it work on Venton/Sogno Uniboxes, because current oscam will not work on them (You will only get audio but no video or vice versa without the patch, not sure).
Set "boxtype = sogno" if you happen to own a Venton/Sogno Unibox.
Most of the times it will be latest trunk - but the oscam-emu team can also be behind one or two days - and it will always be latest emu.
It combines:
- latest trunk (But I can also be behind a day or so, as I'm not watching the trunk code 24/7)
- latest emu (But I can also be behind a day or so, as I'm not watching the trunk code 24/7)
- The webif of oscam-modern by gorgone
- Auto-detection of many cards (All Sky DE on Astra, Vodafone Cable and Unitymedia Cable that oscam can operate), Astra HD+, SRG/SRF (Swiss Television), ORF (Austrian Televion), TivuSat (Italy), Redlight (XXX), Ziggo NL (Dutch Cable), ...
If you want a card added, just let me know, I'm open to additions.
- The Venton/Sogno patch
- A patch to detect and block CWs for German Sky Sat that have been broken by misconfigured oscams or legacy CAMs that do not support latest CW CRC changes for Sky Germany
Oh there is already one in there with a load of German readme.
Better save that somewhere safe and translate that first and see what it says.
I never knew all that stuff in that file. Anyway irrelevant for what I am trying to achieve. so lets jog on.
It's a 1:1 copy from the old CCcam package ... if your previous sample config looked different, it's just another proof of what I said above about the old CAMs being a grab bag on what you get .... the arm ipk might have contained a different sample config than that for mipsel ...
Select CCcams if not already selected.
Restart cam
Side note:
No need to manually restart the CAM.
As soon as you leave SoftCAM setup, it will automatically stop the old CAM and start the newly selected one as soon as you leave the dialog (Green button).
Also just noticed this softcam panel still lives in infopanel. I was under the impression they had removed that with this new version.
Not really:
The file in flash is only a small left-over (The "Install a SoftCAM" screen) of it.
It might go away too, as it's duplictated code from "Install/Update/Remove plugins".
So I might replace the remaining code with a call to "Install/Update/Remove plugins" screen and setting a filter to "softcams only", so regular users will hardly notice the difference.
