X3100 Battle Continues

02.26.08 4 Comments

Very strange…there appears to be something fundamentally wrong or different with the X3100, as best I can tell from my extremely limited experience with such things. Which probably means I’m completely wrong.

D4rk helped me get set up compiling my own fragment programs (thank you!). The approach I took is what I always do, which is get the working code on one end, the non-working code on the other, and then move towards the middle until you find out what breaks.

I took out all the matrix multiplication, and just started with some basic transformations to see what worked. While rgb.r = 1.164 * yuv.r; produced the expected pixel color rgb.r = 1.164 * (yuv.r – 16.0/256.0) + 1.596 * (yuv.b – 128.0/256.0); doesn’t (at least according to my Numbers spreadsheet). So tomorrow I’ll do some more back and forth to see if I can figure out why the second formula isn’t working. (Note that it DOES work on an NVidia card). Doing debugging where the only way to output debugging information is through 0-1 values in pixel color components has given me new respect for people who work in that field.

Share on FacebookTweet about this on TwitterShare on Google+Share on LinkedIn
Share this

4 Comments

  • There are times when I think I could handle being a programmer (I’m a sysadmin).

    Then I read a post like this.

    Good luck, man :-)

  • Could it be a problem with SDL?

  • Thanks for all the hard work you put into this. Hopefully all the x3100 issues can be solved.

  • Thanks for putting down so much work in this. And i hope some of our comments motivate you to still keep on. At the moment i am using my 360 as a media center, mostly watching HD movies in WMV format.

Leave a Reply

Your email address will not be published. Required fields are marked *

You may use these HTML tags and attributes: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <strike> <strong>