Mediaportal 1.14Pre: TV-Server always using a new TV-Card when re-use is possible (1 Viewer)

rue

MP Donator
  • Premium Supporter
  • January 1, 2009
    113
    12
    Home Country
    Germany Germany
    Hi all,

    after having problems grabbing the right channels from DVB-S2@Astra (don't know really what happened, but I always have wrong frequencies in the database), I installed 1.14PR a view minutes ago.

    I have seen was that the recorder alwasy uses a new TVBS-Card when an additional recording on my card would be possible. This consumes my cards ....
    In addition I saw a crash . maybe this is the point ... (Timecode 2016-03-02 19:00:12,248 in TVService-Log)

    Please see logs in attachment.

    best regards

    RUE
     

    Attachments

    • TVService-Error.zip
      147.4 KB

    mm1352000

    Retired Team Member
  • Premium Supporter
  • September 1, 2008
    21,577
    8,224
    Home Country
    New Zealand New Zealand
    Hi

    don't know really what happened, but I always have wrong frequencies in the database
    Providers move their channels sometimes, and when that happens you need to rescan after using the "update satellite list" function.

    I have seen was that the recorder alwasy uses a new TVBS-Card when an additional recording on my card would be possible. This consumes my cards ....
    So the example seems to be:
    0. 3 tuners available.
    1. Start recording using tuner 4:
    [2016-03-28 18:56:22,232] [Log ] [scheduler thread] [INFO ] - Scheduler: Time to record SUPER RTL 18:56-19:15 Dragons - Auf zu neuen Ufern
    ...
    [2016-03-28 18:56:22,560] [Log ] [scheduler thread] [INFO ] - card: Tune on card 4 to subchannel SUPER RTL
    [2016-03-28 18:56:22,560] [Log ] [scheduler thread] [DEBUG] - card: user: scheduler32:4:-1 tune DVBS:tv:RTL World SUPER RTL Freq:12188000 ONID:1 TSID:1089 SID:12040 PMT:0x2D FTA:True LCN:10000 SymbolRate:27500 Modulation:ModNotSet Polarisation:LinearH InnerFecRate:Rate3_4 DisEqc:Level1AA band:Universal Pilot:NotSet RollOff:NotSet
    ...
    [2016-03-28 18:56:23,717] [Log ] [scheduler thread] [INFO ] - card: WaitForFile - video and audio are seen after 0,0780906 seconds

    Now only 2 tuners are free.

    2. Start recording on a different transponder using tuner 5:
    [2016-03-28 18:58:09,190] [Log ] [scheduler thread] [INFO ] - Scheduler: Time to record ProSieben 18:58-20:15 Gravity
    ...
    [2016-03-28 18:58:09,201] [Log ] [scheduler thread] [INFO ] - card: Tune on card 5 to subchannel ProSieben
    [2016-03-28 18:58:09,201] [Log ] [scheduler thread] [DEBUG] - card: user: scheduler33:5:-1 tune DVBS:tv:proSiebenSat.1 ProSieben Freq:12545000 ONID:1 TSID:1107 SID:17501 PMT:0x61 FTA:True LCN:10000 SymbolRate:22000 Modulation:ModNotSet Polarisation:LinearH InnerFecRate:Rate5_6 DisEqc:Level1AA band:Universal Pilot:NotSet RollOff:NotSet
    ...
    [2016-03-28 18:58:09,373] [Log ] [scheduler thread] [INFO ] - card: WaitForFile - video and audio are seen after 0,0879933 seconds

    Now only 1 tuner is free.

    3. Start time-shifting on a different transponder with tuner 3:
    [2016-03-28 19:00:07,745] [Log ] [17 ] [INFO ] - Controller: find free card for channel TELE 5
    ...
    [2016-03-28 19:00:07,763] [Log ] [17 ] [INFO ] - card: Tune on card 3 to subchannel TELE 5
    [2016-03-28 19:00:07,763] [Log ] [17 ] [DEBUG] - card: user: PC3:3:-1 tune DVBS:tv:BetaDigital TELE 5 Freq:12480000 ONID:133 TSID:33 SID:51 PMT:0x63 FTA:True LCN:10000 SymbolRate:27500 Modulation:ModNotSet Polarisation:LinearV InnerFecRate:Rate3_4 DisEqc:Level1AA band:Universal Pilot:NotSet RollOff:NotSet
    ...
    [2016-03-28 19:00:08,373] [Log ] [17 ] [INFO ] - card: WaitForFile - video and audio are seen after 0,0302983 seconds

    Now 0 tuners are free, but it should still be possible to time-shift or record a channel from any of the 3 transponders that the tuners are already tuned to.

    4. Try to start another recording on the same channel as tuner 4's recording. We expect the same tuner 4 to be used:
    [2016-03-28 19:00:10,201] [Log ] [scheduler thread] [INFO ] - Scheduler: Time to record SUPER RTL 19:00-19:45 Der gestiefelte Kater - Abenteuer in San Lorenzo
    ...
    [2016-03-28 19:00:10,217] [Log ] [scheduler thread] [INFO ] - card: Tune on card 4 to subchannel SUPER RTL
    [2016-03-28 19:00:10,217] [Log ] [scheduler thread] [DEBUG] - card: user: scheduler34:4:-1 tune DVBS:tv:RTL World SUPER RTL Freq:12188000 ONID:1 TSID:1089 SID:12040 PMT:0x2D FTA:True LCN:10000 SymbolRate:27500 Modulation:ModNotSet Polarisation:LinearH InnerFecRate:Rate3_4 DisEqc:Level1AA band:Universal Pilot:NotSet RollOff:NotSet

    So far so good, but see what happens next:
    [2016-03-28 19:00:12,248] [Log ] [scheduler thread] [INFO ] - dvb: LockInOnSignal could not lock onto channel - no signal or bad signal

    TV Server was unable to use tuner 4. Another tuner is needed, so TV Server kicks the time-shifting user (lowest priority) from tuner 3, and starts the recording with that tuner:
    [2016-03-28 19:00:12,248] [Log ] [scheduler thread] [INFO ] - scheduler: recording failed, lets try next available card.
    ...
    [2016-03-28 19:00:12,248] [Log ] [scheduler thread] [INFO ] - Scheduler : card is not tuned to the same transponder and not recording, kicking all users. record on card:3 priority:3
    [2016-03-28 19:00:12,248] [Log ] [scheduler thread] [INFO ] - Scheduler : kicking user:pC3
    ...
    [2016-03-28 19:00:12,435] [Log ] [scheduler thread] [INFO ] - card: Tune on card 3 to subchannel SUPER RTL
    [2016-03-28 19:00:12,435] [Log ] [scheduler thread] [DEBUG] - card: user: scheduler34:3:-1 tune DVBS:tv:RTL World SUPER RTL Freq:12188000 ONID:1 TSID:1089 SID:12040 PMT:0x2D FTA:True LCN:10000 SymbolRate:27500 Modulation:ModNotSet Polarisation:LinearH InnerFecRate:Rate3_4 DisEqc:Level1AA band:Universal Pilot:NotSet RollOff:NotSet
    ...
    [2016-03-28 19:00:13,545] [Log ] [scheduler thread] [INFO ] - card: WaitForFile - video and audio are seen after 0,0506808 seconds

    Now the recording succeeds, but 3 tuners are used instead of 2. As you can see above, TV Server tries to reuse tuner 4 for the 3rd recording. So it isn't a bug. Rather, it seems to be a tuner problem (the tuner should not fail to lock on signal).

    I suggest you try to enable preloading for all your tuners and see if it helps:
    http://wiki.team-mediaportal.com/1_...nfiguration/02_TV_Servers#Edit_Tuner_Settings
     

    rue

    MP Donator
  • Premium Supporter
  • January 1, 2009
    113
    12
    Home Country
    Germany Germany
    Hi again and thanks for your reply!

    Yes - of course providers change transponders and channels - but that is not thrue for my problem.
    I have currently 3 installations of MP - all with the same config (and with the plan to have finally only one server).

    And _only_ if I rescan on the new platform I got strange results. Rescan seems working fine, no problems - but in the end when it comes to an access to the transponder MP is using a wrong transponder config. This is weird - I use MP since several year with the same type of cards (TBS), had problems with chipsets and drivers .. issue with MP of course, too :) but never such a behaviour.

    Meanwhile I am possible on step ahead: Both card (in total 3 receivers) are handled by my chipset (C236 + Skylake) in "PCIe incompatible mode", which is strange to.
    In the moment I switche off the support for "incompatible cards" the cards are immediatelly disappearing from PCI structure.

    I had a discussion with TBS Germany but is only a distribution channel. It seem I should use other cards in the future.
    Maybe you have a tip for me regarding this: are there "well tested" DVB-S2 cards?


    Did you see the Error-Message? Is this something to investigate or comes it from the "internal situation"?

    [2016-03-28 19:00:12,248] [Log ] [scheduler thread] [ERROR] - System.NullReferenceException: Der Objektverweis wurde nicht auf eine Objektinstanz festgelegt.
    bei TvService.Scheduler.FindFreeCardAndStartRecord(RecordingDetail recDetail, IUser user, ICollection`1 cards, Int32 maxCards, IDictionary`2 tickets, CardReservationRec cardResImpl)

    Thanks in advance and best regards

    RUE
     

    mm1352000

    Retired Team Member
  • Premium Supporter
  • September 1, 2008
    21,577
    8,224
    Home Country
    New Zealand New Zealand
    Hello again

    And _only_ if I rescan on the new platform I got strange results. Rescan seems working fine, no problems - but in the end when it comes to an access to the transponder MP is using a wrong transponder config.
    Well, without scan log files I'm unable to understand what you're describing, and so there's nothing further I can say or do right now.

    Meanwhile I am possible on step ahead: Both card (in total 3 receivers) are handled by my chipset (C236 + Skylake) in "PCIe incompatible mode", which is strange to.
    In the moment I switche off the support for "incompatible cards" the cards are immediatelly disappearing from PCI structure.

    I had a discussion with TBS Germany but is only a distribution channel. It seem I should use other cards in the future.
    Maybe you have a tip for me regarding this: are there "well tested" DVB-S2 cards?
    In my opinion this is completely irrelevant to the situation.

    You have not filled in your system specifications, so I don't know what motherboard you're using. Therefore I can't look for the setting description in the motherboard manual. However, my guess is that it has something to do with PCIe (PCI Express) versions and backwards compatibility. The C236 chipset supports PCIe version 3. However AFAIK all tuner cards support only PCIe version 1.0a or 1.1 (due to the used chipset - eg. NXP/Trident/Entropic SAA716x, Conexant CX23885/7/8). If you disable C236 PCIe backwards compatibility then of course the card would not be recognised (because it uses PCIe v1 instead of v2 or v3)... but this would be the same for all tuner cards.

    TBS products are well tested, and there's no need to buy new/other cards.

    Did you see the Error-Message? Is this something to investigate or comes it from the "internal situation"?
    It's nothing to investigate.
     

    rue

    MP Donator
  • Premium Supporter
  • January 1, 2009
    113
    12
    Home Country
    Germany Germany
    HI again ... PCIe v3 ... that's something I had not in mind ....
    When I read the boards docu - I don't get much information about the meaning of the "compatibility wording" - but you can be right, maybe they talk about strict PCIe v3 or not.

    I will try to find out more - maybe it can be an idea to restrict the PCI mode ..... I will try that and report.

    Currently I configured the board to use "incompatible" devices, but to "don't use" PCIe L1 power modes.

    About the TBS:
    Yes, you are right - I use them for years - but still having problem:
    - On an Intel H77 in 1 out of 4 power-up cycles the TBS 6928 sometime is getting not recognized and - if recognized - after using it a while, the amount of discontinued packets increases (after several Intel fixes now very slightly)
    - On my Asrock Extreme 6 (Z97), TBS 6991SE runs properly for months - no errors - on the C236 I have some problems after a while of activity (that's what I try to fix now)
    - On my Asrock Extreme 6 (Z97) and on my C236 based boad (Supermicro X11SAE-F) the TBS 6902 did not work - will be recognized but throws high discontinuation rates (I gave that back and receives a TBS6982 instead of).
    - TBS 6982 work fine on the Z97, but has much problems with the C236 (high dicontinuation rates)

    ... so I won't say "no problems" :)
    ... You are absulotely right: they mostly work fine, but not in any case.

    I am absolutely not sure about the reason why.
     

    mm1352000

    Retired Team Member
  • Premium Supporter
  • September 1, 2008
    21,577
    8,224
    Home Country
    New Zealand New Zealand
    Now that you've said which motherboard you have, I downloaded the manual:
    http://www.supermicro.com/support/resources/results.cfm
    http://www.supermicro.com/manuals/motherboard/C236/MNL-1820.pdf

    Is this the "incompatible mode" setting that you're talking about?
    Port 7 Detect Non-Compliant Device
    Select Enabled for the AMI BIOS to automatically detect a PCI-E device that is not compliant with the PCI-E standards. The options are Disabled and Enabled.

    About the TBS:
    Yes, you are right - I use them for years - but still having problem:
    Why do you think that these problems are related to the tuner cards rather than signal strength/quality, motherboard, power saving, BIOS/EFI settings etc.?
     

    rue

    MP Donator
  • Premium Supporter
  • January 1, 2009
    113
    12
    Home Country
    Germany Germany
    I checked this at first and did a parallel recording at a second device without having any problem.

    The signals are pretty good and stable.

    Typical values are:
    ***** SIGNAL LEVEL: 99, SIGNAL QUALITY: 81 *****
    ***** SIGNAL LEVEL: 98, SIGNAL QUALITY: 80 *****

    lowest ever found:
    ***** SIGNAL LEVEL: 95, SIGNAL QUALITY: 55 *****

    On the last line the quality is not so good (most happens on HD channels) and I wonder how I have to interpret this ....
    High signal with low quality .... strange.

    Have to verify it against the 2nd installation - why do I have here no problems?
    Two meters to the switch ... same Power source, located on the same desk.

    Will monitor this too - thanks!


    @mm1352000: yes - have both (port 7 and 8 in use)

    i.e. page 4-22 ------------------

    Port 7 Detect Non-Compliant Device
    Select Enabled for the AMI BIOS to automatically detect a PCI-E device
    that is not compliant with the PCI-E standards. The options are
    Disabled and Enabled.

    ---------------

    RUE
     

    mm1352000

    Retired Team Member
  • Premium Supporter
  • September 1, 2008
    21,577
    8,224
    Home Country
    New Zealand New Zealand
    Have you enabled preload yet, and does it solve the problem with reusing tuners?
     

    rue

    MP Donator
  • Premium Supporter
  • January 1, 2009
    113
    12
    Home Country
    Germany Germany
    No - I earliest can do this today in the evening when I am back home :)

    But I will do that and reply as soon as possible.
     

    rue

    MP Donator
  • Premium Supporter
  • January 1, 2009
    113
    12
    Home Country
    Germany Germany
    Hi did a couple of tests yesterday evening.

    It seems to be better with tuner preloading, never seen the reported problem.

    Switching off the PCIe L1/L0 States seems to make the situation better - I still have discontinuations, but much lesser.
    Before it was nearly impossible to replay a film, now the problem appear not any time _and_ if it happens the amount of errors seems getting much lower (now: 20 drop outs per 90 minutes, before nearly any GOP).

    What I can't understand: I monitored the signal strength and quality of all the cards for a while in "manual control" of TV-Server with the timeshift option.
    I never head signals lower than 90% and qualities lower than 80 - 85%.

    When I take a look into the logfiles I sometimes see qualities about 50% (most on HD channels). If I timeshift the same channels or other HD channels on the transporter the window outputs at least 80-85% quality to me .... Is there a posibility to monitor the quality of the incoming signals during reception?

    About the PCIe compatibility: As both cards draw a MSI option to the system, they should be able to handle PCIe v2(.2). If not, we have found the "compatibility" issue here.

    The TBS 6902 (which had the most problems) signals to have a pericom device on the PCIe ... I banned all pericom devices .... had too much trouble with them, timing is bad (especially PI7C9X442SLB). Lost much time and money to find out the problems on my SBCs.

    best regards

    RUE
     

    Users who are viewing this thread

    Top Bottom