Posts by joeuser

    Yes, I doubt it is a signal problem, but mumudvb will indicate when the client (oscam-emu/OSEmu) is not acking packets. If you start mumudvb like:

    Code
    mumudvb -v -s -d -c mumu_init.conf

    Then it will show you messages when it is buffering. It says something like "cannot send, buffering" then "can send again" (I don't remember exact messages.)


    What settings did you use for oscam.server? Also, since you have the ECM pid in the stream you can disable dvbapi in oscam.conf.

    I don't know why iptv would need the time set before it works. But you can set some sat channel as the startup service. (In channel list press menu and select "set as startup service" ) Or you can setup an ntp client to get the time from the internet, but it varies from image to image on how to do it...

    Looks like it is missing some packets, is mumudvb buffering and dropping packets?
    When you start oscam-emu what does it say is the ffdecsa parallel mode? If it is not 128, you should recompile with the option

    Code
    make EXTRA_CC_OPTS='-DPARALLEL_MODE=PARALLEL_128_SSE2'

    Boa noite joeuser sou do brazil, teria um tutorial para configuração de instalação do plugin_mcas para abrir os canais em Power Vu no AZBOX PREMIUM HD com frimware original / fw 5402. tenho algumas chaves PowerVu banda C aqui em meu país. grato e se possível no seu aguardo


    Sorry I only know of this mcas for spark (sh4 box) - I have not seen a new version for azbox. You can try installing enigma2 and use oscam-emu.

    1) Newest version may help - there were some changes to buffers and a few fixes for occasional non-decrypted audio packets getting by. In VLC, you can look in tools->messages and set Verbosity to "2(debug)" to see what is going on.
    2) Could be related to the forking - again the newest version with threading may fix. If not let me know.

    oscam.keys is used by the closed source oscam-ymod.
    The open source oscam-emu patch modifies the original oscam source code and uses SoftCam.key - which can be included in the binary during build and/or read from the same directory which contains the oscam configuration files.

    Thanks for your reply. Actually I set up a streaming server using mumudvb together with OSEmu like you described in another forum. For comparing I tried to compile my own oscam-emu on my Debian Jessie PC using the latest oscam from svn plus the patch but it fails patching the webif part and than later compiling fails, too. That's why I wondered if it's worth the effort as the only thing I lack with OSEmu is AU, presuming I really have a working EMM key, of course. Good to know about multiple client support so I will try again to get a working oscam-emu on my PC.


    The patch on github is not regularly updated. I will post the latest patch here.
    Streamboard seems to be down (again) but I posted here last night in another thread the latest oscam-svn I checked out.


    - - - Updated - - -


    PVu AU does NOT work with oscam-emu. The EMM stream does not appear to parsed correctly or even at all.


    You can try posting an issue on github with any relevant info you have.

    Thanks for updating status, but i really do not see how the boot loader would affect the tuners??? Either it boots to enigma or not... Strange problem, unfortunately without serial console output not easy to even guess the problem.

    First of all, while I have seen there is code in both for EMM/AU processing, I have not done any testing with AU so my thoughts are mostly speculative. Most of the channels I have tested it with have not changed keys. OSEmu will be limited to what is in the stream and what it receives from oscam via camd protocol. Oscam-emu has more direct access to dvbapi, so it may be more likely to get results. Have you tried playing with the emmcache settings?


    Both now support multiple clients. They have fixed my forking "hack" with a real threaded implementation.

    I see here is a now a new forum for OSEmu, which is nice, but could be confusing for people. In fact there are two closely related, but separate projects - OSemu and oscam-emu. They share mostly the same code, but function differently.


    OSEmu is a standalone application which can be used as a reader for another emulator using the cs357x (camd35 UDP) protocol. (Or in the case of powervu, it can be used as just a standalone stream relay application.)


    Oscam-emu is a patch which can be applied to the oscam source code to give oscam the added OSEmu functionality (softcam.)


    Github sources (and basic tutorials)
    OSEmu is here: https://github.com/oscam-emu/OSEmu
    Oscam-emu is here: https://github.com/oscam-emu/oscam-emu


    I am not sure of the best way to separate them here. Maybe rename the forum to "Oscam-emu/OSEMU" and make 6 sub-forums :


    OSEmu Support
    OSEmu Tutorials, HowTo & Guides
    OSEmu Files


    Oscam-emu Support
    Oscam-emu Tutorials, HowTo & Guides
    Oscam-emu Files


    I write this because even on the oscam forum there is often confusion between the two...