OpenDigitalRadio - User contributions [en]

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

2020-09-04T03:27:41Z

Ubr: Altered the section about using a named fifo to explain when it's necessary and when not. Also adjusted the file names in that section, new names with spi instead of epg.

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.
* 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-08-03T23:43:38Z

Ubr: Added installation of python setuptools in step 5 for installation of pyradiodns

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 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-26T00:50:02Z

Ubr:

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 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 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-23T22:21:13Z

Ubr: Scripts have been moved to Opendigitalradio in Github, and python pip is not used anymore. The section about problems and solutions is removed, because the mentioned problems have been fixed.

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 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.

* 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-21T14:53:01Z

Ubr: Finished the section about updating the 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===

====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 you 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 discribed 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 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-13T05:13:24Z

Ubr:

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
sudo ln -s /home/user/python-dabmsc-master/bin/decode /usr/bin/decode

(If your folder is not /home/user/python-dabmsc-master, use your_path/bin/decode in the last command line above).

====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.

User:Ubr

2020-07-12T17:23:45Z

Ubr: Ubr moved page User:Ubr to How to install odr-radioepg-bridge in Debian Jessie: Was created without a title

#REDIRECT [[How to install odr-radioepg-bridge in Debian Jessie]]

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

2020-07-12T17:23:44Z

Ubr: Ubr moved page User:Ubr to How to install odr-radioepg-bridge in Debian Jessie: Was created without a title

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

2020-07-12T17:18:15Z

Ubr: How to install odr-radioepg-bridge on Debian Jessie

How to install CRC DAB+ transmission chain from scratch in Ubuntu 11.04

2013-05-23T23:39:29Z

Ubr: /* Introduction */

Howto by Ulrik Brinck on CRC DAB+ installation on Ubuntu 11.04
===Introduction===

How to install all the needed software for transmitting DAB+ from scratch on Ubuntu 11.04. Some of it was absolutely not straight-forward in this Linux distro, but with good help from particularly Pascal Charest in the mailing list (thank you Pascal!), I succeeded in the end. So here, I will describe step-by-step how it can be done.

'''Addition, 2013''': This setup has been reported '''not''' to work with the latest generation of the WBX board (WBX revision 3).

===Notes===

Please note:
* The OS in my case is Ubuntu 11.04, 32 bit version, standard version (not the server version). Hardware is Ettus USRP1 and WBX daughterboard. I have not tried it with other OS or hardware.
* I only intend to describe how to install all the software, not how to use it after installation. But how to use it is pretty much the same as on the mmbTools live cd, based on Ubuntu 9.04. Note however, that crc-dabmod, crc-dwap.py and crc-dabplus are installed with their names in lower case, so they must be called with lower case names also in your shell script.
* You will need to know how to unpack a tarball (.tar.gz og .tar.bz2 file). For tar.gz it's "tar xvzf package.tar.gz", and for tar.bz2 it's "tar xvjf package.tar.bz2".
* I installed on a brand new Ubuntu 11.04 installation after installing all the OS updates offered by the Update Manager.
* There might be some of it which can be done in an easier way, but I'm not that experienced with Linux, and this is what worked for me.

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

====Step 1: Installation of Gnuradio 3.3.0====
This is needed for USRP1 with WBX.
# First "sudo apt-get build-dep gnuradio" (takes quite some time).
# Then go to this page: http://gnuradio.org/redmine/projects/gnuradio/wiki/UbuntuInstall and install all the dependencies as mentioned in the first step there (for Ubuntu 11.04). Do NOT continue with the next step (Installing GNU Radio) on that page. Instead -
# Download and unpack this file: http://ftp.gnu.org/gnu/gnuradio/gnuradio-3.3.0.tar.gz (by default it goes to a "Downloads" folder in your homedir, this is fine).
# Before you can compile it, you will need to apply a patch as described here: http://lists.nongnu.org/archive/html/discuss-gnuradio/2011-05/msg00108.html But it was not so easy to apply the patch directly from that page, so you might want to just patch it manually instead (in fact, that's what I did) : To patch it manually, open ~/Downloads/gnuradio-3.3.0/usrp2/host/lib/usrp2.cc with a text editor. In line 41, 43 and 73 change "usrp2::usrp2" into just "usrp2". That's all, then save and close.
# Now you can compile it as described in the file ~/Downloads/gnuradio-3.3.0/INSTALL . It's "./configure", "make", "make check" and "sudo make install".
# Then back to this page: http://gnuradio.org/redmine/projects/gnuradio/wiki/UbuntuInstall and scroll down to "Configuring USRP support" and perform the steps mentioned there. I chose to reboot the pc after this, to be absolutely sure that the USRP support would work. Note: The section also mentions that an UHD driver can be installed from the ettus.com homepage, but you don't need to do that.
# At the end of the "Configuring USRP support" section of that page, there are some test you can perform to test that the USRP is available to Ubuntu. The "./usrp_benchmark_usb.py" test fails, but it doesn't matter in our case. The "./test_usrp_standard_tx" should however go well and a.o. show that your daughterboard is WBX (if that is actually what it is).

====Step 2: Crc-DabMod and CRC-Dwap.py====
# Download CRC-DabMod from the CRC homepage, http://mmbtools.crc.ca/content/view/44/71/ , unpack it and compile as described in ~/Downloads/crc-dabmod-0.2.0/INSTALL . It's "./configure --disable-debug", "make" and "sudo make install".
# Then go here http://mmbtools.crc.ca/content/view/37/63/ and download CRC-Dwap.py for Gnuradio 3.3 .
# Navigate to /usr/local/bin and replace the existing crc-dwap.py with the new one that you have just downloaded (rename it into crc-dwap.py (lower case) so that it's name becomes exactly the same as the old one). Then set it's permissions: "sudo chmod a+x crc-dwap.py".

====Step 3: Crc-DabMux and Libfec====
# First some necessary software: "sudo apt-get install devscripts". Note: This will also install a mail server (postfix) and ask you for a configuration, but, unless you actually want a mail server, you can just select "OK" and then "No configuration" (do not just close the terminal window).
# And "sudo apt-get install debhelper" (you might already have this).
# Go to http://mmbtools.crc.ca/content/view/39/65/ and download and unpack CRC-DabMux and Libfec 3.0.1-2.
# Inside the Libfec 3.0.1-2 package are some more packages and a README file. Be sure to do EXACTLY as described in that README file. After that, also do "sudo dpkg -i ../libfec3-dev_3.0.1-*.deb" (thanks to Chaim Zax for this addition).
# Compile CRC-DabMux as described in ~/Downloads/crc-dabmux-0.3.0.4/INSTALL. It's just the usual way, "./configure", "make" and "sudo make install".

====Step 4: Buffer software====
On the mmbTools live cd, the "bfr" buffer is used between CRC-DabMux and CRC-DabMod. But on this Ubuntu 11.04 system, my experience is, that bfr sometimes stops working and hangs the whole system. Instead I use mbuffer, which works better for me:
# "sudo apt-get install mbuffer".

====Step 5: CRC-DabPlus====
Note: CRC-DabPlus is not free, because of HE-AAC royalty, but can be bought from CRC. If you don't have or want CRC-DabPlus, you can skip this step.
Note: Together with CRC-DabPlus came HASP (for the software protection dongle) and Libfec. You already installed Libfec in step 3, so you don't have to do it again now.
* Install HASP as described in the README-html which came with CRC-DabPlus (sudo dpkg -i *.deb).
* As mentioned on http://opendigitalradio.org/index.php/CRC-dabplus there is a bit more to do, and for me it was a bit different in Ubuntu 11.04, this is what works for me: Open /etc/rc.local with a text editor (with root privileges, for example "sudo gedit /etc/rc.local") and insert the following lines before the existing "exit 0":
sudo mount --bind /dev/bus /proc/bus
sudo ln -s /sys/kernel/debug/usb/devices /proc/bus/usb/devices
sudo /usr/sbin/aksusbd restart

