Posts by joeuser

    [MENTION=60986]joeuser[/MENTION] and all
    we were discussing Amiko Alien 2 boxes wherether in E2 or spark what are the boxes referred to here
    " sbox1 and the other for sbox2"


    sbox refers to the encrytpion/decryption mode used.
    From wikipedia:

    Quote

    In cryptography, an S-box (substitution-box) is a basic component of symmetric key algorithms which performs substitution. In block ciphers, they are typically used to obscure the relationship between the key and the ciphertext — Shannon's property of confusion.


    - - - Updated - - -


    how do you even do stream relay with all these amiko boxes if they don't even support to put any type of IPTV over the bouquets.


    Secondly, where or if there is a tuto on how to add keys to mcas? because I have used all the ones I can find, but non of them work however if I used them with my GigaBlue they work perfectly.


    this is stressful, no documentation what so ever


    Alien 1 and 2 both support iptv (with enigma2 image).


    You should be able to update the keys through the key editor of the plugin. You posted in this thread but, but did you pay attention to this post and the few after?
    https://linuxsat-support.com/showthread.php/91104-MCAS-plugin-with-PowerVu-support?p=330235&viewfull=1#post330235

    Probably need more configuration details. With enigma2, when you tune a channel which is available on two different tuners, it "should" use the tuner with the least number of LNBs connected to it ( leaving you the biggest number of still available channels to watch once one of the tuners is busy.) So, by your description, it should be trying to use tuner B before tuner A. So, I am not sure why you need to "force" it to use tuner B? Have you tried other enigma2 images?

    ah ok yes ive already tested it on a zgemma channels are clearing fine so can i assume then that the amiko when in enigma 2 mode cant install the plugins the same way as a solo 2 would ive read you need to use oscam instead of Cccam ?



    Correct, there is no cccam for the alien2. You may find some files claiming to be cccam for alien2, but they are usually just mgcamd renamed. (however that may work for you depending on your configuration.) Oscam is available for the alien2. If you are worried about compatability with your current config, you can test oscam on your vu solo first.


    The alien2 is sh4, whereas the Edison is mips based. Both are supported by OpenATV and other builds of enigma2 (note however that the openpli team does not "officially" support sh4 boxes) There can be a problem with plugins as some are designed for mips and either do not work well or not at all for sh4. But the plugins you listed do work on the alien2. If you look in the alien section here, you will see lots of info... https://linuxsat-support.com/f…mp-Satellite-HD-Receivers


    I never used the Edison Mega, so I cannot comment on it.

    Thanks, but keep in mind that we are talking here about an Amiko A3 Combo which is an Android box.


    Do you have that MCAS version With auto update? Please share it, thanks!!!


    No, I only have the sh4 version. But if I see it posted somewhere I will let you know.

    BTW - the latest MCAS has auto-update of keys working, so it may be able to find the correct keys if you just leave it on a channel for awhile. BUT again, not sure which channels you are trying and if auto-update will work for them. I only know for sure it worked on afn channels...


    With MCAS, there is no need for stream relay. BUT, I am not familiar with that box - only tested MCAS on alien2/spark.

    Hi esuo.I used your oscam conf.Unfortunately i always have the same issue .I cant see the Discovery channels at 4.8E/0.8W!I have no problems with AFN channels.(also HD)


    On my oscam conf i have these values:

    Code
    [streamrelay]
    stream_emm_enabled = 1
    stream_relay_enabled = 800


    Hw can i fix it?THX in advance.


    Those channels have much higher bandwidth, so you may need to adjust your delay...

    Code
    stream_relay_enabled = 1
    stream_ecm_delay              = 1201


    - - - Updated - - -


    yes i used your list, oscam reports all of the other afn channels as having the correct key and open as normal if i switch to the stream relay counterparts, this channel doesn't say its clearing in the normal list. Very odd as i've checked my softcam and the keys are ok for P 9E0008 00.


    All channels working fine - double check your config.

    With this fork, you do no need to use stream relay anymore, just make a normal dvbapi/capmt connection to oscam-emu and the channels will work like any other scrambled channels.


    see here: http://linuxsat-support.com/sh…ight=tvheadend+mode+oscam


    or here: http://linuxsat-support.com/showthread.php/99348-OScam-config-dvbapi?p=316382&viewfull=1#post316382


    or here: http://linuxsat-support.com/showthread.php/73231-vdr-dvbapi-Where-is-the-problem?p=337533&viewfull=1#post337533



    BTW - I also just updated my fork with a fix for oscam-tvheadend communication for other versions of oscam-emu. It works, but better is to use my updated oscam-emu. See here:http://linuxsat-support.com/sh…644-OSCam-emu-source-code

    Thank you very much for great work.



    2016-06-13 18:50:22.482 http: 127.0.0.1: HTTP/1.1 GET /bysid/4 -- 1
    2016-06-13 18:50:24.579 http: 127.0.0.1: HTTP/1.1 GET /bysid/4 -- 1
    2016-06-13 18:50:26.679 http: 127.0.0.1: HTTP/1.1 GET /bysid/4 -- 1



    "bysid" is only for use with mumudvb, not tvheadend...


    - - - Updated - - -


    have installed tvh from deb and then replayced bin file with your from first thred and become this error from OSEmu


    No need to use stream relay anymore, use my tvheadend fork with builtin exteded_cw support:http://linuxsat-support.com/sh…w-functionality-(powervu)

    I created a git svn clone of the oscam source code on github. The main branch (oscam-svn) is just a clone of the streamboard svn repository.


    https://github.com/joeusercz/OSCam-with-emu-branch


    There are also two branches for oscam patched with oscam-emu:


    oscam-emu-merged - has been patched already with the oscam-emu patch, and new changes to oscam-svn are merged into it. This means the commits will show the same changes as the oscam-svn branch. If however a change needs to be made to oscam-emu when conflicts occur, those changes will show up as separate commits. So this branch will show (via commit history) all the changes made for oscam-svn intermingled with any changes made specifically for oscam-emu to work. Although I did not do so yet, in the future I will try to remember to add the svn revision number to the merge commit.


    oscam-emu-rebased - is just that, a branch rebased from the oscam-svn branch. Which means it resets all the commits and then applies the oscam-emu commit at the end. So the last commit will essentially be the oscam-emu patch. ( If a conflict occurs, the changes will be made and included in the commit.) In fact the final commit can be downloaded as a patch if you grab the link for the commit and add '.patch" to the URL. For example, currently the last commit is here:


    Code
    https://github.com/joeusercz/OSCam-with-emu-branch/commit/aa2f6684ec1df125e54e7aef0616e03df2e8ec79


    So, if you want to download it as a patch, append ".patch" as follows:


    Code
    https://github.com/joeusercz/OSCam-with-emu-branch/commit/aa2f6684ec1df125e54e7aef0616e03df2e8ec79.patch


    Code
    wget -O oscam-emu.patch https://github.com/joeusercz/OSCam-with-emu-branch/commit/aa2f6684ec1df125e54e7aef0616e03df2e8ec79.patch


    Then you will have a patch which can be applied.


    !!! Note: the patch created this way needs to be applied with the "-p1" option instead of the usual "-p0" option. Unfortunately this makes it difficult to use with simplebuild (although it is fairly easy to modify simplebuild...)


    Please, please, please DO NOT pester me (and more importantly the entire forum) with update requests. I will try to keep it updated, but I will not always have time. I will see about making some scripts to automate the updates, but in reality the vast majority of time that people are looking for the latest oscam-emu is because the current patch no longer cleanly applies to the latest oscam-svn revision - and in this case, the automated update will fail and have to be hand tweeked anyway.


    - - - Updated - - -


    BTW - if you want to use simplebuld without modifying it, you can try this trick.


    In one terminal, start simplebuild:

    Code
    ./s3 menu


    select "continue with local svn revision xxxxx"


    Then in another terminal do the following:

    Code
    mv oscam-svn oscam-svn.sv
    git clone  -b oscam-emu-merged https://github.com/joeusercz/OSCam-with-emu-branch.git oscam-svn


    Then back in first terminal choose your toolchain and options and build.
    (make sure in build extra options you do not have use patch enabled.)


    This will make binaries with no svn version in the filename. To include the svn version from the oscam-svn, try the following:


    In one terminal, start simplebuild:

    Code
    ./s3 menu


    select "continue with local svn revision xxxxx"


    Then in another terminal do the following:

    Code
    cd oscam-svn
    git init .
    git remote add origin https://github.com/joeusercz/OSCam-with-emu-branch.git
    git pull origin oscam-emu-merged


    Then back in first terminal choose your toolchain and options and build.
    (make sure in build extra options you do not have use patch enabled.)


    This method overwrites all the oscam files with the patched/added oscam-emu files, but keeps the svn information. With this method, you can restart s3 and build again without loosing your oscam-emu files. (until the server svn revision changes...)

    Either the file did not get extracted from the compressed tar correctly, or the architecture is wrong...

    Quote

    oscam-svn11289-mipsel-webif-dvbapi: ELF 32-bit LSB executable, MIPS, MIPS-I version 1 (SYSV), dynamically linked, interpreter /lib/ld.so.1, stripped


    I built new drivers for my alien2 to extend the number of pids that can be simultaneously descrambled is 9, then used the modified oscam to limit each channel to 3 pids (video, plus two audio tracks) and I was able to record two channels and watch a third without problem. I have no idea how to modify the dreambox drivers, but if you limit the number of pids oscam indexes, you should be able to at least record one channel and watch another...


    I also modified oscam so that if it gets an ioctl error when trying to set too many keys, it just removes the current pid and not remove all the pids (which is the default action...)


    Also you did not post the oscam logs with debug level of 128...