search

braice / MuMuDVB

A DVB IPTV streaming software
http://mumudvb.braice.net/
GNU General Public License v2.0
219 stars 133 forks source link

FE_HAS_SIGNAL : found something above the noise level #146

Open YaPaY opened 7 years ago

YaPaY commented 7 years ago

Hi all,

This is the output. I tried many transporder from different satellites but I get always tis error

mumudvb -d -c /root/42E_11550 MuMuDVB Version 2.0.0 --- Build information --- Built with CAM support. Built with SCAM support. Built with ATSC support. Built with ATSC long channel names support. Built with support for DVB API Version 5.10. Built with support for DVB-T2.

Originally based on dvbstream 0.6 by (C) Dave Chapman 2001-2004 Released under the GPL. Latest version available from http://mumudvb.braice.net/ Project from the cr@ns (http://www.crans.org) by Brice DUBOST (mumudvb@braice.net)

WARN: Main: Config issue : unknow symbol : multicast

Info: Main: ========== End of configuration, MuMuDVB version 2.0.0 is starting ========== WARN: Main: Can't create /var/run/mumudvb/channels_streamed_adapter10_tuner0: No such file or directory WARN: Main: Can't create /var/run/mumudvb/channels_unstreamed_adapter10_tuner0: No such file or directory Info: Main: Streaming. Freq 11550000 Info: Tune: Using DVB card "TurboSight TBS 6909 DVB-S/S2 " tuner 0 Info: Tune: Tuning DVB-S to Freq: 1800000 kHz, LO frequency 9750000 kHz Pol:V Srate=30000000, LNB number: 0 Info: Tune: LNB voltage 13V Info: Tune: DISEQC SETTING SUCCEDED Info: Tune: FE_STATUS: Info: Tune: FE_STATUS: Info: Tune: FE_HAS_SIGNAL : found something above the noise level Info: Tune: FE_STATUS: Info: Tune: FE_HAS_SIGNAL : found something above the noise level Info: Tune: FE_STATUS: Info: Tune: FE_HAS_SIGNAL : found something above the noise level Info: Tune: FE_STATUS: Info: Tune: FE_HAS_SIGNAL : found something above the noise level

vladojko commented 7 years ago

I had same with 6909 I returned it and took 4 x tbs 6902

YaPaY commented 7 years ago

really? send the cards to hong kong and wait a new ones would make only headache

vladojko commented 7 years ago

That's why i order from Amazon and spend fer EUR more, so I can return junk without headache. I couldn't find solution for the same problem, I suppose it is driver related so it is better to contact TBS and ask for help

YaPaY commented 7 years ago

I wrote the TBS but I am not expecting a good answer. If somebody read that please don't buy 6909. It makes really headache

braice commented 7 years ago

Hello

You can try s-scan and w-scan just to check that it is really a card issue not a software issue.

Do you have a diseqc switch or anything similar ?

Brice

2016-12-16 14:45 GMT-05:00 YaPaY notifications@github.com:

I wrote the TBS but I am not expecting a good answer. If somebody read that please don't buy 6909. It makes really headache

— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/braice/MuMuDVB/issues/146#issuecomment-267680034, or mute the thread https://github.com/notifications/unsubscribe-auth/AAUUD4UonoJpQUExPxDS0_RRXedYpRYwks5rIupygaJpZM4LNDoG .

kslimani commented 7 years ago 
WARN: Main: Can't create /var/run/mumudvb/channels_streamed_adapter10_tuner0: No such file or directory
WARN: Main: Can't create /var/run/mumudvb/channels_unstreamed_adapter10_tuner0: No such file or directory

Does the folder /var/run/mumudvb exists and have right permissions ? This may be your issue.

YaPaY commented 7 years ago

I have 2x 6909. after many tries I have been discoveredI can use the mumudvb if I enter the card number <8. if the card number between 8 and 15. I can get this error but the cards work under another programs.

kslimani commented 7 years ago

