OpenATV SoftCam Feed Discussion Thread

Quote from cosy

Why is it that the new oATV image changes the path of the Oscam?

How can one re-edit the path to suit the normal Oscam path ?

It IS using the normal oscam paths NOW.

This is the normal path "/etc/tuxbox/config" not "/etc/tuxbox/config/oscam-trunk"

I am documenting this as I am doing it, if anyone is interested.

Just to see how straight forward it all is. Having fun :)

What am I up to? - My General Waffle Thread

Quote from cosy

This is the normal path "/etc/tuxbox/config" not "/etc/tuxbox/config/oscam-trunk"

Yes and no ...

Indeed, just "/etc/tuxbox/config" is the original default path for oscams config files, in so far you are right.

On the other hand, OpenPLi and others have started years ago to add another directory level "name of oscam variant" to that path, so that users can easily have multiple different oscams with different configs on hand.

The additional directory level allows the user to have

• Multiple identical oscams using different configuration sets
• Multiple different oscams using identical configuration sets (By either copying all files to or more sophisticated by making e.g. oscam-set2 a symlink to oscam-set1)
• Multiple different oscams using different configuration sets

Hell no, I know no real-world scenario in which this would be useful but neither do I know a second real-world scenario in which putting some "own"¹ oscam on the box makes any sense.

The one scenario in which that makes sense (Thus "no second" instead of "no") is if someone built an oscam for you - probably after you paid him - that has additional keys compiled in, e.g. to decrypt certain channels using already paired cards or stuff like that.

Neither does putting mgcamd and other legacy shit like that on the feeds make any sense in 2019 and I do it anyways, as there is demand for it ...

¹ Of course "own" does not really mean "own" here, in terms of "compiled myself", but just "extracting an oscam compiled with some broken toolchain from some silly 3rd-party IPK"

openatv 6.3 with oscam r11523 emu

Info Panel

OScamInfo

show log>> fails

card infos>> fails

ECM Statsitics>>fails

after 3 fais

crashlog

blue screen

restart

*********************crash log*********************

01:11:43.3713 { } /usr/lib/python2.7/site-packages/twisted/python/util.py:815 untilConcludes 2019-06-20 01:11:43+0300 [-] KEY: 352 0 KEY_OK OK

01:11:43.3720 { } /usr/lib/python2.7/site-packages/twisted/python/util.py:815 untilConcludes 2019-06-20 01:11:43+0300 [-] [ActionMap] Keymap 'WizardActions' -> Action = 'ok'

01:11:43.3735 { } /usr/lib/python2.7/site-packages/twisted/python/util.py:815 untilConcludes 2019-06-20 01:11:43+0300 [-] [SCREENNAME] ['OscamInfoMenu_summary', 'SimpleSummary']

01:11:43.3763 { } /usr/lib/python2.7/site-packages/twisted/python/util.py:815 untilConcludes 2019-06-20 01:11:43+0300 [-] [SCREENNAME] OscamInfoMenu

01:11:43.3773 { } /usr/lib/python2.7/site-packages/twisted/python/util.py:815 untilConcludes 2019-06-20 01:11:43+0300 [-] ('line_ccam', 'line_ccam')

01:11:43.3789 { } /usr/lib/python2.7/site-packages/twisted/python/util.py:815 untilConcludes 2019-06-20 01:11:43+0300 [-] [SKIN] processing screen oscReaderStats:

01:11:43.5406 { } /usr/lib/python2.7/site-packages/twisted/python/util.py:815 untilConcludes 2019-06-20 01:11:43+0300 [-] [SCREENNAME] OscamInfoMenu

01:11:43.5417 { } /usr/lib/python2.7/site-packages/twisted/python/util.py:815 untilConcludes 2019-06-20 01:11:43+0300 [-] Traceback (most recent call last):

01:11:43.5421 { } /usr/lib/python2.7/site-packages/twisted/python/util.py:815 untilConcludes 2019-06-20 01:11:43+0300 [-] File "/usr/lib/enigma2/python/mytest.py", line 244, in processDelay

