Superb quality and spec AB-Com PULSe 4K SE. Crazy offer! Only £99! FREE UK DELIVERY! 4K UHD, Enigma 2, Multiboot 4 images & more!...
Superb quality and spec AB-Com PULSe 4K Rev II Twin Satellite tuner only £149! FREE UK DELIVERY! 4K UHD, Enigma 2, SATA HDD facility, Multiboot 4 images & more!...

ABM DVB-T support

Are you sure your stick is FULLY supported, I have a hauppauge nova-t stick and the model number I have is only supported under certain revisions, the problem you are describing matches my problem of trying to get my stick to work under many Linux based program's over the years, I always found it would install because it was seemingly the correct model, but it would never scan because it was a wierd revision.
 
Yes it is supported, it does scan all the channels, it's just that ABM fails to create the Freeview part of the bouquet
 
Yes it is supported, it does scan all the channels, it's just that ABM fails to create the Freeview part of the bouquet

tune to BBC 1 and post your e2 debug log with the area name in the provider your using.
 
Andy, if I wanted to try this in the Saorview environment, what would I need to modify? Obviously the tuning frequency in the xml file for my local transmitter. But what info are you looking for after that? Let me know - SID, VPID ???
 
Andy, if I wanted to try this in the Saorview environment, what would I need to modify? Obviously the tuning frequency in the xml file for my local transmitter. But what info are you looking for after that? Let me know - SID, VPID ???
info tune to a regional channel BBC 1 if poss and give me e2 debug log, i'll add to FreeView xml
 
info tune to a regional channel BBC 1 if poss and give me e2 debug log, i'll add to FreeView xml

- erm Saorview is the Irish terrestrial service, so no BBC, unfortunately. If you let me know what info you need from stream I can send it.
 
- erm Saorview is the Irish terrestrial service, so no BBC, unfortunately. If you let me know what info you need from stream I can send it.

Turn on your debug logs and then tune to RTE 1 for instance. You will see in the debug log all the required XML params for the stream.

From this you can create your own Saorview XML..

I tried this myself however while it did manage to scan 3 channels I wasnt able to watch them, they threw the tune failed error!

You might fair better perhaps...
 
Turn on your debug logs and then tune to RTE 1 for instance. You will see in the debug log all the required XML params for the stream.

From this you can create your own Saorview XML..

I tried this myself however while it did manage to scan 3 channels I wasnt able to watch them, they threw the tune failed error!


You might fair better perhaps...

This was my intention all right - to create the relevant XML file for my local Saorview. I have done this before in the terrestrial.xml file to reduce the unnecessary scanning of the entire UHF band, but this only helps in a manual DVB-T scan. There is some additional information needed beyond the tuning parameters to enable the ABM script and code to build a bouquet for the Irish TV/Radio service, but I'm not sure what that is - ONID, TSID etc.??? The scale of the problem is certainly much less than Freeview as there are only 8 live TV services and 10 radio services in two multiplexes, but as far as I can see, you need two frequency entries in a table for each geographical group of transmitters as you cannot work out the frequencies from the stream data. I'll spend some time later today in reviewing the scripts and table in the ABM folder and see if I can work out what it's doing.
 
There is some additional information needed beyond the tuning parameters to enable the ABM script and code to build a bouquet for the Irish TV/Radio service, but I'm not sure what that is - ONID, TSID etc.???

I'm not sure what those are TBH, you seem to have a good understanding of this stuff, beyond mine anyway..

All I got when I tuned to RTE 1 was this:
Code:
use pmtpid 07d1 for service_id 0835
eventNewProgramInfo 0 0
have 1 video stream(s) (0835), and 2 audio stream(s) (0899, 08a3), and the pcr pid is 1ffe, and the text pid is 08fd
decoder state: play, vpid=2101, apid=2201
bandwidth: 8000000
code_rate_lp: 5
code_rate_hp: 5
constellation: 3
transmission_mode: 2
guard_interval: 4
hierarchy_information: 4
inversion: 2
system: 0
frequency: 657999998
bandwidth: 8000000
code_rate_lp: 5
code_rate_hp: 5
constellation: 3
transmission_mode: 2
guard_interval: 4
hierarchy_information: 4
inversion: 2
system: 0
frequency: 657999998