* Insert the dongle in an empty USB slot and reboot the computer. License for CRC-DabPlus is now ready.
* Install CRC-DabPlus as described in the README.html.

====Step 6: AudioScience ASI504x sound cards====
In the README.html which came with CRC-DabPlus is described how to use it together with AudioScience sound cards. It also tells how to install the AudioScience cards, but this is NOT necessary in Ubuntu 11.04. It already works "out of the box". However the GUI sound control panel does not work correctly with these cards, so if you need to change it's configuration, you must use the non-GUI alsamixer (type "alsamixer" in a terminal window).

That's it. Now you're ready to set up your DAB multiplex.

How to install CRC DAB+ transmission chain from scratch in Ubuntu 11.04

2012-04-18T00:04:37Z

Ubr: /* Step 1: Installation of Gnuradio 3.3.0 */

Howto by Ulrik Brinck on CRC DAB+ installation on Ubuntu 11.04
===Introduction===

How to install all the needed software for transmitting DAB+ from scratch on Ubuntu 11.04. Some of it was absolutely not straight-forward in this Linux distro, but with good help from particularly Pascal Charest in the mailing list (thank you Pascal!), I succeeded in the end. So here, I will describe step-by-step how it can be done.

===Notes===

Please note:
* The OS in my case is Ubuntu 11.04, 32 bit version, standard version (not the server version). Hardware is Ettus USRP1 and WBX daughterboard. I have not tried it with other OS or hardware.
* I only intend to describe how to install all the software, not how to use it after installation. But how to use it is pretty much the same as on the mmbTools live cd, based on Ubuntu 9.04. Note however, that crc-dabmod, crc-dwap.py and crc-dabplus are installed with their names in lower case, so they must be called with lower case names also in your shell script.
* You will need to know how to unpack a tarball (.tar.gz og .tar.bz2 file). For tar.gz it's "tar xvzf package.tar.gz", and for tar.bz2 it's "tar xvjf package.tar.bz2".
* I installed on a brand new Ubuntu 11.04 installation after installing all the OS updates offered by the Update Manager.
* There might be some of it which can be done in an easier way, but I'm not that experienced with Linux, and this is what worked for me.

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

====Step 1: Installation of Gnuradio 3.3.0====
This is needed for USRP1 with WBX.
# First "sudo apt-get build-dep gnuradio" (takes quite some time).
# Then go to this page: http://gnuradio.org/redmine/projects/gnuradio/wiki/UbuntuInstall and install all the dependencies as mentioned in the first step there (for Ubuntu 11.04). Do NOT continue with the next step (Installing GNU Radio) on that page. Instead -
# Download and unpack this file: http://ftp.gnu.org/gnu/gnuradio/gnuradio-3.3.0.tar.gz (by default it goes to a "Downloads" folder in your homedir, this is fine).
# Before you can compile it, you will need to apply a patch as described here: http://lists.nongnu.org/archive/html/discuss-gnuradio/2011-05/msg00108.html But it was not so easy to apply the patch directly from that page, so you might want to just patch it manually instead (in fact, that's what I did) : To patch it manually, open ~/Downloads/gnuradio-3.3.0/usrp2/host/lib/usrp2.cc with a text editor. In line 41, 43 and 73 change "usrp2::usrp2" into just "usrp2". That's all, then save and close.
# Now you can compile it as described in the file ~/Downloads/gnuradio-3.3.0/INSTALL . It's "./configure", "make", "make check" and "sudo make install".
# Then back to this page: http://gnuradio.org/redmine/projects/gnuradio/wiki/UbuntuInstall and scroll down to "Configuring USRP support" and perform the steps mentioned there. I chose to reboot the pc after this, to be absolutely sure that the USRP support would work. Note: The section also mentions that an UHD driver can be installed from the ettus.com homepage, but you don't need to do that.
# At the end of the "Configuring USRP support" section of that page, there are some test you can perform to test that the USRP is available to Ubuntu. The "./usrp_benchmark_usb.py" test fails, but it doesn't matter in our case. The "./test_usrp_standard_tx" should however go well and a.o. show that your daughterboard is WBX (if that is actually what it is).

====Step 2: Crc-DabMod and CRC-Dwap.py====
# Download CRC-DabMod from the CRC homepage, http://mmbtools.crc.ca/content/view/44/71/ , unpack it and compile as described in ~/Downloads/crc-dabmod-0.2.0/INSTALL . It's "./configure --disable-debug", "make" and "sudo make install".
# Then go here http://mmbtools.crc.ca/content/view/37/63/ and download CRC-Dwap.py for Gnuradio 3.3 .
# Navigate to /usr/local/bin and replace the existing crc-dwap.py with the new one that you have just downloaded (rename it into crc-dwap.py (lower case) so that it's name becomes exactly the same as the old one). Then set it's permissions: "sudo chmod a+x crc-dwap.py".

====Step 3: Crc-DabMux and Libfec====
# First some necessary software: "sudo apt-get install devscripts". Note: This will also install a mail server (postfix) and ask you for a configuration, but, unless you actually want a mail server, you can just select "OK" and then "No configuration" (do not just close the terminal window).
# And "sudo apt-get install debhelper" (you might already have this).
# Go to http://mmbtools.crc.ca/content/view/39/65/ and download and unpack CRC-DabMux and Libfec 3.0.1-2.
# Inside the Libfec 3.0.1-2 package are some more packages and a README file. Be sure to do EXACTLY as described in that README file. After that, also do "sudo dpkg -i ../libfec3-dev_3.0.1-*.deb" (thanks to Chaim Zax for this addition).
# Compile CRC-DabMux as described in ~/Downloads/crc-dabmux-0.3.0.4/INSTALL. It's just the usual way, "./configure", "make" and "sudo make install".

====Step 4: Buffer software====
On the mmbTools live cd, the "bfr" buffer is used between CRC-DabMux and CRC-DabMod. But on this Ubuntu 11.04 system, my experience is, that bfr sometimes stops working and hangs the whole system. Instead I use mbuffer, which works better for me:
# "sudo apt-get install mbuffer".

====Step 5: CRC-DabPlus====
Note: CRC-DabPlus is not free, because of HE-AAC royalty, but can be bought from CRC. If you don't have or want CRC-DabPlus, you can skip this step.
Note: Together with CRC-DabPlus came HASP (for the software protection dongle) and Libfec. You already installed Libfec in step 3, so you don't have to do it again now.
* Install HASP as described in the README-html which came with CRC-DabPlus (sudo dpkg -i *.deb).
* As mentioned on http://opendigitalradio.org/index.php/CRC-dabplus there is a bit more to do, and for me it was a bit different in Ubuntu 11.04, this is what works for me: Open /etc/rc.local with a text editor (with root privileges, for example "sudo gedit /etc/rc.local") and insert the following lines before the existing "exit 0":
sudo mount --bind /dev/bus /proc/bus
sudo ln -s /sys/kernel/debug/usb/devices /proc/bus/usb/devices
sudo /usr/sbin/aksusbd restart

* Insert the dongle in an empty USB slot and reboot the computer. License for CRC-DabPlus is now ready.
* Install CRC-DabPlus as described in the README.html.

