Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>Why do you make the assumption that they use the same formula?</p> <p>Even if they do use the same formula and you accept that the implementation is different would you expect the output to be the same?</p> <p>At the end of the day the code is designed to work with perception not be mathematically precise. Although you can get this with CUDA if you want. </p> <p>Rather than being suprised that you get different results i would be very suprised if you got pixel perfect matches.</p> <p>the way they represent colour is different ... I know for a fact nvidia uses a float(maybe double) to represent colour wheras GDI uses int i believe.</p> <p><a href="http://en.wikipedia.org/wiki/GPGPU" rel="nofollow">http://en.wikipedia.org/wiki/GPGPU</a></p> <p>In DX9 shader 2.0 appears which is when the implementation of colour switched from int to 24 and 32 bit floats.</p> <p>try comparing ati/amd rendering to nvidia rendering and you can clearly see that colour is very different. I first noticed this in quake 2 ... the difference between the 2 cards was staggering - of course that is due to a great many number of things, least of which is their bilinier interp implementation.</p> <p>EDIT: the info about how the specification was made happeend after i answered. Anyway i think the datatypes used to store it iwll be different no matter how you specify it. Moreover the implementation of float is likley to be different. I may be wrong but im pretty sure that c# implements float differently to the C compiler that nvidia uses. (and that assumes that GDI+ doesnt just convert the float into the equivalent int ....)</p> <p>Even if i am wrong about that I would enerally hold it to be exceptional to expect 2 different implementations of an algorithm to be identical. they are optomised for speed as a result the difference in optomisation will directly translate to a difference in image quality as this speed will come from a different approach to cutting corners/approximation.</p>
    singulars
    1. This table or related slice is empty.
    1. POBilinear interpolation - DirectX vs. GDI+
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USJohn Nicholas
    1. USJohn Nicholas
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTBountyClose
    1. CO+1 for bringing up the float/byte color-representation issue. The one-bit difference may be simply rounding differences.
      singulars
      1. PO
      1. USStephen Chung
    2. COI added a clarifying point - these are grayscale images (R=G=B)
      singulars
      1. PO
      1. USholtavolt
    3. CO@John - the color elements are being specified identically (GDI+ = PixelFormat.Format32bppPArgb, DX9 = Format.X8R8G8B8)
      singulars
      1. PO
      1. USholtavolt
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload