Posts by joeuser

Quote from wabbit

As mentioned in my first post the reciever is a Vu+ Solo2 running Black Hole 3.0.1.F OE. The LNBs are connected to a DiSEqC. The reciever also has two tuners. I have subscriptions for Canal Digital and Viasat (nordic, OSCam).
Right now I have a SNR of 99% on some Canal Digital channels (Thor), however 59% SNR on Astra. Your idea with the prepared list of channels sounds good. Will try to find one and upload it, to see what SNR I am getting on those channels. Doesn't matter if I am doing it the hard way, wouldn't learn anything otherwise :P

Just bought a satellite signal strenght meter for positioning satellite dishes so I hope that will help a bit.

Im a little confused. What I meant was the leftmost LNB, when looking from behind the dish toward the satellites, was pointing at Thor. Is that correct, or should it be reversed?
I just reversed it and am getting 99% on Thor while staying on 59% on Astra:

Im not sure how to skew the dish as it is locked to the wall mount, and the LNBs are locked to the bracket. Only thing I can do is to rotate the LNBs:

Display More

Picture as labeled is reversed - leftmost when looking from behind the dish towards the satellites is Thor 0.8W and the other for Astra 4.8E.

Yes, with that mount it would be very difficult to skew, so you will be limited to skewing the LNBs.

If Thor is stronger, you can try tilting the dish up just a bit and the Thor signal should drop a little and Astra should gain.

While a signal meter will get you close, it probably will not help much when trying to fine tune - too much work to keep switching it back and forth. If you have an Android phone or tablet, you can download the vu+player app and it has a signal meter you can use while adjusting the dish. It will take a lot of time (and patience) to fine tune to get the maximum signal from both...

MastaG's latest release for many boxes...

Hi folks,
 
It took me a while to build these because there were lots of small bugs and user requests.
I did my best to answer them all.
But due to my limited time I couldn't fulfill all of them, so my apologies if I didn't respond to a PM or forum-post.
 
So anyways.. there are lots of changes compared to my last images.
Too much for me to remember, so I guess:
 
 - Added new receivers: Zgemma H5 and LC, Vu+ Solo 4K, XpeedC (whatever that is) and Atemio Nemesis (user-request, not tested at all so beware).
   There are no Wetek builds and I ain't gonna build them, so don't ask.
 - I've fixed the feed for mips32el-nf receivers (et4x00, hd1100, hd500c and xp1000).
 - Oscam bumped to rev. 11211 with Joeuser's patch (yes I know you guys were waiting for this one).
 - Lots of fixes for spark and spark7162 with the help of my great friend Taapat, they should be of equal quality as other PLi 4 images now.
   The libeplayer versions are in the "eplayer" directory, everything else is gstreamer.
 - No more patches to enigma2's servicemp3.cpp (except the one for aac transcoding), so it should reflect the current state now.
 - Latest gstreamer 1.7.1 master head as of today.
 - Many backports from master-next and Taapat.
 - Lot's of small things I forgot.
 
Note:
 - If you get corrupted jpeg images on spark/spark7162 the hardware decoder is not working for you, simply login using telnet and type:
  rm -f /usr/lib/libmme_host.so
  Then restart enigma2 and they should display fine
- Zram is now disabled by default on spark/spark7162, if would like to use it anyways, simply login using telnet and type:
  touch /etc/gimme-zram
  Then reboot your receiver.
 
If I didn't mess up badly this time, this will be my last round of public images.
I don't think there's any benefit for releasing gstreamer master head images anymore, since the next stable gstreamer release will hit master-next and oe-alliance anyways.
And most work went into supporting non-PLi-supported receivers which takes lots and lots of time.
 
 
Thank you all for the great feedback !
You're the best!

A couple of things to remember:

1. Since the beam is reflected by the dish to the LNBs, the relative positions of the LNBs are reversed. If you haven't taken this into account, your second LNB could be pointing at 4W and not 4E. But you are probably ok since you stated that in your photo, you are using the left LNB for 0.8W, so the right LNB would be for 4.8E.

2. Since both those satellites are to the west of your location and you have an elliptical dish, your dish should be slightly rotated (skewed) clockwise when looking from behind the dish toward the satellites. You can use dishpointer to find the skew for each sat and split the difference. This will make the left LNB (0.8W) be a little higher to account for the fact that 0.8W sat is a little lower on the horizon than 4.8E. (again relfection) I would start with the LNBs mounted straight with respect to the bracket and dish, then skew each one a little to adjust for best signal.

Also I made a mistake earlier - I was thinking 4W, probably because I had just scanned that sat ;) But for 4.8E to 0.8W, there is actually 5.6 degrees of separation, so each sat will be off only around 0.2 degrees if you split the difference and that should give you pretty good signal for both.

Please edit your post better to remove keys..

If you manually add the key to the SoftCam.Key file, does it work? There may be a problem that testing the key does not test the possibility of the alternate sbox. On tablet now, will look at source code later.

(Sent from my A/S10 using Forum Fiend OSP v1.3.3.)

- - - Updated - - -

I checked and it does check with both sboxes. It is still rejecting the found key. If the key is indeed valid, let me know and I will look closer at the code...

Unfortunately I do not have any dreambox to test with anymore and I do not have much free time to debug someone else's code (especially when I cannot test myself...)

You can press the green button to override the settings and try out each mode immediately. Also heed Codar's advice and check your TV's settings.

