ZMQ link between ODR-dab-mux and ODR-dab-mod

[Yoann QUERET]

Hi,

I use a ZMQ link between ODR-dab-mux and ODR-dab-mod.

If i start ODR-dab-mux before ODR-dab-mod i have no problem and all
work perfectly. But if i start ODR-dab-mod before ODR-dab-mux or just
restart ODR-dab-mux, i have many alert message on ODR-dab-mod and never
return in stable mode.

ODR-DabMod: WARN: OutputUHD: Incorrect expect fct 7
WARN OutputUHD: Incorrect expect fct 7
UODR-DabMod: ALERT: Near frame 7: Received Async UHD Message
'Underflow'
ALERT Near frame 7: Received Async UHD Message 'Underflow'
[...]
ODR-DabMod: ALERT: Near frame 247: Received Async UHD Message
'Underflow'
UALERT Near frame 247: Received Async UHD Message 'Underflow'
UODR-DabMod: ALERT: Near frame 1: Received Async UHD Message
'Underflow'
ALERT Near frame 1: Received Async UHD Message 'Underflow'

My ODR-dab-mux output :
outputs {
; ZeroMQ output
; Listen on all interfaces, on port 8080
zmq "zmq+tcp://*:8080"

; Throttle output to real-time
throttle "simul://"
}

My ODR-dab-mod input :
[input]
transport=zeromq
source=tcp://localhost:8080

Did I made a mistake in the configuration? Is there a notion of buffer
and pre-buffer between ODR-dab-mux and ODR-dab-mod such as
fdk-aac-dabplus and ODR-dab-mux ?

Thk a lot
Have a nice WE.

Yoann

[Matthias Brändli]

Hi Yoann,

what version of the tools are you using ? What USRP ?

mpb

[Yoann QUERET]

Hi Matthias,

I use a compiled version from GIT on 04/04/2015 with an ettus B200.

# odr-dabmod
linux; GNU C++ version 4.9.2; Boost_105500; UHD_003.007.000-0-g7fef199d

ODR-DabMod version v0.5.1
Using FFT library FFTW (with fft_simd)
Compiled with features: zeromq output_uhd
Welcome to odr-dabmod v0.5.1, compiled at Apr 4 2015, 14:24:01

# odr-dabmux
Welcome to ODR-DabMux v0.7.2-2-g31e8a4f, compiled at Apr 4 2015,
14:01:42

Y!

[Matthias Brändli]

Thank you for this information.

There have been changes on ODR-DabMod since v0.5.1 about this issue.
Yesterday's v0.5.2 release should behave better now.

Can you update and tell me if you still see this problem ?

mpb

[Yoann QUERET]

I have upgrade odr-dabmod & odr-dabmux (i use zmq 4.0.4 from
http://download.zeromq.org/zeromq-4.0.4.tar.gz)

# odr-dabmod
linux; GNU C++ version 4.9.2; Boost_105500; UHD_003.007.000-0-g7fef199d

ODR-DabMod version v0.5.2

Using FFT library FFTW (with fft_simd)
Compiled with features: zeromq output_uhd

Welcome to odr-dabmod v0.5.2, compiled at Apr 12 2015, 11:06:19

# odr-dabmux
Welcome to ODR-DabMux v0.7.3, compiled at Apr 12 2015, 11:04:13

Now i have the ALERT message every time. (when i start mux or mod in
first) but without problem on receiver (tested on a very short
duration).


Input ZeroMQ:
Receiving from tcp://localhost:8080

ODR-DabMod: WARN: InputZMQ buffer overflow
WARN InputZMQ buffer overflow

Restart modulator


0 DAB frames encoded
0.000000 seconds encoded

Cleaning flowgraph...
ODR-DabMod: INFO: Setting up timestamp decoder with fixed offset
Setting up timestamp decoder with fixed offset
Input ZeroMQ:
Receiving from tcp://localhost:8080

ZeroMQ buffer low: 4 elements !
No resampler
ODR-DabMod: DEBUG: OutputUHD: UHD initialising...
OutputUHD: UHD initialising...
ODR-DabMod: DEBUG: OutputUHD: UHD initialising complete
OutputUHD: UHD initialising complete
UODR-DabMod: ALERT: Near frame 195: Received Async UHD Message
'Underflow'
ALERT Near frame 195: Received Async UHD Message 'Underflow'
UODR-DabMod: ALERT: Near frame 199: Received Async UHD Message
'Underflow'
ALERT Near frame 199: Received Async UHD Message 'Underflow'
UODR-DabMod: ALERT: Near frame 203: Received Async UHD Message
'Underflow'
ALERT Near frame 203: Received Async UHD Message 'Underflow'
UODR-DabMod: ALERT: Near frame 207: Received Async UHD Message
'Underflow'
ALERT Near frame 207: Received Async UHD Message 'Underflow'

[Matthias Brändli]

But does it always settle down after the underruns, and then runs fine ?

mpb

[Yoann QUERET]

Nop same ALERT message with Underflow is already present after 10 min
and i have cut on my receiver.

[Matthias Brändli]

But does it happen often (several underruns per minute) or seldom (one
every 10 minutes) ?

It's quite easy to provoque underruns when the machine is being used for
other activities. I also noticed that it depends on the USB controller,
on the UHD version, on other services running on the machine, and on the
CPU frequency scaling. Sadly, quite a large number of factors are in
play here.

mpb

[Yoann QUERET]

Utcch .. Not simple :-)

I use a DELL R320 with 2*E5-2420 (useless, but i have only this server
for testing) with a Debian Jessie and i have only encoder + mux + mod
running on.

I have underruns many time per minutes (perhaps many per seconds) when
i kill and restart ODR-mux.

Complet ODR-mod Log here :
https://gist.github.com/YoannQueret/7912b841f01ea6e1d5b4

Tomorrow i will try on some other server (SuperMicro, HP, ...), to
check if i have to same behavior.

Y!

[Matthias Brändli]

On 12. 04. 15 21:28, Yoann QUERET wrote:
> I have underruns many time per minutes (perhaps many per seconds) when i
> kill and restart ODR-mux.

Yes, but my question was about what happens when you let everything run
for a longer time.

Leave it all running for five minutes and don't touch it. Ignore what
happens in the first couple of seconds. Does it stabilise ? Once it
stabilises, how many underruns to you get in these five minutes ?

mpb