====Step 6: AudioScience ASI504x sound cards====
In the README.html which came with CRC-DabPlus is described how to use it together with AudioScience sound cards. It also tells how to install the AudioScience cards, but this is NOT necessary in Ubuntu 11.04. It already works "out of the box". However the GUI sound control panel does not work correctly with these cards, so if you need to change it's configuration, you must use the non-GUI alsamixer (type "alsamixer" in a terminal window).

That's it. Now you're ready to set up your DAB multiplex.

DAB+ script and infrastructure used for Kanal Plus ensemble in Denmark

2012-02-24T15:02:23Z

Ubr:

Here's the script by Ulrik Brinck of Kanal Plus for [http://www.wohnort.org/DAB/denmark.html#Local local ensemble in Denmark]

The ensemble consists of 9 DAB+ programmes, some of them with DLS. The full set of CRC mmbTools is used with crc-dabplus for DAB+ encoding, crc-dabmux for multiplexing and crc-dabmod for OFDM modulation.

The hardware setup is made of:
*Intel Core i7-2600 4x3.40Ghz PC running Ubuntu Desktop 11.04, 32 bit version
*2 AudioScience ASI5042 soundcards
*Ettus USRP1 with WBX daughterboard
*Power amplifier from Res-Ingenium, Italy
*Cavity filter from Telmec Broadcasting, Italy
*Antenna from vhfteknik.se, Sweden

[[Media:Danish DAB+ grass roots trial (Kanal Plus).pdf|Pictures from the setup]] with PC, amplifier, antenna (pics by Niels Dreijer)

===Script===

#!/bin/sh

DABPLUS=crc-dabplus

#First kill any eventual old instances of the software

killall CRC-DabMux
killall CRC-DabMod
killall CRC-Dwap.py
killall $DABPLUS
killall mbuffer

sleep 3

#Delete old fifo's and make new ones, just to be sure to avoid problems at startup if e.g. a bit rate has been changed

rm -f fifoer/fifo*

for id in 1 2 3 4 5 6 7 8; do
[ -e fifo$id ] || mkfifo fifoer/fifo$id
done

#Start the multiplexer, modulator and wave player

CRC-DabMux -c 0xE1 -i 0x9101 -L "NivaaDAB" -l "NivaaDAB" \
-F "diverse/testcd56.dab" -b 56 -S -i 0x9101 -y 0 -L "Forsoegskanal" -l "Forsoeg" -C \
-F fifoer/fifo1 -k -b 144 -S -i 0x9102 -y 27 -L "Retro-Radio" -l "Retro" -C \
-F fifoer/fifo2 -k -b 88 -S -i 0x9103 -y 11 -L "Rockkanalen" -l "Rockkanl" -C \
-F fifoer/fifo3 -k -b 88 -S -i 0x9104 -y 9 -L "US Radio" -l "US Radio" -C \
-F fifoer/fifo4 -k -b 88 -S -i 0x9105 -y 9 -L "Humleborg,R.Nord" -l "Hmleborg" -C \
-F fifoer/fifo5 -k -b 88 -S -i 0x9106 -y 10 -L "RadioHLR" -l "RadioHLR" -C \
-F fifoer/fifo6 -k -b 88 -S -i 0x9107 -y 9 -L "Radio 10FM" -l "10FM" -C \
-F fifoer/fifo7 -k -b 48 -S -i 0x9108 -y 9 -L "Interviewkanalen" -l "Intervie" -C \
-F fifoer/fifo8 -k -b 88 -S -i 0x9109 -y 10 -L "Radio Halsnaes" -l "Halsnaes" -C \
-O fifo:///dev/stdout | \
crc-dabmod -g2 -r3200000 -c128000000 | \
mbuffer -m 32m -P 25 | \
crc-dwap.py -r3200000 -f204640000 -g-14 -u &

sleep 3

#Start the encoders
#There are two ASI5042 sound cards, which are identified as hw:2 and hw:3. Each of them have 4 stereo inputs.

$DABPLUS -g -i card://hw:3,0,0 -b 144 -d tcpserver://:49102 -p 28 -t dls | mbuffer -m 100k -P 100 > fifoer/fifo1 &
$DABPLUS -g -i card://hw:2,0,2 -b 88 -d tcpserver://:49103 -p 28 -t dls | mbuffer -m 100k -P 100 > fifoer/fifo2 &
$DABPLUS -g -i card://hw:2,0,3 -b 88 -d tcpserver://:49104 -p 28 -t dls | mbuffer -m 100k -P 100 > fifoer/fifo3 &
$DABPLUS -g -i card://hw:3,0,1 -b 88 | mbuffer -m 100k -P 100 > fifoer/fifo4 &
$DABPLUS -g -i card://hw:3,0,2 -b 88 | mbuffer -m 100k -P 100 > fifoer/fifo5 &
$DABPLUS -g -i card://hw:3,0,3 -b 88 | mbuffer -m 100k -P 100 > fifoer/fifo6 &
$DABPLUS -g -i card://hw:2,0,1 -b 48 -d tcpserver://:49108 -p 28 -t dls | mbuffer -m 100k -P 100 > fifoer/fifo7 &
$DABPLUS -g -i card://hw:2,0,0 -b 88 | mbuffer -m 100k -P 100 > fifoer/fifo8 &

wait

DAB+ script and infrastructure used for Kanal Plus ensemble in Denmark

2012-02-24T15:01:30Z

Ubr:

Here's the script by Ulrik Brinck of Kanal Plus for [http://www.wohnort.org/DAB/denmark.html#Local local ensemble in Denmark]

The ensemble consists of 4 DAB+ programmes with DLS. The full set of CRC mmbTools is used with crc-dabplus for DAB+ encoding, crc-dabmux for multiplexing and crc-dabmod for OFDM modulation.

The hardware setup is made of:
*Intel Core i7-2600 4x3.40Ghz PC running Ubuntu Desktop 11.04, 32 bit version
*2 AudioScience ASI5042 soundcards
*Ettus USRP1 with WBX daughterboard
*Power amplifier from Res-Ingenium, Italy
*Cavity filter from Telmec Broadcasting, Italy
*Antenna from vhfteknik.se, Sweden

[[Media:Danish DAB+ grass roots trial (Kanal Plus).pdf|Pictures from the setup]] with PC, amplifier, antenna (pics by Niels Dreijer)

===Script===

#!/bin/sh

DABPLUS=crc-dabplus

#First kill any eventual old instances of the software

killall CRC-DabMux
killall CRC-DabMod
killall CRC-Dwap.py
killall $DABPLUS
killall mbuffer

sleep 3

#Delete old fifo's and make new ones, just to be sure to avoid problems at startup if e.g. a bit rate has been changed

rm -f fifoer/fifo*

for id in 1 2 3 4 5 6 7 8; do
[ -e fifo$id ] || mkfifo fifoer/fifo$id
done

#Start the multiplexer, modulator and wave player

CRC-DabMux -c 0xE1 -i 0x9101 -L "NivaaDAB" -l "NivaaDAB" \
-F "diverse/testcd56.dab" -b 56 -S -i 0x9101 -y 0 -L "Forsoegskanal" -l "Forsoeg" -C \
-F fifoer/fifo1 -k -b 144 -S -i 0x9102 -y 27 -L "Retro-Radio" -l "Retro" -C \
-F fifoer/fifo2 -k -b 88 -S -i 0x9103 -y 11 -L "Rockkanalen" -l "Rockkanl" -C \
-F fifoer/fifo3 -k -b 88 -S -i 0x9104 -y 9 -L "US Radio" -l "US Radio" -C \
-F fifoer/fifo4 -k -b 88 -S -i 0x9105 -y 9 -L "Humleborg,R.Nord" -l "Hmleborg" -C \
-F fifoer/fifo5 -k -b 88 -S -i 0x9106 -y 10 -L "RadioHLR" -l "RadioHLR" -C \
-F fifoer/fifo6 -k -b 88 -S -i 0x9107 -y 9 -L "Radio 10FM" -l "10FM" -C \
-F fifoer/fifo7 -k -b 48 -S -i 0x9108 -y 9 -L "Interviewkanalen" -l "Intervie" -C \
-F fifoer/fifo8 -k -b 88 -S -i 0x9109 -y 10 -L "Radio Halsnaes" -l "Halsnaes" -C \
-O fifo:///dev/stdout | \
crc-dabmod -g2 -r3200000 -c128000000 | \
mbuffer -m 32m -P 25 | \
crc-dwap.py -r3200000 -f204640000 -g-14 -u &