01:11:43.5428 { } /usr/lib/python2.7/site-packages/twisted/python/util.py:815 untilConcludes 2019-06-20 01:11:43+0300 [-] callback(*retval)

01:11:43.5432 { } /usr/lib/python2.7/site-packages/twisted/python/util.py:815 untilConcludes 2019-06-20 01:11:43+0300 [-] File "/usr/lib/enigma2/python/Screens/OScamInfo.py", line 490, in chooseReaderCallback

01:11:43.5438 { } /usr/lib/python2.7/site-packages/twisted/python/util.py:815 untilConcludes 2019-06-20 01:11:43+0300 [-] File "/usr/lib/enigma2/python/mytest.py", line 341, in open

01:11:43.5448 { } /usr/lib/python2.7/site-packages/twisted/python/util.py:815 untilConcludes 2019-06-20 01:11:43+0300 [-] dlg = self.current_dialog = self.instantiateDialog(screen, *arguments, **kwargs)

01:11:43.5453 { } /usr/lib/python2.7/site-packages/twisted/python/util.py:815 untilConcludes 2019-06-20 01:11:43+0300 [-] File "/usr/lib/enigma2/python/mytest.py", line 276, in instantiateDialog

01:11:43.5460 { } /usr/lib/python2.7/site-packages/twisted/python/util.py:815 untilConcludes 2019-06-20 01:11:43+0300 [-] return self.doInstantiateDialog(screen, arguments, kwargs, self.desktop)

01:11:43.5463 { } /usr/lib/python2.7/site-packages/twisted/python/util.py:815 untilConcludes 2019-06-20 01:11:43+0300 [-] File "/usr/lib/enigma2/python/mytest.py", line 305, in doInstantiateDialog

01:11:43.5469 { } /usr/lib/python2.7/site-packages/twisted/python/util.py:815 untilConcludes 2019-06-20 01:11:43+0300 [-] dlg.applySkin()

01:11:43.5473 { } /usr/lib/python2.7/site-packages/twisted/python/util.py:815 untilConcludes 2019-06-20 01:11:43+0300 [-] File "/usr/lib/enigma2/python/Components/GUISkin.py", line 114, in applySkin

01:11:43.5478 { } /usr/lib/python2.7/site-packages/twisted/python/util.py:815 untilConcludes 2019-06-20 01:11:43+0300 [-] File "/usr/lib/enigma2/python/Components/GUISkin.py", line 47, in createGUIScreen

01:11:43.5483 { } /usr/lib/python2.7/site-packages/twisted/python/util.py:815 untilConcludes 2019-06-20 01:11:43+0300 [-] File "/usr/lib/enigma2/python/Screens/OScamInfo.py", line 1061, in showData

........................................................

something wrong about skins

:)

I was just going to post a very similar crash.

Oscam info. You cannot view clients or readers.

23:21:32.7890 { } /usr/lib/python2.7/site-packages/twisted/python/util.py:815 untilConcludes 2019-06-19 23:21:32+0100 [-] Traceback (most recent call last):

23:21:32.7895 { } /usr/lib/python2.7/site-packages/twisted/python/util.py:815 untilConcludes 2019-06-19 23:21:32+0100 [-] File "/usr/lib/enigma2/python/Components/ActionMap.py", line 69, in action

23:21:32.7902 { } /usr/lib/python2.7/site-packages/twisted/python/util.py:815 untilConcludes 2019-06-19 23:21:32+0100 [-] File "/usr/lib/enigma2/python/Components/ActionMap.py", line 49, in action

23:21:32.7907 { } /usr/lib/python2.7/site-packages/twisted/python/util.py:815 untilConcludes 2019-06-19 23:21:32+0100 [-] File "/usr/lib/enigma2/python/Screens/OScamInfo.py", line 415, in ok

