ATI 690G/x1250 problems (2 Viewers)

[kszabo]

I downgraded to 7.2 and it worked fine. What am I missing? What is this underscanning stuff you're talking about?

I talk about black frame around desktop (overscan) or desktop too big for screen (underscan) if I connect through HDMI. In Catalyst Control Center you can correct it with 60 Hz but not if you use 50 Hz.

 

[pbb]

I downgraded to 7.2 and it worked fine. What am I missing? What is this underscanning stuff you're talking about?

I talk about black frame around desktop (overscan) or desktop too big for screen (underscan) if I connect through HDMI. In Catalyst Control Center you can correct it with 60 Hz but not if you use 50 Hz.

I thought it was the other way around? Underscan shows a black border around your image, and overscan hides some of the picture behind the TV frame...

 

[AndreasHaas]

So many peoples using the 690g chipset. Why can MP-Team say it is an bug in MediaPortol software or in the ATI driver. I wait now 2 month for new driver or a stable MP.

I'm realy unhappy? I think i should switch to other Hardware and other Software

Sorry for my english.:sorry:

 

[The_Stig]

Hey Andreas...

stay calm...its christmas time!

What do you think it is? This chipset is the only one having these problems. So what is more likely? Hardware bug or MP bug? I further dont see a real problem, either use older drivers, or turn of FLIPY or buy a cheap new GFX...

You have several options.

 

[rtv]

My MediaPortal-PC is running on a nv6150/430 chipset therefore I cannot reproduce that issue here. Just for the case that some ATI dev wants to know what we are doing to trigger the bug - this part using plain methods of the Microsoft.DirectX.Direct3D namespace to update the "camera position" is the one and only place where the FLIP transformation is done:

      Point offset = new Point(camera.X - (Width / 2), camera.Y - (Height / 2));

      // grab the viewport dimensions and location
      Viewport viewport = DX9Device.Viewport;
      float w = viewport.Width * 0.5f;
      float h = viewport.Height * 0.5f;

      // world view.  Until this is moved onto the GPU (via a vertex shader for instance), we set it to the identity
      // here.
      Matrix mtxWorld;
      mtxWorld = Matrix.Identity;
      DX9Device.Transform.World = mtxWorld;
      // camera view.  Multiply the Y coord by -1 then translate so that everything is relative to the camera
      // position.
      Matrix flipY, translate, mtxView;
      flipY = Matrix.Scaling(1.0f, -1.0f, 1.0f);
      translate = Matrix.Translation(-(viewport.X + w + offset.X), -(viewport.Y + h + offset.Y), 2 * h);
      mtxView = Matrix.Multiply(translate, flipY);
      DX9Device.Transform.View = mtxView;

      // projection onto screen space
      Matrix mtxProjection = Matrix.PerspectiveOffCenterLH((-w - offset.X) * 0.5f, //Minimum x-value of the view volume.
                                                    (w - offset.X) * 0.5f, //Maximum x-value of the view volume.
                                                    (-h + offset.Y) * 0.5f,//Minimum y-value of the view volume.
                                                    (h + offset.Y) * 0.5f,//Maximum y-value of the view volume.
                                                    h,//Minimum z-value of the view volume.
                                                    100 * h);//Maximum z-value of the view volume.
      DX9Device.Transform.Projection = mtxProjection;

MP-2 indeed uses the GPU's shader units to do stuff like this. However this is plain .NET usage which is supposed to be supported by graphics drivers...

The corresponding documentation from Microsoft can be found here.

 

[kszabo]

So many peoples using the 690g chipset. Why can MP-Team say it is an bug in MediaPortol software or in the ATI driver. I wait now 2 month for new driver or a stable MP.

I'm realy unhappy? I think i should switch to other Hardware and other Software

Sorry for my english.:sorry:

do it! at least you did not pay for MP! Otherwise keep cool :- )

I wait and till I use flip castrated skins!

Another GFX is not an option for some barebone users (like my Asus Pundit http://www.asus.de/products.aspx?l1=1&l2=3&l3=483&l4=0&model=1797&modelmenu=1)
We have only 1 PCI slot for our TV-Card

RTV: thanx for your post, it is the most constructive in the whole thread. I hope someone can do something with the information you privided!

 

[AndreasHaas]

yes it's right, i did not pay for MediaPortal.

and MediaPortal is the best Multimedia Software i tested until today.

and i hope we can use this great software with all these great options and the newest driver soon.

i stay cool and i wish all a Merry Christmas!

 

[Spragleknas]

I have reopened my ticket and provided a link to the rtv's post asking it to be forwarded to the Catalyst Team.

(and I was VERY polite - even wishing a Merry Cristmas, and not mentioning word like nVidia or using sarcasm)

 

[HDnewt]

I have the same problem with my 690g (Asus M2A-VM HDMI) on Windows XP Pro. :/ I hope for a new working driver.

HDnewt

 

[Spragleknas]

Everybody with a 690G does