EPG lines limited to the number of channels (1 Viewer)

greybox

MP Donator
  • Premium Supporter
  • January 23, 2009
    621
    132
    Home Country
    Canada Canada
    If I have only 7 channels in my EPG, the detailed listing for a particular channel is limited to 7 rows only. If I have 10 or more, I get 10 rows. Shouldn't we get at least 10 rows of detailed listing even if we have less then 10 channels?

    MediaPortal Version: MediaPortal 1.2.0 Beta
    MediaPortal Skin: Default Wide with MePo added and analog clock removed
    Windows Version: Windows 7 Ultimate
    CPU Type: Intel Core I7 2.8GHz
    HDD: WDC SATA-2 80GB; Samsung SATA2, 750GB; Blu Ray drive: LiteOn iHES108
    Memory: 4GB DDR3
    Motherboard: Asus P7P55D PRO
    Video Card: ASUS GeForce 9600GT Silent 650MHZ 512MB 1.8GHZ DDR3 PCI-E Dual DVI-I HDCP HDTV
    Video Card Driver: Latest
    Sound Card: IDT High Definition
    Sound Card AC3: Optical out
    Sound Card Driver: Latest
    1. TV Card: Hauppauge WinTV HVR-1800, PCIe
    1. TV Card Type: analog, ATSC
    1. TV Card Driver: Latest
    2. TV Card: Twinhan AD-SE200 (1028), PCIe
    2. TV Card Type: DVB-S
    2. TV Card Driver: Latest
    3. TV Card:
    3. TV Card Type:
    3. TV Card Driver:
    4. TV Card:
    4. TV Card Type:
    4. TV Card Driver:
    MPEG2 Video Codec:
    MPEG2 Audio Codec:
    h.264 Video Codec:
    Satelite/CableTV Provider: FTA/Cable/OTA
    HTPC Case: Custom
    Cooling:
    Power Supply:
    Remote: Universal, URC 200
    TV: Samsung 58" 1080p Plasma HDTV (PN58B530)
    TV - HTPC Connection: DVI/HDMI
     

    Attachments

    • 7 channels epg.png
      7 channels epg.png
      845.3 KB
    • 7 rows.png
      7 rows.png
      612.6 KB
    Last edited by a moderator:

    greybox

    MP Donator
  • Premium Supporter
  • January 23, 2009
    621
    132
    Home Country
    Canada Canada
    By the way, it looks even worse if you switch from the card that populates the entire screen to the card that feeds only a few channels: the old populated portion of the screen does not go away properly, and the new channels are shown on top of the old screen...
     

    elliottmc

    Retired Team Member
  • Premium Supporter
  • August 7, 2005
    14,927
    6,061
    Cardiff, UK
    Home Country
    United Kingdom United Kingdom
    By the way, it looks even worse if you switch from the card that populates the entire screen to the card that feeds only a few channels: the old populated portion of the screen does not go away properly, and the new channels are shown on top of the old screen...

    Detailed steps to reproduce and screenshots?
     

    greybox

    MP Donator
  • Premium Supporter
  • January 23, 2009
    621
    132
    Home Country
    Canada Canada
    OK, to reproduce the ghosting part:

    1. Select the EPG source containing 10+ channels
    2. Select the EPG source containing less then 10 channels (7 in my example)

    You will see EPG source 2 on top of EPG source 1.
     

    Attachments

    • mixup.png
      mixup.png
      839.8 KB

    elliottmc

    Retired Team Member
  • Premium Supporter
  • August 7, 2005
    14,927
    6,061
    Cardiff, UK
    Home Country
    United Kingdom United Kingdom
    OK, to reproduce the ghosting part:

    1. Select the EPG source containing 10+ channels
    2. Select the EPG source containing less then 10 channels (7 in my example)

    You will see EPG source 2 on top of EPG source 1.

    Are you able to compile your own MediaPortal from source? If so, I think I can provide a patch for this one. Basically, it didn't make it in time for 1.2.0, but we are aware of this issue and it will be in the next release.

    Mark
     

    greybox

    MP Donator
  • Premium Supporter
  • January 23, 2009
    621
    132
    Home Country
    Canada Canada
    No, I can't compile, I will wait for 1.2.0. Thank you.
     

    greybox

    MP Donator
  • Premium Supporter
  • January 23, 2009
    621
    132
    Home Country
    Canada Canada
    Installed 1.2.0 final today, exact same bug is still there. I thought it was fixed...
     

    mm1352000

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

    Mark said:
    Basically, it didn't make it in time for 1.2.0, but we are aware of this issue and it will be in the next release.

    ...so I don't know why you expected the fix in 1.2.0. Our policy is only to fix showstoppers in a release candidate (otherwise we'd never release anything! ;)), and this is not considered a showstopper.

    You can track progress on this issue -->here<--.

    mm
     

    greybox

    MP Donator
  • Premium Supporter
  • January 23, 2009
    621
    132
    Home Country
    Canada Canada
    The reason I expected the fix in 1.2.0 final is because the fix already exists (see post #6). I didn't know it was scheduled for 1.3.x, sorry.
     

    Users who are viewing this thread

    Top Bottom