sleep 3

#Start the encoders
#There are two ASI5042 sound cards, which are identified as hw:2 and hw:3. Each of them have 4 stereo inputs.

$DABPLUS -g -i card://hw:3,0,0 -b 144 -d tcpserver://:49102 -p 28 -t dls | mbuffer -m 100k -P 100 > fifoer/fifo1 &
$DABPLUS -g -i card://hw:2,0,2 -b 88 -d tcpserver://:49103 -p 28 -t dls | mbuffer -m 100k -P 100 > fifoer/fifo2 &
$DABPLUS -g -i card://hw:2,0,3 -b 88 -d tcpserver://:49104 -p 28 -t dls | mbuffer -m 100k -P 100 > fifoer/fifo3 &
$DABPLUS -g -i card://hw:3,0,1 -b 88 | mbuffer -m 100k -P 100 > fifoer/fifo4 &
$DABPLUS -g -i card://hw:3,0,2 -b 88 | mbuffer -m 100k -P 100 > fifoer/fifo5 &
$DABPLUS -g -i card://hw:3,0,3 -b 88 | mbuffer -m 100k -P 100 > fifoer/fifo6 &
$DABPLUS -g -i card://hw:2,0,1 -b 48 -d tcpserver://:49108 -p 28 -t dls | mbuffer -m 100k -P 100 > fifoer/fifo7 &
$DABPLUS -g -i card://hw:2,0,0 -b 88 | mbuffer -m 100k -P 100 > fifoer/fifo8 &

wait

How to install latest version of gnuradio with CRC MMBtools live CD

2011-10-29T02:22:14Z

Ubr:

If you have installed Ubuntu and CRC mmbtools CD (beta 9 or older), you cannot use the WBX daughterboard because you need the latest version of gnuradio.
In this case you can follow these steps to remove the old gnuradio and compile/install the new one. (taken from CRC Workshop organised at EBU)

First open /etc/apt/sources.list with a text editor, for example:

sudo gedit /etc/apt/sources.list

Inside this file, change all the URL's from http://(something).ubuntu.com/ubuntu into http://old-releases.ubuntu.com/ubuntu . Then save and close.

sudo apt-get update

sudo apt-get remove -y gnuradio gnuradio-doc libgnuradio libgnuradio-core libgnuradio-omnithread libgruel python-gnuradio-core libusrp usrp-doc python-wxgtk2.6

sudo apt-get -y install git-core autoconf libtool python-dev swig libfftw3-dev libcppunit-dev libusb-dev libboost1.37-dev guile-1.8-dev sdcc-nf libsdl1.2-dev libgsl0-dev

wget http://ftp.gnu.org/gnu/gnuradio/gnuradio-3.3.0.tar.gz
tar xzf gnuradio-3.3.0.tar.gz
cd gnuradio-3.3.0
./configure --prefix=/usr --sysconfdir=/etc
make -j2
sudo make install
sudo ldconfig
sudo ln -s gnuradio-companion /usr/bin/grc
sudo ln -s libgruel.so /usr/lib/libgruel.so.0

How to install latest version of gnuradio with CRC MMBtools live CD

2011-10-29T01:33:27Z

Ubr:

If you have installed Ubuntu and CRC mmbtools CD (beta 9 or older), you cannot use the WBX daughterboard because you need the latest version of gnuradio.

In this case you can follow these steps to remove the old gnuradio and compile/install the new one. (taken from CRC Workshop organised at EBU)

sudo apt-get remove -y gnuradio gnuradio-doc libgnuradio libgnuradio-core libgnuradio-omnithread libgruel python-gnuradio-core libusrp usrp-doc python-wxgtk2.6

sudo apt-get -y install git-core autoconf libtool python-dev swig libfftw3-dev libcppunit-dev libusb-dev libboost1.37-dev guile-1.8-dev sdcc-nf libsdl1.2-dev libgsl0-dev

git clone http://gnuradio.org/git/gnuradio.git
cd gnuradio
git checkout v3.3.0
./bootstrap
./configure --prefix=/usr --sysconfdir=/etc
make -j2
sudo make install
sudo ldconfig
sudo ln -s gnuradio-companion /usr/bin/grc
sudo ln -s libgruel.so /usr/lib/libgruel.so.0

How to install CRC DAB+ transmission chain from scratch in Ubuntu 11.04

2011-10-13T21:58:51Z

Ubr: /* Step 3: Crc-DabMux and Libfec */

Howto by Ulrik Brinck on CRC DAB+ installation on Ubuntu 11.04
===Introduction===

How to install all the needed software for transmitting DAB+ from scratch on Ubuntu 11.04. Some of it was absolutely not straight-forward in this Linux distro, but with good help from particularly Pascal Charest in the mailing list (thank you Pascal!), I succeeded in the end. So here, I will describe step-by-step how it can be done.

===Notes===

Please note:
* The OS in my case is Ubuntu 11.04, 32 bit version, standard version (not the server version). Hardware is Ettus USRP1 and WBX daughterboard. I have not tried it with other OS or hardware.
* I only intend to describe how to install all the software, not how to use it after installation. But how to use it is pretty much the same as on the mmbTools live cd, based on Ubuntu 9.04. Note however, that crc-dabmod, crc-dwap.py and crc-dabplus are installed with their names in lower case, so they must be called with lower case names also in your shell script.
* You will need to know how to unpack a tarball (.tar.gz og .tar.bz2 file). For tar.gz it's "tar xvzf package.tar.gz", and for tar.bz2 it's "tar xvjf package.tar.bz2".
* I installed on a brand new Ubuntu 11.04 installation after installing all the OS updates offered by the Update Manager.
* There might be some of it which can be done in an easier way, but I'm not that experienced with Linux, and this is what worked for me.

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

====Step 1: Installation of Gnuradio 3.3.0====
This is needed for USRP1 with WBX.
# First "sudo apt-get build-dep gnuradio" (takes quite some time).
# Then go to this page: http://gnuradio.org/redmine/projects/gnuradio/wiki/UbuntuInstall and install all the dependencies as mentioned in the first step there (for Ubuntu 10.04 plus the additional line for 11.04). Do NOT continue with the next step (Installing GNU Radio) on that page. Instead -
# Download and unpack this file: http://ftp.gnu.org/gnu/gnuradio/gnuradio-3.3.0.tar.gz (by default it goes to a "Downloads" folder in your homedir, this is fine).
# Before you can compile it, you will need to apply a patch as described here: http://lists.nongnu.org/archive/html/discuss-gnuradio/2011-05/msg00108.html But it was not so easy to apply the patch directly from that page, so you might want to just patch it manually instead (in fact, that's what I did) : To patch it manually, open ~/Downloads/gnuradio-3.3.0/usrp2/host/lib/usrp2.cc with a text editor. In line 41, 43 and 73 change "usrp2::usrp2" into just "usrp2". That's all, then save and close.
# Now you can compile it as described in the file ~/Downloads/gnuradio-3.3.0/INSTALL . It's "./configure", "make", "make check" and "sudo make install".
# Then back to this page: http://gnuradio.org/redmine/projects/gnuradio/wiki/UbuntuInstall and scroll down to "Configuring USRP support" and perform the steps mentioned there. I chose to reboot the pc after this, to be absolutely sure that the USRP support would work. Note: The section also mentions that an UHD driver can be installed from the ettus.com homepage, but you don't need to do that.
# At the end of the "Configuring USRP support" section of that page, there are some test you can perform to test that the USRP is available to Ubuntu. The "./usrp_benchmark_usb.py" test fails, but it doesn't matter in our case. The "./test_usrp_standard_tx" should however go well and a.o. show that your daughterboard is WBX (if that is actually what it is).

