[News] MediaPortal 1.1.0 RC1 - delayed (1 Viewer)

[tourettes]

Instead of be waiting to RC1.. thouse of you that know how to compile the svn, you can compile it , test and report any new issue or revert on funcionality ...(I do this everyday) I have already report several bugs that has help the developer to fix the issue that he was fixing...

Instead of waiting for RC1, people should be waiting for the next SVN . We definitely need to build such as for example the TSReader related changes (among some other pretty high risk bug fixes) need wider verification than team only.

What comes to the SVN and building from it, currently it wont reflect the real source base that will be used for the next SVN as the TsReader related changes aren't yet in the main trunk, so testing results could be quite different and it is adviced not to report any tv related issues with self build SVN (this time only).

 

[infinite.loop]

What comes to the SVN and building from it, currently it wont reflect the real source base that will be used for the next SVN as the TsReader related changes aren't yet in the main trunk, so testing results could be quite different and it is adviced not to report any tv related issues with self build SVN (this time only).

I want to explain this a bit further to avoid that users think that we keep changes away from them.

The team has the policy that changes need to be tested "offline" first, before it is allowed to commit them to the trunk.
This is done to ensure that the trunk stays stable, and not to keep changes hidden from the public.

 

[mylle]

So can we have a new SVN already

 

[infinite.loop]

So can we have a new SVN already

a new public svn build will be published as soon as it is ready.
No ETA.

 

[mylle]

Hehe,

I have heard that before somewhere

Thanks for all your hard work. Looking forward to it

mylle

 

[wonkyd]

What comes to the SVN and building from it, currently it wont reflect the real source base that will be used for the next SVN as the TsReader related changes aren't yet in the main trunk, so testing results could be quite different and it is adviced not to report any tv related issues with self build SVN (this time only).

I want to explain this a bit further to avoid that users think that we keep changes away from them.

The team has the policy that changes need to be tested "offline" first, before it is allowed to commit them to the trunk.
This is done to ensure that the trunk stays stable, and not to keep changes hidden from the public.

The internal tests are much appreciated! The WAF would seriously decrease if the SVNs were completely broken because of a change. You only have to look at the change logs to see the enormous effort that is still going on behind the scenes.

I've been using 1.10 Beta since it came out and because I've left it alone since installing I've been able to sit back and enjoy it! I'm just going to wait patiently until RC1; it'll be ready when it’s ready. I'll be upgrading to Win7 then too.

Cheers guys and Merry Christmas.

P.S on a side note, tourettes whats the TSreader compatibilty with the Win7 H.264 codecs like at the moment?

 

[infinite.loop]

on a side note, tourettes whats the TSreader compatibilty with the Win7 H.264 codecs like at the moment?

The one available in the last public svn works like a charm here.
But be aware that if you use W7 codecs, then you have to use it for mpeg2 AND h.264.
You can not combine it with other video codecs (i.e. mpeg2=MS DTV | h.264=coreavc) since that will lead to issues caused by the MS DTV codec (it does not like to be in the graph with othet video codecs - to put it simple).

In 1.1.0 RC1, MP Configuration wont let you choose not working combinations of videocodecs to avoid issues.

 

[wonkyd]

on a side note, tourettes whats the TSreader compatibilty with the Win7 H.264 codecs like at the moment?

The one available in the last public svn works like a charm here.
But be aware that if you use W7 codecs, then you have to use it for mpeg2 AND h.264.
You can not combine it with other video codecs (i.e. mpeg2=MS DTV | h.264=coreavc) since that will lead to issues caused by the MS DTV codec (it does not like to be in the graph with othet video codecs - to put it simple).

In 1.1.0 RC1, MP Configuration wont let you choose not working combinations of videocodecs to avoid issues.

Thats no problem, the MS MPEG2 video decoder in Vista has never given me any problems. The audio decoder has, never seems to want to play ball with AC3 audio on H.264 streams. I take it I can still use FFDShow for audio with live TV though?

 

[infinite.loop]

on a side note, tourettes whats the TSreader compatibilty with the Win7 H.264 codecs like at the moment?

The one available in the last public svn works like a charm here.
But be aware that if you use W7 codecs, then you have to use it for mpeg2 AND h.264.
You can not combine it with other video codecs (i.e. mpeg2=MS DTV | h.264=coreavc) since that will lead to issues caused by the MS DTV codec (it does not like to be in the graph with othet video codecs - to put it simple).

In 1.1.0 RC1, MP Configuration wont let you choose not working combinations of videocodecs to avoid issues.

Thats no problem, the MS MPEG2 video decoder in Vista has never given me any problems. The audio decoder has, never seems to want to play ball with AC3 audio on H.264 streams. I take it I can still use FFDShow for audio with live TV though?

I suggest to use MPV-MPA for audio. Works like a charm.

And you can choose whatever audiocodec you want. The limitation is just about the videocodecs.

 

[regeszter]

It means MS DTV + ffdshow raw (for post process) are not in a possible combination?