OpenATV SoftCam Feed Discussion Thread

Quote from SpaceRat

The recommended way of installing the OpenATV secret feed is typing this one line on a shell session on the box:

Code

wget -O - -q http://updates.mynonpublic.com/oea/feed | bash

The easiest method of getting a shell session to the box is the "Terminal" in OpenWebif, but feel free to use puTTy or whatever you already use.

That one-liner makes sure you get the latest version of the feed for your actual image version and architecture.

No need to download the IPK, copy it to the box and installing it through GUI or shell when using the one-liner but you are still free to use an IPK, if you insist on it.

Use version 4.3r2 or later in that case.

The new feed supports OpenATV 5.3 through 6.3, that is "the last 5 versions of OpenATV".

In OpenATV 5.3 to 6.1 you will only have one place to configure the CAMs, that is in "Menu -> Settings -> Decryption", because it would probably cause more problems to patch it into old versions of E2, while that hook in "Menu -> Settings -> Decryption" is just a plugin.

Starting as of OpenATV 6.2 (Images 2019-06-15 and later), the softcams can be configured in three places:

- "Menu -> Info Panel", just as before with softcam panel

- "Quick Menu" (In most cases on blue key or long blue key), just as before with softcam panel

- "Menu -> Settings -> Decryption and parental protection", as it is the most logical place to search at if you aren't already used to the other places

The softcam panel was entirely removed due to user problems, e.g. one team member losing his line due to double logins (He had two oscams running in parallel, one through the new method, one through the old one), so to avoid problems, having both methods inside the image appeared a bigger problem than making a cut here.

Installing the feed through older IPKs, like versions 2.0 or 3.0, will only get you an empty secret feed, except for one package: The new secret feed :)

The new feed has multiple advantages:

• All CAMs that can be built from source code (All OScams and Ncam) are built from source code using the matching OpenATV build environment, that means they perfectly fit the libraries inside the actual image.

  
  

  oscams on the feed for OpenATV 6.3 are built inside the OpenATV 6.3 build environment, oscams on the feed for OpenATV 6.2 are built inside the OpenATV 6.2 build environment, oscams on the feed for OpenATV 6.1 are built inside the OpenATV 6.1 build environment and so on.

  Most CAMs you can download from forums are simply built in generic cross-compiler environments that do usually not really contain the matching libs ...

• All OScams and Ncam are built every night if their sources get updated.

  
  

  If you install oscam-trunk, you will always get the latest one with a maximum delay of 24h.

  For conservative users that do not want to live on the edge, there is oscam-stable, which will give you oscam svn11518 until there is some really important change in trunk and that change has proved being stable (By not being changed again within the next weeks).

• Starting CAMs through init.d is more robust and stable than forking them as childs of E2 (That's why there isn't a "watchdog" anymore, it's simply not needed)
• CAMs started through init.d are easier to maintain remotely

  
  

  You can simply start/stop/restart them from the shell

  Code

  root@quad4k ~ # /etc/init.d/softcam stop
  Stopping Softcam service oscam-smod: OK
  root@quad4k ~ # /etc/init.d/softcam start
  Starting Softcam service oscam-smod: OK
  root@quad4k ~ # /etc/init.d/softcam restart
  Stopping Softcam service oscam-smod: OK
  Starting Softcam service oscam-smod: OK
  root@quad4k ~ # /etc/init.d/softcam status
  Softcam service oscam-smod: Running.

  e.g. after editing config files.

  No need to mess around with "kill", "killall" commands or figuring out if you need to background the cam manually or if it will background automatically if you start it directly via shell.

• CAMs started through init.d are ready when you are ...

  
  

  As the CAM starts early during boot, it has time enough to initialize card readers or server connections to decrypt instantly as soon as E2 can tune.

  Python CAM start added a delay, because starting the CAM didn't happen any earlier than tuning the startup/previous station

Display More

Quote from SpaceRat

The recommended way of installing the OpenATV secret feed is typing this one line on a shell session on the box:

Code

wget -O - -q http://updates.mynonpublic.com/oea/feed | bash

The easiest method of getting a shell session to the box is the "Terminal" in OpenWebif, but feel free to use puTTy or whatever you already use.

That one-liner makes sure you get the latest version of the feed for your actual image version and architecture.

No need to download the IPK, copy it to the box and installing it through GUI or shell when using the one-liner but you are still free to use an IPK, if you insist on it.

Use version 4.3r2 or later in that case.

The new feed supports OpenATV 5.3 through 6.3, that is "the last 5 versions of OpenATV".

In OpenATV 5.3 to 6.1 you will only have one place to configure the CAMs, that is in "Menu -> Settings -> Decryption", because it would probably cause more problems to patch it into old versions of E2, while that hook in "Menu -> Settings -> Decryption" is just a plugin.

Starting as of OpenATV 6.2 (Images 2019-06-15 and later), the softcams can be configured in three places:

- "Menu -> Info Panel", just as before with softcam panel

- "Quick Menu" (In most cases on blue key or long blue key), just as before with softcam panel

- "Menu -> Settings -> Decryption and parental protection", as it is the most logical place to search at if you aren't already used to the other places

The softcam panel was entirely removed due to user problems, e.g. one team member losing his line due to double logins (He had two oscams running in parallel, one through the new method, one through the old one), so to avoid problems, having both methods inside the image appeared a bigger problem than making a cut here.

Installing the feed through older IPKs, like versions 2.0 or 3.0, will only get you an empty secret feed, except for one package: The new secret feed :)

