OSEmu - oscam-emu differences

There are 17 replies in this Thread which was already clicked 8,928 times. The last Post () by joeuser.

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

    Thanks for your explanation, very informative.


    Do both variants actually support PowerVu AU? I've been trying to use it with OSEmu (option -e and having the EMM key in SoftCam.Key) but it didn't work. Maybe oscam-emu is better? But does it also support multiple streaming clients like OSEmu?

    Edited once, last by Purrfect ().

    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.

    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.

    Quote from Purrfect

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


    Quote from 007.4

    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.

    I managed to patch and compile oscam-emu now! The problem was the patch not being compatible with the latest version of oscam-svn. Instead I got the sources of version 10943 by using "svn co http://www.oscam.cc/svn/oscam-mirror/trunk oscam-svn -r10943" as streamboard is down presently. I can confirm that PowerVu AU works with oscam-emu like a charm.

    Ok! In my setup I use it only for my PowerVu reception of one "exotic" C-band transponder. But after running my installation for a few hours I noticed the following:


    1) Sporadically I notice annoying glitches using oscam-emu and VLC while OSEmu doesn't have this problem. How to improove this? I would really like to stay with oscam-emu as it has a web gui telling what's going on.


    2) The transponder stream supplied by mumudvb in my case contains 7 stations / sids all using the same ECM's but only the station having the lowest SID is doing AU, this others are just doing nothing. This is not a big problem as they're all using the same ECM keys so I can manually copy it to the other ids but this could be nicer. ;-)


    I noticed the emu-patch was updated today so I will move to the latest oscam-svn tomorrow. Maybe this will improove things further.

    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.

    root@streamer:~# /usr/bin/oscam -V
    Version: oscam-1.20-unstable_svn-r10991


    There are still glitches. Here's what VLC tells about:


    [h264 @ 03aeee20] Reference 3 >= 2
    [h264 @ 03aeee20] error while decoding MB 11 22, bytestream 58
    [h264 @ 03af2aa0] left block unavailable for requested intra4x4 mode -1 at 0 26
    [h264 @ 03af2aa0] error while decoding MB 0 26, bytestream 3878
    [h264 @ 03aecde0] Reference 2 >= 2
    [h264 @ 03aecde0] error while decoding MB 4 16, bytestream 8703
    [h264 @ 03af2aa0] Reference 3 >= 2
    [h264 @ 03af2aa0] error while decoding MB 12 12, bytestream 14366
    [h264 @ 03af2aa0] left block unavailable for requested intra4x4 mode -1 at 0 8
    [h264 @ 03af2aa0] error while decoding MB 0 8, bytestream 43907
    [h264 @ 03aecde0] error while decoding MB 23 28, bytestream -5
    [h264 @ 03aeee20] left block unavailable for requested intra4x4 mode -1 at 0 27
    [h264 @ 03aeee20] error while decoding MB 0 26, bytestream 7070
    [h264 @ 03aeee20] cabac decode of qscale diff failed at 2 26
    [h264 @ 03aeee20] error while decoding MB 2 26, bytestream 504
    [h264 @ 03aeee20] Reference 2 >= 2
    [h264 @ 03aeee20] error while decoding MB 41 6, bytestream 20388
    [h264 @ 03af2aa0] Reference 3 >= 2
    [h264 @ 03af2aa0] error while decoding MB 4 6, bytestream 2643
    [h264 @ 03af2aa0] left block unavailable for requested intra mode at 0 26
    [h264 @ 03af2aa0] error while decoding MB 0 26, bytestream 1703
    [h264 @ 03aecde0] error while decoding MB 3 28, bytestream -10
    [h264 @ 03af2aa0] Reference 2 >= 2
    [h264 @ 03af2aa0] error while decoding MB 28 14, bytestream 8728
    [h264 @ 03af2aa0] Reference 2 >= 2
    [h264 @ 03af2aa0] error while decoding MB 27 12, bytestream 2325
    [h264 @ 03af2aa0] Reference 2 >= 2
    [h264 @ 03af2aa0] error while decoding MB 24 6, bytestream 16140
    [h264 @ 03af2aa0] cabac decode of qscale diff failed at 18 21
    [h264 @ 03af2aa0] error while decoding MB 18 20, bytestream 547
    [h264 @ 03aed600] left block unavailable for requested intra4x4 mode -1 at 0 27
    [h264 @ 03aed600] error while decoding MB 0 26, bytestream 171
    [h264 @ 03aeee20] cabac decode of qscale diff failed at 20 26
    [h264 @ 03aeee20] error while decoding MB 20 26, bytestream 3114
    [h264 @ 03af2aa0] left block unavailable for requested intra4x4 mode -1 at 0 22
    [h264 @ 03af2aa0] error while decoding MB 0 22, bytestream 18487
    [h264 @ 03aed600] Reference 2 >= 2
    [h264 @ 03aed600] error while decoding MB 25 26, bytestream 2699
    [h264 @ 03af2aa0] error while decoding MB 39 28, bytestream -11
    [h264 @ 03aecde0] Reference 2 >= 2
    [h264 @ 03aecde0] error while decoding MB 1 28, bytestream 606
    [h264 @ 03aeee20] error while decoding MB 21 28, bytestream -21
    [h264 @ 03af2aa0] Reference 2 >= 2
    [h264 @ 03af2aa0] error while decoding MB 29 24, bytestream 930
    [h264 @ 03aeee20] Reference 2 >= 2
    [h264 @ 03aeee20] error while decoding MB 29 6, bytestream 6005
    [h264 @ 03aed600] left block unavailable for requested intra4x4 mode -1 at 0 7
    [h264 @ 03aed600] error while decoding MB 0 6, bytestream 22655
    [h264 @ 03aed600] cabac decode of qscale diff failed at 23 17
    [h264 @ 03aed600] error while decoding MB 23 16, bytestream 13490
    [h264 @ 03aed600] Reference 2 >= 2
    [h264 @ 03aed600] error while decoding MB 10 16, bytestream 13200
    [h264 @ 03aed600] Reference 2 >= 2
    [h264 @ 03aed600] error while decoding MB 12 28, bytestream 49
    [h264 @ 03af2aa0] Reference 2 >= 2
    [h264 @ 03af2aa0] error while decoding MB 9 28, bytestream 802
    [h264 @ 03af2aa0] top block unavailable for requested intra4x4 mode -1 at 43 0
    [h264 @ 03af2aa0] error while decoding MB 43 0, bytestream 17126
    [h264 @ 03aecde0] reference picture missing during reorder
    [h264 @ 03aecde0] Missing reference picture, default is 75318
    [h264 @ 03aed600] reference picture missing during reorder
    [h264 @ 03aed600] Missing reference picture, default is 75328


    I hope the log is useful. If I can support the project please just tell me what to test. :-)


    Greetings,
    Purrfect

    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'

    How can I figure out if mumudvb is buffering? On its webgui the BER is always "0". My oscam-emu was compiled using this said option already. With OSEmu there are no glitches at all so I think my satellite reception is good enough. It looks like some timing problem, I think, as it's happening every 10-15 seconds, approximately.

    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.

    Mumudvb is happy not reporting errors:


    Info: DVB: Bit error rate: 0 Signal strength: 13464 SNR: 19650 Uncorrected blocks: 0
    Info: DVB: ts_discontinuities 0


    But when using oscam-emu (r10991), VLC is complaining about encrypted packages occasionally causing the glitches. I made two log files playing the same channel. Once using oscam-emu and then OSEmu. Both show "lost synchro" but this doesn't seem to disturb VLC.


    My oscam.server file looks like this:


    [reader]
    label = emulator
    protocol = emu
    device = emulator
    caid = 0E00
    detect = cd
    ident = 0E00:000000
    group = 1
    emmcache = 1,1,2,1
    saveemm-unknown = 1
    saveemm-u = 1
    saveemm-s = 1
    saveemm-g = 1
    emu_auproviders = 0E00:000000


    When I disable dvapi then my AU doesn't work, as the SID2 which I know it is working is not showing up on mumudvb as being a radio station. Is that normal? With dvapi enabled, oscam-emu receives all SIDs at once including SID2 and AU works, but only for this SID.

    Yes, it looks like some packets are not being decrypted. Are you using the 10991 patch posted here:http://linuxsat-support.com/showthread.php?t=92619
    There was a problem a few revisions prior, but since the latest changes, I have not seen any encrypted packets with vlc. If you are using the above patch already, then I can make a debug version so we can see what is going on...


    And yes, dvbapi will be needed for au, I just wanted you to try without to see if it was the problem...


    Are you using:

    Code
    rewrite_sdt=1
rewrite_pat=1


    in your mumudvb conf?

    Edited 2 times, last by joeuser ().

    I used exactly this patch which worked seamlessly together with oscam svn. Maybe a debug version could help. Thanks for the explanation about AU and dvapi. I think it's not clever to send all SIDs to oscam all the time as it keeps on decrypting all channels in a stream even if noone is watching. This keeps the CPU busy always. And yes, I have those options in my mumudvb conf already as I used your "mumu_init.auto.2.afn.conf" as a template. Thanks for your help, by the way. Have a nice weekend. :-)

OSCam-EMU Support Forum

Configs, discussion, downloads and guides for OSCam-EMU Softcam.

Participate now!

Don’t have an account yet? Register yourself now and be a part of our community!

Register Yourself Login