nfoto Posted June 8, 2020 Share Posted June 8, 2020 TIFs can be 8bit, but frankly I don't see why one should bother when 16bit is the standard. Link to comment
Andy Perrin Posted June 8, 2020 Share Posted June 8, 2020 Yes, also I refuse to use 8bit/channel on principle. It leads to terrible results in skies especially. As the kids say these days, yeet[*] it into the sun! [*] yeet (verb) - to throw with extreme force Link to comment
OlDoinyo Posted June 9, 2020 Share Posted June 9, 2020 It appears that you don't have any level controls on this implementation--I find those to be useful. Having the infrared gamma adjusted separately for each channel seems clumsy, as it is nominally the same parameter. In the Pixelbender script, there is a master slider adjusting it simultaneously in every channel, with two "correction" sliders supplied for the R-->G and G-->B channels if needed (I don't use these very much.) The WavelengthPro interface is very similar. Notice the way I label the channels. If you just say "red" or "green" people can be confused: "green" could be either the R-->G channel or the G-->B channel. Link to comment
bostwickenator Posted June 9, 2020 Author Share Posted June 9, 2020 Seems like this solution doesn't fit what people expect. Quite a variety of distinct deal breakers were identified and only one person seemed immediately interested in the concept of doing this in browser if those were addressed. That being I'll just keep working on it for my own use cases. Link to comment
Recommended Posts
Please sign in to comment
You will be able to leave a comment after signing in
Sign In Now