The new feed has multiple advantages:

• All CAMs that can be built from source code (All OScams and Ncam) are built from source code using the matching OpenATV build environment, that means they perfectly fit the libraries inside the actual image.

  
  

  oscams on the feed for OpenATV 6.3 are built inside the OpenATV 6.3 build environment, oscams on the feed for OpenATV 6.2 are built inside the OpenATV 6.2 build environment, oscams on the feed for OpenATV 6.1 are built inside the OpenATV 6.1 build environment and so on.

  Most CAMs you can download from forums are simply built in generic cross-compiler environments that do usually not really contain the matching libs ...

• All OScams and Ncam are built every night if their sources get updated.

  
  

  If you install oscam-trunk, you will always get the latest one with a maximum delay of 24h.

  For conservative users that do not want to live on the edge, there is oscam-stable, which will give you oscam svn11518 until there is some really important change in trunk and that change has proved being stable (By not being changed again within the next weeks).

• Starting CAMs through init.d is more robust and stable than forking them as childs of E2 (That's why there isn't a "watchdog" anymore, it's simply not needed)
• CAMs started through init.d are easier to maintain remotely

  
  

  You can simply start/stop/restart them from the shell

  Code

  root@quad4k ~ # /etc/init.d/softcam stop
  Stopping Softcam service oscam-smod: OK
  root@quad4k ~ # /etc/init.d/softcam start
  Starting Softcam service oscam-smod: OK
  root@quad4k ~ # /etc/init.d/softcam restart
  Stopping Softcam service oscam-smod: OK
  Starting Softcam service oscam-smod: OK
  root@quad4k ~ # /etc/init.d/softcam status
  Softcam service oscam-smod: Running.

  e.g. after editing config files.

  No need to mess around with "kill", "killall" commands or figuring out if you need to background the cam manually or if it will background automatically if you start it directly via shell.

• CAMs started through init.d are ready when you are ...

  
  

  As the CAM starts early during boot, it has time enough to initialize card readers or server connections to decrypt instantly as soon as E2 can tune.

  Python CAM start added a delay, because starting the CAM didn't happen any earlier than tuning the startup/previous station

Display More

I'm using openatv 6.3 image on 14.06, but if update so the softcam be unavailable, Can get the softcam back if I use your Code?
DM800 se v.2
openAtv 6.3
Oscam 11523

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 ...

https://github.com/openatv/eni…680f29adad1bbe8c99ffdc97f

Quote from Rua Velha

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.

I would prefer, after installation, just to have this path and nothing else "/etc/tuxbox/config"

How do I go about this?

Thank you

Entirely interesting thread. Currently running a backup flash of openatv 6.2 with enigma2-softcams-oscam-all-images_11.523-emu-r796-arm+mips_all.ipk.

Backup restored because of the exact same issue with newer openatv. And loss of the Softcam Panel after an update and new flash of a recent image.
As the message in update suggested installing fresh, and that mine was 'very old'.

I've followed the many different methods of getting control of oscam back posted here.
My opinion due to trying this-and-that is I ended up with a 'dirty' install of oscam and the methods to get it running.
I did find the secret feed for update source selections.
I only ended up with Parental Controls in the new Decryption screen. Nothing at all of oscam.

1) For a fresh install is there a defacto working method to install oscam-emu which doesn't require terminal commands afterwards to start/stop?
I don't use anything but the Softcam.key file. No sharing. Not needed at this time.
Does anyone have a step-by-step for a fresh install of oscam on newer 6.2 versions?

2) Is there a way to get the panel back? The yes and no's in this thread are foggy. I tried the take-files/folders-from previous-backups-and stick-them-here.
Ended up with no joy!
If yes, how? If no (and it's supposedly been moved to the Decryption screen)....didn't happen for me, how exactly to get it working?

3) Softcam feeds. New to me. I've simply installed an oscam in the past from posts here. Moved my softcam.key file to the correct directory.
Perhaps have had to change the webif http port in oscam or edited my bookmark to it in the browser. Hit my red button, entered the panel. And started oscam.
Now things are balky and complicated. What exactly IS a softcam feed? Pardon my stupid question.

