Ergebnis 1 bis 10 von 10
-
07.01.2019, 03:00 #1
- Registriert seit
- 24.09.2018
- Beiträge
- 82
- Thanks (gegeben)
- 5
- Thanks (bekommen)
- 2
- Total Downloaded
- 0
- Total Downloaded
- 0
Zgemma H7.Ac / For the developers and coders
The H7. AC has problems over here in the USA.
See my post for Dolby Digital problems please.
There also is a terrestrial/cable tuner in the AC model with the MStar MSB1237 RF demodulator and Rafael r836 tuner chipset.
Although the tuner is supposed to work with 256-QAM cable (as an option in tuner setup), I cannot get any channels scanned in.
I have a scan frequency log from a Silicon Dust HDHOMERUN and entered those frequencies into the atsc.xml file.
Still no channels found.
Drivers are embedded in code (NO Separate tuner driver). I have not been able to find a dedicated driver or source code for the Mstar demodulator.
It appears that OpenATV and OpenPLI and other builds of Enigma2 use the same exact atsc.xml file.
I would like to know if a developer could help me understand and maybe provide the code to perhaps get the tuner to work.
Also it is confusing why a cheap satellite receiver will decode Dolby AC3 into separate audio channels.
Using the H7, only a test file from Dolby Labs and others will decode discrete audio with the media player, but not on satellite.
Pleas help me understand the workings of the receiver and software drivers that may need some improvement to get it to work properly.
-
Advertising
-
07.01.2019, 08:08 #2
- Registriert seit
- 03.04.2013
- Beiträge
- 14.861
- Thanks (gegeben)
- 763
- Thanks (bekommen)
- 21090
- Total Downloaded
- 162,47 MB
- Total Downloaded
- 162,47 MB
i have report you issue to driver team
we dont have the ac model
openATV we are open Source
Boykott GPL violator
-
07.01.2019, 09:30 #3
- Registriert seit
- 24.09.2018
- Beiträge
- 82
- Thanks (gegeben)
- 5
- Thanks (bekommen)
- 2
- Total Downloaded
- 0
- Total Downloaded
- 0
ThemenstarterUnderstood. Although the chipset in the plugin tuner is used in many different receivers. The tuner may be from different manufacturers. The demodulator is flexible to adapt for many transmission methods.
I have opened the /lib/modules/4.10.12/extra/h7_4.ko file in notepad++ and see references to the MSB1237 demodulator.
The .ko file seems common to different Enigma2 flavors.
I was hoping to find the source or plain (not embedded) driver. Although not a programmer, 256-QAM is the same modulation scheme the HDHOMERUN and my USA televisions use. They scan all frequencies in completely, even scrambled ones which of course I cannot watch. I do not have any terrestrial signals in my isolated area to test the tuner with an antenna.
I also understand blindscan in these receivers is not working still, and therefore manually inputting the frequencies in the proper .xml file is necessary. I get no signal strength when those channels are indicated in a scan or using signal finder.
During initial building of Enigma2, OpenATV, and others the driver must be someplace. I have not been able to find it anyplace although many tuner manufacturers are using the exact 2 components in them. Including USB tuners and other STB's.
Please forward this to the devs if you could.
As for the Dolby issue. My other satellite receivers are a Dreamlink HD T5 and Linkbox 8000 Local. One has a Broadcom receiver/processor and the other has an ALI receiver/processor. They both will decode discrete 5.1 channel Dolby on satellite transmissions. The Zgemma will not. Using the media player, it will. I understand the Zgemma uses the same Broadcom receiver/processor as other receivers.
That would indicate an oversight in programming of software where the audio is processed on satellite versus internal media (USB, HDD).
Thank you and Regards.
-
07.01.2019, 09:43 #4
- Registriert seit
- 15.06.2013
- Beiträge
- 2.359
- Thanks (gegeben)
- 287
- Thanks (bekommen)
- 1399
- Total Downloaded
- 1,32 MB
- Total Downloaded
- 1,32 MB
Box 1:hd51Box 2:vuduo4kseBox 3:und noch 20-30 andereThe drivers are closed source. So you cannot change them. Only the manufacturer has the source code. Same for audio.
hd51, vuduo4se,....
-
Danke - 2 Thanksel bandido, jenseneverest bedankten sich
-
07.01.2019, 20:26 #5
- Registriert seit
- 24.09.2018
- Beiträge
- 82
- Thanks (gegeben)
- 5
- Thanks (bekommen)
- 2
- Total Downloaded
- 0
- Total Downloaded
- 0
ThemenstarterSo you're saying that the manufacturer wrote the code for Enigma2 and included all other drivers for other chip manufacturers in the .ko file I indicated in my initial post?
I find that hard to believe. Requires further looking into. Same for audio.
Let's keep this alive please.
-
08.01.2019, 06:18 #6
- Registriert seit
- 24.09.2018
- Beiträge
- 82
- Thanks (gegeben)
- 5
- Thanks (bekommen)
- 2
- Total Downloaded
- 0
- Total Downloaded
- 0
ThemenstarterDigital ATSC 256-QAM
As you can see I have attached the scan data file from the HDHR Extend and what is edited and placed in etc/tuxbox.
Frequencies and modulation are correct I believe. But scanning comes up with no signal on all channels.
Please help.
-
08.01.2019, 09:18 #7
- Registriert seit
- 15.06.2013
- Beiträge
- 2.359
- Thanks (gegeben)
- 287
- Thanks (bekommen)
- 1399
- Total Downloaded
- 1,32 MB
- Total Downloaded
- 1,32 MB
Box 1:hd51Box 2:vuduo4kseBox 3:und noch 20-30 andereAfaik are the tuner drivers included in the closed source drivers. Audio data is in most cases decoded and processed by the hardware. Only if you play back mkv or or other media files the files are demuxed by gstreamer. As audio decoding is not so difficult for some codecs without hw support (eg dolby true hd) software decoding is used. For software decoding and gstreamer we have the sources. For all what happens in the chip (hw decoding) there are only the closed source drivers. AC3 is decoded in the chip.
It might be that the AC3 stream is not recognized properly by e2 and so e2 doesn’t tell the driver the correct stream info.hd51, vuduo4se,....
-
09.01.2019, 01:33 #8
- Registriert seit
- 24.09.2018
- Beiträge
- 82
- Thanks (gegeben)
- 5
- Thanks (bekommen)
- 2
- Total Downloaded
- 0
- Total Downloaded
- 0
ThemenstarterYou sound very knowledgeable. Thank you for sharing your info.
Does that lead me to believe that Broadcom holds the source code, builds it, and submits it to Enigma2, Android, etc. to use with the different stb's using their chipsets?
If I'm not mislead. It looks like the tuners I have in my receiver and the Broadcom drivers are bundled into one .ko file?
Excuse me, I'm just trying to learn how this all blends together to make the box work.
If the tuner demodulator (which will not work scanning 256-QAM channels here in the USA) and the Broadcom chip which is the receiver on a chip (which has issues with DVB Dolby), AND the Si tuner for DVB-S/S2 (seems to work OK) are all bundled into one driver file.
Somebody must have had the source code for each device to compile into a single file. Yes?
And if a glitch is found, hopefully, the manufacturer can be contacted for a fix.
But the question is. Who holds source code for all the drivers? And who in the Engma2 community who makes OpenATV, OpenPLI, etc. could contact them for a fix and who would compile all of the driver files once again?
Does this make sense?
-
09.01.2019, 06:00 #9
- Registriert seit
- 12.05.2015
- Beiträge
- 127
- Thanks (gegeben)
- 349
- Thanks (bekommen)
- 34
- Total Downloaded
- 0
- Total Downloaded
- 0
You have a similar thread here: H7.AC Cable Reception No Signal
Please read post #4 in this thread.
There is not anything that can be done about your issues at this level. It will take the manufacturer to fix your issues - If they are fixable. Do not hold your breath waiting for that day. Zgemma has moved on to other models, and it is very doubtful they are concerned about these issues in the H7.AC. Look for other options besides the H7.AC.
-
09.01.2019, 08:55 #10
- Registriert seit
- 15.06.2013
- Beiträge
- 2.359
- Thanks (gegeben)
- 287
- Thanks (bekommen)
- 1399
- Total Downloaded
- 1,32 MB
- Total Downloaded
- 1,32 MB
Box 1:hd51Box 2:vuduo4kseBox 3:und noch 20-30 andereBroadcom has the source code and sells it to the manufacturers. But the manufacturers aren’t allowed to publish the source code. They can build closed source drivers which are then delivered to the e2 teams. If non Broadcom tuners are used, it’s similar. The manufacturer include the tuner drivers into the ko files.
As Captain already wrote did he contact the driver developers. They might fix it or not. We cannot do anything more than reporting it.hd51, vuduo4se,....
-
Danke - 1 Thanksjenseneverest bedankten sich
Lesezeichen