OpenDigitalRadio - User contributions [en]

How to configure SPI (Service and Programme Information) for ODR-DabMux

2024-08-16T14:03:33Z

Nickpiggott:

Howto by Ulrik Brinck on odr-radioepg-bridge installation on Debian Jessie. Nick Piggott has contributed with some additions (and edited to show installation for Python 3)

This is now updated to run on Python 3. Instuctions on how to make it (mostly) run on Python 2 are below, but this is now deprecated.

'''This guide assumes your default python envrionment is Python 3.'''

===Introduction===

This tool (or rather series of tools) will pick up your SPI (Service and Programme Information) from the internet via RadioDNS and generate a DAB SPI from it. It was written by Ben Poor and Nick Piggott. In this HowTo, I will describe how it can be installed alongside Python 3.

* Confused about EPG and SPI? In this context, EPG and SPI are basically the same thing. While EPG (Electronic Programme Guide) is an old, but commonly well-known term, SPI (Service and Programme Information) is now the official name of this feature.
* Some Service Providers only allow access to the SI (& PI) files if you get a Client ID (like an API key) from them first. This ClientID is associated with their FQDN (fully qualified domain name). You can create a CSV format file which holds the fqdns and associated ClientIDs, which allows the generator to provide the ClientID when it's asking for the SI & PI files.

===Notes===

'''This tool uses RadioDNS to locate and acquire Service Information (SI.xml), Programme Information (PI.xml) and Logos.'''
Each station you want to add to the SPI must be registered in RadioDNS using the correct information (Ensemble ID, Service ID, Service Component ID), and have correctly formatted SI, PI and logo files in PNG format. Find out more at https://radiodns.org/technical/documentation/howto/

I have assumed that you are logged in to your Linux system as a standard user and have sudo installed on your system. If sudo is not installed, you can see here, how to install it on Debian Jessie:
https://www.geek17.com/en/content/debian-8-jessie-install-and-configure-sudo-25

===Installation===

====Step 0: Update your system====
Begin with

sudo apt-get update

to make sure that you can install all that you need.

====Step 1: Miscellaneous dependencies====
First there are some dependencies to install with apt-get:

sudo apt-get install python3-setuptools python3-pip python3-crcmod python3-dateutil python3-isodate python3-pil git

Next there are some dependencies and subcomponents which must be downloaded from github and installed. Establish yourself in a suitable working directory (e.g. ~/src)

====Step 2: python-dabmot====

git clone https://github.com/Opendigitalradio/python-dabmot
cd python-dabmot
sudo pip3 install .
cd ..

====Step 3: python-mot-epg====

git clone https://github.com/Opendigitalradio/python-mot-epg
cd python-mot-epg
sudo pip3 install .
cd ..

====Step 4: python-msc====

git clone https://github.com/Opendigitalradio/python-dabmsc
cd python-dabmsc
sudo pip3 install .
cd ..

====Step 5: pyradiodns====

git clone https://github.com/radiodns/pyradiodns
cd pyradiodns
sudo python3 setup.py install
cd ..

'''NOTE'''
The installer specifies that dnspython must be at or greater than version 2.0 when used with python3. Most distributions ship with this version.
If the installer can't find dnspython>=2.0, you need to download, unpack, and manually install the package from https://pypi.org/simple/dnspython/

====Step 6: odr-radiodns-bridge====

git clone https://github.com/Opendigitalradio/odr-radiodns-bridge
cd odr-radiodns-bridge
sudo pip3 install .
cd ..

====Step 7: python-hybridspi====

git clone https://github.com/Opendigitalradio/python-hybridspi
cd python-hybridspi
sudo pip3 install .
cd ..

====Step 8: odr-radioepg-bridge====

git clone https://github.com/Opendigitalradio/odr-radioepg-bridge
sudo ln -f odr-radioepg-bridge/generate-epg /usr/local/bin/generate-epg

That's it. You should now be able to run this command and see a help text:
generate-epg -h

===Generating and broadcasting your SPI (EPG)===

====Generating your SPI====

Odr-radioepg-bridge is a command-line tool, which will:
* First read your mux.conf (from your ODR-DabMux configuration) to get information about your services.
* Then try to fetch SPI data for your services from the internet using RadioDNS.
* And lastly generate an output file containing a complete SPI.

If you type "generate-epg -h" you will get a list of available command-line arguments:

usage: generate-epg [-h] [-o OUTPUT] [-X] [-d DAYS] [-p PACKET_SIZE]
[-a PACKET_ADDRESS] [-D]
f

Encodes an SPI bitstream for services in a multiplex configuration file

positional arguments:
f multiplex configuration file

optional arguments:
-h, --help show this help message and exit
-o OUTPUT output bitstream file
-X turn debug on
-d DAYS number of days ahead to encode schedule files
-p PACKET_SIZE Packet size in bytes
-a PACKET_ADDRESS Packet address
-D output Datagroups instead of Packets
-c CLIENTIDS filename of CSV file of fqdn,ClientID key values

The positional argument tells the tool where to find your mux.conf.
The other arguments are optional, and some default values will be used if you don't set them:

* -o can be used to set filename and path to your output file (your SPI). Default is output.dat, placed in the folder from where you run the tool.
* -d is the number of days of programme schedule you want in you SPI. From 1 til 4 days, default is 2.
* -p is packet size. Available values are 24, 48, 72 and 96. Default is 96. Which value you should use, depends on the bitrate in which you are broadcasting your SPI (see below).
* -a is the packet address for your SPI. Default is 1, which will normally be fine. Important is, that you must set the same address in your mux.conf (see below).
* -D will tell the script to output Datagroups instead of Packets. This is useful for some commercial multiplexers or in case you want to broadcast your SPI as X-PAD instead of packet data. Note: You do not need this if you plan to broadcast your SPI the way it's described on this wiki page.
* -c gives the filename of a CSV formatted file which contains Fully Qualified Domain Names (fqdns) and Client IDs. Some service providers will only allow access to their SI file with a Client ID. Contact them directly for a Client ID.

example.org,wkljew324cx

Example:
If your mux.conf is placed in /home/user/odr/config/mux.conf, and you want 4 days in your SPI (today and the next 3 days) and you want to broadcast it in 16 kbit/s, your command line could look like this:

generate-epg -d 4 -p 48 /home/user/odr/config/mux.conf

This will generate a file named output.dat containing your SPI. In this example, I have set the packet size to 48, which is suitable for 16 kbit/s. I have not set the packet address, which means that the default value of 1 will be used.

====Packet sizes and bitrates====

The packet size, which you set when you generate your SPI, should match the bitrate in which you intend to broadcast it. If the packet size is too large, your SPI will not be transmitted. If the packet size is too small, your SPI will (probably) be transmitted, but it will be slower than necessary, because more space will be used for packet headers and maybe partly empty data packets. I will recommend these values:

{| class="wikitable"
! Bitrate
! Packet size
|-
| 8
| 24
|-
| 16
| 48
|-
| 24
| 72
|-
| 32
| 96
|-
| 48
| 72
|-
| 64
| 96
|}

====Broadcasting your SPI====

To broadcast your SPI using ODR-DabMux, create a packet data service in your mux.conf like in this example:

In the services section:

srv-spi {
label "EPG & Logos"
shortlabel "EPGLogos"
; the service-ID consists of 8 hex digits for packet data services. Usually the first two digits will
; be the same as your ECC, and the third digit will be the same as the first digit in your Ensemble Id.
id 0xe1912345
}

In the subchannels section:

sub-spi {
; type packet or enhancedpacket can be used for SPI.
type enhancedpacket
; if you change the bitrate, remember to also change the packet size accordingly (see above) and generate your SPI again.
bitrate 16
protection-profile EEP_A
protection 3
; inputuri is the path and filename for your output file from generate-epg
inputuri "/home/user/odr-radioepg-bridge-master/output.dat"
inputproto file
}

And in the components section (if you are using version 3.1.1 or earlier of odr-dabmux)

comp-spi {
type 60
service srv-spi
subchannel sub-spi
figtype 0x7
; The address must be the same as your packet address set when you generate the SPI (default value is 1).
address 0x1
datagroup true
}

If you are using version 3.1.2 or later of odr-dabmux, the construction of the component section is slightly different

comp-spi {
type 60
service srv-spi
subchannel sub-spi
user-applications {
userapp "spi"
}
address 0x1
datagroup true
}

That's it. Now (re)start your ODR-DabMux, and your SPI should be transmitted.

===Updating your SPI automatically every day===

====Feeding the SPI from a fifo will ensure that you can update it without restarting the MUX====

While the setup shown above will allow you to broadcast your SPI, it ''might'' not allow you to update your SPI without having to restart your MUX.
* If the SPI output file is ''rewritten'', the new content will be picked up by ODR-DabMux automatically, and your SPI will immediately be updated. This will be the case if you use generate-epg to generate a new file directly upon the the old one.
* However, if the SPI output file is ''replaced'', the new file will '''not''' be picked up by ODR-DabMux, until you restart it. This will be the case, if you generate a new file elsewhere (e.g. in a different folder or on another machine) and then ''copy'' it into where the old one is.

To get around this, and be sure that you can always update your SPI, any way you want, you can feed your SPI to ODR-DabMux from a named fifo instead of a file.

Navigate to the folder where you have your SPI and create a fifo like this:

mkfifo spififo

In the subchannel section of your mux.conf, you should replace your SPI file (output.dat) with your fifo, and also add a new line, "nonblock true", so that your SPI subchannel looks like this:

sub-spi {
; type packet or enhancedpacket can be used for SPI.
type enhancedpacket
; if you change the bitrate, remember to also change the packet size accordingly (see above) and generate your SPI again.
bitrate 16
protection-profile EEP_A
protection 3
; inputuri is the path and filename for your output from generate-epg
inputuri "/home/user/odr-radioepg-bridge-master/spififo"
inputproto file
nonblock true
}

Your SPI must be continously sent to the fifo. You can make a shell script for that. Create a file, sendspi.sh, with this content:

#!/bin/bash

while :
do

cat /home/user/odr-radioepg-bridge-master/output.dat >> /home/user/odr-radioepg-bridge-master/spififo

done

And make it executable (chmod +x sendspi.sh).

This script must be running all the time. If you're already using Supervisor to keep your MUX running (as described here: https://github.com/Opendigitalradio/dab-scripts), it's easy to also use supervisor for this script. Create a new file, sendspi.conf, in your /home/user/odr/config/supervisor folder with this content:

[program:sendspi]
command=bash -c "/home/user/odr-radioepg-bridge-master/sendspi.sh"
autostart=true
autorestart=true
startretries=99999
priority=10
stderr_logfile=/dev/stdout
stdout_logfile=/dev/stdout

Then run these commands:

sudo ln -s /home/user/odr/config/supervisor/sendspi.conf /etc/supervisor/conf.d/sendspi.conf
sudo supervisorctl reread
sudo supervisorctl update

Now your SPI is sent to ODR-DabMux from the fifo, and you will now be able to update your SPI, any way you want, without having to restart ODR-DabMux.

====Updating your SPI automatically every day====

You can update your SPI every 24 hours by adding a new daily task to cron.

Create a new file

/etc/cron.daily/spi

with the single line (with the same parameters as when you generate your SPI yourself)

/usr/local/bin/generate-epg -d 4 -p 48 /home/user/odr/config/mux.conf -o /home/user/odr-radioepg-bridge-master/output.dat

By default, the cron job will run every day at around 06:00. If you want your SPI to update more frequently (every 4 hours), you could add it to the user cron job with

crontab -e

and add the line

0 */4 * * * /usr/local/bin/generate-epg -d 4 -p 48 /home/user/odr/config/mux.conf -o /home/user/odr-radioepg-bridge-master/output.dat

'''NOTE:'''
The SPI creates new MOT TransportIDs for every object each time it is run. A receiver will not recognise that objects have been previously received and cached. If there is an interruption in reception, the SPI will be incomplete. The more frequently you update the SPI, more likely it is that a receiver will not be able to utilise the cached objects.

===Some observations===

* According to specs, logo slides in DAB EPG must be PNG. Although JPG is allowed in hybrid radio SPI, JPG logos will not be added to your DAB EPG. Be sure that your logos (at least those up to 320x240) are PNG.
* Resolved on 12APR21: (Programme descriptions (shortDescription) seem to be processed but not shown. Perhaps we will have to look a little further into this.)
* Updated on 15MAR22: Instructions are now for Python 3

How to configure SPI (Service and Programme Information) for ODR-DabMux

2024-04-08T16:06:51Z

Nickpiggott: /* Introduction */

Howto by Ulrik Brinck on odr-radioepg-bridge installation on Debian Jessie. Nick Piggott has contributed with some additions (and edited to show installation for Python 3)

This is now updated to run on Python 3. Instuctions on how to make it (mostly) run on Python 2 are below, but this is now deprecated.

'''This guide assumes your default python envrionment is Python 3.'''

===Introduction===

This tool (or rather series of tools) will pick up your SPI (Service and Programme Information) from the internet via RadioDNS and generate a DAB SPI from it. It was written by Ben Poor and Nick Piggott. In this HowTo, I will describe how it can be installed alongside Python 3.

* Confused about EPG and SPI? In this context, EPG and SPI are basically the same thing. While EPG (Electronic Programme Guide) is an old, but commonly well-known term, SPI (Service and Programme Information) is now the official name of this feature.
* Some Service Providers only allow access to the SI (& PI) files if you get a Client ID (like an API key) from them first. This ClientID is associated with their FQDN (fully qualified domain name). You can create a CSV format file which holds the fqdns and associated ClientIDs, which allows the generator to provide the ClientID when it's asking for the SI & PI files.

===Notes===

'''This tool uses RadioDNS to locate and acquire Service Information (SI.xml), Programme Information (PI.xml) and Logos.'''
Each station you want to add to the SPI must be registered in RadioDNS using the correct information (Ensemble ID, Service ID, Service Component ID), and have correctly formatted SI, PI and logo files in PNG format. Find out more at https://radiodns.org/technical/documentation/howto/

I have assumed that you are logged in to your Linux system as a standard user and have sudo installed on your system. If sudo is not installed, you can see here, how to install it on Debian Jessie:
https://www.geek17.com/en/content/debian-8-jessie-install-and-configure-sudo-25

===Installation===

====Step 0: Update your system====
Begin with

sudo apt-get update

to make sure that you can install all that you need.

====Step 1: Miscellaneous dependencies====
First there are some dependencies to install with apt-get:

sudo apt-get install python3-setuptools python3-pip python3-crcmod python3-dateutil python3-isodate python3-pil git

Next there are some dependencies and subcomponents which must be downloaded from github and installed. Establish yourself in a suitable working directory (e.g. ~/src)

====Step 2: python-dabmot====

git clone https://github.com/Opendigitalradio/python-dabmot
cd python-dabmot
sudo pip3 install .
cd ..

====Step 3: python-mot-epg====

git clone https://github.com/Opendigitalradio/python-mot-epg
cd python-mot-epg
sudo pip3 install .
cd ..

====Step 4: python-msc====

git clone https://github.com/Opendigitalradio/python-dabmsc
cd python-dabmsc
sudo pip3 install .
cd ..

====Step 5: pyradiodns====

git clone https://github.com/radiodns/pyradiodns
cd pyradiodns
sudo python3 setup.py install
cd ..

'''NOTE'''
The installer specifies that dnspython must be at or greater than version 2.0 when used with python3. Most distributions ship with this version.
If the installer can't find dnspython>=2.0, you need to download, unpack, and manually install the package from https://pypi.org/simple/dnspython/

====Step 6: odr-radiodns-bridge====

git clone https://github.com/Opendigitalradio/odr-radiodns-bridge
cd odr-radiodns-bridge
sudo pip3 install .
cd ..

====Step 7: python-hybridspi====

git clone https://github.com/Opendigitalradio/python-hybridspi
cd python-hybridspi
sudo pip3 install .
cd ..

====Step 8: odr-radioepg-bridge====

git clone https://github.com/Opendigitalradio/odr-radioepg-bridge
sudo ln -f odr-radioepg-bridge/generate-epg /usr/local/bin/generate-epg

That's it. You should now be able to run this command and see a help text:
generate-epg -h

===Generating and broadcasting your SPI (EPG)===

====Generating your SPI====

Odr-radioepg-bridge is a command-line tool, which will:
* First read your mux.conf (from your ODR-DabMux configuration) to get information about your services.
* Then try to fetch SPI data for your services from the internet using RadioDNS.
* And lastly generate an output file containing a complete SPI.

If you type "generate-epg -h" you will get a list of available command-line arguments:

usage: generate-epg [-h] [-o OUTPUT] [-X] [-d DAYS] [-p PACKET_SIZE]
[-a PACKET_ADDRESS] [-D]
f

Encodes an SPI bitstream for services in a multiplex configuration file

positional arguments:
f multiplex configuration file

optional arguments:
-h, --help show this help message and exit
-o OUTPUT output bitstream file
-X turn debug on
-d DAYS number of days ahead to encode schedule files
-p PACKET_SIZE Packet size in bytes
-a PACKET_ADDRESS Packet address
-D output Datagroups instead of Packets
-c CLIENTIDS filename of CSV file of fqdn,ClientID key values

The positional argument tells the tool where to find your mux.conf.
The other arguments are optional, and some default values will be used if you don't set them:

* -o can be used to set filename and path to your output file (your SPI). Default is output.dat, placed in the folder from where you run the tool.
* -d is the number of days of programme schedule you want in you SPI. From 1 til 4 days, default is 2.
* -p is packet size. Available values are 24, 48, 72 and 96. Default is 96. Which value you should use, depends on the bitrate in which you are broadcasting your SPI (see below).
* -a is the packet address for your SPI. Default is 1, which will normally be fine. Important is, that you must set the same address in your mux.conf (see below).
* -D will tell the script to output Datagroups instead of Packets. This is useful for some commercial multiplexers or in case you want to broadcast your SPI as X-PAD instead of packet data. Note: You do not need this if you plan to broadcast your SPI the way it's described on this wiki page.
* -c gives the filename of a CSV formatted file which contains Fully Qualified Domain Names (fqdns) and Client IDs. Some service providers will only allow access to their SI file with a Client ID. Contact them directly for a Client ID.
example:
example.org,wkljew324cx

Example:
If your mux.conf is placed in /home/user/odr/config/mux.conf, and you want 4 days in your SPI (today and the next 3 days) and you want to broadcast it in 16 kbit/s, your command line could look like this:

generate-epg -d 4 -p 48 /home/user/odr/config/mux.conf

This will generate a file named output.dat containing your SPI. In this example, I have set the packet size to 48, which is suitable for 16 kbit/s. I have not set the packet address, which means that the default value of 1 will be used.

====Packet sizes and bitrates====

The packet size, which you set when you generate your SPI, should match the bitrate in which you intend to broadcast it. If the packet size is too large, your SPI will not be transmitted. If the packet size is too small, your SPI will (probably) be transmitted, but it will be slower than necessary, because more space will be used for packet headers and maybe partly empty data packets. I will recommend these values:

{| class="wikitable"
! Bitrate
! Packet size
|-
| 8
| 24
|-
| 16
| 48
|-
| 24
| 72
|-
| 32
| 96
|-
| 48
| 72
|-
| 64
| 96
|}

====Broadcasting your SPI====

To broadcast your SPI using ODR-DabMux, create a packet data service in your mux.conf like in this example:

In the services section:

srv-spi {
label "EPG & Logos"
shortlabel "EPGLogos"
; the service-ID consists of 8 hex digits for packet data services. Usually the first two digits will
; be the same as your ECC, and the third digit will be the same as the first digit in your Ensemble Id.
id 0xe1912345
}

In the subchannels section:

sub-spi {
; type packet or enhancedpacket can be used for SPI.
type enhancedpacket
; if you change the bitrate, remember to also change the packet size accordingly (see above) and generate your SPI again.
bitrate 16
protection-profile EEP_A
protection 3
; inputuri is the path and filename for your output file from generate-epg
inputuri "/home/user/odr-radioepg-bridge-master/output.dat"
inputproto file
}

And in the components section (if you are using version 3.1.1 or earlier of odr-dabmux)

comp-spi {
type 60
service srv-spi
subchannel sub-spi
figtype 0x7
; The address must be the same as your packet address set when you generate the SPI (default value is 1).
address 0x1
datagroup true
}

If you are using version 3.1.2 or later of odr-dabmux, the construction of the component section is slightly different

comp-spi {
type 60
service srv-spi
subchannel sub-spi
user-applications {
userapp "spi"
}
address 0x1
datagroup true
}

That's it. Now (re)start your ODR-DabMux, and your SPI should be transmitted.

===Updating your SPI automatically every day===

====Feeding the SPI from a fifo will ensure that you can update it without restarting the MUX====

While the setup shown above will allow you to broadcast your SPI, it ''might'' not allow you to update your SPI without having to restart your MUX.
* If the SPI output file is ''rewritten'', the new content will be picked up by ODR-DabMux automatically, and your SPI will immediately be updated. This will be the case if you use generate-epg to generate a new file directly upon the the old one.
* However, if the SPI output file is ''replaced'', the new file will '''not''' be picked up by ODR-DabMux, until you restart it. This will be the case, if you generate a new file elsewhere (e.g. in a different folder or on another machine) and then ''copy'' it into where the old one is.

To get around this, and be sure that you can always update your SPI, any way you want, you can feed your SPI to ODR-DabMux from a named fifo instead of a file.

Navigate to the folder where you have your SPI and create a fifo like this:

mkfifo spififo

In the subchannel section of your mux.conf, you should replace your SPI file (output.dat) with your fifo, and also add a new line, "nonblock true", so that your SPI subchannel looks like this:

sub-spi {
; type packet or enhancedpacket can be used for SPI.
type enhancedpacket
; if you change the bitrate, remember to also change the packet size accordingly (see above) and generate your SPI again.
bitrate 16
protection-profile EEP_A
protection 3
; inputuri is the path and filename for your output from generate-epg
inputuri "/home/user/odr-radioepg-bridge-master/spififo"
inputproto file
nonblock true
}

Your SPI must be continously sent to the fifo. You can make a shell script for that. Create a file, sendspi.sh, with this content:

#!/bin/bash

while :
do

cat /home/user/odr-radioepg-bridge-master/output.dat >> /home/user/odr-radioepg-bridge-master/spififo

done

And make it executable (chmod +x sendspi.sh).

This script must be running all the time. If you're already using Supervisor to keep your MUX running (as described here: https://github.com/Opendigitalradio/dab-scripts), it's easy to also use supervisor for this script. Create a new file, sendspi.conf, in your /home/user/odr/config/supervisor folder with this content:

[program:sendspi]
command=bash -c "/home/user/odr-radioepg-bridge-master/sendspi.sh"
autostart=true
autorestart=true
startretries=99999
priority=10
stderr_logfile=/dev/stdout
stdout_logfile=/dev/stdout

Then run these commands:

sudo ln -s /home/user/odr/config/supervisor/sendspi.conf /etc/supervisor/conf.d/sendspi.conf
sudo supervisorctl reread
sudo supervisorctl update

Now your SPI is sent to ODR-DabMux from the fifo, and you will now be able to update your SPI, any way you want, without having to restart ODR-DabMux.

====Updating your SPI automatically every day====

You can update your SPI every 24 hours by adding a new daily task to cron.

Create a new file

/etc/cron.daily/spi

with the single line (with the same parameters as when you generate your SPI yourself)

/usr/local/bin/generate-epg -d 4 -p 48 /home/user/odr/config/mux.conf -o /home/user/odr-radioepg-bridge-master/output.dat

By default, the cron job will run every day at around 06:00. If you want your SPI to update more frequently (every 4 hours), you could add it to the user cron job with

crontab -e

and add the line

0 */4 * * * /usr/local/bin/generate-epg -d 4 -p 48 /home/user/odr/config/mux.conf -o /home/user/odr-radioepg-bridge-master/output.dat

'''NOTE:'''
The SPI creates new MOT TransportIDs for every object each time it is run. A receiver will not recognise that objects have been previously received and cached. If there is an interruption in reception, the SPI will be incomplete. The more frequently you update the SPI, more likely it is that a receiver will not be able to utilise the cached objects.

===Some observations===

* According to specs, logo slides in DAB EPG must be PNG. Although JPG is allowed in hybrid radio SPI, JPG logos will not be added to your DAB EPG. Be sure that your logos (at least those up to 320x240) are PNG.
* Resolved on 12APR21: (Programme descriptions (shortDescription) seem to be processed but not shown. Perhaps we will have to look a little further into this.)
* Updated on 15MAR22: Instructions are now for Python 3

How to configure SPI (Service and Programme Information) for ODR-DabMux

2024-04-08T16:05:05Z

Nickpiggott: /* Generating your SPI */

Howto by Ulrik Brinck on odr-radioepg-bridge installation on Debian Jessie. Nick Piggott has contributed with some additions (and edited to show installation for Python 3)

This is now updated to run on Python 3. Instuctions on how to make it (mostly) run on Python 2 are below, but this is now deprecated.

'''This guide assumes your default python envrionment is Python 3.'''

===Introduction===

This tool (or rather series of tools) will pick up your SPI (Service and Programme Information) from the internet via RadioDNS and generate a DAB SPI from it. It was written by Ben Poor and Nick Piggott. In this HowTo, I will describe how it can be installed alongside Python 3.

* Confused about EPG and SPI? In this context, EPG and SPI are basically the same thing. While EPG (Electronic Programme Guide) is an old, but commonly well-known term, SPI (Service and Programme Information) is now the official name of this feature.

===Notes===

'''This tool uses RadioDNS to locate and acquire Service Information (SI.xml), Programme Information (PI.xml) and Logos.'''
Each station you want to add to the SPI must be registered in RadioDNS using the correct information (Ensemble ID, Service ID, Service Component ID), and have correctly formatted SI, PI and logo files in PNG format. Find out more at https://radiodns.org/technical/documentation/howto/

I have assumed that you are logged in to your Linux system as a standard user and have sudo installed on your system. If sudo is not installed, you can see here, how to install it on Debian Jessie:
https://www.geek17.com/en/content/debian-8-jessie-install-and-configure-sudo-25

===Installation===

====Step 0: Update your system====
Begin with

sudo apt-get update

to make sure that you can install all that you need.

====Step 1: Miscellaneous dependencies====
First there are some dependencies to install with apt-get:

sudo apt-get install python3-setuptools python3-pip python3-crcmod python3-dateutil python3-isodate python3-pil git

Next there are some dependencies and subcomponents which must be downloaded from github and installed. Establish yourself in a suitable working directory (e.g. ~/src)

====Step 2: python-dabmot====

git clone https://github.com/Opendigitalradio/python-dabmot
cd python-dabmot
sudo pip3 install .
cd ..

====Step 3: python-mot-epg====

git clone https://github.com/Opendigitalradio/python-mot-epg
cd python-mot-epg
sudo pip3 install .
cd ..

====Step 4: python-msc====

git clone https://github.com/Opendigitalradio/python-dabmsc
cd python-dabmsc
sudo pip3 install .
cd ..

====Step 5: pyradiodns====

git clone https://github.com/radiodns/pyradiodns
cd pyradiodns
sudo python3 setup.py install
cd ..

'''NOTE'''
The installer specifies that dnspython must be at or greater than version 2.0 when used with python3. Most distributions ship with this version.
If the installer can't find dnspython>=2.0, you need to download, unpack, and manually install the package from https://pypi.org/simple/dnspython/

====Step 6: odr-radiodns-bridge====

git clone https://github.com/Opendigitalradio/odr-radiodns-bridge
cd odr-radiodns-bridge
sudo pip3 install .
cd ..

====Step 7: python-hybridspi====

git clone https://github.com/Opendigitalradio/python-hybridspi
cd python-hybridspi
sudo pip3 install .
cd ..

====Step 8: odr-radioepg-bridge====

git clone https://github.com/Opendigitalradio/odr-radioepg-bridge
sudo ln -f odr-radioepg-bridge/generate-epg /usr/local/bin/generate-epg

That's it. You should now be able to run this command and see a help text:
generate-epg -h

===Generating and broadcasting your SPI (EPG)===

====Generating your SPI====

Odr-radioepg-bridge is a command-line tool, which will:
* First read your mux.conf (from your ODR-DabMux configuration) to get information about your services.
* Then try to fetch SPI data for your services from the internet using RadioDNS.
* And lastly generate an output file containing a complete SPI.

If you type "generate-epg -h" you will get a list of available command-line arguments:

usage: generate-epg [-h] [-o OUTPUT] [-X] [-d DAYS] [-p PACKET_SIZE]
[-a PACKET_ADDRESS] [-D]
f

Encodes an SPI bitstream for services in a multiplex configuration file

positional arguments:
f multiplex configuration file

optional arguments:
-h, --help show this help message and exit
-o OUTPUT output bitstream file
-X turn debug on
-d DAYS number of days ahead to encode schedule files
-p PACKET_SIZE Packet size in bytes
-a PACKET_ADDRESS Packet address
-D output Datagroups instead of Packets
-c CLIENTIDS filename of CSV file of fqdn,ClientID key values

The positional argument tells the tool where to find your mux.conf.
The other arguments are optional, and some default values will be used if you don't set them:

* -o can be used to set filename and path to your output file (your SPI). Default is output.dat, placed in the folder from where you run the tool.
* -d is the number of days of programme schedule you want in you SPI. From 1 til 4 days, default is 2.
* -p is packet size. Available values are 24, 48, 72 and 96. Default is 96. Which value you should use, depends on the bitrate in which you are broadcasting your SPI (see below).
* -a is the packet address for your SPI. Default is 1, which will normally be fine. Important is, that you must set the same address in your mux.conf (see below).
* -D will tell the script to output Datagroups instead of Packets. This is useful for some commercial multiplexers or in case you want to broadcast your SPI as X-PAD instead of packet data. Note: You do not need this if you plan to broadcast your SPI the way it's described on this wiki page.
* -c gives the filename of a CSV formatted file which contains Fully Qualified Domain Names (fqdns) and Client IDs. Some service providers will only allow access to their SI file with a Client ID. Contact them directly for a Client ID.
example:
example.org,wkljew324cx

Example:
If your mux.conf is placed in /home/user/odr/config/mux.conf, and you want 4 days in your SPI (today and the next 3 days) and you want to broadcast it in 16 kbit/s, your command line could look like this:

generate-epg -d 4 -p 48 /home/user/odr/config/mux.conf

This will generate a file named output.dat containing your SPI. In this example, I have set the packet size to 48, which is suitable for 16 kbit/s. I have not set the packet address, which means that the default value of 1 will be used.

====Packet sizes and bitrates====

The packet size, which you set when you generate your SPI, should match the bitrate in which you intend to broadcast it. If the packet size is too large, your SPI will not be transmitted. If the packet size is too small, your SPI will (probably) be transmitted, but it will be slower than necessary, because more space will be used for packet headers and maybe partly empty data packets. I will recommend these values:

{| class="wikitable"
! Bitrate
! Packet size
|-
| 8
| 24
|-
| 16
| 48
|-
| 24
| 72
|-
| 32
| 96
|-
| 48
| 72
|-
| 64
| 96
|}

====Broadcasting your SPI====

To broadcast your SPI using ODR-DabMux, create a packet data service in your mux.conf like in this example:

In the services section:

srv-spi {
label "EPG & Logos"
shortlabel "EPGLogos"
; the service-ID consists of 8 hex digits for packet data services. Usually the first two digits will
; be the same as your ECC, and the third digit will be the same as the first digit in your Ensemble Id.
id 0xe1912345
}

In the subchannels section:

sub-spi {
; type packet or enhancedpacket can be used for SPI.
type enhancedpacket
; if you change the bitrate, remember to also change the packet size accordingly (see above) and generate your SPI again.
bitrate 16
protection-profile EEP_A
protection 3
; inputuri is the path and filename for your output file from generate-epg
inputuri "/home/user/odr-radioepg-bridge-master/output.dat"
inputproto file
}

And in the components section (if you are using version 3.1.1 or earlier of odr-dabmux)

comp-spi {
type 60
service srv-spi
subchannel sub-spi
figtype 0x7
; The address must be the same as your packet address set when you generate the SPI (default value is 1).
address 0x1
datagroup true
}

If you are using version 3.1.2 or later of odr-dabmux, the construction of the component section is slightly different

comp-spi {
type 60
service srv-spi
subchannel sub-spi
user-applications {
userapp "spi"
}
address 0x1
datagroup true
}

That's it. Now (re)start your ODR-DabMux, and your SPI should be transmitted.

===Updating your SPI automatically every day===

====Feeding the SPI from a fifo will ensure that you can update it without restarting the MUX====

While the setup shown above will allow you to broadcast your SPI, it ''might'' not allow you to update your SPI without having to restart your MUX.
* If the SPI output file is ''rewritten'', the new content will be picked up by ODR-DabMux automatically, and your SPI will immediately be updated. This will be the case if you use generate-epg to generate a new file directly upon the the old one.
* However, if the SPI output file is ''replaced'', the new file will '''not''' be picked up by ODR-DabMux, until you restart it. This will be the case, if you generate a new file elsewhere (e.g. in a different folder or on another machine) and then ''copy'' it into where the old one is.

To get around this, and be sure that you can always update your SPI, any way you want, you can feed your SPI to ODR-DabMux from a named fifo instead of a file.

Navigate to the folder where you have your SPI and create a fifo like this:

mkfifo spififo

In the subchannel section of your mux.conf, you should replace your SPI file (output.dat) with your fifo, and also add a new line, "nonblock true", so that your SPI subchannel looks like this:

sub-spi {
; type packet or enhancedpacket can be used for SPI.
type enhancedpacket
; if you change the bitrate, remember to also change the packet size accordingly (see above) and generate your SPI again.
bitrate 16
protection-profile EEP_A
protection 3
; inputuri is the path and filename for your output from generate-epg
inputuri "/home/user/odr-radioepg-bridge-master/spififo"
inputproto file
nonblock true
}

Your SPI must be continously sent to the fifo. You can make a shell script for that. Create a file, sendspi.sh, with this content:

#!/bin/bash

while :
do

cat /home/user/odr-radioepg-bridge-master/output.dat >> /home/user/odr-radioepg-bridge-master/spififo

done

And make it executable (chmod +x sendspi.sh).

This script must be running all the time. If you're already using Supervisor to keep your MUX running (as described here: https://github.com/Opendigitalradio/dab-scripts), it's easy to also use supervisor for this script. Create a new file, sendspi.conf, in your /home/user/odr/config/supervisor folder with this content:

[program:sendspi]
command=bash -c "/home/user/odr-radioepg-bridge-master/sendspi.sh"
autostart=true
autorestart=true
startretries=99999
priority=10
stderr_logfile=/dev/stdout
stdout_logfile=/dev/stdout

Then run these commands:

sudo ln -s /home/user/odr/config/supervisor/sendspi.conf /etc/supervisor/conf.d/sendspi.conf
sudo supervisorctl reread
sudo supervisorctl update

Now your SPI is sent to ODR-DabMux from the fifo, and you will now be able to update your SPI, any way you want, without having to restart ODR-DabMux.

====Updating your SPI automatically every day====

You can update your SPI every 24 hours by adding a new daily task to cron.

Create a new file

/etc/cron.daily/spi

with the single line (with the same parameters as when you generate your SPI yourself)

/usr/local/bin/generate-epg -d 4 -p 48 /home/user/odr/config/mux.conf -o /home/user/odr-radioepg-bridge-master/output.dat

By default, the cron job will run every day at around 06:00. If you want your SPI to update more frequently (every 4 hours), you could add it to the user cron job with

crontab -e

and add the line

0 */4 * * * /usr/local/bin/generate-epg -d 4 -p 48 /home/user/odr/config/mux.conf -o /home/user/odr-radioepg-bridge-master/output.dat

'''NOTE:'''
The SPI creates new MOT TransportIDs for every object each time it is run. A receiver will not recognise that objects have been previously received and cached. If there is an interruption in reception, the SPI will be incomplete. The more frequently you update the SPI, more likely it is that a receiver will not be able to utilise the cached objects.

===Some observations===

* According to specs, logo slides in DAB EPG must be PNG. Although JPG is allowed in hybrid radio SPI, JPG logos will not be added to your DAB EPG. Be sure that your logos (at least those up to 320x240) are PNG.
* Resolved on 12APR21: (Programme descriptions (shortDescription) seem to be processed but not shown. Perhaps we will have to look a little further into this.)
* Updated on 15MAR22: Instructions are now for Python 3

Main Page

2023-05-27T12:54:57Z

Nickpiggott: Added link to SPI Generator

__NOTOC__ __NOEDITSECTION__
<div style="font-size:282%">Opendigitalradio.org</div>

<P>

<BIG>
Open techniques for Digital Radio Broadcasting
</BIG>

{| style="width:100%; border-spacing:8px; margin:-8px -8px;"
|class="MainPageBG" style="width:100%; border:1px solid #ddcef2; background:#faf5ff; vertical-align:top; color:#000;"|
{| cellpadding="2" cellspacing="5" style="width:100%; vertical-align:top; background:#faf5ff; color:#000"
! <h2 style="margin:0; background:#ddcef2; font-size:120%; font-weight:bold; border:1px solid #afa3bf; text-align:left; color:#000; padding:0.2em 0.4em;">Background</h2>
|-
|style="color:#000;"|
Open digital broadcasting techniques based on software defined radio. Digital radio transmission and development must also become democratized for experimenters and small broadcasters. Opendigitalradio.org wiki is about creating a community for documenting and exchanging experimentations and gather information about existing small-scale DAB projects. Please read [[Introduction]] for more information.
'''[[Association Opendigitalradio|Opendigitalradio is a non-profit association based in Switzerland]]''' (page in french), offering also a broadcast infrastructure for temporary radio stations.

This wiki is also the home of the '''ODR-mmbTools''', the continuation of the CRC-mmbTools from [http://mmbtools.crc.ca CRC]. Please see [[Introduction on DAB/DAB+]]

Have a look at the [http://opendigitalradio.github.io/mmbtools-doc/mmbtools.pdf guide]

[[News|Older news]]
|-
|}
|}

{| style="width:100%; border-spacing:8px; margin:-8px -8px;"
|class="MainPageBG" style="border:1px solid #cef2e0; background:#f5fffa; vertical-align:top; color:#000;"|
{| cellpadding="2" cellspacing="5" style="width:100%; vertical-align:top; background:#f5fffa; color:#000"
! <h2 style="margin:0; background:#cef2e0; font-size:120%; font-weight:bold; border:1px solid #afa3bf; text-align:left; color:#000; padding:0.2em 0.4em;">DAB/DAB+ transmission</h2>
|-
|style="color:#000;"|
[[Image:Logo mmb.png|right]]
*[[Introduction on DAB/DAB+]]
*[[DAB/DAB+ encoding]]: MPEG Layer II or HE-AAC encoding, slideshow encoding
*[[DAB multiplexing]]: putting together DAB/DAB+/DMB programs
*[[DAB modulation]]: create the baseband COFDM modulation
*[[DAB hardware]]: software radio peripheral, filtering, amplification
|-
|}

{| cellpadding="2" cellspacing="5" style="width:100%; vertical-align:top; background:#f5fffa; color:#000"
! <h2 style="margin:0; background:#cef2e0; font-size:120%; font-weight:bold; border:1px solid #afa3bf; text-align:left; color:#000; padding:0.2em 0.4em;">Real cases, examples</h2>
|-
|style="color:#000;"|

The ODR-mmbTools are used in several real-world 24/7 broadcasts, as shown on http://www.opendigitalradio.org/software

A recipe for a low cost DAB transmission chain for local broadcasts based on the ODR-mmbTools is the [[RaspDAB]] description.

Older presentations:
*[http://www.slideshare.net/radioradioradio/local-dab-broadcasting Presentation] and [[WorldDMB GA 2010 Open DAB demonstration|demonstration]] of the full open source DAB transmission solution at 2010 WorldDMB General Assembly in Belfast
*[[First licensed open dab transmission]] for Label Suisse Festival 17-19 September 2010 Lausanne.
*[[Demonstration of open source digital transmission chain at IBC]], Stand 10.D21 (EBU), 10-14 September 2010
*[[DAB scripts examples]]
*[[Installer scripts]] for '''Debian'''
*[[How to configure SPI (Service and Programme Information) for ODR-DabMux]]
|-
|}
|}

{| style="width:100%; border-spacing:8px; margin:-8px -8px;"
|class="MainPageBG" style="border:1px solid #f2e0ce; background:#fffaf5; vertical-align:top; color:#000;"|
{| cellpadding="2" cellspacing="5" style="width:100%; vertical-align:top; background:#fffaf5; color:#000"
! <h2 style="margin:0; background:#f2e0ce; font-size:120%; font-weight:bold; border:1px solid #afa3bf; text-align:left; color:#000; padding:0.2em 0.4em;">Other digital systems, transmission and reception</h2>
|-
|style="color:#000;"|
*[[DAB reception]] (Openmokast and others)
*[[DAB measurement]] (measurement&monitoring tools, planning tools).
*[[DRM/DRM+ Digital Radio Mondiale]], digital radio system for AM bands (LW, MW and SW) and all VHF bands (FM band and others).
*[[FM RDS transmission]] (not really a digital system except RDS ;)
*[[Crazy techniques using a VGA card as radio peripheral]]
*[[Coverage planning]]
|-
|}
|}

{| style="width:100%; border-spacing:8px; margin:-8px -8px;"
|class="MainPageBG" style="width:100%; border:1px solid #cedff2; background:#f5faff; vertical-align:top; color:#000;"|
{| cellpadding="2" cellspacing="5" style="width:100%; vertical-align:top; background:#f5faff; color:#000"
! <h2 style="margin:0; background:#cedff2; font-size:120%; font-weight:bold; border:1px solid #afa3bf; text-align:left; color:#000; padding:0.2em 0.4em;">Contacts</h2>
|-
|style="color:#000;"|
Please follow the odr-mmbtools discussion on groups.io for bug reports, solutions and updates. See the webiste https://groups.io/g/odr-mmbtools how to subscribe. This is the follow up of the crc-mmbtools mailing list on googlegroups (https://groups.google.com/g/crc-mmbtools) , which is still available to check for solutions to older problems.

Follow us on '''Twitter''': http://twitter.com/opendigiradio to get informed, involved or for any questions. Find us [http://www.facebook.com/opendigitalradio also on '''Facebook''']

Email: broadcast at opendigitalradio.org
|-
|}
|}

How to configure SPI (Service and Programme Information) for ODR-DabMux

2023-05-27T12:51:04Z

Nickpiggott: Update external link to RadioDNS HOWTO guides

Howto by Ulrik Brinck on odr-radioepg-bridge installation on Debian Jessie. Nick Piggott has contributed with some additions (and edited to show installation for Python 3)

This is now updated to run on Python 3. Instuctions on how to make it (mostly) run on Python 2 are below, but this is now deprecated.

'''This guide assumes your default python envrionment is Python 3.'''

===Introduction===

This tool (or rather series of tools) will pick up your SPI (Service and Programme Information) from the internet via RadioDNS and generate a DAB SPI from it. It was written by Ben Poor and Nick Piggott. In this HowTo, I will describe how it can be installed alongside Python 3.

* Confused about EPG and SPI? In this context, EPG and SPI are basically the same thing. While EPG (Electronic Programme Guide) is an old, but commonly well-known term, SPI (Service and Programme Information) is now the official name of this feature.

===Notes===

'''This tool uses RadioDNS to locate and acquire Service Information (SI.xml), Programme Information (PI.xml) and Logos.'''
Each station you want to add to the SPI must be registered in RadioDNS using the correct information (Ensemble ID, Service ID, Service Component ID), and have correctly formatted SI, PI and logo files in PNG format. Find out more at https://radiodns.org/technical/documentation/howto/

I have assumed that you are logged in to your Linux system as a standard user and have sudo installed on your system. If sudo is not installed, you can see here, how to install it on Debian Jessie:
https://www.geek17.com/en/content/debian-8-jessie-install-and-configure-sudo-25

===Installation===

====Step 0: Update your system====
Begin with

sudo apt-get update

to make sure that you can install all that you need.

====Step 1: Miscellaneous dependencies====
First there are some dependencies to install with apt-get:

sudo apt-get install python3-setuptools python3-pip python3-crcmod python3-dateutil python3-isodate python3-pil git

Next there are some dependencies and subcomponents which must be downloaded from github and installed. Establish yourself in a suitable working directory (e.g. ~/src)

====Step 2: python-dabmot====

git clone https://github.com/Opendigitalradio/python-dabmot
cd python-dabmot
sudo pip3 install .
cd ..

====Step 3: python-mot-epg====

git clone https://github.com/Opendigitalradio/python-mot-epg
cd python-mot-epg
sudo pip3 install .
cd ..

====Step 4: python-msc====

git clone https://github.com/Opendigitalradio/python-dabmsc
cd python-dabmsc
sudo pip3 install .
cd ..

====Step 5: pyradiodns====

git clone https://github.com/radiodns/pyradiodns
cd pyradiodns
sudo python3 setup.py install
cd ..

'''NOTE'''
The installer specifies that dnspython must be at or greater than version 2.0 when used with python3. Most distributions ship with this version.
If the installer can't find dnspython>=2.0, you need to download, unpack, and manually install the package from https://pypi.org/simple/dnspython/

====Step 6: odr-radiodns-bridge====

git clone https://github.com/Opendigitalradio/odr-radiodns-bridge
cd odr-radiodns-bridge
sudo pip3 install .
cd ..

====Step 7: python-hybridspi====

git clone https://github.com/Opendigitalradio/python-hybridspi
cd python-hybridspi
sudo pip3 install .
cd ..

====Step 8: odr-radioepg-bridge====

git clone https://github.com/Opendigitalradio/odr-radioepg-bridge
sudo ln -f odr-radioepg-bridge/generate-epg /usr/local/bin/generate-epg

That's it. You should now be able to run this command and see a help text:
generate-epg -h

===Generating and broadcasting your SPI (EPG)===

====Generating your SPI====

Odr-radioepg-bridge is a command-line tool, which will:
* First read your mux.conf (from your ODR-DabMux configuration) to get information about your services.
* Then try to fetch SPI data for your services from the internet using RadioDNS.
* And lastly generate an output file containing a complete SPI.

If you type "generate-epg -h" you will get a list of available command-line arguments:

usage: generate-epg [-h] [-o OUTPUT] [-X] [-d DAYS] [-p PACKET_SIZE]
[-a PACKET_ADDRESS] [-D]
f

Encodes an SPI bitstream for services in a multiplex configuration file

positional arguments:
f multiplex configuration file

optional arguments:
-h, --help show this help message and exit
-o OUTPUT output bitstream file
-X turn debug on
-d DAYS number of days ahead to encode schedule files
-p PACKET_SIZE Packet size in bytes
-a PACKET_ADDRESS Packet address
-D output Datagroups instead of Packets

The positional argument tells the tool where to find your mux.conf.
The other arguments are optional, and some default values will be used if you don't set them:

* -o can be used to set filename and path to your output file (your SPI). Default is output.dat, placed in the folder from where you run the tool.
* -d is the number of days of programme schedule you want in you SPI. From 1 til 4 days, default is 2.
* -p is packet size. Available values are 24, 48, 72 and 96. Default is 96. Which value you should use, depends on the bitrate in which you are broadcasting your SPI (see below).
* -a is the packet address for your SPI. Default is 1, which will normally be fine. Important is, that you must set the same address in your mux.conf (see below).
* -D will tell the script to output Datagroups instead of Packets. This is useful for some commercial multiplexers or in case you want to broadcast your SPI as X-PAD instead of packet data. Note: You do not need this if you plan to broadcast your SPI the way it's described on this wiki page.

Example:
If your mux.conf is placed in /home/user/odr/config/mux.conf, and you want 4 days in your SPI (today and the next 3 days) and you want to broadcast it in 16 kbit/s, your command line could look like this:

generate-epg -d 4 -p 48 /home/user/odr/config/mux.conf

This will generate a file named output.dat containing your SPI. In this example, I have set the packet size to 48, which is suitable for 16 kbit/s. I have not set the packet address, which means that the default value of 1 will be used.

====Packet sizes and bitrates====

The packet size, which you set when you generate your SPI, should match the bitrate in which you intend to broadcast it. If the packet size is too large, your SPI will not be transmitted. If the packet size is too small, your SPI will (probably) be transmitted, but it will be slower than necessary, because more space will be used for packet headers and maybe partly empty data packets. I will recommend these values:

{| class="wikitable"
! Bitrate
! Packet size
|-
| 8
| 24
|-
| 16
| 48
|-
| 24
| 72
|-
| 32
| 96
|-
| 48
| 72
|-
| 64
| 96
|}

====Broadcasting your SPI====

To broadcast your SPI using ODR-DabMux, create a packet data service in your mux.conf like in this example:

In the services section:

srv-spi {
label "EPG & Logos"
shortlabel "EPGLogos"
; the service-ID consists of 8 hex digits for packet data services. Usually the first two digits will
; be the same as your ECC, and the third digit will be the same as the first digit in your Ensemble Id.
id 0xe1912345
}

In the subchannels section:

sub-spi {
; type packet or enhancedpacket can be used for SPI.
type enhancedpacket
; if you change the bitrate, remember to also change the packet size accordingly (see above) and generate your SPI again.
bitrate 16
protection-profile EEP_A
protection 3
; inputuri is the path and filename for your output file from generate-epg
inputuri "/home/user/odr-radioepg-bridge-master/output.dat"
inputproto file
}

And in the components section (if you are using version 3.1.1 or earlier of odr-dabmux)

comp-spi {
type 60
service srv-spi
subchannel sub-spi
figtype 0x7
; The address must be the same as your packet address set when you generate the SPI (default value is 1).
address 0x1
datagroup true
}

If you are using version 3.1.2 or later of odr-dabmux, the construction of the component section is slightly different

comp-spi {
type 60
service srv-spi
subchannel sub-spi
user-applications {
userapp "spi"
}
address 0x1
datagroup true
}

That's it. Now (re)start your ODR-DabMux, and your SPI should be transmitted.

===Updating your SPI automatically every day===

====Feeding the SPI from a fifo will ensure that you can update it without restarting the MUX====

While the setup shown above will allow you to broadcast your SPI, it ''might'' not allow you to update your SPI without having to restart your MUX.
* If the SPI output file is ''rewritten'', the new content will be picked up by ODR-DabMux automatically, and your SPI will immediately be updated. This will be the case if you use generate-epg to generate a new file directly upon the the old one.
* However, if the SPI output file is ''replaced'', the new file will '''not''' be picked up by ODR-DabMux, until you restart it. This will be the case, if you generate a new file elsewhere (e.g. in a different folder or on another machine) and then ''copy'' it into where the old one is.

To get around this, and be sure that you can always update your SPI, any way you want, you can feed your SPI to ODR-DabMux from a named fifo instead of a file.

Navigate to the folder where you have your SPI and create a fifo like this:

mkfifo spififo

In the subchannel section of your mux.conf, you should replace your SPI file (output.dat) with your fifo, and also add a new line, "nonblock true", so that your SPI subchannel looks like this:

sub-spi {
; type packet or enhancedpacket can be used for SPI.
type enhancedpacket
; if you change the bitrate, remember to also change the packet size accordingly (see above) and generate your SPI again.
bitrate 16
protection-profile EEP_A
protection 3
; inputuri is the path and filename for your output from generate-epg
inputuri "/home/user/odr-radioepg-bridge-master/spififo"
inputproto file
nonblock true
}

Your SPI must be continously sent to the fifo. You can make a shell script for that. Create a file, sendspi.sh, with this content:

#!/bin/bash

while :
do

cat /home/user/odr-radioepg-bridge-master/output.dat >> /home/user/odr-radioepg-bridge-master/spififo

done

And make it executable (chmod +x sendspi.sh).

This script must be running all the time. If you're already using Supervisor to keep your MUX running (as described here: https://github.com/Opendigitalradio/dab-scripts), it's easy to also use supervisor for this script. Create a new file, sendspi.conf, in your /home/user/odr/config/supervisor folder with this content:

[program:sendspi]
command=bash -c "/home/user/odr-radioepg-bridge-master/sendspi.sh"
autostart=true
autorestart=true
startretries=99999
priority=10
stderr_logfile=/dev/stdout
stdout_logfile=/dev/stdout

Then run these commands:

sudo ln -s /home/user/odr/config/supervisor/sendspi.conf /etc/supervisor/conf.d/sendspi.conf
sudo supervisorctl reread
sudo supervisorctl update

Now your SPI is sent to ODR-DabMux from the fifo, and you will now be able to update your SPI, any way you want, without having to restart ODR-DabMux.

====Updating your SPI automatically every day====

You can update your SPI every 24 hours by adding a new daily task to cron.

Create a new file

/etc/cron.daily/spi

with the single line (with the same parameters as when you generate your SPI yourself)

/usr/local/bin/generate-epg -d 4 -p 48 /home/user/odr/config/mux.conf -o /home/user/odr-radioepg-bridge-master/output.dat

By default, the cron job will run every day at around 06:00. If you want your SPI to update more frequently (every 4 hours), you could add it to the user cron job with

crontab -e

and add the line

0 */4 * * * /usr/local/bin/generate-epg -d 4 -p 48 /home/user/odr/config/mux.conf -o /home/user/odr-radioepg-bridge-master/output.dat

'''NOTE:'''
The SPI creates new MOT TransportIDs for every object each time it is run. A receiver will not recognise that objects have been previously received and cached. If there is an interruption in reception, the SPI will be incomplete. The more frequently you update the SPI, more likely it is that a receiver will not be able to utilise the cached objects.

===Some observations===

* According to specs, logo slides in DAB EPG must be PNG. Although JPG is allowed in hybrid radio SPI, JPG logos will not be added to your DAB EPG. Be sure that your logos (at least those up to 320x240) are PNG.
* Resolved on 12APR21: (Programme descriptions (shortDescription) seem to be processed but not shown. Perhaps we will have to look a little further into this.)
* Updated on 15MAR22: Instructions are now for Python 3

How to configure SPI (Service and Programme Information) for ODR-DabMux

2022-04-28T07:02:19Z

Nickpiggott: /* Step 8: odr-radioepg-bridge */

Howto by Ulrik Brinck on odr-radioepg-bridge installation on Debian Jessie. Nick Piggott has contributed with some additions (and edited to show installation for Python 3)

This is now updated to run on Python 3. Instuctions on how to make it (mostly) run on Python 2 are below, but this is now deprecated.

'''This guide assumes your default python envrionment is Python 3.'''

===Introduction===

This tool (or rather series of tools) will pick up your SPI (Service and Programme Information) from the internet via RadioDNS and generate a DAB SPI from it. It was written by Ben Poor and Nick Piggott. In this HowTo, I will describe how it can be installed alongside Python 3.

* Confused about EPG and SPI? In this context, EPG and SPI are basically the same thing. While EPG (Electronic Programme Guide) is an old, but commonly well-known term, SPI (Service and Programme Information) is now the official name of this feature.

===Notes===

'''This tool uses RadioDNS to locate and acquire Service Information (SI.xml), Programme Information (PI.xml) and Logos.'''
Each station you want to add to the SPI must be registered in RadioDNS using the correct information (Ensemble ID, Service ID, Service Component ID), and have correctly formatted SI, PI and logo files in PNG format. Find out more at https://radiodns.org/technical/documentation/#howto

I have assumed that you are logged in to your Linux system as a standard user and have sudo installed on your system. If sudo is not installed, you can see here, how to install it on Debian Jessie:
https://www.geek17.com/en/content/debian-8-jessie-install-and-configure-sudo-25

===Installation===

====Step 0: Update your system====
Begin with

sudo apt-get update

to make sure that you can install all that you need.

====Step 1: Miscellaneous dependencies====
First there are some dependencies to install with apt-get:

sudo apt-get install python3-setuptools python3-pip python3-crcmod python3-dateutil python3-isodate python3-pil git

Next there are some dependencies and subcomponents which must be downloaded from github and installed. Establish yourself in a suitable working directory (e.g. ~/src)

====Step 2: python-dabmot====

git clone https://github.com/Opendigitalradio/python-dabmot
cd python-dabmot
sudo pip3 install .
cd ..

====Step 3: python-mot-epg====

git clone https://github.com/Opendigitalradio/python-mot-epg
cd python-mot-epg
sudo pip3 install .
cd ..

====Step 4: python-msc====

git clone https://github.com/Opendigitalradio/python-dabmsc
cd python-dabmsc
sudo pip3 install .
cd ..

====Step 5: pyradiodns====

git clone https://github.com/radiodns/pyradiodns
cd pyradiodns
sudo python3 setup.py install
cd ..

'''NOTE'''
The installer specifies that dnspython must be at or greater than version 2.0 when used with python3. Most distributions ship with this version.
If the installer can't find dnspython>=2.0, you need to download, unpack, and manually install the package from https://pypi.org/simple/dnspython/

====Step 6: odr-radiodns-bridge====

git clone https://github.com/Opendigitalradio/odr-radiodns-bridge
cd odr-radiodns-bridge
sudo pip3 install .
cd ..

====Step 7: python-hybridspi====

git clone https://github.com/Opendigitalradio/python-hybridspi
cd python-hybridspi
sudo pip3 install .
cd ..

====Step 8: odr-radioepg-bridge====

git clone https://github.com/Opendigitalradio/odr-radioepg-bridge
sudo ln -f odr-radioepg-bridge/generate-epg /usr/local/bin/generate-epg

That's it. You should now be able to run this command and see a help text:
generate-epg -h

===Generating and broadcasting your SPI (EPG)===

====Generating your SPI====

Odr-radioepg-bridge is a command-line tool, which will:
* First read your mux.conf (from your ODR-DabMux configuration) to get information about your services.
* Then try to fetch SPI data for your services from the internet using RadioDNS.
* And lastly generate an output file containing a complete SPI.

If you type "generate-epg -h" you will get a list of available command-line arguments:

usage: generate-epg [-h] [-o OUTPUT] [-X] [-d DAYS] [-p PACKET_SIZE]
[-a PACKET_ADDRESS] [-D]
f

Encodes an SPI bitstream for services in a multiplex configuration file

positional arguments:
f multiplex configuration file

optional arguments:
-h, --help show this help message and exit
-o OUTPUT output bitstream file
-X turn debug on
-d DAYS number of days ahead to encode schedule files
-p PACKET_SIZE Packet size in bytes
-a PACKET_ADDRESS Packet address
-D output Datagroups instead of Packets

The positional argument tells the tool where to find your mux.conf.
The other arguments are optional, and some default values will be used if you don't set them:

* -o can be used to set filename and path to your output file (your SPI). Default is output.dat, placed in the folder from where you run the tool.
* -d is the number of days of programme schedule you want in you SPI. From 1 til 4 days, default is 2.
* -p is packet size. Available values are 24, 48, 72 and 96. Default is 96. Which value you should use, depends on the bitrate in which you are broadcasting your SPI (see below).
* -a is the packet address for your SPI. Default is 1, which will normally be fine. Important is, that you must set the same address in your mux.conf (see below).
* -D will tell the script to output Datagroups instead of Packets. This is useful for some commercial multiplexers or in case you want to broadcast your SPI as X-PAD instead of packet data. Note: You do not need this if you plan to broadcast your SPI the way it's described on this wiki page.

Example:
If your mux.conf is placed in /home/user/odr/config/mux.conf, and you want 4 days in your SPI (today and the next 3 days) and you want to broadcast it in 16 kbit/s, your command line could look like this:

generate-epg -d 4 -p 48 /home/user/odr/config/mux.conf

This will generate a file named output.dat containing your SPI. In this example, I have set the packet size to 48, which is suitable for 16 kbit/s. I have not set the packet address, which means that the default value of 1 will be used.

====Packet sizes and bitrates====

The packet size, which you set when you generate your SPI, should match the bitrate in which you intend to broadcast it. If the packet size is too large, your SPI will not be transmitted. If the packet size is too small, your SPI will (probably) be transmitted, but it will be slower than necessary, because more space will be used for packet headers and maybe partly empty data packets. I will recommend these values:

{| class="wikitable"
! Bitrate
! Packet size
|-
| 8
| 24
|-
| 16
| 48
|-
| 24
| 72
|-
| 32
| 96
|-
| 48
| 72
|-
| 64
| 96
|}

====Broadcasting your SPI====

To broadcast your SPI using ODR-DabMux, create a packet data service in your mux.conf like in this example:

In the services section:

srv-spi {
label "EPG & Logos"
shortlabel "EPGLogos"
; the service-ID consists of 8 hex digits for packet data services. Usually the first two digits will
; be the same as your ECC, and the third digit will be the same as the first digit in your Ensemble Id.
id 0xe1912345
}

In the subchannels section:

sub-spi {
; type packet or enhancedpacket can be used for SPI.
type enhancedpacket
; if you change the bitrate, remember to also change the packet size accordingly (see above) and generate your SPI again.
bitrate 16
protection-profile EEP_A
protection 3
; inputuri is the path and filename for your output file from generate-epg
inputuri "/home/user/odr-radioepg-bridge-master/output.dat"
inputproto file
}

And in the components section (if you are using version 3.1.1 or earlier of odr-dabmux)

comp-spi {
type 60
service srv-spi
subchannel sub-spi
figtype 0x7
; The address must be the same as your packet address set when you generate the SPI (default value is 1).
address 0x1
datagroup true
}

If you are using version 3.1.2 or later of odr-dabmux, the construction of the component section is slightly different

comp-spi {
type 60
service srv-spi
subchannel sub-spi
user-applications {
userapp "spi"
}
address 0x1
datagroup true
}

That's it. Now (re)start your ODR-DabMux, and your SPI should be transmitted.

===Updating your SPI automatically every day===

====Feeding the SPI from a fifo will ensure that you can update it without restarting the MUX====

While the setup shown above will allow you to broadcast your SPI, it ''might'' not allow you to update your SPI without having to restart your MUX.
* If the SPI output file is ''rewritten'', the new content will be picked up by ODR-DabMux automatically, and your SPI will immediately be updated. This will be the case if you use generate-epg to generate a new file directly upon the the old one.
* However, if the SPI output file is ''replaced'', the new file will '''not''' be picked up by ODR-DabMux, until you restart it. This will be the case, if you generate a new file elsewhere (e.g. in a different folder or on another machine) and then ''copy'' it into where the old one is.

To get around this, and be sure that you can always update your SPI, any way you want, you can feed your SPI to ODR-DabMux from a named fifo instead of a file.

Navigate to the folder where you have your SPI and create a fifo like this:

mkfifo spififo

In the subchannel section of your mux.conf, you should replace your SPI file (output.dat) with your fifo, and also add a new line, "nonblock true", so that your SPI subchannel looks like this:

sub-spi {
; type packet or enhancedpacket can be used for SPI.
type enhancedpacket
; if you change the bitrate, remember to also change the packet size accordingly (see above) and generate your SPI again.
bitrate 16
protection-profile EEP_A
protection 3
; inputuri is the path and filename for your output from generate-epg
inputuri "/home/user/odr-radioepg-bridge-master/spififo"
inputproto file
nonblock true
}

Your SPI must be continously sent to the fifo. You can make a shell script for that. Create a file, sendspi.sh, with this content:

#!/bin/bash

while :
do

cat /home/user/odr-radioepg-bridge-master/output.dat >> /home/user/odr-radioepg-bridge-master/spififo

done

And make it executable (chmod +x sendspi.sh).

This script must be running all the time. If you're already using Supervisor to keep your MUX running (as described here: https://github.com/Opendigitalradio/dab-scripts), it's easy to also use supervisor for this script. Create a new file, sendspi.conf, in your /home/user/odr/config/supervisor folder with this content:

[program:sendspi]
command=bash -c "/home/user/odr-radioepg-bridge-master/sendspi.sh"
autostart=true
autorestart=true
startretries=99999
priority=10
stderr_logfile=/dev/stdout
stdout_logfile=/dev/stdout

Then run these commands:

sudo ln -s /home/user/odr/config/supervisor/sendspi.conf /etc/supervisor/conf.d/sendspi.conf
sudo supervisorctl reread
sudo supervisorctl update

Now your SPI is sent to ODR-DabMux from the fifo, and you will now be able to update your SPI, any way you want, without having to restart ODR-DabMux.

====Updating your SPI automatically every day====

You can update your SPI every 24 hours by adding a new daily task to cron.

Create a new file

/etc/cron.daily/spi

with the single line (with the same parameters as when you generate your SPI yourself)

/usr/local/bin/generate-epg -d 4 -p 48 /home/user/odr/config/mux.conf -o /home/user/odr-radioepg-bridge-master/output.dat

By default, the cron job will run every day at around 06:00. If you want your SPI to update more frequently (every 4 hours), you could add it to the user cron job with

crontab -e

and add the line

0 */4 * * * /usr/local/bin/generate-epg -d 4 -p 48 /home/user/odr/config/mux.conf -o /home/user/odr-radioepg-bridge-master/output.dat

'''NOTE:'''
The SPI creates new MOT TransportIDs for every object each time it is run. A receiver will not recognise that objects have been previously received and cached. If there is an interruption in reception, the SPI will be incomplete. The more frequently you update the SPI, more likely it is that a receiver will not be able to utilise the cached objects.

===Some observations===

* According to specs, logo slides in DAB EPG must be PNG. Although JPG is allowed in hybrid radio SPI, JPG logos will not be added to your DAB EPG. Be sure that your logos (at least those up to 320x240) are PNG.
* Resolved on 12APR21: (Programme descriptions (shortDescription) seem to be processed but not shown. Perhaps we will have to look a little further into this.)
* Updated on 15MAR22: Instructions are now for Python 3

How to configure SPI (Service and Programme Information) for ODR-DabMux

2022-04-03T13:27:27Z

Nickpiggott: /* Step 5: pyradiodns */

Howto by Ulrik Brinck on odr-radioepg-bridge installation on Debian Jessie. Nick Piggott has contributed with some additions (and edited to show installation for Python 3)

This is now updated to run on Python 3. Instuctions on how to make it (mostly) run on Python 2 are below, but this is now deprecated.

'''This guide assumes your default python envrionment is Python 3.'''

===Introduction===

This tool (or rather series of tools) will pick up your SPI (Service and Programme Information) from the internet via RadioDNS and generate a DAB SPI from it. It was written by Ben Poor and Nick Piggott. In this HowTo, I will describe how it can be installed alongside Python 3.

* Confused about EPG and SPI? In this context, EPG and SPI are basically the same thing. While EPG (Electronic Programme Guide) is an old, but commonly well-known term, SPI (Service and Programme Information) is now the official name of this feature.

===Notes===

'''This tool uses RadioDNS to locate and acquire Service Information (SI.xml), Programme Information (PI.xml) and Logos.'''
Each station you want to add to the SPI must be registered in RadioDNS using the correct information (Ensemble ID, Service ID, Service Component ID), and have correctly formatted SI, PI and logo files in PNG format. Find out more at https://radiodns.org/technical/documentation/#howto

I have assumed that you are logged in to your Linux system as a standard user and have sudo installed on your system. If sudo is not installed, you can see here, how to install it on Debian Jessie:
https://www.geek17.com/en/content/debian-8-jessie-install-and-configure-sudo-25

===Installation===

====Step 0: Update your system====
Begin with

sudo apt-get update

to make sure that you can install all that you need.

====Step 1: Miscellaneous dependencies====
First there are some dependencies to install with apt-get:

sudo apt-get install python3-setuptools python3-pip python3-crcmod python3-dateutil python3-isodate python3-pil git

Next there are some dependencies and subcomponents which must be downloaded from github and installed. Establish yourself in a suitable working directory (e.g. ~/src)

====Step 2: python-dabmot====

git clone https://github.com/Opendigitalradio/python-dabmot
cd python-dabmot
sudo pip3 install .
cd ..

====Step 3: python-mot-epg====

git clone https://github.com/Opendigitalradio/python-mot-epg
cd python-mot-epg
sudo pip3 install .
cd ..

====Step 4: python-msc====

git clone https://github.com/Opendigitalradio/python-dabmsc
cd python-dabmsc
sudo pip3 install .
cd ..

====Step 5: pyradiodns====

git clone https://github.com/radiodns/pyradiodns
cd pyradiodns
sudo python3 setup.py install
cd ..

'''NOTE'''
The installer specifies that dnspython must be at or greater than version 2.0 when used with python3. Most distributions ship with this version.
If the installer can't find dnspython>=2.0, you need to download, unpack, and manually install the package from https://pypi.org/simple/dnspython/

====Step 6: odr-radiodns-bridge====

git clone https://github.com/Opendigitalradio/odr-radiodns-bridge
cd odr-radiodns-bridge
sudo pip3 install .
cd ..

====Step 7: python-hybridspi====

git clone https://github.com/Opendigitalradio/python-hybridspi
cd python-hybridspi
sudo pip3 install .
cd ..

====Step 8: odr-radioepg-bridge====

git clone https://github.com/Opendigitalradio/odr-radioepg-bridge
sudo ln odr-radioepg-bridge/generate-epg /usr/local/bin/generate-epg

That's it. You should now be able to run this command and see a help text:
generate-epg -h

===Generating and broadcasting your SPI (EPG)===

====Generating your SPI====

Odr-radioepg-bridge is a command-line tool, which will:
* First read your mux.conf (from your ODR-DabMux configuration) to get information about your services.
* Then try to fetch SPI data for your services from the internet using RadioDNS.
* And lastly generate an output file containing a complete SPI.

If you type "generate-epg -h" you will get a list of available command-line arguments:

usage: generate-epg [-h] [-o OUTPUT] [-X] [-d DAYS] [-p PACKET_SIZE]
[-a PACKET_ADDRESS] [-D]
f

Encodes an SPI bitstream for services in a multiplex configuration file

positional arguments:
f multiplex configuration file

optional arguments:
-h, --help show this help message and exit
-o OUTPUT output bitstream file
-X turn debug on
-d DAYS number of days ahead to encode schedule files
-p PACKET_SIZE Packet size in bytes
-a PACKET_ADDRESS Packet address
-D output Datagroups instead of Packets

The positional argument tells the tool where to find your mux.conf.
The other arguments are optional, and some default values will be used if you don't set them:

* -o can be used to set filename and path to your output file (your SPI). Default is output.dat, placed in the folder from where you run the tool.
* -d is the number of days of programme schedule you want in you SPI. From 1 til 4 days, default is 2.
* -p is packet size. Available values are 24, 48, 72 and 96. Default is 96. Which value you should use, depends on the bitrate in which you are broadcasting your SPI (see below).
* -a is the packet address for your SPI. Default is 1, which will normally be fine. Important is, that you must set the same address in your mux.conf (see below).
* -D will tell the script to output Datagroups instead of Packets. This is useful for some commercial multiplexers or in case you want to broadcast your SPI as X-PAD instead of packet data. Note: You do not need this if you plan to broadcast your SPI the way it's described on this wiki page.

Example:
If your mux.conf is placed in /home/user/odr/config/mux.conf, and you want 4 days in your SPI (today and the next 3 days) and you want to broadcast it in 16 kbit/s, your command line could look like this:

generate-epg -d 4 -p 48 /home/user/odr/config/mux.conf

This will generate a file named output.dat containing your SPI. In this example, I have set the packet size to 48, which is suitable for 16 kbit/s. I have not set the packet address, which means that the default value of 1 will be used.

====Packet sizes and bitrates====

The packet size, which you set when you generate your SPI, should match the bitrate in which you intend to broadcast it. If the packet size is too large, your SPI will not be transmitted. If the packet size is too small, your SPI will (probably) be transmitted, but it will be slower than necessary, because more space will be used for packet headers and maybe partly empty data packets. I will recommend these values:

{| class="wikitable"
! Bitrate
! Packet size
|-
| 8
| 24
|-
| 16
| 48
|-
| 24
| 72
|-
| 32
| 96
|-
| 48
| 72
|-
| 64
| 96
|}

====Broadcasting your SPI====

To broadcast your SPI using ODR-DabMux, create a packet data service in your mux.conf like in this example:

In the services section:

srv-spi {
label "EPG & Logos"
shortlabel "EPGLogos"
; the service-ID consists of 8 hex digits for packet data services. Usually the first two digits will
; be the same as your ECC, and the third digit will be the same as the first digit in your Ensemble Id.
id 0xe1912345
}

In the subchannels section:

sub-spi {
; type packet or enhancedpacket can be used for SPI.
type enhancedpacket
; if you change the bitrate, remember to also change the packet size accordingly (see above) and generate your SPI again.
bitrate 16
protection-profile EEP_A
protection 3
; inputuri is the path and filename for your output file from generate-epg
inputuri "/home/user/odr-radioepg-bridge-master/output.dat"
inputproto file
}

And in the components section (if you are using version 3.1.1 or earlier of odr-dabmux)

comp-spi {
type 60
service srv-spi
subchannel sub-spi
figtype 0x7
; The address must be the same as your packet address set when you generate the SPI (default value is 1).
address 0x1
datagroup true
}

If you are using version 3.1.2 or later of odr-dabmux, the construction of the component section is slightly different

comp-spi {
type 60
service srv-spi
subchannel sub-spi
user-applications {
userapp "spi"
}
address 0x1
datagroup true
}

That's it. Now (re)start your ODR-DabMux, and your SPI should be transmitted.

===Updating your SPI automatically every day===

====Feeding the SPI from a fifo will ensure that you can update it without restarting the MUX====

While the setup shown above will allow you to broadcast your SPI, it ''might'' not allow you to update your SPI without having to restart your MUX.
* If the SPI output file is ''rewritten'', the new content will be picked up by ODR-DabMux automatically, and your SPI will immediately be updated. This will be the case if you use generate-epg to generate a new file directly upon the the old one.
* However, if the SPI output file is ''replaced'', the new file will '''not''' be picked up by ODR-DabMux, until you restart it. This will be the case, if you generate a new file elsewhere (e.g. in a different folder or on another machine) and then ''copy'' it into where the old one is.

To get around this, and be sure that you can always update your SPI, any way you want, you can feed your SPI to ODR-DabMux from a named fifo instead of a file.

Navigate to the folder where you have your SPI and create a fifo like this:

mkfifo spififo

In the subchannel section of your mux.conf, you should replace your SPI file (output.dat) with your fifo, and also add a new line, "nonblock true", so that your SPI subchannel looks like this:

sub-spi {
; type packet or enhancedpacket can be used for SPI.
type enhancedpacket
; if you change the bitrate, remember to also change the packet size accordingly (see above) and generate your SPI again.
bitrate 16
protection-profile EEP_A
protection 3
; inputuri is the path and filename for your output from generate-epg
inputuri "/home/user/odr-radioepg-bridge-master/spififo"
inputproto file
nonblock true
}

Your SPI must be continously sent to the fifo. You can make a shell script for that. Create a file, sendspi.sh, with this content:

#!/bin/bash

while :
do

cat /home/user/odr-radioepg-bridge-master/output.dat >> /home/user/odr-radioepg-bridge-master/spififo

done

And make it executable (chmod +x sendspi.sh).

This script must be running all the time. If you're already using Supervisor to keep your MUX running (as described here: https://github.com/Opendigitalradio/dab-scripts), it's easy to also use supervisor for this script. Create a new file, sendspi.conf, in your /home/user/odr/config/supervisor folder with this content:

[program:sendspi]
command=bash -c "/home/user/odr-radioepg-bridge-master/sendspi.sh"
autostart=true
autorestart=true
startretries=99999
priority=10
stderr_logfile=/dev/stdout
stdout_logfile=/dev/stdout

Then run these commands:

sudo ln -s /home/user/odr/config/supervisor/sendspi.conf /etc/supervisor/conf.d/sendspi.conf
sudo supervisorctl reread
sudo supervisorctl update

Now your SPI is sent to ODR-DabMux from the fifo, and you will now be able to update your SPI, any way you want, without having to restart ODR-DabMux.

====Updating your SPI automatically every day====

You can update your SPI every 24 hours by adding a new daily task to cron.

Create a new file

/etc/cron.daily/spi

with the single line (with the same parameters as when you generate your SPI yourself)

/usr/local/bin/generate-epg -d 4 -p 48 /home/user/odr/config/mux.conf -o /home/user/odr-radioepg-bridge-master/output.dat

By default, the cron job will run every day at around 06:00. If you want your SPI to update more frequently (every 4 hours), you could add it to the user cron job with

crontab -e

and add the line

0 */4 * * * /usr/local/bin/generate-epg -d 4 -p 48 /home/user/odr/config/mux.conf -o /home/user/odr-radioepg-bridge-master/output.dat

'''NOTE:'''
The SPI creates new MOT TransportIDs for every object each time it is run. A receiver will not recognise that objects have been previously received and cached. If there is an interruption in reception, the SPI will be incomplete. The more frequently you update the SPI, more likely it is that a receiver will not be able to utilise the cached objects.

===Some observations===

* According to specs, logo slides in DAB EPG must be PNG. Although JPG is allowed in hybrid radio SPI, JPG logos will not be added to your DAB EPG. Be sure that your logos (at least those up to 320x240) are PNG.
* Resolved on 12APR21: (Programme descriptions (shortDescription) seem to be processed but not shown. Perhaps we will have to look a little further into this.)
* Updated on 15MAR22: Instructions are now for Python 3

How to configure SPI (Service and Programme Information) for ODR-DabMux

2022-04-01T18:18:01Z

Nickpiggott:

Howto by Ulrik Brinck on odr-radioepg-bridge installation on Debian Jessie. Nick Piggott has contributed with some additions (and edited to show installation for Python 3)

This is now updated to run on Python 3. Instuctions on how to make it (mostly) run on Python 2 are below, but this is now deprecated.

'''This guide assumes your default python envrionment is Python 3.'''

===Introduction===

This tool (or rather series of tools) will pick up your SPI (Service and Programme Information) from the internet via RadioDNS and generate a DAB SPI from it. It was written by Ben Poor and Nick Piggott. In this HowTo, I will describe how it can be installed alongside Python 3.

* Confused about EPG and SPI? In this context, EPG and SPI are basically the same thing. While EPG (Electronic Programme Guide) is an old, but commonly well-known term, SPI (Service and Programme Information) is now the official name of this feature.

===Notes===

'''This tool uses RadioDNS to locate and acquire Service Information (SI.xml), Programme Information (PI.xml) and Logos.'''
Each station you want to add to the SPI must be registered in RadioDNS using the correct information (Ensemble ID, Service ID, Service Component ID), and have correctly formatted SI, PI and logo files in PNG format. Find out more at https://radiodns.org/technical/documentation/#howto

I have assumed that you are logged in to your Linux system as a standard user and have sudo installed on your system. If sudo is not installed, you can see here, how to install it on Debian Jessie:
https://www.geek17.com/en/content/debian-8-jessie-install-and-configure-sudo-25

===Installation===

====Step 0: Update your system====
Begin with

sudo apt-get update

to make sure that you can install all that you need.

====Step 1: Miscellaneous dependencies====
First there are some dependencies to install with apt-get:

sudo apt-get install python3-setuptools python3-pip python3-crcmod python3-dateutil python3-isodate python3-pil git

Next there are some dependencies and subcomponents which must be downloaded from github and installed. Establish yourself in a suitable working directory (e.g. ~/src)

====Step 2: python-dabmot====

git clone https://github.com/Opendigitalradio/python-dabmot
cd python-dabmot
sudo pip3 install .
cd ..

====Step 3: python-mot-epg====

git clone https://github.com/Opendigitalradio/python-mot-epg
cd python-mot-epg
sudo pip3 install .
cd ..

====Step 4: python-msc====

git clone https://github.com/Opendigitalradio/python-dabmsc
cd python-dabmsc
sudo pip3 install .
cd ..

====Step 5: pyradiodns====

git clone https://github.com/radiodns/pyradiodns
cd pyradiodns
sudo python setup.py install
cd ..

'''NOTE'''
The installer specifies that dnspython must be at or greater than version 2.0 when used with python3. Most distributions ship with this version.
If the installer can't find dnspython>=2.0, you need to download, unpack, and manually install the package from https://pypi.org/simple/dnspython/

====Step 6: odr-radiodns-bridge====

git clone https://github.com/Opendigitalradio/odr-radiodns-bridge
cd odr-radiodns-bridge
sudo pip3 install .
cd ..

====Step 7: python-hybridspi====

git clone https://github.com/Opendigitalradio/python-hybridspi
cd python-hybridspi
sudo pip3 install .
cd ..

====Step 8: odr-radioepg-bridge====

git clone https://github.com/Opendigitalradio/odr-radioepg-bridge
sudo ln odr-radioepg-bridge/generate-epg /usr/local/bin/generate-epg

That's it. You should now be able to run this command and see a help text:
generate-epg -h

===Generating and broadcasting your SPI (EPG)===

====Generating your SPI====

Odr-radioepg-bridge is a command-line tool, which will:
* First read your mux.conf (from your ODR-DabMux configuration) to get information about your services.
* Then try to fetch SPI data for your services from the internet using RadioDNS.
* And lastly generate an output file containing a complete SPI.

If you type "generate-epg -h" you will get a list of available command-line arguments:

usage: generate-epg [-h] [-o OUTPUT] [-X] [-d DAYS] [-p PACKET_SIZE]
[-a PACKET_ADDRESS] [-D]
f

Encodes an SPI bitstream for services in a multiplex configuration file

positional arguments:
f multiplex configuration file

optional arguments:
-h, --help show this help message and exit
-o OUTPUT output bitstream file
-X turn debug on
-d DAYS number of days ahead to encode schedule files
-p PACKET_SIZE Packet size in bytes
-a PACKET_ADDRESS Packet address
-D output Datagroups instead of Packets

The positional argument tells the tool where to find your mux.conf.
The other arguments are optional, and some default values will be used if you don't set them:

* -o can be used to set filename and path to your output file (your SPI). Default is output.dat, placed in the folder from where you run the tool.
* -d is the number of days of programme schedule you want in you SPI. From 1 til 4 days, default is 2.
* -p is packet size. Available values are 24, 48, 72 and 96. Default is 96. Which value you should use, depends on the bitrate in which you are broadcasting your SPI (see below).
* -a is the packet address for your SPI. Default is 1, which will normally be fine. Important is, that you must set the same address in your mux.conf (see below).
* -D will tell the script to output Datagroups instead of Packets. This is useful for some commercial multiplexers or in case you want to broadcast your SPI as X-PAD instead of packet data. Note: You do not need this if you plan to broadcast your SPI the way it's described on this wiki page.

Example:
If your mux.conf is placed in /home/user/odr/config/mux.conf, and you want 4 days in your SPI (today and the next 3 days) and you want to broadcast it in 16 kbit/s, your command line could look like this:

generate-epg -d 4 -p 48 /home/user/odr/config/mux.conf

This will generate a file named output.dat containing your SPI. In this example, I have set the packet size to 48, which is suitable for 16 kbit/s. I have not set the packet address, which means that the default value of 1 will be used.

====Packet sizes and bitrates====

The packet size, which you set when you generate your SPI, should match the bitrate in which you intend to broadcast it. If the packet size is too large, your SPI will not be transmitted. If the packet size is too small, your SPI will (probably) be transmitted, but it will be slower than necessary, because more space will be used for packet headers and maybe partly empty data packets. I will recommend these values:

{| class="wikitable"
! Bitrate
! Packet size
|-
| 8
| 24
|-
| 16
| 48
|-
| 24
| 72
|-
| 32
| 96
|-
| 48
| 72
|-
| 64
| 96
|}

====Broadcasting your SPI====

To broadcast your SPI using ODR-DabMux, create a packet data service in your mux.conf like in this example:

In the services section:

srv-spi {
label "EPG & Logos"
shortlabel "EPGLogos"
; the service-ID consists of 8 hex digits for packet data services. Usually the first two digits will
; be the same as your ECC, and the third digit will be the same as the first digit in your Ensemble Id.
id 0xe1912345
}

In the subchannels section:

sub-spi {
; type packet or enhancedpacket can be used for SPI.
type enhancedpacket
; if you change the bitrate, remember to also change the packet size accordingly (see above) and generate your SPI again.
bitrate 16
protection-profile EEP_A
protection 3
; inputuri is the path and filename for your output file from generate-epg
inputuri "/home/user/odr-radioepg-bridge-master/output.dat"
inputproto file
}

And in the components section (if you are using version 3.1.1 or earlier of odr-dabmux)

comp-spi {
type 60
service srv-spi
subchannel sub-spi
figtype 0x7
; The address must be the same as your packet address set when you generate the SPI (default value is 1).
address 0x1
datagroup true
}

If you are using version 3.1.2 or later of odr-dabmux, the construction of the component section is slightly different

comp-spi {
type 60
service srv-spi
subchannel sub-spi
user-applications {
userapp "spi"
}
address 0x1
datagroup true
}

That's it. Now (re)start your ODR-DabMux, and your SPI should be transmitted.

===Updating your SPI automatically every day===

====Feeding the SPI from a fifo will ensure that you can update it without restarting the MUX====

While the setup shown above will allow you to broadcast your SPI, it ''might'' not allow you to update your SPI without having to restart your MUX.
* If the SPI output file is ''rewritten'', the new content will be picked up by ODR-DabMux automatically, and your SPI will immediately be updated. This will be the case if you use generate-epg to generate a new file directly upon the the old one.
* However, if the SPI output file is ''replaced'', the new file will '''not''' be picked up by ODR-DabMux, until you restart it. This will be the case, if you generate a new file elsewhere (e.g. in a different folder or on another machine) and then ''copy'' it into where the old one is.

To get around this, and be sure that you can always update your SPI, any way you want, you can feed your SPI to ODR-DabMux from a named fifo instead of a file.

Navigate to the folder where you have your SPI and create a fifo like this:

mkfifo spififo

In the subchannel section of your mux.conf, you should replace your SPI file (output.dat) with your fifo, and also add a new line, "nonblock true", so that your SPI subchannel looks like this:

sub-spi {
; type packet or enhancedpacket can be used for SPI.
type enhancedpacket
; if you change the bitrate, remember to also change the packet size accordingly (see above) and generate your SPI again.
bitrate 16
protection-profile EEP_A
protection 3
; inputuri is the path and filename for your output from generate-epg
inputuri "/home/user/odr-radioepg-bridge-master/spififo"
inputproto file
nonblock true
}

Your SPI must be continously sent to the fifo. You can make a shell script for that. Create a file, sendspi.sh, with this content:

#!/bin/bash

while :
do

cat /home/user/odr-radioepg-bridge-master/output.dat >> /home/user/odr-radioepg-bridge-master/spififo

done

And make it executable (chmod +x sendspi.sh).

This script must be running all the time. If you're already using Supervisor to keep your MUX running (as described here: https://github.com/Opendigitalradio/dab-scripts), it's easy to also use supervisor for this script. Create a new file, sendspi.conf, in your /home/user/odr/config/supervisor folder with this content:

[program:sendspi]
command=bash -c "/home/user/odr-radioepg-bridge-master/sendspi.sh"
autostart=true
autorestart=true
startretries=99999
priority=10
stderr_logfile=/dev/stdout
stdout_logfile=/dev/stdout

Then run these commands:

sudo ln -s /home/user/odr/config/supervisor/sendspi.conf /etc/supervisor/conf.d/sendspi.conf
sudo supervisorctl reread
sudo supervisorctl update

Now your SPI is sent to ODR-DabMux from the fifo, and you will now be able to update your SPI, any way you want, without having to restart ODR-DabMux.

====Updating your SPI automatically every day====

You can update your SPI every 24 hours by adding a new daily task to cron.

Create a new file

/etc/cron.daily/spi

with the single line (with the same parameters as when you generate your SPI yourself)

/usr/local/bin/generate-epg -d 4 -p 48 /home/user/odr/config/mux.conf -o /home/user/odr-radioepg-bridge-master/output.dat

By default, the cron job will run every day at around 06:00. If you want your SPI to update more frequently (every 4 hours), you could add it to the user cron job with

crontab -e

and add the line

0 */4 * * * /usr/local/bin/generate-epg -d 4 -p 48 /home/user/odr/config/mux.conf -o /home/user/odr-radioepg-bridge-master/output.dat

'''NOTE:'''
The SPI creates new MOT TransportIDs for every object each time it is run. A receiver will not recognise that objects have been previously received and cached. If there is an interruption in reception, the SPI will be incomplete. The more frequently you update the SPI, more likely it is that a receiver will not be able to utilise the cached objects.

===Some observations===

* According to specs, logo slides in DAB EPG must be PNG. Although JPG is allowed in hybrid radio SPI, JPG logos will not be added to your DAB EPG. Be sure that your logos (at least those up to 320x240) are PNG.
* Resolved on 12APR21: (Programme descriptions (shortDescription) seem to be processed but not shown. Perhaps we will have to look a little further into this.)
* Updated on 15MAR22: Instructions are now for Python 3

How to configure SPI (Service and Programme Information) for ODR-DabMux

2022-04-01T15:46:28Z

Nickpiggott:

Howto by Ulrik Brinck on odr-radioepg-bridge installation on Debian Jessie. Nick Piggott has contributed with some additions (and edited to show installation for Python 3)

This is now updated to run on Python 3. Instuctions on how to make it (mostly) run on Python 2 are below, but this is now deprecated.

'''This guide assumes your default python envrionment is Python 3.'''

===Introduction===

This tool (or rather series of tools) will pick up your SPI (Service and Programme Information) from the internet via RadioDNS and generate a DAB SPI from it. It was written by Ben Poor and Nick Piggott. In this HowTo, I will describe how it can be installed alongside Python 3.

* Confused about EPG and SPI? In this context, EPG and SPI are basically the same thing. While EPG (Electronic Programme Guide) is an old, but commonly well-known term, SPI (Service and Programme Information) is now the official name of this feature.

===Notes===

'''This tool uses RadioDNS to locate and acquire Service Information (SI.xml), Programme Information (PI.xml) and Logos.'''
Each station you want to add to the SPI must be registered in RadioDNS using the correct information (Ensemble ID, Service ID, Service Component ID), and have correctly formatted SI, PI and logo files in PNG format. Find out more at https://radiodns.org/technical/documentation/#howto

I have assumed that you are logged in to your Linux system as a standard user and have sudo installed on your system. If sudo is not installed, you can see here, how to install it on Debian Jessie:
https://www.geek17.com/en/content/debian-8-jessie-install-and-configure-sudo-25

===Installation===

====Step 0: Update your system====
Begin with

sudo apt-get update

to make sure that you can install all that you need.

====Step 1: Miscellaneous dependencies====
First there are some dependencies to install with apt-get:

sudo apt-get install python3-setuptools python3-crcmod python3-dateutil python3-isodate python3-pil git

Next there are some dependencies and subcomponents which must be downloaded from github and installed. Establish yourself in a suitable working directory (e.g. ~/src)

====Step 2: python-dabmot====

git clone https://github.com/Opendigitalradio/python-dabmot
cd python-dabmot
sudo pip3 install .
cd ..

====Step 3: python-mot-epg====

git clone https://github.com/Opendigitalradio/python-mot-epg
cd python-mot-epg
sudo pip3 install .
cd ..

====Step 4: python-msc====

git clone https://github.com/Opendigitalradio/python-dabmsc
cd python-dabmsc
sudo pip3 install .
cd ..

====Step 5: pyradiodns====

git clone https://github.com/radiodns/pyradiodns
cd pyradiodns
sudo python setup.py install
cd ..

'''NOTE'''
The installer specifies that dnspython must be at or greater than version 2.0 when used with python3. Most distributions ship with this version.
If the installer can't find dnspython>=2.0, you need to download, unpack, and manually install the package from https://pypi.org/simple/dnspython/

====Step 6: odr-radiodns-bridge====

git clone https://github.com/Opendigitalradio/odr-radiodns-bridge
cd odr-radiodns-bridge
sudo pip3 install .
cd ..

====Step 7: python-hybridspi====

git clone https://github.com/Opendigitalradio/python-hybridspi
cd python-hybridspi
sudo pip3 install .
cd ..

====Step 8: odr-radioepg-bridge====

git clone https://github.com/Opendigitalradio/odr-radioepg-bridge
sudo ln odr-radioepg-bridge/generate-epg /usr/local/bin/generate-epg

That's it. You should now be able to run this command and see a help text:
generate-epg -h

===Generating and broadcasting your SPI (EPG)===

====Generating your SPI====

Odr-radioepg-bridge is a command-line tool, which will:
* First read your mux.conf (from your ODR-DabMux configuration) to get information about your services.
* Then try to fetch SPI data for your services from the internet using RadioDNS.
* And lastly generate an output file containing a complete SPI.

If you type "generate-epg -h" you will get a list of available command-line arguments:

usage: generate-epg [-h] [-o OUTPUT] [-X] [-d DAYS] [-p PACKET_SIZE]
[-a PACKET_ADDRESS] [-D]
f

Encodes an SPI bitstream for services in a multiplex configuration file

positional arguments:
f multiplex configuration file

optional arguments:
-h, --help show this help message and exit
-o OUTPUT output bitstream file
-X turn debug on
-d DAYS number of days ahead to encode schedule files
-p PACKET_SIZE Packet size in bytes
-a PACKET_ADDRESS Packet address
-D output Datagroups instead of Packets

The positional argument tells the tool where to find your mux.conf.
The other arguments are optional, and some default values will be used if you don't set them:

* -o can be used to set filename and path to your output file (your SPI). Default is output.dat, placed in the folder from where you run the tool.
* -d is the number of days of programme schedule you want in you SPI. From 1 til 4 days, default is 2.
* -p is packet size. Available values are 24, 48, 72 and 96. Default is 96. Which value you should use, depends on the bitrate in which you are broadcasting your SPI (see below).
* -a is the packet address for your SPI. Default is 1, which will normally be fine. Important is, that you must set the same address in your mux.conf (see below).
* -D will tell the script to output Datagroups instead of Packets. This is useful for some commercial multiplexers or in case you want to broadcast your SPI as X-PAD instead of packet data. Note: You do not need this if you plan to broadcast your SPI the way it's described on this wiki page.

Example:
If your mux.conf is placed in /home/user/odr/config/mux.conf, and you want 4 days in your SPI (today and the next 3 days) and you want to broadcast it in 16 kbit/s, your command line could look like this:

generate-epg -d 4 -p 48 /home/user/odr/config/mux.conf

This will generate a file named output.dat containing your SPI. In this example, I have set the packet size to 48, which is suitable for 16 kbit/s. I have not set the packet address, which means that the default value of 1 will be used.

====Packet sizes and bitrates====

The packet size, which you set when you generate your SPI, should match the bitrate in which you intend to broadcast it. If the packet size is too large, your SPI will not be transmitted. If the packet size is too small, your SPI will (probably) be transmitted, but it will be slower than necessary, because more space will be used for packet headers and maybe partly empty data packets. I will recommend these values:

{| class="wikitable"
! Bitrate
! Packet size
|-
| 8
| 24
|-
| 16
| 48
|-
| 24
| 72
|-
| 32
| 96
|-
| 48
| 72
|-
| 64
| 96
|}

====Broadcasting your SPI====

To broadcast your SPI using ODR-DabMux, create a packet data service in your mux.conf like in this example:

In the services section:

srv-spi {
label "EPG & Logos"
shortlabel "EPGLogos"
; the service-ID consists of 8 hex digits for packet data services. Usually the first two digits will
; be the same as your ECC, and the third digit will be the same as the first digit in your Ensemble Id.
id 0xe1912345
}

In the subchannels section:

sub-spi {
; type packet or enhancedpacket can be used for SPI.
type enhancedpacket
; if you change the bitrate, remember to also change the packet size accordingly (see above) and generate your SPI again.
bitrate 16
protection-profile EEP_A
protection 3
; inputuri is the path and filename for your output file from generate-epg
inputuri "/home/user/odr-radioepg-bridge-master/output.dat"
inputproto file
}

And in the components section (if you are using version 3.1.1 or earlier of odr-dabmux)

comp-spi {
type 60
service srv-spi
subchannel sub-spi
figtype 0x7
; The address must be the same as your packet address set when you generate the SPI (default value is 1).
address 0x1
datagroup true
}

If you are using version 3.1.2 or later of odr-dabmux, the construction of the component section is slightly different

comp-spi {
type 60
service srv-spi
subchannel sub-spi
user-applications {
userapp "spi"
}
address 0x1
datagroup true
}

That's it. Now (re)start your ODR-DabMux, and your SPI should be transmitted.

===Updating your SPI automatically every day===

====Feeding the SPI from a fifo will ensure that you can update it without restarting the MUX====

While the setup shown above will allow you to broadcast your SPI, it ''might'' not allow you to update your SPI without having to restart your MUX.
* If the SPI output file is ''rewritten'', the new content will be picked up by ODR-DabMux automatically, and your SPI will immediately be updated. This will be the case if you use generate-epg to generate a new file directly upon the the old one.
* However, if the SPI output file is ''replaced'', the new file will '''not''' be picked up by ODR-DabMux, until you restart it. This will be the case, if you generate a new file elsewhere (e.g. in a different folder or on another machine) and then ''copy'' it into where the old one is.

To get around this, and be sure that you can always update your SPI, any way you want, you can feed your SPI to ODR-DabMux from a named fifo instead of a file.

Navigate to the folder where you have your SPI and create a fifo like this:

mkfifo spififo

In the subchannel section of your mux.conf, you should replace your SPI file (output.dat) with your fifo, and also add a new line, "nonblock true", so that your SPI subchannel looks like this:

sub-spi {
; type packet or enhancedpacket can be used for SPI.
type enhancedpacket
; if you change the bitrate, remember to also change the packet size accordingly (see above) and generate your SPI again.
bitrate 16
protection-profile EEP_A
protection 3
; inputuri is the path and filename for your output from generate-epg
inputuri "/home/user/odr-radioepg-bridge-master/spififo"
inputproto file
nonblock true
}

Your SPI must be continously sent to the fifo. You can make a shell script for that. Create a file, sendspi.sh, with this content:

#!/bin/bash

while :
do

cat /home/user/odr-radioepg-bridge-master/output.dat >> /home/user/odr-radioepg-bridge-master/spififo

done

And make it executable (chmod +x sendspi.sh).

This script must be running all the time. If you're already using Supervisor to keep your MUX running (as described here: https://github.com/Opendigitalradio/dab-scripts), it's easy to also use supervisor for this script. Create a new file, sendspi.conf, in your /home/user/odr/config/supervisor folder with this content:

[program:sendspi]
command=bash -c "/home/user/odr-radioepg-bridge-master/sendspi.sh"
autostart=true
autorestart=true
startretries=99999
priority=10
stderr_logfile=/dev/stdout
stdout_logfile=/dev/stdout

Then run these commands:

sudo ln -s /home/user/odr/config/supervisor/sendspi.conf /etc/supervisor/conf.d/sendspi.conf
sudo supervisorctl reread
sudo supervisorctl update

Now your SPI is sent to ODR-DabMux from the fifo, and you will now be able to update your SPI, any way you want, without having to restart ODR-DabMux.

====Updating your SPI automatically every day====

You can update your SPI every 24 hours by adding a new daily task to cron.

Create a new file

/etc/cron.daily/spi

with the single line (with the same parameters as when you generate your SPI yourself)

/usr/local/bin/generate-epg -d 4 -p 48 /home/user/odr/config/mux.conf -o /home/user/odr-radioepg-bridge-master/output.dat

By default, the cron job will run every day at around 06:00. If you want your SPI to update more frequently (every 4 hours), you could add it to the user cron job with

crontab -e

and add the line

0 */4 * * * /usr/local/bin/generate-epg -d 4 -p 48 /home/user/odr/config/mux.conf -o /home/user/odr-radioepg-bridge-master/output.dat

'''NOTE:'''
The SPI creates new MOT TransportIDs for every object each time it is run. A receiver will not recognise that objects have been previously received and cached. If there is an interruption in reception, the SPI will be incomplete. The more frequently you update the SPI, more likely it is that a receiver will not be able to utilise the cached objects.

===Some observations===

* According to specs, logo slides in DAB EPG must be PNG. Although JPG is allowed in hybrid radio SPI, JPG logos will not be added to your DAB EPG. Be sure that your logos (at least those up to 320x240) are PNG.
* Resolved on 12APR21: (Programme descriptions (shortDescription) seem to be processed but not shown. Perhaps we will have to look a little further into this.)
* Updated on 15MAR22: Instructions are now for Python 3

How to configure SPI (Service and Programme Information) for ODR-DabMux

2022-04-01T11:09:31Z

Nickpiggott: /* Step 8: odr-radioepg-bridge */

Howto by Ulrik Brinck on odr-radioepg-bridge installation on Debian Jessie. Nick Piggott has contributed with some additions (and edited to show installation for Python 3)

This is now updated to run on Python 3. Instuctions on how to make it (mostly) run on Python 2 are below, but this is now deprecated.

'''This guide assumes your default python envrionment is Python 3.'''

===Introduction===

This tool (or rather series of tools) will pick up your SPI (Service and Programme Information) from the internet via RadioDNS and generate a DAB SPI from it. It was written by Ben Poor and Nick Piggott. In this HowTo, I will describe how it can be installed alongside Python 3.

* Confused about EPG and SPI? In this context, EPG and SPI are basically the same thing. While EPG (Electronic Programme Guide) is an old, but commonly well-known term, SPI (Service and Programme Information) is now the official name of this feature.

===Notes===

'''This tool uses RadioDNS to locate and acquire Service Information (SI.xml), Programme Information (PI.xml) and Logos.'''
Each station you want to add to the SPI must be registered in RadioDNS using the correct information (Ensemble ID, Service ID, Service Component ID), and have correctly formatted SI, PI and logo files in PNG format. Find out more at https://radiodns.org/technical/documentation/#howto

I have assumed that you are logged in to your Linux system as a standard user and have sudo installed on your system. If sudo is not installed, you can see here, how to install it on Debian Jessie:
https://www.geek17.com/en/content/debian-8-jessie-install-and-configure-sudo-25

===Installation===

====Step 0: Update your system====
Begin with

sudo apt-get update

to make sure that you can install all that you need.

====Step 1: Miscellaneous dependencies====
First there are some dependencies to install with apt-get:

sudo apt-get install python3-setuptools python3-crcmod python3-dateutil python3-isodate python3-pil git

Next there are some dependencies and subcomponents which must be downloaded from github and installed. Establish yourself in a suitable working directory (e.g. ~/src)

====Step 2: python-dabmot====

git clone https://github.com/Opendigitalradio/python-dabmot
cd python-dabmot
sudo python setup.py install
cd ..

====Step 3: python-mot-epg====

git clone https://github.com/Opendigitalradio/python-mot-epg
cd python-mot-epg
sudo python setup.py install
cd ..

====Step 4: python-msc====

git clone https://github.com/Opendigitalradio/python-dabmsc
cd python-dabmsc
sudo python setup.py install
cd ..

====Step 5: pyradiodns====

git clone https://github.com/radiodns/pyradiodns
cd pyradiodns
sudo python setup.py install
cd ..

'''NOTE'''
The installer specifies that dnspython must be at or greater than version 2.0 when used with python3. Most distributions ship with this version.
If the installer can't find dnspython>=2.0, you need to download, unpack, and manually install the package from https://pypi.org/simple/dnspython/

====Step 6: odr-radiodns-bridge====

git clone https://github.com/Opendigitalradio/odr-radiodns-bridge
cd odr-radiodns-bridge
sudo python setup.py install
cd ..

====Step 7: python-hybridspi====

git clone https://github.com/Opendigitalradio/python-hybridspi
cd python-hybridspi
sudo python setup.py install
cd ..

====Step 8: odr-radioepg-bridge====

git clone https://github.com/Opendigitalradio/odr-radioepg-bridge
sudo ln odr-radioepg-bridge/generate-epg /usr/local/bin/generate-epg

That's it. You should now be able to run this command and see a help text:
generate-epg -h

===Generating and broadcasting your SPI (EPG)===

====Generating your SPI====

Odr-radioepg-bridge is a command-line tool, which will:
* First read your mux.conf (from your ODR-DabMux configuration) to get information about your services.
* Then try to fetch SPI data for your services from the internet using RadioDNS.
* And lastly generate an output file containing a complete SPI.

If you type "generate-epg -h" you will get a list of available command-line arguments:

usage: generate-epg [-h] [-o OUTPUT] [-X] [-d DAYS] [-p PACKET_SIZE]
[-a PACKET_ADDRESS] [-D]
f

Encodes an SPI bitstream for services in a multiplex configuration file

positional arguments:
f multiplex configuration file

optional arguments:
-h, --help show this help message and exit
-o OUTPUT output bitstream file
-X turn debug on
-d DAYS number of days ahead to encode schedule files
-p PACKET_SIZE Packet size in bytes
-a PACKET_ADDRESS Packet address
-D output Datagroups instead of Packets

The positional argument tells the tool where to find your mux.conf.
The other arguments are optional, and some default values will be used if you don't set them:

* -o can be used to set filename and path to your output file (your SPI). Default is output.dat, placed in the folder from where you run the tool.
* -d is the number of days of programme schedule you want in you SPI. From 1 til 4 days, default is 2.
* -p is packet size. Available values are 24, 48, 72 and 96. Default is 96. Which value you should use, depends on the bitrate in which you are broadcasting your SPI (see below).
* -a is the packet address for your SPI. Default is 1, which will normally be fine. Important is, that you must set the same address in your mux.conf (see below).
* -D will tell the script to output Datagroups instead of Packets. This is useful for some commercial multiplexers or in case you want to broadcast your SPI as X-PAD instead of packet data. Note: You do not need this if you plan to broadcast your SPI the way it's described on this wiki page.

Example:
If your mux.conf is placed in /home/user/odr/config/mux.conf, and you want 4 days in your SPI (today and the next 3 days) and you want to broadcast it in 16 kbit/s, your command line could look like this:

generate-epg -d 4 -p 48 /home/user/odr/config/mux.conf

This will generate a file named output.dat containing your SPI. In this example, I have set the packet size to 48, which is suitable for 16 kbit/s. I have not set the packet address, which means that the default value of 1 will be used.

====Packet sizes and bitrates====

The packet size, which you set when you generate your SPI, should match the bitrate in which you intend to broadcast it. If the packet size is too large, your SPI will not be transmitted. If the packet size is too small, your SPI will (probably) be transmitted, but it will be slower than necessary, because more space will be used for packet headers and maybe partly empty data packets. I will recommend these values:

{| class="wikitable"
! Bitrate
! Packet size
|-
| 8
| 24
|-
| 16
| 48
|-
| 24
| 72
|-
| 32
| 96
|-
| 48
| 72
|-
| 64
| 96
|}

====Broadcasting your SPI====

To broadcast your SPI using ODR-DabMux, create a packet data service in your mux.conf like in this example:

In the services section:

srv-spi {
label "EPG & Logos"
shortlabel "EPGLogos"
; the service-ID consists of 8 hex digits for packet data services. Usually the first two digits will
; be the same as your ECC, and the third digit will be the same as the first digit in your Ensemble Id.
id 0xe1912345
}

In the subchannels section:

sub-spi {
; type packet or enhancedpacket can be used for SPI.
type enhancedpacket
; if you change the bitrate, remember to also change the packet size accordingly (see above) and generate your SPI again.
bitrate 16
protection-profile EEP_A
protection 3
; inputuri is the path and filename for your output file from generate-epg
inputuri "/home/user/odr-radioepg-bridge-master/output.dat"
inputproto file
}

And in the components section (if you are using version 3.1.1 or earlier of odr-dabmux)

comp-spi {
type 60
service srv-spi
subchannel sub-spi
figtype 0x7
; The address must be the same as your packet address set when you generate the SPI (default value is 1).
address 0x1
datagroup true
}

If you are using version 3.1.2 or later of odr-dabmux, the construction of the component section is slightly different

comp-spi {
type 60
service srv-spi
subchannel sub-spi
user-applications {
userapp "spi"
}
address 0x1
datagroup true
}

That's it. Now (re)start your ODR-DabMux, and your SPI should be transmitted.

===Updating your SPI automatically every day===

====Feeding the SPI from a fifo will ensure that you can update it without restarting the MUX====

While the setup shown above will allow you to broadcast your SPI, it ''might'' not allow you to update your SPI without having to restart your MUX.
* If the SPI output file is ''rewritten'', the new content will be picked up by ODR-DabMux automatically, and your SPI will immediately be updated. This will be the case if you use generate-epg to generate a new file directly upon the the old one.
* However, if the SPI output file is ''replaced'', the new file will '''not''' be picked up by ODR-DabMux, until you restart it. This will be the case, if you generate a new file elsewhere (e.g. in a different folder or on another machine) and then ''copy'' it into where the old one is.

To get around this, and be sure that you can always update your SPI, any way you want, you can feed your SPI to ODR-DabMux from a named fifo instead of a file.

Navigate to the folder where you have your SPI and create a fifo like this:

mkfifo spififo

In the subchannel section of your mux.conf, you should replace your SPI file (output.dat) with your fifo, and also add a new line, "nonblock true", so that your SPI subchannel looks like this:

sub-spi {
; type packet or enhancedpacket can be used for SPI.
type enhancedpacket
; if you change the bitrate, remember to also change the packet size accordingly (see above) and generate your SPI again.
bitrate 16
protection-profile EEP_A
protection 3
; inputuri is the path and filename for your output from generate-epg
inputuri "/home/user/odr-radioepg-bridge-master/spififo"
inputproto file
nonblock true
}

Your SPI must be continously sent to the fifo. You can make a shell script for that. Create a file, sendspi.sh, with this content:

#!/bin/bash

while :
do

cat /home/user/odr-radioepg-bridge-master/output.dat >> /home/user/odr-radioepg-bridge-master/spififo

done

And make it executable (chmod +x sendspi.sh).

This script must be running all the time. If you're already using Supervisor to keep your MUX running (as described here: https://github.com/Opendigitalradio/dab-scripts), it's easy to also use supervisor for this script. Create a new file, sendspi.conf, in your /home/user/odr/config/supervisor folder with this content:

[program:sendspi]
command=bash -c "/home/user/odr-radioepg-bridge-master/sendspi.sh"
autostart=true
autorestart=true
startretries=99999
priority=10
stderr_logfile=/dev/stdout
stdout_logfile=/dev/stdout

Then run these commands:

sudo ln -s /home/user/odr/config/supervisor/sendspi.conf /etc/supervisor/conf.d/sendspi.conf
sudo supervisorctl reread
sudo supervisorctl update

Now your SPI is sent to ODR-DabMux from the fifo, and you will now be able to update your SPI, any way you want, without having to restart ODR-DabMux.

====Updating your SPI automatically every day====

You can update your SPI every 24 hours by adding a new daily task to cron.

Create a new file

/etc/cron.daily/spi

with the single line (with the same parameters as when you generate your SPI yourself)

/usr/local/bin/generate-epg -d 4 -p 48 /home/user/odr/config/mux.conf -o /home/user/odr-radioepg-bridge-master/output.dat

By default, the cron job will run every day at around 06:00. If you want your SPI to update more frequently (every 4 hours), you could add it to the user cron job with

crontab -e

and add the line

0 */4 * * * /usr/local/bin/generate-epg -d 4 -p 48 /home/user/odr/config/mux.conf -o /home/user/odr-radioepg-bridge-master/output.dat

'''NOTE:'''
The SPI creates new MOT TransportIDs for every object each time it is run. A receiver will not recognise that objects have been previously received and cached. If there is an interruption in reception, the SPI will be incomplete. The more frequently you update the SPI, more likely it is that a receiver will not be able to utilise the cached objects.

===Some observations===

* According to specs, logo slides in DAB EPG must be PNG. Although JPG is allowed in hybrid radio SPI, JPG logos will not be added to your DAB EPG. Be sure that your logos (at least those up to 320x240) are PNG.
* Resolved on 12APR21: (Programme descriptions (shortDescription) seem to be processed but not shown. Perhaps we will have to look a little further into this.)
* Updated on 15MAR22: Instructions are now for Python 3

How to configure SPI (Service and Programme Information) for ODR-DabMux

2022-04-01T08:03:10Z

Nickpiggott: /* Step 0: Update your system */

Howto by Ulrik Brinck on odr-radioepg-bridge installation on Debian Jessie. Nick Piggott has contributed with some additions (and edited to show installation for Python 3)

This is now updated to run on Python 3. Instuctions on how to make it (mostly) run on Python 2 are below, but this is now deprecated.

'''This guide assumes your default python envrionment is Python 3.'''

===Introduction===

This tool (or rather series of tools) will pick up your SPI (Service and Programme Information) from the internet via RadioDNS and generate a DAB SPI from it. It was written by Ben Poor and Nick Piggott. In this HowTo, I will describe how it can be installed alongside Python 3.

* Confused about EPG and SPI? In this context, EPG and SPI are basically the same thing. While EPG (Electronic Programme Guide) is an old, but commonly well-known term, SPI (Service and Programme Information) is now the official name of this feature.

===Notes===

'''This tool uses RadioDNS to locate and acquire Service Information (SI.xml), Programme Information (PI.xml) and Logos.'''
Each station you want to add to the SPI must be registered in RadioDNS using the correct information (Ensemble ID, Service ID, Service Component ID), and have correctly formatted SI, PI and logo files in PNG format. Find out more at https://radiodns.org/technical/documentation/#howto

I have assumed that you are logged in to your Linux system as a standard user and have sudo installed on your system. If sudo is not installed, you can see here, how to install it on Debian Jessie:
https://www.geek17.com/en/content/debian-8-jessie-install-and-configure-sudo-25

===Installation===

====Step 0: Update your system====
Begin with

sudo apt-get update

to make sure that you can install all that you need.

====Step 1: Miscellaneous dependencies====
First there are some dependencies to install with apt-get:

sudo apt-get install python3-setuptools python3-crcmod python3-dateutil python3-isodate python3-pil git

Next there are some dependencies and subcomponents which must be downloaded from github and installed. Establish yourself in a suitable working directory (e.g. ~/src)

====Step 2: python-dabmot====

git clone https://github.com/Opendigitalradio/python-dabmot
cd python-dabmot
sudo python setup.py install
cd ..

====Step 3: python-mot-epg====

git clone https://github.com/Opendigitalradio/python-mot-epg
cd python-mot-epg
sudo python setup.py install
cd ..

====Step 4: python-msc====

git clone https://github.com/Opendigitalradio/python-dabmsc
cd python-dabmsc
sudo python setup.py install
cd ..

====Step 5: pyradiodns====

git clone https://github.com/radiodns/pyradiodns
cd pyradiodns
sudo python setup.py install
cd ..

'''NOTE'''
The installer specifies that dnspython must be at or greater than version 2.0 when used with python3. Most distributions ship with this version.
If the installer can't find dnspython>=2.0, you need to download, unpack, and manually install the package from https://pypi.org/simple/dnspython/

====Step 6: odr-radiodns-bridge====

git clone https://github.com/Opendigitalradio/odr-radiodns-bridge
cd odr-radiodns-bridge
sudo python setup.py install
cd ..

====Step 7: python-hybridspi====

git clone https://github.com/Opendigitalradio/python-hybridspi
cd python-hybridspi
sudo python setup.py install
cd ..

====Step 8: odr-radioepg-bridge====

git clone https://github.com/Opendigitalradio/odr-radioepg-bridge
sudo ln -s odr-radioepg-bridge-master/generate-epg /usr/local/bin/generate-epg

That's it. You should now be able to run this command and see a help text:
generate-epg -h

===Generating and broadcasting your SPI (EPG)===

====Generating your SPI====

Odr-radioepg-bridge is a command-line tool, which will:
* First read your mux.conf (from your ODR-DabMux configuration) to get information about your services.
* Then try to fetch SPI data for your services from the internet using RadioDNS.
* And lastly generate an output file containing a complete SPI.

If you type "generate-epg -h" you will get a list of available command-line arguments:

usage: generate-epg [-h] [-o OUTPUT] [-X] [-d DAYS] [-p PACKET_SIZE]
[-a PACKET_ADDRESS] [-D]
f

Encodes an SPI bitstream for services in a multiplex configuration file

positional arguments:
f multiplex configuration file

optional arguments:
-h, --help show this help message and exit
-o OUTPUT output bitstream file
-X turn debug on
-d DAYS number of days ahead to encode schedule files
-p PACKET_SIZE Packet size in bytes
-a PACKET_ADDRESS Packet address
-D output Datagroups instead of Packets

The positional argument tells the tool where to find your mux.conf.
The other arguments are optional, and some default values will be used if you don't set them:

* -o can be used to set filename and path to your output file (your SPI). Default is output.dat, placed in the folder from where you run the tool.
* -d is the number of days of programme schedule you want in you SPI. From 1 til 4 days, default is 2.
* -p is packet size. Available values are 24, 48, 72 and 96. Default is 96. Which value you should use, depends on the bitrate in which you are broadcasting your SPI (see below).
* -a is the packet address for your SPI. Default is 1, which will normally be fine. Important is, that you must set the same address in your mux.conf (see below).
* -D will tell the script to output Datagroups instead of Packets. This is useful for some commercial multiplexers or in case you want to broadcast your SPI as X-PAD instead of packet data. Note: You do not need this if you plan to broadcast your SPI the way it's described on this wiki page.

Example:
If your mux.conf is placed in /home/user/odr/config/mux.conf, and you want 4 days in your SPI (today and the next 3 days) and you want to broadcast it in 16 kbit/s, your command line could look like this:

generate-epg -d 4 -p 48 /home/user/odr/config/mux.conf

This will generate a file named output.dat containing your SPI. In this example, I have set the packet size to 48, which is suitable for 16 kbit/s. I have not set the packet address, which means that the default value of 1 will be used.

====Packet sizes and bitrates====

The packet size, which you set when you generate your SPI, should match the bitrate in which you intend to broadcast it. If the packet size is too large, your SPI will not be transmitted. If the packet size is too small, your SPI will (probably) be transmitted, but it will be slower than necessary, because more space will be used for packet headers and maybe partly empty data packets. I will recommend these values:

{| class="wikitable"
! Bitrate
! Packet size
|-
| 8
| 24
|-
| 16
| 48
|-
| 24
| 72
|-
| 32
| 96
|-
| 48
| 72
|-
| 64
| 96
|}

====Broadcasting your SPI====

To broadcast your SPI using ODR-DabMux, create a packet data service in your mux.conf like in this example:

In the services section:

srv-spi {
label "EPG & Logos"
shortlabel "EPGLogos"
; the service-ID consists of 8 hex digits for packet data services. Usually the first two digits will
; be the same as your ECC, and the third digit will be the same as the first digit in your Ensemble Id.
id 0xe1912345
}

In the subchannels section:

sub-spi {
; type packet or enhancedpacket can be used for SPI.
type enhancedpacket
; if you change the bitrate, remember to also change the packet size accordingly (see above) and generate your SPI again.
bitrate 16
protection-profile EEP_A
protection 3
; inputuri is the path and filename for your output file from generate-epg
inputuri "/home/user/odr-radioepg-bridge-master/output.dat"
inputproto file
}

And in the components section (if you are using version 3.1.1 or earlier of odr-dabmux)

comp-spi {
type 60
service srv-spi
subchannel sub-spi
figtype 0x7
; The address must be the same as your packet address set when you generate the SPI (default value is 1).
address 0x1
datagroup true
}

If you are using version 3.1.2 or later of odr-dabmux, the construction of the component section is slightly different

comp-spi {
type 60
service srv-spi
subchannel sub-spi
user-applications {
userapp "spi"
}
address 0x1
datagroup true
}

That's it. Now (re)start your ODR-DabMux, and your SPI should be transmitted.

===Updating your SPI automatically every day===

====Feeding the SPI from a fifo will ensure that you can update it without restarting the MUX====

While the setup shown above will allow you to broadcast your SPI, it ''might'' not allow you to update your SPI without having to restart your MUX.
* If the SPI output file is ''rewritten'', the new content will be picked up by ODR-DabMux automatically, and your SPI will immediately be updated. This will be the case if you use generate-epg to generate a new file directly upon the the old one.
* However, if the SPI output file is ''replaced'', the new file will '''not''' be picked up by ODR-DabMux, until you restart it. This will be the case, if you generate a new file elsewhere (e.g. in a different folder or on another machine) and then ''copy'' it into where the old one is.

To get around this, and be sure that you can always update your SPI, any way you want, you can feed your SPI to ODR-DabMux from a named fifo instead of a file.

Navigate to the folder where you have your SPI and create a fifo like this:

mkfifo spififo

In the subchannel section of your mux.conf, you should replace your SPI file (output.dat) with your fifo, and also add a new line, "nonblock true", so that your SPI subchannel looks like this:

sub-spi {
; type packet or enhancedpacket can be used for SPI.
type enhancedpacket
; if you change the bitrate, remember to also change the packet size accordingly (see above) and generate your SPI again.
bitrate 16
protection-profile EEP_A
protection 3
; inputuri is the path and filename for your output from generate-epg
inputuri "/home/user/odr-radioepg-bridge-master/spififo"
inputproto file
nonblock true
}

Your SPI must be continously sent to the fifo. You can make a shell script for that. Create a file, sendspi.sh, with this content:

#!/bin/bash

while :
do

cat /home/user/odr-radioepg-bridge-master/output.dat >> /home/user/odr-radioepg-bridge-master/spififo

done

And make it executable (chmod +x sendspi.sh).

This script must be running all the time. If you're already using Supervisor to keep your MUX running (as described here: https://github.com/Opendigitalradio/dab-scripts), it's easy to also use supervisor for this script. Create a new file, sendspi.conf, in your /home/user/odr/config/supervisor folder with this content:

[program:sendspi]
command=bash -c "/home/user/odr-radioepg-bridge-master/sendspi.sh"
autostart=true
autorestart=true
startretries=99999
priority=10
stderr_logfile=/dev/stdout
stdout_logfile=/dev/stdout

Then run these commands:

sudo ln -s /home/user/odr/config/supervisor/sendspi.conf /etc/supervisor/conf.d/sendspi.conf
sudo supervisorctl reread
sudo supervisorctl update

Now your SPI is sent to ODR-DabMux from the fifo, and you will now be able to update your SPI, any way you want, without having to restart ODR-DabMux.

====Updating your SPI automatically every day====

You can update your SPI every 24 hours by adding a new daily task to cron.

Create a new file

/etc/cron.daily/spi

with the single line (with the same parameters as when you generate your SPI yourself)

/usr/local/bin/generate-epg -d 4 -p 48 /home/user/odr/config/mux.conf -o /home/user/odr-radioepg-bridge-master/output.dat

By default, the cron job will run every day at around 06:00. If you want your SPI to update more frequently (every 4 hours), you could add it to the user cron job with

crontab -e

and add the line

0 */4 * * * /usr/local/bin/generate-epg -d 4 -p 48 /home/user/odr/config/mux.conf -o /home/user/odr-radioepg-bridge-master/output.dat

'''NOTE:'''
The SPI creates new MOT TransportIDs for every object each time it is run. A receiver will not recognise that objects have been previously received and cached. If there is an interruption in reception, the SPI will be incomplete. The more frequently you update the SPI, more likely it is that a receiver will not be able to utilise the cached objects.

===Some observations===

* According to specs, logo slides in DAB EPG must be PNG. Although JPG is allowed in hybrid radio SPI, JPG logos will not be added to your DAB EPG. Be sure that your logos (at least those up to 320x240) are PNG.
* Resolved on 12APR21: (Programme descriptions (shortDescription) seem to be processed but not shown. Perhaps we will have to look a little further into this.)
* Updated on 15MAR22: Instructions are now for Python 3

How to configure SPI (Service and Programme Information) for ODR-DabMux

2022-04-01T08:02:10Z

Nickpiggott:

Howto by Ulrik Brinck on odr-radioepg-bridge installation on Debian Jessie. Nick Piggott has contributed with some additions (and edited to show installation for Python 3)

This is now updated to run on Python 3. Instuctions on how to make it (mostly) run on Python 2 are below, but this is now deprecated.

'''This guide assumes your default python envrionment is Python 3.'''

===Introduction===

This tool (or rather series of tools) will pick up your SPI (Service and Programme Information) from the internet via RadioDNS and generate a DAB SPI from it. It was written by Ben Poor and Nick Piggott. In this HowTo, I will describe how it can be installed alongside Python 3.

* Confused about EPG and SPI? In this context, EPG and SPI are basically the same thing. While EPG (Electronic Programme Guide) is an old, but commonly well-known term, SPI (Service and Programme Information) is now the official name of this feature.

===Notes===

'''This tool uses RadioDNS to locate and acquire Service Information (SI.xml), Programme Information (PI.xml) and Logos.'''
Each station you want to add to the SPI must be registered in RadioDNS using the correct information (Ensemble ID, Service ID, Service Component ID), and have correctly formatted SI, PI and logo files in PNG format. Find out more at https://radiodns.org/technical/documentation/#howto

I have assumed that you are logged in to your Linux system as a standard user and have sudo installed on your system. If sudo is not installed, you can see here, how to install it on Debian Jessie:
https://www.geek17.com/en/content/debian-8-jessie-install-and-configure-sudo-25

===Installation===

====Step 0: Update your system====
Begin with "sudo apt-get update" to make sure that you can install all that you need.

====Step 1: Miscellaneous dependencies====
First there are some dependencies to install with apt-get:

sudo apt-get install python3-setuptools python3-crcmod python3-dateutil python3-isodate python3-pil git

Next there are some dependencies and subcomponents which must be downloaded from github and installed. Establish yourself in a suitable working directory (e.g. ~/src)

====Step 2: python-dabmot====

git clone https://github.com/Opendigitalradio/python-dabmot
cd python-dabmot
sudo python setup.py install
cd ..

====Step 3: python-mot-epg====

git clone https://github.com/Opendigitalradio/python-mot-epg
cd python-mot-epg
sudo python setup.py install
cd ..

====Step 4: python-msc====

git clone https://github.com/Opendigitalradio/python-dabmsc
cd python-dabmsc
sudo python setup.py install
cd ..

====Step 5: pyradiodns====

git clone https://github.com/radiodns/pyradiodns
cd pyradiodns
sudo python setup.py install
cd ..

'''NOTE'''
The installer specifies that dnspython must be at or greater than version 2.0 when used with python3. Most distributions ship with this version.
If the installer can't find dnspython>=2.0, you need to download, unpack, and manually install the package from https://pypi.org/simple/dnspython/

====Step 6: odr-radiodns-bridge====

git clone https://github.com/Opendigitalradio/odr-radiodns-bridge
cd odr-radiodns-bridge
sudo python setup.py install
cd ..

====Step 7: python-hybridspi====

git clone https://github.com/Opendigitalradio/python-hybridspi
cd python-hybridspi
sudo python setup.py install
cd ..

====Step 8: odr-radioepg-bridge====

git clone https://github.com/Opendigitalradio/odr-radioepg-bridge
sudo ln -s odr-radioepg-bridge-master/generate-epg /usr/local/bin/generate-epg

That's it. You should now be able to run this command and see a help text:
generate-epg -h

===Generating and broadcasting your SPI (EPG)===

====Generating your SPI====

Odr-radioepg-bridge is a command-line tool, which will:
* First read your mux.conf (from your ODR-DabMux configuration) to get information about your services.
* Then try to fetch SPI data for your services from the internet using RadioDNS.
* And lastly generate an output file containing a complete SPI.

If you type "generate-epg -h" you will get a list of available command-line arguments:

usage: generate-epg [-h] [-o OUTPUT] [-X] [-d DAYS] [-p PACKET_SIZE]
[-a PACKET_ADDRESS] [-D]
f

Encodes an SPI bitstream for services in a multiplex configuration file

positional arguments:
f multiplex configuration file

optional arguments:
-h, --help show this help message and exit
-o OUTPUT output bitstream file
-X turn debug on
-d DAYS number of days ahead to encode schedule files
-p PACKET_SIZE Packet size in bytes
-a PACKET_ADDRESS Packet address
-D output Datagroups instead of Packets

The positional argument tells the tool where to find your mux.conf.
The other arguments are optional, and some default values will be used if you don't set them:

* -o can be used to set filename and path to your output file (your SPI). Default is output.dat, placed in the folder from where you run the tool.
* -d is the number of days of programme schedule you want in you SPI. From 1 til 4 days, default is 2.
* -p is packet size. Available values are 24, 48, 72 and 96. Default is 96. Which value you should use, depends on the bitrate in which you are broadcasting your SPI (see below).
* -a is the packet address for your SPI. Default is 1, which will normally be fine. Important is, that you must set the same address in your mux.conf (see below).
* -D will tell the script to output Datagroups instead of Packets. This is useful for some commercial multiplexers or in case you want to broadcast your SPI as X-PAD instead of packet data. Note: You do not need this if you plan to broadcast your SPI the way it's described on this wiki page.

Example:
If your mux.conf is placed in /home/user/odr/config/mux.conf, and you want 4 days in your SPI (today and the next 3 days) and you want to broadcast it in 16 kbit/s, your command line could look like this:

generate-epg -d 4 -p 48 /home/user/odr/config/mux.conf

This will generate a file named output.dat containing your SPI. In this example, I have set the packet size to 48, which is suitable for 16 kbit/s. I have not set the packet address, which means that the default value of 1 will be used.

====Packet sizes and bitrates====

The packet size, which you set when you generate your SPI, should match the bitrate in which you intend to broadcast it. If the packet size is too large, your SPI will not be transmitted. If the packet size is too small, your SPI will (probably) be transmitted, but it will be slower than necessary, because more space will be used for packet headers and maybe partly empty data packets. I will recommend these values:

{| class="wikitable"
! Bitrate
! Packet size
|-
| 8
| 24
|-
| 16
| 48
|-
| 24
| 72
|-
| 32
| 96
|-
| 48
| 72
|-
| 64
| 96
|}

====Broadcasting your SPI====

To broadcast your SPI using ODR-DabMux, create a packet data service in your mux.conf like in this example:

In the services section:

srv-spi {
label "EPG & Logos"
shortlabel "EPGLogos"
; the service-ID consists of 8 hex digits for packet data services. Usually the first two digits will
; be the same as your ECC, and the third digit will be the same as the first digit in your Ensemble Id.
id 0xe1912345
}

In the subchannels section:

sub-spi {
; type packet or enhancedpacket can be used for SPI.
type enhancedpacket
; if you change the bitrate, remember to also change the packet size accordingly (see above) and generate your SPI again.
bitrate 16
protection-profile EEP_A
protection 3
; inputuri is the path and filename for your output file from generate-epg
inputuri "/home/user/odr-radioepg-bridge-master/output.dat"
inputproto file
}

And in the components section (if you are using version 3.1.1 or earlier of odr-dabmux)

comp-spi {
type 60
service srv-spi
subchannel sub-spi
figtype 0x7
; The address must be the same as your packet address set when you generate the SPI (default value is 1).
address 0x1
datagroup true
}

If you are using version 3.1.2 or later of odr-dabmux, the construction of the component section is slightly different

comp-spi {
type 60
service srv-spi
subchannel sub-spi
user-applications {
userapp "spi"
}
address 0x1
datagroup true
}

That's it. Now (re)start your ODR-DabMux, and your SPI should be transmitted.

===Updating your SPI automatically every day===

====Feeding the SPI from a fifo will ensure that you can update it without restarting the MUX====

While the setup shown above will allow you to broadcast your SPI, it ''might'' not allow you to update your SPI without having to restart your MUX.
* If the SPI output file is ''rewritten'', the new content will be picked up by ODR-DabMux automatically, and your SPI will immediately be updated. This will be the case if you use generate-epg to generate a new file directly upon the the old one.
* However, if the SPI output file is ''replaced'', the new file will '''not''' be picked up by ODR-DabMux, until you restart it. This will be the case, if you generate a new file elsewhere (e.g. in a different folder or on another machine) and then ''copy'' it into where the old one is.

To get around this, and be sure that you can always update your SPI, any way you want, you can feed your SPI to ODR-DabMux from a named fifo instead of a file.

Navigate to the folder where you have your SPI and create a fifo like this:

mkfifo spififo

In the subchannel section of your mux.conf, you should replace your SPI file (output.dat) with your fifo, and also add a new line, "nonblock true", so that your SPI subchannel looks like this:

sub-spi {
; type packet or enhancedpacket can be used for SPI.
type enhancedpacket
; if you change the bitrate, remember to also change the packet size accordingly (see above) and generate your SPI again.
bitrate 16
protection-profile EEP_A
protection 3
; inputuri is the path and filename for your output from generate-epg
inputuri "/home/user/odr-radioepg-bridge-master/spififo"
inputproto file
nonblock true
}

Your SPI must be continously sent to the fifo. You can make a shell script for that. Create a file, sendspi.sh, with this content:

#!/bin/bash

while :
do

cat /home/user/odr-radioepg-bridge-master/output.dat >> /home/user/odr-radioepg-bridge-master/spififo

done

And make it executable (chmod +x sendspi.sh).

This script must be running all the time. If you're already using Supervisor to keep your MUX running (as described here: https://github.com/Opendigitalradio/dab-scripts), it's easy to also use supervisor for this script. Create a new file, sendspi.conf, in your /home/user/odr/config/supervisor folder with this content:

[program:sendspi]
command=bash -c "/home/user/odr-radioepg-bridge-master/sendspi.sh"
autostart=true
autorestart=true
startretries=99999
priority=10
stderr_logfile=/dev/stdout
stdout_logfile=/dev/stdout

Then run these commands:

sudo ln -s /home/user/odr/config/supervisor/sendspi.conf /etc/supervisor/conf.d/sendspi.conf
sudo supervisorctl reread
sudo supervisorctl update

Now your SPI is sent to ODR-DabMux from the fifo, and you will now be able to update your SPI, any way you want, without having to restart ODR-DabMux.

====Updating your SPI automatically every day====

You can update your SPI every 24 hours by adding a new daily task to cron.

Create a new file

/etc/cron.daily/spi

with the single line (with the same parameters as when you generate your SPI yourself)

/usr/local/bin/generate-epg -d 4 -p 48 /home/user/odr/config/mux.conf -o /home/user/odr-radioepg-bridge-master/output.dat

By default, the cron job will run every day at around 06:00. If you want your SPI to update more frequently (every 4 hours), you could add it to the user cron job with

crontab -e

and add the line

0 */4 * * * /usr/local/bin/generate-epg -d 4 -p 48 /home/user/odr/config/mux.conf -o /home/user/odr-radioepg-bridge-master/output.dat

'''NOTE:'''
The SPI creates new MOT TransportIDs for every object each time it is run. A receiver will not recognise that objects have been previously received and cached. If there is an interruption in reception, the SPI will be incomplete. The more frequently you update the SPI, more likely it is that a receiver will not be able to utilise the cached objects.

===Some observations===

* According to specs, logo slides in DAB EPG must be PNG. Although JPG is allowed in hybrid radio SPI, JPG logos will not be added to your DAB EPG. Be sure that your logos (at least those up to 320x240) are PNG.
* Resolved on 12APR21: (Programme descriptions (shortDescription) seem to be processed but not shown. Perhaps we will have to look a little further into this.)
* Updated on 15MAR22: Instructions are now for Python 3

How to install odr-radioepg-bridge in Debian Jessie

2022-03-15T20:36:22Z

Nickpiggott: Nickpiggott moved page How to install odr-radioepg-bridge in Debian Jessie to How to configure SPI (Service and Programme Information) for ODR-DabMux: More appropriate title

#REDIRECT [[How to configure SPI (Service and Programme Information) for ODR-DabMux]]

How to configure SPI (Service and Programme Information) for ODR-DabMux

2022-03-15T20:36:22Z

Nickpiggott: Nickpiggott moved page How to install odr-radioepg-bridge in Debian Jessie to How to configure SPI (Service and Programme Information) for ODR-DabMux: More appropriate title

Howto by Ulrik Brinck on odr-radioepg-bridge installation on Debian Jessie. Nick Piggott has contributed with some additions (and edited to show installation for Python 3)

This is now updated to run on Python 3. Instuctions on how to make it (mostly) run on Python 2 are below, but this is now deprecated.

'''This guide assumes your default python envrionment is Python 3.'''

===Introduction===

This tool (or rather series of tools) will pick up your SPI (Service and Programme Information) from the internet via RadioDNS and generate a DAB SPI from it. It was written by Ben Poor and Nick Piggott. In this HowTo, I will describe how it can be installed alongside Python 3.

* Confused about EPG and SPI? In this context, EPG and SPI are basically the same thing. While EPG (Electronic Programme Guide) is an old, but commonly well-known term, SPI (Service and Programme Information) is now the official name of this feature.

===Notes===

'''This tool uses RadioDNS to locate and acquire Service Information (SI.xml), Programme Information (PI.xml) and Logos.'''
Each station you want to add to the SPI must be registered in RadioDNS using the correct information (Ensemble ID, Service ID, Service Component ID), and have correctly formatted SI, PI and logo files in PNG format. Find out more at https://radiodns.org/technical/documentation/#howto

I have assumed that you are logged in to your Linux system as a standard user and have sudo installed on your system. If sudo is not installed, you can see here, how to install it on Debian Jessie:
https://www.geek17.com/en/content/debian-8-jessie-install-and-configure-sudo-25

===Installation===

====Step 0: Update your system====
Begin with "sudo apt-get update" to make sure that you can install all that you need.

====Step 1: Miscellaneous dependencies====
First there are some dependencies to install with apt-get:

sudo apt-get install python3-setuptools python3-crcmod python3-dateutil python3-isodate python3-pil git

Next there are some dependencies and subcomponents which must be downloaded from github and installed. Establish yourself in a suitable working directory (e.g. ~/src)

====Step 2: python-dabmot====

git clone https://github.com/Opendigitalradio/python-dabmot
cd python-dabmot
sudo python setup.py install
cd ..

====Step 3: python-mot-epg====

git clone https://github.com/Opendigitalradio/python-mot-epg
cd python-mot-epg
sudo python setup.py install
cd ..

====Step 4: python-msc====

git clone https://github.com/Opendigitalradio/python-dabmsc
cd python-dabmsc
sudo python setup.py install
cd ..

====Step 5: pyradiodns====

git clone https://github.com/radiodns/pyradiodns
cd pyradiodns
sudo python setup.py install
cd ..

'''NOTE'''
The installer specifies that dnspython must be at or greater than version 2.0 when used with python3. Most distributions ship with this version.
If the installer can't find dnspython>=2.0, you need to download, unpack, and manually install the package from https://pypi.org/simple/dnspython/

====Step 6: odr-radiodns-bridge====

git clone https://github.com/Opendigitalradio/odr-radiodns-bridge
cd odr-radiodns-bridge
sudo python setup.py install
cd ..

====Step 7: python-hybridspi====

git clone https://github.com/Opendigitalradio/python-hybridspi
cd python-hybridspi
sudo python setup.py install
cd ..

'''NOTE'''
The installer specifies bitarray at ''exactly'' version 1.2.0. You should make sure that you only have this version installed in your python enivronment.
If it isn't installed, you need to download, unpack, and manually install the package from https://pypi.org/simple/bitarray/

====Step 8: odr-radioepg-bridge====

git clone https://github.com/Opendigitalradio/odr-radioepg-bridge
sudo ln -s odr-radioepg-bridge-master/generate-epg /usr/local/bin/generate-epg

That's it. You should now be able to run this command and see a help text:
generate-epg -h

===Generating and broadcasting your SPI (EPG)===

====Generating your SPI====

Odr-radioepg-bridge is a command-line tool, which will:
* First read your mux.conf (from your ODR-DabMux configuration) to get information about your services.
* Then try to fetch SPI data for your services from the internet using RadioDNS.
* And lastly generate an output file containing a complete SPI.

If you type "generate-epg -h" you will get a list of available command-line arguments:

usage: generate-epg [-h] [-o OUTPUT] [-X] [-d DAYS] [-p PACKET_SIZE]
[-a PACKET_ADDRESS] [-D]
f

Encodes an SPI bitstream for services in a multiplex configuration file

positional arguments:
f multiplex configuration file

optional arguments:
-h, --help show this help message and exit
-o OUTPUT output bitstream file
-X turn debug on
-d DAYS number of days ahead to encode schedule files
-p PACKET_SIZE Packet size in bytes
-a PACKET_ADDRESS Packet address
-D output Datagroups instead of Packets

The positional argument tells the tool where to find your mux.conf.
The other arguments are optional, and some default values will be used if you don't set them:

* -o can be used to set filename and path to your output file (your SPI). Default is output.dat, placed in the folder from where you run the tool.
* -d is the number of days of programme schedule you want in you SPI. From 1 til 4 days, default is 2.
* -p is packet size. Available values are 24, 48, 72 and 96. Default is 96. Which value you should use, depends on the bitrate in which you are broadcasting your SPI (see below).
* -a is the packet address for your SPI. Default is 1, which will normally be fine. Important is, that you must set the same address in your mux.conf (see below).
* -D will tell the script to output Datagroups instead of Packets. This is useful for some commercial multiplexers or in case you want to broadcast your SPI as X-PAD instead of packet data. Note: You do not need this if you plan to broadcast your SPI the way it's described on this wiki page.

Example:
If your mux.conf is placed in /home/user/odr/config/mux.conf, and you want 4 days in your SPI (today and the next 3 days) and you want to broadcast it in 16 kbit/s, your command line could look like this:

generate-epg -d 4 -p 48 /home/user/odr/config/mux.conf

This will generate a file named output.dat containing your SPI. In this example, I have set the packet size to 48, which is suitable for 16 kbit/s. I have not set the packet address, which means that the default value of 1 will be used.

====Packet sizes and bitrates====

The packet size, which you set when you generate your SPI, should match the bitrate in which you intend to broadcast it. If the packet size is too large, your SPI will not be transmitted. If the packet size is too small, your SPI will (probably) be transmitted, but it will be slower than necessary, because more space will be used for packet headers and maybe partly empty data packets. I will recommend these values:

{| class="wikitable"
! Bitrate
! Packet size
|-
| 8
| 24
|-
| 16
| 48
|-
| 24
| 72
|-
| 32
| 96
|-
| 48
| 72
|-
| 64
| 96
|}

====Broadcasting your SPI====

To broadcast your SPI using ODR-DabMux, create a packet data service in your mux.conf like in this example:

In the services section:

srv-spi {
label "EPG & Logos"
shortlabel "EPGLogos"
; the service-ID consists of 8 hex digits for packet data services. Usually the first two digits will
; be the same as your ECC, and the third digit will be the same as the first digit in your Ensemble Id.
id 0xe1912345
}

In the subchannels section:

sub-spi {
; type packet or enhancedpacket can be used for SPI.
type enhancedpacket
; if you change the bitrate, remember to also change the packet size accordingly (see above) and generate your SPI again.
bitrate 16
protection-profile EEP_A
protection 3
; inputuri is the path and filename for your output file from generate-epg
inputuri "/home/user/odr-radioepg-bridge-master/output.dat"
inputproto file
}

And in the components section (if you are using version 3.1.1 or earlier of odr-dabmux)

comp-spi {
type 60
service srv-spi
subchannel sub-spi
figtype 0x7
; The address must be the same as your packet address set when you generate the SPI (default value is 1).
address 0x1
datagroup true
}

If you are using version 3.1.2 or later of odr-dabmux, the construction of the component section is slightly different

comp-spi {
type 60
service srv-spi
subchannel sub-spi
user-applications {
userapp "spi"
}
address 0x1
datagroup true
}

That's it. Now (re)start your ODR-DabMux, and your SPI should be transmitted.

===Updating your SPI automatically every day===

====Feeding the SPI from a fifo will ensure that you can update it without restarting the MUX====

While the setup shown above will allow you to broadcast your SPI, it ''might'' not allow you to update your SPI without having to restart your MUX.
* If the SPI output file is ''rewritten'', the new content will be picked up by ODR-DabMux automatically, and your SPI will immediately be updated. This will be the case if you use generate-epg to generate a new file directly upon the the old one.
* However, if the SPI output file is ''replaced'', the new file will '''not''' be picked up by ODR-DabMux, until you restart it. This will be the case, if you generate a new file elsewhere (e.g. in a different folder or on another machine) and then ''copy'' it into where the old one is.

To get around this, and be sure that you can always update your SPI, any way you want, you can feed your SPI to ODR-DabMux from a named fifo instead of a file.

Navigate to the folder where you have your SPI and create a fifo like this:

mkfifo spififo

In the subchannel section of your mux.conf, you should replace your SPI file (output.dat) with your fifo, and also add a new line, "nonblock true", so that your SPI subchannel looks like this:

sub-spi {
; type packet or enhancedpacket can be used for SPI.
type enhancedpacket
; if you change the bitrate, remember to also change the packet size accordingly (see above) and generate your SPI again.
bitrate 16
protection-profile EEP_A
protection 3
; inputuri is the path and filename for your output from generate-epg
inputuri "/home/user/odr-radioepg-bridge-master/spififo"
inputproto file
nonblock true
}

Your SPI must be continously sent to the fifo. You can make a shell script for that. Create a file, sendspi.sh, with this content:

#!/bin/bash

while :
do

cat /home/user/odr-radioepg-bridge-master/output.dat >> /home/user/odr-radioepg-bridge-master/spififo

done

And make it executable (chmod +x sendspi.sh).

This script must be running all the time. If you're already using Supervisor to keep your MUX running (as described here: https://github.com/Opendigitalradio/dab-scripts), it's easy to also use supervisor for this script. Create a new file, sendspi.conf, in your /home/user/odr/config/supervisor folder with this content:

[program:sendspi]
command=bash -c "/home/user/odr-radioepg-bridge-master/sendspi.sh"
autostart=true
autorestart=true
startretries=99999
priority=10
stderr_logfile=/dev/stdout
stdout_logfile=/dev/stdout

Then run these commands:

sudo ln -s /home/user/odr/config/supervisor/sendspi.conf /etc/supervisor/conf.d/sendspi.conf
sudo supervisorctl reread
sudo supervisorctl update

Now your SPI is sent to ODR-DabMux from the fifo, and you will now be able to update your SPI, any way you want, without having to restart ODR-DabMux.

====Updating your SPI automatically every day====

You can update your SPI every 24 hours by adding a new daily task to cron.

Create a new file

/etc/cron.daily/spi

with the single line (with the same parameters as when you generate your SPI yourself)

/usr/local/bin/generate-epg -d 4 -p 48 /home/user/odr/config/mux.conf -o /home/user/odr-radioepg-bridge-master/output.dat

By default, the cron job will run every day at around 06:00. If you want your SPI to update more frequently (every 4 hours), you could add it to the user cron job with

crontab -e

and add the line

0 */4 * * * /usr/local/bin/generate-epg -d 4 -p 48 /home/user/odr/config/mux.conf -o /home/user/odr-radioepg-bridge-master/output.dat

'''NOTE:'''
The SPI creates new MOT TransportIDs for every object each time it is run. A receiver will not recognise that objects have been previously received and cached. If there is an interruption in reception, the SPI will be incomplete. The more frequently you update the SPI, more likely it is that a receiver will not be able to utilise the cached objects.

===Some observations===

* According to specs, logo slides in DAB EPG must be PNG. Although JPG is allowed in hybrid radio SPI, JPG logos will not be added to your DAB EPG. Be sure that your logos (at least those up to 320x240) are PNG.
* Resolved on 12APR21: (Programme descriptions (shortDescription) seem to be processed but not shown. Perhaps we will have to look a little further into this.)
* Updated on 15MAR22: Instructions are now for Python 3

How to configure SPI (Service and Programme Information) for ODR-DabMux

2022-03-15T20:20:36Z

Nickpiggott:

Howto by Ulrik Brinck on odr-radioepg-bridge installation on Debian Jessie. Nick Piggott has contributed with some additions (and edited to show installation for Python 3)

This is now updated to run on Python 3. Instuctions on how to make it (mostly) run on Python 2 are below, but this is now deprecated.

'''This guide assumes your default python envrionment is Python 3.'''

===Introduction===

This tool (or rather series of tools) will pick up your SPI (Service and Programme Information) from the internet via RadioDNS and generate a DAB SPI from it. It was written by Ben Poor and Nick Piggott. In this HowTo, I will describe how it can be installed alongside Python 3.

* Confused about EPG and SPI? In this context, EPG and SPI are basically the same thing. While EPG (Electronic Programme Guide) is an old, but commonly well-known term, SPI (Service and Programme Information) is now the official name of this feature.

===Notes===

'''This tool uses RadioDNS to locate and acquire Service Information (SI.xml), Programme Information (PI.xml) and Logos.'''
Each station you want to add to the SPI must be registered in RadioDNS using the correct information (Ensemble ID, Service ID, Service Component ID), and have correctly formatted SI, PI and logo files in PNG format. Find out more at https://radiodns.org/technical/documentation/#howto

I have assumed that you are logged in to your Linux system as a standard user and have sudo installed on your system. If sudo is not installed, you can see here, how to install it on Debian Jessie:
https://www.geek17.com/en/content/debian-8-jessie-install-and-configure-sudo-25

===Installation===

====Step 0: Update your system====
Begin with "sudo apt-get update" to make sure that you can install all that you need.

====Step 1: Miscellaneous dependencies====
First there are some dependencies to install with apt-get:

sudo apt-get install python3-setuptools python3-crcmod python3-dateutil python3-isodate python3-pil git

Next there are some dependencies and subcomponents which must be downloaded from github and installed. Establish yourself in a suitable working directory (e.g. ~/src)

====Step 2: python-dabmot====

git clone https://github.com/Opendigitalradio/python-dabmot
cd python-dabmot
sudo python setup.py install
cd ..

====Step 3: python-mot-epg====

git clone https://github.com/Opendigitalradio/python-mot-epg
cd python-mot-epg
sudo python setup.py install
cd ..

====Step 4: python-msc====

git clone https://github.com/Opendigitalradio/python-dabmsc
cd python-dabmsc
sudo python setup.py install
cd ..

====Step 5: pyradiodns====

git clone https://github.com/radiodns/pyradiodns
cd pyradiodns
sudo python setup.py install
cd ..

'''NOTE'''
The installer specifies that dnspython must be at or greater than version 2.0 when used with python3. Most distributions ship with this version.
If the installer can't find dnspython>=2.0, you need to download, unpack, and manually install the package from https://pypi.org/simple/dnspython/

====Step 6: odr-radiodns-bridge====

git clone https://github.com/Opendigitalradio/odr-radiodns-bridge
cd odr-radiodns-bridge
sudo python setup.py install
cd ..

====Step 7: python-hybridspi====

git clone https://github.com/Opendigitalradio/python-hybridspi
cd python-hybridspi
sudo python setup.py install
cd ..

'''NOTE'''
The installer specifies bitarray at ''exactly'' version 1.2.0. You should make sure that you only have this version installed in your python enivronment.
If it isn't installed, you need to download, unpack, and manually install the package from https://pypi.org/simple/bitarray/

====Step 8: odr-radioepg-bridge====

git clone https://github.com/Opendigitalradio/odr-radioepg-bridge
sudo ln -s odr-radioepg-bridge-master/generate-epg /usr/local/bin/generate-epg

That's it. You should now be able to run this command and see a help text:
generate-epg -h

===Generating and broadcasting your SPI (EPG)===

====Generating your SPI====

Odr-radioepg-bridge is a command-line tool, which will:
* First read your mux.conf (from your ODR-DabMux configuration) to get information about your services.
* Then try to fetch SPI data for your services from the internet using RadioDNS.
* And lastly generate an output file containing a complete SPI.

If you type "generate-epg -h" you will get a list of available command-line arguments:

usage: generate-epg [-h] [-o OUTPUT] [-X] [-d DAYS] [-p PACKET_SIZE]
[-a PACKET_ADDRESS] [-D]
f

Encodes an SPI bitstream for services in a multiplex configuration file

positional arguments:
f multiplex configuration file

optional arguments:
-h, --help show this help message and exit
-o OUTPUT output bitstream file
-X turn debug on
-d DAYS number of days ahead to encode schedule files
-p PACKET_SIZE Packet size in bytes
-a PACKET_ADDRESS Packet address
-D output Datagroups instead of Packets

The positional argument tells the tool where to find your mux.conf.
The other arguments are optional, and some default values will be used if you don't set them:

* -o can be used to set filename and path to your output file (your SPI). Default is output.dat, placed in the folder from where you run the tool.
* -d is the number of days of programme schedule you want in you SPI. From 1 til 4 days, default is 2.
* -p is packet size. Available values are 24, 48, 72 and 96. Default is 96. Which value you should use, depends on the bitrate in which you are broadcasting your SPI (see below).
* -a is the packet address for your SPI. Default is 1, which will normally be fine. Important is, that you must set the same address in your mux.conf (see below).
* -D will tell the script to output Datagroups instead of Packets. This is useful for some commercial multiplexers or in case you want to broadcast your SPI as X-PAD instead of packet data. Note: You do not need this if you plan to broadcast your SPI the way it's described on this wiki page.

Example:
If your mux.conf is placed in /home/user/odr/config/mux.conf, and you want 4 days in your SPI (today and the next 3 days) and you want to broadcast it in 16 kbit/s, your command line could look like this:

generate-epg -d 4 -p 48 /home/user/odr/config/mux.conf

This will generate a file named output.dat containing your SPI. In this example, I have set the packet size to 48, which is suitable for 16 kbit/s. I have not set the packet address, which means that the default value of 1 will be used.

====Packet sizes and bitrates====

The packet size, which you set when you generate your SPI, should match the bitrate in which you intend to broadcast it. If the packet size is too large, your SPI will not be transmitted. If the packet size is too small, your SPI will (probably) be transmitted, but it will be slower than necessary, because more space will be used for packet headers and maybe partly empty data packets. I will recommend these values:

{| class="wikitable"
! Bitrate
! Packet size
|-
| 8
| 24
|-
| 16
| 48
|-
| 24
| 72
|-
| 32
| 96
|-
| 48
| 72
|-
| 64
| 96
|}

====Broadcasting your SPI====

To broadcast your SPI using ODR-DabMux, create a packet data service in your mux.conf like in this example:

In the services section:

srv-spi {
label "EPG & Logos"
shortlabel "EPGLogos"
; the service-ID consists of 8 hex digits for packet data services. Usually the first two digits will
; be the same as your ECC, and the third digit will be the same as the first digit in your Ensemble Id.
id 0xe1912345
}

In the subchannels section:

sub-spi {
; type packet or enhancedpacket can be used for SPI.
type enhancedpacket
; if you change the bitrate, remember to also change the packet size accordingly (see above) and generate your SPI again.
bitrate 16
protection-profile EEP_A
protection 3
; inputuri is the path and filename for your output file from generate-epg
inputuri "/home/user/odr-radioepg-bridge-master/output.dat"
inputproto file
}

And in the components section (if you are using version 3.1.1 or earlier of odr-dabmux)

comp-spi {
type 60
service srv-spi
subchannel sub-spi
figtype 0x7
; The address must be the same as your packet address set when you generate the SPI (default value is 1).
address 0x1
datagroup true
}

If you are using version 3.1.2 or later of odr-dabmux, the construction of the component section is slightly different

comp-spi {
type 60
service srv-spi
subchannel sub-spi
user-applications {
userapp "spi"
}
address 0x1
datagroup true
}

That's it. Now (re)start your ODR-DabMux, and your SPI should be transmitted.

===Updating your SPI automatically every day===

====Feeding the SPI from a fifo will ensure that you can update it without restarting the MUX====

While the setup shown above will allow you to broadcast your SPI, it ''might'' not allow you to update your SPI without having to restart your MUX.
* If the SPI output file is ''rewritten'', the new content will be picked up by ODR-DabMux automatically, and your SPI will immediately be updated. This will be the case if you use generate-epg to generate a new file directly upon the the old one.
* However, if the SPI output file is ''replaced'', the new file will '''not''' be picked up by ODR-DabMux, until you restart it. This will be the case, if you generate a new file elsewhere (e.g. in a different folder or on another machine) and then ''copy'' it into where the old one is.

To get around this, and be sure that you can always update your SPI, any way you want, you can feed your SPI to ODR-DabMux from a named fifo instead of a file.

Navigate to the folder where you have your SPI and create a fifo like this:

mkfifo spififo

In the subchannel section of your mux.conf, you should replace your SPI file (output.dat) with your fifo, and also add a new line, "nonblock true", so that your SPI subchannel looks like this:

sub-spi {
; type packet or enhancedpacket can be used for SPI.
type enhancedpacket
; if you change the bitrate, remember to also change the packet size accordingly (see above) and generate your SPI again.
bitrate 16
protection-profile EEP_A
protection 3
; inputuri is the path and filename for your output from generate-epg
inputuri "/home/user/odr-radioepg-bridge-master/spififo"
inputproto file
nonblock true
}

Your SPI must be continously sent to the fifo. You can make a shell script for that. Create a file, sendspi.sh, with this content:

#!/bin/bash

while :
do

cat /home/user/odr-radioepg-bridge-master/output.dat >> /home/user/odr-radioepg-bridge-master/spififo

done

And make it executable (chmod +x sendspi.sh).

This script must be running all the time. If you're already using Supervisor to keep your MUX running (as described here: https://github.com/Opendigitalradio/dab-scripts), it's easy to also use supervisor for this script. Create a new file, sendspi.conf, in your /home/user/odr/config/supervisor folder with this content:

[program:sendspi]
command=bash -c "/home/user/odr-radioepg-bridge-master/sendspi.sh"
autostart=true
autorestart=true
startretries=99999
priority=10
stderr_logfile=/dev/stdout
stdout_logfile=/dev/stdout

Then run these commands:

sudo ln -s /home/user/odr/config/supervisor/sendspi.conf /etc/supervisor/conf.d/sendspi.conf
sudo supervisorctl reread
sudo supervisorctl update

Now your SPI is sent to ODR-DabMux from the fifo, and you will now be able to update your SPI, any way you want, without having to restart ODR-DabMux.

====Updating your SPI automatically every day====

You can update your SPI every 24 hours by adding a new daily task to cron.

Create a new file

/etc/cron.daily/spi

with the single line (with the same parameters as when you generate your SPI yourself)

/usr/local/bin/generate-epg -d 4 -p 48 /home/user/odr/config/mux.conf -o /home/user/odr-radioepg-bridge-master/output.dat

By default, the cron job will run every day at around 06:00. If you want your SPI to update more frequently (every 4 hours), you could add it to the user cron job with

crontab -e

and add the line

0 */4 * * * /usr/local/bin/generate-epg -d 4 -p 48 /home/user/odr/config/mux.conf -o /home/user/odr-radioepg-bridge-master/output.dat

'''NOTE:'''
The SPI creates new MOT TransportIDs for every object each time it is run. A receiver will not recognise that objects have been previously received and cached. If there is an interruption in reception, the SPI will be incomplete. The more frequently you update the SPI, more likely it is that a receiver will not be able to utilise the cached objects.

===Some observations===

* According to specs, logo slides in DAB EPG must be PNG. Although JPG is allowed in hybrid radio SPI, JPG logos will not be added to your DAB EPG. Be sure that your logos (at least those up to 320x240) are PNG.
* Resolved on 12APR21: (Programme descriptions (shortDescription) seem to be processed but not shown. Perhaps we will have to look a little further into this.)
* Updated on 15MAR22: Instructions are now for Python 3

How to configure SPI (Service and Programme Information) for ODR-DabMux

2022-03-15T20:17:26Z

Nickpiggott:

Howto by Ulrik Brinck on odr-radioepg-bridge installation on Debian Jessie. Nick Piggott has contributed with some additions (and edited to show installation for Python 3)

This is now updated to run on Python 3. Instuctions on how to make it (mostly) run on Python 2 are below, but this is now deprecated.

'''This guide assumes your default python envrionment is Python 3.'''

===Introduction===

This tool (or rather series of tools) will pick up your SPI (Service and Programme Information) from the internet via RadioDNS and generate a DAB SPI from it. It was written by Ben Poor and Nick Piggott. In this HowTo, I will describe how it can be installed alongside Python 3.

* Confused about EPG and SPI? In this context, EPG and SPI are basically the same thing. While EPG (Electronic Programme Guide) is an old, but commonly well-known term, SPI (Service and Programme Information) is now the official name of this feature.

===Notes===

'''This tool uses RadioDNS to locate and acquire Service Information (SI.xml), Programme Information (PI.xml) and Logos.'''
Each station you want to add to the SPI must be registered in RadioDNS using the correct information (Ensemble ID, Service ID, Service Component ID), and have correctly formatted SI, PI and logo files in PNG format. Find out more at https://radiodns.org/technical/documentation/#howto

I have assumed that you are logged in to your Linux system as a standard user and have sudo installed on your system. If sudo is not installed, you can see here, how to install it on Debian Jessie:
https://www.geek17.com/en/content/debian-8-jessie-install-and-configure-sudo-25

===Installation===

====Step 0: Update your system====
Begin with "sudo apt-get update" to make sure that you can install all that you need.

====Step 1: Miscellaneous dependencies====
First there are some dependencies to install with apt-get:

sudo apt-get install python3-crcmod python3-dateutil python3-isodate python3-pil git

Next there are some dependencies and subcomponents which must be downloaded from github and installed. Establish yourself in a suitable working directory (e.g. ~/src)

====Step 2: python-dabmot====

git clone https://github.com/Opendigitalradio/python-dabmot
cd python-dabmot
sudo python setup.py install
cd ..

====Step 3: python-mot-epg====

git clone https://github.com/Opendigitalradio/python-mot-epg
cd python-mot-epg
sudo python setup.py install
cd ..

====Step 4: python-msc====

git clone https://github.com/Opendigitalradio/python-dabmsc
cd python-dabmsc
sudo python setup.py install
cd ..

====Step 5: pyradiodns====

git clone https://github.com/radiodns/pyradiodns
cd pyradiodns
sudo python setup.py install
cd ..

'''NOTE'''
The installer specifies that dnspython must be at or greater than version 2.0 when used with python3. Most distributions ship with this version.
If the installer can't find dnspython>=2.0, you need to download, unpack, and manually install the package from https://pypi.org/simple/dnspython/

====Step 6: odr-radiodns-bridge====

git clone https://github.com/Opendigitalradio/odr-radiodns-bridge
cd odr-radiodns-bridge
sudo python setup.py install
cd ..

====Step 7: python-hybridspi====

git clone https://github.com/Opendigitalradio/python-hybridspi
cd python-hybridspi
sudo python setup.py install
cd ..

'''NOTE'''
The installer specifies bitarray at ''exactly'' version 1.2.0. You should make sure that you only have this version installed in your python enivronment.
If it isn't installed, you need to download, unpack, and manually install the package from https://pypi.org/simple/bitarray/

====Step 8: odr-radioepg-bridge====

git clone https://github.com/Opendigitalradio/odr-radioepg-bridge
sudo ln -s odr-radioepg-bridge-master/generate-epg /usr/local/bin/generate-epg

That's it. You should now be able to run this command and see a help text:
generate-epg -h

===Generating and broadcasting your SPI (EPG)===

====Generating your SPI====

Odr-radioepg-bridge is a command-line tool, which will:
* First read your mux.conf (from your ODR-DabMux configuration) to get information about your services.
* Then try to fetch SPI data for your services from the internet using RadioDNS.
* And lastly generate an output file containing a complete SPI.

If you type "generate-epg -h" you will get a list of available command-line arguments:

usage: generate-epg [-h] [-o OUTPUT] [-X] [-d DAYS] [-p PACKET_SIZE]
[-a PACKET_ADDRESS] [-D]
f

Encodes an SPI bitstream for services in a multiplex configuration file

positional arguments:
f multiplex configuration file

optional arguments:
-h, --help show this help message and exit
-o OUTPUT output bitstream file
-X turn debug on
-d DAYS number of days ahead to encode schedule files
-p PACKET_SIZE Packet size in bytes
-a PACKET_ADDRESS Packet address
-D output Datagroups instead of Packets

The positional argument tells the tool where to find your mux.conf.
The other arguments are optional, and some default values will be used if you don't set them:

* -o can be used to set filename and path to your output file (your SPI). Default is output.dat, placed in the folder from where you run the tool.
* -d is the number of days of programme schedule you want in you SPI. From 1 til 4 days, default is 2.
* -p is packet size. Available values are 24, 48, 72 and 96. Default is 96. Which value you should use, depends on the bitrate in which you are broadcasting your SPI (see below).
* -a is the packet address for your SPI. Default is 1, which will normally be fine. Important is, that you must set the same address in your mux.conf (see below).
* -D will tell the script to output Datagroups instead of Packets. This is useful for some commercial multiplexers or in case you want to broadcast your SPI as X-PAD instead of packet data. Note: You do not need this if you plan to broadcast your SPI the way it's described on this wiki page.

Example:
If your mux.conf is placed in /home/user/odr/config/mux.conf, and you want 4 days in your SPI (today and the next 3 days) and you want to broadcast it in 16 kbit/s, your command line could look like this:

generate-epg -d 4 -p 48 /home/user/odr/config/mux.conf

This will generate a file named output.dat containing your SPI. In this example, I have set the packet size to 48, which is suitable for 16 kbit/s. I have not set the packet address, which means that the default value of 1 will be used.

====Packet sizes and bitrates====

The packet size, which you set when you generate your SPI, should match the bitrate in which you intend to broadcast it. If the packet size is too large, your SPI will not be transmitted. If the packet size is too small, your SPI will (probably) be transmitted, but it will be slower than necessary, because more space will be used for packet headers and maybe partly empty data packets. I will recommend these values:

{| class="wikitable"
! Bitrate
! Packet size
|-
| 8
| 24
|-
| 16
| 48
|-
| 24
| 72
|-
| 32
| 96
|-
| 48
| 72
|-
| 64
| 96
|}

====Broadcasting your SPI====

To broadcast your SPI using ODR-DabMux, create a packet data service in your mux.conf like in this example:

In the services section:

srv-spi {
label "EPG & Logos"
shortlabel "EPGLogos"
; the service-ID consists of 8 hex digits for packet data services. Usually the first two digits will
; be the same as your ECC, and the third digit will be the same as the first digit in your Ensemble Id.
id 0xe1912345
}

In the subchannels section:

sub-spi {
; type packet or enhancedpacket can be used for SPI.
type enhancedpacket
; if you change the bitrate, remember to also change the packet size accordingly (see above) and generate your SPI again.
bitrate 16
protection-profile EEP_A
protection 3
; inputuri is the path and filename for your output file from generate-epg
inputuri "/home/user/odr-radioepg-bridge-master/output.dat"
inputproto file
}

And in the components section (if you are using version 3.1.1 or earlier of odr-dabmux)

comp-spi {
type 60
service srv-spi
subchannel sub-spi
figtype 0x7
; The address must be the same as your packet address set when you generate the SPI (default value is 1).
address 0x1
datagroup true
}

If you are using version 3.1.2 or later of odr-dabmux, the construction of the component section is slightly different

comp-spi {
type 60
service srv-spi
subchannel sub-spi
user-applications {
userapp "spi"
}
address 0x1
datagroup true
}

That's it. Now (re)start your ODR-DabMux, and your SPI should be transmitted.

===Updating your SPI automatically every day===

====Feeding the SPI from a fifo will ensure that you can update it without restarting the MUX====

While the setup shown above will allow you to broadcast your SPI, it ''might'' not allow you to update your SPI without having to restart your MUX.
* If the SPI output file is ''rewritten'', the new content will be picked up by ODR-DabMux automatically, and your SPI will immediately be updated. This will be the case if you use generate-epg to generate a new file directly upon the the old one.
* However, if the SPI output file is ''replaced'', the new file will '''not''' be picked up by ODR-DabMux, until you restart it. This will be the case, if you generate a new file elsewhere (e.g. in a different folder or on another machine) and then ''copy'' it into where the old one is.

To get around this, and be sure that you can always update your SPI, any way you want, you can feed your SPI to ODR-DabMux from a named fifo instead of a file.

Navigate to the folder where you have your SPI and create a fifo like this:

mkfifo spififo

In the subchannel section of your mux.conf, you should replace your SPI file (output.dat) with your fifo, and also add a new line, "nonblock true", so that your SPI subchannel looks like this:

sub-spi {
; type packet or enhancedpacket can be used for SPI.
type enhancedpacket
; if you change the bitrate, remember to also change the packet size accordingly (see above) and generate your SPI again.
bitrate 16
protection-profile EEP_A
protection 3
; inputuri is the path and filename for your output from generate-epg
inputuri "/home/user/odr-radioepg-bridge-master/spififo"
inputproto file
nonblock true
}

Your SPI must be continously sent to the fifo. You can make a shell script for that. Create a file, sendspi.sh, with this content:

#!/bin/bash

while :
do

cat /home/user/odr-radioepg-bridge-master/output.dat >> /home/user/odr-radioepg-bridge-master/spififo

done

And make it executable (chmod +x sendspi.sh).

This script must be running all the time. If you're already using Supervisor to keep your MUX running (as described here: https://github.com/Opendigitalradio/dab-scripts), it's easy to also use supervisor for this script. Create a new file, sendspi.conf, in your /home/user/odr/config/supervisor folder with this content:

[program:sendspi]
command=bash -c "/home/user/odr-radioepg-bridge-master/sendspi.sh"
autostart=true
autorestart=true
startretries=99999
priority=10
stderr_logfile=/dev/stdout
stdout_logfile=/dev/stdout

Then run these commands:

sudo ln -s /home/user/odr/config/supervisor/sendspi.conf /etc/supervisor/conf.d/sendspi.conf
sudo supervisorctl reread
sudo supervisorctl update

Now your SPI is sent to ODR-DabMux from the fifo, and you will now be able to update your SPI, any way you want, without having to restart ODR-DabMux.

====Updating your SPI automatically every day====

You can update your SPI every 24 hours by adding a new daily task to cron.

Create a new file

/etc/cron.daily/spi

with the single line (with the same parameters as when you generate your SPI yourself)

/usr/local/bin/generate-epg -d 4 -p 48 /home/user/odr/config/mux.conf -o /home/user/odr-radioepg-bridge-master/output.dat

By default, the cron job will run every day at around 06:00. If you want your SPI to update more frequently (every 4 hours), you could add it to the user cron job with

crontab -e

and add the line

0 */4 * * * /usr/local/bin/generate-epg -d 4 -p 48 /home/user/odr/config/mux.conf -o /home/user/odr-radioepg-bridge-master/output.dat

'''NOTE:'''
The SPI creates new MOT TransportIDs for every object each time it is run. A receiver will not recognise that objects have been previously received and cached. If there is an interruption in reception, the SPI will be incomplete. The more frequently you update the SPI, more likely it is that a receiver will not be able to utilise the cached objects.

===Some observations===

* According to specs, logo slides in DAB EPG must be PNG. Although JPG is allowed in hybrid radio SPI, JPG logos will not be added to your DAB EPG. Be sure that your logos (at least those up to 320x240) are PNG.
* Resolved on 12APR21: (Programme descriptions (shortDescription) seem to be processed but not shown. Perhaps we will have to look a little further into this.)
* Updated on 15MAR22: Instructions are now for Python 3

How to configure SPI (Service and Programme Information) for ODR-DabMux

2022-03-15T20:16:41Z

Nickpiggott:

Howto by Ulrik Brinck on odr-radioepg-bridge installation on Debian Jessie. Nick Piggott has contributed with some additions (and edited to show installation for Python 3)

This is now updated to run on Python 3. Instuctions on how to make it (mostly) run on Python 2 are below, but this is now deprecated.
===Introduction===

This tool (or rather series of tools) will pick up your SPI (Service and Programme Information) from the internet via RadioDNS and generate a DAB SPI from it. It was written by Ben Poor and Nick Piggott. In this HowTo, I will describe how it can be installed alongside Python 3.

* Confused about EPG and SPI? In this context, EPG and SPI are basically the same thing. While EPG (Electronic Programme Guide) is an old, but commonly well-known term, SPI (Service and Programme Information) is now the official name of this feature.

===Notes===

'''This tool uses RadioDNS to locate and acquire Service Information (SI.xml), Programme Information (PI.xml) and Logos.'''
Each station you want to add to the SPI must be registered in RadioDNS using the correct information (Ensemble ID, Service ID, Service Component ID), and have correctly formatted SI, PI and logo files in PNG format. Find out more at https://radiodns.org/technical/documentation/#howto

I have assumed that you are logged in to your Linux system as a standard user and have sudo installed on your system. If sudo is not installed, you can see here, how to install it on Debian Jessie:
https://www.geek17.com/en/content/debian-8-jessie-install-and-configure-sudo-25

===Installation===

====Step 0: Update your system====
Begin with "sudo apt-get update" to make sure that you can install all that you need.

====Step 1: Miscellaneous dependencies====
First there are some dependencies to install with apt-get:

sudo apt-get install python3-crcmod python3-dateutil python3-isodate python3-pil git

Next there are some dependencies and subcomponents which must be downloaded from github and installed. Establish yourself in a suitable working directory (e.g. ~/src)

====Step 2: python-dabmot====

git clone https://github.com/Opendigitalradio/python-dabmot
cd python-dabmot
sudo python setup.py install
cd ..

====Step 3: python-mot-epg====

git clone https://github.com/Opendigitalradio/python-mot-epg
cd python-mot-epg
sudo python setup.py install
cd ..

====Step 4: python-msc====

git clone https://github.com/Opendigitalradio/python-dabmsc
cd python-dabmsc
sudo python setup.py install
cd ..

====Step 5: pyradiodns====

git clone https://github.com/radiodns/pyradiodns
cd pyradiodns
sudo python setup.py install
cd ..

'''NOTE'''
The installer specifies that dnspython must be at or greater than version 2.0 when used with python3. Most distributions ship with this version.
If the installer can't find dnspython>=2.0, you need to download, unpack, and manually install the package from https://pypi.org/simple/dnspython/

====Step 6: odr-radiodns-bridge====

git clone https://github.com/Opendigitalradio/odr-radiodns-bridge
cd odr-radiodns-bridge
sudo python setup.py install
cd ..

====Step 7: python-hybridspi====

git clone https://github.com/Opendigitalradio/python-hybridspi
cd python-hybridspi
sudo python setup.py install
cd ..

'''NOTE'''
The installer specifies bitarray at ''exactly'' version 1.2.0. You should make sure that you only have this version installed in your python enivronment.
If it isn't installed, you need to download, unpack, and manually install the package from https://pypi.org/simple/bitarray/

====Step 8: odr-radioepg-bridge====

git clone https://github.com/Opendigitalradio/odr-radioepg-bridge
sudo ln -s odr-radioepg-bridge-master/generate-epg /usr/local/bin/generate-epg

That's it. You should now be able to run this command and see a help text:
generate-epg -h

===Generating and broadcasting your SPI (EPG)===

====Generating your SPI====

Odr-radioepg-bridge is a command-line tool, which will:
* First read your mux.conf (from your ODR-DabMux configuration) to get information about your services.
* Then try to fetch SPI data for your services from the internet using RadioDNS.
* And lastly generate an output file containing a complete SPI.

If you type "generate-epg -h" you will get a list of available command-line arguments:

usage: generate-epg [-h] [-o OUTPUT] [-X] [-d DAYS] [-p PACKET_SIZE]
[-a PACKET_ADDRESS] [-D]
f

Encodes an SPI bitstream for services in a multiplex configuration file

positional arguments:
f multiplex configuration file

optional arguments:
-h, --help show this help message and exit
-o OUTPUT output bitstream file
-X turn debug on
-d DAYS number of days ahead to encode schedule files
-p PACKET_SIZE Packet size in bytes
-a PACKET_ADDRESS Packet address
-D output Datagroups instead of Packets

The positional argument tells the tool where to find your mux.conf.
The other arguments are optional, and some default values will be used if you don't set them:

* -o can be used to set filename and path to your output file (your SPI). Default is output.dat, placed in the folder from where you run the tool.
* -d is the number of days of programme schedule you want in you SPI. From 1 til 4 days, default is 2.
* -p is packet size. Available values are 24, 48, 72 and 96. Default is 96. Which value you should use, depends on the bitrate in which you are broadcasting your SPI (see below).
* -a is the packet address for your SPI. Default is 1, which will normally be fine. Important is, that you must set the same address in your mux.conf (see below).
* -D will tell the script to output Datagroups instead of Packets. This is useful for some commercial multiplexers or in case you want to broadcast your SPI as X-PAD instead of packet data. Note: You do not need this if you plan to broadcast your SPI the way it's described on this wiki page.

Example:
If your mux.conf is placed in /home/user/odr/config/mux.conf, and you want 4 days in your SPI (today and the next 3 days) and you want to broadcast it in 16 kbit/s, your command line could look like this:

generate-epg -d 4 -p 48 /home/user/odr/config/mux.conf

This will generate a file named output.dat containing your SPI. In this example, I have set the packet size to 48, which is suitable for 16 kbit/s. I have not set the packet address, which means that the default value of 1 will be used.

====Packet sizes and bitrates====

The packet size, which you set when you generate your SPI, should match the bitrate in which you intend to broadcast it. If the packet size is too large, your SPI will not be transmitted. If the packet size is too small, your SPI will (probably) be transmitted, but it will be slower than necessary, because more space will be used for packet headers and maybe partly empty data packets. I will recommend these values:

{| class="wikitable"
! Bitrate
! Packet size
|-
| 8
| 24
|-
| 16
| 48
|-
| 24
| 72
|-
| 32
| 96
|-
| 48
| 72
|-
| 64
| 96
|}

====Broadcasting your SPI====

To broadcast your SPI using ODR-DabMux, create a packet data service in your mux.conf like in this example:

In the services section:

srv-spi {
label "EPG & Logos"
shortlabel "EPGLogos"
; the service-ID consists of 8 hex digits for packet data services. Usually the first two digits will
; be the same as your ECC, and the third digit will be the same as the first digit in your Ensemble Id.
id 0xe1912345
}

In the subchannels section:

sub-spi {
; type packet or enhancedpacket can be used for SPI.
type enhancedpacket
; if you change the bitrate, remember to also change the packet size accordingly (see above) and generate your SPI again.
bitrate 16
protection-profile EEP_A
protection 3
; inputuri is the path and filename for your output file from generate-epg
inputuri "/home/user/odr-radioepg-bridge-master/output.dat"
inputproto file
}

And in the components section (if you are using version 3.1.1 or earlier of odr-dabmux)

comp-spi {
type 60
service srv-spi
subchannel sub-spi
figtype 0x7
; The address must be the same as your packet address set when you generate the SPI (default value is 1).
address 0x1
datagroup true
}

If you are using version 3.1.2 or later of odr-dabmux, the construction of the component section is slightly different

comp-spi {
type 60
service srv-spi
subchannel sub-spi
user-applications {
userapp "spi"
}
address 0x1
datagroup true
}

That's it. Now (re)start your ODR-DabMux, and your SPI should be transmitted.

===Updating your SPI automatically every day===

====Feeding the SPI from a fifo will ensure that you can update it without restarting the MUX====

While the setup shown above will allow you to broadcast your SPI, it ''might'' not allow you to update your SPI without having to restart your MUX.
* If the SPI output file is ''rewritten'', the new content will be picked up by ODR-DabMux automatically, and your SPI will immediately be updated. This will be the case if you use generate-epg to generate a new file directly upon the the old one.
* However, if the SPI output file is ''replaced'', the new file will '''not''' be picked up by ODR-DabMux, until you restart it. This will be the case, if you generate a new file elsewhere (e.g. in a different folder or on another machine) and then ''copy'' it into where the old one is.

To get around this, and be sure that you can always update your SPI, any way you want, you can feed your SPI to ODR-DabMux from a named fifo instead of a file.

Navigate to the folder where you have your SPI and create a fifo like this:

mkfifo spififo

In the subchannel section of your mux.conf, you should replace your SPI file (output.dat) with your fifo, and also add a new line, "nonblock true", so that your SPI subchannel looks like this:

sub-spi {
; type packet or enhancedpacket can be used for SPI.
type enhancedpacket
; if you change the bitrate, remember to also change the packet size accordingly (see above) and generate your SPI again.
bitrate 16
protection-profile EEP_A
protection 3
; inputuri is the path and filename for your output from generate-epg
inputuri "/home/user/odr-radioepg-bridge-master/spififo"
inputproto file
nonblock true
}

Your SPI must be continously sent to the fifo. You can make a shell script for that. Create a file, sendspi.sh, with this content:

#!/bin/bash

while :
do

cat /home/user/odr-radioepg-bridge-master/output.dat >> /home/user/odr-radioepg-bridge-master/spififo

done

And make it executable (chmod +x sendspi.sh).

This script must be running all the time. If you're already using Supervisor to keep your MUX running (as described here: https://github.com/Opendigitalradio/dab-scripts), it's easy to also use supervisor for this script. Create a new file, sendspi.conf, in your /home/user/odr/config/supervisor folder with this content:

[program:sendspi]
command=bash -c "/home/user/odr-radioepg-bridge-master/sendspi.sh"
autostart=true
autorestart=true
startretries=99999
priority=10
stderr_logfile=/dev/stdout
stdout_logfile=/dev/stdout

Then run these commands:

sudo ln -s /home/user/odr/config/supervisor/sendspi.conf /etc/supervisor/conf.d/sendspi.conf
sudo supervisorctl reread
sudo supervisorctl update

Now your SPI is sent to ODR-DabMux from the fifo, and you will now be able to update your SPI, any way you want, without having to restart ODR-DabMux.

====Updating your SPI automatically every day====

You can update your SPI every 24 hours by adding a new daily task to cron.

Create a new file

/etc/cron.daily/spi

with the single line (with the same parameters as when you generate your SPI yourself)

/usr/local/bin/generate-epg -d 4 -p 48 /home/user/odr/config/mux.conf -o /home/user/odr-radioepg-bridge-master/output.dat

By default, the cron job will run every day at around 06:00. If you want your SPI to update more frequently (every 4 hours), you could add it to the user cron job with

crontab -e

and add the line

0 */4 * * * /usr/local/bin/generate-epg -d 4 -p 48 /home/user/odr/config/mux.conf -o /home/user/odr-radioepg-bridge-master/output.dat

'''NOTE:'''
The SPI creates new MOT TransportIDs for every object each time it is run. A receiver will not recognise that objects have been previously received and cached. If there is an interruption in reception, the SPI will be incomplete. The more frequently you update the SPI, more likely it is that a receiver will not be able to utilise the cached objects.

===Some observations===

* According to specs, logo slides in DAB EPG must be PNG. Although JPG is allowed in hybrid radio SPI, JPG logos will not be added to your DAB EPG. Be sure that your logos (at least those up to 320x240) are PNG.
* Resolved on 12APR21: (Programme descriptions (shortDescription) seem to be processed but not shown. Perhaps we will have to look a little further into this.)
* Updated on 15MAR22: Instructions are now for Python 3

How to configure SPI (Service and Programme Information) for ODR-DabMux

2022-03-15T19:07:38Z

Nickpiggott:

Howto by Ulrik Brinck on odr-radioepg-bridge installation on Debian Jessie. Nick Piggott has contributed with some additions (and edited to show installation for Python 3)

This is now updated to run on Python 3. Instuctions on how to make it (mostly) run on Python 2 are below, but this is now deprecated.
===Introduction===

This tool (or rather series of tools) will pick up your SPI (Service and Programme Information) from the internet via RadioDNS and generate a DAB SPI from it. It was written by Ben Poor and Nick Piggott. In this HowTo, I will describe how it can be installed alongside Python 3.

* Confused about EPG and SPI? In this context, EPG and SPI are basically the same thing. While EPG (Electronic Programme Guide) is an old, but commonly well-known term, SPI (Service and Programme Information) is now the official name of this feature.

===Notes===

'''This tool uses RadioDNS to locate and acquire Service Information (SI.xml), Programme Information (PI.xml) and Logos.'''
Each station you want to add to the SPI must be registered in RadioDNS using the correct information (Ensemble ID, Service ID, Service Component ID), and have correctly formatted SI, PI and logo files in PNG format. Find out more at https://radiodns.org/technical/documentation/#howto

I have assumed that you are logged in to your Linux system as a standard user and have sudo installed on your system. If sudo is not installed, you can see here, how to install it on Debian Jessie:
https://www.geek17.com/en/content/debian-8-jessie-install-and-configure-sudo-25

===Installation===

====Step 0: Update your system====
Begin with "sudo apt-get update" to make sure that you can install all that you need.

====Step 1: Miscellaneous dependencies====
First there are some dependencies to install with apt-get:

sudo apt-get install python3-crcmod python3-bitarray python3-dateutil python3-isodate python3-pil git

Next there are some dependencies and subcomponents which must be downloaded from github and installed. Establish yourself in a suitable working directory (e.g. ~/src)

====Step 2: python-dabmot====

git clone https://github.com/Opendigitalradio/python-dabmot
cd python-dabmot
sudo python setup.py install
cd ..

====Step 3: python-mot-epg====

git clone https://github.com/Opendigitalradio/python-mot-epg
cd python-mot-epg
sudo python setup.py install
cd ..

====Step 4: python-msc====

git clone https://github.com/Opendigitalradio/python-dabmsc
cd python-dabmsc
sudo python setup.py install
cd ..

====Step 5: pyradiodns====

git clone https://github.com/radiodns/pyradiodns
cd pyradiodns
sudo python setup.py install
cd ..

====Step 6: odr-radiodns-bridge====

git clone https://github.com/Opendigitalradio/odr-radiodns-bridge
cd odr-radiodns-bridge
sudo python setup.py install
cd ..

====Step 7: python-hybridspi====

git clone https://github.com/Opendigitalradio/python-hybridspi
cd python-hybridspi
sudo python setup.py install
cd ..

====Step 8: odr-radioepg-bridge====

git clone https://github.com/Opendigitalradio/odr-radioepg-bridge
sudo ln -s odr-radioepg-bridge-master/generate-epg /usr/local/bin/generate-epg

That's it. You should now be able to run this command and see a help text:
generate-epg -h

===Generating and broadcasting your SPI (EPG)===

====Generating your SPI====

Odr-radioepg-bridge is a command-line tool, which will:
* First read your mux.conf (from your ODR-DabMux configuration) to get information about your services.
* Then try to fetch SPI data for your services from the internet using RadioDNS.
* And lastly generate an output file containing a complete SPI.

If you type "generate-epg -h" you will get a list of available command-line arguments:

usage: generate-epg [-h] [-o OUTPUT] [-X] [-d DAYS] [-p PACKET_SIZE]
[-a PACKET_ADDRESS] [-D]
f

Encodes an SPI bitstream for services in a multiplex configuration file

positional arguments:
f multiplex configuration file

optional arguments:
-h, --help show this help message and exit
-o OUTPUT output bitstream file
-X turn debug on
-d DAYS number of days ahead to encode schedule files
-p PACKET_SIZE Packet size in bytes
-a PACKET_ADDRESS Packet address
-D output Datagroups instead of Packets

The positional argument tells the tool where to find your mux.conf.
The other arguments are optional, and some default values will be used if you don't set them:

* -o can be used to set filename and path to your output file (your SPI). Default is output.dat, placed in the folder from where you run the tool.
* -d is the number of days of programme schedule you want in you SPI. From 1 til 4 days, default is 2.
* -p is packet size. Available values are 24, 48, 72 and 96. Default is 96. Which value you should use, depends on the bitrate in which you are broadcasting your SPI (see below).
* -a is the packet address for your SPI. Default is 1, which will normally be fine. Important is, that you must set the same address in your mux.conf (see below).
* -D will tell the script to output Datagroups instead of Packets. This is useful for some commercial multiplexers or in case you want to broadcast your SPI as X-PAD instead of packet data. Note: You do not need this if you plan to broadcast your SPI the way it's described on this wiki page.

Example:
If your mux.conf is placed in /home/user/odr/config/mux.conf, and you want 4 days in your SPI (today and the next 3 days) and you want to broadcast it in 16 kbit/s, your command line could look like this:

generate-epg -d 4 -p 48 /home/user/odr/config/mux.conf

This will generate a file named output.dat containing your SPI. In this example, I have set the packet size to 48, which is suitable for 16 kbit/s. I have not set the packet address, which means that the default value of 1 will be used.

====Packet sizes and bitrates====

The packet size, which you set when you generate your SPI, should match the bitrate in which you intend to broadcast it. If the packet size is too large, your SPI will not be transmitted. If the packet size is too small, your SPI will (probably) be transmitted, but it will be slower than necessary, because more space will be used for packet headers and maybe partly empty data packets. I will recommend these values:

{| class="wikitable"
! Bitrate
! Packet size
|-
| 8
| 24
|-
| 16
| 48
|-
| 24
| 72
|-
| 32
| 96
|-
| 48
| 72
|-
| 64
| 96
|}

====Broadcasting your SPI====

To broadcast your SPI using ODR-DabMux, create a packet data service in your mux.conf like in this example:

In the services section:

srv-spi {
label "EPG & Logos"
shortlabel "EPGLogos"
; the service-ID consists of 8 hex digits for packet data services. Usually the first two digits will
; be the same as your ECC, and the third digit will be the same as the first digit in your Ensemble Id.
id 0xe1912345
}

In the subchannels section:

sub-spi {
; type packet or enhancedpacket can be used for SPI.
type enhancedpacket
; if you change the bitrate, remember to also change the packet size accordingly (see above) and generate your SPI again.
bitrate 16
protection-profile EEP_A
protection 3
; inputuri is the path and filename for your output file from generate-epg
inputuri "/home/user/odr-radioepg-bridge-master/output.dat"
inputproto file
}

And in the components section (if you are using version 3.1.1 or earlier of odr-dabmux)

comp-spi {
type 60
service srv-spi
subchannel sub-spi
figtype 0x7
; The address must be the same as your packet address set when you generate the SPI (default value is 1).
address 0x1
datagroup true
}

If you are using version 3.1.2 or later of odr-dabmux, the construction of the component section is slightly different

comp-spi {
type 60
service srv-spi
subchannel sub-spi
user-applications {
userapp "spi"
}
address 0x1
datagroup true
}

That's it. Now (re)start your ODR-DabMux, and your SPI should be transmitted.

===Updating your SPI automatically every day===

====Feeding the SPI from a fifo will ensure that you can update it without restarting the MUX====

While the setup shown above will allow you to broadcast your SPI, it ''might'' not allow you to update your SPI without having to restart your MUX.
* If the SPI output file is ''rewritten'', the new content will be picked up by ODR-DabMux automatically, and your SPI will immediately be updated. This will be the case if you use generate-epg to generate a new file directly upon the the old one.
* However, if the SPI output file is ''replaced'', the new file will '''not''' be picked up by ODR-DabMux, until you restart it. This will be the case, if you generate a new file elsewhere (e.g. in a different folder or on another machine) and then ''copy'' it into where the old one is.

To get around this, and be sure that you can always update your SPI, any way you want, you can feed your SPI to ODR-DabMux from a named fifo instead of a file.

Navigate to the folder where you have your SPI and create a fifo like this:

mkfifo spififo

In the subchannel section of your mux.conf, you should replace your SPI file (output.dat) with your fifo, and also add a new line, "nonblock true", so that your SPI subchannel looks like this:

sub-spi {
; type packet or enhancedpacket can be used for SPI.
type enhancedpacket
; if you change the bitrate, remember to also change the packet size accordingly (see above) and generate your SPI again.
bitrate 16
protection-profile EEP_A
protection 3
; inputuri is the path and filename for your output from generate-epg
inputuri "/home/user/odr-radioepg-bridge-master/spififo"
inputproto file
nonblock true
}

Your SPI must be continously sent to the fifo. You can make a shell script for that. Create a file, sendspi.sh, with this content:

#!/bin/bash

while :
do

cat /home/user/odr-radioepg-bridge-master/output.dat >> /home/user/odr-radioepg-bridge-master/spififo

done

And make it executable (chmod +x sendspi.sh).

This script must be running all the time. If you're already using Supervisor to keep your MUX running (as described here: https://github.com/Opendigitalradio/dab-scripts), it's easy to also use supervisor for this script. Create a new file, sendspi.conf, in your /home/user/odr/config/supervisor folder with this content:

[program:sendspi]
command=bash -c "/home/user/odr-radioepg-bridge-master/sendspi.sh"
autostart=true
autorestart=true
startretries=99999
priority=10
stderr_logfile=/dev/stdout
stdout_logfile=/dev/stdout

Then run these commands:

sudo ln -s /home/user/odr/config/supervisor/sendspi.conf /etc/supervisor/conf.d/sendspi.conf
sudo supervisorctl reread
sudo supervisorctl update

Now your SPI is sent to ODR-DabMux from the fifo, and you will now be able to update your SPI, any way you want, without having to restart ODR-DabMux.

====Updating your SPI automatically every day====

You can update your SPI every 24 hours by adding a new daily task to cron.

Create a new file

/etc/cron.daily/spi

with the single line (with the same parameters as when you generate your SPI yourself)

/usr/local/bin/generate-epg -d 4 -p 48 /home/user/odr/config/mux.conf -o /home/user/odr-radioepg-bridge-master/output.dat

By default, the cron job will run every day at around 06:00. If you want your SPI to update more frequently (every 4 hours), you could add it to the user cron job with

crontab -e

and add the line

0 */4 * * * /usr/local/bin/generate-epg -d 4 -p 48 /home/user/odr/config/mux.conf -o /home/user/odr-radioepg-bridge-master/output.dat

'''NOTE:'''
The SPI creates new MOT TransportIDs for every object each time it is run. A receiver will not recognise that objects have been previously received and cached. If there is an interruption in reception, the SPI will be incomplete. The more frequently you update the SPI, more likely it is that a receiver will not be able to utilise the cached objects.

===Some observations===

* According to specs, logo slides in DAB EPG must be PNG. Although JPG is allowed in hybrid radio SPI, JPG logos will not be added to your DAB EPG. Be sure that your logos (at least those up to 320x240) are PNG.
* Resolved on 12APR21: (Programme descriptions (shortDescription) seem to be processed but not shown. Perhaps we will have to look a little further into this.)
* Updated on 15MAR22: Instructions are now for Python 3

How to configure SPI (Service and Programme Information) for ODR-DabMux

2022-03-15T10:57:59Z

Nickpiggott:

Howto by Ulrik Brinck on odr-radioepg-bridge installation on Debian Jessie. Nick Piggott has contributed with some additions (and edited to show installation for Python 3)

This is now updated to run on Python 3. Instuctions on how to make it (mostly) run on Python 2 are below, but this is now deprecated.
===Introduction===

This tool (or rather series of tools) will pick up your SPI (Service and Programme Information) from the internet via RadioDNS and generate a DAB SPI from it. It was written by Ben Poor and Nick Piggott. In this HowTo, I will describe how it can be installed alongside Python 3.

* Confused about EPG and SPI? In this context, EPG and SPI are basically the same thing. While EPG (Electronic Programme Guide) is an old, but commonly well-known term, SPI (Service and Programme Information) is now the official name of this feature.

===Notes===

'''This tool uses RadioDNS to locate and acquire Service Information (SI.xml), Programme Information (PI.xml) and Logos.'''
Each station you want to add to the SPI must be registered in RadioDNS using the correct information (Ensemble ID, Service ID, Service Component ID), and have correctly formatted SI, PI and logo files in PNG format. Find out more at https://radiodns.org/technical/documentation/#howto

I have assumed that you are logged in to your Linux system as a standard user and have sudo installed on your system. If sudo is not installed, you can see here, how to install it on Debian Jessie:
https://www.geek17.com/en/content/debian-8-jessie-install-and-configure-sudo-25

===Installation===

====Step 0: Update your system====
Begin with "sudo apt-get update" to make sure that you can install all that you need.

====Step 1: Miscellaneous dependencies====
First there are some dependencies to install with apt-get:

sudo apt-get install python3-crcmod python3-bitarray python3-dateutil python3-isodate git

Next there are some dependencies and subcomponents which must be downloaded from github and installed. Establish yourself in a suitable working directory (e.g. ~/src)

====Step 2: python-dabmot====

git clone https://github.com/Opendigitalradio/python-dabmot
cd python-dabmot
sudo python setup.py install
cd ..

====Step 3: python-mot-epg====

git clone https://github.com/Opendigitalradio/python-mot-epg
cd python-mot-epg
sudo python setup.py install
cd ..

====Step 4: python-msc====

git clone https://github.com/Opendigitalradio/python-dabmsc
cd python-dabmsc
sudo python setup.py install
cd ..

====Step 5: pyradiodns====

git clone https://github.com/radiodns/pyradiodns
cd pyradiodns
sudo python setup.py install
cd ..

====Step 6: odr-radiodns-bridge====

git clone https://github.com/Opendigitalradio/odr-radiodns-bridge
cd odr-radiodns-bridge
sudo python setup.py install
cd ..

====Step 7: python-hybridspi====

git clone https://github.com/Opendigitalradio/python-hybridspi
cd python-hybridspi
sudo python setup.py install
cd ..

====Step 8: odr-radioepg-bridge====

git clone https://github.com/Opendigitalradio/odr-radioepg-bridge
sudo ln -s odr-radioepg-bridge-master/generate-epg /usr/local/bin/generate-epg

That's it. You should now be able to run this command and see a help text:
generate-epg -h

===Generating and broadcasting your SPI (EPG)===

====Generating your SPI====

Odr-radioepg-bridge is a command-line tool, which will:
* First read your mux.conf (from your ODR-DabMux configuration) to get information about your services.
* Then try to fetch SPI data for your services from the internet using RadioDNS.
* And lastly generate an output file containing a complete SPI.

If you type "generate-epg -h" you will get a list of available command-line arguments:

usage: generate-epg [-h] [-o OUTPUT] [-X] [-d DAYS] [-p PACKET_SIZE]
[-a PACKET_ADDRESS] [-D]
f

Encodes an SPI bitstream for services in a multiplex configuration file

positional arguments:
f multiplex configuration file

optional arguments:
-h, --help show this help message and exit
-o OUTPUT output bitstream file
-X turn debug on
-d DAYS number of days ahead to encode schedule files
-p PACKET_SIZE Packet size in bytes
-a PACKET_ADDRESS Packet address
-D output Datagroups instead of Packets

The positional argument tells the tool where to find your mux.conf.
The other arguments are optional, and some default values will be used if you don't set them:

* -o can be used to set filename and path to your output file (your SPI). Default is output.dat, placed in the folder from where you run the tool.
* -d is the number of days of programme schedule you want in you SPI. From 1 til 4 days, default is 2.
* -p is packet size. Available values are 24, 48, 72 and 96. Default is 96. Which value you should use, depends on the bitrate in which you are broadcasting your SPI (see below).
* -a is the packet address for your SPI. Default is 1, which will normally be fine. Important is, that you must set the same address in your mux.conf (see below).
* -D will tell the script to output Datagroups instead of Packets. This is useful for some commercial multiplexers or in case you want to broadcast your SPI as X-PAD instead of packet data. Note: You do not need this if you plan to broadcast your SPI the way it's described on this wiki page.

Example:
If your mux.conf is placed in /home/user/odr/config/mux.conf, and you want 4 days in your SPI (today and the next 3 days) and you want to broadcast it in 16 kbit/s, your command line could look like this:

generate-epg -d 4 -p 48 /home/user/odr/config/mux.conf

This will generate a file named output.dat containing your SPI. In this example, I have set the packet size to 48, which is suitable for 16 kbit/s. I have not set the packet address, which means that the default value of 1 will be used.

====Packet sizes and bitrates====

The packet size, which you set when you generate your SPI, should match the bitrate in which you intend to broadcast it. If the packet size is too large, your SPI will not be transmitted. If the packet size is too small, your SPI will (probably) be transmitted, but it will be slower than necessary, because more space will be used for packet headers and maybe partly empty data packets. I will recommend these values:

{| class="wikitable"
! Bitrate
! Packet size
|-
| 8
| 24
|-
| 16
| 48
|-
| 24
| 72
|-
| 32
| 96
|-
| 48
| 72
|-
| 64
| 96
|}

====Broadcasting your SPI====

To broadcast your SPI using ODR-DabMux, create a packet data service in your mux.conf like in this example:

In the services section:

srv-spi {
label "EPG & Logos"
shortlabel "EPGLogos"
; the service-ID consists of 8 hex digits for packet data services. Usually the first two digits will
; be the same as your ECC, and the third digit will be the same as the first digit in your Ensemble Id.
id 0xe1912345
}

In the subchannels section:

sub-spi {
; type packet or enhancedpacket can be used for SPI.
type enhancedpacket
; if you change the bitrate, remember to also change the packet size accordingly (see above) and generate your SPI again.
bitrate 16
protection-profile EEP_A
protection 3
; inputuri is the path and filename for your output file from generate-epg
inputuri "/home/user/odr-radioepg-bridge-master/output.dat"
inputproto file
}

And in the components section (if you are using version 3.1.1 or earlier of odr-dabmux)

comp-spi {
type 60
service srv-spi
subchannel sub-spi
figtype 0x7
; The address must be the same as your packet address set when you generate the SPI (default value is 1).
address 0x1
datagroup true
}

If you are using version 3.1.2 or later of odr-dabmux, the construction of the component section is slightly different

comp-spi {
type 60
service srv-spi
subchannel sub-spi
user-applications {
userapp "spi"
}
address 0x1
datagroup true
}

That's it. Now (re)start your ODR-DabMux, and your SPI should be transmitted.

===Updating your SPI automatically every day===

====Feeding the SPI from a fifo will ensure that you can update it without restarting the MUX====

While the setup shown above will allow you to broadcast your SPI, it ''might'' not allow you to update your SPI without having to restart your MUX.
* If the SPI output file is ''rewritten'', the new content will be picked up by ODR-DabMux automatically, and your SPI will immediately be updated. This will be the case if you use generate-epg to generate a new file directly upon the the old one.
* However, if the SPI output file is ''replaced'', the new file will '''not''' be picked up by ODR-DabMux, until you restart it. This will be the case, if you generate a new file elsewhere (e.g. in a different folder or on another machine) and then ''copy'' it into where the old one is.

To get around this, and be sure that you can always update your SPI, any way you want, you can feed your SPI to ODR-DabMux from a named fifo instead of a file.

Navigate to the folder where you have your SPI and create a fifo like this:

mkfifo spififo

In the subchannel section of your mux.conf, you should replace your SPI file (output.dat) with your fifo, and also add a new line, "nonblock true", so that your SPI subchannel looks like this:

sub-spi {
; type packet or enhancedpacket can be used for SPI.
type enhancedpacket
; if you change the bitrate, remember to also change the packet size accordingly (see above) and generate your SPI again.
bitrate 16
protection-profile EEP_A
protection 3
; inputuri is the path and filename for your output from generate-epg
inputuri "/home/user/odr-radioepg-bridge-master/spififo"
inputproto file
nonblock true
}

Your SPI must be continously sent to the fifo. You can make a shell script for that. Create a file, sendspi.sh, with this content:

#!/bin/bash

while :
do

cat /home/user/odr-radioepg-bridge-master/output.dat >> /home/user/odr-radioepg-bridge-master/spififo

done

And make it executable (chmod +x sendspi.sh).

This script must be running all the time. If you're already using Supervisor to keep your MUX running (as described here: https://github.com/Opendigitalradio/dab-scripts), it's easy to also use supervisor for this script. Create a new file, sendspi.conf, in your /home/user/odr/config/supervisor folder with this content:

[program:sendspi]
command=bash -c "/home/user/odr-radioepg-bridge-master/sendspi.sh"
autostart=true
autorestart=true
startretries=99999
priority=10
stderr_logfile=/dev/stdout
stdout_logfile=/dev/stdout

Then run these commands:

sudo ln -s /home/user/odr/config/supervisor/sendspi.conf /etc/supervisor/conf.d/sendspi.conf
sudo supervisorctl reread
sudo supervisorctl update

Now your SPI is sent to ODR-DabMux from the fifo, and you will now be able to update your SPI, any way you want, without having to restart ODR-DabMux.

====Updating your SPI automatically every day====

You can update your SPI every 24 hours by adding a new daily task to cron.

Create a new file

/etc/cron.daily/spi

with the single line (with the same parameters as when you generate your SPI yourself)

/usr/local/bin/generate-epg -d 4 -p 48 /home/user/odr/config/mux.conf -o /home/user/odr-radioepg-bridge-master/output.dat

By default, the cron job will run every day at around 06:00. If you want your SPI to update more frequently (every 4 hours), you could add it to the user cron job with

crontab -e

and add the line

0 */4 * * * /usr/local/bin/generate-epg -d 4 -p 48 /home/user/odr/config/mux.conf -o /home/user/odr-radioepg-bridge-master/output.dat

'''NOTE:'''
The SPI creates new MOT TransportIDs for every object each time it is run. A receiver will not recognise that objects have been previously received and cached. If there is an interruption in reception, the SPI will be incomplete. The more frequently you update the SPI, more likely it is that a receiver will not be able to utilise the cached objects.

===Some observations===

* According to specs, logo slides in DAB EPG must be PNG. Although JPG is allowed in hybrid radio SPI, JPG logos will not be added to your DAB EPG. Be sure that your logos (at least those up to 320x240) are PNG.
* Resolved on 12APR21: (Programme descriptions (shortDescription) seem to be processed but not shown. Perhaps we will have to look a little further into this.)
* Updated on 15MAR22: Instructions are now for Python 3

How to configure SPI (Service and Programme Information) for ODR-DabMux

2021-04-15T08:57:58Z

Nickpiggott: /* Some observations */

Howto by Ulrik Brinck on odr-radioepg-bridge installation on Debian Jessie. Nick Piggott has contributed with some additions.
===Introduction===

This tool (or rather series of tools) will pick up your SPI (Service and Programme Information) from the internet via RadioDNS and generate a DAB SPI from it. It was written by Ben Poor and Nick Piggott. In this HowTo, I will describe how it can be installed on Debian Jessie. Some details might be slightly different on other Debian generations.

* Confused about EPG and SPI? In this context, EPG and SPI are basically the same thing. While EPG (Electronic Programme Guide) is an old, but commonly well-known term, SPI (Service and Programme Information) is now the official name of this feature.

===Notes===

'''This tool uses RadioDNS to locate and acquire Service Information (SI.xml), Programme Information (PI.xml) and Logos.'''
Each station you want to add to the SPI must be registered in RadioDNS using the correct information (Ensemble ID, Service ID, Service Component ID), and have correctly formatted SI, PI and logo files in PNG format. Find out more at https://radiodns.org/technical/documentation/#howto

I have assumed that you are logged in to your Linux system as a standard user and have sudo installed on your system. If sudo is not installed, you can see here, how to install it on Debian Jessie:
https://www.geek17.com/en/content/debian-8-jessie-install-and-configure-sudo-25

===Installation===

====Step 0: Update your system====
Begin with "sudo apt-get update" to make sure that you can install all that you need.

====Step 1: Miscellaneous dependencies====
First there are some dependencies to install with apt-get:

sudo apt-get install python-crcmod python-bitarray python-dateutil python-isodate

Next there are some dependencies and subcomponents which must be downloaded from github and installed:

====Step 2: python-dabmot====

Download from here https://github.com/Opendigitalradio/python-dabmot and unpack to a folder, e.g. /home/user/python-dabmot-master

Then navigate to the folder and run:
sudo python setup.py install

====Step 3: python-mot-epg====

Download from here https://github.com/Opendigitalradio/python-mot-epg and unpack to a folder, e.g. /home/user/python-mot-epg-master

Then navigate to the folder and run:
sudo python setup.py install

====Step 4: python-msc====

Download from here https://github.com/Opendigitalradio/python-dabmsc and unpack to a folder, e.g. /home/user/python-dabmsc-master

Then navigate to the folder and run:
sudo python setup.py install

====Step 5: pyradiodns====

Download from here https://github.com/radiodns/pyradiodns and unpack to a folder, e.g. /home/user/pyradiodns-master

Then navigate to the folder and run:
sudo apt-get install python-pip
pip install setuptools
sudo python setup.py install

====Step 6: odr-radiodns-bridge====

Download from here https://github.com/Opendigitalradio/odr-radiodns-bridge and unpack to a folder, e.g. /home/user/odr-radiodns-bridge-master

Then navigate to the folder and run:
sudo python setup.py install

====Step 7: python-hybridspi====

Download from here https://github.com/Opendigitalradio/python-hybridspi and unpack to a folder, e.g. /home/user/python-hybridspi-master

Then navigate to the folder and run:
sudo python setup.py install

====Step 8: odr-radioepg-bridge====

And now for the RadioEPG-bridge itself.

Download from here https://github.com/Opendigitalradio/odr-radioepg-bridge and unpack to a folder, e.g. /home/user/odr-radioepg-bridge-master

Then run:
sudo ln -s /home/user/odr-radioepg-bridge-master/generate-epg /usr/local/bin/generate-epg
(If your folder is not /home/user/odr-radioepg-bridge-master, use your_path/generate-epg in the last command line above).

That's it. You should now be able to run this command and see a help text:
generate-epg -h

===Generating and broadcasting your SPI (EPG)===

====Generating your SPI====

Odr-radioepg-bridge is a command-line tool, which will:
* First read your mux.conf (from your ODR-DabMux configuration) to get information about your services.
* Then try to fetch SPI data for your services from the internet using RadioDNS.
* And lastly generate an output file containing a complete SPI.

If you type "generate-epg -h" you will get a list of available command-line arguments:

usage: generate-epg [-h] [-o OUTPUT] [-X] [-d DAYS] [-p PACKET_SIZE]
[-a PACKET_ADDRESS] [-D]
f

Encodes an SPI bitstream for services in a multiplex configuration file

positional arguments:
f multiplex configuration file

optional arguments:
-h, --help show this help message and exit
-o OUTPUT output bitstream file
-X turn debug on
-d DAYS number of days ahead to encode schedule files
-p PACKET_SIZE Packet size in bytes
-a PACKET_ADDRESS Packet address
-D output Datagroups instead of Packets

The positional argument tells the tool where to find your mux.conf.
The other arguments are optional, and some default values will be used if you don't set them:

* -o can be used to set filename and path to your output file (your SPI). Default is output.dat, placed in the folder from where you run the tool.
* -d is the number of days of programme schedule you want in you SPI. From 1 til 4 days, default is 2.
* -p is packet size. Available values are 24, 48, 72 and 96. Default is 96. Which value you should use, depends on the bitrate in which you are broadcasting your SPI (see below).
* -a is the packet address for your SPI. Default is 1, which will normally be fine. Important is, that you must set the same address in your mux.conf (see below).
* -D will tell the script to output Datagroups instead of Packets. This is useful for some commercial multiplexers or in case you want to broadcast your SPI as X-PAD instead of packet data. Note: You do not need this if you plan to broadcast your SPI the way it's described on this wiki page.

Example:
If your mux.conf is placed in /home/user/odr/config/mux.conf, and you want 4 days in your SPI (today and the next 3 days) and you want to broadcast it in 16 kbit/s, your command line could look like this:

generate-epg -d 4 -p 48 /home/user/odr/config/mux.conf

This will generate a file named output.dat containing your SPI. In this example, I have set the packet size to 48, which is suitable for 16 kbit/s. I have not set the packet address, which means that the default value of 1 will be used.

====Packet sizes and bitrates====

The packet size, which you set when you generate your SPI, should match the bitrate in which you intend to broadcast it. If the packet size is too large, your SPI will not be transmitted. If the packet size is too small, your SPI will (probably) be transmitted, but it will be slower than necessary, because more space will be used for packet headers and maybe partly empty data packets. I will recommend these values:

{| class="wikitable"
! Bitrate
! Packet size
|-
| 8
| 24
|-
| 16
| 48
|-
| 24
| 72
|-
| 32
| 96
|-
| 48
| 72
|-
| 64
| 96
|}

====Broadcasting your SPI====

To broadcast your SPI using ODR-DabMux, create a packet data service in your mux.conf like in this example:

In the services section:

srv-spi {
label "EPG & Logos"
shortlabel "EPGLogos"
; the service-ID consists of 8 hex digits for packet data services. Usually the first two digits will
; be the same as your ECC, and the third digit will be the same as the first digit in your Ensemble Id.
id 0xe1912345
}

In the subchannels section:

sub-spi {
; type packet or enhancedpacket can be used for SPI.
type enhancedpacket
; if you change the bitrate, remember to also change the packet size accordingly (see above) and generate your SPI again.
bitrate 16
protection-profile EEP_A
protection 3
; inputuri is the path and filename for your output file from generate-epg
inputuri "/home/user/odr-radioepg-bridge-master/output.dat"
inputproto file
}

And in the components section (if you are using version 3.1.1 or earlier of odr-dabmux)

comp-spi {
type 60
service srv-spi
subchannel sub-spi
figtype 0x7
; The address must be the same as your packet address set when you generate the SPI (default value is 1).
address 0x1
datagroup true
}

If you are using version 3.1.2 or later of odr-dabmux, the construction of the component section is slightly different

comp-spi {
type 60
service srv-spi
subchannel sub-spi
user-applications {
userapp "spi"
}
address 0x1
datagroup true
}

That's it. Now (re)start your ODR-DabMux, and your SPI should be transmitted.

===Updating your SPI automatically every day===

====Feeding the SPI from a fifo will ensure that you can update it without restarting the MUX====

While the setup shown above will allow you to broadcast your SPI, it ''might'' not allow you to update your SPI without having to restart your MUX.
* If the SPI output file is ''rewritten'', the new content will be picked up by ODR-DabMux automatically, and your SPI will immediately be updated. This will be the case if you use generate-epg to generate a new file directly upon the the old one.
* However, if the SPI output file is ''replaced'', the new file will '''not''' be picked up by ODR-DabMux, until you restart it. This will be the case, if you generate a new file elsewhere (e.g. in a different folder or on another machine) and then ''copy'' it into where the old one is.

To get around this, and be sure that you can always update your SPI, any way you want, you can feed your SPI to ODR-DabMux from a named fifo instead of a file.

Navigate to the folder where you have your SPI and create a fifo like this:

mkfifo spififo

In the subchannel section of your mux.conf, you should replace your SPI file (output.dat) with your fifo, and also add a new line, "nonblock true", so that your SPI subchannel looks like this:

sub-spi {
; type packet or enhancedpacket can be used for SPI.
type enhancedpacket
; if you change the bitrate, remember to also change the packet size accordingly (see above) and generate your SPI again.
bitrate 16
protection-profile EEP_A
protection 3
; inputuri is the path and filename for your output from generate-epg
inputuri "/home/user/odr-radioepg-bridge-master/spififo"
inputproto file
nonblock true
}

Your SPI must be continously sent to the fifo. You can make a shell script for that. Create a file, sendspi.sh, with this content:

#!/bin/bash

while :
do

cat /home/user/odr-radioepg-bridge-master/output.dat >> /home/user/odr-radioepg-bridge-master/spififo

done

And make it executable (chmod +x sendspi.sh).

This script must be running all the time. If you're already using Supervisor to keep your MUX running (as described here: https://github.com/Opendigitalradio/dab-scripts), it's easy to also use supervisor for this script. Create a new file, sendspi.conf, in your /home/user/odr/config/supervisor folder with this content:

[program:sendspi]
command=bash -c "/home/user/odr-radioepg-bridge-master/sendspi.sh"
autostart=true
autorestart=true
startretries=99999
priority=10
stderr_logfile=/dev/stdout
stdout_logfile=/dev/stdout

Then run these commands:

sudo ln -s /home/user/odr/config/supervisor/sendspi.conf /etc/supervisor/conf.d/sendspi.conf
sudo supervisorctl reread
sudo supervisorctl update

Now your SPI is sent to ODR-DabMux from the fifo, and you will now be able to update your SPI, any way you want, without having to restart ODR-DabMux.

====Updating your SPI automatically every day====

You can update your SPI every 24 hours by adding a new daily task to cron.

Create a new file

/etc/cron.daily/spi

with the single line (with the same parameters as when you generate your SPI yourself)

/usr/local/bin/generate-epg -d 4 -p 48 /home/user/odr/config/mux.conf -o /home/user/odr-radioepg-bridge-master/output.dat

By default, the cron job will run every day at around 06:00. If you want your SPI to update more frequently (every 4 hours), you could add it to the user cron job with

crontab -e

and add the line

0 */4 * * * /usr/local/bin/generate-epg -d 4 -p 48 /home/user/odr/config/mux.conf -o /home/user/odr-radioepg-bridge-master/output.dat

'''NOTE:'''
The SPI creates new MOT TransportIDs for every object each time it is run. A receiver will not recognise that objects have been previously received and cached. If there is an interruption in reception, the SPI will be incomplete. The more frequently you update the SPI, more likely it is that a receiver will not be able to utilise the cached objects.

===Some observations===

* According to specs, logo slides in DAB EPG must be PNG. Although JPG is allowed in hybrid radio SPI, JPG logos will not be added to your DAB EPG. Be sure that your logos (at least those up to 320x240) are PNG.
* Resolved on 12APR21: (Programme descriptions (shortDescription) seem to be processed but not shown. Perhaps we will have to look a little further into this.)

How to configure SPI (Service and Programme Information) for ODR-DabMux

2020-07-24T15:01:50Z

Nickpiggott: /* Updating your SPI automatically every day */

Howto by Ulrik Brinck on odr-radioepg-bridge installation on Debian Jessie. Nick Piggott has contributed with some additions.
===Introduction===

This tool (or rather series of tools) will pick up your SPI (Service and Programme Information) from the internet via RadioDNS and generate a DAB SPI from it. It was written by Ben Poor and Nick Piggott. In this HowTo, I will describe how it can be installed on Debian Jessie. Some details might be slightly different on other Debian generations.

* Confused about EPG and SPI? In this context, EPG and SPI are basically the same thing. While EPG (Electronic Programme Guide) is an old, but commonly well-known term, SPI (Service and Programme Information) is now the official name of this feature.

===Notes===

'''This tool uses RadioDNS to locate and acquire Service Information (SI.xml), Programme Information (PI.xml) and Logos.'''
Each station you want to add to the SPI must be registered in RadioDNS using the correct information (Ensemble ID, Service ID, Service Component ID), and have correctly formatted SI, PI and logo files in PNG format. Find out more at https://radiodns.org/technical/documentation/#howto

I have assumed that you are logged in to your Linux system as a standard user and have sudo installed on your system. If sudo is not installed, you can see here, how to install it on Debian Jessie:
https://www.geek17.com/en/content/debian-8-jessie-install-and-configure-sudo-25

===Installation===

====Step 0: Update your system====
Begin with "sudo apt-get update" to make sure that you can install all that you need.

====Step 1: Miscellaneous dependencies====
First there are some dependencies to install with apt-get:

sudo apt-get install python-crcmod python-bitarray python-dateutil python-isodate

Next there are some dependencies and subcomponents which must be downloaded from github and installed:

====Step 2: python-dabmot====

Download from here https://github.com/Opendigitalradio/python-dabmot and unpack to a folder, e.g. /home/user/python-dabmot-master

Then navigate to the folder and run:
sudo python setup.py install

====Step 3: python-mot-epg====

Download from here https://github.com/Opendigitalradio/python-mot-epg and unpack to a folder, e.g. /home/user/python-mot-epg-master

Then navigate to the folder and run:
sudo python setup.py install

====Step 4: python-msc====

Download from here https://github.com/Opendigitalradio/python-dabmsc and unpack to a folder, e.g. /home/user/python-dabmsc-master

Then navigate to the folder and run:
sudo python setup.py install

====Step 5: pyradiodns====

Download from here https://github.com/radiodns/pyradiodns and unpack to a folder, e.g. /home/user/pyradiodns-master

Then navigate to the folder and run:
sudo python setup.py install

====Step 6: odr-radiodns-bridge====

Download from here https://github.com/Opendigitalradio/odr-radiodns-bridge and unpack to a folder, e.g. /home/user/odr-radiodns-bridge-master

Then navigate to the folder and run:
sudo python setup.py install

====Step 7: python-hybridspi====

Download from here https://github.com/Opendigitalradio/python-hybridspi and unpack to a folder, e.g. /home/user/python-hybridspi-master

Then navigate to the folder and run:
sudo python setup.py install

====Step 8: odr-radioepg-bridge====

And now for the RadioEPG-bridge itself.

Download from here https://github.com/Opendigitalradio/odr-radioepg-bridge and unpack to a folder, e.g. /home/user/odr-radioepg-bridge-master

Then run:
sudo ln -s /home/user/odr-radioepg-bridge-master/generate-epg /usr/local/bin/generate-epg
(If your folder is not /home/user/odr-radioepg-bridge-master, use your_path/generate-epg in the last command line above).

That's it. You should now be able to run this command and see a help text:
generate-epg -h

===Generating and broadcasting your EPG===

====Generating your SPI====

Odr-radioepg-bridge is a command-line tool, which will:
* First read your mux.conf (from your ODR-DabMux configuration) to get information about your services.
* Then try to fetch SPI data for your services from the internet using RadioDNS.
* And lastly generate an output file containing a complete SPI.

If you type "generate-epg -h" you will get a list of available command-line arguments:

usage: generate-epg [-h] [-o OUTPUT] [-X] [-d DAYS] [-p PACKET_SIZE]
[-a PACKET_ADDRESS] [-D]
f

Encodes an SPI bitstream for services in a multiplex configuration file

positional arguments:
f multiplex configuration file

optional arguments:
-h, --help show this help message and exit
-o OUTPUT output bitstream file
-X turn debug on
-d DAYS number of days ahead to encode schedule files
-p PACKET_SIZE Packet size in bytes
-a PACKET_ADDRESS Packet address
-D output Datagroups instead of Packets

The positional argument tells the tool where to find your mux.conf.
The other arguments are optional, and some default values will be used if you don't set them:

* -o can be used to set filename and path to your output file (your SPI). Default is output.dat, placed in the folder from where you run the tool.
* -d is the number of days of programme schedule you want in you SPI. From 1 til 4 days, default is 2.
* -p is packet size. Available values are 24, 48, 72 and 96. Default is 96. Which value you should use, depends on the bitrate in which you are broadcasting your SPI (see below).
* -a is the packet address for your SPI. Default is 1, which will normally be fine. Important is, that you must set the same address in your mux.conf (see below).
* -D will tell the script to output Datagroups instead of Packets. This is useful for some commercial multiplexers or in case you want to broadcast your SPI as X-PAD instead of packet data. Note: You do not need this if you plan to broadcast your SPI the way it's described on this wiki page.

Example:
If your mux.conf is placed in /home/user/odr/config/mux.conf, and you want 4 days in your SPI (today and the next 3 days) and you want to broadcast it in 16 kbit/s, your command line could look like this:

generate-epg -d 4 -p 48 /home/user/odr/config/mux.conf

This will generate a file named output.dat containing your SPI. In this example, I have set the packet size to 48, which is suitable for 16 kbit/s. I have not set the packet address, which means that the default value of 1 will be used.

====Packet sizes and bitrates====

The packet size, which you set when you generate your SPI, should match the bitrate in which you intend to broadcast it. If the packet size is too large, your SPI will not be transmitted. If the packet size is too small, your SPI will (probably) be transmitted, but it will be slower than necessary, because more space will be used for packet headers and maybe partly empty data packets. I will recommend these values:

{| class="wikitable"
! Bitrate
! Packet size
|-
| 8
| 24
|-
| 16
| 48
|-
| 24
| 72
|-
| 32
| 96
|-
| 48
| 72
|-
| 64
| 96
|}

====Broadcasting your SPI====

To broadcast your SPI using ODR-DabMux, create a packet data service in your mux.conf like in this example:

In the services section:

srv-spi{
label "EPG & Logos"
shortlabel "EPGLogos"
; the service-ID consists of 8 hex digits for packet data services. Usually the first two digits will
; be the same as your ECC, and the third digit will be the same as the first digit in your Ensemble Id.
id 0xe1912345
}

In the subchannels section:

sub-spi {
; type packet or enhancedpacket can be used for SPI.
type enhancedpacket
; if you change the bitrate, remember to also change the packet size accordingly (see above) and generate your EPG again.
bitrate 16
protection-profile EEP_A
protection 3
; inputuri is the path and filename for your output file from generate-epg
inputuri "/home/user/odr-radioepg-bridge-master/output.dat"
inputproto file
}

And in the components section (if you are using version 3.1.1 or earlier of odr-dabmux)

comp-spi {
type 60
service srv-spi
subchannel sub-spi
figtype 0x7
; The address must be the same as your packet address set when you generate the SPI (default value is 1).
address 0x1
datagroup true
}

If you using version 3.1.2 or later of odr-dabmux, the construction of the component section is slightly different

comp-spi {
type 60
service srv-spi
subchannel sub-spi
user-applications {
userapp "spi"
}
address 0x1
datagroup true
}

That's it. Now (re)start your ODR-DabMux, and your SPI should be transmitted.

===Updating your SPI automatically every day===

====Feeding the SPI from a fifo to be able to update it without restarting the MUX====

While the setup shown above will allow you to broadcast your SPI, it will not allow you to update your SPI without having to restart your MUX. To get around this, you can feed your SPI to ODR-DabMux from a named fifo instead of a file.

Navigate to the folder where you have your SPI and create a fifo like this:

mkfifo epgfifo

In the subchannel section of your mux.conf, you should replace your SPI file (output.dat) with your fifo, and also add a new line, "nonblock true", so that your SPI subchannel looks like this:

sub-spi{
; type packet or enhancedpacket can be used for SPI.
type enhancedpacket
; if you change the bitrate, remember to also change the packet size accordingly (see above) and generate your SPI again.
bitrate 16
protection-profile EEP_A
protection 3
; inputuri is the path and filename for your output from generate-epg
inputuri "/home/user/odr-radioepg-bridge-master/epgfifo"
inputproto file
nonblock true
}

Your SPI must be continously sent to the fifo. You can make a shell script for that. Create a file, sendepg.sh, with this content:

#!/bin/bash

while :
do

cat /home/user/odr-radioepg-bridge-master/output.dat >> /home/user/odr-radioepg-bridge-master/epgfifo

done

And make it executable (chmod +x sendepg.sh).

This script must be running all the time. If you're already using Supervisor to keep your MUX running (as described here: https://github.com/Opendigitalradio/dab-scripts), it's easy to also use supervisor for this script. Create a new file, sendepg.conf, in your /home/user/odr/config/supervisor folder with this content:

[program:sendepg]
command=bash -c "/home/user/odr-radioepg-bridge-master/sendepg.sh"
autostart=true
autorestart=true
startretries=99999
priority=10
stderr_logfile=/dev/stdout
stdout_logfile=/dev/stdout

Then run these commands:

sudo ln -s /home/user/odr/config/supervisor/sendepg.conf /etc/supervisor/conf.d/sendepg.conf
sudo supervisorctl reread
sudo supervisorctl update

Now your SPI is sent to ODR-DabMux from the fifo, and you will now be able to update your SPI without having to restart ODR-DabMux.

====Updating your SPI automatically every day====

You can update your SPI every 24 hours by adding a new daily task to cron.

Create a new file

/etc/cron.daily/spi

with the single line (with the same parameters as when you generate your SPI yourself)

/usr/local/bin/generate-epg -d 4 -p 48 /home/user/odr/config/mux.conf -o /home/user/odr-radioepg-bridge-master/output.dat

By default, the cron job will run every day at around 06:00. If you want your SPI to update more frequently (every 4 hours), you could add it to the user cron job with

crontab -e

and add the line

0 */4 * * * /usr/local/bin/generate-epg -d 4 -p 48 /home/user/odr/config/mux.conf -o /home/user/odr-radioepg-bridge-master/output.dat

'''NOTE:'''
The SPI creates new MOT TransportIDs for every object each time it is run. A receiver will not recognise that objects have been previously received and cached. If there is an interruption in reception, the SPI will be incomplete. The more frequently you update the SPI, more likely it is that a receiver will not be able to utilise the cached objects.

===Some observations===

* According to specs, logo slides in DAB EPG must be PNG. Although JPG is allowed in hybrid radio SPI, JPG logos will not be added to your DAB EPG. Be sure that your logos (at least those up to 320x240) are PNG.
* Programme descriptions (shortDescription) seem to be processed but not shown. Perhaps we will have to look a little further into this.

How to configure SPI (Service and Programme Information) for ODR-DabMux

2020-07-24T15:00:02Z

Nickpiggott: /* Updating your EPG automatically every day */

Howto by Ulrik Brinck on odr-radioepg-bridge installation on Debian Jessie. Nick Piggott has contributed with some additions.
===Introduction===

This tool (or rather series of tools) will pick up your SPI (Service and Programme Information) from the internet via RadioDNS and generate a DAB SPI from it. It was written by Ben Poor and Nick Piggott. In this HowTo, I will describe how it can be installed on Debian Jessie. Some details might be slightly different on other Debian generations.

* Confused about EPG and SPI? In this context, EPG and SPI are basically the same thing. While EPG (Electronic Programme Guide) is an old, but commonly well-known term, SPI (Service and Programme Information) is now the official name of this feature.

===Notes===

'''This tool uses RadioDNS to locate and acquire Service Information (SI.xml), Programme Information (PI.xml) and Logos.'''
Each station you want to add to the SPI must be registered in RadioDNS using the correct information (Ensemble ID, Service ID, Service Component ID), and have correctly formatted SI, PI and logo files in PNG format. Find out more at https://radiodns.org/technical/documentation/#howto

I have assumed that you are logged in to your Linux system as a standard user and have sudo installed on your system. If sudo is not installed, you can see here, how to install it on Debian Jessie:
https://www.geek17.com/en/content/debian-8-jessie-install-and-configure-sudo-25

===Installation===

====Step 0: Update your system====
Begin with "sudo apt-get update" to make sure that you can install all that you need.

====Step 1: Miscellaneous dependencies====
First there are some dependencies to install with apt-get:

sudo apt-get install python-crcmod python-bitarray python-dateutil python-isodate

Next there are some dependencies and subcomponents which must be downloaded from github and installed:

====Step 2: python-dabmot====

Download from here https://github.com/Opendigitalradio/python-dabmot and unpack to a folder, e.g. /home/user/python-dabmot-master

Then navigate to the folder and run:
sudo python setup.py install

====Step 3: python-mot-epg====

Download from here https://github.com/Opendigitalradio/python-mot-epg and unpack to a folder, e.g. /home/user/python-mot-epg-master

Then navigate to the folder and run:
sudo python setup.py install

====Step 4: python-msc====

Download from here https://github.com/Opendigitalradio/python-dabmsc and unpack to a folder, e.g. /home/user/python-dabmsc-master

Then navigate to the folder and run:
sudo python setup.py install

====Step 5: pyradiodns====

Download from here https://github.com/radiodns/pyradiodns and unpack to a folder, e.g. /home/user/pyradiodns-master

Then navigate to the folder and run:
sudo python setup.py install

====Step 6: odr-radiodns-bridge====

Download from here https://github.com/Opendigitalradio/odr-radiodns-bridge and unpack to a folder, e.g. /home/user/odr-radiodns-bridge-master

Then navigate to the folder and run:
sudo python setup.py install

====Step 7: python-hybridspi====

Download from here https://github.com/Opendigitalradio/python-hybridspi and unpack to a folder, e.g. /home/user/python-hybridspi-master

Then navigate to the folder and run:
sudo python setup.py install

====Step 8: odr-radioepg-bridge====

And now for the RadioEPG-bridge itself.

Download from here https://github.com/Opendigitalradio/odr-radioepg-bridge and unpack to a folder, e.g. /home/user/odr-radioepg-bridge-master

Then run:
sudo ln -s /home/user/odr-radioepg-bridge-master/generate-epg /usr/local/bin/generate-epg
(If your folder is not /home/user/odr-radioepg-bridge-master, use your_path/generate-epg in the last command line above).

That's it. You should now be able to run this command and see a help text:
generate-epg -h

===Generating and broadcasting your EPG===

====Generating your SPI====

Odr-radioepg-bridge is a command-line tool, which will:
* First read your mux.conf (from your ODR-DabMux configuration) to get information about your services.
* Then try to fetch SPI data for your services from the internet using RadioDNS.
* And lastly generate an output file containing a complete SPI.

If you type "generate-epg -h" you will get a list of available command-line arguments:

usage: generate-epg [-h] [-o OUTPUT] [-X] [-d DAYS] [-p PACKET_SIZE]
[-a PACKET_ADDRESS] [-D]
f

Encodes an SPI bitstream for services in a multiplex configuration file

positional arguments:
f multiplex configuration file

optional arguments:
-h, --help show this help message and exit
-o OUTPUT output bitstream file
-X turn debug on
-d DAYS number of days ahead to encode schedule files
-p PACKET_SIZE Packet size in bytes
-a PACKET_ADDRESS Packet address
-D output Datagroups instead of Packets

The positional argument tells the tool where to find your mux.conf.
The other arguments are optional, and some default values will be used if you don't set them:

* -o can be used to set filename and path to your output file (your SPI). Default is output.dat, placed in the folder from where you run the tool.
* -d is the number of days of programme schedule you want in you SPI. From 1 til 4 days, default is 2.
* -p is packet size. Available values are 24, 48, 72 and 96. Default is 96. Which value you should use, depends on the bitrate in which you are broadcasting your SPI (see below).
* -a is the packet address for your SPI. Default is 1, which will normally be fine. Important is, that you must set the same address in your mux.conf (see below).
* -D will tell the script to output Datagroups instead of Packets. This is useful for some commercial multiplexers or in case you want to broadcast your SPI as X-PAD instead of packet data. Note: You do not need this if you plan to broadcast your SPI the way it's described on this wiki page.

Example:
If your mux.conf is placed in /home/user/odr/config/mux.conf, and you want 4 days in your SPI (today and the next 3 days) and you want to broadcast it in 16 kbit/s, your command line could look like this:

generate-epg -d 4 -p 48 /home/user/odr/config/mux.conf

This will generate a file named output.dat containing your SPI. In this example, I have set the packet size to 48, which is suitable for 16 kbit/s. I have not set the packet address, which means that the default value of 1 will be used.

====Packet sizes and bitrates====

The packet size, which you set when you generate your SPI, should match the bitrate in which you intend to broadcast it. If the packet size is too large, your SPI will not be transmitted. If the packet size is too small, your SPI will (probably) be transmitted, but it will be slower than necessary, because more space will be used for packet headers and maybe partly empty data packets. I will recommend these values:

{| class="wikitable"
! Bitrate
! Packet size
|-
| 8
| 24
|-
| 16
| 48
|-
| 24
| 72
|-
| 32
| 96
|-
| 48
| 72
|-
| 64
| 96
|}

====Broadcasting your SPI====

To broadcast your SPI using ODR-DabMux, create a packet data service in your mux.conf like in this example:

In the services section:

srv-spi{
label "EPG & Logos"
shortlabel "EPGLogos"
; the service-ID consists of 8 hex digits for packet data services. Usually the first two digits will
; be the same as your ECC, and the third digit will be the same as the first digit in your Ensemble Id.
id 0xe1912345
}

In the subchannels section:

sub-spi {
; type packet or enhancedpacket can be used for SPI.
type enhancedpacket
; if you change the bitrate, remember to also change the packet size accordingly (see above) and generate your EPG again.
bitrate 16
protection-profile EEP_A
protection 3
; inputuri is the path and filename for your output file from generate-epg
inputuri "/home/user/odr-radioepg-bridge-master/output.dat"
inputproto file
}

And in the components section (if you are using version 3.1.1 or earlier of odr-dabmux)

comp-spi {
type 60
service srv-spi
subchannel sub-spi
figtype 0x7
; The address must be the same as your packet address set when you generate the SPI (default value is 1).
address 0x1
datagroup true
}

If you using version 3.1.2 or later of odr-dabmux, the construction of the component section is slightly different

comp-spi {
type 60
service srv-spi
subchannel sub-spi
user-applications {
userapp "spi"
}
address 0x1
datagroup true
}

That's it. Now (re)start your ODR-DabMux, and your SPI should be transmitted.

===Updating your SPI automatically every day===

====Feeding the SPI from a fifo to be able to update it without restarting the MUX====

While the setup shown above will allow you to broadcast your SPI, it will not allow you to update your SPI without having to restart your MUX. To get around this, you can feed your SPI to ODR-DabMux from a named fifo instead of a file.

Navigate to the folder where you have your SPI and create a fifo like this:

mkfifo epgfifo

In the subchannel section of your mux.conf, you should replace your SPI file (output.dat) with your fifo, and also add a new line, "nonblock true", so that your SPI subchannel looks like this:

sub-spi{
; type packet or enhancedpacket can be used for SPI.
type enhancedpacket
; if you change the bitrate, remember to also change the packet size accordingly (see above) and generate your SPI again.
bitrate 16
protection-profile EEP_A
protection 3
; inputuri is the path and filename for your output from generate-epg
inputuri "/home/user/odr-radioepg-bridge-master/epgfifo"
inputproto file
nonblock true
}

Your SPI must be continously sent to the fifo. You can make a shell script for that. Create a file, sendepg.sh, with this content:

#!/bin/bash

while :
do

cat /home/user/odr-radioepg-bridge-master/output.dat >> /home/user/odr-radioepg-bridge-master/epgfifo

done

And make it executable (chmod +x sendepg.sh).

This script must be running all the time. If you're already using Supervisor to keep your MUX running (as described here: https://github.com/Opendigitalradio/dab-scripts), it's easy to also use supervisor for this script. Create a new file, sendepg.conf, in your /home/user/odr/config/supervisor folder with this content:

[program:sendepg]
command=bash -c "/home/user/odr-radioepg-bridge-master/sendepg.sh"
autostart=true
autorestart=true
startretries=99999
priority=10
stderr_logfile=/dev/stdout
stdout_logfile=/dev/stdout

Then run these commands:

sudo ln -s /home/user/odr/config/supervisor/sendepg.conf /etc/supervisor/conf.d/sendepg.conf
sudo supervisorctl reread
sudo supervisorctl update

Now your SPI is sent to ODR-DabMux from the fifo, and you will now be able to update your SPI without having to restart ODR-DabMux.

====Updating your SPI automatically every day====

You can update your SPI every 24 hours by adding a new daily task to cron.

Create a new file

/etc/cron.daily/epg

with the single line (with the same parameters as when you generate your SPI yourself)

/usr/local/bin/generate-epg -d 4 -p 48 /home/user/odr/config/mux.conf -o /home/user/odr-radioepg-bridge-master/output.dat

By default, the cron job will run every day at around 06:00. If you want your SPI to update more frequently (every 4 hours), you could add it to the user cron job with

crontab -e

and add the line

0 */4 * * * /usr/local/bin/generate-epg -d 4 -p 48 /home/user/odr/config/mux.conf -o /home/user/odr-radioepg-bridge-master/output.dat

'''NOTE:'''
The SPI creates new MOT TransportIDs for every object each time it is run. A receiver will not recognise that objects have been previously received and cached. If there is an interruption in reception, the SPI will be incomplete. The more frequently you update the SPI, more likely it is that a receiver will not be able to utilise the cached objects.

===Some observations===

* According to specs, logo slides in DAB EPG must be PNG. Although JPG is allowed in hybrid radio SPI, JPG logos will not be added to your DAB EPG. Be sure that your logos (at least those up to 320x240) are PNG.
* Programme descriptions (shortDescription) seem to be processed but not shown. Perhaps we will have to look a little further into this.

How to configure SPI (Service and Programme Information) for ODR-DabMux

2020-07-24T14:58:21Z

Nickpiggott: /* Broadcasting your SPI*/

Howto by Ulrik Brinck on odr-radioepg-bridge installation on Debian Jessie. Nick Piggott has contributed with some additions.
===Introduction===

This tool (or rather series of tools) will pick up your SPI (Service and Programme Information) from the internet via RadioDNS and generate a DAB SPI from it. It was written by Ben Poor and Nick Piggott. In this HowTo, I will describe how it can be installed on Debian Jessie. Some details might be slightly different on other Debian generations.

* Confused about EPG and SPI? In this context, EPG and SPI are basically the same thing. While EPG (Electronic Programme Guide) is an old, but commonly well-known term, SPI (Service and Programme Information) is now the official name of this feature.

===Notes===

'''This tool uses RadioDNS to locate and acquire Service Information (SI.xml), Programme Information (PI.xml) and Logos.'''
Each station you want to add to the SPI must be registered in RadioDNS using the correct information (Ensemble ID, Service ID, Service Component ID), and have correctly formatted SI, PI and logo files in PNG format. Find out more at https://radiodns.org/technical/documentation/#howto

I have assumed that you are logged in to your Linux system as a standard user and have sudo installed on your system. If sudo is not installed, you can see here, how to install it on Debian Jessie:
https://www.geek17.com/en/content/debian-8-jessie-install-and-configure-sudo-25

===Installation===

====Step 0: Update your system====
Begin with "sudo apt-get update" to make sure that you can install all that you need.

====Step 1: Miscellaneous dependencies====
First there are some dependencies to install with apt-get:

sudo apt-get install python-crcmod python-bitarray python-dateutil python-isodate

Next there are some dependencies and subcomponents which must be downloaded from github and installed:

====Step 2: python-dabmot====

Download from here https://github.com/Opendigitalradio/python-dabmot and unpack to a folder, e.g. /home/user/python-dabmot-master

Then navigate to the folder and run:
sudo python setup.py install

====Step 3: python-mot-epg====

Download from here https://github.com/Opendigitalradio/python-mot-epg and unpack to a folder, e.g. /home/user/python-mot-epg-master

Then navigate to the folder and run:
sudo python setup.py install

====Step 4: python-msc====

Download from here https://github.com/Opendigitalradio/python-dabmsc and unpack to a folder, e.g. /home/user/python-dabmsc-master

Then navigate to the folder and run:
sudo python setup.py install

====Step 5: pyradiodns====

Download from here https://github.com/radiodns/pyradiodns and unpack to a folder, e.g. /home/user/pyradiodns-master

Then navigate to the folder and run:
sudo python setup.py install

====Step 6: odr-radiodns-bridge====

Download from here https://github.com/Opendigitalradio/odr-radiodns-bridge and unpack to a folder, e.g. /home/user/odr-radiodns-bridge-master

Then navigate to the folder and run:
sudo python setup.py install

====Step 7: python-hybridspi====

Download from here https://github.com/Opendigitalradio/python-hybridspi and unpack to a folder, e.g. /home/user/python-hybridspi-master

Then navigate to the folder and run:
sudo python setup.py install

====Step 8: odr-radioepg-bridge====

And now for the RadioEPG-bridge itself.

Download from here https://github.com/Opendigitalradio/odr-radioepg-bridge and unpack to a folder, e.g. /home/user/odr-radioepg-bridge-master

Then run:
sudo ln -s /home/user/odr-radioepg-bridge-master/generate-epg /usr/local/bin/generate-epg
(If your folder is not /home/user/odr-radioepg-bridge-master, use your_path/generate-epg in the last command line above).

That's it. You should now be able to run this command and see a help text:
generate-epg -h

===Generating and broadcasting your EPG===

====Generating your SPI====

Odr-radioepg-bridge is a command-line tool, which will:
* First read your mux.conf (from your ODR-DabMux configuration) to get information about your services.
* Then try to fetch SPI data for your services from the internet using RadioDNS.
* And lastly generate an output file containing a complete SPI.

If you type "generate-epg -h" you will get a list of available command-line arguments:

usage: generate-epg [-h] [-o OUTPUT] [-X] [-d DAYS] [-p PACKET_SIZE]
[-a PACKET_ADDRESS] [-D]
f

Encodes an SPI bitstream for services in a multiplex configuration file

positional arguments:
f multiplex configuration file

optional arguments:
-h, --help show this help message and exit
-o OUTPUT output bitstream file
-X turn debug on
-d DAYS number of days ahead to encode schedule files
-p PACKET_SIZE Packet size in bytes
-a PACKET_ADDRESS Packet address
-D output Datagroups instead of Packets

The positional argument tells the tool where to find your mux.conf.
The other arguments are optional, and some default values will be used if you don't set them:

* -o can be used to set filename and path to your output file (your SPI). Default is output.dat, placed in the folder from where you run the tool.
* -d is the number of days of programme schedule you want in you SPI. From 1 til 4 days, default is 2.
* -p is packet size. Available values are 24, 48, 72 and 96. Default is 96. Which value you should use, depends on the bitrate in which you are broadcasting your SPI (see below).
* -a is the packet address for your SPI. Default is 1, which will normally be fine. Important is, that you must set the same address in your mux.conf (see below).
* -D will tell the script to output Datagroups instead of Packets. This is useful for some commercial multiplexers or in case you want to broadcast your SPI as X-PAD instead of packet data. Note: You do not need this if you plan to broadcast your SPI the way it's described on this wiki page.

Example:
If your mux.conf is placed in /home/user/odr/config/mux.conf, and you want 4 days in your SPI (today and the next 3 days) and you want to broadcast it in 16 kbit/s, your command line could look like this:

generate-epg -d 4 -p 48 /home/user/odr/config/mux.conf

This will generate a file named output.dat containing your SPI. In this example, I have set the packet size to 48, which is suitable for 16 kbit/s. I have not set the packet address, which means that the default value of 1 will be used.

====Packet sizes and bitrates====

The packet size, which you set when you generate your SPI, should match the bitrate in which you intend to broadcast it. If the packet size is too large, your SPI will not be transmitted. If the packet size is too small, your SPI will (probably) be transmitted, but it will be slower than necessary, because more space will be used for packet headers and maybe partly empty data packets. I will recommend these values:

{| class="wikitable"
! Bitrate
! Packet size
|-
| 8
| 24
|-
| 16
| 48
|-
| 24
| 72
|-
| 32
| 96
|-
| 48
| 72
|-
| 64
| 96
|}

====Broadcasting your SPI====

To broadcast your SPI using ODR-DabMux, create a packet data service in your mux.conf like in this example:

In the services section:

srv-spi{
label "EPG & Logos"
shortlabel "EPGLogos"
; the service-ID consists of 8 hex digits for packet data services. Usually the first two digits will
; be the same as your ECC, and the third digit will be the same as the first digit in your Ensemble Id.
id 0xe1912345
}

In the subchannels section:

sub-spi {
; type packet or enhancedpacket can be used for SPI.
type enhancedpacket
; if you change the bitrate, remember to also change the packet size accordingly (see above) and generate your EPG again.
bitrate 16
protection-profile EEP_A
protection 3
; inputuri is the path and filename for your output file from generate-epg
inputuri "/home/user/odr-radioepg-bridge-master/output.dat"
inputproto file
}

And in the components section (if you are using version 3.1.1 or earlier of odr-dabmux)

comp-spi {
type 60
service srv-spi
subchannel sub-spi
figtype 0x7
; The address must be the same as your packet address set when you generate the SPI (default value is 1).
address 0x1
datagroup true
}

If you using version 3.1.2 or later of odr-dabmux, the construction of the component section is slightly different

comp-spi {
type 60
service srv-spi
subchannel sub-spi
user-applications {
userapp "spi"
}
address 0x1
datagroup true
}

That's it. Now (re)start your ODR-DabMux, and your SPI should be transmitted.

===Updating your EPG automatically every day===

====Feeding the EPG from a fifo to be able to update it without restarting the MUX====

While the setup shown above will allow you to broadcast your EPG, it will not allow you to update your EPG without having to restart your MUX. To get around this, you can feed your EPG to ODR-DabMux from a named fifo instead of a file.

Navigate to the folder where you have your EPG and create a fifo like this:

mkfifo epgfifo

In the subchannel section of your mux.conf, you should replace your EPG file (output.dat) with your fifo, and also add a new line, "nonblock true", so that your EPG subchannel looks like this:

sub-epg {
; type packet or enhancedpacket can be used for EPG.
type enhancedpacket
; if you change the bitrate, remember to also change the packet size accordingly (see above) and generate your EPG again.
bitrate 16
protection-profile EEP_A
protection 3
; inputuri is the path and filename for your output from generate-epg
inputuri "/home/user/odr-radioepg-bridge-master/epgfifo"
inputproto file
nonblock true
}

Your EPG must be continously sent to the fifo. You can make a shell script for that. Create a file, sendepg.sh, with this content:

#!/bin/bash

while :
do

cat /home/user/odr-radioepg-bridge-master/output.dat >> /home/user/odr-radioepg-bridge-master/epgfifo

done

And make it executable (chmod +x sendepg.sh).

This script must be running all the time. If you're already using Supervisor to keep your MUX running (as described here: https://github.com/Opendigitalradio/dab-scripts), it's easy to also use supervisor for this script. Create a new file, sendepg.conf, in your /home/user/odr/config/supervisor folder with this content:

[program:sendepg]
command=bash -c "/home/user/odr-radioepg-bridge-master/sendepg.sh"
autostart=true
autorestart=true
startretries=99999
priority=10
stderr_logfile=/dev/stdout
stdout_logfile=/dev/stdout

Then run these commands:

sudo ln -s /home/user/odr/config/supervisor/sendepg.conf /etc/supervisor/conf.d/sendepg.conf
sudo supervisorctl reread
sudo supervisorctl update

Now your EPG is sent to ODR-DabMux from the fifo, and you will now be able to update your EPG without having to restart ODR-DabMux.

====Updating your EPG automatically every day====

You can update your EPG every 24 hours by adding a new daily task to cron.

Create a new file

/etc/cron.daily/epg

with the single line (with the same parameters as when you generate your EPG yourself)

/usr/local/bin/generate-epg -d 4 -p 48 /home/user/odr/config/mux.conf -o /home/user/odr-radioepg-bridge-master/output.dat

By default, the cron job will run every day at around 06:00. If you want your EPG to update more frequently (every 4 hours), you could add it to the user cron job with

crontab -e

and add the line

0 */4 * * * /usr/local/bin/generate-epg -d 4 -p 48 /home/user/odr/config/mux.conf -o /home/user/odr-radioepg-bridge-master/output.dat

'''NOTE:'''
The EPG creates new MOT TransportIDs for every object each time it is run. A receiver will not recognise that objects have been previously received and cached. If there is an interruption in reception, the EPG will be incomplete. The more frequently you update the EPG, more likely it is that a receiver will not be able to utilise the cached objects.

===Some observations===

* According to specs, logo slides in DAB EPG must be PNG. Although JPG is allowed in hybrid radio SPI, JPG logos will not be added to your DAB EPG. Be sure that your logos (at least those up to 320x240) are PNG.
* Programme descriptions (shortDescription) seem to be processed but not shown. Perhaps we will have to look a little further into this.

How to configure SPI (Service and Programme Information) for ODR-DabMux

2020-07-24T14:54:15Z

Nickpiggott: /* Packet sizes and bitrates */

Howto by Ulrik Brinck on odr-radioepg-bridge installation on Debian Jessie. Nick Piggott has contributed with some additions.
===Introduction===

This tool (or rather series of tools) will pick up your SPI (Service and Programme Information) from the internet via RadioDNS and generate a DAB SPI from it. It was written by Ben Poor and Nick Piggott. In this HowTo, I will describe how it can be installed on Debian Jessie. Some details might be slightly different on other Debian generations.

* Confused about EPG and SPI? In this context, EPG and SPI are basically the same thing. While EPG (Electronic Programme Guide) is an old, but commonly well-known term, SPI (Service and Programme Information) is now the official name of this feature.

===Notes===

'''This tool uses RadioDNS to locate and acquire Service Information (SI.xml), Programme Information (PI.xml) and Logos.'''
Each station you want to add to the SPI must be registered in RadioDNS using the correct information (Ensemble ID, Service ID, Service Component ID), and have correctly formatted SI, PI and logo files in PNG format. Find out more at https://radiodns.org/technical/documentation/#howto

I have assumed that you are logged in to your Linux system as a standard user and have sudo installed on your system. If sudo is not installed, you can see here, how to install it on Debian Jessie:
https://www.geek17.com/en/content/debian-8-jessie-install-and-configure-sudo-25

===Installation===

====Step 0: Update your system====
Begin with "sudo apt-get update" to make sure that you can install all that you need.

====Step 1: Miscellaneous dependencies====
First there are some dependencies to install with apt-get:

sudo apt-get install python-crcmod python-bitarray python-dateutil python-isodate

Next there are some dependencies and subcomponents which must be downloaded from github and installed:

====Step 2: python-dabmot====

Download from here https://github.com/Opendigitalradio/python-dabmot and unpack to a folder, e.g. /home/user/python-dabmot-master

Then navigate to the folder and run:
sudo python setup.py install

====Step 3: python-mot-epg====

Download from here https://github.com/Opendigitalradio/python-mot-epg and unpack to a folder, e.g. /home/user/python-mot-epg-master

Then navigate to the folder and run:
sudo python setup.py install

====Step 4: python-msc====

Download from here https://github.com/Opendigitalradio/python-dabmsc and unpack to a folder, e.g. /home/user/python-dabmsc-master

Then navigate to the folder and run:
sudo python setup.py install

====Step 5: pyradiodns====

Download from here https://github.com/radiodns/pyradiodns and unpack to a folder, e.g. /home/user/pyradiodns-master

Then navigate to the folder and run:
sudo python setup.py install

====Step 6: odr-radiodns-bridge====

Download from here https://github.com/Opendigitalradio/odr-radiodns-bridge and unpack to a folder, e.g. /home/user/odr-radiodns-bridge-master

Then navigate to the folder and run:
sudo python setup.py install

====Step 7: python-hybridspi====

Download from here https://github.com/Opendigitalradio/python-hybridspi and unpack to a folder, e.g. /home/user/python-hybridspi-master

Then navigate to the folder and run:
sudo python setup.py install

====Step 8: odr-radioepg-bridge====

And now for the RadioEPG-bridge itself.

Download from here https://github.com/Opendigitalradio/odr-radioepg-bridge and unpack to a folder, e.g. /home/user/odr-radioepg-bridge-master

Then run:
sudo ln -s /home/user/odr-radioepg-bridge-master/generate-epg /usr/local/bin/generate-epg
(If your folder is not /home/user/odr-radioepg-bridge-master, use your_path/generate-epg in the last command line above).

That's it. You should now be able to run this command and see a help text:
generate-epg -h

===Generating and broadcasting your EPG===

====Generating your SPI====

Odr-radioepg-bridge is a command-line tool, which will:
* First read your mux.conf (from your ODR-DabMux configuration) to get information about your services.
* Then try to fetch SPI data for your services from the internet using RadioDNS.
* And lastly generate an output file containing a complete SPI.

If you type "generate-epg -h" you will get a list of available command-line arguments:

usage: generate-epg [-h] [-o OUTPUT] [-X] [-d DAYS] [-p PACKET_SIZE]
[-a PACKET_ADDRESS] [-D]
f

Encodes an SPI bitstream for services in a multiplex configuration file

positional arguments:
f multiplex configuration file

optional arguments:
-h, --help show this help message and exit
-o OUTPUT output bitstream file
-X turn debug on
-d DAYS number of days ahead to encode schedule files
-p PACKET_SIZE Packet size in bytes
-a PACKET_ADDRESS Packet address
-D output Datagroups instead of Packets

The positional argument tells the tool where to find your mux.conf.
The other arguments are optional, and some default values will be used if you don't set them:

* -o can be used to set filename and path to your output file (your SPI). Default is output.dat, placed in the folder from where you run the tool.
* -d is the number of days of programme schedule you want in you SPI. From 1 til 4 days, default is 2.
* -p is packet size. Available values are 24, 48, 72 and 96. Default is 96. Which value you should use, depends on the bitrate in which you are broadcasting your SPI (see below).
* -a is the packet address for your SPI. Default is 1, which will normally be fine. Important is, that you must set the same address in your mux.conf (see below).
* -D will tell the script to output Datagroups instead of Packets. This is useful for some commercial multiplexers or in case you want to broadcast your SPI as X-PAD instead of packet data. Note: You do not need this if you plan to broadcast your SPI the way it's described on this wiki page.

Example:
If your mux.conf is placed in /home/user/odr/config/mux.conf, and you want 4 days in your SPI (today and the next 3 days) and you want to broadcast it in 16 kbit/s, your command line could look like this:

generate-epg -d 4 -p 48 /home/user/odr/config/mux.conf

This will generate a file named output.dat containing your SPI. In this example, I have set the packet size to 48, which is suitable for 16 kbit/s. I have not set the packet address, which means that the default value of 1 will be used.

====Packet sizes and bitrates====

The packet size, which you set when you generate your SPI, should match the bitrate in which you intend to broadcast it. If the packet size is too large, your SPI will not be transmitted. If the packet size is too small, your SPI will (probably) be transmitted, but it will be slower than necessary, because more space will be used for packet headers and maybe partly empty data packets. I will recommend these values:

{| class="wikitable"
! Bitrate
! Packet size
|-
| 8
| 24
|-
| 16
| 48
|-
| 24
| 72
|-
| 32
| 96
|-
| 48
| 72
|-
| 64
| 96
|}

====Broadcasting your EPG====

To broadcast your EPG using ODR-DabMux, create a packet data service in your mux.conf like in this example:

In the services section:

srv-epg {
label "EPG"
shortlabel "EPG"
; the service-ID consists of 8 hex digits for packet data services. Usually the first two digits will
; be the same as your ECC, and the third digit will be the same as the first digit in your Ensemble Id.
id 0xe1912345
}

In the subchannels section:

sub-epg {
; type packet or enhancedpacket can be used for EPG.
type enhancedpacket
; if you change the bitrate, remember to also change the packet size accordingly (see above) and generate your EPG again.
bitrate 16
protection-profile EEP_A
protection 3
; inputuri is the path and filename for your output file from generate-epg
inputuri "/home/user/odr-radioepg-bridge-master/output.dat"
inputproto file
}

And in the components section:

comp-epg {
type 60
service srv-epg
subchannel sub-epg
figtype 0x7
; The address must be the same as your packet address set when you generate the EPG (default value is 1).
address 0x1
datagroup true
}

That's it. Now (re)start your ODR-DabMux, and your EPG should be broadcasted.

===Updating your EPG automatically every day===

====Feeding the EPG from a fifo to be able to update it without restarting the MUX====

While the setup shown above will allow you to broadcast your EPG, it will not allow you to update your EPG without having to restart your MUX. To get around this, you can feed your EPG to ODR-DabMux from a named fifo instead of a file.

Navigate to the folder where you have your EPG and create a fifo like this:

mkfifo epgfifo

In the subchannel section of your mux.conf, you should replace your EPG file (output.dat) with your fifo, and also add a new line, "nonblock true", so that your EPG subchannel looks like this:

sub-epg {
; type packet or enhancedpacket can be used for EPG.
type enhancedpacket
; if you change the bitrate, remember to also change the packet size accordingly (see above) and generate your EPG again.
bitrate 16
protection-profile EEP_A
protection 3
; inputuri is the path and filename for your output from generate-epg
inputuri "/home/user/odr-radioepg-bridge-master/epgfifo"
inputproto file
nonblock true
}

Your EPG must be continously sent to the fifo. You can make a shell script for that. Create a file, sendepg.sh, with this content:

#!/bin/bash

while :
do

cat /home/user/odr-radioepg-bridge-master/output.dat >> /home/user/odr-radioepg-bridge-master/epgfifo

done

And make it executable (chmod +x sendepg.sh).

This script must be running all the time. If you're already using Supervisor to keep your MUX running (as described here: https://github.com/Opendigitalradio/dab-scripts), it's easy to also use supervisor for this script. Create a new file, sendepg.conf, in your /home/user/odr/config/supervisor folder with this content:

[program:sendepg]
command=bash -c "/home/user/odr-radioepg-bridge-master/sendepg.sh"
autostart=true
autorestart=true
startretries=99999
priority=10
stderr_logfile=/dev/stdout
stdout_logfile=/dev/stdout

Then run these commands:

sudo ln -s /home/user/odr/config/supervisor/sendepg.conf /etc/supervisor/conf.d/sendepg.conf
sudo supervisorctl reread
sudo supervisorctl update

Now your EPG is sent to ODR-DabMux from the fifo, and you will now be able to update your EPG without having to restart ODR-DabMux.

====Updating your EPG automatically every day====

You can update your EPG every 24 hours by adding a new daily task to cron.

Create a new file

/etc/cron.daily/epg

with the single line (with the same parameters as when you generate your EPG yourself)

/usr/local/bin/generate-epg -d 4 -p 48 /home/user/odr/config/mux.conf -o /home/user/odr-radioepg-bridge-master/output.dat

By default, the cron job will run every day at around 06:00. If you want your EPG to update more frequently (every 4 hours), you could add it to the user cron job with

crontab -e

and add the line

0 */4 * * * /usr/local/bin/generate-epg -d 4 -p 48 /home/user/odr/config/mux.conf -o /home/user/odr-radioepg-bridge-master/output.dat

'''NOTE:'''
The EPG creates new MOT TransportIDs for every object each time it is run. A receiver will not recognise that objects have been previously received and cached. If there is an interruption in reception, the EPG will be incomplete. The more frequently you update the EPG, more likely it is that a receiver will not be able to utilise the cached objects.

===Some observations===

* According to specs, logo slides in DAB EPG must be PNG. Although JPG is allowed in hybrid radio SPI, JPG logos will not be added to your DAB EPG. Be sure that your logos (at least those up to 320x240) are PNG.
* Programme descriptions (shortDescription) seem to be processed but not shown. Perhaps we will have to look a little further into this.

How to configure SPI (Service and Programme Information) for ODR-DabMux

2020-07-24T14:53:45Z

Nickpiggott: /* Generating your SPI */

Howto by Ulrik Brinck on odr-radioepg-bridge installation on Debian Jessie. Nick Piggott has contributed with some additions.
===Introduction===

This tool (or rather series of tools) will pick up your SPI (Service and Programme Information) from the internet via RadioDNS and generate a DAB SPI from it. It was written by Ben Poor and Nick Piggott. In this HowTo, I will describe how it can be installed on Debian Jessie. Some details might be slightly different on other Debian generations.

* Confused about EPG and SPI? In this context, EPG and SPI are basically the same thing. While EPG (Electronic Programme Guide) is an old, but commonly well-known term, SPI (Service and Programme Information) is now the official name of this feature.

===Notes===

'''This tool uses RadioDNS to locate and acquire Service Information (SI.xml), Programme Information (PI.xml) and Logos.'''
Each station you want to add to the SPI must be registered in RadioDNS using the correct information (Ensemble ID, Service ID, Service Component ID), and have correctly formatted SI, PI and logo files in PNG format. Find out more at https://radiodns.org/technical/documentation/#howto

I have assumed that you are logged in to your Linux system as a standard user and have sudo installed on your system. If sudo is not installed, you can see here, how to install it on Debian Jessie:
https://www.geek17.com/en/content/debian-8-jessie-install-and-configure-sudo-25

===Installation===

====Step 0: Update your system====
Begin with "sudo apt-get update" to make sure that you can install all that you need.

====Step 1: Miscellaneous dependencies====
First there are some dependencies to install with apt-get:

sudo apt-get install python-crcmod python-bitarray python-dateutil python-isodate

Next there are some dependencies and subcomponents which must be downloaded from github and installed:

====Step 2: python-dabmot====

Download from here https://github.com/Opendigitalradio/python-dabmot and unpack to a folder, e.g. /home/user/python-dabmot-master

Then navigate to the folder and run:
sudo python setup.py install

====Step 3: python-mot-epg====

Download from here https://github.com/Opendigitalradio/python-mot-epg and unpack to a folder, e.g. /home/user/python-mot-epg-master

Then navigate to the folder and run:
sudo python setup.py install

====Step 4: python-msc====

Download from here https://github.com/Opendigitalradio/python-dabmsc and unpack to a folder, e.g. /home/user/python-dabmsc-master

Then navigate to the folder and run:
sudo python setup.py install

====Step 5: pyradiodns====

Download from here https://github.com/radiodns/pyradiodns and unpack to a folder, e.g. /home/user/pyradiodns-master

Then navigate to the folder and run:
sudo python setup.py install

====Step 6: odr-radiodns-bridge====

Download from here https://github.com/Opendigitalradio/odr-radiodns-bridge and unpack to a folder, e.g. /home/user/odr-radiodns-bridge-master

Then navigate to the folder and run:
sudo python setup.py install

====Step 7: python-hybridspi====

Download from here https://github.com/Opendigitalradio/python-hybridspi and unpack to a folder, e.g. /home/user/python-hybridspi-master

Then navigate to the folder and run:
sudo python setup.py install

====Step 8: odr-radioepg-bridge====

And now for the RadioEPG-bridge itself.

Download from here https://github.com/Opendigitalradio/odr-radioepg-bridge and unpack to a folder, e.g. /home/user/odr-radioepg-bridge-master

Then run:
sudo ln -s /home/user/odr-radioepg-bridge-master/generate-epg /usr/local/bin/generate-epg
(If your folder is not /home/user/odr-radioepg-bridge-master, use your_path/generate-epg in the last command line above).

That's it. You should now be able to run this command and see a help text:
generate-epg -h

===Generating and broadcasting your EPG===

====Generating your SPI====

Odr-radioepg-bridge is a command-line tool, which will:
* First read your mux.conf (from your ODR-DabMux configuration) to get information about your services.
* Then try to fetch SPI data for your services from the internet using RadioDNS.
* And lastly generate an output file containing a complete SPI.

If you type "generate-epg -h" you will get a list of available command-line arguments:

usage: generate-epg [-h] [-o OUTPUT] [-X] [-d DAYS] [-p PACKET_SIZE]
[-a PACKET_ADDRESS] [-D]
f

Encodes an SPI bitstream for services in a multiplex configuration file

positional arguments:
f multiplex configuration file

optional arguments:
-h, --help show this help message and exit
-o OUTPUT output bitstream file
-X turn debug on
-d DAYS number of days ahead to encode schedule files
-p PACKET_SIZE Packet size in bytes
-a PACKET_ADDRESS Packet address
-D output Datagroups instead of Packets

The positional argument tells the tool where to find your mux.conf.
The other arguments are optional, and some default values will be used if you don't set them:

* -o can be used to set filename and path to your output file (your SPI). Default is output.dat, placed in the folder from where you run the tool.
* -d is the number of days of programme schedule you want in you SPI. From 1 til 4 days, default is 2.
* -p is packet size. Available values are 24, 48, 72 and 96. Default is 96. Which value you should use, depends on the bitrate in which you are broadcasting your SPI (see below).
* -a is the packet address for your SPI. Default is 1, which will normally be fine. Important is, that you must set the same address in your mux.conf (see below).
* -D will tell the script to output Datagroups instead of Packets. This is useful for some commercial multiplexers or in case you want to broadcast your SPI as X-PAD instead of packet data. Note: You do not need this if you plan to broadcast your SPI the way it's described on this wiki page.

Example:
If your mux.conf is placed in /home/user/odr/config/mux.conf, and you want 4 days in your SPI (today and the next 3 days) and you want to broadcast it in 16 kbit/s, your command line could look like this:

generate-epg -d 4 -p 48 /home/user/odr/config/mux.conf

This will generate a file named output.dat containing your SPI. In this example, I have set the packet size to 48, which is suitable for 16 kbit/s. I have not set the packet address, which means that the default value of 1 will be used.

====Packet sizes and bitrates====

The packet size, which you set when you generate your EPG, should match the bitrate in which you intend to broadcast it. If the packet size is too large, your EPG will not be broadcasted. If the packet size is too small, your EPG will (probably) be broadcasted, but it will be slower than necessary, because more space will be used for packet headers and maybe partly empty data packets. I will recommend these values:

{| class="wikitable"
! Bitrate
! Packet size
|-
| 8
| 24
|-
| 16
| 48
|-
| 24
| 72
|-
| 32
| 96
|-
| 48
| 72
|-
| 64
| 96
|}

====Broadcasting your EPG====

To broadcast your EPG using ODR-DabMux, create a packet data service in your mux.conf like in this example:

In the services section:

srv-epg {
label "EPG"
shortlabel "EPG"
; the service-ID consists of 8 hex digits for packet data services. Usually the first two digits will
; be the same as your ECC, and the third digit will be the same as the first digit in your Ensemble Id.
id 0xe1912345
}

In the subchannels section:

sub-epg {
; type packet or enhancedpacket can be used for EPG.
type enhancedpacket
; if you change the bitrate, remember to also change the packet size accordingly (see above) and generate your EPG again.
bitrate 16
protection-profile EEP_A
protection 3
; inputuri is the path and filename for your output file from generate-epg
inputuri "/home/user/odr-radioepg-bridge-master/output.dat"
inputproto file
}

And in the components section:

comp-epg {
type 60
service srv-epg
subchannel sub-epg
figtype 0x7
; The address must be the same as your packet address set when you generate the EPG (default value is 1).
address 0x1
datagroup true
}

That's it. Now (re)start your ODR-DabMux, and your EPG should be broadcasted.

===Updating your EPG automatically every day===

====Feeding the EPG from a fifo to be able to update it without restarting the MUX====

While the setup shown above will allow you to broadcast your EPG, it will not allow you to update your EPG without having to restart your MUX. To get around this, you can feed your EPG to ODR-DabMux from a named fifo instead of a file.

Navigate to the folder where you have your EPG and create a fifo like this:

mkfifo epgfifo

In the subchannel section of your mux.conf, you should replace your EPG file (output.dat) with your fifo, and also add a new line, "nonblock true", so that your EPG subchannel looks like this:

sub-epg {
; type packet or enhancedpacket can be used for EPG.
type enhancedpacket
; if you change the bitrate, remember to also change the packet size accordingly (see above) and generate your EPG again.
bitrate 16
protection-profile EEP_A
protection 3
; inputuri is the path and filename for your output from generate-epg
inputuri "/home/user/odr-radioepg-bridge-master/epgfifo"
inputproto file
nonblock true
}

Your EPG must be continously sent to the fifo. You can make a shell script for that. Create a file, sendepg.sh, with this content:

#!/bin/bash

while :
do

cat /home/user/odr-radioepg-bridge-master/output.dat >> /home/user/odr-radioepg-bridge-master/epgfifo

done

And make it executable (chmod +x sendepg.sh).

This script must be running all the time. If you're already using Supervisor to keep your MUX running (as described here: https://github.com/Opendigitalradio/dab-scripts), it's easy to also use supervisor for this script. Create a new file, sendepg.conf, in your /home/user/odr/config/supervisor folder with this content:

[program:sendepg]
command=bash -c "/home/user/odr-radioepg-bridge-master/sendepg.sh"
autostart=true
autorestart=true
startretries=99999
priority=10
stderr_logfile=/dev/stdout
stdout_logfile=/dev/stdout

Then run these commands:

sudo ln -s /home/user/odr/config/supervisor/sendepg.conf /etc/supervisor/conf.d/sendepg.conf
sudo supervisorctl reread
sudo supervisorctl update

Now your EPG is sent to ODR-DabMux from the fifo, and you will now be able to update your EPG without having to restart ODR-DabMux.

====Updating your EPG automatically every day====

You can update your EPG every 24 hours by adding a new daily task to cron.

Create a new file

/etc/cron.daily/epg

with the single line (with the same parameters as when you generate your EPG yourself)

/usr/local/bin/generate-epg -d 4 -p 48 /home/user/odr/config/mux.conf -o /home/user/odr-radioepg-bridge-master/output.dat

By default, the cron job will run every day at around 06:00. If you want your EPG to update more frequently (every 4 hours), you could add it to the user cron job with

crontab -e

and add the line

0 */4 * * * /usr/local/bin/generate-epg -d 4 -p 48 /home/user/odr/config/mux.conf -o /home/user/odr-radioepg-bridge-master/output.dat

'''NOTE:'''
The EPG creates new MOT TransportIDs for every object each time it is run. A receiver will not recognise that objects have been previously received and cached. If there is an interruption in reception, the EPG will be incomplete. The more frequently you update the EPG, more likely it is that a receiver will not be able to utilise the cached objects.

===Some observations===

* According to specs, logo slides in DAB EPG must be PNG. Although JPG is allowed in hybrid radio SPI, JPG logos will not be added to your DAB EPG. Be sure that your logos (at least those up to 320x240) are PNG.
* Programme descriptions (shortDescription) seem to be processed but not shown. Perhaps we will have to look a little further into this.

How to configure SPI (Service and Programme Information) for ODR-DabMux

2020-07-24T14:53:09Z

Nickpiggott: /* Generating your SPI*/

Howto by Ulrik Brinck on odr-radioepg-bridge installation on Debian Jessie. Nick Piggott has contributed with some additions.
===Introduction===

This tool (or rather series of tools) will pick up your SPI (Service and Programme Information) from the internet via RadioDNS and generate a DAB SPI from it. It was written by Ben Poor and Nick Piggott. In this HowTo, I will describe how it can be installed on Debian Jessie. Some details might be slightly different on other Debian generations.

* Confused about EPG and SPI? In this context, EPG and SPI are basically the same thing. While EPG (Electronic Programme Guide) is an old, but commonly well-known term, SPI (Service and Programme Information) is now the official name of this feature.

===Notes===

'''This tool uses RadioDNS to locate and acquire Service Information (SI.xml), Programme Information (PI.xml) and Logos.'''
Each station you want to add to the SPI must be registered in RadioDNS using the correct information (Ensemble ID, Service ID, Service Component ID), and have correctly formatted SI, PI and logo files in PNG format. Find out more at https://radiodns.org/technical/documentation/#howto

I have assumed that you are logged in to your Linux system as a standard user and have sudo installed on your system. If sudo is not installed, you can see here, how to install it on Debian Jessie:
https://www.geek17.com/en/content/debian-8-jessie-install-and-configure-sudo-25

===Installation===

====Step 0: Update your system====
Begin with "sudo apt-get update" to make sure that you can install all that you need.

====Step 1: Miscellaneous dependencies====
First there are some dependencies to install with apt-get:

sudo apt-get install python-crcmod python-bitarray python-dateutil python-isodate

Next there are some dependencies and subcomponents which must be downloaded from github and installed:

====Step 2: python-dabmot====

Download from here https://github.com/Opendigitalradio/python-dabmot and unpack to a folder, e.g. /home/user/python-dabmot-master

Then navigate to the folder and run:
sudo python setup.py install

====Step 3: python-mot-epg====

Download from here https://github.com/Opendigitalradio/python-mot-epg and unpack to a folder, e.g. /home/user/python-mot-epg-master

Then navigate to the folder and run:
sudo python setup.py install

====Step 4: python-msc====

Download from here https://github.com/Opendigitalradio/python-dabmsc and unpack to a folder, e.g. /home/user/python-dabmsc-master

Then navigate to the folder and run:
sudo python setup.py install

====Step 5: pyradiodns====

Download from here https://github.com/radiodns/pyradiodns and unpack to a folder, e.g. /home/user/pyradiodns-master

Then navigate to the folder and run:
sudo python setup.py install

====Step 6: odr-radiodns-bridge====

Download from here https://github.com/Opendigitalradio/odr-radiodns-bridge and unpack to a folder, e.g. /home/user/odr-radiodns-bridge-master

Then navigate to the folder and run:
sudo python setup.py install

====Step 7: python-hybridspi====

Download from here https://github.com/Opendigitalradio/python-hybridspi and unpack to a folder, e.g. /home/user/python-hybridspi-master

Then navigate to the folder and run:
sudo python setup.py install

====Step 8: odr-radioepg-bridge====

And now for the RadioEPG-bridge itself.

Download from here https://github.com/Opendigitalradio/odr-radioepg-bridge and unpack to a folder, e.g. /home/user/odr-radioepg-bridge-master

Then run:
sudo ln -s /home/user/odr-radioepg-bridge-master/generate-epg /usr/local/bin/generate-epg
(If your folder is not /home/user/odr-radioepg-bridge-master, use your_path/generate-epg in the last command line above).

That's it. You should now be able to run this command and see a help text:
generate-epg -h

===Generating and broadcasting your EPG===

====Generating your SPI====

Odr-radioepg-bridge is a command-line tool, which will:
* First read your mux.conf (from your ODR-DabMux configuration) to get information about your services.
* Then try to fetch SPI data for your services from the internet using RadioDNS.
* And lastly generate an output file containing a complete SPI.

If you type "generate-epg -h" you will get a list of available command-line arguments:

usage: generate-epg [-h] [-o OUTPUT] [-X] [-d DAYS] [-p PACKET_SIZE]
[-a PACKET_ADDRESS] [-D]
f

Encodes an SPI bitstream for services in a multiplex configuration file

positional arguments:
f multiplex configuration file

optional arguments:
-h, --help show this help message and exit
-o OUTPUT output bitstream file
-X turn debug on
-d DAYS number of days ahead to encode schedule files
-p PACKET_SIZE Packet size in bytes
-a PACKET_ADDRESS Packet address
-D output Datagroups instead of Packets

The positional argument tells the tool where to find your mux.conf.
The other arguments are optional, and some default values will be used if you don't set them:

* -o can be used to set filename and path to your output file (your EPG). Default is output.dat, placed in the folder from where you run the tool.
* -d is the number of days of programme schedule you want in you EPG. From 1 til 4 days, default is 2.
* -p is packet size. Available values are 24, 48, 72 and 96. Default is 96. Which value you should use, depends on the bitrate in which you are broadcasting your EPG (see below).
* -a is the packet address for your EPG. Default is 1, which will normally be fine. Important is, that you must set the same address in your mux.conf (see below).
* -D will tell the script to output Datagroups instead of Packets. This is useful for some commercial multiplexers or in case you want to broadcast your EPG as X-PAD instead of packet data. Note: You do not need this if you plan to broadcast your EPG the way it's described on this wiki page.

Example:
If your mux.conf is placed in /home/user/odr/config/mux.conf, and you want 4 days in your EPG (today and the next 3 days) and you want to broadcast it in 16 kbit/s, your command line could look like this:

generate-epg -d 4 -p 48 /home/user/odr/config/mux.conf

This will generate a file named output.dat containing your EPG. In this example, I have set the packet size to 48, which is suitable for 16 kbit/s. I have not set the packet address, which means that the default value of 1 will be used.

====Packet sizes and bitrates====

The packet size, which you set when you generate your EPG, should match the bitrate in which you intend to broadcast it. If the packet size is too large, your EPG will not be broadcasted. If the packet size is too small, your EPG will (probably) be broadcasted, but it will be slower than necessary, because more space will be used for packet headers and maybe partly empty data packets. I will recommend these values:

{| class="wikitable"
! Bitrate
! Packet size
|-
| 8
| 24
|-
| 16
| 48
|-
| 24
| 72
|-
| 32
| 96
|-
| 48
| 72
|-
| 64
| 96
|}

====Broadcasting your EPG====

To broadcast your EPG using ODR-DabMux, create a packet data service in your mux.conf like in this example:

In the services section:

srv-epg {
label "EPG"
shortlabel "EPG"
; the service-ID consists of 8 hex digits for packet data services. Usually the first two digits will
; be the same as your ECC, and the third digit will be the same as the first digit in your Ensemble Id.
id 0xe1912345
}

In the subchannels section:

sub-epg {
; type packet or enhancedpacket can be used for EPG.
type enhancedpacket
; if you change the bitrate, remember to also change the packet size accordingly (see above) and generate your EPG again.
bitrate 16
protection-profile EEP_A
protection 3
; inputuri is the path and filename for your output file from generate-epg
inputuri "/home/user/odr-radioepg-bridge-master/output.dat"
inputproto file
}

And in the components section:

comp-epg {
type 60
service srv-epg
subchannel sub-epg
figtype 0x7
; The address must be the same as your packet address set when you generate the EPG (default value is 1).
address 0x1
datagroup true
}

That's it. Now (re)start your ODR-DabMux, and your EPG should be broadcasted.

===Updating your EPG automatically every day===

====Feeding the EPG from a fifo to be able to update it without restarting the MUX====

While the setup shown above will allow you to broadcast your EPG, it will not allow you to update your EPG without having to restart your MUX. To get around this, you can feed your EPG to ODR-DabMux from a named fifo instead of a file.

Navigate to the folder where you have your EPG and create a fifo like this:

mkfifo epgfifo

In the subchannel section of your mux.conf, you should replace your EPG file (output.dat) with your fifo, and also add a new line, "nonblock true", so that your EPG subchannel looks like this:

sub-epg {
; type packet or enhancedpacket can be used for EPG.
type enhancedpacket
; if you change the bitrate, remember to also change the packet size accordingly (see above) and generate your EPG again.
bitrate 16
protection-profile EEP_A
protection 3
; inputuri is the path and filename for your output from generate-epg
inputuri "/home/user/odr-radioepg-bridge-master/epgfifo"
inputproto file
nonblock true
}

Your EPG must be continously sent to the fifo. You can make a shell script for that. Create a file, sendepg.sh, with this content:

#!/bin/bash

while :
do

cat /home/user/odr-radioepg-bridge-master/output.dat >> /home/user/odr-radioepg-bridge-master/epgfifo

done

And make it executable (chmod +x sendepg.sh).

This script must be running all the time. If you're already using Supervisor to keep your MUX running (as described here: https://github.com/Opendigitalradio/dab-scripts), it's easy to also use supervisor for this script. Create a new file, sendepg.conf, in your /home/user/odr/config/supervisor folder with this content:

[program:sendepg]
command=bash -c "/home/user/odr-radioepg-bridge-master/sendepg.sh"
autostart=true
autorestart=true
startretries=99999
priority=10
stderr_logfile=/dev/stdout
stdout_logfile=/dev/stdout

Then run these commands:

sudo ln -s /home/user/odr/config/supervisor/sendepg.conf /etc/supervisor/conf.d/sendepg.conf
sudo supervisorctl reread
sudo supervisorctl update

Now your EPG is sent to ODR-DabMux from the fifo, and you will now be able to update your EPG without having to restart ODR-DabMux.

====Updating your EPG automatically every day====

You can update your EPG every 24 hours by adding a new daily task to cron.

Create a new file

/etc/cron.daily/epg

with the single line (with the same parameters as when you generate your EPG yourself)

/usr/local/bin/generate-epg -d 4 -p 48 /home/user/odr/config/mux.conf -o /home/user/odr-radioepg-bridge-master/output.dat

By default, the cron job will run every day at around 06:00. If you want your EPG to update more frequently (every 4 hours), you could add it to the user cron job with

crontab -e

and add the line

0 */4 * * * /usr/local/bin/generate-epg -d 4 -p 48 /home/user/odr/config/mux.conf -o /home/user/odr-radioepg-bridge-master/output.dat

'''NOTE:'''
The EPG creates new MOT TransportIDs for every object each time it is run. A receiver will not recognise that objects have been previously received and cached. If there is an interruption in reception, the EPG will be incomplete. The more frequently you update the EPG, more likely it is that a receiver will not be able to utilise the cached objects.

===Some observations===

* According to specs, logo slides in DAB EPG must be PNG. Although JPG is allowed in hybrid radio SPI, JPG logos will not be added to your DAB EPG. Be sure that your logos (at least those up to 320x240) are PNG.
* Programme descriptions (shortDescription) seem to be processed but not shown. Perhaps we will have to look a little further into this.

How to configure SPI (Service and Programme Information) for ODR-DabMux

2020-07-24T14:52:12Z

Nickpiggott: /* Step 1: Miscellaneous dependencies */

Howto by Ulrik Brinck on odr-radioepg-bridge installation on Debian Jessie. Nick Piggott has contributed with some additions.
===Introduction===

This tool (or rather series of tools) will pick up your SPI (Service and Programme Information) from the internet via RadioDNS and generate a DAB SPI from it. It was written by Ben Poor and Nick Piggott. In this HowTo, I will describe how it can be installed on Debian Jessie. Some details might be slightly different on other Debian generations.

* Confused about EPG and SPI? In this context, EPG and SPI are basically the same thing. While EPG (Electronic Programme Guide) is an old, but commonly well-known term, SPI (Service and Programme Information) is now the official name of this feature.

===Notes===

'''This tool uses RadioDNS to locate and acquire Service Information (SI.xml), Programme Information (PI.xml) and Logos.'''
Each station you want to add to the SPI must be registered in RadioDNS using the correct information (Ensemble ID, Service ID, Service Component ID), and have correctly formatted SI, PI and logo files in PNG format. Find out more at https://radiodns.org/technical/documentation/#howto

I have assumed that you are logged in to your Linux system as a standard user and have sudo installed on your system. If sudo is not installed, you can see here, how to install it on Debian Jessie:
https://www.geek17.com/en/content/debian-8-jessie-install-and-configure-sudo-25

===Installation===

====Step 0: Update your system====
Begin with "sudo apt-get update" to make sure that you can install all that you need.

====Step 1: Miscellaneous dependencies====
First there are some dependencies to install with apt-get:

sudo apt-get install python-crcmod python-bitarray python-dateutil python-isodate

Next there are some dependencies and subcomponents which must be downloaded from github and installed:

====Step 2: python-dabmot====

Download from here https://github.com/Opendigitalradio/python-dabmot and unpack to a folder, e.g. /home/user/python-dabmot-master

Then navigate to the folder and run:
sudo python setup.py install

====Step 3: python-mot-epg====

Download from here https://github.com/Opendigitalradio/python-mot-epg and unpack to a folder, e.g. /home/user/python-mot-epg-master

Then navigate to the folder and run:
sudo python setup.py install

====Step 4: python-msc====

Download from here https://github.com/Opendigitalradio/python-dabmsc and unpack to a folder, e.g. /home/user/python-dabmsc-master

Then navigate to the folder and run:
sudo python setup.py install

====Step 5: pyradiodns====

Download from here https://github.com/radiodns/pyradiodns and unpack to a folder, e.g. /home/user/pyradiodns-master

Then navigate to the folder and run:
sudo python setup.py install

====Step 6: odr-radiodns-bridge====

Download from here https://github.com/Opendigitalradio/odr-radiodns-bridge and unpack to a folder, e.g. /home/user/odr-radiodns-bridge-master

Then navigate to the folder and run:
sudo python setup.py install

====Step 7: python-hybridspi====

Download from here https://github.com/Opendigitalradio/python-hybridspi and unpack to a folder, e.g. /home/user/python-hybridspi-master

Then navigate to the folder and run:
sudo python setup.py install

====Step 8: odr-radioepg-bridge====

And now for the RadioEPG-bridge itself.

Download from here https://github.com/Opendigitalradio/odr-radioepg-bridge and unpack to a folder, e.g. /home/user/odr-radioepg-bridge-master

Then run:
sudo ln -s /home/user/odr-radioepg-bridge-master/generate-epg /usr/local/bin/generate-epg
(If your folder is not /home/user/odr-radioepg-bridge-master, use your_path/generate-epg in the last command line above).

That's it. You should now be able to run this command and see a help text:
generate-epg -h

===Generating and broadcasting your EPG===

====Generating your EPG====

Odr-radioepg-bridge is a command-line tool, which will:
* First read your mux.conf (from your ODR-DabMux configuration) to get information about your services.
* Then try to fetch SPI data for your services from the internet using RadioDNS.
* And lastly generate an output file containing a complete EPG.

If you type "generate-epg -h" you will get a list of available command-line arguments:

usage: generate-epg [-h] [-o OUTPUT] [-X] [-d DAYS] [-p PACKET_SIZE]
[-a PACKET_ADDRESS] [-D]
f

Encodes an SPI bitstream for services in a multiplex configuration file

positional arguments:
f multiplex configuration file

optional arguments:
-h, --help show this help message and exit
-o OUTPUT output bitstream file
-X turn debug on
-d DAYS number of days ahead to encode schedule files
-p PACKET_SIZE Packet size in bytes
-a PACKET_ADDRESS Packet address
-D output Datagroups instead of Packets

The positional argument tells the tool where to find your mux.conf.
The other arguments are optional, and some default values will be used if you don't set them:

* -o can be used to set filename and path to your output file (your EPG). Default is output.dat, placed in the folder from where you run the tool.
* -d is the number of days of programme schedule you want in you EPG. From 1 til 4 days, default is 2.
* -p is packet size. Available values are 24, 48, 72 and 96. Default is 96. Which value you should use, depends on the bitrate in which you are broadcasting your EPG (see below).
* -a is the packet address for your EPG. Default is 1, which will normally be fine. Important is, that you must set the same address in your mux.conf (see below).
* -D will tell the script to output Datagroups instead of Packets. This is useful for some commercial multiplexers or in case you want to broadcast your EPG as X-PAD instead of packet data. Note: You do not need this if you plan to broadcast your EPG the way it's described on this wiki page.

Example:
If your mux.conf is placed in /home/user/odr/config/mux.conf, and you want 4 days in your EPG (today and the next 3 days) and you want to broadcast it in 16 kbit/s, your command line could look like this:

generate-epg -d 4 -p 48 /home/user/odr/config/mux.conf

This will generate a file named output.dat containing your EPG. In this example, I have set the packet size to 48, which is suitable for 16 kbit/s. I have not set the packet address, which means that the default value of 1 will be used.

====Packet sizes and bitrates====

The packet size, which you set when you generate your EPG, should match the bitrate in which you intend to broadcast it. If the packet size is too large, your EPG will not be broadcasted. If the packet size is too small, your EPG will (probably) be broadcasted, but it will be slower than necessary, because more space will be used for packet headers and maybe partly empty data packets. I will recommend these values:

{| class="wikitable"
! Bitrate
! Packet size
|-
| 8
| 24
|-
| 16
| 48
|-
| 24
| 72
|-
| 32
| 96
|-
| 48
| 72
|-
| 64
| 96
|}

====Broadcasting your EPG====

To broadcast your EPG using ODR-DabMux, create a packet data service in your mux.conf like in this example:

In the services section:

srv-epg {
label "EPG"
shortlabel "EPG"
; the service-ID consists of 8 hex digits for packet data services. Usually the first two digits will
; be the same as your ECC, and the third digit will be the same as the first digit in your Ensemble Id.
id 0xe1912345
}

In the subchannels section:

sub-epg {
; type packet or enhancedpacket can be used for EPG.
type enhancedpacket
; if you change the bitrate, remember to also change the packet size accordingly (see above) and generate your EPG again.
bitrate 16
protection-profile EEP_A
protection 3
; inputuri is the path and filename for your output file from generate-epg
inputuri "/home/user/odr-radioepg-bridge-master/output.dat"
inputproto file
}

And in the components section:

comp-epg {
type 60
service srv-epg
subchannel sub-epg
figtype 0x7
; The address must be the same as your packet address set when you generate the EPG (default value is 1).
address 0x1
datagroup true
}

That's it. Now (re)start your ODR-DabMux, and your EPG should be broadcasted.

===Updating your EPG automatically every day===

====Feeding the EPG from a fifo to be able to update it without restarting the MUX====

While the setup shown above will allow you to broadcast your EPG, it will not allow you to update your EPG without having to restart your MUX. To get around this, you can feed your EPG to ODR-DabMux from a named fifo instead of a file.

Navigate to the folder where you have your EPG and create a fifo like this:

mkfifo epgfifo

In the subchannel section of your mux.conf, you should replace your EPG file (output.dat) with your fifo, and also add a new line, "nonblock true", so that your EPG subchannel looks like this:

sub-epg {
; type packet or enhancedpacket can be used for EPG.
type enhancedpacket
; if you change the bitrate, remember to also change the packet size accordingly (see above) and generate your EPG again.
bitrate 16
protection-profile EEP_A
protection 3
; inputuri is the path and filename for your output from generate-epg
inputuri "/home/user/odr-radioepg-bridge-master/epgfifo"
inputproto file
nonblock true
}

Your EPG must be continously sent to the fifo. You can make a shell script for that. Create a file, sendepg.sh, with this content:

#!/bin/bash

while :
do

cat /home/user/odr-radioepg-bridge-master/output.dat >> /home/user/odr-radioepg-bridge-master/epgfifo

done

And make it executable (chmod +x sendepg.sh).

This script must be running all the time. If you're already using Supervisor to keep your MUX running (as described here: https://github.com/Opendigitalradio/dab-scripts), it's easy to also use supervisor for this script. Create a new file, sendepg.conf, in your /home/user/odr/config/supervisor folder with this content:

[program:sendepg]
command=bash -c "/home/user/odr-radioepg-bridge-master/sendepg.sh"
autostart=true
autorestart=true
startretries=99999
priority=10
stderr_logfile=/dev/stdout
stdout_logfile=/dev/stdout

Then run these commands:

sudo ln -s /home/user/odr/config/supervisor/sendepg.conf /etc/supervisor/conf.d/sendepg.conf
sudo supervisorctl reread
sudo supervisorctl update

Now your EPG is sent to ODR-DabMux from the fifo, and you will now be able to update your EPG without having to restart ODR-DabMux.

====Updating your EPG automatically every day====

You can update your EPG every 24 hours by adding a new daily task to cron.

Create a new file

/etc/cron.daily/epg

with the single line (with the same parameters as when you generate your EPG yourself)

/usr/local/bin/generate-epg -d 4 -p 48 /home/user/odr/config/mux.conf -o /home/user/odr-radioepg-bridge-master/output.dat

By default, the cron job will run every day at around 06:00. If you want your EPG to update more frequently (every 4 hours), you could add it to the user cron job with

crontab -e

and add the line

0 */4 * * * /usr/local/bin/generate-epg -d 4 -p 48 /home/user/odr/config/mux.conf -o /home/user/odr-radioepg-bridge-master/output.dat

'''NOTE:'''
The EPG creates new MOT TransportIDs for every object each time it is run. A receiver will not recognise that objects have been previously received and cached. If there is an interruption in reception, the EPG will be incomplete. The more frequently you update the EPG, more likely it is that a receiver will not be able to utilise the cached objects.

===Some observations===

* According to specs, logo slides in DAB EPG must be PNG. Although JPG is allowed in hybrid radio SPI, JPG logos will not be added to your DAB EPG. Be sure that your logos (at least those up to 320x240) are PNG.
* Programme descriptions (shortDescription) seem to be processed but not shown. Perhaps we will have to look a little further into this.

How to configure SPI (Service and Programme Information) for ODR-DabMux

2020-07-24T14:51:48Z

Nickpiggott: /* Step 1: Miscellaneous dependencies */

Howto by Ulrik Brinck on odr-radioepg-bridge installation on Debian Jessie. Nick Piggott has contributed with some additions.
===Introduction===

This tool (or rather series of tools) will pick up your SPI (Service and Programme Information) from the internet via RadioDNS and generate a DAB SPI from it. It was written by Ben Poor and Nick Piggott. In this HowTo, I will describe how it can be installed on Debian Jessie. Some details might be slightly different on other Debian generations.

* Confused about EPG and SPI? In this context, EPG and SPI are basically the same thing. While EPG (Electronic Programme Guide) is an old, but commonly well-known term, SPI (Service and Programme Information) is now the official name of this feature.

===Notes===

'''This tool uses RadioDNS to locate and acquire Service Information (SI.xml), Programme Information (PI.xml) and Logos.'''
Each station you want to add to the SPI must be registered in RadioDNS using the correct information (Ensemble ID, Service ID, Service Component ID), and have correctly formatted SI, PI and logo files in PNG format. Find out more at https://radiodns.org/technical/documentation/#howto

I have assumed that you are logged in to your Linux system as a standard user and have sudo installed on your system. If sudo is not installed, you can see here, how to install it on Debian Jessie:
https://www.geek17.com/en/content/debian-8-jessie-install-and-configure-sudo-25

===Installation===

====Step 0: Update your system====
Begin with "sudo apt-get update" to make sure that you can install all that you need.

====Step 1: Miscellaneous dependencies====
First there are some dependencies to install with apt-get:

sudo apt-get install python-crcmod
sudo apt-get install python-bitarray
sudo apt-get install python-dateutil
sudo apt-get install python-isodate

Next there are some dependencies and subcomponents which must be downloaded from github and installed:

====Step 2: python-dabmot====

Download from here https://github.com/Opendigitalradio/python-dabmot and unpack to a folder, e.g. /home/user/python-dabmot-master

Then navigate to the folder and run:
sudo python setup.py install

====Step 3: python-mot-epg====

Download from here https://github.com/Opendigitalradio/python-mot-epg and unpack to a folder, e.g. /home/user/python-mot-epg-master

Then navigate to the folder and run:
sudo python setup.py install

====Step 4: python-msc====

Download from here https://github.com/Opendigitalradio/python-dabmsc and unpack to a folder, e.g. /home/user/python-dabmsc-master

Then navigate to the folder and run:
sudo python setup.py install

====Step 5: pyradiodns====

Download from here https://github.com/radiodns/pyradiodns and unpack to a folder, e.g. /home/user/pyradiodns-master

Then navigate to the folder and run:
sudo python setup.py install

====Step 6: odr-radiodns-bridge====

Download from here https://github.com/Opendigitalradio/odr-radiodns-bridge and unpack to a folder, e.g. /home/user/odr-radiodns-bridge-master

Then navigate to the folder and run:
sudo python setup.py install

====Step 7: python-hybridspi====

Download from here https://github.com/Opendigitalradio/python-hybridspi and unpack to a folder, e.g. /home/user/python-hybridspi-master

Then navigate to the folder and run:
sudo python setup.py install

====Step 8: odr-radioepg-bridge====

And now for the RadioEPG-bridge itself.

Download from here https://github.com/Opendigitalradio/odr-radioepg-bridge and unpack to a folder, e.g. /home/user/odr-radioepg-bridge-master

Then run:
sudo ln -s /home/user/odr-radioepg-bridge-master/generate-epg /usr/local/bin/generate-epg
(If your folder is not /home/user/odr-radioepg-bridge-master, use your_path/generate-epg in the last command line above).

That's it. You should now be able to run this command and see a help text:
generate-epg -h

===Generating and broadcasting your EPG===

====Generating your EPG====

Odr-radioepg-bridge is a command-line tool, which will:
* First read your mux.conf (from your ODR-DabMux configuration) to get information about your services.
* Then try to fetch SPI data for your services from the internet using RadioDNS.
* And lastly generate an output file containing a complete EPG.

If you type "generate-epg -h" you will get a list of available command-line arguments:

usage: generate-epg [-h] [-o OUTPUT] [-X] [-d DAYS] [-p PACKET_SIZE]
[-a PACKET_ADDRESS] [-D]
f

Encodes an SPI bitstream for services in a multiplex configuration file

positional arguments:
f multiplex configuration file

optional arguments:
-h, --help show this help message and exit
-o OUTPUT output bitstream file
-X turn debug on
-d DAYS number of days ahead to encode schedule files
-p PACKET_SIZE Packet size in bytes
-a PACKET_ADDRESS Packet address
-D output Datagroups instead of Packets

The positional argument tells the tool where to find your mux.conf.
The other arguments are optional, and some default values will be used if you don't set them:

* -o can be used to set filename and path to your output file (your EPG). Default is output.dat, placed in the folder from where you run the tool.
* -d is the number of days of programme schedule you want in you EPG. From 1 til 4 days, default is 2.
* -p is packet size. Available values are 24, 48, 72 and 96. Default is 96. Which value you should use, depends on the bitrate in which you are broadcasting your EPG (see below).
* -a is the packet address for your EPG. Default is 1, which will normally be fine. Important is, that you must set the same address in your mux.conf (see below).
* -D will tell the script to output Datagroups instead of Packets. This is useful for some commercial multiplexers or in case you want to broadcast your EPG as X-PAD instead of packet data. Note: You do not need this if you plan to broadcast your EPG the way it's described on this wiki page.

Example:
If your mux.conf is placed in /home/user/odr/config/mux.conf, and you want 4 days in your EPG (today and the next 3 days) and you want to broadcast it in 16 kbit/s, your command line could look like this:

generate-epg -d 4 -p 48 /home/user/odr/config/mux.conf

This will generate a file named output.dat containing your EPG. In this example, I have set the packet size to 48, which is suitable for 16 kbit/s. I have not set the packet address, which means that the default value of 1 will be used.

====Packet sizes and bitrates====

The packet size, which you set when you generate your EPG, should match the bitrate in which you intend to broadcast it. If the packet size is too large, your EPG will not be broadcasted. If the packet size is too small, your EPG will (probably) be broadcasted, but it will be slower than necessary, because more space will be used for packet headers and maybe partly empty data packets. I will recommend these values:

{| class="wikitable"
! Bitrate
! Packet size
|-
| 8
| 24
|-
| 16
| 48
|-
| 24
| 72
|-
| 32
| 96
|-
| 48
| 72
|-
| 64
| 96
|}

====Broadcasting your EPG====

To broadcast your EPG using ODR-DabMux, create a packet data service in your mux.conf like in this example:

In the services section:

srv-epg {
label "EPG"
shortlabel "EPG"
; the service-ID consists of 8 hex digits for packet data services. Usually the first two digits will
; be the same as your ECC, and the third digit will be the same as the first digit in your Ensemble Id.
id 0xe1912345
}

In the subchannels section:

sub-epg {
; type packet or enhancedpacket can be used for EPG.
type enhancedpacket
; if you change the bitrate, remember to also change the packet size accordingly (see above) and generate your EPG again.
bitrate 16
protection-profile EEP_A
protection 3
; inputuri is the path and filename for your output file from generate-epg
inputuri "/home/user/odr-radioepg-bridge-master/output.dat"
inputproto file
}

And in the components section:

comp-epg {
type 60
service srv-epg
subchannel sub-epg
figtype 0x7
; The address must be the same as your packet address set when you generate the EPG (default value is 1).
address 0x1
datagroup true
}

That's it. Now (re)start your ODR-DabMux, and your EPG should be broadcasted.

===Updating your EPG automatically every day===

====Feeding the EPG from a fifo to be able to update it without restarting the MUX====

While the setup shown above will allow you to broadcast your EPG, it will not allow you to update your EPG without having to restart your MUX. To get around this, you can feed your EPG to ODR-DabMux from a named fifo instead of a file.

Navigate to the folder where you have your EPG and create a fifo like this:

mkfifo epgfifo

In the subchannel section of your mux.conf, you should replace your EPG file (output.dat) with your fifo, and also add a new line, "nonblock true", so that your EPG subchannel looks like this:

sub-epg {
; type packet or enhancedpacket can be used for EPG.
type enhancedpacket
; if you change the bitrate, remember to also change the packet size accordingly (see above) and generate your EPG again.
bitrate 16
protection-profile EEP_A
protection 3
; inputuri is the path and filename for your output from generate-epg
inputuri "/home/user/odr-radioepg-bridge-master/epgfifo"
inputproto file
nonblock true
}

Your EPG must be continously sent to the fifo. You can make a shell script for that. Create a file, sendepg.sh, with this content:

#!/bin/bash

while :
do

cat /home/user/odr-radioepg-bridge-master/output.dat >> /home/user/odr-radioepg-bridge-master/epgfifo

done

And make it executable (chmod +x sendepg.sh).

This script must be running all the time. If you're already using Supervisor to keep your MUX running (as described here: https://github.com/Opendigitalradio/dab-scripts), it's easy to also use supervisor for this script. Create a new file, sendepg.conf, in your /home/user/odr/config/supervisor folder with this content:

[program:sendepg]
command=bash -c "/home/user/odr-radioepg-bridge-master/sendepg.sh"
autostart=true
autorestart=true
startretries=99999
priority=10
stderr_logfile=/dev/stdout
stdout_logfile=/dev/stdout

Then run these commands:

sudo ln -s /home/user/odr/config/supervisor/sendepg.conf /etc/supervisor/conf.d/sendepg.conf
sudo supervisorctl reread
sudo supervisorctl update

Now your EPG is sent to ODR-DabMux from the fifo, and you will now be able to update your EPG without having to restart ODR-DabMux.

====Updating your EPG automatically every day====

You can update your EPG every 24 hours by adding a new daily task to cron.

Create a new file

/etc/cron.daily/epg

with the single line (with the same parameters as when you generate your EPG yourself)

/usr/local/bin/generate-epg -d 4 -p 48 /home/user/odr/config/mux.conf -o /home/user/odr-radioepg-bridge-master/output.dat

By default, the cron job will run every day at around 06:00. If you want your EPG to update more frequently (every 4 hours), you could add it to the user cron job with

crontab -e

and add the line

0 */4 * * * /usr/local/bin/generate-epg -d 4 -p 48 /home/user/odr/config/mux.conf -o /home/user/odr-radioepg-bridge-master/output.dat

'''NOTE:'''
The EPG creates new MOT TransportIDs for every object each time it is run. A receiver will not recognise that objects have been previously received and cached. If there is an interruption in reception, the EPG will be incomplete. The more frequently you update the EPG, more likely it is that a receiver will not be able to utilise the cached objects.

===Some observations===

* According to specs, logo slides in DAB EPG must be PNG. Although JPG is allowed in hybrid radio SPI, JPG logos will not be added to your DAB EPG. Be sure that your logos (at least those up to 320x240) are PNG.
* Programme descriptions (shortDescription) seem to be processed but not shown. Perhaps we will have to look a little further into this.

How to configure SPI (Service and Programme Information) for ODR-DabMux

2020-07-24T14:51:41Z

Nickpiggott: moved the standard date/time Deb package up to that section

Howto by Ulrik Brinck on odr-radioepg-bridge installation on Debian Jessie. Nick Piggott has contributed with some additions.
===Introduction===

This tool (or rather series of tools) will pick up your SPI (Service and Programme Information) from the internet via RadioDNS and generate a DAB SPI from it. It was written by Ben Poor and Nick Piggott. In this HowTo, I will describe how it can be installed on Debian Jessie. Some details might be slightly different on other Debian generations.

* Confused about EPG and SPI? In this context, EPG and SPI are basically the same thing. While EPG (Electronic Programme Guide) is an old, but commonly well-known term, SPI (Service and Programme Information) is now the official name of this feature.

===Notes===

'''This tool uses RadioDNS to locate and acquire Service Information (SI.xml), Programme Information (PI.xml) and Logos.'''
Each station you want to add to the SPI must be registered in RadioDNS using the correct information (Ensemble ID, Service ID, Service Component ID), and have correctly formatted SI, PI and logo files in PNG format. Find out more at https://radiodns.org/technical/documentation/#howto

I have assumed that you are logged in to your Linux system as a standard user and have sudo installed on your system. If sudo is not installed, you can see here, how to install it on Debian Jessie:
https://www.geek17.com/en/content/debian-8-jessie-install-and-configure-sudo-25

===Installation===

====Step 0: Update your system====
Begin with "sudo apt-get update" to make sure that you can install all that you need.

====Step 1: Miscellaneous dependencies====
First there are some dependencies to install with apt-get:

sudo apt-get install python-crcmod
sudo apt-get install python-bitarray
sudo apt-get install python-isodate

Next there are some dependencies and subcomponents which must be downloaded from github and installed:

====Step 2: python-dabmot====

Download from here https://github.com/Opendigitalradio/python-dabmot and unpack to a folder, e.g. /home/user/python-dabmot-master

Then navigate to the folder and run:
sudo python setup.py install

====Step 3: python-mot-epg====

Download from here https://github.com/Opendigitalradio/python-mot-epg and unpack to a folder, e.g. /home/user/python-mot-epg-master

Then navigate to the folder and run:
sudo python setup.py install

====Step 4: python-msc====

Download from here https://github.com/Opendigitalradio/python-dabmsc and unpack to a folder, e.g. /home/user/python-dabmsc-master

Then navigate to the folder and run:
sudo python setup.py install

====Step 5: pyradiodns====

Download from here https://github.com/radiodns/pyradiodns and unpack to a folder, e.g. /home/user/pyradiodns-master

Then navigate to the folder and run:
sudo python setup.py install

====Step 6: odr-radiodns-bridge====

Download from here https://github.com/Opendigitalradio/odr-radiodns-bridge and unpack to a folder, e.g. /home/user/odr-radiodns-bridge-master

Then navigate to the folder and run:
sudo python setup.py install

====Step 7: python-hybridspi====

Download from here https://github.com/Opendigitalradio/python-hybridspi and unpack to a folder, e.g. /home/user/python-hybridspi-master

Then navigate to the folder and run:
sudo python setup.py install

====Step 8: odr-radioepg-bridge====

And now for the RadioEPG-bridge itself.

Download from here https://github.com/Opendigitalradio/odr-radioepg-bridge and unpack to a folder, e.g. /home/user/odr-radioepg-bridge-master

Then run:
sudo ln -s /home/user/odr-radioepg-bridge-master/generate-epg /usr/local/bin/generate-epg
(If your folder is not /home/user/odr-radioepg-bridge-master, use your_path/generate-epg in the last command line above).

That's it. You should now be able to run this command and see a help text:
generate-epg -h

===Generating and broadcasting your EPG===

====Generating your EPG====

Odr-radioepg-bridge is a command-line tool, which will:
* First read your mux.conf (from your ODR-DabMux configuration) to get information about your services.
* Then try to fetch SPI data for your services from the internet using RadioDNS.
* And lastly generate an output file containing a complete EPG.

If you type "generate-epg -h" you will get a list of available command-line arguments:

usage: generate-epg [-h] [-o OUTPUT] [-X] [-d DAYS] [-p PACKET_SIZE]
[-a PACKET_ADDRESS] [-D]
f

Encodes an SPI bitstream for services in a multiplex configuration file

positional arguments:
f multiplex configuration file

optional arguments:
-h, --help show this help message and exit
-o OUTPUT output bitstream file
-X turn debug on
-d DAYS number of days ahead to encode schedule files
-p PACKET_SIZE Packet size in bytes
-a PACKET_ADDRESS Packet address
-D output Datagroups instead of Packets

The positional argument tells the tool where to find your mux.conf.
The other arguments are optional, and some default values will be used if you don't set them:

* -o can be used to set filename and path to your output file (your EPG). Default is output.dat, placed in the folder from where you run the tool.
* -d is the number of days of programme schedule you want in you EPG. From 1 til 4 days, default is 2.
* -p is packet size. Available values are 24, 48, 72 and 96. Default is 96. Which value you should use, depends on the bitrate in which you are broadcasting your EPG (see below).
* -a is the packet address for your EPG. Default is 1, which will normally be fine. Important is, that you must set the same address in your mux.conf (see below).
* -D will tell the script to output Datagroups instead of Packets. This is useful for some commercial multiplexers or in case you want to broadcast your EPG as X-PAD instead of packet data. Note: You do not need this if you plan to broadcast your EPG the way it's described on this wiki page.

Example:
If your mux.conf is placed in /home/user/odr/config/mux.conf, and you want 4 days in your EPG (today and the next 3 days) and you want to broadcast it in 16 kbit/s, your command line could look like this:

generate-epg -d 4 -p 48 /home/user/odr/config/mux.conf

This will generate a file named output.dat containing your EPG. In this example, I have set the packet size to 48, which is suitable for 16 kbit/s. I have not set the packet address, which means that the default value of 1 will be used.

====Packet sizes and bitrates====

The packet size, which you set when you generate your EPG, should match the bitrate in which you intend to broadcast it. If the packet size is too large, your EPG will not be broadcasted. If the packet size is too small, your EPG will (probably) be broadcasted, but it will be slower than necessary, because more space will be used for packet headers and maybe partly empty data packets. I will recommend these values:

{| class="wikitable"
! Bitrate
! Packet size
|-
| 8
| 24
|-
| 16
| 48
|-
| 24
| 72
|-
| 32
| 96
|-
| 48
| 72
|-
| 64
| 96
|}

====Broadcasting your EPG====

To broadcast your EPG using ODR-DabMux, create a packet data service in your mux.conf like in this example:

In the services section:

srv-epg {
label "EPG"
shortlabel "EPG"
; the service-ID consists of 8 hex digits for packet data services. Usually the first two digits will
; be the same as your ECC, and the third digit will be the same as the first digit in your Ensemble Id.
id 0xe1912345
}

In the subchannels section:

sub-epg {
; type packet or enhancedpacket can be used for EPG.
type enhancedpacket
; if you change the bitrate, remember to also change the packet size accordingly (see above) and generate your EPG again.
bitrate 16
protection-profile EEP_A
protection 3
; inputuri is the path and filename for your output file from generate-epg
inputuri "/home/user/odr-radioepg-bridge-master/output.dat"
inputproto file
}

And in the components section:

comp-epg {
type 60
service srv-epg
subchannel sub-epg
figtype 0x7
; The address must be the same as your packet address set when you generate the EPG (default value is 1).
address 0x1
datagroup true
}

That's it. Now (re)start your ODR-DabMux, and your EPG should be broadcasted.

===Updating your EPG automatically every day===

====Feeding the EPG from a fifo to be able to update it without restarting the MUX====

While the setup shown above will allow you to broadcast your EPG, it will not allow you to update your EPG without having to restart your MUX. To get around this, you can feed your EPG to ODR-DabMux from a named fifo instead of a file.

Navigate to the folder where you have your EPG and create a fifo like this:

mkfifo epgfifo

In the subchannel section of your mux.conf, you should replace your EPG file (output.dat) with your fifo, and also add a new line, "nonblock true", so that your EPG subchannel looks like this:

sub-epg {
; type packet or enhancedpacket can be used for EPG.
type enhancedpacket
; if you change the bitrate, remember to also change the packet size accordingly (see above) and generate your EPG again.
bitrate 16
protection-profile EEP_A
protection 3
; inputuri is the path and filename for your output from generate-epg
inputuri "/home/user/odr-radioepg-bridge-master/epgfifo"
inputproto file
nonblock true
}

Your EPG must be continously sent to the fifo. You can make a shell script for that. Create a file, sendepg.sh, with this content:

#!/bin/bash

while :
do

cat /home/user/odr-radioepg-bridge-master/output.dat >> /home/user/odr-radioepg-bridge-master/epgfifo

done

And make it executable (chmod +x sendepg.sh).

This script must be running all the time. If you're already using Supervisor to keep your MUX running (as described here: https://github.com/Opendigitalradio/dab-scripts), it's easy to also use supervisor for this script. Create a new file, sendepg.conf, in your /home/user/odr/config/supervisor folder with this content:

[program:sendepg]
command=bash -c "/home/user/odr-radioepg-bridge-master/sendepg.sh"
autostart=true
autorestart=true
startretries=99999
priority=10
stderr_logfile=/dev/stdout
stdout_logfile=/dev/stdout

Then run these commands:

sudo ln -s /home/user/odr/config/supervisor/sendepg.conf /etc/supervisor/conf.d/sendepg.conf
sudo supervisorctl reread
sudo supervisorctl update

Now your EPG is sent to ODR-DabMux from the fifo, and you will now be able to update your EPG without having to restart ODR-DabMux.

====Updating your EPG automatically every day====

You can update your EPG every 24 hours by adding a new daily task to cron.

Create a new file

/etc/cron.daily/epg

with the single line (with the same parameters as when you generate your EPG yourself)

/usr/local/bin/generate-epg -d 4 -p 48 /home/user/odr/config/mux.conf -o /home/user/odr-radioepg-bridge-master/output.dat

By default, the cron job will run every day at around 06:00. If you want your EPG to update more frequently (every 4 hours), you could add it to the user cron job with

crontab -e

and add the line

0 */4 * * * /usr/local/bin/generate-epg -d 4 -p 48 /home/user/odr/config/mux.conf -o /home/user/odr-radioepg-bridge-master/output.dat

'''NOTE:'''
The EPG creates new MOT TransportIDs for every object each time it is run. A receiver will not recognise that objects have been previously received and cached. If there is an interruption in reception, the EPG will be incomplete. The more frequently you update the EPG, more likely it is that a receiver will not be able to utilise the cached objects.

===Some observations===

* According to specs, logo slides in DAB EPG must be PNG. Although JPG is allowed in hybrid radio SPI, JPG logos will not be added to your DAB EPG. Be sure that your logos (at least those up to 320x240) are PNG.
* Programme descriptions (shortDescription) seem to be processed but not shown. Perhaps we will have to look a little further into this.

How to configure SPI (Service and Programme Information) for ODR-DabMux

2020-07-24T14:50:59Z

Nickpiggott: /* Notes */

Howto by Ulrik Brinck on odr-radioepg-bridge installation on Debian Jessie. Nick Piggott has contributed with some additions.
===Introduction===

This tool (or rather series of tools) will pick up your SPI (Service and Programme Information) from the internet via RadioDNS and generate a DAB SPI from it. It was written by Ben Poor and Nick Piggott. In this HowTo, I will describe how it can be installed on Debian Jessie. Some details might be slightly different on other Debian generations.

* Confused about EPG and SPI? In this context, EPG and SPI are basically the same thing. While EPG (Electronic Programme Guide) is an old, but commonly well-known term, SPI (Service and Programme Information) is now the official name of this feature.

===Notes===

'''This tool uses RadioDNS to locate and acquire Service Information (SI.xml), Programme Information (PI.xml) and Logos.'''
Each station you want to add to the SPI must be registered in RadioDNS using the correct information (Ensemble ID, Service ID, Service Component ID), and have correctly formatted SI, PI and logo files in PNG format. Find out more at https://radiodns.org/technical/documentation/#howto

I have assumed that you are logged in to your Linux system as a standard user and have sudo installed on your system. If sudo is not installed, you can see here, how to install it on Debian Jessie:
https://www.geek17.com/en/content/debian-8-jessie-install-and-configure-sudo-25

===Installation===

====Step 0: Update your system====
Begin with "sudo apt-get update" to make sure that you can install all that you need.

====Step 1: Miscellaneous dependencies====
First there are some dependencies to install with apt-get:

sudo apt-get install python-crcmod
sudo apt-get install python-bitarray
sudo apt-get install python-isodate

Next there are some dependencies and subcomponents which must be downloaded from github and installed:

====Step 2: python-dabmot====

Download from here https://github.com/Opendigitalradio/python-dabmot and unpack to a folder, e.g. /home/user/python-dabmot-master

Then navigate to the folder and run:
sudo python setup.py install

====Step 3: python-mot-epg====

Download from here https://github.com/Opendigitalradio/python-mot-epg and unpack to a folder, e.g. /home/user/python-mot-epg-master

Then navigate to the folder and run:
sudo python setup.py install

====Step 4: python-msc====

Download from here https://github.com/Opendigitalradio/python-dabmsc and unpack to a folder, e.g. /home/user/python-dabmsc-master

Then navigate to the folder and run:
sudo apt-get install python-dateutil
sudo python setup.py install

====Step 5: pyradiodns====

Download from here https://github.com/radiodns/pyradiodns and unpack to a folder, e.g. /home/user/pyradiodns-master

Then navigate to the folder and run:
sudo python setup.py install

====Step 6: odr-radiodns-bridge====

Download from here https://github.com/Opendigitalradio/odr-radiodns-bridge and unpack to a folder, e.g. /home/user/odr-radiodns-bridge-master

Then navigate to the folder and run:
sudo python setup.py install

====Step 7: python-hybridspi====

Download from here https://github.com/Opendigitalradio/python-hybridspi and unpack to a folder, e.g. /home/user/python-hybridspi-master

Then navigate to the folder and run:
sudo python setup.py install

====Step 8: odr-radioepg-bridge====

And now for the RadioEPG-bridge itself.

Download from here https://github.com/Opendigitalradio/odr-radioepg-bridge and unpack to a folder, e.g. /home/user/odr-radioepg-bridge-master

Then run:
sudo ln -s /home/user/odr-radioepg-bridge-master/generate-epg /usr/local/bin/generate-epg
(If your folder is not /home/user/odr-radioepg-bridge-master, use your_path/generate-epg in the last command line above).

That's it. You should now be able to run this command and see a help text:
generate-epg -h

===Generating and broadcasting your EPG===

====Generating your EPG====

Odr-radioepg-bridge is a command-line tool, which will:
* First read your mux.conf (from your ODR-DabMux configuration) to get information about your services.
* Then try to fetch SPI data for your services from the internet using RadioDNS.
* And lastly generate an output file containing a complete EPG.

If you type "generate-epg -h" you will get a list of available command-line arguments:

usage: generate-epg [-h] [-o OUTPUT] [-X] [-d DAYS] [-p PACKET_SIZE]
[-a PACKET_ADDRESS] [-D]
f

Encodes an SPI bitstream for services in a multiplex configuration file

positional arguments:
f multiplex configuration file

optional arguments:
-h, --help show this help message and exit
-o OUTPUT output bitstream file
-X turn debug on
-d DAYS number of days ahead to encode schedule files
-p PACKET_SIZE Packet size in bytes
-a PACKET_ADDRESS Packet address
-D output Datagroups instead of Packets

The positional argument tells the tool where to find your mux.conf.
The other arguments are optional, and some default values will be used if you don't set them:

* -o can be used to set filename and path to your output file (your EPG). Default is output.dat, placed in the folder from where you run the tool.
* -d is the number of days of programme schedule you want in you EPG. From 1 til 4 days, default is 2.
* -p is packet size. Available values are 24, 48, 72 and 96. Default is 96. Which value you should use, depends on the bitrate in which you are broadcasting your EPG (see below).
* -a is the packet address for your EPG. Default is 1, which will normally be fine. Important is, that you must set the same address in your mux.conf (see below).
* -D will tell the script to output Datagroups instead of Packets. This is useful for some commercial multiplexers or in case you want to broadcast your EPG as X-PAD instead of packet data. Note: You do not need this if you plan to broadcast your EPG the way it's described on this wiki page.

Example:
If your mux.conf is placed in /home/user/odr/config/mux.conf, and you want 4 days in your EPG (today and the next 3 days) and you want to broadcast it in 16 kbit/s, your command line could look like this:

generate-epg -d 4 -p 48 /home/user/odr/config/mux.conf

This will generate a file named output.dat containing your EPG. In this example, I have set the packet size to 48, which is suitable for 16 kbit/s. I have not set the packet address, which means that the default value of 1 will be used.

====Packet sizes and bitrates====

The packet size, which you set when you generate your EPG, should match the bitrate in which you intend to broadcast it. If the packet size is too large, your EPG will not be broadcasted. If the packet size is too small, your EPG will (probably) be broadcasted, but it will be slower than necessary, because more space will be used for packet headers and maybe partly empty data packets. I will recommend these values:

{| class="wikitable"
! Bitrate
! Packet size
|-
| 8
| 24
|-
| 16
| 48
|-
| 24
| 72
|-
| 32
| 96
|-
| 48
| 72
|-
| 64
| 96
|}

====Broadcasting your EPG====

To broadcast your EPG using ODR-DabMux, create a packet data service in your mux.conf like in this example:

In the services section:

srv-epg {
label "EPG"
shortlabel "EPG"
; the service-ID consists of 8 hex digits for packet data services. Usually the first two digits will
; be the same as your ECC, and the third digit will be the same as the first digit in your Ensemble Id.
id 0xe1912345
}

In the subchannels section:

sub-epg {
; type packet or enhancedpacket can be used for EPG.
type enhancedpacket
; if you change the bitrate, remember to also change the packet size accordingly (see above) and generate your EPG again.
bitrate 16
protection-profile EEP_A
protection 3
; inputuri is the path and filename for your output file from generate-epg
inputuri "/home/user/odr-radioepg-bridge-master/output.dat"
inputproto file
}

And in the components section:

comp-epg {
type 60
service srv-epg
subchannel sub-epg
figtype 0x7
; The address must be the same as your packet address set when you generate the EPG (default value is 1).
address 0x1
datagroup true
}

That's it. Now (re)start your ODR-DabMux, and your EPG should be broadcasted.

===Updating your EPG automatically every day===

====Feeding the EPG from a fifo to be able to update it without restarting the MUX====

While the setup shown above will allow you to broadcast your EPG, it will not allow you to update your EPG without having to restart your MUX. To get around this, you can feed your EPG to ODR-DabMux from a named fifo instead of a file.

Navigate to the folder where you have your EPG and create a fifo like this:

mkfifo epgfifo

In the subchannel section of your mux.conf, you should replace your EPG file (output.dat) with your fifo, and also add a new line, "nonblock true", so that your EPG subchannel looks like this:

sub-epg {
; type packet or enhancedpacket can be used for EPG.
type enhancedpacket
; if you change the bitrate, remember to also change the packet size accordingly (see above) and generate your EPG again.
bitrate 16
protection-profile EEP_A
protection 3
; inputuri is the path and filename for your output from generate-epg
inputuri "/home/user/odr-radioepg-bridge-master/epgfifo"
inputproto file
nonblock true
}

Your EPG must be continously sent to the fifo. You can make a shell script for that. Create a file, sendepg.sh, with this content:

#!/bin/bash

while :
do

cat /home/user/odr-radioepg-bridge-master/output.dat >> /home/user/odr-radioepg-bridge-master/epgfifo

done

And make it executable (chmod +x sendepg.sh).

This script must be running all the time. If you're already using Supervisor to keep your MUX running (as described here: https://github.com/Opendigitalradio/dab-scripts), it's easy to also use supervisor for this script. Create a new file, sendepg.conf, in your /home/user/odr/config/supervisor folder with this content:

[program:sendepg]
command=bash -c "/home/user/odr-radioepg-bridge-master/sendepg.sh"
autostart=true
autorestart=true
startretries=99999
priority=10
stderr_logfile=/dev/stdout
stdout_logfile=/dev/stdout

Then run these commands:

sudo ln -s /home/user/odr/config/supervisor/sendepg.conf /etc/supervisor/conf.d/sendepg.conf
sudo supervisorctl reread
sudo supervisorctl update

Now your EPG is sent to ODR-DabMux from the fifo, and you will now be able to update your EPG without having to restart ODR-DabMux.

====Updating your EPG automatically every day====

You can update your EPG every 24 hours by adding a new daily task to cron.

Create a new file

/etc/cron.daily/epg

with the single line (with the same parameters as when you generate your EPG yourself)

/usr/local/bin/generate-epg -d 4 -p 48 /home/user/odr/config/mux.conf -o /home/user/odr-radioepg-bridge-master/output.dat

By default, the cron job will run every day at around 06:00. If you want your EPG to update more frequently (every 4 hours), you could add it to the user cron job with

crontab -e

and add the line

0 */4 * * * /usr/local/bin/generate-epg -d 4 -p 48 /home/user/odr/config/mux.conf -o /home/user/odr-radioepg-bridge-master/output.dat

'''NOTE:'''
The EPG creates new MOT TransportIDs for every object each time it is run. A receiver will not recognise that objects have been previously received and cached. If there is an interruption in reception, the EPG will be incomplete. The more frequently you update the EPG, more likely it is that a receiver will not be able to utilise the cached objects.

===Some observations===

* According to specs, logo slides in DAB EPG must be PNG. Although JPG is allowed in hybrid radio SPI, JPG logos will not be added to your DAB EPG. Be sure that your logos (at least those up to 320x240) are PNG.
* Programme descriptions (shortDescription) seem to be processed but not shown. Perhaps we will have to look a little further into this.

How to configure SPI (Service and Programme Information) for ODR-DabMux

2020-07-24T14:50:48Z

Nickpiggott: /* Introduction */

Howto by Ulrik Brinck on odr-radioepg-bridge installation on Debian Jessie. Nick Piggott has contributed with some additions.
===Introduction===

This tool (or rather series of tools) will pick up your SPI (Service and Programme Information) from the internet via RadioDNS and generate a DAB SPI from it. It was written by Ben Poor and Nick Piggott. In this HowTo, I will describe how it can be installed on Debian Jessie. Some details might be slightly different on other Debian generations.

* Confused about EPG and SPI? In this context, EPG and SPI are basically the same thing. While EPG (Electronic Programme Guide) is an old, but commonly well-known term, SPI (Service and Programme Information) is now the official name of this feature.

===Notes===

'''This tool uses RadioDNS to locate and acquire Service Information (SI.xml), Programme Information (PI.xml) and Logos.'''
Each station you want to add to the EPG must be registered in RadioDNS using the correct information (Ensemble ID, Service ID, Service Component ID), and have correctly formatted SI, PI and logo files in PNG format. Find out more at https://radiodns.org/technical/documentation/#howto

I have assumed that you are logged in to your Linux system as a standard user and have sudo installed on your system. If sudo is not installed, you can see here, how to install it on Debian Jessie:
https://www.geek17.com/en/content/debian-8-jessie-install-and-configure-sudo-25

===Installation===

====Step 0: Update your system====
Begin with "sudo apt-get update" to make sure that you can install all that you need.

====Step 1: Miscellaneous dependencies====
First there are some dependencies to install with apt-get:

sudo apt-get install python-crcmod
sudo apt-get install python-bitarray
sudo apt-get install python-isodate

Next there are some dependencies and subcomponents which must be downloaded from github and installed:

====Step 2: python-dabmot====

Download from here https://github.com/Opendigitalradio/python-dabmot and unpack to a folder, e.g. /home/user/python-dabmot-master

Then navigate to the folder and run:
sudo python setup.py install

====Step 3: python-mot-epg====

Download from here https://github.com/Opendigitalradio/python-mot-epg and unpack to a folder, e.g. /home/user/python-mot-epg-master

Then navigate to the folder and run:
sudo python setup.py install

====Step 4: python-msc====

Download from here https://github.com/Opendigitalradio/python-dabmsc and unpack to a folder, e.g. /home/user/python-dabmsc-master

Then navigate to the folder and run:
sudo apt-get install python-dateutil
sudo python setup.py install

====Step 5: pyradiodns====

Download from here https://github.com/radiodns/pyradiodns and unpack to a folder, e.g. /home/user/pyradiodns-master

Then navigate to the folder and run:
sudo python setup.py install

====Step 6: odr-radiodns-bridge====

Download from here https://github.com/Opendigitalradio/odr-radiodns-bridge and unpack to a folder, e.g. /home/user/odr-radiodns-bridge-master

Then navigate to the folder and run:
sudo python setup.py install

====Step 7: python-hybridspi====

Download from here https://github.com/Opendigitalradio/python-hybridspi and unpack to a folder, e.g. /home/user/python-hybridspi-master

Then navigate to the folder and run:
sudo python setup.py install

====Step 8: odr-radioepg-bridge====

And now for the RadioEPG-bridge itself.

Download from here https://github.com/Opendigitalradio/odr-radioepg-bridge and unpack to a folder, e.g. /home/user/odr-radioepg-bridge-master

Then run:
sudo ln -s /home/user/odr-radioepg-bridge-master/generate-epg /usr/local/bin/generate-epg
(If your folder is not /home/user/odr-radioepg-bridge-master, use your_path/generate-epg in the last command line above).

That's it. You should now be able to run this command and see a help text:
generate-epg -h

===Generating and broadcasting your EPG===

====Generating your EPG====

Odr-radioepg-bridge is a command-line tool, which will:
* First read your mux.conf (from your ODR-DabMux configuration) to get information about your services.
* Then try to fetch SPI data for your services from the internet using RadioDNS.
* And lastly generate an output file containing a complete EPG.

If you type "generate-epg -h" you will get a list of available command-line arguments:

usage: generate-epg [-h] [-o OUTPUT] [-X] [-d DAYS] [-p PACKET_SIZE]
[-a PACKET_ADDRESS] [-D]
f

Encodes an SPI bitstream for services in a multiplex configuration file

positional arguments:
f multiplex configuration file

optional arguments:
-h, --help show this help message and exit
-o OUTPUT output bitstream file
-X turn debug on
-d DAYS number of days ahead to encode schedule files
-p PACKET_SIZE Packet size in bytes
-a PACKET_ADDRESS Packet address
-D output Datagroups instead of Packets

The positional argument tells the tool where to find your mux.conf.
The other arguments are optional, and some default values will be used if you don't set them:

* -o can be used to set filename and path to your output file (your EPG). Default is output.dat, placed in the folder from where you run the tool.
* -d is the number of days of programme schedule you want in you EPG. From 1 til 4 days, default is 2.
* -p is packet size. Available values are 24, 48, 72 and 96. Default is 96. Which value you should use, depends on the bitrate in which you are broadcasting your EPG (see below).
* -a is the packet address for your EPG. Default is 1, which will normally be fine. Important is, that you must set the same address in your mux.conf (see below).
* -D will tell the script to output Datagroups instead of Packets. This is useful for some commercial multiplexers or in case you want to broadcast your EPG as X-PAD instead of packet data. Note: You do not need this if you plan to broadcast your EPG the way it's described on this wiki page.

Example:
If your mux.conf is placed in /home/user/odr/config/mux.conf, and you want 4 days in your EPG (today and the next 3 days) and you want to broadcast it in 16 kbit/s, your command line could look like this:

generate-epg -d 4 -p 48 /home/user/odr/config/mux.conf

This will generate a file named output.dat containing your EPG. In this example, I have set the packet size to 48, which is suitable for 16 kbit/s. I have not set the packet address, which means that the default value of 1 will be used.

====Packet sizes and bitrates====

The packet size, which you set when you generate your EPG, should match the bitrate in which you intend to broadcast it. If the packet size is too large, your EPG will not be broadcasted. If the packet size is too small, your EPG will (probably) be broadcasted, but it will be slower than necessary, because more space will be used for packet headers and maybe partly empty data packets. I will recommend these values:

{| class="wikitable"
! Bitrate
! Packet size
|-
| 8
| 24
|-
| 16
| 48
|-
| 24
| 72
|-
| 32
| 96
|-
| 48
| 72
|-
| 64
| 96
|}

====Broadcasting your EPG====

To broadcast your EPG using ODR-DabMux, create a packet data service in your mux.conf like in this example:

In the services section:

srv-epg {
label "EPG"
shortlabel "EPG"
; the service-ID consists of 8 hex digits for packet data services. Usually the first two digits will
; be the same as your ECC, and the third digit will be the same as the first digit in your Ensemble Id.
id 0xe1912345
}

In the subchannels section:

sub-epg {
; type packet or enhancedpacket can be used for EPG.
type enhancedpacket
; if you change the bitrate, remember to also change the packet size accordingly (see above) and generate your EPG again.
bitrate 16
protection-profile EEP_A
protection 3
; inputuri is the path and filename for your output file from generate-epg
inputuri "/home/user/odr-radioepg-bridge-master/output.dat"
inputproto file
}

And in the components section:

comp-epg {
type 60
service srv-epg
subchannel sub-epg
figtype 0x7
; The address must be the same as your packet address set when you generate the EPG (default value is 1).
address 0x1
datagroup true
}

That's it. Now (re)start your ODR-DabMux, and your EPG should be broadcasted.

===Updating your EPG automatically every day===

====Feeding the EPG from a fifo to be able to update it without restarting the MUX====

While the setup shown above will allow you to broadcast your EPG, it will not allow you to update your EPG without having to restart your MUX. To get around this, you can feed your EPG to ODR-DabMux from a named fifo instead of a file.

Navigate to the folder where you have your EPG and create a fifo like this:

mkfifo epgfifo

In the subchannel section of your mux.conf, you should replace your EPG file (output.dat) with your fifo, and also add a new line, "nonblock true", so that your EPG subchannel looks like this:

sub-epg {
; type packet or enhancedpacket can be used for EPG.
type enhancedpacket
; if you change the bitrate, remember to also change the packet size accordingly (see above) and generate your EPG again.
bitrate 16
protection-profile EEP_A
protection 3
; inputuri is the path and filename for your output from generate-epg
inputuri "/home/user/odr-radioepg-bridge-master/epgfifo"
inputproto file
nonblock true
}

Your EPG must be continously sent to the fifo. You can make a shell script for that. Create a file, sendepg.sh, with this content:

#!/bin/bash

while :
do

cat /home/user/odr-radioepg-bridge-master/output.dat >> /home/user/odr-radioepg-bridge-master/epgfifo

done

And make it executable (chmod +x sendepg.sh).

This script must be running all the time. If you're already using Supervisor to keep your MUX running (as described here: https://github.com/Opendigitalradio/dab-scripts), it's easy to also use supervisor for this script. Create a new file, sendepg.conf, in your /home/user/odr/config/supervisor folder with this content:

[program:sendepg]
command=bash -c "/home/user/odr-radioepg-bridge-master/sendepg.sh"
autostart=true
autorestart=true
startretries=99999
priority=10
stderr_logfile=/dev/stdout
stdout_logfile=/dev/stdout

Then run these commands:

sudo ln -s /home/user/odr/config/supervisor/sendepg.conf /etc/supervisor/conf.d/sendepg.conf
sudo supervisorctl reread
sudo supervisorctl update

Now your EPG is sent to ODR-DabMux from the fifo, and you will now be able to update your EPG without having to restart ODR-DabMux.

====Updating your EPG automatically every day====

You can update your EPG every 24 hours by adding a new daily task to cron.

Create a new file

/etc/cron.daily/epg

with the single line (with the same parameters as when you generate your EPG yourself)

/usr/local/bin/generate-epg -d 4 -p 48 /home/user/odr/config/mux.conf -o /home/user/odr-radioepg-bridge-master/output.dat

By default, the cron job will run every day at around 06:00. If you want your EPG to update more frequently (every 4 hours), you could add it to the user cron job with

crontab -e

and add the line

0 */4 * * * /usr/local/bin/generate-epg -d 4 -p 48 /home/user/odr/config/mux.conf -o /home/user/odr-radioepg-bridge-master/output.dat

'''NOTE:'''
The EPG creates new MOT TransportIDs for every object each time it is run. A receiver will not recognise that objects have been previously received and cached. If there is an interruption in reception, the EPG will be incomplete. The more frequently you update the EPG, more likely it is that a receiver will not be able to utilise the cached objects.

===Some observations===

* According to specs, logo slides in DAB EPG must be PNG. Although JPG is allowed in hybrid radio SPI, JPG logos will not be added to your DAB EPG. Be sure that your logos (at least those up to 320x240) are PNG.
* Programme descriptions (shortDescription) seem to be processed but not shown. Perhaps we will have to look a little further into this.

How to configure SPI (Service and Programme Information) for ODR-DabMux

2020-07-14T16:31:51Z

Nickpiggott: /* Updating your EPG automatically every day */

Howto by Ulrik Brinck on odr-radioepg-bridge installation on Debian Jessie
===Introduction===

This tool (or rather series of tools) will pick up your SPI (Service and Programme Information) from the internet via RadioDNS and generate a DAB EPG from it. It was written by Ben Poor and Nick Piggott. In this HowTo, I will describe how it can be installed on Debian Jessie. Some details might be slightly different on other Debian generations.

* In this context, EPG and SPI is basically the same thing. While EPG (Electronic Programme Guide) is an old, but commonly well-known term, SPI (Service and Programme Information) is now the official name of this feature.

===Notes===

'''This tool uses RadioDNS to locate and acquire Service Information (SI.xml), Programme Information (PI.xml) and Logos.'''
Each station you want to add to the EPG must be registered in RadioDNS using the correct information (Ensemble ID, Service ID, Service Component ID), and have correctly formatted SI, PI and logo files in PNG format. Find out more at https://radiodns.org/technical/documentation/#howto

I have assumed that you are logged in to your Linux system as a standard user and have sudo installed on your system. If sudo is not installed, you can see here, how to install it on Debian Jessie:
https://www.geek17.com/en/content/debian-8-jessie-install-and-configure-sudo-25

===Installation===

====Step 0: Update your system====
Begin with "sudo apt-get update" to make sure that you can install all that you need.

====Step 1: Miscellaneous dependencies====
First there are some dependencies to install with apt-get:

sudo apt-get install python-crcmod
sudo apt-get install python-bitarray
sudo apt-get install python-isodate

Next there are some dependencies and subcomponents which must be downloaded from github and installed:

====Step 2: python-dabmot====

Download from here https://github.com/GlobalRadio/python-dabmot and unpack to a folder, e.g. /home/user/python-dabmot-master

Then navigate to the folder and run:
sudo python setup.py install

====Step 3: python-mot-epg====

Download from here https://github.com/GlobalRadio/python-mot-epg and unpack to a folder, e.g. /home/user/python-mot-epg-master

Then navigate to the folder and run:
sudo python setup.py install

====Step 4: python-msc====

Download from here https://github.com/nickpiggott/python-dabmsc and unpack to a folder, e.g. /home/user/python-dabmsc-master

Important: '''It MUST be this commit''', NOT the original one from GlobalRadio from 2017 (thanks to Nick Piggott for help figuring out this).

Then navigate to the folder and run:
sudo apt-get install python-dateutil
sudo python setup.py install

====Step 5: odr-radiodns-bridge====

Download from here https://github.com/nickpiggott/odr-radiodns-bridge and unpack to a folder, e.g. /home/user/odr-radiodns-bridge-master

Then navigate to the folder and run:
sudo apt-get install python-pip
sudo pip install hybridspi
sudo pip install pyradiodns
sudo python setup.py install

====Step 6: python-hybridspi====

Download from here https://github.com/magicbadger/python-hybridspi and unpack to a folder, e.g. /home/user/python-hybridspi-master

Then navigate to the folder and run:
sudo python setup.py install

====Step 7: odr-radioepg-bridge====

And now for the RadioEPG-bridge itself.

Download from here https://github.com/nickpiggott/odr-radioepg-bridge and unpack to a folder, e.g. /home/user/odr-radioepg-bridge-master

Then run:
sudo ln -s /home/user/odr-radioepg-bridge-master/generate-epg /usr/local/bin/generate-epg
(If your folder is not /home/user/odr-radioepg-bridge-master, use your_path/generate-epg in the last command line above).

That's it. You should now be able to run this command and see a help text:
generate-epg -h

===Generating and broadcasting your EPG===

====Generating your EPG====

Odr-radioepg-bridge is a command-line tool, which will:
* First read your mux.conf (from your ODR-DabMux configuration) to get information about your services.
* Then try to fetch SPI data for your services from the internet using RadioDNS.
* And lastly generate an output file containing a complete EPG.

If you type "generate-epg -h" you will get a list of available command-line arguments:

usage: generate-epg [-h] [-o OUTPUT] [-X] [-d DAYS] [-p PACKET_SIZE]
[-a PACKET_ADDRESS]
f

Encodes an EPG bitstream for services in a multiplex configuration file

positional arguments:
f multiplex configuration file

optional arguments:
-h, --help show this help message and exit
-o OUTPUT output bitstream file
-X turn debug on
-d DAYS number of days ahead to encode schedule files
-p PACKET_SIZE Packet size in bytes
-a PACKET_ADDRESS Packet address

The positional argument tells the tool where to find your mux.conf.
The other arguments are optional, and some default values will be used if you don't set them:

* -o can be used to set filename and path to your output file (your EPG). Default is output.dat, placed in the folder from where you run the tool.
* -d is the number of days of programme schedule you want in you EPG. From 1 til 4 days, default is 2.
* -p is packet size. Available values are 24, 48, 72 and 96. Default is 96. Which value you should use, depends on the bitrate in which you are broadcasting your EPG (see below).
* -a is the packet address for your EPG. Default is 1, which will normally be fine. Important is, that you must set the same address in your mux.conf (see below).

Example:
If your mux.conf is placed in /home/user/odr/config/mux.conf, and you want 4 days in your EPG (today and the next 3 days) and you want to broadcast it in 16 kbit/s, your command line could look like this:

generate-epg -d 4 -p 48 /home/user/odr/config/mux.conf

This will generate a file named output.dat containing your EPG. In this example, I have set the packet size to 48, which is suitable for 16 kbit/s. I have not set the packet address, which means that the default value of 1 will be used.

====Packet sizes and bitrates====

The packet size, which you set when you generate your EPG, should match the bitrate in which you intend to broadcast it. If the packet size is too large, your EPG will not be broadcasted. If the packet size is too small, your EPG will (probably) be broadcasted, but it will be slower than necessary, because more space will be used for packet headers and maybe partly empty data packets. I will recommend these values:

{| class="wikitable"
! Bitrate
! Packet size
|-
| 8
| 24
|-
| 16
| 48
|-
| 24
| 72
|-
| 32
| 96
|-
| 48
| 72
|-
| 64
| 96
|}

====Broadcasting your EPG====

To broadcast your EPG using ODR-DabMux, create a packet data service in your mux.conf like in this example:

In the services section:

srv-epg {
label "EPG"
shortlabel "EPG"
; the service-ID consists of 8 hex digits for packet data services. Usually the first two digits will
; be the same as your ECC, and the third digit will be the same as the first digit in your Ensemble Id.
id 0xe1912345
}

In the subchannels section:

sub-epg {
; type packet or enhancedpacket can be used for EPG.
type enhancedpacket
; if you change the bitrate, remember to also change the packet size accordingly (see above) and generate your EPG again.
bitrate 16
protection-profile EEP_A
protection 3
; inputuri is the path and filename for your output file from generate-epg
inputuri "/home/user/odr-radioepg-bridge-master/output.dat"
inputproto file
}

And in the components section:

comp-epg {
type 60
service srv-epg
subchannel sub-epg
figtype 0x7
; The address must be the same as your packet address set when you generate the EPG (default value is 1).
address 0x1
datagroup true
}

That's it. Now (re)start your ODR-DabMux, and your EPG should be broadcasted.

===Updating your EPG automatically every day===

You can update your EPG every 24 hours by adding a new daily task to cron.

Assuming you have a ~/odr/epg folder, create a new file

/etc/cron.daily/epg

with the single line

/usr/local/bin/generate-epg -d 4 -p 48 /home/user/odr/config/mux.conf -o /home/user/odr/epg/epg_data.dat

In your mux.conf you would use the lines

inputuri "/home/user/odr/epg/epg_data.dat"
inputproto file

to tell odr-dabmux where to read the EPG packet data from.

By default, the cron job will run every day at around 06:00. If you want your EPG to update more frequently (every 4 hours), you could add it to the user cron job with

crontab -e

and add the line

0 */4 * * * /usr/local/bin/generate-epg -d 4 -p 48 /home/user/odr/config/mux.conf -o /home/user/odr/epg/epg_data.dat

'''NOTE:'''
The EPG creates new MOT TransportIDs for every object each time it is run. A receiver will not recognise that objects have been previously received and cached. If there is an interruption in reception, the EPG will be incomplete. The more frequently you update the EPG, more likely it is that a receiver will not be able to utilise the cached objects.

===Some problems and solutions===

====Local variable 'ecc' referenced before assignment====

For some domains, lookup will cause the script to fail with error message "local variable 'ecc' referenced before assignment" if the domain has no _radiotag._tcp SRV record.

You can get around this by opening this file in a text editor:
/usr/local/lib/python2.7/dist-packages/pyradiodns/rdns.py
and remove or comment out line 13 "('radiotag', 'TCP'),".

If the domain is not using RadioVIS, you might also have to remove line 14 "('radiovis', 'TCP'),", but I haven't experienced this myself.

Note: When you modify this file, you might have to remove '''rdns.pyc''' in the same folder to make sure that your changes are being used.

====Radio programmes listed on a wrong date====

I have observed that radio programmes beginning before noon (or all programmes on some receivers) were listed on a wrong date, one day before the correct date. My solution was to modify line 428 in this file:

/usr/local/lib/python2.7/dist-packages/spi/binary/__init__py

Here, "(timepoint.hour - 12)" should be changed to "timepoint.hour", so that line 428 will be:

jd = jdn + timepoint.hour / 24 + timepoint.minute / 1440 + timepoint.second / 86400

This should fix the daystamp issue.

Note: When you modify this file, you might have to remove '''__init__.pyc''' in the same folder to make sure that your changes are being used.

====Radio programmes listed with wrong timestamps if your time zone is not UTC====

I have observed that if the time zone is not UTC, all radio programmes were listed with wrong times. My solution was to make some modifications to this file:
/usr/local/lib/python2.7/dist-packages/spi/binary/__init__py

After line 419 ("bits.setall(False)") I have added the following two lines:

offset = (timepoint.utcoffset().days * 86400 + timepoint.utcoffset().seconds) + (timepoint.dst().days * 86400 + timepoint.dst().days)
timepoint=timepoint - timedelta(seconds=offset)

(The first line is taken from line 457, from where it can then be removed)

And after line 28 ("import sys"), I have added this line:

from datetime import timedelta

This should fix the timestamp issue.

Note: When you modify this file, you might have to remove '''__init__.pyc''' in the same folder to make sure that your changes are being used.

===Other observations===

* According to specs, logo slides in DAB EPG must be PNG. Although JPG is allowed in hybrid radio SPI, JPG logos will not be added to your DAB EPG. Be sure that your logos (up to 320x240) are PNG.
* Programme descriptions (shortDescription) seem to be processed but not shown. Perhaps we will have to look a little further into this.

How to configure SPI (Service and Programme Information) for ODR-DabMux

2020-07-14T16:22:49Z

Nickpiggott: Explain how to run a daily cron job.

Howto by Ulrik Brinck on odr-radioepg-bridge installation on Debian Jessie
===Introduction===

This tool (or rather series of tools) will pick up your SPI (Service and Programme Information) from the internet via RadioDNS and generate a DAB EPG from it. It was written by Ben Poor and Nick Piggott. In this HowTo, I will describe how it can be installed on Debian Jessie. Some details might be slightly different on other Debian generations.

* In this context, EPG and SPI is basically the same thing. While EPG (Electronic Programme Guide) is an old, but commonly well-known term, SPI (Service and Programme Information) is now the official name of this feature.

===Notes===

'''This tool uses RadioDNS to locate and acquire Service Information (SI.xml), Programme Information (PI.xml) and Logos.'''
Each station you want to add to the EPG must be registered in RadioDNS using the correct information (Ensemble ID, Service ID, Service Component ID), and have correctly formatted SI, PI and logo files in PNG format. Find out more at https://radiodns.org/technical/documentation/#howto

I have assumed that you are logged in to your Linux system as a standard user and have sudo installed on your system. If sudo is not installed, you can see here, how to install it on Debian Jessie:
https://www.geek17.com/en/content/debian-8-jessie-install-and-configure-sudo-25

===Installation===

====Step 0: Update your system====
Begin with "sudo apt-get update" to make sure that you can install all that you need.

====Step 1: Miscellaneous dependencies====
First there are some dependencies to install with apt-get:

sudo apt-get install python-crcmod
sudo apt-get install python-bitarray
sudo apt-get install python-isodate

Next there are some dependencies and subcomponents which must be downloaded from github and installed:

====Step 2: python-dabmot====

Download from here https://github.com/GlobalRadio/python-dabmot and unpack to a folder, e.g. /home/user/python-dabmot-master

Then navigate to the folder and run:
sudo python setup.py install

====Step 3: python-mot-epg====

Download from here https://github.com/GlobalRadio/python-mot-epg and unpack to a folder, e.g. /home/user/python-mot-epg-master

Then navigate to the folder and run:
sudo python setup.py install

====Step 4: python-msc====

Download from here https://github.com/nickpiggott/python-dabmsc and unpack to a folder, e.g. /home/user/python-dabmsc-master

Important: '''It MUST be this commit''', NOT the original one from GlobalRadio from 2017 (thanks to Nick Piggott for help figuring out this).

Then navigate to the folder and run:
sudo apt-get install python-dateutil
sudo python setup.py install

====Step 5: odr-radiodns-bridge====

Download from here https://github.com/nickpiggott/odr-radiodns-bridge and unpack to a folder, e.g. /home/user/odr-radiodns-bridge-master

Then navigate to the folder and run:
sudo apt-get install python-pip
sudo pip install hybridspi
sudo pip install pyradiodns
sudo python setup.py install

====Step 6: python-hybridspi====

Download from here https://github.com/magicbadger/python-hybridspi and unpack to a folder, e.g. /home/user/python-hybridspi-master

Then navigate to the folder and run:
sudo python setup.py install

====Step 7: odr-radioepg-bridge====

And now for the RadioEPG-bridge itself.

Download from here https://github.com/nickpiggott/odr-radioepg-bridge and unpack to a folder, e.g. /home/user/odr-radioepg-bridge-master

Then run:
sudo ln -s /home/user/odr-radioepg-bridge-master/generate-epg /usr/local/bin/generate-epg
(If your folder is not /home/user/odr-radioepg-bridge-master, use your_path/generate-epg in the last command line above).

That's it. You should now be able to run this command and see a help text:
generate-epg -h

===Generating and broadcasting your EPG===

====Generating your EPG====

Odr-radioepg-bridge is a command-line tool, which will:
* First read your mux.conf (from your ODR-DabMux configuration) to get information about your services.
* Then try to fetch SPI data for your services from the internet using RadioDNS.
* And lastly generate an output file containing a complete EPG.

If you type "generate-epg -h" you will get a list of available command-line arguments:

usage: generate-epg [-h] [-o OUTPUT] [-X] [-d DAYS] [-p PACKET_SIZE]
[-a PACKET_ADDRESS]
f

Encodes an EPG bitstream for services in a multiplex configuration file

positional arguments:
f multiplex configuration file

optional arguments:
-h, --help show this help message and exit
-o OUTPUT output bitstream file
-X turn debug on
-d DAYS number of days ahead to encode schedule files
-p PACKET_SIZE Packet size in bytes
-a PACKET_ADDRESS Packet address

The positional argument tells the tool where to find your mux.conf.
The other arguments are optional, and some default values will be used if you don't set them:

* -o can be used to set filename and path to your output file (your EPG). Default is output.dat, placed in the folder from where you run the tool.
* -d is the number of days of programme schedule you want in you EPG. From 1 til 4 days, default is 2.
* -p is packet size. Available values are 24, 48, 72 and 96. Default is 96. Which value you should use, depends on the bitrate in which you are broadcasting your EPG (see below).
* -a is the packet address for your EPG. Default is 1, which will normally be fine. Important is, that you must set the same address in your mux.conf (see below).

Example:
If your mux.conf is placed in /home/user/odr/config/mux.conf, and you want 4 days in your EPG (today and the next 3 days) and you want to broadcast it in 16 kbit/s, your command line could look like this:

generate-epg -d 4 -p 48 /home/user/odr/config/mux.conf

This will generate a file named output.dat containing your EPG. In this example, I have set the packet size to 48, which is suitable for 16 kbit/s. I have not set the packet address, which means that the default value of 1 will be used.

====Packet sizes and bitrates====

The packet size, which you set when you generate your EPG, should match the bitrate in which you intend to broadcast it. If the packet size is too large, your EPG will not be broadcasted. If the packet size is too small, your EPG will (probably) be broadcasted, but it will be slower than necessary, because more space will be used for packet headers and maybe partly empty data packets. I will recommend these values:

{| class="wikitable"
! Bitrate
! Packet size
|-
| 8
| 24
|-
| 16
| 48
|-
| 24
| 72
|-
| 32
| 96
|-
| 48
| 72
|-
| 64
| 96
|}

====Broadcasting your EPG====

To broadcast your EPG using ODR-DabMux, create a packet data service in your mux.conf like in this example:

In the services section:

srv-epg {
label "EPG"
shortlabel "EPG"
; the service-ID consists of 8 hex digits for packet data services. Usually the first two digits will
; be the same as your ECC, and the third digit will be the same as the first digit in your Ensemble Id.
id 0xe1912345
}

In the subchannels section:

sub-epg {
; type packet or enhancedpacket can be used for EPG.
type enhancedpacket
; if you change the bitrate, remember to also change the packet size accordingly (see above) and generate your EPG again.
bitrate 16
protection-profile EEP_A
protection 3
; inputuri is the path and filename for your output file from generate-epg
inputuri "/home/user/odr-radioepg-bridge-master/output.dat"
inputproto file
}

And in the components section:

comp-epg {
type 60
service srv-epg
subchannel sub-epg
figtype 0x7
; The address must be the same as your packet address set when you generate the EPG (default value is 1).
address 0x1
datagroup true
}

That's it. Now (re)start your ODR-DabMux, and your EPG should be broadcasted.

===Updating your EPG automatically every day===

You can update your EPG every 24 hours by adding a new daily task to cron.

Assuming you have a ~/odr/epg folder Create a new file

/etc/cron.daily/epg

with the single line

/usr/local/bin/generate-epg -d 4 -p 48 /home/user/odr/config/mux.conf -o /home/user/odr/epg/epg_data.dat

In your mux.conf you would use the lines

inputuri "/home/user/odr/epg/epg_data.dat"
inputproto file

to tell odr-dabmux where to read the EPG packet data from.

By default, the cron job will run every day at around 06:00. If you want your EPG to update more frequently (every 4 hours), you could add it to the user cron job with

crontab -e

and add the line

0 */4 * * * /usr/local/bin/generate-epg -d 4 -p 48 /home/user/odr/config/mux.conf -o /home/user/odr/epg/epg_data.dat

'''NOTE:'''
The EPG creates new MOT TransportIDs for every object each time it is run. A receiver will not recognise that objects have been previously received and cached. If there is an interruption in reception, the EPG will be incomplete. The more frequently you update the EPG, more likely it is that a receiver will not be able to utilise the cached objects.

===Some problems and solutions===

====Local variable 'ecc' referenced before assignment====

For some domains, lookup will cause the script to fail with error message "local variable 'ecc' referenced before assignment" if the domain has no _radiotag._tcp SRV record.

You can get around this by opening this file in a text editor:
/usr/local/lib/python2.7/dist-packages/pyradiodns/rdns.py
and remove or comment out line 13 "('radiotag', 'TCP'),".

If the domain is not using RadioVIS, you might also have to remove line 14 "('radiovis', 'TCP'),", but I haven't experienced this myself.

Note: When you modify this file, you might have to remove '''rdns.pyc''' in the same folder to make sure that your changes are being used.

====Radio programmes listed on a wrong date====

I have observed that radio programmes beginning before noon (or all programmes on some receivers) were listed on a wrong date, one day before the correct date. My solution was to modify line 428 in this file:

/usr/local/lib/python2.7/dist-packages/spi/binary/__init__py

Here, "(timepoint.hour - 12)" should be changed to "timepoint.hour", so that line 428 will be:

jd = jdn + timepoint.hour / 24 + timepoint.minute / 1440 + timepoint.second / 86400

This should fix the daystamp issue.

Note: When you modify this file, you might have to remove '''__init__.pyc''' in the same folder to make sure that your changes are being used.

====Radio programmes listed with wrong timestamps if your time zone is not UTC====

I have observed that if the time zone is not UTC, all radio programmes were listed with wrong times. My solution was to make some modifications to this file:
/usr/local/lib/python2.7/dist-packages/spi/binary/__init__py

After line 419 ("bits.setall(False)") I have added the following two lines:

offset = (timepoint.utcoffset().days * 86400 + timepoint.utcoffset().seconds) + (timepoint.dst().days * 86400 + timepoint.dst().days)
timepoint=timepoint - timedelta(seconds=offset)

(The first line is taken from line 457, from where it can then be removed)

And after line 28 ("import sys"), I have added this line:

from datetime import timedelta

This should fix the timestamp issue.

Note: When you modify this file, you might have to remove '''__init__.pyc''' in the same folder to make sure that your changes are being used.

===Other observations===

* According to specs, logo slides in DAB EPG must be PNG. Although JPG is allowed in hybrid radio SPI, JPG logos will not be added to your DAB EPG. Be sure that your logos (up to 320x240) are PNG.
* Programme descriptions (shortDescription) seem to be processed but not shown. Perhaps we will have to look a little further into this.

How to configure SPI (Service and Programme Information) for ODR-DabMux

2020-07-14T16:11:44Z

Nickpiggott: Correct link

Howto by Ulrik Brinck on odr-radioepg-bridge installation on Debian Jessie
===Introduction===

This tool (or rather series of tools) will pick up your SPI (Service and Programme Information) from the internet via RadioDNS and generate a DAB EPG from it. It was written by Ben Poor and Nick Piggott. In this HowTo, I will describe how it can be installed on Debian Jessie. Some details might be slightly different on other Debian generations.

* In this context, EPG and SPI is basically the same thing. While EPG (Electronic Programme Guide) is an old, but commonly well-known term, SPI (Service and Programme Information) is now the official name of this feature.

===Notes===

'''This tool uses RadioDNS to locate and acquire Service Information (SI.xml), Programme Information (PI.xml) and Logos.'''
Each station you want to add to the EPG must be registered in RadioDNS using the correct information (Ensemble ID, Service ID, Service Component ID), and have correctly formatted SI, PI and logo files in PNG format. Find out more at https://radiodns.org/technical/documentation/#howto

I have assumed that you are logged in to your Linux system as a standard user and have sudo installed on your system. If sudo is not installed, you can see here, how to install it on Debian Jessie:
https://www.geek17.com/en/content/debian-8-jessie-install-and-configure-sudo-25

===Installation===

====Step 0: Update your system====
Begin with "sudo apt-get update" to make sure that you can install all that you need.

====Step 1: Miscellaneous dependencies====
First there are some dependencies to install with apt-get:

sudo apt-get install python-crcmod
sudo apt-get install python-bitarray
sudo apt-get install python-isodate

Next there are some dependencies and subcomponents which must be downloaded from github and installed:

====Step 2: python-dabmot====

Download from here https://github.com/GlobalRadio/python-dabmot and unpack to a folder, e.g. /home/user/python-dabmot-master

Then navigate to the folder and run:
sudo python setup.py install

====Step 3: python-mot-epg====

Download from here https://github.com/GlobalRadio/python-mot-epg and unpack to a folder, e.g. /home/user/python-mot-epg-master

Then navigate to the folder and run:
sudo python setup.py install

====Step 4: python-msc====

Download from here https://github.com/nickpiggott/python-dabmsc and unpack to a folder, e.g. /home/user/python-dabmsc-master

Important: '''It MUST be this commit''', NOT the original one from GlobalRadio from 2017 (thanks to Nick Piggott for help figuring out this).

Then navigate to the folder and run:
sudo apt-get install python-dateutil
sudo python setup.py install

====Step 5: odr-radiodns-bridge====

Download from here https://github.com/nickpiggott/odr-radiodns-bridge and unpack to a folder, e.g. /home/user/odr-radiodns-bridge-master

Then navigate to the folder and run:
sudo apt-get install python-pip
sudo pip install hybridspi
sudo pip install pyradiodns
sudo python setup.py install

====Step 6: python-hybridspi====

Download from here https://github.com/magicbadger/python-hybridspi and unpack to a folder, e.g. /home/user/python-hybridspi-master

Then navigate to the folder and run:
sudo python setup.py install

====Step 7: odr-radioepg-bridge====

And now for the RadioEPG-bridge itself.

Download from here https://github.com/nickpiggott/odr-radioepg-bridge and unpack to a folder, e.g. /home/user/odr-radioepg-bridge-master

Then run:
sudo ln -s /home/user/odr-radioepg-bridge-master/generate-epg /usr/local/bin/generate-epg
(If your folder is not /home/user/odr-radioepg-bridge-master, use your_path/generate-epg in the last command line above).

That's it. You should now be able to run this command and see a help text:
generate-epg -h

===Generating and broadcasting your EPG===

====Generating your EPG====

Odr-radioepg-bridge is a command-line tool, which will:
* First read your mux.conf (from your ODR-DabMux configuration) to get information about your services.
* Then try to fetch SPI data for your services from the internet using RadioDNS.
* And lastly generate an output file containing a complete EPG.

If you type "generate-epg -h" you will get a list of available command-line arguments:

usage: generate-epg [-h] [-o OUTPUT] [-X] [-d DAYS] [-p PACKET_SIZE]
[-a PACKET_ADDRESS]
f

Encodes an EPG bitstream for services in a multiplex configuration file

positional arguments:
f multiplex configuration file

optional arguments:
-h, --help show this help message and exit
-o OUTPUT output bitstream file
-X turn debug on
-d DAYS number of days ahead to encode schedule files
-p PACKET_SIZE Packet size in bytes
-a PACKET_ADDRESS Packet address

The positional argument tells the tool where to find your mux.conf.
The other arguments are optional, and some default values will be used if you don't set them:

* -o can be used to set filename and path to your output file (your EPG). Default is output.dat, placed in the folder from where you run the tool.
* -d is the number of days of programme schedule you want in you EPG. From 1 til 4 days, default is 2.
* -p is packet size. Available values are 24, 48, 72 and 96. Default is 96. Which value you should use, depends on the bitrate in which you are broadcasting your EPG (see below).
* -a is the packet address for your EPG. Default is 1, which will normally be fine. Important is, that you must set the same address in your mux.conf (see below).

Example:
If your mux.conf is placed in /home/user/odr/config/mux.conf, and you want 4 days in your EPG (today and the next 3 days) and you want to broadcast it in 16 kbit/s, your command line could look like this:

generate-epg -d 4 -p 48 /home/user/odr/config/mux.conf

This will generate a file named output.dat containing your EPG. In this example, I have set the packet size to 48, which is suitable for 16 kbit/s. I have not set the packet address, which means that the default value of 1 will be used.

====Packet sizes and bitrates====

The packet size, which you set when you generate your EPG, should match the bitrate in which you intend to broadcast it. If the packet size is too large, your EPG will not be broadcasted. If the packet size is too small, your EPG will (probably) be broadcasted, but it will be slower than necessary, because more space will be used for packet headers and maybe partly empty data packets. I will recommend these values:

{| class="wikitable"
! Bitrate
! Packet size
|-
| 8
| 24
|-
| 16
| 48
|-
| 24
| 72
|-
| 32
| 96
|-
| 48
| 72
|-
| 64
| 96
|}

====Broadcasting your EPG====

To broadcast your EPG using ODR-DabMux, create a packet data service in your mux.conf like in this example:

In the services section:

srv-epg {
label "EPG"
shortlabel "EPG"
; the service-ID consists of 8 hex digits for packet data services. Usually the first two digits will
; be the same as your ECC, and the third digit will be the same as the first digit in your Ensemble Id.
id 0xe1912345
}

In the subchannels section:

sub-epg {
; type packet or enhancedpacket can be used for EPG.
type enhancedpacket
; if you change the bitrate, remember to also change the packet size accordingly (see above) and generate your EPG again.
bitrate 16
protection-profile EEP_A
protection 3
; inputuri is the path and filename for your output file from generate-epg
inputuri "/home/user/odr-radioepg-bridge-master/output.dat"
inputproto file
}

And in the components section:

comp-epg {
type 60
service srv-epg
subchannel sub-epg
figtype 0x7
; The address must be the same as your packet address set when you generate the EPG (default value is 1).
address 0x1
datagroup true
}

That's it. Now (re)start your ODR-DabMux, and your EPG should be broadcasted.

===Updating your EPG automatically every day===

To be written....

===Some problems and solutions===

====Local variable 'ecc' referenced before assignment====

For some domains, lookup will cause the script to fail with error message "local variable 'ecc' referenced before assignment" if the domain has no _radiotag._tcp SRV record.

You can get around this by opening this file in a text editor:
/usr/local/lib/python2.7/dist-packages/pyradiodns/rdns.py
and remove or comment out line 13 "('radiotag', 'TCP'),".

If the domain is not using RadioVIS, you might also have to remove line 14 "('radiovis', 'TCP'),", but I haven't experienced this myself.

Note: When you modify this file, you might have to remove '''rdns.pyc''' in the same folder to make sure that your changes are being used.

====Radio programmes listed on a wrong date====

I have observed that radio programmes beginning before noon (or all programmes on some receivers) were listed on a wrong date, one day before the correct date. My solution was to modify line 428 in this file:

/usr/local/lib/python2.7/dist-packages/spi/binary/__init__py

Here, "(timepoint.hour - 12)" should be changed to "timepoint.hour", so that line 428 will be:

jd = jdn + timepoint.hour / 24 + timepoint.minute / 1440 + timepoint.second / 86400

This should fix the daystamp issue.

Note: When you modify this file, you might have to remove '''__init__.pyc''' in the same folder to make sure that your changes are being used.

====Radio programmes listed with wrong timestamps if your time zone is not UTC====

I have observed that if the time zone is not UTC, all radio programmes were listed with wrong times. My solution was to make some modifications to this file:
/usr/local/lib/python2.7/dist-packages/spi/binary/__init__py

After line 419 ("bits.setall(False)") I have added the following two lines:

offset = (timepoint.utcoffset().days * 86400 + timepoint.utcoffset().seconds) + (timepoint.dst().days * 86400 + timepoint.dst().days)
timepoint=timepoint - timedelta(seconds=offset)

(The first line is taken from line 457, from where it can then be removed)

And after line 28 ("import sys"), I have added this line:

from datetime import timedelta

This should fix the timestamp issue.

Note: When you modify this file, you might have to remove '''__init__.pyc''' in the same folder to make sure that your changes are being used.

===Other observations===

* According to specs, logo slides in DAB EPG must be PNG. Although JPG is allowed in hybrid radio SPI, JPG logos will not be added to your DAB EPG. Be sure that your logos (up to 320x240) are PNG.
* Programme descriptions (shortDescription) seem to be processed but not shown. Perhaps we will have to look a little further into this.

How to configure SPI (Service and Programme Information) for ODR-DabMux

2020-07-14T16:10:56Z

Nickpiggott: Extended explanation of how the bridge works by sourcing content using RadioDNS

Howto by Ulrik Brinck on odr-radioepg-bridge installation on Debian Jessie
===Introduction===

This tool (or rather series of tools) will pick up your SPI (Service and Programme Information) from the internet via RadioDNS and generate a DAB EPG from it. It was written by Ben Poor and Nick Piggott. In this HowTo, I will describe how it can be installed on Debian Jessie. Some details might be slightly different on other Debian generations.

* In this context, EPG and SPI is basically the same thing. While EPG (Electronic Programme Guide) is an old, but commonly well-known term, SPI (Service and Programme Information) is now the official name of this feature.

===Notes===

'''This tool uses RadioDNS to locate and acquire Service Information (SI.xml), Programme Information (PI.xml) and Logos.'''
Each station you want to add to the EPG must be registered in RadioDNS using the correct information (Ensemble ID, Service ID, Service Component ID), and have correctly formatted SI, PI and logo files in PNG format. Find out more at [radiodns.org](https://radiodns.org/technical/documentation/#howto)

I have assumed that you are logged in to your Linux system as a standard user and have sudo installed on your system. If sudo is not installed, you can see here, how to install it on Debian Jessie:
https://www.geek17.com/en/content/debian-8-jessie-install-and-configure-sudo-25

===Installation===

====Step 0: Update your system====
Begin with "sudo apt-get update" to make sure that you can install all that you need.

====Step 1: Miscellaneous dependencies====
First there are some dependencies to install with apt-get:

sudo apt-get install python-crcmod
sudo apt-get install python-bitarray
sudo apt-get install python-isodate

Next there are some dependencies and subcomponents which must be downloaded from github and installed:

====Step 2: python-dabmot====

Download from here https://github.com/GlobalRadio/python-dabmot and unpack to a folder, e.g. /home/user/python-dabmot-master

Then navigate to the folder and run:
sudo python setup.py install

====Step 3: python-mot-epg====

Download from here https://github.com/GlobalRadio/python-mot-epg and unpack to a folder, e.g. /home/user/python-mot-epg-master

Then navigate to the folder and run:
sudo python setup.py install

====Step 4: python-msc====

Download from here https://github.com/nickpiggott/python-dabmsc and unpack to a folder, e.g. /home/user/python-dabmsc-master

Important: '''It MUST be this commit''', NOT the original one from GlobalRadio from 2017 (thanks to Nick Piggott for help figuring out this).

Then navigate to the folder and run:
sudo apt-get install python-dateutil
sudo python setup.py install

====Step 5: odr-radiodns-bridge====

Download from here https://github.com/nickpiggott/odr-radiodns-bridge and unpack to a folder, e.g. /home/user/odr-radiodns-bridge-master

Then navigate to the folder and run:
sudo apt-get install python-pip
sudo pip install hybridspi
sudo pip install pyradiodns
sudo python setup.py install

====Step 6: python-hybridspi====

Download from here https://github.com/magicbadger/python-hybridspi and unpack to a folder, e.g. /home/user/python-hybridspi-master

Then navigate to the folder and run:
sudo python setup.py install

====Step 7: odr-radioepg-bridge====

And now for the RadioEPG-bridge itself.

Download from here https://github.com/nickpiggott/odr-radioepg-bridge and unpack to a folder, e.g. /home/user/odr-radioepg-bridge-master

Then run:
sudo ln -s /home/user/odr-radioepg-bridge-master/generate-epg /usr/local/bin/generate-epg
(If your folder is not /home/user/odr-radioepg-bridge-master, use your_path/generate-epg in the last command line above).

That's it. You should now be able to run this command and see a help text:
generate-epg -h

===Generating and broadcasting your EPG===

====Generating your EPG====

Odr-radioepg-bridge is a command-line tool, which will:
* First read your mux.conf (from your ODR-DabMux configuration) to get information about your services.
* Then try to fetch SPI data for your services from the internet using RadioDNS.
* And lastly generate an output file containing a complete EPG.

If you type "generate-epg -h" you will get a list of available command-line arguments:

usage: generate-epg [-h] [-o OUTPUT] [-X] [-d DAYS] [-p PACKET_SIZE]
[-a PACKET_ADDRESS]
f

Encodes an EPG bitstream for services in a multiplex configuration file

positional arguments:
f multiplex configuration file

optional arguments:
-h, --help show this help message and exit
-o OUTPUT output bitstream file
-X turn debug on
-d DAYS number of days ahead to encode schedule files
-p PACKET_SIZE Packet size in bytes
-a PACKET_ADDRESS Packet address

The positional argument tells the tool where to find your mux.conf.
The other arguments are optional, and some default values will be used if you don't set them:

* -o can be used to set filename and path to your output file (your EPG). Default is output.dat, placed in the folder from where you run the tool.
* -d is the number of days of programme schedule you want in you EPG. From 1 til 4 days, default is 2.
* -p is packet size. Available values are 24, 48, 72 and 96. Default is 96. Which value you should use, depends on the bitrate in which you are broadcasting your EPG (see below).
* -a is the packet address for your EPG. Default is 1, which will normally be fine. Important is, that you must set the same address in your mux.conf (see below).

Example:
If your mux.conf is placed in /home/user/odr/config/mux.conf, and you want 4 days in your EPG (today and the next 3 days) and you want to broadcast it in 16 kbit/s, your command line could look like this:

generate-epg -d 4 -p 48 /home/user/odr/config/mux.conf

This will generate a file named output.dat containing your EPG. In this example, I have set the packet size to 48, which is suitable for 16 kbit/s. I have not set the packet address, which means that the default value of 1 will be used.

====Packet sizes and bitrates====

The packet size, which you set when you generate your EPG, should match the bitrate in which you intend to broadcast it. If the packet size is too large, your EPG will not be broadcasted. If the packet size is too small, your EPG will (probably) be broadcasted, but it will be slower than necessary, because more space will be used for packet headers and maybe partly empty data packets. I will recommend these values:

{| class="wikitable"
! Bitrate
! Packet size
|-
| 8
| 24
|-
| 16
| 48
|-
| 24
| 72
|-
| 32
| 96
|-
| 48
| 72
|-
| 64
| 96
|}

====Broadcasting your EPG====

To broadcast your EPG using ODR-DabMux, create a packet data service in your mux.conf like in this example:

In the services section:

srv-epg {
label "EPG"
shortlabel "EPG"
; the service-ID consists of 8 hex digits for packet data services. Usually the first two digits will
; be the same as your ECC, and the third digit will be the same as the first digit in your Ensemble Id.
id 0xe1912345
}

In the subchannels section:

sub-epg {
; type packet or enhancedpacket can be used for EPG.
type enhancedpacket
; if you change the bitrate, remember to also change the packet size accordingly (see above) and generate your EPG again.
bitrate 16
protection-profile EEP_A
protection 3
; inputuri is the path and filename for your output file from generate-epg
inputuri "/home/user/odr-radioepg-bridge-master/output.dat"
inputproto file
}

And in the components section:

comp-epg {
type 60
service srv-epg
subchannel sub-epg
figtype 0x7
; The address must be the same as your packet address set when you generate the EPG (default value is 1).
address 0x1
datagroup true
}

That's it. Now (re)start your ODR-DabMux, and your EPG should be broadcasted.

===Updating your EPG automatically every day===

To be written....

===Some problems and solutions===

====Local variable 'ecc' referenced before assignment====

For some domains, lookup will cause the script to fail with error message "local variable 'ecc' referenced before assignment" if the domain has no _radiotag._tcp SRV record.

You can get around this by opening this file in a text editor:
/usr/local/lib/python2.7/dist-packages/pyradiodns/rdns.py
and remove or comment out line 13 "('radiotag', 'TCP'),".

If the domain is not using RadioVIS, you might also have to remove line 14 "('radiovis', 'TCP'),", but I haven't experienced this myself.

Note: When you modify this file, you might have to remove '''rdns.pyc''' in the same folder to make sure that your changes are being used.

====Radio programmes listed on a wrong date====

I have observed that radio programmes beginning before noon (or all programmes on some receivers) were listed on a wrong date, one day before the correct date. My solution was to modify line 428 in this file:

/usr/local/lib/python2.7/dist-packages/spi/binary/__init__py

Here, "(timepoint.hour - 12)" should be changed to "timepoint.hour", so that line 428 will be:

jd = jdn + timepoint.hour / 24 + timepoint.minute / 1440 + timepoint.second / 86400

This should fix the daystamp issue.

Note: When you modify this file, you might have to remove '''__init__.pyc''' in the same folder to make sure that your changes are being used.

====Radio programmes listed with wrong timestamps if your time zone is not UTC====

I have observed that if the time zone is not UTC, all radio programmes were listed with wrong times. My solution was to make some modifications to this file:
/usr/local/lib/python2.7/dist-packages/spi/binary/__init__py

After line 419 ("bits.setall(False)") I have added the following two lines:

offset = (timepoint.utcoffset().days * 86400 + timepoint.utcoffset().seconds) + (timepoint.dst().days * 86400 + timepoint.dst().days)
timepoint=timepoint - timedelta(seconds=offset)

(The first line is taken from line 457, from where it can then be removed)

And after line 28 ("import sys"), I have added this line:

from datetime import timedelta

This should fix the timestamp issue.

Note: When you modify this file, you might have to remove '''__init__.pyc''' in the same folder to make sure that your changes are being used.

===Other observations===

* According to specs, logo slides in DAB EPG must be PNG. Although JPG is allowed in hybrid radio SPI, JPG logos will not be added to your DAB EPG. Be sure that your logos (up to 320x240) are PNG.
* Programme descriptions (shortDescription) seem to be processed but not shown. Perhaps we will have to look a little further into this.

How to configure SPI (Service and Programme Information) for ODR-DabMux

2020-07-14T16:07:24Z

Nickpiggott: Moved to /usr/local/bin per Debian guidelines

Howto by Ulrik Brinck on odr-radioepg-bridge installation on Debian Jessie
===Introduction===

This tool (or rather series of tools) will pick up your SPI (Service and Programme Information) from the internet via RadioDNS and generate a DAB EPG from it. It was written by Ben Poor and Nick Piggott. In this HowTo, I will describe how it can be installed on Debian Jessie. Some details might be slightly different on other Debian generations.

* In this context, EPG and SPI is basically the same thing. While EPG (Electronic Programme Guide) is an old, but commonly well-known term, SPI (Service and Programme Information) is now the official name of this feature.

===Notes===

'''You must already have a working EPG (SPI) for hybrid radio via radioDNS, before you can use this tool.'''

I have assumed that you are logged in to your Linux system as a standard user and have sudo installed on your system. If sudo is not installed, you can see here, how to install it on Debian Jessie:
https://www.geek17.com/en/content/debian-8-jessie-install-and-configure-sudo-25

===Installation===

====Step 0: Update your system====
Begin with "sudo apt-get update" to make sure that you can install all that you need.

====Step 1: Miscellaneous dependencies====
First there are some dependencies to install with apt-get:

sudo apt-get install python-crcmod
sudo apt-get install python-bitarray
sudo apt-get install python-isodate

Next there are some dependencies and subcomponents which must be downloaded from github and installed:

====Step 2: python-dabmot====

Download from here https://github.com/GlobalRadio/python-dabmot and unpack to a folder, e.g. /home/user/python-dabmot-master

Then navigate to the folder and run:
sudo python setup.py install

====Step 3: python-mot-epg====

Download from here https://github.com/GlobalRadio/python-mot-epg and unpack to a folder, e.g. /home/user/python-mot-epg-master

Then navigate to the folder and run:
sudo python setup.py install

====Step 4: python-msc====

Download from here https://github.com/nickpiggott/python-dabmsc and unpack to a folder, e.g. /home/user/python-dabmsc-master

Important: '''It MUST be this commit''', NOT the original one from GlobalRadio from 2017 (thanks to Nick Piggott for help figuring out this).

Then navigate to the folder and run:
sudo apt-get install python-dateutil
sudo python setup.py install

====Step 5: odr-radiodns-bridge====

Download from here https://github.com/nickpiggott/odr-radiodns-bridge and unpack to a folder, e.g. /home/user/odr-radiodns-bridge-master

Then navigate to the folder and run:
sudo apt-get install python-pip
sudo pip install hybridspi
sudo pip install pyradiodns
sudo python setup.py install

====Step 6: python-hybridspi====

Download from here https://github.com/magicbadger/python-hybridspi and unpack to a folder, e.g. /home/user/python-hybridspi-master

Then navigate to the folder and run:
sudo python setup.py install

====Step 7: odr-radioepg-bridge====

And now for the RadioEPG-bridge itself.

Download from here https://github.com/nickpiggott/odr-radioepg-bridge and unpack to a folder, e.g. /home/user/odr-radioepg-bridge-master

Then run:
sudo ln -s /home/user/odr-radioepg-bridge-master/generate-epg /usr/local/bin/generate-epg
(If your folder is not /home/user/odr-radioepg-bridge-master, use your_path/generate-epg in the last command line above).

That's it. You should now be able to run this command and see a help text:
generate-epg -h

===Generating and broadcasting your EPG===

====Generating your EPG====

Odr-radioepg-bridge is a command-line tool, which will:
* First read your mux.conf (from your ODR-DabMux configuration) to get information about your services.
* Then try to fetch SPI data for your services from the internet using RadioDNS.
* And lastly generate an output file containing a complete EPG.

If you type "generate-epg -h" you will get a list of available command-line arguments:

usage: generate-epg [-h] [-o OUTPUT] [-X] [-d DAYS] [-p PACKET_SIZE]
[-a PACKET_ADDRESS]
f

Encodes an EPG bitstream for services in a multiplex configuration file

positional arguments:
f multiplex configuration file

optional arguments:
-h, --help show this help message and exit
-o OUTPUT output bitstream file
-X turn debug on
-d DAYS number of days ahead to encode schedule files
-p PACKET_SIZE Packet size in bytes
-a PACKET_ADDRESS Packet address

The positional argument tells the tool where to find your mux.conf.
The other arguments are optional, and some default values will be used if you don't set them:

* -o can be used to set filename and path to your output file (your EPG). Default is output.dat, placed in the folder from where you run the tool.
* -d is the number of days of programme schedule you want in you EPG. From 1 til 4 days, default is 2.
* -p is packet size. Available values are 24, 48, 72 and 96. Default is 96. Which value you should use, depends on the bitrate in which you are broadcasting your EPG (see below).
* -a is the packet address for your EPG. Default is 1, which will normally be fine. Important is, that you must set the same address in your mux.conf (see below).

Example:
If your mux.conf is placed in /home/user/odr/config/mux.conf, and you want 4 days in your EPG (today and the next 3 days) and you want to broadcast it in 16 kbit/s, your command line could look like this:

generate-epg -d 4 -p 48 /home/user/odr/config/mux.conf

This will generate a file named output.dat containing your EPG. In this example, I have set the packet size to 48, which is suitable for 16 kbit/s. I have not set the packet address, which means that the default value of 1 will be used.

====Packet sizes and bitrates====

The packet size, which you set when you generate your EPG, should match the bitrate in which you intend to broadcast it. If the packet size is too large, your EPG will not be broadcasted. If the packet size is too small, your EPG will (probably) be broadcasted, but it will be slower than necessary, because more space will be used for packet headers and maybe partly empty data packets. I will recommend these values:

{| class="wikitable"
! Bitrate
! Packet size
|-
| 8
| 24
|-
| 16
| 48
|-
| 24
| 72
|-
| 32
| 96
|-
| 48
| 72
|-
| 64
| 96
|}

====Broadcasting your EPG====

To broadcast your EPG using ODR-DabMux, create a packet data service in your mux.conf like in this example:

In the services section:

srv-epg {
label "EPG"
shortlabel "EPG"
; the service-ID consists of 8 hex digits for packet data services. Usually the first two digits will
; be the same as your ECC, and the third digit will be the same as the first digit in your Ensemble Id.
id 0xe1912345
}

In the subchannels section:

sub-epg {
; type packet or enhancedpacket can be used for EPG.
type enhancedpacket
; if you change the bitrate, remember to also change the packet size accordingly (see above) and generate your EPG again.
bitrate 16
protection-profile EEP_A
protection 3
; inputuri is the path and filename for your output file from generate-epg
inputuri "/home/user/odr-radioepg-bridge-master/output.dat"
inputproto file
}

And in the components section:

comp-epg {
type 60
service srv-epg
subchannel sub-epg
figtype 0x7
; The address must be the same as your packet address set when you generate the EPG (default value is 1).
address 0x1
datagroup true
}

That's it. Now (re)start your ODR-DabMux, and your EPG should be broadcasted.

===Updating your EPG automatically every day===

To be written....

===Some problems and solutions===

====Local variable 'ecc' referenced before assignment====

For some domains, lookup will cause the script to fail with error message "local variable 'ecc' referenced before assignment" if the domain has no _radiotag._tcp SRV record.

You can get around this by opening this file in a text editor:
/usr/local/lib/python2.7/dist-packages/pyradiodns/rdns.py
and remove or comment out line 13 "('radiotag', 'TCP'),".

If the domain is not using RadioVIS, you might also have to remove line 14 "('radiovis', 'TCP'),", but I haven't experienced this myself.

Note: When you modify this file, you might have to remove '''rdns.pyc''' in the same folder to make sure that your changes are being used.

====Radio programmes listed on a wrong date====

I have observed that radio programmes beginning before noon (or all programmes on some receivers) were listed on a wrong date, one day before the correct date. My solution was to modify line 428 in this file:

/usr/local/lib/python2.7/dist-packages/spi/binary/__init__py

Here, "(timepoint.hour - 12)" should be changed to "timepoint.hour", so that line 428 will be:

jd = jdn + timepoint.hour / 24 + timepoint.minute / 1440 + timepoint.second / 86400

This should fix the daystamp issue.

Note: When you modify this file, you might have to remove '''__init__.pyc''' in the same folder to make sure that your changes are being used.

====Radio programmes listed with wrong timestamps if your time zone is not UTC====

I have observed that if the time zone is not UTC, all radio programmes were listed with wrong times. My solution was to make some modifications to this file:
/usr/local/lib/python2.7/dist-packages/spi/binary/__init__py

After line 419 ("bits.setall(False)") I have added the following two lines:

offset = (timepoint.utcoffset().days * 86400 + timepoint.utcoffset().seconds) + (timepoint.dst().days * 86400 + timepoint.dst().days)
timepoint=timepoint - timedelta(seconds=offset)

(The first line is taken from line 457, from where it can then be removed)

And after line 28 ("import sys"), I have added this line:

from datetime import timedelta

This should fix the timestamp issue.

Note: When you modify this file, you might have to remove '''__init__.pyc''' in the same folder to make sure that your changes are being used.

===Other observations===

* According to specs, logo slides in DAB EPG must be PNG. Although JPG is allowed in hybrid radio SPI, JPG logos will not be added to your DAB EPG. Be sure that your logos (up to 320x240) are PNG.
* Programme descriptions (shortDescription) seem to be processed but not shown. Perhaps we will have to look a little further into this.

How to configure SPI (Service and Programme Information) for ODR-DabMux

2020-07-14T16:06:42Z

Nickpiggott: Have added a setup.py file to that package

Howto by Ulrik Brinck on odr-radioepg-bridge installation on Debian Jessie
===Introduction===

This tool (or rather series of tools) will pick up your SPI (Service and Programme Information) from the internet via RadioDNS and generate a DAB EPG from it. It was written by Ben Poor and Nick Piggott. In this HowTo, I will describe how it can be installed on Debian Jessie. Some details might be slightly different on other Debian generations.

* In this context, EPG and SPI is basically the same thing. While EPG (Electronic Programme Guide) is an old, but commonly well-known term, SPI (Service and Programme Information) is now the official name of this feature.

===Notes===

'''You must already have a working EPG (SPI) for hybrid radio via radioDNS, before you can use this tool.'''

I have assumed that you are logged in to your Linux system as a standard user and have sudo installed on your system. If sudo is not installed, you can see here, how to install it on Debian Jessie:
https://www.geek17.com/en/content/debian-8-jessie-install-and-configure-sudo-25

===Installation===

====Step 0: Update your system====
Begin with "sudo apt-get update" to make sure that you can install all that you need.

====Step 1: Miscellaneous dependencies====
First there are some dependencies to install with apt-get:

sudo apt-get install python-crcmod
sudo apt-get install python-bitarray
sudo apt-get install python-isodate

Next there are some dependencies and subcomponents which must be downloaded from github and installed:

====Step 2: python-dabmot====

Download from here https://github.com/GlobalRadio/python-dabmot and unpack to a folder, e.g. /home/user/python-dabmot-master

Then navigate to the folder and run:
sudo python setup.py install

====Step 3: python-mot-epg====

Download from here https://github.com/GlobalRadio/python-mot-epg and unpack to a folder, e.g. /home/user/python-mot-epg-master

Then navigate to the folder and run:
sudo python setup.py install

====Step 4: python-msc====

Download from here https://github.com/nickpiggott/python-dabmsc and unpack to a folder, e.g. /home/user/python-dabmsc-master

Important: '''It MUST be this commit''', NOT the original one from GlobalRadio from 2017 (thanks to Nick Piggott for help figuring out this).

Then navigate to the folder and run:
sudo apt-get install python-dateutil
sudo python setup.py install

====Step 5: odr-radiodns-bridge====

Download from here https://github.com/nickpiggott/odr-radiodns-bridge and unpack to a folder, e.g. /home/user/odr-radiodns-bridge-master

Then navigate to the folder and run:
sudo apt-get install python-pip
sudo pip install hybridspi
sudo pip install pyradiodns
sudo python setup.py install

====Step 6: python-hybridspi====

Download from here https://github.com/magicbadger/python-hybridspi and unpack to a folder, e.g. /home/user/python-hybridspi-master

Then navigate to the folder and run:
sudo python setup.py install

====Step 7: odr-radioepg-bridge====

And now for the RadioEPG-bridge itself.

Download from here https://github.com/nickpiggott/odr-radioepg-bridge and unpack to a folder, e.g. /home/user/odr-radioepg-bridge-master

Then run:
sudo ln -s /home/user/odr-radioepg-bridge-master/generate-epg /usr/bin/generate-epg
(If your folder is not /home/user/odr-radioepg-bridge-master, use your_path/generate-epg in the last command line above).

That's it. You should now be able to run this command and see a help text:
generate-epg -h

===Generating and broadcasting your EPG===

====Generating your EPG====

Odr-radioepg-bridge is a command-line tool, which will:
* First read your mux.conf (from your ODR-DabMux configuration) to get information about your services.
* Then try to fetch SPI data for your services from the internet using RadioDNS.
* And lastly generate an output file containing a complete EPG.

If you type "generate-epg -h" you will get a list of available command-line arguments:

usage: generate-epg [-h] [-o OUTPUT] [-X] [-d DAYS] [-p PACKET_SIZE]
[-a PACKET_ADDRESS]
f

Encodes an EPG bitstream for services in a multiplex configuration file

positional arguments:
f multiplex configuration file

optional arguments:
-h, --help show this help message and exit
-o OUTPUT output bitstream file
-X turn debug on
-d DAYS number of days ahead to encode schedule files
-p PACKET_SIZE Packet size in bytes
-a PACKET_ADDRESS Packet address

The positional argument tells the tool where to find your mux.conf.
The other arguments are optional, and some default values will be used if you don't set them:

* -o can be used to set filename and path to your output file (your EPG). Default is output.dat, placed in the folder from where you run the tool.
* -d is the number of days of programme schedule you want in you EPG. From 1 til 4 days, default is 2.
* -p is packet size. Available values are 24, 48, 72 and 96. Default is 96. Which value you should use, depends on the bitrate in which you are broadcasting your EPG (see below).
* -a is the packet address for your EPG. Default is 1, which will normally be fine. Important is, that you must set the same address in your mux.conf (see below).

Example:
If your mux.conf is placed in /home/user/odr/config/mux.conf, and you want 4 days in your EPG (today and the next 3 days) and you want to broadcast it in 16 kbit/s, your command line could look like this:

generate-epg -d 4 -p 48 /home/user/odr/config/mux.conf

This will generate a file named output.dat containing your EPG. In this example, I have set the packet size to 48, which is suitable for 16 kbit/s. I have not set the packet address, which means that the default value of 1 will be used.

====Packet sizes and bitrates====

The packet size, which you set when you generate your EPG, should match the bitrate in which you intend to broadcast it. If the packet size is too large, your EPG will not be broadcasted. If the packet size is too small, your EPG will (probably) be broadcasted, but it will be slower than necessary, because more space will be used for packet headers and maybe partly empty data packets. I will recommend these values:

{| class="wikitable"
! Bitrate
! Packet size
|-
| 8
| 24
|-
| 16
| 48
|-
| 24
| 72
|-
| 32
| 96
|-
| 48
| 72
|-
| 64
| 96
|}

====Broadcasting your EPG====

To broadcast your EPG using ODR-DabMux, create a packet data service in your mux.conf like in this example:

In the services section:

srv-epg {
label "EPG"
shortlabel "EPG"
; the service-ID consists of 8 hex digits for packet data services. Usually the first two digits will
; be the same as your ECC, and the third digit will be the same as the first digit in your Ensemble Id.
id 0xe1912345
}

In the subchannels section:

sub-epg {
; type packet or enhancedpacket can be used for EPG.
type enhancedpacket
; if you change the bitrate, remember to also change the packet size accordingly (see above) and generate your EPG again.
bitrate 16
protection-profile EEP_A
protection 3
; inputuri is the path and filename for your output file from generate-epg
inputuri "/home/user/odr-radioepg-bridge-master/output.dat"
inputproto file
}

And in the components section:

comp-epg {
type 60
service srv-epg
subchannel sub-epg
figtype 0x7
; The address must be the same as your packet address set when you generate the EPG (default value is 1).
address 0x1
datagroup true
}

That's it. Now (re)start your ODR-DabMux, and your EPG should be broadcasted.

===Updating your EPG automatically every day===

To be written....

===Some problems and solutions===

====Local variable 'ecc' referenced before assignment====

For some domains, lookup will cause the script to fail with error message "local variable 'ecc' referenced before assignment" if the domain has no _radiotag._tcp SRV record.

You can get around this by opening this file in a text editor:
/usr/local/lib/python2.7/dist-packages/pyradiodns/rdns.py
and remove or comment out line 13 "('radiotag', 'TCP'),".

If the domain is not using RadioVIS, you might also have to remove line 14 "('radiovis', 'TCP'),", but I haven't experienced this myself.

Note: When you modify this file, you might have to remove '''rdns.pyc''' in the same folder to make sure that your changes are being used.

====Radio programmes listed on a wrong date====

I have observed that radio programmes beginning before noon (or all programmes on some receivers) were listed on a wrong date, one day before the correct date. My solution was to modify line 428 in this file:

/usr/local/lib/python2.7/dist-packages/spi/binary/__init__py

Here, "(timepoint.hour - 12)" should be changed to "timepoint.hour", so that line 428 will be:

jd = jdn + timepoint.hour / 24 + timepoint.minute / 1440 + timepoint.second / 86400

This should fix the daystamp issue.

Note: When you modify this file, you might have to remove '''__init__.pyc''' in the same folder to make sure that your changes are being used.

====Radio programmes listed with wrong timestamps if your time zone is not UTC====

I have observed that if the time zone is not UTC, all radio programmes were listed with wrong times. My solution was to make some modifications to this file:
/usr/local/lib/python2.7/dist-packages/spi/binary/__init__py

After line 419 ("bits.setall(False)") I have added the following two lines:

offset = (timepoint.utcoffset().days * 86400 + timepoint.utcoffset().seconds) + (timepoint.dst().days * 86400 + timepoint.dst().days)
timepoint=timepoint - timedelta(seconds=offset)

(The first line is taken from line 457, from where it can then be removed)

And after line 28 ("import sys"), I have added this line:

from datetime import timedelta

This should fix the timestamp issue.

Note: When you modify this file, you might have to remove '''__init__.pyc''' in the same folder to make sure that your changes are being used.

===Other observations===

* According to specs, logo slides in DAB EPG must be PNG. Although JPG is allowed in hybrid radio SPI, JPG logos will not be added to your DAB EPG. Be sure that your logos (up to 320x240) are PNG.
* Programme descriptions (shortDescription) seem to be processed but not shown. Perhaps we will have to look a little further into this.

How to configure SPI (Service and Programme Information) for ODR-DabMux

2020-07-14T15:56:44Z

Nickpiggott: Not necessary to install the binary "decode" to use the bridge.

Howto by Ulrik Brinck on odr-radioepg-bridge installation on Debian Jessie
===Introduction===

This tool (or rather series of tools) will pick up your SPI (Service and Programme Information) from the internet via RadioDNS and generate a DAB EPG from it. It was written by Ben Poor and Nick Piggott. In this HowTo, I will describe how it can be installed on Debian Jessie. Some details might be slightly different on other Debian generations.

* In this context, EPG and SPI is basically the same thing. While EPG (Electronic Programme Guide) is an old, but commonly well-known term, SPI (Service and Programme Information) is now the official name of this feature.

===Notes===

'''You must already have a working EPG (SPI) for hybrid radio via radioDNS, before you can use this tool.'''

I have assumed that you are logged in to your Linux system as a standard user and have sudo installed on your system. If sudo is not installed, you can see here, how to install it on Debian Jessie:
https://www.geek17.com/en/content/debian-8-jessie-install-and-configure-sudo-25

===Installation===

====Step 0: Update your system====
Begin with "sudo apt-get update" to make sure that you can install all that you need.

====Step 1: Miscellaneous dependencies====
First there are some dependencies to install with apt-get:

sudo apt-get install python-crcmod
sudo apt-get install python-bitarray
sudo apt-get install python-isodate

Next there are some dependencies and subcomponents which must be downloaded from github and installed:

====Step 2: python-dabmot====

Download from here https://github.com/GlobalRadio/python-dabmot and unpack to a folder, e.g. /home/user/python-dabmot-master

Then navigate to the folder and run:
sudo python setup.py install

====Step 3: python-mot-epg====

Download from here https://github.com/GlobalRadio/python-mot-epg and unpack to a folder, e.g. /home/user/python-mot-epg-master

Then navigate to the folder and run:
sudo python setup.py install

====Step 4: python-msc====

Download from here https://github.com/nickpiggott/python-dabmsc and unpack to a folder, e.g. /home/user/python-dabmsc-master

Important: '''It MUST be this commit''', NOT the original one from GlobalRadio from 2017 (thanks to Nick Piggott for help figuring out this).

Then navigate to the folder and run:
sudo apt-get install python-dateutil
sudo python setup.py install

====Step 5: odr-radiodns-bridge====

Download from here https://github.com/nickpiggott/odr-radiodns-bridge and unpack to a folder, e.g. /home/user/odr-radiodns-bridge-master

Then navigate to the folder and run:
sudo apt-get install python-pip
sudo pip install hybridspi
sudo pip install pyradiodns

There is no setup.py file in this package, but you can create one yourself. Go to the /src subfolder (/home/user/odr-radiodns-bridge-master/src) and create a file, setup.py with this content:

from distutils.core import setup

setup(
name='odr-radiodns-bridge',
version='1.0',
packages=['odr', 'odr.radiodns'],
url='https://github.com/nickpiggott/odr-radiodns-bridge',
license='GNU Lesser General Public License 2.1',
author='Nick Piggott',
author_email='nick@piggott.eu',
description='Tools to bridge RadioDNS applications into the OpenDigitalRadio environment'
)

Then run:
sudo python setup.py install

====Step 6: python-hybridspi====

Download from here https://github.com/magicbadger/python-hybridspi and unpack to a folder, e.g. /home/user/python-hybridspi-master

Then navigate to the folder and run:
sudo python setup.py install

====Step 7: odr-radioepg-bridge====

And now for the RadioEPG-bridge itself.

Download from here https://github.com/nickpiggott/odr-radioepg-bridge and unpack to a folder, e.g. /home/user/odr-radioepg-bridge-master

Then run:
sudo ln -s /home/user/odr-radioepg-bridge-master/generate-epg /usr/bin/generate-epg
(If your folder is not /home/user/odr-radioepg-bridge-master, use your_path/generate-epg in the last command line above).

That's it. You should now be able to run this command and see a help text:
generate-epg -h

===Generating and broadcasting your EPG===

====Generating your EPG====

Odr-radioepg-bridge is a command-line tool, which will:
* First read your mux.conf (from your ODR-DabMux configuration) to get information about your services.
* Then try to fetch SPI data for your services from the internet using RadioDNS.
* And lastly generate an output file containing a complete EPG.

If you type "generate-epg -h" you will get a list of available command-line arguments:

usage: generate-epg [-h] [-o OUTPUT] [-X] [-d DAYS] [-p PACKET_SIZE]
[-a PACKET_ADDRESS]
f

Encodes an EPG bitstream for services in a multiplex configuration file

positional arguments:
f multiplex configuration file

optional arguments:
-h, --help show this help message and exit
-o OUTPUT output bitstream file
-X turn debug on
-d DAYS number of days ahead to encode schedule files
-p PACKET_SIZE Packet size in bytes
-a PACKET_ADDRESS Packet address

The positional argument tells the tool where to find your mux.conf.
The other arguments are optional, and some default values will be used if you don't set them:

* -o can be used to set filename and path to your output file (your EPG). Default is output.dat, placed in the folder from where you run the tool.
* -d is the number of days of programme schedule you want in you EPG. From 1 til 4 days, default is 2.
* -p is packet size. Available values are 24, 48, 72 and 96. Default is 96. Which value you should use, depends on the bitrate in which you are broadcasting your EPG (see below).
* -a is the packet address for your EPG. Default is 1, which will normally be fine. Important is, that you must set the same address in your mux.conf (see below).

Example:
If your mux.conf is placed in /home/user/odr/config/mux.conf, and you want 4 days in your EPG (today and the next 3 days) and you want to broadcast it in 16 kbit/s, your command line could look like this:

generate-epg -d 4 -p 48 /home/user/odr/config/mux.conf

This will generate a file named output.dat containing your EPG. In this example, I have set the packet size to 48, which is suitable for 16 kbit/s. I have not set the packet address, which means that the default value of 1 will be used.

====Packet sizes and bitrates====

The packet size, which you set when you generate your EPG, should match the bitrate in which you intend to broadcast it. If the packet size is too large, your EPG will not be broadcasted. If the packet size is too small, your EPG will (probably) be broadcasted, but it will be slower than necessary, because more space will be used for packet headers and maybe partly empty data packets. I will recommend these values:

{| class="wikitable"
! Bitrate
! Packet size
|-
| 8
| 24
|-
| 16
| 48
|-
| 24
| 72
|-
| 32
| 96
|-
| 48
| 72
|-
| 64
| 96
|}

====Broadcasting your EPG====

To broadcast your EPG using ODR-DabMux, create a packet data service in your mux.conf like in this example:

In the services section:

srv-epg {
label "EPG"
shortlabel "EPG"
; the service-ID consists of 8 hex digits for packet data services. Usually the first two digits will
; be the same as your ECC, and the third digit will be the same as the first digit in your Ensemble Id.
id 0xe1912345
}

In the subchannels section:

sub-epg {
; type packet or enhancedpacket can be used for EPG.
type enhancedpacket
; if you change the bitrate, remember to also change the packet size accordingly (see above) and generate your EPG again.
bitrate 16
protection-profile EEP_A
protection 3
; inputuri is the path and filename for your output file from generate-epg
inputuri "/home/user/odr-radioepg-bridge-master/output.dat"
inputproto file
}

And in the components section:

comp-epg {
type 60
service srv-epg
subchannel sub-epg
figtype 0x7
; The address must be the same as your packet address set when you generate the EPG (default value is 1).
address 0x1
datagroup true
}

That's it. Now (re)start your ODR-DabMux, and your EPG should be broadcasted.

===Updating your EPG automatically every day===

To be written....

===Some problems and solutions===

====Local variable 'ecc' referenced before assignment====

For some domains, lookup will cause the script to fail with error message "local variable 'ecc' referenced before assignment" if the domain has no _radiotag._tcp SRV record.

You can get around this by opening this file in a text editor:
/usr/local/lib/python2.7/dist-packages/pyradiodns/rdns.py
and remove or comment out line 13 "('radiotag', 'TCP'),".

If the domain is not using RadioVIS, you might also have to remove line 14 "('radiovis', 'TCP'),", but I haven't experienced this myself.

Note: When you modify this file, you might have to remove '''rdns.pyc''' in the same folder to make sure that your changes are being used.

====Radio programmes listed on a wrong date====

I have observed that radio programmes beginning before noon (or all programmes on some receivers) were listed on a wrong date, one day before the correct date. My solution was to modify line 428 in this file:

/usr/local/lib/python2.7/dist-packages/spi/binary/__init__py

Here, "(timepoint.hour - 12)" should be changed to "timepoint.hour", so that line 428 will be:

jd = jdn + timepoint.hour / 24 + timepoint.minute / 1440 + timepoint.second / 86400

This should fix the daystamp issue.

Note: When you modify this file, you might have to remove '''__init__.pyc''' in the same folder to make sure that your changes are being used.

====Radio programmes listed with wrong timestamps if your time zone is not UTC====

I have observed that if the time zone is not UTC, all radio programmes were listed with wrong times. My solution was to make some modifications to this file:
/usr/local/lib/python2.7/dist-packages/spi/binary/__init__py

After line 419 ("bits.setall(False)") I have added the following two lines:

offset = (timepoint.utcoffset().days * 86400 + timepoint.utcoffset().seconds) + (timepoint.dst().days * 86400 + timepoint.dst().days)
timepoint=timepoint - timedelta(seconds=offset)

(The first line is taken from line 457, from where it can then be removed)

And after line 28 ("import sys"), I have added this line:

from datetime import timedelta

This should fix the timestamp issue.

Note: When you modify this file, you might have to remove '''__init__.pyc''' in the same folder to make sure that your changes are being used.

===Other observations===

* According to specs, logo slides in DAB EPG must be PNG. Although JPG is allowed in hybrid radio SPI, JPG logos will not be added to your DAB EPG. Be sure that your logos (up to 320x240) are PNG.
* Programme descriptions (shortDescription) seem to be processed but not shown. Perhaps we will have to look a little further into this.

RaspDAB/Automate operation with Supervisor

2018-07-11T14:32:14Z

Nickpiggott: /* The contents of the configuration file */

== Installing Supervisor ==

It is time to make the operation automatic, such that when you power up the Raspberry Pi it will start the encoders and the multiplexer and deliver a multiplexed stream to the EasyDAB board.

To do so we use a software package called supervisor (extended information can be found at http://supervisord.org). We first need to install it with

$ sudo apt-get install supervisor

This will probably also install python-meld3 as it needs that package to function correctly.

== Supervisor configuration files folder ==

In this manual we will put the supervisor configuration files in a folder config in the user's home directory. If you want to put this elsewhere you need to make appropriate changes to the commands shown here. You can do this from a terminal window with

$ mkdir config

or from the graphical file manager. In this folder we make 2 subfolders, supervisor and mux:

$ chdir config
$ mkdir supervisor
$ mkdir mux

Again, you can also do this with the graphical filemanager.

Now we can make the configuration file for program srv1 (the name is arbitrary, you can use your own names to make identification of the stations easy). Do this for all stations that you want include in the ensemble.

== The contents of the configuration file ==

Now let's have a look at the configuration file for the encoders. The following are examples:

[program:enc-srv1]
# DAB encoding using odr-audioenc
command=/usr/local/bin/odr-audioenc -v [URL of audio stream] -C 200 -b 64 -r 48000 -c 2 -o tcp://localhost:59001 -D -L --audio-resampler=samplerate -L --src-converter-type=0 -p 58 -P /tmp/srv1-pad.fifo
autostart=true
autorestart=true
startretries=100
priority=10
stderr_logfile=/var/log/supervisor/enc-srv1.log
stdout_logfile=/var/log/supervisor/enc-srv1.log

[program:pad-srv1]
# PAD encoding using odr-padenc
command=/usr/local/bin/odr-padenc -o /tmp/srv1-pad.fifo -p 58 -t /home/[UserID]/PAD/srv1/DLS/DLS1.txt -d /home/[UserID]/PAD/srv1/MOT
autostart=true
autorestart=true
startretries=100
priority=10
stderr_logfile=/var/log/supervisor/pad-srv1.log
stdout_logfile=/var/log/supervisor/pad-srv1.log

So you define a name for the program that supervisor uses to identify the process it governs. In this case 2 programs, the audio encoder and PAD encoder for station srv1.

You declare the command line as if you would invoke the program from a command line in a terminal window. Note that we don't use the more verbose reporting, as this would all be put in the log file, which is not necessary. The next 2 lines tell the supervisor program to start the program automatically, and also restart it when it stops. The number of startretries may seem high, but this is to ensure the audio encoder makes a sufficient number of retries when the connection to the stream server is temporarily lost. Then you can declare the priority, which in our case should all be the same - perhaps with the exception of the multiplexer. And you provide the location of the log files, in this case just one file in which both error and normal log messages are collected.

Make similar files for each station, and put these in the config/supervisor folder.

The configuration file for the multiplexer is similar:

[program:mux]
command=/usr/local/bin/odr-dabmux -e /home/[UserID]/config/mux/dab.mux
autostart=true
autorestart=true
priority=100
stderr_logfile=/var/log/supervisor/mux.log
stdout_logfile=/var/log/supervisor/mux.log

Note we give this priority 100 to delay the start of the multiplexer to give the processor time to start the NTP protocol and update the time.

=== Special Note for Commands that start Child Processes ===

In certain situations, your command may need to start more than one process. For example:

command=bash -c "rtpdump -F payload 239.192.1.1/5004 | sox -t raw -e signed-integer -r 48000 -c 2 -b 24 -B /dev/stdin -t raw --no-dither -r 48000 -c 2 -b 16 -L /dev/stdout gain 4 | odr-audioenc --format=raw --dab --bitrate=128 --dabmode=j --dabpsy=2 --pad=24 --pad-fifo=/home/dabsys/site/mot/sam.mot --input=/dev/stdin --output=tcp://127.0.0.1:9010"
stopasgroup=true

This composite command extracts linear audio from a multicast source (such as Telos Alliance "Livewire" system), piping the audio to sox to convert the audio format and levels and then piping onwards to the odr-audioenc process.

This scenario requires special handling:
* The entire composite command should be specified within the correct shell - in this case, bash. This prevents parsing confusion.
* An additional line is added to the configuration - [http://supervisord.org/configuration.html stopasgroup=true]. This tells supervisor to stop this process AND all the child processes it has spawned. If you don't do this, you'll end up with orphaned sox and odr-audioenc processes, which will continue to stream silent packets to the destination.

== Creating symbolic links ==

For each radio program that will be part of the multiplex ensemble you need to create a symbolic link into the /etc/supervisor/conf.d/ folder. This is where supervisor will look for the configuration files. Providing symbolic links will point the program to the files we just created, so supervisor will know the parameters for the audio and PAD encoders and the multiplexer.

Now we can make the symbolic links (assuming 'odr' is your username):

$ sudo ln -s /home/odr/config/supervisor/srv1.conf /etc/supervisor/conf.d/srv1.conf

for the configuration file for program srv1. You should do this for all stations you want to include in the multiplex and the multiplex program configuration file itself.

== Getting Supervisor to work ==

For every change you make to the configuration files you need to call supervisorctl to reread and update its configuration:

$ sudo supervisorctl reread
$ sudo supervisorctl update

This will start supervisord and install it as a deamon, so it will automatically start from now on and start/restart the programs. All services are launched from supervisor, you don't need to start them manually anymore.

To show status of all services :

$ sudo supervisorctl status

To [stop|start|restart] a service :

$ sudo supervisorctl [stop|start|restart] service-name

To apply change after change anything in /home/[UserID]/config/supervisor/ file you need to call supervisor to reread and update configuration.

If you simply type

sudo supervisorctl

this will not revert to the command prompt, but you will be able to monitor the supervisor status and issue the commands directly.

Supervisor redirects all logs from the tools to files in /var/log/supervisor/ You may need to ensure yourself that this directory exists. The logs will get rotated according to the policy defined by your distribution. More details in the child logging section of the documentation. Please refer to the official supervisor documentation for more details.

If you have correctly installed all programs and configured them correctly you will now have a micro DAB transmitter, with the audio encoding, PAD encoding and multiplexer in a single Raspberry Pi and the modulator in the EasyDAB v2 board, that will automatically start to encode and multiplex and subsequently modulate and transmit the DAB ensemble as soon as you provide a supply voltage. It may take about a minute for the whole process to start, but once it does it will continue until you remove the supply voltage again.