23:21:32.7914 { } /usr/lib/python2.7/site-packages/twisted/python/util.py:815 untilConcludes 2019-06-19 23:21:32+0100 [-] File "/usr/lib/enigma2/python/Screens/OScamInfo.py", line 456, in goEntry

23:21:32.7921 { } /usr/lib/python2.7/site-packages/twisted/python/util.py:815 untilConcludes 2019-06-19 23:21:32+0100 [-] File "/usr/lib/enigma2/python/mytest.py", line 347, in open

23:21:32.7929 { } /usr/lib/python2.7/site-packages/twisted/python/util.py:815 untilConcludes 2019-06-19 23:21:32+0100 [-] dlg = self.current_dialog = self.instantiateDialog(screen, *arguments, **kwargs)

23:21:32.7934 { } /usr/lib/python2.7/site-packages/twisted/python/util.py:815 untilConcludes 2019-06-19 23:21:32+0100 [-] File "/usr/lib/enigma2/python/mytest.py", line 276, in instantiateDialog

23:21:32.7941 { } /usr/lib/python2.7/site-packages/twisted/python/util.py:815 untilConcludes 2019-06-19 23:21:32+0100 [-] return self.doInstantiateDialog(screen, arguments, kwargs, self.desktop)

23:21:32.7945 { } /usr/lib/python2.7/site-packages/twisted/python/util.py:815 untilConcludes 2019-06-19 23:21:32+0100 [-] File "/usr/lib/enigma2/python/mytest.py", line 298, in doInstantiateDialog

23:21:32.7952 { } /usr/lib/python2.7/site-packages/twisted/python/util.py:815 untilConcludes 2019-06-19 23:21:32+0100 [-] dlg = screen(self, *arguments, **kwargs)

23:21:32.7956 { } /usr/lib/python2.7/site-packages/twisted/python/util.py:815 untilConcludes 2019-06-19 23:21:32+0100 [-] File "/usr/lib/enigma2/python/Screens/OScamInfo.py", line 584, in __init__

23:21:32.7962 { } /usr/lib/python2.7/site-packages/twisted/python/util.py:815 untilConcludes 2019-06-19 23:21:32+0100 [-] File "/usr/lib/enigma2/python/Screens/OScamInfo.py", line 198, in readXML

23:21:32.7967 { } /usr/lib/python2.7/site-packages/twisted/python/util.py:815 untilConcludes 2019-06-19 23:21:32+0100 [-] File "/usr/lib/enigma2/python/Screens/OScamInfo.py", line 137, in openWebIF

23:21:32.7972 { } /usr/lib/python2.7/site-packages/twisted/python/util.py:815 untilConcludes 2019-06-19 23:21:32+0100 [-] File "/usr/lib/enigma2/python/Screens/OScamInfo.py", line 94, in getUserData

23:21:32.7978 { E } /usr/lib/python2.7/site-packages/twisted/python/util.py:815 untilConcludes 2019-06-19 23:21:32+0100 [-] TypeError: cannot concatenate 'str' and 'NoneType' objects

23:21:32.7979 [ E ] python/python.cpp:210 call [ePyObject] (PyObject_CallObject(<bound method NumberActionMap.action of <Components.ActionMap.NumberActionMap instance at 0xaf542508>>,('OkCancelActions', 'ok')) failed)

but extensions>>oscaminfo(6.3+git3321) in plugins menu works correctly

Doesn't fix my crash :frown:

oscaminfo(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

https://github.com/openatv/eni…0e54f14be9404acdf68b5df0e

????

Quote from KiddaC

I am documenting this as I am doing it, if anyone is interested.

Just to see how straight forward it all is. Having fun :)

What am I up to? - My General Waffle Thread

I don't want to disturb your "blog", so I'll comment on some of your statements here instead:

Quote from KiddaC

Part 7: Softcams

As I believe we can no longer install softcams 2 or 3 or 6 ipks. (I maybe wrong)

That 6.Plus IPK was accidently spread, it's about the same as 4.3-r0 and should work, but no warranty if it doesn't.