====Step 2: Crc-DabMod and CRC-Dwap.py====
# Download CRC-DabMod from the CRC homepage, http://mmbtools.crc.ca/content/view/44/71/ , unpack it and compile as described in ~/Downloads/crc-dabmod-0.2.0/INSTALL . It's "./configure --disable-debug", "make" and "sudo make install".
# Then go here http://mmbtools.crc.ca/content/view/37/63/ and download CRC-Dwap.py for Gnuradio 3.3 .
# Navigate to /usr/local/bin and replace the existing crc-dwap.py with the new one that you have just downloaded (rename it into crc-dwap.py (lower case) so that it's name becomes exactly the same as the old one). Then set it's permissions: "sudo chmod a+x crc-dwap.py".

====Step 3: Crc-DabMux and Libfec====
# First some necessary software: "sudo apt-get install devscripts". Note: This will also install a mail server (postfix) and ask you for a configuration, but, unless you actually want a mail server, you can just select "OK" and then "No configuration" (do not just close the terminal window).
# And "sudo apt-get install debhelper" (you might already have this).
# Go to http://mmbtools.crc.ca/content/view/39/65/ and download and unpack CRC-DabMux and Libfec 3.0.1-2.
# Inside the Libfec 3.0.1-2 package are some more packages and a README file. Be sure to do EXACTLY as described in that README file. After that, also do "sudo dpkg -i ../libfec3-dev_3.0.1-*.deb" (thanks to Chaim Zax for this addition).
# Compile CRC-DabMux as described in ~/Downloads/crc-dabmux-0.3.0.4/INSTALL. It's just the usual way, "./configure", "make" and "sudo make install".

====Step 4: Buffer software====
On the mmbTools live cd, the "bfr" buffer is used between CRC-DabMux and CRC-DabMod. But on this Ubuntu 11.04 system, my experience is, that bfr sometimes stops working and hangs the whole system. Instead I use mbuffer, which works better for me:
# "sudo apt-get install mbuffer".

====Step 5: CRC-DabPlus====
Note: CRC-DabPlus is not free, because of HE-AAC royalty, but can be bought from CRC. If you don't have or want CRC-DabPlus, you can skip this step.
Note: Together with CRC-DabPlus came HASP (for the software protection dongle) and Libfec. You already installed Libfec in step 3, so you don't have to do it again now.
* Install HASP as described in the README-html which came with CRC-DabPlus (sudo dpkg -i *.deb).
* As mentioned on http://opendigitalradio.org/index.php/CRC-dabplus there is a bit more to do, and for me it was a bit different in Ubuntu 11.04, this is what works for me: Open /etc/rc.local with a text editor (with root privileges, for example "sudo gedit /etc/rc.local") and insert the following lines before the existing "exit 0":
sudo mount --bind /dev/bus /proc/bus
sudo ln -s /sys/kernel/debug/usb/devices /proc/bus/usb/devices
sudo /usr/sbin/aksusbd restart

* Insert the dongle in an empty USB slot and reboot the computer. License for CRC-DabPlus is now ready.
* Install CRC-DabPlus as described in the README.html.

====Step 6: AudioScience ASI504x sound cards====
In the README.html which came with CRC-DabPlus is described how to use it together with AudioScience sound cards. It also tells how to install the AudioScience cards, but this is NOT necessary in Ubuntu 11.04. It already works "out of the box". However the GUI sound control panel does not work correctly with these cards, so if you need to change it's configuration, you must use the non-GUI alsamixer (type "alsamixer" in a terminal window).

That's it. Now you're ready to set up your DAB multiplex.

DAB+ script and infrastructure used for Kanal Plus ensemble in Denmark

2011-10-06T13:23:58Z

Ubr:

Here's the script by Ulrik Brinck of Kanal Plus for [http://www.wohnort.org/DAB/denmark.html#Local local ensemble in Denmark]

The ensemble consists of 4 DAB+ programmes with DLS.

The hardware setup is made of:
*Intel Core i7-2600 4x3.40Ghz PC running Ubuntu Desktop 11.04, 32 bit version
*2 AudioScience ASI5042 soundcards
*Ettus USRP1 with WBX daughterboard
*Power amplifier from Res-Ingenium, Italy
*Cavity filter from Telmec, Italy
*Antenna from vhfteknik.se, Sweden

[[Media:Danish DAB+ grass roots trial (Kanal Plus).pdf|Pictures from the setup]] with PC, amplifier, antenna (pics by Niels Dreijer)

===Script===

#!/bin/sh

DABPLUS=crc-dabplus

killall CRC-DabMux
killall CRC-DabMod
killall CRC-Dwap.py
killall $DABPLUS
killall mbuffer

sleep 3

rm -f fifoer/fifo*

for id in 0 1 2 3 4 5 6 7 8; do
[ -e fifo$id ] || mkfifo fifoer/fifo$id
done

CRC-DabMux -c 0xE1 -i 0x9101 -L "NivaaDAB" -l "NivaaDAB" \
-F "diverse/testcd.dab" -b 64 -S -i 0x9101 -y 0 -L "Forsoegskanal" -l "Forsoeg" -C \
-F fifoer/fifo1 -k -b 144 -S -i 0x9102 -y 27 -L "Retro-Radio" -l "Retro" -C \
-F fifoer/fifo2 -k -b 144 -S -i 0x9103 -y 10 -L "Kanal Plus 90" -l "Plus 90" -C \
-F fifoer/fifo3 -k -b 88 -S -i 0x9104 -y 9 -L "US Radio" -l "US Radio" -C \
-O fifo:///dev/stdout | \
crc-dabmod -g2 -r3200000 -c128000000 | \
mbuffer -m 32m -P 25 | \
crc-dwap.py -r3200000 -f204640000 -g-14 -u &

sleep 3

$DABPLUS -g -i card://hw:3,0,0 -b 144 -d tcpserver://:49102 -p 28 -t dls | mbuffer -m 100k -P 100 > fifoer/fifo1 &
$DABPLUS -g -i card://hw:2,0,0 -b 144 -d tcpserver://:49103 -p 28 -t dls | mbuffer -m 100k -P 100 > fifoer/fifo2 &
$DABPLUS -g -i card://hw:2,0,3 -b 88 -d tcpserver://:49104 -p 28 -t dls | mbuffer -m 100k -P 100 > fifoer/fifo3 &

wait

How to install CRC DAB+ transmission chain from scratch in Ubuntu 11.04

2011-07-21T14:43:15Z

Ubr: /* Step 3: Crc-DabMux and Libfec */

Howto by Ulrik Brinck on CRC DAB+ installation on Ubuntu 11.04
===Introduction===

How to install all the needed software for transmitting DAB+ from scratch on Ubuntu 11.04. Some of it was absolutely not straight-forward in this Linux distro, but with good help from particularly Pascal Charest in the mailing list (thank you Pascal!), I succeeded in the end. So here, I will describe step-by-step how it can be done.

