Computing desk | ||
---|---|---|
< March 21 | << Feb | March | Apr >> | Current desk > |
Welcome to the Wikipedia Computing Reference Desk Archives |
---|
The page you are currently viewing is an archive page. While you can leave answers for any questions shown below, please ask new questions on one of the current reference desk pages. |
How small can pixel get, until it does not make sense, since humans won't notice the difference? -- Doroletho ( talk) 14:19, 22 March 2018 (UTC)
I've been working on a suite of image enhancement and analysis tools. I've been using a set of decent jpegs converted to bmp as test images, and I've gotten good results, but I would, ideally, like to work with a source that has more bits per channel than 8.
However, I am not sure the best way to go about this. My ideal work flow would to be find a converter from Raw to Tiff that will give me a 16bit per channel image, then to import this into C++ using some library.
On the first front, I've seen some people mention, elsewhere, that certain Raw viewed and converters just work with the jpg of the image embedded in the file, which would be a major problem for me.
On the second front, libtiff seems like what I should be using for programming, but I am under the impression you can't do more than 8 bits per channel.
Is all of this accurate? Any suggestions or resources that might help? Would it be worth my time to just code my own reader and writer for the Tiff format?
I come for more of a mathematics background than a tech one, so while I can code competently and have no problem with the theoretical side of what I'm actually doing, I'm a bit out of my depth with the specifics of dealing with the file types (which is why i went jpeg to bmp, it's easy to convert and bmp is easy to code a reader for).
Any help would be greatly appreciated, thank you very much. 2600:1016:B027:8A65:A34D:55AF:2185:D518 ( talk) 17:33, 22 March 2018 (UTC)
Computing desk | ||
---|---|---|
< March 21 | << Feb | March | Apr >> | Current desk > |
Welcome to the Wikipedia Computing Reference Desk Archives |
---|
The page you are currently viewing is an archive page. While you can leave answers for any questions shown below, please ask new questions on one of the current reference desk pages. |
How small can pixel get, until it does not make sense, since humans won't notice the difference? -- Doroletho ( talk) 14:19, 22 March 2018 (UTC)
I've been working on a suite of image enhancement and analysis tools. I've been using a set of decent jpegs converted to bmp as test images, and I've gotten good results, but I would, ideally, like to work with a source that has more bits per channel than 8.
However, I am not sure the best way to go about this. My ideal work flow would to be find a converter from Raw to Tiff that will give me a 16bit per channel image, then to import this into C++ using some library.
On the first front, I've seen some people mention, elsewhere, that certain Raw viewed and converters just work with the jpg of the image embedded in the file, which would be a major problem for me.
On the second front, libtiff seems like what I should be using for programming, but I am under the impression you can't do more than 8 bits per channel.
Is all of this accurate? Any suggestions or resources that might help? Would it be worth my time to just code my own reader and writer for the Tiff format?
I come for more of a mathematics background than a tech one, so while I can code competently and have no problem with the theoretical side of what I'm actually doing, I'm a bit out of my depth with the specifics of dealing with the file types (which is why i went jpeg to bmp, it's easy to convert and bmp is easy to code a reader for).
Any help would be greatly appreciated, thank you very much. 2600:1016:B027:8A65:A34D:55AF:2185:D518 ( talk) 17:33, 22 March 2018 (UTC)