The actual feed contained in 6.Plus, 4.3-r0, 4.3-r1, 4.3-r2 is the very same, r1 and r2 just added some cleanup actions intended to make OpenATV switch from usage of SoftCAM-Panel to SoftCAM-Setup, as soon as the new feed gets installed, as SoftCAM-Panel is not able to handle the new CAMs.

Sadly some users chose the hard path and messed around with the image to make SoftCAM Panel re-appear and then used a sledge hammer to control the new CAMs with old SoftCAM Panel or at least installed old and new CAMs in parallel ... with varying luck ... varying only between bad and tough luck though ...

... so instead of waiting for more users to lose their pay CS lines (One team member did, by running two oscams, each completely configured incl. the CS line, in parallel), I pulled the plug to the old SoftCAM Panel entirely.

Originally it was meant to stay there for old CAMs for a bit longer to make the transition smoother: Old CAMs, e-g. from settings restore, would have continued to work in SoftCAM-Panel while newly installed ones would disable the SoftCAM Panel and enable SoftCAM Setup instead.

Now about the versions 2 and 3 of the feed:

That feed was taken down for a completely different reason ....

... the old secret feed was hosted in Russia and some day Vodafone (At least Vodafone in Germany and Austria) stopped routing to that server ... no idea if it was on behalf of Vodafone or some peer of them, but all out of sudden like 50% of our users were cut off from the feed, resulting in problems when trying to install additional plugins or performing online updates.

As a large part of OpenATV users was affected, a new server had to be put up and the chance was used to clean up the old CAM mess on the feed.

Actually, even if you install softcam-feed-universal 2 or 3, you should also get the current feed on performing "opkg update && opkg upgrade", as the only package that is still on the old server is softcam-feed-universal 4.3-r2 ... there is just no reason to give it a try if you can instantly have the correct one installed instead :)

The fact that plenty of our users simply had no, zero, nil feed anymore thanks to Vaderphone was the reason why everything was done in quite a rush ... I did half of the work on it from a hotel room with Morse WiFi (On, off, on, off, on, off) on a business trip ...

Quote from KiddaC

Er no. Where has oscam-atv gone. Er.. Do I use EMU, Stable or TRUNK.

oscam-atv is quite a good example of why the old feed needed a cleanup ...

Excerpt from the old feed:

22.04.2019  13:21           881.246 enigma2-plugin-softcams-oscam-atv-emu-arm_1.2_11444-r783_aarch64.ipk
22.04.2019  13:20           781.198 enigma2-plugin-softcams-oscam-emu-atv_1.2_11398_armv7a-vfp.ipk
22.04.2019  13:20           522.084 enigma2-plugin-softcams-oscam-atv-emu-arm_1.2_11353_all.ipk
22.04.2019  13:20           585.332 enigma2-plugin-softcams-oscam-emu-atv_1.2_9659_armv7a-vfp.ipk
22.04.2019  13:20           588.132 enigma2-plugin-softcams-oscam-atv-emu_1.2_11353_all.ipk

Note that you didn't even get the same version of oscam on two different architectures ... let alone that in some cases it was named "oscam-emu-atv" in some other cases "oscam-atv-emu".

The IPKs on the feed were just a pile of losely collected packages created by volunteers for the machines they own themselves ... in this case for example, nobody with a Spark Triplex (sh4) cared about oscam-atv-emu, so there was no package oscam-atv-emu (or oscam-emu-atv) for sh4 ...

If volunteer A had a mipsel box, he created an IPK for mipsel and if volunteer B had an aarch64 box, he created an IPK for aarch64 ... at different times with different versions of oscams inside and different sample configs.

If you used boxes with different architectures, it was a grab bag if you could get similar softcams for all of them or not ...

... it was also entirely by accident if the CAM really worked on your box, because the feed covered versions 6.0 to 6.3 of OpenATV, not considering that they contain different libs ... so if someone compiled oscam with HAVE_SSL using a toolchain with OpenSSL 1.0.2, it would work on OpenATV 6.3 and 6.2, but probably not on 6.0 (Dunno exactly when OpenATV switched from OpenSSL 1.0.0 to 1.0.1 and then to 1.0.2).