Would someone be willing to narrow down all of these pages and give some sure fire steps to get up and running after a fresh install?
I'm not the best at understanding terminal commands. Beyond the help file and google searches, some are simply undocumented.
But I try!

Q: Getting CAMs on OpenATV:

A: OpenATV SoftCam Feed

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.

Quote from SpaceRat

Q: Getting CAMs on OpenATV:

A: OpenATV SoftCam Feed

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.

Display More

So what this leads me to believe is that the softcam installer (ipk) method to 'get you there' will leave a softcam in the system.
But starting it and controlling it will be a bit complicated.
And explains why I wasn't able to get it in the webif. It wasn't running at all.
So what it looks like is a team should (could) develop an installer to add everything that the openatv team deemed necessary to remove.
I could be wrong. Not even being aware of a softcam feed, I used the ipk installer method.
And later in different versions, the binary swap and version edit to properly show in the softcam panel was the procedure.
If in the future other versions of Enigma2 dev's should deem removal of their own softcam panels necessary for the reasons you pointed out, headaches would be already taken care of.

Your post is utter nonsense.

Re-read my post, especìally the last passage.

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.

Quote from SpaceRat

Your post is utter nonsense.

Re-read my post, especìally the last passage.

If you're referring to me. Sir.
Softcam Panel V2.0 is simply nonexistent in the versions of openatv I downloaded and installed on an os mio 4k the past 2 or so days.
So I'm currently running a version from a full backup from March of this year..
If I were to update it, the panel would disappear.

"Nonsense" comments simply do not assist a person realize what they simply may have missed.
Or what they have occur that you may or may not have happen on your end.
But thank you for your previous explanation.

Quote from SpaceRat

Your post is utter nonsense.

Then try to answer some questions put forward in clear terms, so we do understand

supwiddiss. see my thread. It's in plain english with no technical jargon.

See if it helps your cause.

What am I up to? - My General Waffle Thread

But my interpretation of this entire softcam issue.

OpenATV is german.

It's main user base is German

ISP Providers were blocking the original URL for feeds.

Something had to be done quickly.

While correcting feeds, they have also tidied up all the multiple mutations of softcam.

The old might have worked, but they were a complete mess

All the main images are trying to provide a solution to this mess.

Their will be teething problems.

In the end it will all work, just like it used to. But different ;)

Quote from KiddaC

see my thread supwiddiss. It's in plain english with no technical jargon.

See if it helps your cause.

What am I up to? - My General Waffle Thread

But my interpretation of this entire softcam issue.

OpenATV is german.

It's main user base is German

ISP Providers were blocking the original URL for feeds.

Something had to be done quickly.

While correcting feeds, they have also tidied up all the multiple mutations of softcam.

The old might have worked, but they were a complete mess

All the main images are trying to provide a solution to this mess.

Their will be teething problems.

In the end it will all work, just like it used to. But different ;)

Display More

Well....Shit...This should be made a sticky.
I'll jump on it once my tourettes and utter nonsense subsides. Lol!
Thanks!

Quote from SpaceRat

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 ...

https://github.com/openatv/eni…680f29adad1bbe8c99ffdc97fT

Thanks, today I copied the infopanel folder to my PC , then I updated the Openatv 6.3 image.
After rebooting the softcam panel missed, but when i recopied the infopanel , every think working perfect , but the Sky sport De freezing yet .
Oscam 11523

I am not going to lie, I did the exact same thing. Copied all the folders and relevant files.

In the end none of my backups were needed.

If you follow the correct new process. It does all work.

No need to manual install IPKs, because the files in the feeds are the correct ones you should be using.

And no need for the old softcam panel, because the new panel auto restarts without having to set it to, and via the blue button gives access to the cam info pages.

KiddaC. Very good, clear, and easy to understand instructions.
Nothing pompous about you. Exactly how I would do a write up to assist others.
Actually I take industrial technical literature buried in page after page and dummy it down to a 10-step. Sometimes more, sometimes less.
Still a bit of the ole gibberish running around upstairs. At least that's what some believe. Let's have a beer!
Thanks!

I am going to defend SpaceRat here.

If you read this entire post, he has been burning the candle both ends.

He / openatv , are getting stick left right and center, not just on this forum, but on multiple forums and on github.

Despite that he has had the decency to stick around and answer as many questions as he can.

His answers are definently over techincal when people are just after simple answers.

But I work with developers all day long. They speak a different language. ;) I am a front-ender. My job is to communicate to the user.

So in my waffle thread, that is exactly what I have done. Lets approach this as a user and lets go through the motions.

I have no answers to techincal questions, that is exactly what SpaceRat is for. But if my walk through is helpful, then I have achieved what I set out to do.

Quote from KiddaC

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.