👍 @YaPaY i think this is because 6909 has 8 tuners. So it it card (adapter) number 0 for tuner 0 to 7 and it is card number 1 for tuner 8 to 15.

EDIT:

I may be wrong, but for TBS card i think it is one adapter number per tuner (depending on driver). So it must be something like adapter0 to adapter15. So yes setting card parameter in config file should solve the issue).

YaPaY commented 7 years ago

Does the folder /var/run/mumudvb exists and have right permissions ? This may be your issue.

I don't have /var/run/mumudvb

kslimani commented 7 years ago

@YaPaY this folder must exists in order to mumudvb work properly (if i am not missing this path is hardcoded)

YaPaY commented 7 years ago

@kslimani

thats weird because mumudvb works if I use the card number <8

should I reinstall it. What would you like to suggest me?

kslimani commented 7 years ago

you don't need to reinstall, just create the folder if missing (with proper permissions according the user used to run mumudvb instance).

If you use a card between 8 to 15 mumudvb does not work ?

YaPaY commented 7 years ago

If you use a card between 8 to 15 mumudvb does not work ?

I can get above error (see my first post) if I change the card number 1-7 for same transporder mumudvb works.

kslimani commented 7 years ago

By "error" do you mean the following warning ? :

WARN: Main: Config issue : unknow symbol : multicast
WARN: Main: Can't create /var/run/mumudvb/channels_streamed_adapter10_tuner0: No such file or directory
WARN: Main: Can't create /var/run/mumudvb/channels_unstreamed_adapter10_tuner0: No such file or directory

or it is something else you are talking about ? (sorry english is not my native language 😃 )

Btw, this first warning seems to be a "misplaced" option in config file (multicast).

The 2 other warning may results of /var/run/mumudvb folder not existing of with wrong permissions)

braice commented 7 years ago

Hello

Sounds very much like an hardware or driver issue,

You can try to physically swap the cards and see if the behavior changes.

You can check with w_scan what each card is seeing,

In term of reception chaining is not very reliable, do you have a multiswitch ?

Brice

2017-01-02 6:01 GMT-05:00 kslimani notifications@github.com:

By "error" do you mean the following warning ? :

WARN: Main: Config issue : unknow symbol : multicast WARN: Main: Can't create /var/run/mumudvb/channels_streamed_adapter10_tuner0: No such file or directory WARN: Main: Can't create /var/run/mumudvb/channels_unstreamed_adapter10_tuner0: No such file or directory

or it is something else you are talking about ? (sorry english is not my native language 😃 )

Btw, this first warning seems to be a "misplaced" option in config file (multicast).

The 2 other warning may results of /var/run/mumudvb folder not existing of with wrong permissions)

— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/braice/MuMuDVB/issues/146#issuecomment-269958265, or mute the thread https://github.com/notifications/unsubscribe-auth/AAUUD5ngSykmCZ2pR6awQkXKl86ckJDWks5rONkhgaJpZM4LNDoG .

kslimani commented 7 years ago

The TBS6909 is a "special" card, because it internally has a multiswitch and does not need one. Instead of plug in four lnb multiswith output, you plug in the four polarity signals (like for a multiswitch input).

This is why i am curious about this one. I wonder if from drivers/DVB api point of view it behave like "classical" dvb card behind a multiswitch. (especially with DiSEqC command, etc...)

YaPaY commented 7 years ago

@braice

yes I have one 32x output.

The changing the cards or advanced troubleshooting makes a bit trouble because the all equipment in another country. I have a another MOI Pro AMD with 4x 4 tuner cards. It works like charm. Only 6909 (actually one of them) card refuse the work with mumudvb.

I don't know what w_scan is meanwhile

YaPaY commented 7 years ago

@kslimani the cards and all tuners works with DVBBlast. The problem is the cards 7-15 doesn't work with mumudvb. Mumudvb is my favorite program and I am really happy with it.

Second question yes the 6909 works behind a multiswitch like a classical DVB cards. I can't use them direct LL,LH,VH,HH method because I need get signal more than 8 transporders for a satellite.

kslimani commented 7 years ago

@YaPaY w_scan is a small (but very cool !) utility for scan frequencies.

Which mode are you using for driver module ? Because with mode 2, in documentation they wrote :

In some case multiswitch have more than one satellite input, need to choose the satellite first, then you can use this mode .Noticed that the Satellite will be selected when first DiSEqC command send ,and cannot be changed any more , if you want to change the Satellite port you need to restart your PC and send the new DiSEqC.

YaPaY commented 7 years ago

mode 1.

kslimani commented 7 years ago

@YaPaY can you run a lsdvb shell command and paste output ? (cards must not be in use)

Also, can you post the MuMuDVB configuration for the cards 8 to 15 you are using ? (only the part with card=value, tuner=value, sat_number=value)

YaPaY commented 7 years ago

@kslimani at this time only card=13 is free because if use any transporder in astra cesbo card 13 and the other cards disconnecting. (it is reaally weird, isn't it). I can't use DVBBlast because multicast traffic make my network unusable. (Therefore I am using always unicast)

I can use your command but affect the other cards? My customers wathing TV's.

This is the values card=13 tuner= (I am not using this value) sat_number=13

kslimani commented 7 years ago

@YaPaY sat_number=13 ? you have a multiswitch with 13 satellite inputs ? The documentation say it is 0 or 1 to 4. Or are you using unicable ? (this should be your DiSEqC position)

YaPaY commented 7 years ago

It was a typo. Sat_number=0. This transporder using SAT A İnput. no difference 0 to 3

My multiswitch has got 4x4=16 inputs. So you can plug 4 different satellites

braice commented 7 years ago

Hi

Your issue is very strange as the only thing MuMuDVB is doing when changing a card is using the other file descriptors.

Lets try to summarize. MuMuDVB works fine with the first 8 adapters corresponding to a given card. MuMuDVB Fail to get a signal on the second card. Dvblast get a signal on both. The cards are behind a multi switch (on top of their internal one) .

If I am correct can you please resend us the mumudvb configuration files (both the working ones and non working ones) and the Dvblast ones for the same cards as the mumu ones.

Thank you

Brice

On Jan 4, 2017 2:42 PM, "YaPaY" notifications@github.com wrote:

It was a typo. Sat_number=0. This transporder using SAT A İnput. no difference 0 to 3

My multiswitch has got 4x4=16 inputs. So you can plug 4 different satellites

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/braice/MuMuDVB/issues/146#issuecomment-270466629, or mute the thread https://github.com/notifications/unsubscribe-auth/AAUUD-rtbIJjDOogzI_Piy3qeh6YwnXyks5rO_YmgaJpZM4LNDoG .

YaPaY commented 7 years ago

MuMuDVB works fine with the first 8 adapters corresponding to a given card. MuMuDVB Fail to get a signal on the second card. Dvblast get a signal on both. The cards are behind a multi switch (on top of their internal one) .

everything is correct.

Mumudvb working config: card=1 multicast=0 multicast_ipv4=0 multicast_ipv6=0 port_http=4265 unicast=1 freq=12015 pol=h srate=27500 dvr_buffer_size=7 ip_http=0.0.0.0 autoconfiguration=full modulation=QPSK delivery_system=DVBS coderate=5/6

mumudvb doesnt work: card=8 multicast=0 multicast_ipv4=0 multicast_ipv6=0 port_http=4265 unicast=1 freq=12015 pol=h srate=27500 dvr_buffer_size=7 ip_http=0.0.0.0 autoconfiguration=full modulation=QPSK delivery_system=DVBS coderate=5/6

I am using GUI of DVBBlast so I haven't got any config file for it. I can get from every satellite and transporder signal for every cards 0-15

kslimani commented 7 years ago

@YaPaY ok, these two configurations tell me that you are trying to get the same frequency of same sattelite with the second adapter of the first physical card, and with the first adapter of the second physical card.

I see that sat_number is not set and your multiswitch has 4 inputs : A, B,C and D (respectively 1, 2, 3 and 4 for sat_number)

Have you tried to set the same sat_number value for these 2 configuration ?

Because without, the default sat_number value is 0 which mean no DiSEqC message send.

YaPaY commented 7 years ago

@kslimani

it doesn't matter if I use sat_number=0 to 4 (for 2nd conf). First config works if I add sat_number=0 or without sat_number parameter.

kslimani commented 7 years ago

@YaPaY : that depend of the "state" of the multiswitch output connected to second card. If you set the same sat_number for the 2 configuration, you ensure that the same sattelite is selected with DiSEqC message send. (maybe this is not the issue, but it is possible)

EDIT: i mean that it is possible that multiswitch output connected to second card is not on same sat. than the first card and is why the second card fail to tune on frequency.

braice commented 7 years ago

Hello

Can you take a screenshot of dvblast configuration?

Brice

On Jan 5, 2017 11:31 AM, "kslimani" notifications@github.com wrote:

@YaPaY https://github.com/YaPaY : that depend of the "state" of the multiswitch output connected to second card. If you set the same sat_number for the 2 configuration, you ensure that the same sattelite is selected with DiSEqC message send. (maybe this is not the issue, but it is possible)

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/braice/MuMuDVB/issues/146#issuecomment-270688737, or mute the thread https://github.com/notifications/unsubscribe-auth/AAUUD_bPD8civrc_BDR0nJbIoYftE7CFks5rPRrIgaJpZM4LNDoG .

YaPaY commented 7 years ago

hello,

please see the SS: http://i.imgur.com/PDM9KNm.png

kslimani commented 7 years ago

on screenshot, i see that Switch Port equals 1 for adapter13.

you should try to set sat_number=1 to card=13 in your MuMuDVB configuration.

EDIT:

try also with switch_input=1 in MuMuDVB configuration.

@braice what is the difference between sat_number and switch_input ?

YaPaY commented 7 years ago

sat_number=1 and card=13

 mumudvb -d -c /root/42/starhd
MuMuDVB Version 2.0.0
 --- Build information ---
Built with CAM support.
Built with SCAM support.
Built with ATSC support.
Built with ATSC long channel names support.
Built with support for DVB API Version 5.10.
Built with support for DVB-T2.
---------
Originally based on dvbstream 0.6 by (C) Dave Chapman 2001-2004
Released under the GPL.
Latest version available from http://mumudvb.braice.net/
Project from the cr@ns (http://www.crans.org)
by Brice DUBOST (mumudvb@braice.net)

WARN:  Main:  Config issue : unknow symbol : multicast

Info:  Tune:  You will use DVB API version 5 for tuning your card.
Info:  Main:  Autoconfiguration, we activate SAP announces. if you want to disable them see the README.
Info:  Main:  Autoconfiguration, we activate PAT rewriting. if you want to disable it see the README.
Info:  Main:  Autoconfiguration, we activate SDT rewriting. if you want to disable it see the README.
Info:  Main:  ========== End of configuration, MuMuDVB version 2.0.0 is starting ==========
Info:  Main:  Streaming. Freq 12015000
Info:  Tune:  Using DVB card "TurboSight TBS 6909 DVB-S/S2 " tuner 0
Info:  Tune:  Tuning DVB-S to Freq: 1415000 kHz, LO frequency 10600000 kHz Pol:H Srate=27500000, LNB number: 1
Info:  Tune:  LNB voltage 18V
Info:  Tune:  DISEQC SETTING SUCCEDED
Info:  Tune:  Tuning With DVB-API version 5. delivery system : 5
Info:  Tune:  Stream_id = 0, stream id with PLS parameters 0
Info:  Tune:  FE_STATUS:
Info:  Tune:  FE_STATUS:
Info:  Tune:       FE_HAS_SIGNAL : found something above the noise level
Info:  Tune:  FE_STATUS:
Info:  Tune:       FE_HAS_SIGNAL : found something above the noise level
Info:  Tune:  FE_STATUS:
Info:  Tune:       FE_HAS_SIGNAL : found something above the noise level
Info:  Tune:  FE_STATUS:
Info:  Tune:       FE_HAS_SIGNAL : found something above the noise level
Info:  Tune:  FE_STATUS:
Info:  Tune:       FE_HAS_SIGNAL : found something above the noise level
Info:  Tune:  FE_STATUS:
Info:  Tune:       FE_HAS_SIGNAL : found something above the noise level
Info:  Tune:  FE_STATUS:
Info:  Tune:       FE_HAS_SIGNAL : found something above the noise level
Info:  Tune:  FE_STATUS:
Info:  Tune:       FE_HAS_SIGNAL : found something above the noise level
Info:  Tune:  FE_STATUS:
Info:  Tune:       FE_HAS_SIGNAL : found something above the noise level
Info:  Tune:  FE_STATUS:
Info:  Tune:       FE_HAS_SIGNAL : found something above the noise level
Info:  Tune:  FE_STATUS:
Info:  Tune:       FE_HAS_SIGNAL : found something above the noise level
Info:  Tune:  FE_STATUS:
Info:  Tune:       FE_HAS_SIGNAL : found something above the noise level
Info:  Tune:  FE_STATUS:
Info:  Tune:       FE_HAS_SIGNAL : found something above the noise level
Info:  Tune:  FE_STATUS:
Info:  Tune:       FE_HAS_SIGNAL : found something above the noise level
Info:  Tune:  FE_STATUS:
Info:  Tune:       FE_HAS_SIGNAL : found something above the noise level
Info:  Tune:  FE_STATUS:
Info:  Tune:       FE_HAS_SIGNAL : found something above the noise level
Info:  Tune:  FE_STATUS:
Info:  Tune:       FE_HAS_SIGNAL : found something above the noise level
Info:  Tune:  FE_STATUS:
Info:  Tune:       FE_HAS_SIGNAL : found something above the noise level
Info:  Tune:  FE_STATUS:
Info:  Tune:       FE_HAS_SIGNAL : found something above the noise level
Info:  Tune:  FE_STATUS:
Info:  Tune:       FE_HAS_SIGNAL : found something above the noise level
Info:  Tune:  FE_STATUS:
Info:  Tune:       FE_HAS_SIGNAL : found something above the noise level
^C

switch_input=1

same :(

braice commented 7 years ago

In DVB last you set the modulation to be PSK_8, which seems to be DVB-S2 for me. So you can try modulation = 8psk and maybe change the delivery system

Also do you have a link to kingofsat for the transponder you are trying to tune.

Can you also please describe how your multiswitch is wired ?

Thank you

Brice

2017-01-06 4:04 GMT-05:00 YaPaY notifications@github.com:

sat_number=1 and card=13

mumudvb -d -c /root/42/starhd MuMuDVB Version 2.0.0 --- Build information --- Built with CAM support. Built with SCAM support. Built with ATSC support. Built with ATSC long channel names support. Built with support for DVB API Version 5.10. Built with support for DVB-T2.

Originally based on dvbstream 0.6 by (C) Dave Chapman 2001-2004 Released under the GPL. Latest version available from http://mumudvb.braice.net/ Project from the cr@ns (http://www.crans.org) by Brice DUBOST (mumudvb@braice.net)

WARN: Main: Config issue : unknow symbol : multicast

Info: Tune: You will use DVB API version 5 for tuning your card. Info: Main: Autoconfiguration, we activate SAP announces. if you want to disable them see the README. Info: Main: Autoconfiguration, we activate PAT rewriting. if you want to disable it see the README. Info: Main: Autoconfiguration, we activate SDT rewriting. if you want to disable it see the README. Info: Main: ========== End of configuration, MuMuDVB version 2.0.0 is starting ========== Info: Main: Streaming. Freq 12015000 Info: Tune: Using DVB card "TurboSight TBS 6909 DVB-S/S2 " tuner 0 Info: Tune: Tuning DVB-S to Freq: 1415000 kHz, LO frequency 10600000 kHz Pol:H Srate=27500000, LNB number: 1 Info: Tune: LNB voltage 18V Info: Tune: DISEQC SETTING SUCCEDED Info: Tune: Tuning With DVB-API version 5. delivery system : 5 Info: Tune: Stream_id = 0, stream id with PLS parameters 0 Info: Tune: FE_STATUS: Info: Tune: FE_STATUS: Info: Tune: FE_HAS_SIGNAL : found something above the noise level Info: Tune: FE_STATUS: Info: Tune: FE_HAS_SIGNAL : found something above the noise level Info: Tune: FE_STATUS: Info: Tune: FE_HAS_SIGNAL : found something above the noise level Info: Tune: FE_STATUS: Info: Tune: FE_HAS_SIGNAL : found something above the noise level Info: Tune: FE_STATUS: Info: Tune: FE_HAS_SIGNAL : found something above the noise level Info: Tune: FE_STATUS: Info: Tune: FE_HAS_SIGNAL : found something above the noise level Info: Tune: FE_STATUS: Info: Tune: FE_HAS_SIGNAL : found something above the noise level Info: Tune: FE_STATUS: Info: Tune: FE_HAS_SIGNAL : found something above the noise level Info: Tune: FE_STATUS: Info: Tune: FE_HAS_SIGNAL : found something above the noise level Info: Tune: FE_STATUS: Info: Tune: FE_HAS_SIGNAL : found something above the noise level Info: Tune: FE_STATUS: Info: Tune: FE_HAS_SIGNAL : found something above the noise level Info: Tune: FE_STATUS: Info: Tune: FE_HAS_SIGNAL : found something above the noise level Info: Tune: FE_STATUS: Info: Tune: FE_HAS_SIGNAL : found something above the noise level Info: Tune: FE_STATUS: Info: Tune: FE_HAS_SIGNAL : found something above the noise level Info: Tune: FE_STATUS: Info: Tune: FE_HAS_SIGNAL : found something above the noise level Info: Tune: FE_STATUS: Info: Tune: FE_HAS_SIGNAL : found something above the noise level Info: Tune: FE_STATUS: Info: Tune: FE_HAS_SIGNAL : found something above the noise level Info: Tune: FE_STATUS: Info: Tune: FE_HAS_SIGNAL : found something above the noise level Info: Tune: FE_STATUS: Info: Tune: FE_HAS_SIGNAL : found something above the noise level Info: Tune: FE_STATUS: Info: Tune: FE_HAS_SIGNAL : found something above the noise level Info: Tune: FE_STATUS: Info: Tune: FE_HAS_SIGNAL : found something above the noise level ^C

switch_input=1

same :(

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/braice/MuMuDVB/issues/146#issuecomment-270860817, or mute the thread https://github.com/notifications/unsubscribe-auth/AAUUD_Hcu_aLA5QZvwtIgmsXwMnZM8a8ks5rPgOXgaJpZM4LNDoG .

braice commented 7 years ago

Also, can you run dvblast in command line as https://forum.videolan.org/viewtopic.php?t=107613 and mumudvb with -vvv so I will be able to check that both software are asking the card the same way.

Thank you

2017-01-07 20:37 GMT-05:00 Brice Dubost braice@braice.net:

In DVB last you set the modulation to be PSK_8, which seems to be DVB-S2 for me. So you can try modulation = 8psk and maybe change the delivery system

Also do you have a link to kingofsat for the transponder you are trying to tune.

Can you also please describe how your multiswitch is wired ?

Thank you

Brice

2017-01-06 4:04 GMT-05:00 YaPaY notifications@github.com:

sat_number=1 and card=13

mumudvb -d -c /root/42/starhd MuMuDVB Version 2.0.0 --- Build information --- Built with CAM support. Built with SCAM support. Built with ATSC support. Built with ATSC long channel names support. Built with support for DVB API Version 5.10. Built with support for DVB-T2.

Originally based on dvbstream 0.6 by (C) Dave Chapman 2001-2004 Released under the GPL. Latest version available from http://mumudvb.braice.net/ Project from the cr@ns (http://www.crans.org) by Brice DUBOST (mumudvb@braice.net)

WARN: Main: Config issue : unknow symbol : multicast

Info: Tune: You will use DVB API version 5 for tuning your card. Info: Main: Autoconfiguration, we activate SAP announces. if you want to disable them see the README. Info: Main: Autoconfiguration, we activate PAT rewriting. if you want to disable it see the README. Info: Main: Autoconfiguration, we activate SDT rewriting. if you want to disable it see the README. Info: Main: ========== End of configuration, MuMuDVB version 2.0.0 is starting ========== Info: Main: Streaming. Freq 12015000 Info: Tune: Using DVB card "TurboSight TBS 6909 DVB-S/S2 " tuner 0 Info: Tune: Tuning DVB-S to Freq: 1415000 kHz, LO frequency 10600000 kHz Pol:H Srate=27500000, LNB number: 1 Info: Tune: LNB voltage 18V Info: Tune: DISEQC SETTING SUCCEDED Info: Tune: Tuning With DVB-API version 5. delivery system : 5 Info: Tune: Stream_id = 0, stream id with PLS parameters 0 Info: Tune: FE_STATUS: Info: Tune: FE_STATUS: Info: Tune: FE_HAS_SIGNAL : found something above the noise level Info: Tune: FE_STATUS: Info: Tune: FE_HAS_SIGNAL : found something above the noise level Info: Tune: FE_STATUS: Info: Tune: FE_HAS_SIGNAL : found something above the noise level Info: Tune: FE_STATUS: Info: Tune: FE_HAS_SIGNAL : found something above the noise level Info: Tune: FE_STATUS: Info: Tune: FE_HAS_SIGNAL : found something above the noise level Info: Tune: FE_STATUS: Info: Tune: FE_HAS_SIGNAL : found something above the noise level Info: Tune: FE_STATUS: Info: Tune: FE_HAS_SIGNAL : found something above the noise level Info: Tune: FE_STATUS: Info: Tune: FE_HAS_SIGNAL : found something above the noise level Info: Tune: FE_STATUS: Info: Tune: FE_HAS_SIGNAL : found something above the noise level Info: Tune: FE_STATUS: Info: Tune: FE_HAS_SIGNAL : found something above the noise level Info: Tune: FE_STATUS: Info: Tune: FE_HAS_SIGNAL : found something above the noise level Info: Tune: FE_STATUS: Info: Tune: FE_HAS_SIGNAL : found something above the noise level Info: Tune: FE_STATUS: Info: Tune: FE_HAS_SIGNAL : found something above the noise level Info: Tune: FE_STATUS: Info: Tune: FE_HAS_SIGNAL : found something above the noise level Info: Tune: FE_STATUS: Info: Tune: FE_HAS_SIGNAL : found something above the noise level Info: Tune: FE_STATUS: Info: Tune: FE_HAS_SIGNAL : found something above the noise level Info: Tune: FE_STATUS: Info: Tune: FE_HAS_SIGNAL : found something above the noise level Info: Tune: FE_STATUS: Info: Tune: FE_HAS_SIGNAL : found something above the noise level Info: Tune: FE_STATUS: Info: Tune: FE_HAS_SIGNAL : found something above the noise level Info: Tune: FE_STATUS: Info: Tune: FE_HAS_SIGNAL : found something above the noise level Info: Tune: FE_STATUS: Info: Tune: FE_HAS_SIGNAL : found something above the noise level ^C

switch_input=1

same :(

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/braice/MuMuDVB/issues/146#issuecomment-270860817, or mute the thread https://github.com/notifications/unsubscribe-auth/AAUUD_Hcu_aLA5QZvwtIgmsXwMnZM8a8ks5rPgOXgaJpZM4LNDoG .

azzahrah commented 7 years ago

I have some problem with TBS6909 but sometime port >=8 working fine...