Now compare to the new feed:

./3.4/armv7ahf-neon/enigma2-plugin-softcams-oscam-emu-ipv4only_1.20+git1749+1a63986-r2_armv7ahf-neon.ipk
./3.4/armv7a-neon/enigma2-plugin-softcams-oscam-emu-ipv4only_1.20+git1749+1a63986-r2_armv7a-neon.ipk
./3.4/cortexa9hf-neon/enigma2-plugin-softcams-oscam-emu-ipv4only_1.20+git1749+1a63986-r2_cortexa9hf-neon.ipk
./3.4/mips32el/enigma2-plugin-softcams-oscam-emu-ipv4only_1.20+git1749+1a63986-r2_mips32el.ipk
./3.4/sh4/enigma2-plugin-softcams-oscam-emu-ipv4only_1.20+git1749+1a63986-r2_sh4.ipk
./4.0/armv7a-neon/enigma2-plugin-softcams-oscam-emu-ipv4only_1.20+git1749+1a63986-r2_armv7a-neon.ipk
./4.0/cortexa15hf-neon-vfpv4/enigma2-plugin-softcams-oscam-emu-ipv4only_1.20+git1749+1a63986-r2_cortexa15hf-neon-vfpv4.ipk
./4.0/cortexa9hf-neon/enigma2-plugin-softcams-oscam-emu-ipv4only_1.20+git1749+1a63986-r2_cortexa9hf-neon.ipk
./4.0/mips32el/enigma2-plugin-softcams-oscam-emu-ipv4only_1.20+git1749+1a63986-r2_mips32el.ipk
./4.0/sh4/enigma2-plugin-softcams-oscam-emu-ipv4only_1.20+git1749+1a63986-r2_sh4.ipk
./4.1/armv7athf-neon/enigma2-plugin-softcams-oscam-emu-ipv4only_1.20+git1749+1a63986-r2_armv7athf-neon.ipk
./4.1/cortexa15hf-neon-vfpv4/enigma2-plugin-softcams-oscam-emu-ipv4only_1.20+git1749+1a63986-r2_cortexa15hf-neon-vfpv4.ipk
./4.1/cortexa9hf-neon/enigma2-plugin-softcams-oscam-emu-ipv4only_1.20+git1749+1a63986-r2_cortexa9hf-neon.ipk
./4.1/mips32el/enigma2-plugin-softcams-oscam-emu-ipv4only_1.20+git1749+1a63986-r2_mips32el.ipk
./4.1/sh4/enigma2-plugin-softcams-oscam-emu-ipv4only_1.20+git1749+1a63986-r2_sh4.ipk
./4.2/aarch64/enigma2-plugin-softcams-oscam-emu-ipv4only_1.20+git1749+1a63986-r2_aarch64.ipk
./4.2/armv7a/enigma2-plugin-softcams-oscam-emu-ipv4only_1.20+git1749+1a63986-r2_armv7a.ipk
./4.2/cortexa15hf-neon-vfpv4/enigma2-plugin-softcams-oscam-emu-ipv4only_1.20+git1749+1a63986-r2_cortexa15hf-neon-vfpv4.ipk
./4.2/cortexa9hf-neon/enigma2-plugin-softcams-oscam-emu-ipv4only_1.20+git1749+1a63986-r2_cortexa9hf-neon.ipk
./4.2/mips32el/enigma2-plugin-softcams-oscam-emu-ipv4only_1.20+git1749+1a63986-r2_mips32el.ipk
./4.2/sh4/enigma2-plugin-softcams-oscam-emu-ipv4only_1.20+git1749+1a63986-r2_sh4.ipk
./4.3/aarch64/enigma2-plugin-softcams-oscam-emu-ipv4only_1.20+git1749+1a63986-r2_aarch64.ipk
./4.3/armv7a/enigma2-plugin-softcams-oscam-emu-ipv4only_1.20+git1749+1a63986-r2_armv7a.ipk
./4.3/cortexa15hf-neon-vfpv4/enigma2-plugin-softcams-oscam-emu-ipv4only_1.20+git1749+1a63986-r2_cortexa15hf-neon-vfpv4.ipk
./4.3/cortexa9hf-neon/enigma2-plugin-softcams-oscam-emu-ipv4only_1.20+git1749+1a63986-r2_cortexa9hf-neon.ipk
./4.3/mips32el/enigma2-plugin-softcams-oscam-emu-ipv4only_1.20+git1749+1a63986-r2_mips32el.ipk
./4.3/sh4/enigma2-plugin-softcams-oscam-emu-ipv4only_1.20+git1749+1a63986-r2_sh4.ipk