===Notes===

Please note:
* The OS in my case is Ubuntu 11.04, 32 bit version, standard version (not the server version). Hardware is Ettus USRP1 and WBX daughterboard. I have not tried it with other OS or hardware.
* I only intend to describe how to install all the software, not how to use it after installation. But how to use it is pretty much the same as on the mmbTools live cd, based on Ubuntu 9.04. Note however, that crc-dabmod, crc-dwap.py and crc-dabplus are installed with their names in lower case, so they must be called with lower case names also in your shell script.
* You will need to know how to unpack a tarball (.tar.gz og .tar.bz2 file). For tar.gz it's "tar xvzf package.tar.gz", and for tar.bz2 it's "tar xvjf package.tar.bz2".
* I installed on a brand new Ubuntu 11.04 installation after installing all the OS updates offered by the Update Manager.
* There might be some of it which can be done in an easier way, but I'm not that experienced with Linux, and this is what worked for me.

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

====Step 1: Installation of Gnuradio 3.3.0====
This is needed for USRP1 with WBX.
# First "sudo apt-get build-dep gnuradio" (takes quite some time).
# Then go to this page: http://gnuradio.org/redmine/projects/gnuradio/wiki/UbuntuInstall and install all the dependencies as mentioned in the first step there (for Ubuntu 10.04 plus the additional line for 11.04). Do NOT continue with the next step (Installing GNU Radio) on that page. Instead -
# Download and unpack this file: http://ftp.gnu.org/gnu/gnuradio/gnuradio-3.3.0.tar.gz (by default it goes to a "Downloads" folder in your homedir, this is fine).
# Before you can compile it, you will need to apply a patch as described here: http://lists.nongnu.org/archive/html/discuss-gnuradio/2011-05/msg00108.html But it was not so easy to apply the patch directly from that page, so you might want to just patch it manually instead (in fact, that's what I did) : To patch it manually, open ~/Downloads/gnuradio-3.3.0/usrp2/host/lib/usrp2.cc with a text editor. In line 41, 43 and 73 change "usrp2::usrp2" into just "usrp2". That's all, then save and close.
# Now you can compile it as described in the file ~/Downloads/gnuradio-3.3.0/INSTALL . It's "./configure", "make", "make check" and "sudo make install".
# Then back to this page: http://gnuradio.org/redmine/projects/gnuradio/wiki/UbuntuInstall and scroll down to "Configuring USRP support" and perform the steps mentioned there. I chose to reboot the pc after this, to be absolutely sure that the USRP support would work. Note: The section also mentions that an UHD driver can be installed from the ettus.com homepage, but you don't need to do that.
# At the end of the "Configuring USRP support" section of that page, there are some test you can perform to test that the USRP is available to Ubuntu. The "./usrp_benchmark_usb.py" test fails, but it doesn't matter in our case. The "./test_usrp_standard_tx" should however go well and a.o. show that your daughterboard is WBX (if that is actually what it is).

====Step 2: Crc-DabMod and CRC-Dwap.py====
# Download CRC-DabMod from the CRC homepage, http://mmbtools.crc.ca/content/view/44/71/ , unpack it and compile as described in ~/Downloads/crc-dabmod-0.2.0/INSTALL . It's "./configure --disable-debug", "make" and "sudo make install".
# Then go here http://mmbtools.crc.ca/content/view/37/63/ and download CRC-Dwap.py for Gnuradio 3.3 .
# Navigate to /usr/local/bin and replace the existing crc-dwap.py with the new one that you have just downloaded (rename it into crc-dwap.py (lower case) so that it's name becomes exactly the same as the old one). Then set it's permissions: "sudo chmod a+x crc-dwap.py".

====Step 3: Crc-DabMux and Libfec====
# First some necessary software: "sudo apt-get install devscripts". Note: This will also install a mail server (postfix) and ask you for a configuration, but, unless you actually want a mail server, you can just select "OK" and then "No configuration" (do not just close the terminal window).
# And "sudo apt-get install debhelper" (you might already have this).
# Go to http://mmbtools.crc.ca/content/view/39/65/ and download and unpack CRC-DabMux and Libfec 3.0.1-2.
# Inside the Libfec 3.0.1-2 package are some more packages and a README file. Be sure to do EXACTLY as described in that README file.
# Compile CRC-DabMux as described in ~/Downloads/crc-dabmux-0.3.0.4/INSTALL. It's just the usual way, "./configure", "make" and "sudo make install".

====Step 4: Buffer software====
On the mmbTools live cd, the "bfr" buffer is used between CRC-DabMux and CRC-DabMod. But on this Ubuntu 11.04 system, my experience is, that bfr sometimes stops working and hangs the whole system. Instead I use mbuffer, which works better for me:
# "sudo apt-get install mbuffer".

====Step 5: CRC-DabPlus====
Note: CRC-DabPlus is not free, because of HE-AAC royalty, but can be bought from CRC. If you don't have or want CRC-DabPlus, you can skip this step.
Note: Together with CRC-DabPlus came HASP (for the software protection dongle) and Libfec. You already installed Libfec in step 3, so you don't have to do it again now.
* Install HASP as described in the README-html which came with CRC-DabPlus (sudo dpkg -i *.deb).
* As mentioned on http://opendigitalradio.org/index.php/CRC-dabplus there is a bit more to do, and for me it was a bit different in Ubuntu 11.04, this is what works for me: Open /etc/rc.local with a text editor (with root privileges, for example "sudo gedit /etc/rc.local") and insert the following lines before the existing "exit 0":
sudo mount --bind /dev/bus /proc/bus
sudo ln -s /sys/kernel/debug/usb/devices /proc/bus/usb/devices
sudo /usr/sbin/aksusbd restart

* Insert the dongle in an empty USB slot and reboot the computer. License for CRC-DabPlus is now ready.
* Install CRC-DabPlus as described in the README.html.

====Step 6: AudioScience ASI504x sound cards====
In the README.html which came with CRC-DabPlus is described how to use it together with AudioScience sound cards. It also tells how to install the AudioScience cards, but this is NOT necessary in Ubuntu 11.04. It already works "out of the box". However the GUI sound control panel does not work correctly with these cards, so if you need to change it's configuration, you must use the non-GUI alsamixer (type "alsamixer" in a terminal window).

That's it. Now you're ready to set up your DAB multiplex.

CRC-dabplus

2011-07-11T22:39:38Z

Ubr: /* Licence key */

CRC-dabplus , HE-AAC DAB+ encoder from CRC.

It is not a free/open source product partly because HE-AAC is subject to royalty payment.

