Issues After 1.0.2.0 Upgrade (1 Viewer)

[Woggle]

MediaPortal Version: 1.0.2.0
TV Server Version: 1.0.2.0
MediaPortal Skin: Monochrome Black
Windows Version: XP Home
CPU Type: AMD Athlon 64 X2 4850e
HDD: Western Digital 1TB Hard Drive SATAII 7200rpm
Memory: Corsair 2GB Kit (2x1GB) DDR2 800MHz
Motherboard: Gigabyte GA-MA78GPM-DS2H 780G
Video Card: Integrated ATI Radeon HD3200 graphics
TV Card: Hauppauge WinTV Nova-T 500
MPEG2 Video Codec: Cyberlink Video/SP Decoder (PVD7)
MPEG2 Audio Codec: MPA Decoder Filter
h.264 Video Codec: Cyberlink h.264/AVC Decoder (PVD7)
Satelite/CableTV Provider: Freeview
HTPC Case: Antec Fusion Remote Veris Black MATX Media Center Case
Cooling: Scythe Mini Ninja Socket 478
Power Supply: Corsair 450W VX Series PSU - ATX12V v2.2
Remote: Windows MCE Remote
TV: Samsung LCD
TV - HTPC Connection: HDMI

Hiya,
I've recently upgraded (rather than a new installation) MediaPortal from 1.0.0.0 to 1.0.2.0. Most things have gone fine and with a bit of tweaking are working ok.

However, I've come across some issues which I hope you might be able to help me work through.

1. Not a major issue and I'm sure I remember a way to solve this but the Monochrome skin is saying it is outdated on entering MediaPortal - can someone point me in the direction of the xml file to amend please?

2. My Recorded TV view is not coming up with anything in even though I know there are programmes which have been recorded. Interestingly, although it can be changed, the MP setup is greyed out in terms of the folders which need to be pointed to for recording purposes.

3. I had standby issues sorted in 1.0.0.0 but now in the new version it does not want to go into hibernate. I've got MPStandbyHandler running which worked fine previously but not now.

4. The EPG is an hour out (possibly daylight saving as I live in the UK?) meaning that the EPG shows something playing at 7.00pm when actually it doesn't start until 8.00pm - an issue when recording programmes.

5. An ongoing issue which was never resolved in the previous version - although MediaPortal doesn't hang, after a period of time it won't let me play live TV / watch recorded TV. It's like the TV Service has ended even though playing music and other bits are fine.

An ongoing source of frustration for my other half so any advice to help me fix this would help immensly!

Thanks!

 

[rsbrux]

Can't answer all of your questions, but here is what I know:

1. Not a major issue and I'm sure I remember a way to solve this but the Monochrome skin is saying it is outdated on entering MediaPortal - can someone point me in the direction of the xml file to amend please?

references.xml

2. My Recorded TV view is not coming up with anything in even though I know there are programmes which have been recorded. Interestingly, although it can be changed, the MP setup is greyed out in terms of the folders which need to be pointed to for recording purposes.

I think an import is necessary after a new installation; not sure about post-upgrade.

3. I had standby issues sorted in 1.0.0.0 but now in the new version it does not want to go into hibernate. I've got MPStandbyHandler running which worked fine previously but not now.

My system goes into hibernate fine without any extra tools like MPStandbyHandler. It sometimes hangs on reawakening. This happened with previous MP versions, but happens more frequently since switching to 1.0.2.

4. The EPG is an hour out (possibly daylight saving as I live in the UK?) meaning that the EPG shows something playing at 7.00pm when actually it doesn't start until 8.00pm - an issue when recording programmes.

I use WebEPG (with analog TV). The schedule gets imported via XMLTV. If you use XMLTV (with or without WebEPG), you can adjust the offset in MP's TV Server Configuration. Select "XmlTv" under "Plugins", check the box labelled "Apply time compensation..." and enter the needed time adjustment in the boxes below.

5. An ongoing issue which was never resolved in the previous version - although MediaPortal doesn't hang, after a period of time it won't let me play live TV / watch recorded TV. It's like the TV Service has ended even though playing music and other bits are fine.

Sorry, no ideas here.

 

[RobNorthcott]

4. The EPG is an hour out (possibly daylight saving as I live in the UK?) meaning that the EPG shows something playing at 7.00pm when actually it doesn't start until 8.00pm - an issue when recording programmes.

Mine was like that when I started using WebEPG. There's a setting called something like "adjust for time zone" that is by default set to zero, but enabled. My EPG was an hour out until I disabled this option.

Rob

 

[wonkyd]

1. Not a major issue and I'm sure I remember a way to solve this but the Monochrome skin is saying it is outdated on entering MediaPortal - can someone point me in the direction of the xml file to amend please?

2. My Recorded TV view is not coming up with anything in even though I know there are programmes which have been recorded. Interestingly, although it can be changed, the MP setup is greyed out in terms of the folders which need to be pointed to for recording purposes.

You should update monochrome to the latest version see MEDIAPORTAL - free media center - Monochrome 2.8

That will fix both those issues.

4. The EPG is an hour out (possibly daylight saving as I live in the UK?) meaning that the EPG shows something playing at 7.00pm when actually it doesn't start until 8.00pm - an issue when recording programmes.

Have you checked all your time/date/regional settings are correct in windows? Sounds like a BST issue to me.

5. An ongoing issue which was never resolved in the previous version - although MediaPortal doesn't hang, after a period of time it won't let me play live TV / watch recorded TV. It's like the TV Service has ended even though playing music and other bits are fine.

It probably has ended and needs restarting. Try going run>services.msc>find TV Service right click and press properties. On the Recovery Tab change all the failure options from Do Nothing to Restart the service to see if that helps.

 

[Woggle]

Thanks for all the advice.

1. Thanks for the link to the references file - changed to 1.0.2 but this still shows. Should it be 1.0.2.0 or shouldn't it matter?

2. Thanks for the link to the updated skin - the recorded programmes view now shows.

3. Standby now works ok but will continue to monitor as I've not checked it with scheduled recordings - thanks.

4. Thanks for the update on the EPG - unticked the box and this seems to be working ok.

5. I'll check the hanging suggestion and see if it works and let you know.

Many thanks for all your help. Will close this thread as fixed but want to check the couple of things highlighted above.

 

[rsbrux]

Thanks for all the advice.

1. Thanks for the link to the references file - changed to 1.0.2 but this still shows. Should it be 1.0.2.0 or shouldn't it matter?

Should theoretically be 1.0.2.0, however all of the skins I have working say 1.0.1.0.
You can see the versions of the available skins in MP Configuration - GENERAL - Skin

 

[wonkyd]

Thanks for all the advice.

1. Thanks for the link to the references file - changed to 1.0.2 but this still shows. Should it be 1.0.2.0 or shouldn't it matter?

Should theoretically be 1.0.2.0, however all of the skins I have working say 1.0.1.0.
You can see the versions of the available skins in MP Configuration - GENERAL - Skin

I think your right the refernce files for 1.0.2.0 still show as 1.0.1.0. The updated monochrome should be fully compatible with MP 1.0.2 though no need to edit the references file.

 

[Woggle]

Just a quick update.

All the issues now resolved except the skin out of date query - for some reason it still displays despite trying both 1.0.2.0 and 1.0.2 in the references.xml file (which coincidently also show the same in the MP Config setting).

Thanks for all your help!

 

[rekenaar]

The skin out of date message is given when your skin value does not match the value in Blue3 or Blue3Wide.
Therefore, I think you should try 1.0.1.0 in your references.xml.

Just remember that the recommended method is still to rather use a skin version that was specifically designed for 1.0.1 or 1.0.2 out of the box.
No skin changes between 1.0.1 and 1.0.2 therefore the number did not change. But if you man-handle a 1.0.0 skin to work in 1.0.2, there might be a few small problems.

 

[Woggle]

oh yes, 1.0.1.0 works!

Many thanks.