You will see that you get the very same version of oscam-emu for any architecture and any version of OpenATV you use the feed on.

The version numbers at the beginning match the oe-a core, not the openatv version, so 3.4 is for OpenATV 5.3, 4.0 is for OpenATV 6.0 and so on.

Each package will contain the same init.d script and the same sample config, so if you set oscam-whatever on your own aarch64 box and then you have to set up your parent's mipsel box, don't think about it, just use the very same oscam-whatever, just for mipsel instead of aarch64!

All CAMs that can be built from source ...

• oscam-trunk - http://www.streamboard.tv/oscam/browser/trunk
• oscam-emu - https://github.com/oscam-emu/oscam-patched
• oscam-smod -https://github.com/Schimmelreiter/oscam-smod
• NCam - https://github.com/fairbird/NCam

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

• oscam-trunk - The genuine original oscam-trunk, built right from streamboard.tv sources
• oscam-stable - The same as oscam-trunk, but not being updated for each and every change done to the source but only once the code has settled, that means hasn't been touched in a while, which is a good indicator for the last revision being o.k. for general use and not containing silly new bugs.

  
  

  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.

• oscam-emu - oscam with emu, but not using a patch file but simply the git of the oscam-emu project containing the already patched oscam-emu source.

  
  

  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.

• oscam-smod - This is my own variant of oscam.

  
  

  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

• NCam - See fairbird's own thread on this forum

Quote from KiddaC

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

Quote from KiddaC

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

Quote from KiddaC

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.

Quote from hango

oscaminfo(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

Display More

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

etc/tuxbox/config/oscam-emu/oscam.conf

plugins menu>> oscaminfo(6.3+git3321) cant autodetect conf file.but added manualy it works.

under info panel>> embedded OScamInfo can detect conf file .show tmp--show client--show reader--setup works.

but others fails.

The problem of inaccessibility of softcam in open atv image has been solved by new update for ncam emulator

EDIT ( Abu Baniaz): Screenshot with server details removed

thank you READ

May I ask why the file " . version" has disappeared from tmp directory ? It was quite useful (at least for me) to read the exact place of conf files and many more things. I'm using OpenAtv 6.3 with new Infopanel. Thanks

SpaceRat Thanks for taking the time to write a very detailed technical answer.

The entire point of my post was just lets just do this, learn as I go, see what issues people might be experiencing in the process and document it in a way a non technical person can understand.

I have been reading lots of posts this week about the new softcams and it was the very technical answers that was confusing the hell out of an average user, me included.

It seemed like only a handful of people actual knew what was going on with this.

From my initial readings, it looked like a lot had to be done to achieve these new softcam feeds. This was not the case.

When explained in very simple language it's actually a rather easy process. Not everyone is a developer. Most people are probably not interested in all the finer details.

People just want it to work in similar way to old. And when you go through the process, there isn't actually a lot of difference.

I know there will be initial teething problems, like you say, a lot of the changes had to be done quickly.

With a small amount of googling, I got up and running first time. So apart from oscaminfo.py being broke in my setup, I found no real major issues.

And feel free to comment in my waffle thread. It's what it's there for :)

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: