Norway
MediaPortal Version: 1.1.3 (stable, no SVN, fresh installed)
MediaPortal Skin: BlueTwoWide
Windows Version: XP, SP3
CPU Type: AMD Athlon II X3 415e
HDD: OCX SSD 128GB
Memory: 4GB
Motherboard: Aopen
Video Card: Nvidia 8400GS
Video Card Driver: 266.58
Sound Card: Realtec HD Audio
Sound Card AC3: not in use
Sound Card Driver: 5.10.0.5636
1. TV Card: Digital Everywhere FloppyDTV
1. TV Card Type: DVB-S2
1. TV Card Driver: FW Ver.: 1.5.2 Build 30740 Driver : 5.0 (6201-3000)
2. TV Card: Digital Everywhere FloppyDTV
2. TV Card Type: DVB-S2
2. TV Card Driver: FW Ver.: 1.5.2 Build 30740 Driver : 5.0 (6201-3000)
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: ffdshow-rev3721_20110107_clsid_icl10
MPEG2 Audio Codec: ffdshow-rev3721_20110107_clsid_icl10
h.264 Video Codec: ffdshow-rev3721_20110107_clsid_icl10
Satelite/CableTV Provider: Canal Digital 2W (nordic)
HTPC Case: -
Cooling: 12cm quiet fan
Power Supply: Epsilon 600W (huge overkill, I know)
Remote: Firefly
TV: Monitors+projector, no TV
TV - HTPC Connection: DVI
This does not really need any log, it's about timeout/the way RSS reader is handling communication trouble.
When user enters the RSS plugin, it's possible to choose from several RSS sources.
if a source's server is down, or the internet connection is down, user is stuck, apparently for no visible reason, and thinks MP froze.
Moreover, whatever is the "first" source, is automatically opened when user enter RSS plugin, if this source is down, the user will also be left with a "frozen" impression.
Suggestions:
- make the timeout shorter, and/or the GUI responsive while attemting to communicate with server.
- notify user if there's no response from server after 1s. - just a simple symbol would do.
The last experience is harder to reproduce:
My wife discovered that browsing RSS with TV minimized have good chance of crashing MP.
(reading articles by selecting them - not only reading the short preview)
This does seem to happen after a while/day of MP use, not right after starting MP.
-My theory is that it handles the big html-pages poorly, and maybe leaks/corrupts memory at some point.
MediaPortal Skin: BlueTwoWide
Windows Version: XP, SP3
CPU Type: AMD Athlon II X3 415e
HDD: OCX SSD 128GB
Memory: 4GB
Motherboard: Aopen
Video Card: Nvidia 8400GS
Video Card Driver: 266.58
Sound Card: Realtec HD Audio
Sound Card AC3: not in use
Sound Card Driver: 5.10.0.5636
1. TV Card: Digital Everywhere FloppyDTV
1. TV Card Type: DVB-S2
1. TV Card Driver: FW Ver.: 1.5.2 Build 30740 Driver : 5.0 (6201-3000)
2. TV Card: Digital Everywhere FloppyDTV
2. TV Card Type: DVB-S2
2. TV Card Driver: FW Ver.: 1.5.2 Build 30740 Driver : 5.0 (6201-3000)
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: ffdshow-rev3721_20110107_clsid_icl10
MPEG2 Audio Codec: ffdshow-rev3721_20110107_clsid_icl10
h.264 Video Codec: ffdshow-rev3721_20110107_clsid_icl10
Satelite/CableTV Provider: Canal Digital 2W (nordic)
HTPC Case: -
Cooling: 12cm quiet fan
Power Supply: Epsilon 600W (huge overkill, I know)
Remote: Firefly
TV: Monitors+projector, no TV
TV - HTPC Connection: DVI
This does not really need any log, it's about timeout/the way RSS reader is handling communication trouble.
When user enters the RSS plugin, it's possible to choose from several RSS sources.
if a source's server is down, or the internet connection is down, user is stuck, apparently for no visible reason, and thinks MP froze.
Moreover, whatever is the "first" source, is automatically opened when user enter RSS plugin, if this source is down, the user will also be left with a "frozen" impression.
Suggestions:
- make the timeout shorter, and/or the GUI responsive while attemting to communicate with server.
- notify user if there's no response from server after 1s. - just a simple symbol would do.
The last experience is harder to reproduce:
My wife discovered that browsing RSS with TV minimized have good chance of crashing MP.
(reading articles by selecting them - not only reading the short preview)
This does seem to happen after a while/day of MP use, not right after starting MP.
-My theory is that it handles the big html-pages poorly, and maybe leaks/corrupts memory at some point.