MediaPortal 1.0.1 Release (2 Viewers)

[CHli]

Yes, but I am having problems reading what it says under the lines, and opening 100 tabs is alot of work I did a site search for rate and it does not seem to have the refreshrate changer.

1.0 Didn't have any RefreshRate changer included, you had to use an external plugin
1.0.1 Will have integrated RefreshRate changer

Other important changes in 1.0.1 are :

- Improvement in GUI smoothness
- Improvement of TS (Transport Stream) handling (faster channel changing)

And a hell lot of bug fixes. Nice...

If you can't read the overlined text go there :

Change Log - MediaPortal Bugtracker


For even more details (may timeout...)

http://mediaportal.svn.sourceforge.net/viewvc/mediaportal/trunk/TvEngine3/?view=log
http://mediaportal.svn.sourceforge.net/viewvc/mediaportal/trunk/mediaportal/?view=log
http://mediaportal.svn.sourceforge.net/viewvc/mediaportal/trunk/DirectShowFilters/?view=log

Have fun reading.

 

[Paranoid Delusion]

Hm, why isn't it possible to update from SVN to 1.01? Is there any reason or only to have a new software bundle?

Unfortunately people have a habit of putting svn on top of svn, this can make what should be a pretty stable setup, unstable.

Also most plugins have been updated to newer versions as well, so what does a person who is on MP1.0 need to do to fix any possible clash, it's remove all plugins they have installed prior to upgrading and make sure you have the current replacements available to reinstall once upgraded, bet we get a lot of faults reported regarding this

Personally, because it takes me so little time to set everything up, will myself be doing a clean install rather than a upgrade, at least then, i know how things should be

 

[tesco]

1.0 Didn't have any RefreshRate changer included, you had to use an external plugin
1.0.1 Will have integrated RefreshRate changer

Other important changes in 1.0.1 are :

- Improvement in GUI smoothness
- Improvement of TS (Transport Stream) handling (faster channel changing)

And a hell lot of bug fixes. Nice...

If you can't read the overlined text go there :

Change Log - MediaPortal Bugtracker

Have fun reading.

Thank you

 

[Iwen]

Unfortunately people have a habit of putting svn on top of svn, this can make what should be a pretty stable setup, unstable.

Personally, because it takes me so little time to set everything up, will myself be doing a clean install rather than a upgrade, at least then, i know how things should be

Seems logical. Will do a clean install a well when it's ready.
Thanks for your answer

 

[hardcorehire]

If you have everything setup the way you want with 1.0 and latest SVN build why then can't you just backup your settings. And then do clean install of 1.01 while reinstalling settings with backup plugin? That is what I think I am going to try.

 

[Gixxer]

If you have everything setup the way you want with 1.0 and latest SVN build why then can't you just backup your settings. And then do clean install of 1.01 while reinstalling settings with backup plugin? That is what I think I am going to try.

great, but then dont start posting logs and complains about mp failing please.

 

[hardcorehire]

I don't plan on it if things don't work I'll just do a clean install. It really doesn't take much to reinstall and setup if you just have a few things configured. This would be more for people that have customized their installations.

 

[dir]

The reason I'm checking literally every day for 1.01 is because the main plugins that I use and love have all been updated to run on 1.01 and >>> won't run on 1.0 <<< properly. So all the advancement and corrections to skins/plugins are all being done on an unreleased MP. People running the released supported version of MP don't get to take advantage of updates. It's very frustrating.

I don't know why they have to develop for unreleased, future versions of MP and can't update their skins/plugins etc. for MP 1.0, but I'm sure they have their reasons. The net result is that we can't take advantage of them until MP 1.01 comes out.

I've dutifully read all the FAQs and threads but it's been weeks (or months) since it was announced that MP 1.01 would be "delayed". For some reason I thought this would mean 2 or 3 weeks; maybe a month. But there's no update since then and it's been months.

I'd really prefer to make a decision to give up on waiting for MP 1.01 and just update to unreleased SVNs so I can get on with things, hence threads like this that might possibly give a hint as to when MP 1.01 is coming get scoured for info.

A week?
A month?
A quarter?

I don't need exact dates, just indicative ones. "It's ready when it's ready" isn't helpful; "sometime in the next 3 months, probably not the next month" would be sufficient.

With the excellent project management that's been done to date, I'm sure it's possible to give some indication. If it's really that unknown, then perhaps a decision should be made to forgo waiting any longer. Not being able to release 1.01 because of some enhancement that can't be put against a timeline seems a poor decision.

 

[rekenaar]

I think it is important for plugin and skin developers to start working before the actual release otherwise nothing will work on the released version of MP.

The official reason for no release yet is that the testers and developers are working so hard to iron out the last few things and they do not really know what they will pick up and how long it will take to test. It sure is frustrating for an end user, but trust me, it is worth the wait. When I read all the testing and work that is done on a daily basis, I can do nothing but admire the dedication.

I've dutifully read all the FAQs and threads but it's been weeks (or months) since it was announced that MP 1.01 would be "delayed"

By the way, one of the devs leaked the planned release date a couple of days ago, but luckily it was not really noticed
And I think it is better that way since we do not want unnecessary pressure on them. And the planned date might change. Who knows.

Hang in there please...

 

[tesco]

Well things seem to be getting closer now since the 1.0.1 has been removed from the roadmaps.