Posted by
on 21 May 2018 - 23:07
You both reply to different things! 
@frankviana, if I recall correctly astra requires the last : in the reference!
So try this
astra --analyze "t2mi://#t2mi_pid=64&t2mi_input=http://127.0.0.1:8001/1:0:1:320:3A2:0:C7A0FA0:0:0:0:"
I know, it sounds stupid but worked for me!
Posted by
on 30 March 2018 - 00:51
So, I'm trolling now, OK....
I've been trying so hard with evidence to prove what's wrong and all I get is that I'm trolling...
No, my friend I will not answer any of these questions. Because it seems everything I say is trolling to you! And everything you say is right!
Yes, HD51 is a perfect receiver. It has no problems at all, you say it is and because you say it it's right!
Everyone else is trolling!
I'm sorry I even lost my time with this, it's more than apparent we will never get the support we deserve for this receiver with this kind of attitude!
I'm totally out of this conversation. I've been on satellite forums for years and have been always helpful. My only mistake is buying a receiver I mistakenly thought would be correctly supported and all I get is people mocking me for trolling!
Good luck to everyone who owns an HD51. Enjoy your perfect problem-free product!
Posted by
on 29 March 2018 - 23:59
OK, I try the most of my capacity, but let's make myself even more clear then. I report two different issues that were already reported by other people as well!
PROBLEM 1:
No LIVE tuner values supported.
When OpenPLI is set to read the frequency data from the tuner and not the lamedb
Infobar frontent data source -- Tuner
instead of the tuned live frequency data we get only the oscillator frequency of the LNB. If the frequency for instance is 12034V we will only get 10600V, if it's 10775H we get 9750H!
All other receivers with Silabs tuners report the tuner values with this setting on correctly!
This also affects the DVB-T2 tuner of HD51, which means it could be more than the driver, something else has to be missing too!
PROBLEM 2:
The tuner driver DOES NOT report the db values correctly, but a calculated down value which in many cases differs up to 2 db from the real one!
Plus there is a lot of variation in the db value (signal goes up and down randomly with no reason) especially on Multistream channels.
Plus when a frequency is tuned you don't see the real db right away but a lower value. For instance it goes from 7.5db to 17.2db!
Instead of outputting the correct 0.25 increment values for example 10.25 - 10.50 - 10.75 - 11.00 - 11.25 etc
the generic driver that HD51 uses outputs calculated down values 10.20 - 10.50 - 10.70 - 11.20 etc. Often it skips increments as well.
I ran femon and fe-tool to monitor the demodulator's behaviour. Although it is DVBAPI v5.1 this DOES NOT mean the values are correct. DVBAPI reads the values from the driver. If the driver reports erroreous values, DVBAPI will too!
So this is what femon reports on HD51.
Find content
Not Telling
Display name history
Lock (0x1f) Signal= 56.25% C/N= 14.70dB
Layer A: C/N= 75.00%
Lock (0x1f) Signal= 56.25% C/N= 14.70dB
Layer A: C/N= 75.00%
Lock (0x1f) Signal= 58.59% C/N= 17.50dB
Layer A: C/N= 89.00%
Lock (0x1f) Signal= 58.59% C/N= 17.20dB
Layer A: C/N= 88.00%
Lock (0x1f) Signal= 58.59% C/N= 17.20dB
Layer A: C/N= 88.00%
Lock (0x1f) Signal= 56.64% C/N= 9.70dB
Layer A: C/N= 50.00%
Lock (0x1f) Signal= 56.64% C/N= 13.20dB
Layer A: C/N= 67.00%
Lock (0x1f) Signal= 59.38% C/N= 9.00dB
Layer A: C/N= 46.00%
Lock (0x1f) Signal= 59.38% C/N= 13.20dB
Layer A: C/N= 67.00%
In the marked red you can also see the issue these 9db values happen when you zap through channels with different frequencies. None of the other Silabs receivers have this problem.
Let's compare what SF4008 outputs with fe-tool.
root@sf4008:~# dvb-fe-tool -m -a 0 -f 1 Lock (0x1f) Signal= 0.00% C/N= 10.75dB Layer A: C/N= 62.49% Lock (0x1f) Signal= 0.00% C/N= 10.75dB Layer A: C/N= 62.49% Lock (0x1f) Signal= 0.00% C/N= 10.75dB Layer A: C/N= 62.49% Lock (0x1f) Signal= 0.00% C/N= 10.75dB Layer A: C/N= 62.49% Lock (0x1f) Signal= 0.00% C/N= 10.75dB Layer A: C/N= 62.49% Lock (0x1f) Signal= 0.00% C/N= 11.00dB Layer A: C/N= 68.73% Lock (0x1f) Signal= 0.00% C/N= 11.00dB Layer A: C/N= 68.73%
As you can see we have 0.25 increments and steady values. This is the expected behaviour!
Now, I can't make myself any more clear. These are two basic tuner driver problems. WTE claims that this is normal behaviour and all other receivers report fake values. If this is not denial, I don't know what is!
Posted by
on 29 March 2018 - 22:35
No, we're not discussing the motor problem anymore, the tuner values are another issue, not having to do with the motor. No team can make their own drivers to fix these (unless they are Dreambox)
I don't know what else to say, it's like WTE is trying to convince himself that everything works correctly, but it seems like he is in complete denial. If this is the support we are getting in the future from Mutant, I can easily see people moving on to other receivers that will at least listen to what the customers have to say... I'm REALLY disappointed! 
Posted by
on 29 March 2018 - 02:08
I would say that you were joking, but I see you did not understand what I am writing!
Live Tuner Values are the ones that are reported directly from the tuner when any service is tuned, not the ones stored in the lamedb.
The correct Silabs driver reports these with no problems. This happens on Dreamboxes, Octagon and VuZero4K.
Instead HD51 and H7 use a driver/firmware that has not these enabled and it shows only the IF frequency of the LNB, thus 9750 and 10600 in Ku band. No SR, no other values.
Here's a screenshot of what is shown
[Attachment = 93098: livetuner1.jpg]
As you can see only 10600 is reported, no SR, no FEC, no nothing. What is more interesting is that even the DVB-T2 tuner has this problem. Something tells me that it's more than the driver, something went missing completely from the manufacturer?
As for the db values these are wrong too. Of course Silabs has 0.25db increments, and this is what we expect to have. Instead we get a calculated down value from the tuner driver which would not be such a problem if actually would be close, but in many cases the increments are of even 2db apart. This has nothing to do with other tuners like BCM that output increments of 0.01db, don't get that confused!
Here's a femon report of what is returned, no 0.25db. You can see even a 9.50db signal, this is another bug from the tuner driver, it first reports less signal!
root@hd51:~# dvb-fe-tool -m -a 0 -f 0
Lock (0x1f) Signal= 62.89% C/N= 16.50dB
Layer A: C/N= 84.00%
Lock (0x1f) Signal= 62.89% C/N= 16.50dB
Layer A: C/N= 84.00%
Lock (0x1f) Signal= 62.89% C/N= 16.50dB
Layer A: C/N= 84.00%
Lock (0x1f) Signal= 62.89% C/N= 16.50dB
Layer A: C/N= 84.00%
(0x00)
Lock (0x1f) Signal= 58.99% C/N= 17.50dB
Layer A: C/N= 89.00%
Lock (0x1f) Signal= 58.99% C/N= 17.50dB
Layer A: C/N= 89.00%
Lock (0x1f) Signal= 61.72% C/N= 15.70dB
Layer A: C/N= 80.00%
(0x00)
Lock (0x1f) Signal= 58.20% C/N= 9.70dB
Layer A: C/N= 50.00%
Lock (0x1f) Signal= 58.20% C/N= 15.20dB
Layer A: C/N= 78.00%
Lock (0x1f) Signal= 58.20% C/N= 15.20dB
Layer A: C/N= 78.00%
Lock (0x1f) Signal= 55.08% C/N= 13.70dB
Layer A: C/N= 70.00%
Lock (0x1f) Signal= 56.64% C/N= 13.70dB
Layer A: C/N= 70.00%
Lock (0x1f) Signal= 56.64% C/N= 13.70dB
Layer A: C/N= 70.00%
(0x00)
Lock (0x1f) Signal= 59.38% C/N= 15.20dB
Layer A: C/N= 78.00%
Lock (0x1f) Signal= 59.38% C/N= 15.20dB
Layer A: C/N= 78.00%
Lock (0x1f) Signal= 59.38% C/N= 15.20dB
Layer A: C/N= 78.00%
Now, let's compare what Octagon SF4008 outputs from their tuner driver
root@sf4008:~# dvb-fe-tool -m -a 0 -f 1 Lock (0x1f) Signal= 0.00% C/N= 10.75dB Layer A: C/N= 62.49% Lock (0x1f) Signal= 0.00% C/N= 10.75dB Layer A: C/N= 62.49% Lock (0x1f) Signal= 0.00% C/N= 10.75dB Layer A: C/N= 62.49% Lock (0x1f) Signal= 0.00% C/N= 10.75dB Layer A: C/N= 62.49% Lock (0x1f) Signal= 0.00% C/N= 10.75dB Layer A: C/N= 62.49% Lock (0x1f) Signal= 0.00% C/N= 11.00dB Layer A: C/N= 68.73% Lock (0x1f) Signal= 0.00% C/N= 11.00dB Layer A: C/N= 68.73%
Hmmm, surprised? The increments are absolutely correct!
These are REAL driver problems, that any manufacturer that respects their clients should push to fix. It's unfortunate that an excellent receiver like HD51 to almost any other extend gets the last of the stick in the support for the faulty drivers they use for the Silabs tuner.
Posted by
on 10 February 2018 - 15:14
That was a challenge, all description fields for tuner settings were added.
Pulled my Greek translation on github as usual!
Posted by
on 26 November 2017 - 20:02
GLAMOUR AURA FHD v. RC6
- Added Flash Image screens (love the new icon)
- Added Subtitle QuickMenu screen
https://mega.nz/#!DJ...pzfYTN5fMVMymRw
Posted by
on 25 November 2017 - 15:56
Glamour Aura FHD v.RC5
- minor cosmetic changes and better cam name detection
https://mega.nz/#!KR...ZTv5eg1NK3eH1To
Posted by
on 17 November 2017 - 13:09
With great pleasure, I finally present publicly my latest project, which is none other than my new skin called Glamour Aura FHD. It's a labor of more than a year in the making and testing!
Glamour Aura FHD (GAFHD) is a Full High Definition and High graphic resolution skin for receivers running Enigma2 and the recent OpenPLI/OpenPLI-based images.
Due to it's high resolution graphical nature, GAFHD was designed and optimized to run on new generation receivers. The minimal requirement is an STB with a CPU of 750 Mhz (2000 DMIPS).
GAFHD is also a skin you can contribute to. The ipk of the skin is distributed with closed converters/renderers, but all the python code along with the skin code is available on Github.
You can find the source code here: https://github.com/MCelliotG/GlamourAuraFHD-skin
You can pull your requests, make recipes for it and I will push contributions after testing.
GAFHD on par with its graphical user interface is fortified with an extended python system that runs along with OpenPLI's enviroment, providing it with some exclusive new features.
SCREENSHOTS and extended features presentation
1. Main Infobar
The main infobar is divided into two sections. The top section contains all frequency and signal info. GAFHD is the first skin that fully supports real-time info for Multistream services, showing MIS info when such a service is tuned. Up to 12 tuners can also be displayed. The left top part is a weather panel which shows today's weather. Weather info requires the MSN weather plugin to be installed and configured (instructions will follow).
The top infobar will also display full stream URL and stream type when a service is stream.
The lower section is the main infobar which contains along with the program info, an extended service info icons panel, including icons for audio/video codecs, a full exact framerate display, and a short weather panel which shows the current weather condition. GAFHD can also display a live bitrate if the bitrate plugin is installed and configured (this will be explained below as well).
The lowest part of the main infobar is the extended encryption info. GAFHD uses a new detection feature which shows all available caids and encryption system names of a service.
NOTE: The skin works best with 400X240 picon size.
2. Second infobar
The second infobar brings an amplitude of extra information for both the service and the system layout. The weather panel shows additional info on tomorrows weather.
The left panel is the layout info showing real time CPU work, temperature, speed and load and internal HDD temperature. The upper layers show the pids of the service in decimal format and also real time info on connected storage devices, memory and swap.The middle part displays now and next program extended description.
3. Channel selection screens
Channel selection along with the service list on the right displays the extended program description on the left, the five following events and also a new transponder info panel which also shows the stream type and stream url on a stream service and transponder info for the rest.
4. Media player infobar
Media player will additionally show icons for resolution, audio/video codecs, subtitle availability and the exact framerate of a video or stream.
5. Info screen
Info screen along with the usual info also displays the HDD storage panel, which shows connected devices space both internal and network HDD and USB. The storage panel is also available on the HDD screens.
6. Language selection
GAFHD is a truly multilingual skin. It utilizes the new Aura new font I created based on Roboto and Noto fonts the skin is able to show Greek, Cyrillic, Arabic and Georgian among others. More alphabets can be added by request.
INSTRUCTIONS:
1) Download the ipk of the file. Send the file to /tmp your receiver using an FTP program. Then you can install it manually via telnet or via the software manager.
Manually:
opkg install /tmp/enigma2-plugin-skins-glamouraurafhd_RC.3_all.ipk
2) FOR BITRATE INFO
The bitrate plugin is essential for bitrate to work. You can download it from the plugins menu. For correct display in the skin it needs to be configured as follows:
mode: as infobar, style skin: compact, background window: transparent-black, X screen position: 1645, Y screen position: 0837, Z screen position: 14.
The correct settings are also shown in the screencap below:
3) FOR WEATHER INFO
The weather info requires the msn weather plugin to be installed. I have included the ipk as well. After installation you can configure your location via its settings menu.
Download MSN weather plugin from here: https://mega.nz/#!bN...3KOsUKNOg87-0sk
NOTE: For IPTV streams serviceapp is highly recommended with this skin.
IMPORTANT NOTE: As stated above, GAFHD is designed to work well ONLY for receivers with a CPU higher than 750Mhz. This is an obligatory limitation due to the high resolution graphical nature of the skin which also makes the package large in size. For receivers with slower CPUs use at your own risk! Also, GAFHD for the moment will not work on any other images (such as OE-A) than OpenPLI and OpenPLI-based images (like SatDreamGr, etc).
DOWNLOAD THE GAFHD SKIN IPK HERE:
https://mega.nz/#!KQ...yVe-4jfMzgDQ6mE
I want to personally thank my beta testers for their feedback. I encourage developers to contribute to the skin's further development in github.
I really hope you enjoy my work.
Posted by
on 5 September 2017 - 03:20
satedit.zip 11.7KB
16 downloads
Posted by
on 28 June 2014 - 20:06
Thanks, Pedro, here's the full translation now that I got the full file!
BackupSuite.zip 11.3KB
13 downloads
Posted by
on 28 June 2014 - 00:01
Professional GREEK translation in full for BackupSuite
Mo and po included in the zip file
el.zip 7.76KB
5 downloads
Posted by
on 18 June 2014 - 01:06
New Greek translation update, super complete with all new official changes, directly from the github!
10001-Update-Greek-Language.patch 332.94KB
10 downloads
