Posts by joeuser

    My latest changes.


    Includes:
    Increase powervu stream relay total combined audio and subtitle tracks to 16 (limit was 4 previously.)


    Plus:
    a few possible resource leak/memory leak fixes (thanks to tanaseiv)
    some compiler warning fixes


    Note - not updated on github yet. If no one reports problems I will create a pull request later.

    Thanks again for the tip! I couldn't get it working with my 85cm dish, but on the 60cm dish it is working "ok" with the old LNB. It took 30min of tweaking back and forth and adjusting the skew to find the sweet spot in between. I get bit errors on both sats, but no uncorrected blocks. Hopefully with a new, good twin LNB, I will get a better signal on both sats...

    Last year I helped a friend get his cable working, although not on your box and not OpenATV. Cable scan was not working. Finally we did a manual scan with parameters for one transponder and selected "network scan" to find all channels. We used this website to find out the details for his area: http://helpdesk.kdgforum.de/sendb/belegung.html Pick one transponder and use its frequency, QAM mode and symbol rate (probably 6900.)


    In tuner configuration, we set
    Network ID = "00000"
    Used Service Scan Type = "Frequency/bands"
    Scan EU .... = all yes
    Scan US ... = all no
    Scan QAM 64 = yes
    Scan QAM 256 = yes
    Scan SR6900 = yes


    Others set to no

    Thanks, I did not think to try that. They are 7e and 9e, but one would be connected to my alien2 and the other to my linux pc. But possibly I could use a good twin tuner...


    Yes, the whole system looks good, but this is just to play with for powervu - and who knows how long it will last. ;) So I wasn't planning on spending too much.


    I will experiment a bit with what I have and see if I can get good enough reception for both sats without moving the dish. And actually in this case, my smaller dish may work better... :)

    Thanks for the info Prophet. Actually, my original plan was to just upgrade the old cheap single LNB on my motorized dish with a twin black ultra for those "fringe area" satellites. But when I was looking for which LNB, I stumbled across the multi LNBS and got the idea of using them on my fixed dish. Do you recall when you had them on the smaller dish, how close together the 19.2 and 23.5 LNBs were? That is 4 degrees and I would need half that, so do you think another LNB could have fit between them? I am still planning on ordering the twin black ultra, just not sure about a couple of multis also.


    BTW - are you using the Inverto multi bracket? I am also debating on whether or not to buy it - it cost more than the two multi LNBs combined. I have been quite creative a few times in the past connecting two LNBs with various spare parts... :)

    Does anyone have experience with the Inverto Multi (slim) LNBs? I am guessing from the price that the performance is not great, but that is probably not an issue for me. I am looking to receive two satellites which are just 2 degrees apart. I can pick each of them up separately now with pretty good signal with an old 60cm dish and a very old no-name LNB. The specs say from 2-30 degrees, but the bracket is marked at 3 degree intervals. My question is, how big of a dish will I need to get just 2 degrees separation? I am guessing that the 60cm dish will not be enough, but maybe an 80cm would? I could do the math, but real world experience is always more helpful. :)


    http://www.inverto.tv/products/product.php?id=111&typ=52
    http://www.inverto.tv/products/product.php?section=1&id=70

    I just saw tonight the references to twin in the oscam changelog. Have you tried it yet? I think this is the correct build for your box, but I have no way to test it. It is the latest oscam without any changes. If it works for you, we can see about making the above patch...


    Also attached is the version you posted "as is" to see the basics are working before trying to make any changes... :)

    thanks joeuser on the telnet top command, never used that before


    just did it on mine and 2 came up top (lol)


    one was usr/local/bin/enigma2 with about 1% ish and less but the biggest was one called button/0 with 6%


    Unfortunately most plugins just show up as enigma2, so hard to debug plugin problems...


    BTW - if you press "H" it will also show all threads.


    Also, haven't gotten around to find out why button always uses so much cpu - but on my list of things to do!

    I am currently testing the latest Spark (1.2.80) and I do not find it any faster at changing channels or displaying info bar than my HDMU or OpenSPA images I usually use. I do not have a lot of plugins installed though, so maybe that is the difference??? Have you tried installing the latest HDMU image directly from HDMU ( not a backup image )? As a start, you can try telneting to the box and running "top" to see if anything is using a lot of cpu. I occasionally see a spinner, but never when changing channels (unless the motor needs to move...)

    If the file is being updated by oscam, then there must be some problem that it doesn't have permissions to create the file, only update, which is strange.
    The executable is probably in /var/emu - are you both using the same version of oscam? Which version? Have you tried connecting to the webif (http://box_ip:8888) to see the logs?

    Yes, I understand all tmp files are cleared on reboot, but does the file get updated by oscam after you copy it to his box? (Does the time change just like on your box?)
    Depending on which enigma2 you have installed, there are differences in how they start up oscam.

    Tested on a (Debian Wheezy 64bit) Linux PC with an old Skystar2 (DVB-S only) pci card. I assume you have a working card/usb tuner and a basic build environment already setup. Or, if you don't want to build your own, you can try the attached binaries.


    MuMuDVB is a streaming server which can stream via multicast and/or unicast (http). I disable the multicast and use just the http streaming. It uses the default port of 4242 to listen for connections. The feature I use is a url with the sid of the channel you want to watch. (e.g. http://127.0.0.1:4242/bysid/2) So, I have made a patch for oscam-emu/OSEmu to translate the usual powervu stream relay http request url (e.g. http://192.168.1.12:17999/1:0:1:2:1:9:5A0000:0:0:0:) which is made to osemu's stream relay to the "bysid" format. So the basic path is from stb/vlc/(any video stream client) via http to OSEmu port 17999, which then does an http connection to MuMuDVB for the desired sid which then streams back the channel (including ecm pid) to OSEmu which decrypts the stream and sends it to the requesting client. Since I am using this mostly with the AFN channels on 9E, I also made a patch to allow multiple clients to connect at the same time to the same or different channels. (Made possible by the fact that all the channels are on the same transponder.) It is also useful for the 4W HBO package...


    Here is a basic howto.


    1. Download OSEmu


    Code
    git clone https://github.com/oscam-emu/OSEmu.git


    Basic instructions for building/use are here: https://github.com/oscam-emu/OSEmu



    (or optionally you can use oscam-svn with oscam_emu patch)



    3. Add the following changes to request correct channel by sid from MuMuDVB: (tested with both oscam_emu and OSEMU...)




    4. Command-line for OSEMU

    Code
    ./OSEmu -v -a user:pass -p1234 -s 127.0.0.1 -r 4242:17999


    5. Install MuMuDVB
    (I have tested with version 1.7.1 installed with "apt-get install mumudvb" on Debian, and also built/tested 1.7.3 and 2.0. All work ok, but beware that some of the config options are slightly different between versions....)
    https://github.com/braice/MuMuDVB


    6. Example configuration file for MuMuDVB. Default is for adapter0, you may need to change to reflect your hardware.
    http://www.mumudvb.net/doc/mumudvb-2.0.0/README_CONF.html


    7. I made some patches for MuMuDVB to enable autconfigure to find and add the ECM pids. Here are the patches, or you can use the included binary....


    8. Example configuration file for MuMuDVB with autoconfiguration


    9. Some example playlists and user bouquet files.
    VLC playlist:


    userbouquet.HBO.tv


    10. Included in the attached tar:


    OSEmu directory containing latest source code already modified with bysid patch and a 64bit binary.
    MuMuDVB directory containing latest source code already modified with ecm pid autoconfig patch and a 64bit binary.
    Example playlists and user bouquets.
    Start scripts for OSEmu and MuMuDVB with example command line options.


    - - - Updated - - -


    I forgot to add that since osemu now supports multiple clients, you can watch/record all channels on the same transponder at the same time - including the same channel on multiple devices at the same time. the Only limit is your cpu and network bandwidth....