Using Saorview Providers, scan finds channels but no picture/sound.

[nosnikrap78]

Box: Vu+ Solo²
Firmware version: Hades.010
AutoBouquetMaker: latest version pulled from GIT oe-alliance-plugins/AutoBouquetsMaker/ on 29th May
DVB-T: USB Nova-T Stick (DVB-T)

I updated to the the latest version of ABM as it now includes Saorview Provider files, previously I would scan the channels to favourites and then add the channels to the Main Bouquet file. This has worked great for the last few years, and now want to make use of the new features in ABM CustomMix etc...

ABM setup with 3 providers SkyUK LondonCustom, Soarview 1 (dublin threerock) and Saorview 2 (dublin threerock).

Scan runs and finds all channels for SkyUk and Saorview1/2 and adds them to the Bouquets.

When I change channel to a Saorview station, the epg/channel name info is displayed but no picture/sound, the channel info shows DVB-T CH8 199MHz 8Mhz, which I know is wrong and should be CH30 / Ch33. I have checked the Soarview frequency files and they have the correct values (the channels are found so must be good).

Any advice would be good...thanks.

Note, If I do a manual scan of Ch30 / Ch33 after ABM has run, then I get picture/sound.

[abu baniaz]

We are still fine tuning Saorview.

Can you put enigma to sleep with "init 4" telnet command. Run a normal scan (dont use ABM). Upload the lamedb file that is created.

Put Enigma to sleep, delete lamednb file, run ABM for saorview only again, upload lamedb from this run too.

[nosnikrap78]

Thanks Abu.

2 lamedb files attached as requested.

[abu baniaz]

Can you double check that the frequencies being used tally/match. Please edit the ones in the custom tranponder file

From your manual lamedb file, they are:


eDVB services /4/
transponders
eeee0000:03e9:2174
t 545999998:0:5:5:3:2:4:4:2:0:0:0
/
eeee0000:03ea:2174
t 569999998:0:5:5:3:2:4:4:2:0:0:0


However, the xml files are using (part of lines posted)


key="three_rock_psb1" transport_stream_id="03e9" frequency="738000000"
key="three_rock_psb2" transport_stream_id="03ea" frequency="770000000"

You may need to change these to 546000000 and 570000000 respectively

[Huevos]

You need the latest copies of dvbscanner.py, manager.py and tools.py. GUI restart and try again.

[nosnikrap78]

I updated the 2 provider files (terrestrial_ie_saorview_PSB1.xml + terrestrial_ie_saorview_PSB2.xml), to have the correct frequencies:



<configuration key="three_rock" frequency="546000000" inversion="2" modulation="4" system="0" bandwidth="8000000" code_rate_hp="5" code_rate_lp="5" transmission_mode="2" guard_interval="4" hierarchy="4">Dublin THREE ROCK</configuration>

<customtransponder key="three_rock" transport_stream_id="03e9" frequency="546000000" />

<configuration key="three_rock" frequency="570000000" inversion="2" modulation="4" system="0" bandwidth="8000000" code_rate_hp="5" code_rate_lp="5" transmission_mode="2" guard_interval="4" hierarchy="4">Dublin THREE ROCK</configuration>

<customtransponder key="three_rock" transport_stream_id="03ea" frequency="570000000" />


Copied over the updated .py files (and restarted box).

Re-scan Saorview 1/2 only and same problem, all channels are showing DVB-T CH8 199MHz 8Mhz.

Here is the transponders output from the lamedb file:


eDVB services /4/
transponders
eeee0000:03e9:2174
t 198500000:0:1:1:2:1:0:0:0:0:0:0
/
eeee0000:03ea:2174
t 198500000:0:1:1:2:1:0:0:0:0:0:0
/

[abu baniaz]

Did you update the files Huevos mentioned? There were changes to read the custom TP entries.

Should be in the ABM that is in Hades 011.

[Joe_90]

Folks - @abu and @Huevos particularly. The standard terrestrial.xml file has all the correct transmitters and frequencies as supplied by me some time back. The OP has indicated as much in that a normal E2 scan works.

The Saorview files for ABM were not ready for production use as they were based on wrong data. They are being cross-checked and corrected versions should be ready for inclusion in builds from 1st June.

[nosnikrap78]

I pulled the latest version of ABM this morning (31/05/2015), and can see Huevos made changes to the Saorview files (key and modulation) updates and also correct freq for Dublin Three Rock. I replaced the /usr/lib/enigma2/python/Plugins/SystemPlugins/AutoBouquetsMaker folder with that version and tried a re-scan (changing my abm setup as the transponder name changed from 'three_rock' to 'Dublin, Three Rock'. Same problem channels scan, but no picture/sound and channel details showing DVB-T CH8 199MHz 8Mhz.

--###

Next step, updated to Hades 11. This removed the changes made by Huevos last night (Saorview files (key and modulation) updates).

Replaced the provider files with the latest version on GIT, and tried a re-scan.....

It works perfect...saorview channels clearing and thanks to the new CustomMix logic, these get added to the 1-100 range of the main bouquet. :)

Thanks lads.

[Joe_90]

The provider file changes didn't quite make it into the Hades 11 build, but you have got around that by pulling the update from Github. There will be a further update to the provider files to add in some additional transmitters which won't affect you. There may be further minor tweaks to the provider files in the coming day or two, but it's 99% there.

[white_westie]

Pulled the latest code from the git and updated my et9x00
Deleted all terrestrial channels from lamedb and did a full ABM scan again - just using Freesat FTA and Saorview providers
All Saorview channels pulled in nicely on both muxes - using Dublin Three Rock as location

Thks to all for great work.....:thumbsup:

[Joe_90]

@Huevos is tweaking the code further, so there should be more user-friendly changes coming!

[Huevos]

Yep. It's finally got to the point where it is working like a normal provider, without the need for custom files, or the need to select and configure multiple providers.

Only problem is I cant use it.

[Joe_90]

Yes - tested fine and ready for release! See further tweaks tonight which have improved Freesat scanning time.