Support for MP 1.1.x? (1 Viewer)

[Scandermore]

Hi!

I've been using StreamedMP, and it's great! But when testing the new MP 1.1.0 Alpha version, I noticed that the actual version of streamedMP is not detected. For me, the alpha is working great, and has some important improvements over the 1.0.2, so the only reason for not moving to it is the skin.

Any news about supporting 1.1.x ?

Thanx

aLeX

 

[sergiocos]

Did you copy the skin files inside ProgramData, instead Program Files (where the skin installer copy the skin files)? I'm runnin' 1.1a and StreamedMP and the skin is functional.

# UAC compatibillty enhancements:
following folders are now also located in %ProgramData%\TeamMediaPortal\MediaPortal

* Tuningdetails
* Languages
* Skins

 

[Scandermore]

Now it's working. As the installation of StreamedMP was an exe, I didn't know if the skin files were stored in the same way...

Thanks

aLeX

 

[stevie_j_b]

Has anyone managed to get the Basic Home Editor working with 1.1.0 and StreamedMP? I know problems are to be expected - and I run with Normal Home, so it isn't a problem - but I've noticed with this and X-Factor that when trying to run the Basic Home Editor, no modules are visible.

Is the Editor hard-wired to point towards the old skin location?

I'm also running Windows 7 RC - for the first time along with the 1.1.0 Alpha - so I'm unsure whether this has any effect. Would logs help?

 

[ltfearme]

The StreamedMP Basic Home Editor currently does not have support for the new Skin Path in MP 1.1.0 Alpha nor has it support for Custom Skin directories defined in MediaPortalDirs.xml but you can manually point to skin folder from the File Menu. This will load the current BasicHome.xml you have.

There is an outstanding issue on the tracker for the BasicHome Skin Editor to read path from MediaPortalDirs.xml (I forgot to do it at the same time I did the setup program)

 

[ltfearme]

I've been using StreamedMP, and it's great! But when testing the new MP 1.1.0 Alpha version, I noticed that the actual version of streamedMP is not detected. For me, the alpha is working great, and has some important improvements over the 1.0.2, so the only reason for not moving to it is the skin.

It should install to the correct location as the Installer picks up the path defined in MediaPortalDirs.xml which is always the correct path. You may have a problem if you had it installed before Installing the Alpha release because the path would of changed.

I recommend Uninstalling the skin from the Add\Remove programs and Re-Installing.

Im not sure what works and what doesnt though so be warned that StreamedMP 0.8 was designed for MP 1.0.2.

Any news about supporting 1.1.x ?

StreamedMP v0.9 should be ready in a couple weeks, mostly everything is done and im currently testing it.

 

[stevie_j_b]

The StreamedMP Basic Home Editor currently does not have support for the new Skin Path in MP 1.1.0 Alpha nor has it support for Custom Skin directories defined in MediaPortalDirs.xml but you can manually point to skin folder from the File Menu. This will load the current BasicHome.xml you have.

There is an outstanding issue on the tracker for the BasicHome Skin Editor to read path from MediaPortalDirs.xml (I forgot to do it at the same time I did the setup program)

Many thanks for that confirmation.

 

[peque]

StreamedMP v0.9 should be ready in a couple weeks, mostly everything is done and im currently testing it.

Sorry to use this post... Will you improve support for plugin MyFilms in 0.9? Or at least fix this:

https://forum.team-mediaportal.com/streamedmp-301/bugs-around-myfilms-xmls-54546/

I've got some .xmls developed for StreamedMP, but also triggers this bug...

Thanks.

 

[ltfearme]

Sorry, it will have to be by someone in the community that uses the plugin. If I have time to install it and get it configured I will have a go but its very low on the priority list. Can the plugin author give you any tips on what is wrong?

 

[peque]

Xface and Blue3wide don't mess other MP sections as StreamedMP xmls for MyFilms... I asume there must be a problem in the .xmls from this skin... What do you think that could be the origin of this problem? I must ask to skin devs, because it seems to be skin related. I don't think zebons (myfilms plugin dev) can help me in this case... ¿?

I've tried debbuging the problem, but I have no error log or any other hint that can help you debug this problem.