I then created this Saorview XML and then ran a scan.. It only picked up RTE1, RTE 1+1 and RTE Jnr but I got tune failed on all 3..
Code:
<provider>
	<name>SaorView</name>
	<streamtype>dvbt</streamtype>
	<protocol>lcn</protocol>
	<namespace>0xeeee0000</namespace>
	<dvbtconfigs>
		<configuration key="monaghan" frequency="657999998" inversion="2" modulation="4" system="0" bandwidth="8000000" code_rate_hp="5" code_rate_lp="5" transmission_mode="2" guard_interval="4" hierarchy="4">Monaghan</configuration>
	</dvbtconfigs>
	<sections>
		<section number="1">SaorView</section>
	</sections>
	<servicehacks>
		<![CDATA[
		]]>
	</servicehacks>
</provider>

Best of luck with this, I'd be interested in your findings.. I have a PCTV 290e connected to a Duo and for some unknown reason I keep loosing my channels, think ABM scan is knocking something out.

If I had this working then I wouldn't need t worry about it..
 
Last edited:
@mcquaim - thanks for your post. I was trying to edit my local transmitter (Greystones, Co. Wicklow) into the GB Freeview xml file, but I kept getting a tune fail for some reason, even though all the parameters were correct as far as I could see. Then I tried your method of creating a separate xml file for Saorview and had some limited success. Similar to you I got RTE1, RTE1+1 and RTE Junior in a separate bouquet, but they wouldn't tune afterwards. The reason for this is that the ABM plug-in uses your initial frequency information to tune in the multiplex (terrestrial equivalent to transponder on satellite) and then stores the services it finds on that multiplex. Unfortunately 2RN (the transmission network managers for the RTE network), have an erroneous fixed piece of information stored in the NIT (sorry about this!) "CentreFrequency =198500 kHz" and ABM seems to use this and stores it as part of the tuning information in lamedb. This frequency is wrong and results in the box being unable to tune the multiplex subsequently. The only way to recover it is to store the multiplex using a manual scan.
The reason why you are only getting RTE1, RTE1+1 and RTE Junior on the ABM scan is that you are only providing tuning information for one multiplex. You would need to create a second xml file for the second multiplex, where the frequency is "682000000". I'm guessing that your transmitter is Cairn Hill (Monaghan being your geographic location) and the multiplexfrequencies there are 658000000 and 682000000.

All this is rather moot, though, as it won't result in a successful scan using ABM. I have offered to help andyblac, but I'm still constrained by the non-availability of a ViX image for my Gigablue Quad Plus. I'm actually using the OpenATV 4.1 image, which has ABM installed, but I'm not sure if it's the latest and greatest version.

Info for @andyblac:

Saorview ONID is 0x2174, NetwID is 0x3201, TSID for RTENL1 is 0x03E9 and TSID for RTENL2 is 0x03EA - those are the only two multiplexes.

There is no BAT in the Saorview SI entries. The SI data is the same across the entire network as far as I know. Frequency lists contained in the SI data are incomplete and possibly erroneous.
As far as I can make out the only strategy which would work is to use two frequency settings from each Saorview transmitter contained in the xml file and not try to automate the frequency finding from the NIT. And as there is no BAT, you would need just a fixed bouquet and no need of separate SD and HD listings for Saorview.
 
NIT dump from Saorview multiplex

Here's an xml file dump (in txt format) of a Saorview NIT, showing the issues with frequency. Just missed the 30 minute deadline for editing my original post :whistle:
 

Attachments

