auto close in dvbt radio streaming

[davoudafshari]

Hi
I found a problem in streaming DVB-T radios. When I stream a DVB-T frequency that have TV and radio channels, every thing is OK and for radio channels we see in log:

"Info: Main: Channel "RADIO EGHTESAD" down.Card 1"

But there is no problem with any of radio streams and we receive them by VLC correctly.
When I stream just radio channels of the frequency without any TV channel, After 1 to 5 min I see all radios in log file is down but we also have correct stream and signal.

"
Info: Main: Channel "RADIO KETAB" down.Card 1
Info: Main: Channel "RADIO IRAN" down.Card 1
Info: Main: Channel "RADIO PAYAM" down.Card 1
Info: Main: Channel "RADIO JAVAN" down.Card 1
Info: Main: Channel "RADIO MAAREF" down.Card 1
Info: Main: Channel "RADIO QURAN" down.Card 1
Info: Main: Channel "RADIO FARHANG" down.Card 1
Info: Main: Channel "RADIO SALAMAT" down.Card 1
Info: Main: Channel "RADIO VARZESH" down.Card 1
Info: Main: Channel "RADIO EGHTESAD" down.Card 1
Info: Main: Channel "RADIO TEHRAN" down.Card 1
Info: Main: Channel "RADIO NAMAYESH" down.Card 1
Info: Main: Channel "RADIO FASLI" down.Card 1
Info: Main: Channel "RADIO CALL OF ISLAM" down.Card 1
Info: Main: Channel "RADIO SEDAYE ASHENA 3" down.Card 1
Info: Main: Channel "RADIO ARABI" down.Card 1
Info: Main: Channel "RADIO DANESH" down.Card 1
Info: Main: Channel "RADIO TELAVAT" down.Card 1
Info: Main: Channel "RADIO GOFTEGO" down.Card 1
"
and because of mumudvb "timeout_no_diff" mechanism it will kill its process! this means there is a problem with streamig just radio channels in DVB-T. I dont have such a problem with DVB-S or S2.

[davoudafshari]

I also run in verbose mode and see this in logs:
"
Deb0: SDT rewrite: NEW program for channel 0 : "RADIO IRAN". service_id : 151
Info: Main: Channel "RADIO IRAN" down.Card 1
ERRO: Main: No data from card 1 in 600s, exiting.
Info: Main: End of streaming. We streamed during 0d 0:11:22
Info: Main: Closing cleanly. Error 8
Deb1: Main: Signal/power Thread closing
Deb1: Main: Monitor Thread closing
Deb1: Main: Monitor thread stopping, it lasted 682.000000 seconds
Info: Main: ========== MuMuDVB version 1.7.2_release is stopping with ExitCode 8 ==========

"

[braice]

Hello

Yes you are right, the up/down mechanism is not excellent

I have reworked it a bit in Mumudvb 2 can you have a try and tell me if you
still have the behavior?

Thanks
Le 27 avr. 2014 11:43, "davoudafshari" notifications@github.com a écrit :

Hi
I found a problem in streaming DVB-T radios. When I stream a DVB-T
frequency that have TV and radio channels, every thing is OK and for radio
channels we see in log:

"Info: Main: Channel "RADIO EGHTESAD" down.Card 1"

But there is no problem with any of radio streams and we receive them by
VLC correctly.
When I stream just radio channels of the frequency without any TV channel,
After 1 to 5 min I see all radios in log file is down but we also have
correct stream and signal.

"
Info: Main: Channel "RADIO KETAB" down.Card 1
Info: Main: Channel "RADIO IRAN" down.Card 1
Info: Main: Channel "RADIO PAYAM" down.Card 1
Info: Main: Channel "RADIO JAVAN" down.Card 1
Info: Main: Channel "RADIO MAAREF" down.Card 1
Info: Main: Channel "RADIO QURAN" down.Card 1
Info: Main: Channel "RADIO FARHANG" down.Card 1
Info: Main: Channel "RADIO SALAMAT" down.Card 1
Info: Main: Channel "RADIO VARZESH" down.Card 1
Info: Main: Channel "RADIO EGHTESAD" down.Card 1
Info: Main: Channel "RADIO TEHRAN" down.Card 1
Info: Main: Channel "RADIO NAMAYESH" down.Card 1
Info: Main: Channel "RADIO FASLI" down.Card 1
Info: Main: Channel "RADIO CALL OF ISLAM" down.Card 1
Info: Main: Channel "RADIO SEDAYE ASHENA 3" down.Card 1
Info: Main: Channel "RADIO ARABI" down.Card 1
Info: Main: Channel "RADIO DANESH" down.Card 1
Info: Main: Channel "RADIO TELAVAT" down.Card 1
Info: Main: Channel "RADIO GOFTEGO" down.Card 1
"
and because of mumudvb "timeout_no_diff" mechanism it will kill its
process! this means there is a problem with streamig just radio channels in
DVB-T. I dont have such a problem with DVB-S or S2.

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/62
.