Also you have to be aware that some channels send some pictures with strange settings that are hard to override...

If you do live in the Nordic region, it probably is doable with that bracket. but each sat will be 1 degree off, so the signal will be degraded.

Your screen shot show you are trying Thor, but a DVB-S (not S2) transponder with freq 11836 - which does not exist on either lyngsat or kingofsat and I also looked at a scan I did a long time ago and I also do not show a transponder for that sat at 11836. So, you are probably picking up a different sat...

Also, you cannot just "play" with symbol rate and FEC - you need to lookup a strong transponder for your area and set those values to what it says on lyngsat or kingofsat. Although, setting the FEC to auto is usually not a problem - it will figure out the correct setting.

As for the skew setting, the values listed assume your LNB is centered on the dish. So since your bracket is offset, those values will also be a little off. You will have to play a bit with the skew and see what gives you the best setting. (Don't forget to test both V and H transponders...)

If you created a timer from an EPG listing, sometimes there are "special" characters in the EPG which the timer does not like. Happens quite often with non-English languages.

The link gives instructions on how to clear the timers.xml file, which will solve the problem, but you will lose all timers you have set. If this is not a problem, just follow the instructions in the link MastaG gave you.

If you want to try to save the file, you can try to edit timers.xml and look for invalid characters in each "name" and especially in the "description" sections. If unsure, you can remove everything in the "description" section and replace with something like

description="."

But be aware that you may need to edit the file (or at least save the file) when enigma2 is not running because when enigma2 is restarted, it will first write a new timers.xml file before ending... So, it is best to run "init 4" from a telnet session, then edit the file, then run "init 3" to restart enigma2.

Keys need to be in file named SoftCam.Key. The file oscam.keys is not used

(Sent from my A/S10 using Forum Fiend OSP v1.3.3.)

http://linuxsat-support.com/showthread.php?t=90823&p=332125&viewfull=1#post332125

The patch needs to be applied to the oscam source code then compiled. Probably easiest way is to use simplebuild by gorgone.
Or you can download the latest oscam-emu with my patch here:http://linuxsat-support.com/showthread.php?t=90823&p=332125&viewfull=1#post332125

BTW - make sure to read the readme about the change in the key file format.
Also, the AC3 fix is only for stream relay connections.

You probably need to post more info about what you actually tried, not just "followed tutorials" - which tutorials? What steps? How exactly is it not working?

Probably best to use my latest patch which allows the update of multiple channels with one UA key.

But, be aware that the key file format has changed!!!!!!

There are posts about the new patch and format and someone has also posted latest builds with my patch in oscam-emu section (with readme including the new file format info.)

(I would post links, but I am on a tablet now...)

(Sent from my A/S10 using Forum Fiend OSP v1.3.3.)

For more clients, you have to change the static definition and recompile:

module-emulator-stream.h:#define EMU_STREAM_SERVER_MAX_CONNECTIONS 8

If you have two tuners, for a second TP, you need another instance of mumudvb (using a different port than 4242) pointing to another instance of OSEmu (using a different port than 17999).
Or, it may be better to use TVHeadend:http://linuxsat-support.com/showthread.php?t=98100
Then you only need one instance of TVHeadend and one instance of oscam-emu/osemu running. The setup is a little more difficult, but after it is easy to use and TVHeadend has a very nice web interface. It also uses less CPU (especially when no channels are being streamed...)

Have you tried Pauldb's latest HDMU backup image? He has it all configured already...
If you have problems (or often have problems loading backup images) use the re-packed version in post #5.
http://linuxsat-support.com/showthread.php?t=101832

powervu emu and oscam-emu/osemu use different key file formats. For osemu, you need something like:

P 04 00 xxxxxxxxxxxxxx
P 04 01 yyyyyyyyyyyyyy

Where "04" represents the SID (service ID) of the channel.

Quote from spacedvb

getting this error when run:

./OSEmu -v -a user:pass -p1234 -s 172.16.0.18 -r 4242:17999 -c key.txt

OSEmu version 719
cannot open key file path: key.txt
cannot open key file path: /var/keys
starting thread emu stream server
emu stream server thread started
[Emu] info: FFDecsa parallel mode = 128
starting thread emu stream client
emu stream client thread started
[Emu] stream client connected
[Emu] stream client request /1:1:1:4
[Emu] stream found pmt pid: 104
[Emu] stream found ecm_pid: 1770
[Emu] stream found video pid: 203
[Emu] stream found audio pid: 2A8
[Emu] stream found audio pid: 2A9
[Emu] Key not found: Identifier P Provider 4 keyName 00
[Emu] Key not found: Identifier P Provider 4 keyName 00
[Emu] Key not found: Identifier P Provider 4 keyName 00
[Emu] Key not found: Identifier P Provider 4 keyName 00

Display More

You are telling osemu to use a file "key.txt" for keys, but it cannot find/open it in the current directory.
It then looks in the default directory (/var/keys) and does not find it there either.

I had similar problems and finally had to manually edit the file /etc/enigma2/automounts.xml and make sure it read:

<hdd_replacement>True</hdd_replacement>

for my nfs server. A reboot is necessary...

The box will put out 13v for vertical and 18v for horizontal.

Sorry, I do not boot to spark much and so I have not tested the latest version myself. But, as I understand it, the the provider id is just the key number. For example, the first key will be 00000 (00 key of first channel) then second key will be 00001 (01 key of first channel) etc.