Same here but I'm just so sick of the world of SVN 
Would try with 1.02. And second that comment about some one looking into this.. Thanks
Would try with 1.02. And second that comment about some one looking into this.. Thanks
Flickering Tv-guide and other overlays with EVR enabled (6 Viewers)
- Thread starter pnyberg
- Start date
Unfortunately I'm not looking into this issue actively, just happened to spot something in MSDN and tried it (and it didn't help).
- December 6, 2007
- 432
- 14
- Home Country
-
Netherlands
I use a nvidia card, but saw this post:
https://forum.team-mediaportal.com/...rc1-release-plan-68187/index3.html#post495879
Ith might be fixed.
https://forum.team-mediaportal.com/...rc1-release-plan-68187/index3.html#post495879
Ith might be fixed.
- December 6, 2007
- 432
- 14
- Home Country
-
Netherlands
Ok, that is why.
No, it's not for me (Catalyst 9.8). Also tried some really fast GPUs like Radeon 4770 and Radeon 4850 - they also flicker. And under Windows 7 they also flicker. But it is really a problem within Mediaportal. I don't know any other application that suffer from this problem.
The only trick for me to solve this is using FFDShow as MPEG2-decoder, forcing NV12-output and forcing Bobbing in the Output settings. You'll get hardware deinterlacing and there is no flicker at all. The only problem remains is that Mediaportal is still blacklisting FFDShow as decoder within MyTV and I have to set FFDShow to connect more than once so that it can connect to Mediaportal.
tourettes
Could you delete the blacklisting permanently within Mediaportal? I think it is not neccessary anymore.
The only trick for me to solve this is using FFDShow as MPEG2-decoder, forcing NV12-output and forcing Bobbing in the Output settings. You'll get hardware deinterlacing and there is no flicker at all. The only problem remains is that Mediaportal is still blacklisting FFDShow as decoder within MyTV and I have to set FFDShow to connect more than once so that it can connect to Mediaportal.
tourettes
Could you delete the blacklisting permanently within Mediaportal? I think it is not neccessary anymore.
- Thread starter
- #287
Well actually I'm not suffering that much any longer, it's been a lot better than it was when I first reported it. The devs have almost got rid of it - at least on my system (Vista (server2008) HD2600XT). So for me this is almost "case closed".
Are you sure that it is working ok with MPEG2 / MPEG4 channel changes as that was the reason why TsReader has been blocking ffdshow in the past. Most likely that issue is caused by TsReader itself (wrong output pin info delivered to codecs). No one has had time to fix it -> blocking gives better user experience as channel changes aren't freezing when user uses ffdshow as H.264 codec.
tourettes
If I remember correctly, FFDShow does not work very well as H264-decoder for Mediaportal. I am using FFDShow only as MPEG2-decoder.
I have this MPEG2 / MPEG 4 changing channel freezes because of the blocking. Do you remember, you already sent me an unblocked Tsreader.ax some time ago and that was working very nicely (no channel freezes anymore). I have disabled H264-decoding within FFDShow so it won't interfere with other codecs like the Cyberlink H264-codec.
It would be nice if the unblocking of FFDShow could be disabled - just as an clickable option for example.
If I remember correctly, FFDShow does not work very well as H264-decoder for Mediaportal. I am using FFDShow only as MPEG2-decoder.
I have this MPEG2 / MPEG 4 changing channel freezes because of the blocking. Do you remember, you already sent me an unblocked Tsreader.ax some time ago and that was working very nicely (no channel freezes anymore). I have disabled H264-decoding within FFDShow so it won't interfere with other codecs like the Cyberlink H264-codec.
It would be nice if the unblocking of FFDShow could be disabled - just as an clickable option for example.
Too many options make application too complex for average user (althou I don't mind such, but rest of the team doesn't agree with me that MP is not targeted to average consumers
)., and complex application will have 1) wrongly configured applications (end user bugs)
2) more bugs in code as code base gets bigger
...also it will take development time to:
1) patch config application
2) patch MP to provide new setting to TsReader
3) patch TsReader interface
4) patch TsReader to behave correctly according to the new setting (small part of the required code changes)
Few of our team members did test the unblocked ffdshow MPEG2 and it was causing some trouble, so we cannot say it is working correctly and continue blacklisting it. It will be tested again when the TsReader matures/starts to work correctly with it's output pin information.
What might be possible is to add a debug .txt file that could be used to disable the blacklisting, I'll talk to the team about this to see what they think about it.