Streaming over local lan or internet?
For me, the internal player seems to work best. I have also had good results with mxplayer.
Streaming over local lan or internet?
For me, the internal player seems to work best. I have also had good results with mxplayer.
I am now using tvheadend with OSEmu. I have made a few patches to both to get it to work, but it is working well. Unfortunately I do not have much time now to document what I did. Some of the changes are already incorporated into the nightly tvheadend builds, but they have also made some other changes which do similar things but in a slightly different way than my patches. I need to take their latest changes and try to adapt my setup to them. The OSEmu changes are not big, but there were also some recent changes upstream which I need to add (although they should not affect my patches...)
I was on the streamboard site (oscam developers) and noticed this plugin. I have not tested it, but maybe you can give it a try.
http://linuxsat-support.com/showthread.php?t=96338
I have not tested this, but I thought I would upload it here in case anyone is interested in giving it a try...
DVBViewer Recording Service / MDAPI DVB Api Plugin
Version: v0.13
by schwa226
Special THX to Appiemulder the author of Acamd!
v0.03:
Fixed filter & mask issue
Added adaptation field support for filter
v0.04:
Add fix for wrong cluster size in decrypt
Add fix for corrupt data (table len) in EMM data.
v0.05:
Add MDAPI 184/188 Bytes support
v0.06:
Fixed PMT parsing (TNTSat, Digi TV,...)
v0.07:
Code cleanup
Changed plugin name to mdvbapi
v0.08:
Improved tranponder stream handling for decryption
Added SID to PMT filter
v0.09:
FFdecsa performance improvement:
MMX_64: +30%
SSE2_128: +55%
Fixed Long ECM data handling (tested on TNTSat Cherie 25)
v0.10:
Fixed MDAPI filter handling of tables > 181 bytes
Added support for oscam dvbapi protocol 2 (oscam revision equal or higher than 10653 is required)
Added function to filter multiple tables in single ts packet (like ORF)
v0.11:
Fixed FFdecsa memory allocate
Moved filter actions to a separate thread for better performance
v0.12:
Fixed MDAPI Plus support
Performance improvements
v0.13:
Fixed MDAPI Plus timing issue on plugin init
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.
How to install:
The INI-File:
The mdvbapi.ini have to be in the plugins directory like ../DVBViewer/Plugins, ../ProgDVB/Plugins or ../MDPlugins
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]
ip=< ip where oscam can be reached >
port=< listen_port of the oscam dvbapi >
[options]
debug=< debug level in decimal >
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
The log file is saved in ../MDPlugins or ../Plugins directory.
oscam:
You will need a oscam supporting dvbapi protocol 1.
Display More
The latest HDMU images are the most stable for me it has the newest gstreamer. There are some backup images here that people uploaded, but with the old version of gstreamer. You may want to start with one of the backup images and if it is working ok, do an update...
I think the CaptainBlast image is the most recent of the backup images...
Each tuned transponder can have many channels on it - with each channel being view-able/record-able at the same time from just one tuner.
Could be many things, maybe some more info about your config and a debug log file? Which version are you using?
I think for most images, the default setting for the tuner is for DVB-T. Depending on which image, there are different ways to change to DVB-C. The tuner gets configured at boot time, so after any changes the box needs to be rebooted. Not sure about OpenATV, but for PKT there should be an option in the blue panel to change tuner type. (I am not using now, so I can't give you detailed location of the setting...)
After thinking about it, if I remember correctly, for openATV the setting is in a cable scan plugin, or union tuner? Something like that...
BTW, for OpenSPA the setting is in menu->service searching->uniontunertype->
When I get a chance to reboot into HDMU, I will post where the settings are for it....
- - - Updated - - -
For HDMU the setting is under Menu -> HDMU-CENTER -> Tuner control ->
I understand. :) Last year I had a similar problem with HDMU. I ended up telneting to the box and using fp_control to set the clock. Different versions have slightly different options, here is the help from my openspa version:
root@sparktriplex:~# fp_control --help
fp_control: SW Version 1.04
Model: spark7162
vBoxType: 11
Selected Model: Edision Spark frontpanel control utility
Spark_init
config file (/etc/vdstandby.cfg) not found, use standard configconfigs: DISPLAY = 0, DISPLAYCUSTOM = 0, CUSTOM = (null), WAKEUPDECREMENT 300
Spark_usage: not implemented
usage:
fp_control argument [optarg1] [optarg2]
-e --setTimer Args: No arguments or [time date] Format: HH:MM:S S dd-mm-YYYY
Set the most recent timer from e2 or neutrino to the frontcontroller and standby
Set the current frontcontroller wake-up time
-d --shutdown Args: [time date] Format: HH:MM:SS dd-mm-YYYY
Mimics shutdown command. Shutdown receiver via fc at given time.
-g --getTime Args: No arguments
Return current set frontcontroller time
-gs --getTimeAndSet Args: No arguments
Set system time to current frontcontroller time
-gw --getWakeupTime Args: No arguments
Return current wakeup time
-s --setTime Args: time date Format: HH:MM:SS dd-mm-YYYY
Set the current frontcontroller time
-gt --getTimer Args: No arguments
Get the current frontcontroller wake-up time
-r --reboot Args: time date Format: HH:MM:SS dd-mm-YYYY
Reboot receiver via fc at given time
-p --sleep Args: time date Format: HH:MM:SS dd-mm-YYYY
Reboot receiver via fc at given time
-t --settext Args: text
Set text to frontpanel.
-l --setLed Args: led on
Set a led on or off
-i --setIcon Args: icon on
Set an icon on or off
-b --setBrightness Args: brightness
Set display brightness
-P --setPwrLed Args: 0..15
Set PowerLed brightness
-w --getWakeupReason Args: No arguments
Get the wake-up reason
-L --setLight Args: 0/1
Set light
-c --clear Args: No argumens
Clear display, all icons and leds off
-v --version Args: No argumens
Get version from fc
-sf --setFan Args: 0/1
set fan on/off
-sr --setRF Args: 0/1
set rf modulator on/off
-dt --display_timer Args: 0/1
set display time on/off
-tm --time_mode Args: 0/1
toggle 12/24 hour mode
Display More
Of course after setting correctly, there is no guarantee openatv won't "fix" it again. :)
Does the info/epg screens show the correct time? You may have to reboot for it to be corrected (if you did not try already...)
I had OpenSPA running over night and it changed everything ok. (Even the scheduled recordings early this morning were fine.)
Not sure about that setup, and not sure of your location, but for 26e you probably need at least a 1.2 meter dish and probably a better LNB than provided in that package...
I couldn't get a signal for those (although the weather isn't great here and tree's are not helping).
Feeds only active for games, and change each time.
Today
22.10.2015
Europa League
All feed 4:2:2
00h table
PID:1020h B8h-Crypt8:FA 68 81 99 6D A3 2F 60 # CW: XX XX XX XX XX
Eutelsat 7A (7.0°E)
10960 V 9874
Infos: Liverpool - Rubin Kazan
Eutelsat 7A (7.0°E)
10986 H 9874
Infos: Lokomotiv Moscow - Besiktas
Eutelsat 7A (7.0°E)
10961 H 9874
Infos: Lazio - Rosenborg BK
Eutelsat 7A (7.0°E)
11106 V 9874
Infos: FK Gabala - Borussia Dortmund
FTA
Eutelsat 7A (7.0°E)
11009 V 9874
Infos: Partizan Beograd - Athletic Bilbao
Eutelsat 7A (7.0°E)
10973 H 9874
Infos: Molde FK - Celtic
Eutelsat 7A (7.0°E)
10998 H 9874
Infos: Fenerbahce - Ajax
Eutelsat 7A (7.0°E)
10985 V 9874
Infos: FC Schalke 04 - Sparta Prague
Eutelsat 7A (7.0°E)
11009 H 9874
Infos: FC Basel - Belenenses
Eutelsat 7A (7.0°E)
11045 V 9874
Infos: Dnipro Dnipropetrovsk - Saint Etienne
Eutelsat 7A (7.0°E)
11021 H 9874
Infos: Slovan Liberec - FC Groningen
Eutelsat 7A (7.0°E)
11080 H 9874
Infos: Sporting CP - Skenderbeu Korce
Eutelsat 7A (7.0°E)
10998 V 9874
Infos: Villarreal - Dinamo Minsk
I was looking for a skin editor and there wasn't much here, so I looked around and found this. It is apparently based on e2skinner (which I never used...) and was updated last year, which is much more recent than anything else I found.
https://github.com/iMaxxx/OpenSkin-Designer
I installed (well just extracted the zip) and just started playing with it. It loaded a few skins without error and seems functional, but I haven't done much with it.
Is there something better that people are using? I am not interested in starting some new skin from scratch, just making a few changes to some existing skins (for alien2.)
Is anything broadcast in 4:2:2 over europe still ?
Yes, many feeds... Like all of this weeks UEFA matches... :)
It has twin fixed fbc tuners, from this my understanding is that each tuners will give you effectively 4 sat tuners (4 different frequency's per tuner).
Then you can use a conventional twin plug and play tuner onto of that, so you could in effect have 10 sat tuners in total (or 8 sat and 2 cable or terrestrial)
The tuner supports something like Inverto's unicable LNB. Look in this thread: http://linuxsat-support.com/showthread.php?t=95392&goto=newpost
It supports many tuners connected to the same LNB with one cable.
Hi,
I hope this is alowed here - My apologies if it is not.
It is not allowed here.
Forum Rules here
QuoteRules:
<1> Anyone found to be running a Pay Server / PAY PORTAL of any sort whether it be through satellite or internet or any other medium will be permanently banned.
<2> If you are the supporter of a Pay Server DO NOT ask for support, your request will be ignored.
Does anyone know if it will support 4:2:2 feeds? I am guessing not since I don't see it in the specs... But I noticed that they have switched to an ARM processor.
I am not using usals so surely the motor will not move to what thinks is the right postion
But if you do use USALS, then the motor WILL move to what IS the right position, and then you can adjust from there...
BTW - I don't think there is much use in trying to save and use your old gotox positions. In a perfect world, theoretically you could use them again, but if there is just a small change on any of the multiple adjustments, they will probably never all line up again. Sure you can get one, but what is the point of a motor if it will only work on one sat???
Then why is it when i get SNR 84% AG84% on hotbird and watch for few hours in evening all is fine switch box to standby and switch back on the morning no signal and not touched the dish.
Even the if the dish had moved slightly the signal should not go from 84% to zero on all channels.
After a box was in standby, it cannot know what has happened while it was off. So, before it tunes, it sends motor commands to make sure the motor is in the correct position.
Another thing to check, when you loose only some channels, is there a consistency as to their H/V or hi/lo freq values? i.e. do you loose all horizontal channels? If you see a pattern, it can help narrow done possible problems.