hdmu center->system control, switch c to t
Then you must restart box to take affect.
hdmu center->system control, switch c to t
Then you must restart box to take affect.
Did you try realigning your new dish on 19.2 like suggested before?
Have you tried adjusting the skew of the 13e lnb?
Have you tried swapping inputs to your diseqc switch?
Have you tried replacing the diseqc switch with a simple male/male adapter (to test both cables together)?
Like I wrote I have not tried it.
But here is the latest version.
You can try asking for support from the original author on oscam website:http://www.streamboard.tv/wbb2/thread.php?threadid=42677
QuoteDisplay Morev0.13:
Fixed MDAPI Plus timing issue on plugin init
v0.14:
Added DVBViewer plugin menu entry to activate/deactivate mdvbapi
Changed caPMT list item to dynamic size by PMT size
Changed socket handling
Changed internal IPC handling
Changed filter handling
Fixed DVBViewer timing issue on plugin init
Fixed filter to be able to filter PMT pid and PAT pid
Added filter crc32 check on data with section_syntax_indicator flag
Added one shot cache on filter data, cache get cleared by changing/removing the filter
Fixed filter to filter data splitted in packets with PUSI flag
Changed default number of adapters to 16, can be changed by setting the parameter adapters=< number of adapters > in the ini file
Fixed blocking deadlock on shutdown by Sendmessage
Added support of KeepAlive and 188 byte mode on filter data with MDAPI Plus version equal or higher than 0.9.0.1615
v0.14.1
Hotfix for creating caPMT item by PMT size between 245 to 267 bytes
v0.14.2
Hotfix for MDAPI 184 byte filter
v0.15
Added ProgDVB MDAPI 188 byte mode
Added special 188 byte mode for DVBLink/TVSource MDAPI
Changed at mdvbapi.ini "ip" to "host", it will be changed automatically on the first start
Added IPv6 support, see HowTo at "mdvbapi.ini"
v0.15.1
Hotfix for overlapped socket receive
v0.15.2
Fixed FFdecsa SSE2_128 boost for INT_32 mode
v0.16
Removed MMX64 version because of working SSE2_128
SSE2_128 FFdecsa performance improvement: +65% against original INT_32 (again +10% to v0.09)
Added special SSE2_128 FFdecsa version for SAT>IP: +105% against original INT_32
Fixed socket receive
This is a dvbapi plugin for the DVBViewer Recording Service or an MDAPI DVB software.
It will work also with DVBViewer but it is optimized for the DVBViewer Recording Service.
You can get the DVBViewer Recording Service at http://www.dvbviewer.com.
v0.17
Fixed possible crash on closing the plugin
Changed config folder destination to %ALLUSERSPROFILE%\mdvbapi (example: C:\ProgramData\mdvbapi).
Existing config mdvbapi.ini or mdvbapi.log is getting moved to the new config folder on the first start.
How to install:
The INI-File:
%ALLUSERSPROFILE%\mdvbapi (example: C:\ProgramData\mdvbapi)
There is only one INI-File for all mdvbapi.dll plugins which make it easier for the user.
DVBViewer Recording Service:
Install DVBViewer and DVBViewer Recording Service on the PC.
The plugin(s) have to be in ../DVBViewer/Plugins/Plugins[1 - 32]
For each tuner one plugin folder is used.
So if you have 4 tuners in DVBViewer Recording Service you will have folder "Plugins1" to "Plugins4".
DVBViewer:
Install DVBViewer on the PC.
The plugin have to be in ../DVBViewer/Plugins
The plugin makes a connection to oscam dvbapi by a inet socket TCP.
mdvbapi.ini:
Section:
[oscam]
host=< hostname, IPv4 or IPv6 where oscam can be reached >
port=< listen_port of the oscam dvbapi >
[options]
debug=< debug level in decimal >
active=< 0 to deactivate, 1 to activate (Default) >
adapters=< number of adapters, adapter number have to be between 2 to 65, default 16 >
IPv6=< 0 to use IPv4 (Default), 1 to use IPv6 >
Please take a look to oscam wiki:
http://www.streamboard.tv/wiki/OSCam/en/...cam.conf#DVBapi
Possible debug values:
D_PLUGIN 0x0001 1 Log transfer from/to DVB software
D_FILTER 0x0002 2 Log filter actions
D_OSCAM 0x0004 4 Log transfer from/to oscam
D_DECSA 0x0008 8 Log FFdecsa infos
D_PIPE 0x0010 16 Log internal pipe transfer
D_ECMINFO 0x0020 32 Log ECM infos provided by oscam
Example for debug level:
D_PLUGIN and D_OSCAM: 1 OR 4 == 5
The log file is saved in %ALLUSERSPROFILE%\mdvbapi (example: C:\ProgramData\mdvbapi).
oscam:
You will need a oscam supporting dvbapi protocol minimum 1.
About the FFdecsa boost:
As the INT_32 mode is the mode with the lowest CPU usage for live TV this mode got modfied with SSE2_128 instructions.
Like there are a lot of loops handling 4 single integers these loops where be replaced by a single SSE2 instruction.
Fore sure the original SSE2 version will be the fastest but the CPU usage against INT_32 will be 2-6 times higher.
With these modifications this leeds to a speed improvement +65% against the original INT_32 mode for standard packet count.
For low packet count (maximum 7 TS packets) the SAT>IP SSE2 version code got optimized again and this leeds
to +105% against the original INT_32 mode. But using this version for other DVB hardware with more than 7 TS packets
will lead to a lower performance than the SSE2 modified for standard packet count version.
Tests on a low power Atom CPU with ~15MBit/s
Original INT_32 mode: ~55-65% CPU usage
INT_32 with SSE2 mode: ~35-45% CPU usage
INT_32 with SSE2 SAT>IP mode: ~20-30% CPU usage
Release Notes for v1.2.83:
Improvements:
- Improved YouPorn playback support
I have not tried it, just noticed it was not posted here yet even though it is almost a year old...
There is a know problem with some drivers which do not properly switch back to CSA mode after doing DES decryption. Unfortunately there is nothing that oscam can do about it...
im experience some trouble when i installed oscam i get powervu on my dm7080 but when i change to other system the screen is bkack i mean or wors powervy or works the other systems not the 2 at the same time
where do i see the groupid to setup my auto roll powervu SoftCam.Key on dm? help
the groupid is just something you make up to group all the same channels which use the same keys together (ecm +UA) That way, when a new key is found, oscam-emu knows which keys need to be updated..
My code was kinda a quick hack with limited testing. It is quite possible it is crashing if keys are changing every 30min... :)
Try using the latest "official" oscam-emu/osemu - they have incorporated all my changes and probably did a better job... :)
(as a bonus, they also added Tandberg...)
Display MoreFound this in log after oscam frozen,does anyone know how to sort my oscam freezing every half hour ??
CodeDisplay More14:57:42 718471B1 r [Emu] Key found in EMM: P 0001 00 XXXXXXXXXXXXXX ; UA: XXXXX 6 2 718471B1 r writing key file: /etc/tuxbox/config/oscam/SoftCam.Key 718471B1 r [Emu] Key written: P 000100XX 01 XXXXXXXXXXXXXX 718471B1 r writing key file: /etc/tuxbox/config/oscam/SoftCam.Key 718471B1 r [Emu] Key written: P 000100XX 01 XXXXXXXXXXXXXX 718471B1 r writing key file: /etc/tuxbox/config/oscam/SoftCam.Key 718471B1 r [Emu] Key written: P 000100XX 01 XXXXXXXXXXXXXX 1D614F96 c (reader) emulator [emu] Successfully added EMM to /var/etc /log/emulator_unique_emm.log 718471B1 r writing key file: /etc/tuxbox/config/oscam/SoftCam.Key 718471B1 r [Emu] Key written: P 000100XX 01 XXXXXXXXXXXXXX 718471B1 r writing key file: /etc/tuxbox/config/oscam/SoftCam.Key 718471B1 r [Emu] Key written: P 000100XX 01 XXXXXXXXXXXXXX 718471B1 r writing key file: /etc/tuxbox/config/oscam/SoftCam.Key 718471B1 r [Emu] Key written: P 000100XX 01 XXXXXXXXXXXXXX 718471B1 r writing key file: /etc/tuxbox/config/oscam/SoftCam.Key 718471B1 r [Emu] Key written: P 000100XX 01 XXXXXXXXXXXXXX 718471B1 r writing key file: /etc/tuxbox/config/oscam/SoftCam.Key 718471B1 r [Emu] Key written: P 000100XX 01 XXXXXXXXXXXXXX 718471B1 r writing key file: /etc/tuxbox/config/oscam/SoftCam.Key 718471B1 r [Emu] Key written: P 000100XX 01 XXXXXXXXXXXXXX *** Error in `./oscam': free(): invalid pointer: 0x77013358 *** root@zgemma-star-2s:/usr/bin#
Please someone help me,are going mad rebooting this fooking box !
cheers
- - - Updated - - -
Or maybe a script to monitor that oscam is still running,and restart if it has stopped ?
somebody please point me in the right direction.
cheers
Sorry, not much free time lately, but I finally got around to adjusting the script...
You can try this for the VLC playlist.
/#!/bin/bash
# you must have installed jq (apt-get install jq)
############### BEGIN CONFIG ###################
tvh_data_path="/home/hts/.hts"
OSEmu="192.168.1.11:17999"
profile="PowerVU"
userpass="pvu:pvu"
############### END CONFIG ###################
wget -O /tmp/services.json http://admin:admin@localhost:9981/api/mpegts/service/grid?limit=100000
echo \#EXTM3U
entries=$(/usr/bin/jq -c '.total' /tmp/services.json)
for (( service=0; service<= $entries; service++ ))
do
if [ $(/usr/bin/jq -c '.entries['$service'].caid' /tmp/services.json) = '"0E00:000000"' ]
then
enabled=$(/usr/bin/jq -c '.entries['$service'].enabled' /tmp/services.json)
if [ '$enabled' = 'true' ]
then
svcname=$(/usr/bin/jq -c -r '.entries['$service'].svcname' /tmp/services.json)
uuid=$(/usr/bin/jq -c -r '.entries['$service'].uuid' /tmp/services.json)
network=$(/usr/bin/jq -c -r '.entries['$service'].network' /tmp/services.json)
multiplex=$(/usr/bin/jq -c -r '.entries['$service'].multiplex' /tmp/services.json)
sid_dec=$(/usr/bin/jq -c '.entries['$service'].sid' /tmp/services.json)
sid=$(printf '%x' $sid_dec)
desc="$network/$multiplex/$svcname"
echo \#EXTINF:-1, $desc
echo http://$userpass@$OSEmu/stream/service/$uuid\?profile=$profile\&descramble=0\&emm=1\&:0:0:$sid
fi
fi
done
Display More
Something similar can be done for creating userbouquets. I can post later when I get some more free time...
Sorry I did not see your first post earlier, but glad you got it sorted and better yet, that you posted the solution, which many people do not bother doing...
Display Morejoeuser , can help me to apply patch for mumudvb?
i receiving this message
patch < ../pat.patch
patching file module-emulator-stream.c
Hunk #1 succeeded at 1626 with fuzz 2 (offset 1105 lines).
Hunk #2 FAILED at 549.
Hunk #3 FAILED at 715.
2 out of 3 hunks FAILED -- saving rejects to file module-emulator-stream.c.rej
You should post in this thread (http://linuxsat-support.com/showthread.php?t=90369) for issues with MuMuDVB.
What exactly are you trying to patch? Oscam or Osemu - version??
If you want to try an easier route first, you can look in the backup images thread (http://linuxsat-support.com/forumdisplay.php?f=477) and try an image which has already been pre-configured. Pauldb's HDMU image, or Champions OpenATv, or Fano's Hyperion should all be stable. Other's probably as well, but I never tested them. It is a good way to try out different images fairly quickly to get an idea of what you like/don't like. Later you can install one from scratch and configure to your own taste. (Or of course reconfigure one of the backup images...)
Now added:
Quotesimplebuild 2.45 + config 1.48
-add solo4k for VU+ Solo 4K
-add arm_v7 for:
DS114 DS115j DS213j DS214 DS214+ DS214se
DS216DS216j DS216se DS414 DS414slim
DS416j DS416slim EDS14 RS214 RS814 RS815 and many more
More info/logs might help...
Please give the method to use it in vu + solo2 stb (power vu)
You need to use stream relay. Look here for details: http://linuxsat-support.com/showthread.php?t=88764
There is already info on this site for setting up oscam on a linux pc and about using oscam with tvheadend. Do you have some specific questions?
You can try telneting to each box and running "top" - it will show you what is using CPU. But 20-30ms is not a problem at all.
I am not sure what you are asking. It works and you only want to reduce response times? Or it doesn't work and you think response times are the problem?
I built openatv about a week ago from github sources and it was ok (but only did a quick test.) They are based on oe-alliance, but I don't see any changes there to drivers for alien2.
If you are testing a lot, a serial connection is very helpful. I had an extra serial->network adapter from another project that I am using with my box. They are a little expensive, but makes it much easier than running serial cables. You connect a short serial cable to the adapter and connect the adapter to your network and then it can be accessed from anywhere on your net. (also need to change the default bootargs in your flash environment settings so it uses ttyAS0 instead of the default of ttyAS1. "console=ttyAS0")
If your coordinates are entered correctly and you still have problems, perhaps the dish or motor mount has slipped out of position. Big winds?
Checkout the dishpointer link above under "Useful Links".