Timeline for Took my first ever 4k picture; Why is it so disappointing?
Current License: CC BY-SA 3.0
12 events
when toggle format | what | by | license | comment | |
---|---|---|---|---|---|
Jul 20, 2016 at 10:21 | comment | added | Agent_L | @MichaelKjörling Biggest point is that unless photo is misexposed or wrongly whitebalanced, RAW provide neglible benefits over low-compression JPGs. And if one misexposes or can't do white balance, he needs to spend more time with the camera learning to get it right, not spend more in with a computer, trying to turn old crap into something slightly less crappy. Time spent on processing RAWs is better used on becoming a better photographer, that's why I strongly believe that no newcomer should ever bother or be bothered with RAWs. | |
Jul 20, 2016 at 10:14 | comment | added | Agent_L | @MichaelKjörling Nice catch! However there are 2 problems still: 1) RAWs provide Bayer-filtered data that need to be interpreted and 2/3 of missing information reconstructed. Algorithms for that are expensive and niche software rarely gives results on par with that provided by camera or Adobe. 2) using a new tool will wreak your workflow and it's unlikely you'll get good result with unfamiliar software. | |
Jul 20, 2016 at 9:33 | comment | added | user | @Agent_L Ufraw lists "Nikon D1" under "Other supported cameras as of today. (Looks like the most recent version is 0.22.) So does Dcraw RCS revision 1.477 date 2016/05/10 which Ufraw is based on. Does that count? | |
Jul 20, 2016 at 9:27 | comment | added | Agent_L | @MichaelKjörling RAWs are actually the most volatile of all formats and susceptible to digital rot. JPGs are future proof, not RAWs. Try finding a software that can open RAWs from Nikon D1 in 2016. in 15 years same will happen to what you shot today. The first rule of dealing with RAWs is: Process them now or delete them forever. Otherwise they're just a deadweight. | |
Jul 19, 2016 at 11:35 | comment | added | user | @Agent_L Unless you want to future-proof by shooting JPEG+RAW and keep the RAWs for those times when you want to go back and fix whitebalance or exposure or whatever later. | |
Jul 19, 2016 at 9:29 | comment | added | Agent_L | @ReeceDodds Also the RAW advice is a very bad one, because RAW is not an image at all. It's just a dump of sensor data that requires much work to turn it into a useful image. Unless someone knows how to perform this work, can do it better than the camera and is willing to actually put in the effort, advising to shot RAWs boils down to "make your photos cumbersomely large and unreadable". There is no need for RAWs until the need manifests itself. | |
Jul 19, 2016 at 9:28 | comment | added | Agent_L | @ReeceDodds DPI in JPEG is just a parameter. You can edit it to 1 dpi or to 10000 dpi and it won't change a singe pixel. It's merely a hint about how the file should be zoomed when displayed or printed. | |
Jul 19, 2016 at 5:20 | comment | added | Michael C | "The same resolution at 300dpi in JPG will be around 5-7MB in size. The same resolution JPG again but in 96dpi or 72dpi will only be 800-1200kB in size." ??!!??!!??!!?? 3840x2160 pixels is 3840x2160 pixels. The dpi has absolutely NO impact on image file size. Compression ratio does. | |
Jul 19, 2016 at 1:56 | comment | added | aroth | The role of sensor size in image quality/noise probably also warrants a mention here. | |
Jul 18, 2016 at 23:20 | comment | added | Reece | Also - shoot in RAW. JPEG/JPG is a lossy format and uses compression. So your JPG image won't be anywhere near as high quality as a RAW shot. And when you transfer it to a computer, do a straight copy without any import processing at all. An image with 3840x2160 resolution at 300dpi in RAW will be around 18MB in size. The same resolution at 300dpi in JPG will be around 5-7MB in size. The same resolution JPG again but in 96dpi or 72dpi will only be 800-1200kB in size. | |
Jul 18, 2016 at 18:35 | review | First posts | |||
Jul 18, 2016 at 19:49 | |||||
Jul 18, 2016 at 18:34 | history | answered | Xudonax | CC BY-SA 3.0 |