[davoudafshari]

I have tested with new version but problem does exist. here is the log:
"
Info: Main: Channel "RADIO PAYAM" down.Card 7
...
...
ERRO: Main: No data from card 7 in 600s, exiting.
Info: Main: End of streaming. We streamed during 0d 0:30:05
Info: Main: Closing cleanly. Error 8
Info: Main: ========== MuMuDVB version 2.0.0_20140330_mumudvb2 is stopping with ExitCode 8 ==========
"
Why and how the program find the card is down or not? Is there any way to improve this mechanism? It seems a good mechanism when signal or card or network face with problems.
Thanks a lot

[braice]

Please add

timeout_no_diff=0

to your configuration file

Best

2014-04-27 23:05 GMT+02:00 davoudafshari notifications@github.com:

I have tested with new version but problem does exist. here is the log:
"
Info: Main: Channel "RADIO PAYAM" down.Card 7
...
...

ERRO: Main: No data from card 7 in 600s, exiting.
Info: Main: End of streaming. We streamed during 0d 0:30:05

Info: Main: Closing cleanly. Error 8
Info: Main: ========== MuMuDVB version 2.0.0_20140330_mumudvb2 is stopping
with ExitCode 8 ==========
"
Why and how the program find the card is down or not? Is there any way to
improve this mechanism? It seems a good mechanism when signal or card or
network face with problems.
Thanks a lot

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/62#issuecomment-41509085
.

[davoudafshari]

I have changed
timeout_no_diff=600
by
timeout_no_diff=0
It means checking for channel stream will be disabled.(?) It solved my problem.
thanks

[braice]

Yes kind of, this feature is a watchdog for some buggy cards which stop
streaming without reasons, but it is based on data rate threshold well
suited for TV but not for radio.

I can lower them I think, I'll keep this issue updated

Best regards

2014-04-28 10:35 GMT+02:00 davoudafshari notifications@github.com:

I have changed
timeout_no_diff=600
by
timeout_no_diff=0
It means checking for channel stream will be disabled.(?) It solved my
problem.
thanks

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/62#issuecomment-41534670
.

[m0yellow]

Maybe as side note mildly interesting ;)
I have this up/down/up states when there is work on the transponder, your detection obviously detected an encoder/muxer restart, or the uplink is switched to a redundancy system.

If you describe more about the intended algorithm we might find out what use cases this (unintended) has. I check for correct station name in stream for dead cards ;) And I get notified if it changes as a bonus.

[braice]

Hello

The code is there
https://github.com/braice/MuMuDVB/blob/mumudvb2/src/mumudvb_mon.c
starting line 599

You can adjust the threshold via the options (undocumented :-( )

else if (!strcmp (substring, "up_threshold")) { substring = strtok (NULL,
delimiteurs); stats_infos->up_threshold= atoi (substring); } else if (!
strcmp (substring, "down_threshold")) { substring = strtok (NULL,
delimiteurs); stats_infos->down_threshold= atoi (substring); } else if (!
strcmp (substring, "debug_updown")) { substring = strtok (NULL,
delimiteurs); stats_infos->debug_updown= atoi (substring); }

2014-06-30 13:27 GMT+02:00 m0yellow notifications@github.com:

Maybe as side note mildly interesting ;)
I have this up/down/up states when there is work on the transponder, your
detection obviously detected an encoder/muxer restart, or the uplink is
switched to a redundancy system.

If you describe more about the intended algorithm we might find out what
use cases this (unintended) has. I check for correct station name in stream
for dead cards ;) And I get notified if it changes as a bonus.

—
Reply to this email directly or view it on GitHub
#62 (comment).