CRC is selling a licence for it. Please visit [http://mmbtools.crc.ca/content/view/40/66/ CRC page on CRC-dabplus] for more information

===Usage===
Usage:
crc-dabplus [OPTION...]

Help Options:
-h, --help Show help options
--help-all Show all help options
--help-gst Show GStreamer Options

Application Options:
-b, --bitrate={ 8, 16, ..., 80 } Output bitrate. Must be 8 multiple.
-c, --channels={ 1, 2 } Nb of input channels.
-d, --data=FILENAME Set data filename.
-g, --fs-bug Turn on FS bug mitigation.
-i, --input=FILENAME Input filename. Try -i help for more info.
-m, --message Turn on AAC frame messages.
-o, --output=FILENAME Output filename. Try -o help for more info.
-p, --pad=BYTES Set PAD size in bytes.
-r, --rate={ 32000, 48000 } Sample rate input.
-t, --type=TYPE Set data type (dls|pad|packet|dg).
-u, --up Speed up for testing purpose.
-v, --verbose=LEVEL Set verbosity level.
-V, --version Print version and exit.
-w, --down Speed down for testing purpose.
-x, --extra=OPTIONS Extra options in the form name1[,property1=value[,property2...]][:name2...].
-E, --Encode Set encoding mode. (default)
-D, --Decode Set decoding mode.
--mi=[ 0, ... ] Set AAC frame messages interval in milliseconds.
--ma=[ 0, ... ] Set AAC frame messages attack time in milliseconds.
--pi=GST_PIPELINE Probe in GStreamer pipeline inserted before the encoder.
--po=GST_PIPELINE Probe out GStreamer pipeline inserted after the decoder.

===Licence key===

Licence key is a a HASP usb key.
Packages are delivered with the package sold by CRC.

However, since Ubuntu 10.04 some tweaks must be done to have it working because of change in USB stack in Linux.

tweaks to simulate /proc/usb:
sudo mount --bind /dev/bus /proc/bus
sudo ln -s /sys/kernel/debug/usb/devices /proc/bus/usb/devices
sudo /etc/init.d/aksusbd restart

In Ubuntu 11.04 the last line is a bit different:
sudo mount --bind /dev/bus /proc/bus
sudo ln -s /sys/kernel/debug/usb/devices /proc/bus/usb/devices
sudo /usr/sbin/aksusbd restart

You can add these lines into your /etc/rc.local before the existing "exit 0" to have them performed automatically on startup. Otherwise you will have to perform them after every reboot.

How to install CRC DAB+ transmission chain from scratch in Ubuntu 11.04

2011-07-11T22:22:57Z

Ubr: /* Step 1: Installation of Gnuradio 3.3.0 */

Howto by Ulrik Brinck on CRC DAB+ installation on Ubuntu 11.04
===Introduction===

How to install all the needed software for transmitting DAB+ from scratch on Ubuntu 11.04. Some of it was absolutely not straight-forward in this Linux distro, but with good help from particularly Pascal Charest in the mailing list (thank you Pascal!), I succeeded in the end. So here, I will describe step-by-step how it can be done.

===Notes===

Please note:
* The OS in my case is Ubuntu 11.04, 32 bit version, standard version (not the server version). Hardware is Ettus USRP1 and WBX daughterboard. I have not tried it with other OS or hardware.
* I only intend to describe how to install all the software, not how to use it after installation. But how to use it is pretty much the same as on the mmbTools live cd, based on Ubuntu 9.04. Note however, that crc-dabmod, crc-dwap.py and crc-dabplus are installed with their names in lower case, so they must be called with lower case names also in your shell script.
* You will need to know how to unpack a tarball (.tar.gz og .tar.bz2 file). For tar.gz it's "tar xvzf package.tar.gz", and for tar.bz2 it's "tar xvjf package.tar.bz2".
* I installed on a brand new Ubuntu 11.04 installation after installing all the OS updates offered by the Update Manager.
* There might be some of it which can be done in an easier way, but I'm not that experienced with Linux, and this is what worked for me.

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

====Step 1: Installation of Gnuradio 3.3.0====
This is needed for USRP1 with WBX.
# First "sudo apt-get build-dep gnuradio" (takes quite some time).
# Then go to this page: http://gnuradio.org/redmine/projects/gnuradio/wiki/UbuntuInstall and install all the dependencies as mentioned in the first step there (for Ubuntu 10.04 plus the additional line for 11.04). Do NOT continue with the next step (Installing GNU Radio) on that page. Instead -
# Download and unpack this file: http://ftp.gnu.org/gnu/gnuradio/gnuradio-3.3.0.tar.gz (by default it goes to a "Downloads" folder in your homedir, this is fine).
# Before you can compile it, you will need to apply a patch as described here: http://lists.nongnu.org/archive/html/discuss-gnuradio/2011-05/msg00108.html But it was not so easy to apply the patch directly from that page, so you might want to just patch it manually instead (in fact, that's what I did) : To patch it manually, open ~/Downloads/gnuradio-3.3.0/usrp2/host/lib/usrp2.cc with a text editor. In line 41, 43 and 73 change "usrp2::usrp2" into just "usrp2". That's all, then save and close.
# Now you can compile it as described in the file ~/Downloads/gnuradio-3.3.0/INSTALL . It's "./configure", "make", "make check" and "sudo make install".
# Then back to this page: http://gnuradio.org/redmine/projects/gnuradio/wiki/UbuntuInstall and scroll down to "Configuring USRP support" and perform the steps mentioned there. I chose to reboot the pc after this, to be absolutely sure that the USRP support would work. Note: The section also mentions that an UHD driver can be installed from the ettus.com homepage, but you don't need to do that.
# At the end of the "Configuring USRP support" section of that page, there are some test you can perform to test that the USRP is available to Ubuntu. The "./usrp_benchmark_usb.py" test fails, but it doesn't matter in our case. The "./test_usrp_standard_tx" should however go well and a.o. show that your daughterboard is WBX (if that is actually what it is).

====Step 2: Crc-DabMod and CRC-Dwap.py====
# Download CRC-DabMod from the CRC homepage, http://mmbtools.crc.ca/content/view/44/71/ , unpack it and compile as described in ~/Downloads/crc-dabmod-0.2.0/INSTALL . It's "./configure --disable-debug", "make" and "sudo make install".
# Then go here http://mmbtools.crc.ca/content/view/37/63/ and download CRC-Dwap.py for Gnuradio 3.3 .
# Navigate to /usr/local/bin and replace the existing crc-dwap.py with the new one that you have just downloaded (rename it into crc-dwap.py (lower case) so that it's name becomes exactly the same as the old one). Then set it's permissions: "sudo chmod a+x crc-dwap.py".

====Step 3: Crc-DabMux and Libfec====
# First some necessary software: "sudo apt-get install devscripts". Note: This will also install a mail server (postfix) and ask you for a configuration, but, unless you actually want a mail server, you can just select "OK" and then "No configuration" (do not just close the terminal window).
# And "sudo apt-get install debhelper" (you might already have this).
# Go to http://mmbtools.crc.ca/content/view/39/65/ and download and unpack CRC-DabMux and Libfec 3.0.1-2.
# Inside the Libfec 3.0.1-2 package are some more packages and a README file. Be sure to do EXACTLY as described in that README file.
# Compile CRC-DabMux as described in ~/Downloads/crc-dabmux-0.3.0.4/INSTALL. It's just the usual way, "./compile", "make" and "sudo make install".

====Step 4: Buffer software====
On the mmbTools live cd, the "bfr" buffer is used between CRC-DabMux and CRC-DabMod. But on this Ubuntu 11.04 system, my experience is, that bfr sometimes stops working and hangs the whole system. Instead I use mbuffer, which works better for me:
# "sudo apt-get install mbuffer".

====Step 5: CRC-DabPlus====
Note: CRC-DabPlus is not free, because of HE-AAC royalty, but can be bought from CRC. If you don't have or want CRC-DabPlus, you can skip this step.
Note: Together with CRC-DabPlus came HASP (for the software protection dongle) and Libfec. You already installed Libfec in step 3, so you don't have to do it again now.
* Install HASP as described in the README-html which came with CRC-DabPlus (sudo dpkg -i *.deb).
* As mentioned on http://opendigitalradio.org/index.php/CRC-dabplus there is a bit more to do, and for me it was a bit different in Ubuntu 11.04, this is what works for me: Open /etc/rc.local with a text editor (with root privileges, for example "sudo gedit /etc/rc.local") and insert the following lines before the existing "exit 0":
sudo mount --bind /dev/bus /proc/bus
sudo ln -s /sys/kernel/debug/usb/devices /proc/bus/usb/devices
sudo /usr/sbin/aksusbd restart

* Insert the dongle in an empty USB slot and reboot the computer. License for CRC-DabPlus is now ready.
* Install CRC-DabPlus as described in the README.html.

====Step 6: AudioScience ASI504x sound cards====
In the README.html which came with CRC-DabPlus is described how to use it together with AudioScience sound cards. It also tells how to install the AudioScience cards, but this is NOT necessary in Ubuntu 11.04. It already works "out of the box". However the GUI sound control panel does not work correctly with these cards, so if you need to change it's configuration, you must use the non-GUI alsamixer (type "alsamixer" in a terminal window).

That's it. Now you're ready to set up your DAB multiplex.

How to install CRC DAB+ transmission chain from scratch in Ubuntu 11.04

2011-07-11T22:19:54Z

Ubr:

Howto by Ulrik Brinck on CRC DAB+ installation on Ubuntu 11.04
===Introduction===

How to install all the needed software for transmitting DAB+ from scratch on Ubuntu 11.04. Some of it was absolutely not straight-forward in this Linux distro, but with good help from particularly Pascal Charest in the mailing list (thank you Pascal!), I succeeded in the end. So here, I will describe step-by-step how it can be done.

===Notes===

Please note:
* The OS in my case is Ubuntu 11.04, 32 bit version, standard version (not the server version). Hardware is Ettus USRP1 and WBX daughterboard. I have not tried it with other OS or hardware.
* I only intend to describe how to install all the software, not how to use it after installation. But how to use it is pretty much the same as on the mmbTools live cd, based on Ubuntu 9.04. Note however, that crc-dabmod, crc-dwap.py and crc-dabplus are installed with their names in lower case, so they must be called with lower case names also in your shell script.
* You will need to know how to unpack a tarball (.tar.gz og .tar.bz2 file). For tar.gz it's "tar xvzf package.tar.gz", and for tar.bz2 it's "tar xvjf package.tar.bz2".
* I installed on a brand new Ubuntu 11.04 installation after installing all the OS updates offered by the Update Manager.
* There might be some of it which can be done in an easier way, but I'm not that experienced with Linux, and this is what worked for me.

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

====Step 1: Installation of Gnuradio 3.3.0====
This is needed for USRP1 with WBX.
# First "sudo apt-get build-dep gnuradio" (takes quite some time).
# Then go to this page: http://gnuradio.org/redmine/projects/gnuradio/wiki/UbuntuInstall and install all the dependencies as mentioned in the first step there (for Ubuntu 10.04 plus the additional line for 11.04). Do NOT continue with the next step (Installing GNU Radio) on that page. Instead -
# Download and unpack this file: http://ftp.gnu.org/gnu/gnuradio/gnuradio-3.3.0.tar.gz (be default it goes to a "Downloads" folder in your homedir, this is fine).
# Before you can compile it, you will need to apply a patch as described here: http://lists.nongnu.org/archive/html/discuss-gnuradio/2011-05/msg00108.html But it was not so easy to apply the patch directly from that page, so you might want to just patch it manually instead (in fact, that's what I did) : To patch it manually, open ~/Downloads/gnuradio-3.3.0/usrp2/host/lib/usrp2.cc with a text editor. In line 41, 43 and 73 change "usrp2::usrp2" into just "usrp2". That's all, then save and close.
# Now you can compile it as described in the file ~/Downloads/gnuradio-3.3.0/INSTALL . It's "./configure", "make", "make check" and "sudo make install".
# Then back to this page: http://gnuradio.org/redmine/projects/gnuradio/wiki/UbuntuInstall and scroll down to "Configuring USRP support" and perform the steps mentioned there. I chose to reboot the pc after this, to be absolutely sure that the USRP support would work. Note: The section also mentions that an UHD driver can be installed from the ettus.com homepage, but you don't need to do that.
# At the end of the "Configuring USRP support" section of that page, there are some test you can perform to test that the USRP is available to Ubuntu. The "./usrp_benchmark_usb.py" test fails, but it doesn't matter in our case. The "./test_usrp_standard_tx" should however go well and a.o. show that your daughterboard is WBX (if that is actually what it is).

====Step 2: Crc-DabMod and CRC-Dwap.py====
# Download CRC-DabMod from the CRC homepage, http://mmbtools.crc.ca/content/view/44/71/ , unpack it and compile as described in ~/Downloads/crc-dabmod-0.2.0/INSTALL . It's "./configure --disable-debug", "make" and "sudo make install".
# Then go here http://mmbtools.crc.ca/content/view/37/63/ and download CRC-Dwap.py for Gnuradio 3.3 .
# Navigate to /usr/local/bin and replace the existing crc-dwap.py with the new one that you have just downloaded (rename it into crc-dwap.py (lower case) so that it's name becomes exactly the same as the old one). Then set it's permissions: "sudo chmod a+x crc-dwap.py".

====Step 3: Crc-DabMux and Libfec====
# First some necessary software: "sudo apt-get install devscripts". Note: This will also install a mail server (postfix) and ask you for a configuration, but, unless you actually want a mail server, you can just select "OK" and then "No configuration" (do not just close the terminal window).
# And "sudo apt-get install debhelper" (you might already have this).
# Go to http://mmbtools.crc.ca/content/view/39/65/ and download and unpack CRC-DabMux and Libfec 3.0.1-2.
# Inside the Libfec 3.0.1-2 package are some more packages and a README file. Be sure to do EXACTLY as described in that README file.
# Compile CRC-DabMux as described in ~/Downloads/crc-dabmux-0.3.0.4/INSTALL. It's just the usual way, "./compile", "make" and "sudo make install".

====Step 4: Buffer software====
On the mmbTools live cd, the "bfr" buffer is used between CRC-DabMux and CRC-DabMod. But on this Ubuntu 11.04 system, my experience is, that bfr sometimes stops working and hangs the whole system. Instead I use mbuffer, which works better for me:
# "sudo apt-get install mbuffer".

====Step 5: CRC-DabPlus====
Note: CRC-DabPlus is not free, because of HE-AAC royalty, but can be bought from CRC. If you don't have or want CRC-DabPlus, you can skip this step.
Note: Together with CRC-DabPlus came HASP (for the software protection dongle) and Libfec. You already installed Libfec in step 3, so you don't have to do it again now.
* Install HASP as described in the README-html which came with CRC-DabPlus (sudo dpkg -i *.deb).
* As mentioned on http://opendigitalradio.org/index.php/CRC-dabplus there is a bit more to do, and for me it was a bit different in Ubuntu 11.04, this is what works for me: Open /etc/rc.local with a text editor (with root privileges, for example "sudo gedit /etc/rc.local") and insert the following lines before the existing "exit 0":
sudo mount --bind /dev/bus /proc/bus
sudo ln -s /sys/kernel/debug/usb/devices /proc/bus/usb/devices
sudo /usr/sbin/aksusbd restart

* Insert the dongle in an empty USB slot and reboot the computer. License for CRC-DabPlus is now ready.
* Install CRC-DabPlus as described in the README.html.

====Step 6: AudioScience ASI504x sound cards====
In the README.html which came with CRC-DabPlus is described how to use it together with AudioScience sound cards. It also tells how to install the AudioScience cards, but this is NOT necessary in Ubuntu 11.04. It already works "out of the box". However the GUI sound control panel does not work correctly with these cards, so if you need to change it's configuration, you must use the non-GUI alsamixer (type "alsamixer" in a terminal window).

That's it. Now you're ready to set up your DAB multiplex.