"CentreFrequency =198500 kHz" and ABM seems to use this and stores it as part of the tuning information in lamedb. This frequency is wrong and results in the box being unable to tune the multiplex subsequently. The only way to recover it is to store the multiplex using a manual scan.
Correct. ABM uses the Centrefrequency from descriptor 5A. Do you know a way we can pick the correct alternative frequency from descriptor 62? How do we know we must choose one of these (and which one), instead the CentreFrequency?
 
Correct. ABM uses the Centrefrequency from descriptor 5A. Do you know a way we can pick the correct alternative frequency from descriptor 62? How do we know we must choose one of these (and which one), instead the CentreFrequency?

Thanks @Peterj - see my post #39 where I pondered how ABM was going to deal with the absence (or poor quality) of data in the Saorview SI streams!

Are you saying that the Freeview CentreFrequency data in descriptor 5A is correct for each different transmitter in the UK? This would mean that there would be unique coded data being relayed to each transmitter, but this may be the case. It's my understanding that in the Saorview network all the SI data is essentially the same and relayed to each transmitter by microwave link or whatever.

The alternative frequencies in descriptor 62 are just a list of some of the channels in use, are wrong with regard to the VHF frequencies and are missing some UHF frequencies. Again, I believe all transmitters share the exact same set of data.

As regards a solution, I can only see that some sort of list system could be used. For example, my nearest transmitter uses 722 MHz and 754 Mhz for the two multiplexes and any solution would have to use just those two frequencies for storage in lamedb and ignore descriptors 5A and 62. There are xml files earlier in this thread and others which could be used to form the basis of such a list system, but it would be an on-going exercise to keep updated. As the Saorview system is relatively new and limited in channels and there is no regionalisation there was probably no need for BAT or for more fine-grained frequency lists in the SI data. Maybe the data quality will get better as the system evolves, but for the moment there is one full multiplex and room for about 5 or 6 more TV channels in the second multiplex. The two primary channels RTE One and RTE Two are in HD only and the remainder are SD. There is no simulcasting of SD and HD required as Saorview kit is required to support HD (MPEG4 over DVB-T). No word on deployment of DVB-T2 but new kit would support this and be backward compliant to DVB-T. The advantage of Saorview over Freeview is that all the transmission parameters are the same for each transmitter, only the frequencies change.

If a list system is a possibility I could look at hacking some of the existing Saorview xml files, but it would be good to understand how ABM works at some level of pseudocode so that the relevant info could be supplied. I'm curious to know how the frequency selection is handled for the Freeview network, though? There could be lots of relay stations transmitting to isolated areas so how do you select the appropriate frequencies to scan? It's a much simpler process for satellite as reception quality is similar for all, whereas in the terrestrial environment it's tricky.
 
@fat-tony.
I would like to analyse your dvb-t streams.
Can you do a full scan, so you will have correct freq. in your lamedb and post the lamedb.
Also make a NIT dump for a couple of different freq.
You need dvbsnoop.
Code:
opkg install dvbsnoop
Tune to a valid freq. (channel) and run dvbsnoop.
Code:
dvbsnoop -s sec -tn -timeout 10000 -b -f 0x40 -n 100 0x10 > /tmp/nit.bin
post me for each freq. the nit.bin (rename it to e.g. 722.bin)
 
@fat-tony.
I would like to analyse your dvb-t streams.
Can you do a full scan, so you will have correct freq. in your lamedb and post the lamedb.
Also make a NIT dump for a couple of different freq.
You need dvbsnoop.
Code:
opkg install dvbsnoop
Tune to a valid freq. (channel) and run dvbsnoop.
Code:
dvbsnoop -s sec -tn -timeout 10000 -b -f 0x40 -n 100 0x10 > /tmp/nit.bin
post me for each freq. the nit.bin (rename it to e.g. 722.bin)

Ok here you go! By the way, I had to terminate the dvbsnoop command after several minutes when it seemed like it wasn't going to finish by itself. I guess the count of whatever packets you were looking for didn't make it to 100?
 

Attachments

OpenViX Feeds Status

Back
Top