I searched for camera mods to allow for capturing of RAW data from the sensor on the Charge.
As far as I can tell, nobody has been successful in getting any Android phone to capture the RAW data.
Does anybody know if this is possible? I know others who would love to have the ability. I didn't really want to start a discussion of RAW vs JPEG compression, etc. I know the drawbacks and advantages of RAW.
I think that this would require camera firmware modifications as well as Camera APK modifications. My development knowledge is very limited, hence my name.
Does anybody know if this would require a reasonable about of effort or if its far beyond being worth the trouble?
It looks possible, and the code is in the API to do this, but it has yet to be done as far as I know. It looks to be an issue with the "RAW callback function" always returning NULL. If I have some time I will to look into it.
Do Not ask Questions in the Development thread if it is not Development it does not belong in here
Moving to General
My apologies and thanks.
Bumping this, seems like an interesting feature, considering it has API support.
bcpk said:
Bumping this, seems like an interesting feature, considering it has API support.
Click to expand...
Click to collapse
I would plus one this
Sent from my Xoom using XDA Premium App
I don't know if its prohibitively difficult to mod, but I couldn't find any other phone which has been developed to shoot RAW. Perhaps people just haven't shown much interest.
I would love this feature, but I figure most people shooting in RAW already have a "real" camera. I would expect a decent increase in photo quality though. I have 32 GB on my phone waiting to store some RAW data!
I just wish someone would mod the camera APK to use +2 sharpness, which would result in better quality photos. The camera app applies a bad blur/denoise filter on the lower sharpness settings which reduces the quality of the picture. Worse, the camera does not save that setting, so it needs to be set each time I use it.
BeefJerky9 said:
I just wish someone would mod the camera APK to use +2 sharpness, which would result in better quality photos. The camera app applies a bad blur/denoise filter on the lower sharpness settings which reduces the quality of the picture. Worse, the camera does not save that setting, so it needs to be set each time I use it.
Click to expand...
Click to collapse
You know u can modify the frame work for the camera, I've done it before, search xda. I doubt remember the form
Sent from my DROIDX using XDA Premium App
xdadevnube said:
I don't know if its prohibitively difficult to mod, but I couldn't find any other phone which has been developed to shoot RAW. Perhaps people just haven't shown much interest.
I would love this feature, but I figure most people shooting in RAW already have a "real" camera. I would expect a decent increase in photo quality though. I have 32 GB on my phone waiting to store some RAW data!
Click to expand...
Click to collapse
Shooting raw will make the color correction possible which will significantly boost the image quality to...a 70 dollars' compact camera you can find on ebay, BUT, the best camera is always the one that is with you, so I always support anyone who like to improve android phone's shooting ability.
---------- Post added at 02:38 AM ---------- Previous post was at 02:26 AM ----------
The real issue isn't allowing the camera to shoot raw because they can be done but the raw format will not be recognized by any raw processing software on the market. The possible way is to use DNG format which will significantly increase the difficulty of modification because it means the programmer will put in hours to create a brand new application to understand and compress the raw file to the DNG file...unlike Canon, android does not have an official raw format...so everything will need to start from zero. This process could easily take 20 very experienced engineers up to a year to complete, and the result might not be very ideal and will need another year to modify and improve...so we are looking at a potentially five million dollars project here - and it will better be turning in to profitable application - and if so it will have to be the best selling android app ever.
xdadevnube said:
I don't know if its prohibitively difficult to mod, but I couldn't find any other phone which has been developed to shoot RAW. Perhaps people just haven't shown much interest.
I would love this feature, but I figure most people shooting in RAW already have a "real" camera. I would expect a decent increase in photo quality though. I have 32 GB on my phone waiting to store some RAW data!
Click to expand...
Click to collapse
Yes, most (like myself) probably do but since I'm carrying around a high quality 8 megapixel camera in my pocket I'd like to be able to shoot in raw for those times that I don't have my DSLR with me. There is so much more that com be done to a RAW photograph, not to mention not having any data loss form it being converted to a jpeg. Looking forward to seeing if anyone can make this possible.
desmalta said:
Yes, most (like myself) probably do but since I'm carrying around a high quality 8 megapixel camera in my pocket I'd like to be able to shoot in raw for those times that I don't have my DSLR with me. There is so much more that com be done to a RAW photograph, not to mention not having any data loss form it being converted to a jpeg. Looking forward to seeing if anyone can make this possible.
Click to expand...
Click to collapse
Just a reminder....this is a cell phone, not a camera!
buhohitr said:
Just a reminder....this is a cell phone, not a camera!
Click to expand...
Click to collapse
Just a reminder, anything is possible in the world of android!
Sent from my SCH-I510 using XDA App
desmalta said:
Yes, most (like myself) probably do but since I'm carrying around a high quality 8 megapixel camera in my pocket I'd like to be able to shoot in raw for those times that I don't have my DSLR with me. There is so much more that com be done to a RAW photograph, not to mention not having any data loss form it being converted to a jpeg. Looking forward to seeing if anyone can make this possible.
Click to expand...
Click to collapse
RAW does not equal improved quality if the camera is not capturing more image information prior to compressing to JPG. You're still working with a tiny fixed lens and dense, compact sensor with tiny photo sites. This is limiting the amount and quality of light. Shooting RAW will not change this. JPG compression is not a limiting factor for image quality. You won't be able to resolve significantly finer detail or shoot in lower light settings just because you're shooting RAW. Open a JPG as RAW with Photoshop, it'll provide a similar experience.
You'll end up with similar photo quality, a bit more flexibility in PP, and huge lag while the camera tries to handle transfering and saving the huge photo file 10x larger than what it was designed to handle.
These are the only mobile phone sensors I've seen that would support or justify shooting in RAW.
Another story on them: http://www.engadget.com/2011/04/14/omnivisions-new-12mp-cmos-sensor-shoots-raw-pics-and-1080-60p-v/
In other words, RAW will be here eventually. When it is, it'll be an improvement. To try and force it (if it were even possible) with the sensor and hardware limitations in the DC is pointless.
charlie_c said:
RAW does not equal improved quality if the camera is not capturing more image information prior to compressing to JPG.
Click to expand...
Click to collapse
true, but shooting raw does preserve more of the image, because its the raw/real image that sensors seems is not a jpg processed image the way camera applications decided the scene should look like.
basically would would be taking your camera off the auto mode.
with raw you would have greated control over white balance, shadows, highlights etc...
There is a question about how many bits of image data you got on mobile sensor. On DSLR there is 12 or 14 bits information that is compressed to 8bit JPG information - that's why there is plenty more information about the image in RAW format. If CMOS in your mobile phone deliver just strait 8bit - your RAW will not have much more data.
As I don't have slightest idea how many bits of data is served by mobile camera sensor I can't say if there is a reason for RAW.
i found this
http://stackoverflow.com/questions/14777953/how-to-capture-raw-image-from-android-camera
i am really looking forward for a raw file from android camera this will be a huge move forward to the mobile world and the abilities of android
and since its supported in the api means google wants it to happen
Edit:
Create this dir /data/misc/camera/RaW_PiCtUrEs case sensitive btw
Assuming the capture mode used is high-quality and not high-quality-zsl it should produce a raw image everytime you capture a jpeg image
Click to expand...
Click to collapse
try this maybe it will work i found it here : http://forum.xda-developers.com/showthread.php?t=1977654&nocache=1
Related
I was testing out the HDR options for this and they do not seem to do much at all. There is a difference, but it is VERY minor. I took a shot without HDR, one with HDR, and then one using the free HDR app, and the HDR app simply blew the HTC HDR mode completely out of the water...
Has anyone else had any experience with this? Is there something I may be missing?
HDR always seemed like something better left to photo editing software to me (like photoshop). Phone camera filters always seem kind of lackluster, but then again, none of us are taking professional shots with a cell camera I assume
On topic though, I wouldn't doubt it being better. Sense stuff isn't exactly always perfection as far as software quality and HDR was probably just an afterthought tied into the camera so they could tick off a notch somewhere on some sheet for features.
Absolutely the same as my experience. I used HDR Camera from the market before this (free), and I really loved its results. When I installed the 3.0 Sense camera and saw the HDR setting, I was happy until I tried it. My theory is that it is NOT taking multiple pictures, but only doing an image adjustment --->> NOT the same thing. HDR Camera doesn't have the issues that some of you described. You do not have to be rock steady and my phone is plenty fast enough to take the three photos within about a second. The image settings are also adjustable (color, etc.).
On the other hand, the panorama mode in the Sense camera is Awesome!
yareally said:
HDR always seemed like something better left to photo editing software to me (like photoshop). Phone camera filters always seem kind of lackluster, but then again, none of us are taking professional shots with a cell camera I assume
On topic though, I wouldn't doubt it being better. Sense stuff isn't exactly always perfection as far as software quality and HDR was probably just an afterthought tied into the camera so they could tick off a notch somewhere on some sheet for features.
Click to expand...
Click to collapse
Software cannot do what HDR does. HDR takes 2 pictures, adjusting the gain on the sensor between low and high. It combines the best of both images to gain detail in low light areas and avoid over exposure in high light areas. Software will not work after the fact because the extra information gained from low/high gain is not present. Unfortunately the HDR option is poorly implemented by HTC. If you try HDR on the Iphone, you can see a drastic difference.
Actually, I use Pro HDR on my Evo, and it takes fantastic pictures in true HDR. It is a touch slower than a pro camera, but it does actually meter the scene and adjust the camera's aperture accordingly. It then allows for adjustments between the composite image and allows for saving the final as well as the source images, meaning you can do further editing elsewhere. Outside of some cropping, I haven't had problems.
With that said, I would be curious to know what the deal is with Sense. What's interesting is if you put it in HDR mode, it shows the little icon in the top right with multiple images...like whoever designed it at least understood how true HDR *should* operate. Then, if you push and release it instead of the regular shutter button, it beeps and you hear the lens go, and the image focuses itself. So...idk. I don't see a noticeable effect in the regular images at all...
I recently made the jump to 5.1.1 (XXU2BOGG) to be able to use the new Camera2 API and play around with RAW files (.dng’s here).
Thing is, when I shoot pics with a Camera2-enabled app (Camera FV-5 or Snap Camera HDR (which can even toggle API modes), the JPG’s it makes (besides the DNG’s) are unsharp. It’s very visible compared to when you shoot the same thing with a non-Camera2 API camera app. I wonder if it’s the same for others.
Here’s how you can check.
Shoot a pic with a Camera2 API enabled app such as Camera FV-5, with RAW/DNG support enabled.
Shoot a pic with a non-Camera2 API enabled app, such as Google Camera.
Compare the resulting JPG files (not the .dng)
For me, the latter is way sharper.
My theories of the cause:
Bad Camera2 API implementation by Samsung.
XXU2BOGG firmware is in XtreStoLite ROM (2.2.1 RC3), that makes my S6 say it's an S6 Edge. Maybe a driver issue. It's properly recognised as an SM-G920F, so I guess this is not a possible issue.
Complication of 5.0.2 ENG bootloader with 5.1.1 ROM. It's caused the fingerprint sensor to be broken, maybe it also breaks camera stuff.
jelbo said:
I recently made the jump to 5.1.1 (XXU2BOGG) to be able to use the new Camera2 API and play around with RAW files (.dng’s here).
Thing is, when I shoot pics with a Camera2-enabled app (Camera FV-5 or Snap Camera HDR (which can even toggle API modes), the JPG’s it makes (besides the DNG’s) are unsharp. It’s very visible compared to when you shoot the same thing with a non-Camera2 API camera app. I wonder if it’s the same for others.
Click to expand...
Click to collapse
It's normal but I know some guys have been asked why in that S6 Camera thread in the general section. I've played around with Snap and FV5 after up to 5.1.1 too. When you enabled API2, their JPG/PNG output will set the sharpen level to zero and indeed it is the original quality from your tiny sensor(we finally know how crap of 1/2.6" without post-processing).
I use Photoshop CS6 plus Adobe DNG Converter 9.1(I think Lightroom plus Adobe DNG Converter 9.1 does the same thing), they can read out the S6 RAW correctly though S6 isn't on the supported device list. After I turned the Sharpening amount to around 100 and denoise set to like 30, the photo quality is very similar to stock S6 camera now with good sharpness and no noise.
The stock camera(or other 3rd apps) default does a heavy job on sharp/denoise but if you ask for API2 and decided to shoot RAW, it's your turn now to do the adjustment by yourself.
TheEndHK said:
It's normal but I know some guys have been asked why in that S6 Camera thread in the general section. I've played around with Snap and FV5 after up to 5.1.1 too. When you enabled API2, their JPG/PNG output will set the sharpen level to zero and indeed it is the original quality from your tiny sensor(we finally know how crap of 1/2.6" without post-processing).
I use Photoshop CS6 plus Adobe DNG Converter 9.1(I think Lightroom plus Adobe DNG Converter 9.1 does the same thing), they can read out the S6 RAW correctly though S6 isn't on the supported device list. After I turned the Sharpening amount to around 100 and denoise set to like 30, the photo quality is very similar to stock S6 camera now with good sharpness and no noise.
The stock camera(or other 3rd apps) default does a heavy job on sharp/denoise but if you ask for API2 and decided to shoot RAW, it's your turn now to do the adjustment by yourself.
Click to expand...
Click to collapse
This makes sense, thank you, very good reply. So that basically means you have to choose between RAW and JPG, because the JPG won't be processed properly and thus be worse than the non-Camera2 API JPG.
Do you also see constant over-exposure 'flashes' when the light meter does it's thing? It happens with Snap Camera HDR and Open Camera (free Camera2 API app (that doesn't save photos when in that mode here)) as well.
jelbo said:
This makes sense, thank you, very good reply. So that basically means you have to choose between RAW and JPG, because the JPG won't be processed properly and thus be worse than the non-Camera2 API JPG.
Do you also see constant over-exposure 'flashes' when the light meter does it's thing? It happens with Snap Camera HDR and Open Camera (free Camera2 API app (that doesn't save photos when in that mode here)) as well.
Click to expand...
Click to collapse
Yes, I'm sure snap/fv5 will ignore the JPG/PNG sharpen filter when you take RAW and it is very weird. Indeed, we should report it to the developer, I think it is a bug. Because of that you have to choose between RAW and JPG/PNG now, not the combination of both.
I didn't test to disable API2 in snap/fv5 because if I don't shoot RAW, I will just use the stock camera. Just import the RAW in CS6/LR + DNG converter, set the sharpen amount to 80 ~ 110 and denosie 30 ~ 60, the result is pretty much same with stock camera now. So, no worry your API2 is normal.
Can you explain it a bit more about over-exposure flashes?
I'll explain the over-exposure later, but here are some samples I just worked on that illustrate your first point. All pics are untouched, losslessly saved crops and zoomed to 200%.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
^Google Camera (non-API2, default settings, lossless JPG crop (saved as .png)
^Camera FV-5 .JPG (non-API2, default settings, lossless JPG crop (saved as .png)
^Camera FV-5 .DNG (API2, default settings, Adobe Camera Raw 8.4 from Photoshop CS6 13.0.1 *no processing* crop (saved as .png)
^Camera FV-5 .DNG (API2, default settings, Adobe Camera Raw 8.4 from Photoshop CS6 13.0.1 *processed* crop (saved as .png)
jelbo said:
I'll explain the over-exposure later, but here are some samples I just worked on that illustrate your first point.
Click to expand...
Click to collapse
Yes, RAW isn't easy to deal with, every photo does need different set of parameters and very time consuming to find out best values. In some manner, RAW is only for real photo taker and professional. Stock camera or google camera on the other hands they do a smart job to optimize all photo automatically.
In your example, I don't see it over-exposure. It is just how the stock/google cam tweaked that for you. You can tune the exposure or any color in the DNG converter to achieve the same result but again it is a time wasting work.
And I would like to mention the DNG convertor default set at 25 sharpen(default 0 denoise) so it actually got some kinds of processing, so the ^Camera FV-5 .DNG is much sharper than ^Camera FV-5 .JPG. It looks like you are total new to RAW, I beat you understand how hard of it and time to lesson. Welcome to the Hell. lol
TheEndHK said:
Yes, I'm sure snap/fv5 will ignore the JPG/PNG sharpen filter when you take RAW and it is very weird. Indeed, we should report it to the developer, I think it is a bug. Because of that you have to choose between RAW and JPG/PNG now, not the combination of both.
Click to expand...
Click to collapse
Exactly. I'll contact their support again (but so far they haven't responded to previous e-mails). Made a post on Snap's Google+ page and updated my post in the Snap Camera HDR topic too (because Snap's JPG next to a DNG is the same unprocessed, fuzzy one).
I didn't test to disable API2 in snap/fv5 because if I don't shoot RAW, I will just use the stock camera. Just import the RAW in CS6/LR + DNG converter, set the sharpen amount to 80 ~ 110 and denosie 30 ~ 60, the result is pretty much same with stock camera now.
Click to expand...
Click to collapse
Just tested FV-5 with DNG capture set to Disabled, but the JPG's are still unprocessed (fuzzy).
So, no worry your API2 is normal.
Click to expand...
Click to collapse
Yeah, I'm convinced of the same now. It's just the Camera2 API apps doing a bad job. Maybe because of API limitations, or its a Samsung issue, who knows.
Can you explain it a bit more about over-exposure flashes?
Click to expand...
Click to collapse
Yeah. FV-5 doesn't have it, but Snap Camera HDR and Open Camera have it when using Camera2 API mode. In Auto Focus mode, all is well. But as soon as I manually focus by touching on the screen, you see it overexposing a few seconds after the focus was grabbed (Snap Camera HDR) or on the exact moment of manually focusing by touching (Open Camera). The photo taken is not overexposed.
Curious about three things:
1) is this S6 specific?
2) is this a XXU2BOGG bug? /edit: could be, but it's the same on XXU2COH2.
3) what would Manual Camera do? (Tempted to spend yet another few dollars to test that one out) /edit: bought and refunded: it doesn't 'see' the Camera2 API and it won't shoot in 16:9, just 4:3. o_o
TheEndHK said:
Yes, RAW isn't easy to deal with, every photo does need different set of parameters and very time consuming to find out best values. In some manner, RAW is only for real photo taker and professional. Stock camera or google camera on the other hands they do a smart job to optimize all photo automatically.
Click to expand...
Click to collapse
And I would like to mention the DNG convertor default set at 25 sharpen(default 0 denoise) so it actually got some kinds of processing, so the ^Camera FV-5 .DNG is much sharper than ^Camera FV-5 .JPG. It looks like you are total new to RAW, I beat you understand how hard of it and time to lesson. Welcome to the Hell. lol[/QUOTE]
I'm not new to RAW, I shoot RAW on my dSLR (Nikon had .NEF's) and I love getting the most out of my photos. It can be very complex yeah, and I agree that every photo ideally needs his own post processing settings.
Nice that you know quite a bit about it as well and have done tests. Let's hope we'll find the ultimate culprit and things will be fixed.
jelbo said:
Just tested FV-5 with DNG capture set to Disabled, but the JPG's are still unprocessed (fuzzy).
Yeah. FV-5 doesn't have it, but Snap Camera HDR and Open Camera have it when using Camera2 API mode. In Auto Focus mode, all is well. But as soon as I manually focus by touching on the screen, you see it overexposing a few seconds after the focus was grabbed (Snap Camera HDR) or on the exact moment of manually focusing by touching (Open Camera). The photo taken is not overexposed.
Click to expand...
Click to collapse
In FV5 you can't real disable API2(I can't find the option) but just tested to disable API2 in SnapCamera and after that the JPG sharpness comes back. Yup, it will over exposure a sec when you touch the manual focus bcoz it will bump up the iso to real high(you can notice the real-time iso info getting high) but it is just a minor bug.
It is interesting to see what will happen on Note5/S6e+, they comes with the ability to shoot RAW+JPG in stock camera.
TheEndHK said:
In FV5 you can't real disable API2(I can't find the option) but just tested to disable API2 in SnapCamera and after that the JPG sharpness comes back. Yup, it will over exposure a sec when you touch the manual focus bcoz it will bump up the iso to real high(you can notice the real-time iso info getting high) but it is just a minor bug.
Click to expand...
Click to collapse
Yeah, but as I got more or less the same in Open Camera, to me it feels like it's not app related but driver/device's API implementation.
It is interesting to see what will happen on Note5/S6e+, they comes with the ability to shoot RAW+JPG in stock camera.
Click to expand...
Click to collapse
There's a Note5 ROM port in the Android Dev subforum
jelbo said:
Yeah, but as I got more or less the same in Open Camera, to me it feels like it's not app related but driver/device's API implementation.
There's a Note5 ROM port in the Android Dev subforum
Click to expand...
Click to collapse
I know that but I'm on dual sims and not supported, so a no go to me and I'm still with my warranty didn't trip the knox yet because my camera got little weird sound, guess time to travel Samsung service center later.
Camera2 api app's always freeze
Hello, I had not seen any complaint at all, so i really wonder if no one cares or it really only happens on my phone. The problem is no matter which app I use, the screen always freezes on the s6 after taking about 8 to 9 raw pictures in a row. Does anyone experience it as well? Thanks.
I have had similar issues. Raw images are big. I think it's bogging down while writing to the SD card. Probably, it's the reason Samsung hasn't integrated raw into the stock camera.
Sheldor1967 said:
I have had similar issues. Raw images are big. I think it's bogging down while writing to the SD card. Probably, it's the reason Samsung hasn't integrated raw into the stock camera.
Click to expand...
Click to collapse
Ok... So it's not just me... Thank you for confirming.
I know the note 5 can handle the raw pictures well. Even the LG G4 has much slower internal storage. I do not own a G4 but I'm assuming the G4's stock camera is handling it well too. I believe it's bad implementation by Samsung, as it happens to all camera apps. And it's always the 9th raw picture screwing it. If Samsung is not trying to make this raw feature exclusive on the note 5, I'm sure they know how to make it work flawlessly on the s6 but they just don't want to.
In fairness, it really is a niche feature. Probably an extremely small percentage of S6 owners even know what raw is and an even smaller percentage would ever really use it. They probably figured they were fine not prepping for it. Now the external sd card and removal battery...
Sheldor1967 said:
In fairness, it really is a niche feature. Probably an extremely small percentage of S6 owners even know what raw is and an even smaller percentage would ever really use it. They probably figured they were fine not prepping for it. Now the external sd card and removal battery...
Click to expand...
Click to collapse
True it's a niche feature. But I would think that smaller percentage of s6 users who want to shoot raw is actually more people than the total number of note 5, edge+ and G4 users who can currently shoot stable raw. Given that the hardware of the s6 and note 5 should be very similar. It should not really be a hard implementation from Samsung. I will probably go back to nexus when the next one is out and never return to Samsung again.
fay99 said:
True it's a niche feature. But I would think that smaller percentage of s6 users who want to shoot raw is actually more people than the total number of note 5, edge+ and G4 users who can currently shoot stable raw. Given that the hardware of the s6 and note 5 should be very similar. It should not really be a hard implementation from Samsung. I will probably go back to nexus when the next one is out and never return to Samsung again.
Click to expand...
Click to collapse
Well, I guess if ya feel that strongly about it, it's the thing to do! Personally, I have never used a camera on a phone that performed this well, so I have no need to mess with raw and don't miss it. I was curious mostly, but Raw files are a lot of work to edit, so I won't bother.
Same here with Snap Camera or FV-5. Shooting passed 5 times may starting to have problem(need to kill the app to make it works again) while sometimes no problem up to 7 ~ 9 RAW. Not sure bad API2 implementation or 3rd apps not working good. Wish Samsung gives us stock RAW later or someone port it from Note5/S6e+.
I don't know what be can use at 5.1.1 (But I know that's can be use at Camera2 API at 10s - 1/8000s) but I will be does known' that's 6.0.1 as Marshmallow it's will be have in "OOTB" (On-Out-The-Box): Full-Pro Mode (as Shutter Speed/RAW - Pretty same options as 5.1.1 will have of Note 5/S6 Edge Plus Models)
I am attaching 1 raw and 1 jpg of the same photo. The noise from the raw photos are very high even on iso 50. Also vignetting is evident and exposure is down. Can these problems be fixed? Are they known problem? I had 3 phones with raw capabilities prior to this and the raw pics from the where excellent (LG G4 and G3).
https:// mega.nz/#F!QZ4mHCDI!QgKMil010ISvCzNKg7dFwQ
(sorry, i really dont know how to share the raw files just delete the space next to "https:// " from the link on ur browser)
Well, everything can be fixed manually in post (vignetting is fixed with radial filter, increase exposure by half a stop, and temperature and hue +10 in lightroom), but from inside the camera not really. What I found out, that if you take GCAM and shoot in raw, then it stacks multiple raws into one and noise is much lower, maybe try that, but you have to be on EMUI 8.1. And the problem with vignetting still persists, regardless which app you use, I think it has something to do with huawei's processing, other phones fix vignetting in raw before processing into jpeg, but Huawei propably shoots just raw and then fixes vignette while processing JPEG.
panjaksli said:
Well, everything can be fixed manually in post (vignetting is fixed with radial filter, increase exposure by half a stop, and temperature and hue +10 in lightroom), but from inside the camera not really. What I found out, that if you take GCAM and shoot in raw, then it stacks multiple raws into one and noise is much lower, maybe try that, but you have to be on EMUI 8.1. And the problem with vignetting still persists, regardless which app you use, I think it has something to do with huawei's processing, other phones fix vignetting in raw before processing into jpeg, but Huawei propably shoots just raw and then fixes vignette while processing JPEG.
Click to expand...
Click to collapse
Do you know any gcam port that works with the p20? I have emui 9. Thanks for your reply!
Unfortunately that's just how it is.
Despite what people say, it's not-so-great camera hardware backed by very good software, so much so that the hardware flaws of the sensors are masked by the over-aggressive post processing, and the occasional spectacular fail of the software distracts people from realising that the underlying hardware is the real issue.
Anyone know if raw dng photo capture is capable on this phone? And anyone know what sensor is used? The stock app does not seem to offer raw. It would be unfortunate if raw is not supported. Presumably the sensor is decent but Samsung stock software is usual not very good. 3rd party camera software rules, if raw is capable.
I tried using the pro shot app in the play store. No luck. There is a Samsung system app that crashes when trying to take a raw picture. Kind of annoying, I really would like to be able to take raw pictures because I use Lightroom to clean things up. Cleaning up a jpeg in the edit app on the camera/gallery pretty much destroys the quality by double compressing.
This is really frustrating because I'm sure the camera sensor is capable of taking raw images it's almost like Samsung is trying to prevent it at the OS level just to prevent people from having a good camera feature in a mid-range phone.
No RAW. You can download the Camera 2 API Prober to see all the feature it supports. It supports Camera 2 Limited (Full or Level 3 are better).
Yes, Samsung limited it at the system level, the processing is done by the kernel and the software only receives the result in JPG or HEIF. That's why you can't really use other camera apps to improve the results either.
poog said:
And anyone know what sensor is used?
Click to expand...
Click to collapse
The main camera (f/1.8, 0.8µm and around 1/1.7X" sensor size with PDAF and OIS) can either use a Samsung s5kgw1p sensor, commonly known as the GW1 or a Sony IMX682.
No camera2api LVL3/FULL support. Disappointing. Is there any way to port it?
DRSdroid said:
I tried using the pro shot app in the play store. No luck. There is a Samsung system app that crashes when trying to take a raw picture. Kind of annoying, I really would like to be able to take raw pictures because I use Lightroom to clean things up. Cleaning up a jpeg in the edit app on the camera/gallery pretty much destroys the quality by double compressing.
This is really frustrating because I'm sure the camera sensor is capable of taking raw images it's almost like Samsung is trying to prevent it at the OS level just to prevent people from having a good camera feature in a mid-range phone.
Click to expand...
Click to collapse
Do you able to capture raw/dng using Lightroom camera app?
Just wondering if there's any way I can get an astrophotography time lapse greater than 1 second? I would love to have 60 seconds, but I know it would probably take 4 hours or something.
Just wondering if this is possible or there's any third party apps that might be able to do this (take a longer exposure than the 4 minutes that astrophotography takes)?
I don't think it is possible, the astro time-lapse is made up from the images used to and then stacked for the astro image itself so you would end up with shed loads of images as well.
Have you tried just using the normal time-lapse option in the video settings?
Exactly, take a normal night video and then slow it down with editing software.
schmeggy929 said:
Exactly, take a normal night video and then slow it down with editing software.
Click to expand...
Click to collapse
The dude is talking about astrophotography and long exposure shots for a reason. What will a "night video" do good? And timelapse is not slowing down the video. lmao
That is my mistake, I totally read his post wrong.
Thing is the astro time laps is made up of the individual shots taken when Astrophotography mode is active so those individual image have been taken at f1.85, if you just did a normal time lapse using the main lens the video will still be at f1.85 and with a bit of post processing it should work.
The other way around it is to just take a night mode photo every 30 seconds for 2 hours using a timer and a Bluetooth remote.
MrBelter said:
Thing is the astro time laps is made up of the individual shots taken when Astrophotography mode is active so those individual image have been taken at f1.85, if you just did a normal time lapse using the main lens the video will still be at f1.85 and with a bit of post processing it should work.
The other way around it is to just take a night mode photo every 30 seconds for 2 hours using a timer and a Bluetooth remote.
Click to expand...
Click to collapse
You're talking about Aperture that is FIXED and completely irrelevant in this case. It's not like you have a variable aperture on the lens so you can adjust it.
What matters in his case is the shutter speed and the exposure time.
And no, normal timelapse WON'T work because the shutter speed will be low (fast) and the phone will try to compensate by pushing the ISO high. You'll end up with very dark scenes and TONS of noise.
And what makes Astro mode very important is the FRAME STACKING. Frame stacking reduces the overall noise and increases the "quality" of the image.
Deadmau-five said:
Just wondering if there's any way I can get an astrophotography time lapse greater than 1 second? I would love to have 60 seconds, but I know it would probably take 4 hours or something.
Just wondering if this is possible or there's any third party apps that might be able to do this (take a longer exposure than the 4 minutes that astrophotography takes)?
Click to expand...
Click to collapse
Not with stock camera.
You can try MotionCam Pro for that. It has a timelapse option where you can set your exposure time even to 15 seconds.
MotionCam is mainly for RAW video recording, but you can do photos and time-lapses. The output is absolutely GREAT. You're working with a RAW VIDEO basically and the quality is not comparable to ANY other app.
I had one Astro timelapse from it but I can't seem to find it now. It's sh**y weather outside now so can't do even a short one. I could do just a daylight one so you can see what quality I'm talking about here.
Uploaded a screenshot of the viewfinder. As you can see on the SS, you can adjust the ISO and shutter speed (among many other things) and do a timelapse.
This is basically taking RAW shots that you can later post process with various editing software like, Davinci Resolve, Adobe Premiere, Vegas, etc...
What you get is a video quality on the level of a DSLR and BETTER because there is no post-processing involved on the phone, it's basically RAW DNG images taken (sequence) that you can export (render) into a video at your QUALITY choice with YOUR post-processing involved.
Here is one sample I shot at and rendered to 4k60 (no color grading, just stock output).
Keep in mind that this is YOUTUBE, the quality of the original video is FAR better.
JohnTheFarm3r said:
You're talking about Aperture that is FIXED and completely irrelevant in this case. It's not like you have a variable aperture on the lens so you can adjust it.
What matters in his case is the shutter speed and the exposure time.
And no, normal timelapse WON'T work because the shutter speed will be low (fast) and the phone will try to compensate by pushing the ISO high. You'll end up with very dark scenes and TONS of noise.
And what makes Astro mode very important is the FRAME STACKING. Frame stacking reduces the overall noise and increases the "quality" of the image.
Click to expand...
Click to collapse
I know the aperture is fixed that's why i said it should work given the astrophotography mode time lapse is made up from the 16 images taken when the mode is active and not once the images have been stacked in to a single image. Given the way you talk you of all people should appreciate just how fast f1.85 is, not a single one of my Canon L lenses is that fast or even comes anywhere close to it.
The OP has nothing to lose by giving it a go before recommending extra software and shooting raw (it is raw BTW if we are getting picky, it isn't an acronym for anything).
MrBelter said:
I know the aperture is fixed that's why i said it should work given the astrophotography mode time lapse is made up from the 16 images taken when the mode is active and not once the images have been stacked in to a single image. Given the way you talk you of all people should appreciate just how fast f1.85 is, not a single one of my Canon L lenses is that fast or even comes anywhere close to it.
The OP has nothing to lose by giving it a go before recommending extra software and shooting raw (it is raw BTW if we are getting picky, it isn't an acronym for anything).
Click to expand...
Click to collapse
Where did I say ANYTHING against the fixed aperture of F1.85? I just said that since it's fixed, it's not relevant to the "settings" he uses since he CAN'T change the aperture value anyway.
It's not about "losing" anything, it's about the technical part of understanding that your recommendation won't work because it doesn't use long exposure shutter speeds or frame stacking.
By NOT using frame stacking, the noise will be horrible and there is little much you can do with post-processing without killing completely the "details" on the photo by suppressing both luma and chroma noise.
Another thing is that regular timelapse doesn't push long exposures...It's just not meant to be used for "astro", that's all.
Erm ok fella but how do you think this was all done before Google and its wonderful computational photography came along?
My point about the aperture is it is very fast so it being fixed is not irrelevant at all given it is the only chance of this even working, the OP may have tried it at 0.5x or 5x where the apertures are much slower, the OP has absolutely nothing to lose by giving it a go, it might be crap, you might end up with only the brightest objects in the sky, you might end up with a noisy mush and yet it might be good fun who knows.
Sadly there is always one person that comes along and stomps on the parade because they know best though isn't there?
MrBelter said:
Erm ok fella but how do you think this was all done before Google and its wonderful computational photography came along?
My point about the aperture is it is very fast so it being fixed is not irrelevant at all given it is the only chance of this even working, the OP may have tried it at 0.5x or 5x where the apertures are much slower, the OP has absolutely nothing to lose by giving it a go, it might be crap, you might end up with only the brightest objects in the sky, you might end up with a noisy mush and yet it might be good fun who knows.
Sadly there is always one person that comes along and stomps on the parade because they know best though isn't there?
Click to expand...
Click to collapse
It was done in a way that results were not even close to what we have today. Why use "outdated" methods when we have these VERY capable devices?
The app I suggested is great and has exactly what is he looking for.
Your logic of "How did we do this before XY time" is equal to "Let's just ride horses instead of cars because that's how we did it before". lmao