Related
Hi
I have a problem with my Nexus 4 camera, the pictures taken are quit good (Not best quality - and by this I mean pictures of people, places etc.. not documents) but when I zoom them just a little, Its all blurry (during the shot, or after taking it) which should not be the case for a 8mp camera ( I had Xperia P, pictures with its 8mp camera were OUTSTANDING! ), and the thing that bothers me most, its taking pictures of documents : ALWAYS blurry, never good or lisible to read.
Please help me solve this
Z.Blackbeard said:
Hi
I have a problem with my Nexus 4 camera, the pictures taken are quit good (Not best quality - and by this I mean pictures of people, places etc.. not documents) but when I zoom them just a little, Its all blurry (during the shot, or after taking it) which should not be the case for a 8mp camera ( I had Xperia P, pictures with its 8mp camera were OUTSTANDING! ), and the thing that bothers me most, its taking pictures of documents : ALWAYS blurry, never good or lisible to read.
Please help me solve this
Click to expand...
Click to collapse
No solution. The camera on this phone sucks. Don't bother with zooming; it's pointless. Zooming is digital and merely crops, rather than actually zooming in optically like a "real" camera.
If you're taking pics of still things, use a timer. That way you can initiate the taking of the picture and stabilize yourself, rather than trying to keep your hands steady while also hitting the shutter "button". Or use a voice-activated shutter.
At first on kitkat 4.4.4, I had some good pics with it :/ isnt it a do of software? this is really despressing to know that this camera originally sucks to this level :/ thanks anyway
Greetings guys, ive seen that the camera api 2 is still broken for galaxy s6 in the android m, this can be checked easelly by running any custom camera app like camera fv 5, a better camera or proshot camera.
All of them return blurry pictures with camera api 2, while works flawlessly with old camera api.
Even though im very very happy with the galaxy default camera app finally supporting shutter speed and raw, i was hoping the camera api 2 wouldve been properly implemented in this build which unfortunatelly it wasnt.
So im trying to do get as much data as possible by asking you guys to post your phone model, android version, sensor brand/model and experience with camera api 2:
Ill go first:
Phone: G920F
Android: Android 6.0.1
Camera Sensor: Sony_IMX240 (To check your sensor install this app from google play: https://play.google.com/store/apps/details?id=com.finalwire.aida64&hl=pt_PT)
Testing:
ProShot(Paid) Blurry pictures,
Camera FV5(Paid)=Blurry Camera API2 (Resolution maximum of 8mp) and up to 3200 iso, but normal image quality with old camera api (Resolution maximum of 16mp) but only 800iso,
A Better Camera (Paid) Blurry Camera Api2 but normal image quality with old camera api.
This problem is included in lollipop 5.1.1
I talk with proshot developers for this problem 5 months ago and he hasn t solution
supera3 said:
This problem is included in lollipop 5.1.1
I talk with proshot developers for this problem 5 months ago and he hasn t solution
Click to expand...
Click to collapse
Hi! I'm the dev of ProShot. I'm really stumped on the soft images issue on Samsung phones. If you shoot RAW you will see that correct focus was achieved, but the JPEG doesn't look quite right. Running a simple sharpen filter produces results closer to the stock camera app, but it's not quite 100%.
No other device has this issue, so Samsung is definitely at fault here. And only offering 8MP resolutions in Android M is a pretty bad oversight, they clearly didn't test this update that well :/
Hi all , I have to say that with CameraFV all problems said up are same here - blury detail on jpg photo , 8mpx max resolution for jpgs in MM. But in RAW everything is just right - detail and resolution. Dont know where is problem but think on 90% is base on Samsung's camera driver. Dont know also situation in S7.
A made also comparisson between RAWs in CameraFV and Stock Camera app for Sammy and may say that cameraFV take better detail at all , stock camera app has more noise and detail is more aggressive.
If u want i can upload reaults here to discuss
Cheers !
edee1337 said:
Hi! I'm the dev of ProShot. I'm really stumped on the soft images issue on Samsung phones. If you shoot RAW you will see that correct focus was achieved, but the JPEG doesn't look quite right. Running a simple sharpen filter produces results closer to the stock camera app, but it's not quite 100%.
No other device has this issue, so Samsung is definitely at fault here. And only offering 8MP resolutions in Android M is a pretty bad oversight, they clearly didn't test this update that well :/
Click to expand...
Click to collapse
Thank you for your contribution people, both camera fv5 and proshot are excelent camera apps. I actually love the ability to disable ois in proshot and the very nice ui. It is indeed a shame that samsung didnt pay more attention to fix buggy camera api 2. I really like the stock app in MM it has pretty much everything and im very happy with it but the phone camera couldve been even more perfect than it already is with proper support for custom camera apps :/
edee1337 said:
Hi! I'm the dev of ProShot. I'm really stumped on the soft images issue on Samsung phones. If you shoot RAW you will see that correct focus was achieved, but the JPEG doesn't look quite right. Running a simple sharpen filter produces results closer to the stock camera app, but it's not quite 100%.
No other device has this issue, so Samsung is definitely at fault here. And only offering 8MP resolutions in Android M is a pretty bad oversight, they clearly didn't test this update that well :/
Click to expand...
Click to collapse
Does this happen in S7 or S6E+ Marshmallow?
Yesterday I borrowed my friends LG G4 and found out they still have best implementaion of camera2 api.
Smasung photos will have always have grennish yellowish tint.
sarvesh563 said:
Does this happen in S7 or S6E+ Marshmallow?
Yesterday I borrowed my friends LG G4 and found out they still have best implementaion of camera2 api.
Smasung photos will have always have grennish yellowish tint.
Click to expand...
Click to collapse
Still haven't been able to get the MM update on my S6, but from other reports I hear it still might be there.
I use ProShot and I get blurry shots on my S6 but to be honest some pictures come out awesome, as if shot using a DSLR, and some it's just too soft. It's not the dev's fault, it's Samsung's.
I use ProShot on my LG G4 also and it doesn't have an issue with that. Noise Reduction removal is better in the G4 as well. In the S6 you see some type of weird over sharpening effect.
What I love about ProShot (with low noise reduction) is that it removes Samsung's over sharpening effect and extreme contrast so pictures come out natural.
---------- Post added at 06:03 PM ---------- Previous post was at 06:03 PM ----------
edee1337 said:
Hi! I'm the dev of ProShot. I'm really stumped on the soft images issue on Samsung phones. If you shoot RAW you will see that correct focus was achieved, but the JPEG doesn't look quite right. Running a simple sharpen filter produces results closer to the stock camera app, but it's not quite 100%.
No other device has this issue, so Samsung is definitely at fault here. And only offering 8MP resolutions in Android M is a pretty bad oversight, they clearly didn't test this update that well :/
Click to expand...
Click to collapse
Here's the interesting thing, when you disable noise reduction on the S6, the pictures are sharp and not blurry.
TheWarKeeper said:
Greetings guys, ive seen that the camera api 2 is still broken for galaxy s6 in the android m, this can be checked easelly by running any custom camera app like camera fv 5, a better camera or proshot camera.
All of them return blurry pictures with camera api 2, while works flawlessly with old camera api.
Even though im very very happy with the galaxy default camera app finally supporting shutter speed and raw, i was hoping the camera api 2 wouldve been properly implemented in this build which unfortunatelly it wasnt.
So im trying to do get as much data as possible by asking you guys to post your phone model, android version, sensor brand/model and experience with camera api 2:
Ill go first:
Phone: G920F
Android: Android 6.0.1
Camera Sensor: Sony_IMX240 (To check your sensor install this app from google play: https://play.google.com/store/apps/details?id=com.finalwire.aida64&hl=pt_PT)
Testing:
ProShot(Paid) Blurry pictures,
Camera FV5(Paid)=Blurry Camera API2 (Resolution maximum of 8mp) and up to 3200 iso, but normal image quality with old camera api (Resolution maximum of 16mp) but only 800iso,
A Better Camera (Paid) Blurry Camera Api2 but normal image quality with old camera api.
Click to expand...
Click to collapse
There is a app called cinema 4k which also uses camera2 api. It didn't work on marshmallow so i had to downgrade to lollipop, after downgrading it worked without any problems
the tech blog on insta said:
There is a app called cinema 4k which also uses camera2 api. It didn't work on marshmallow so i had to downgrade to lollipop, after downgrading it worked without any problems
Click to expand...
Click to collapse
Thats because when you downgraded the camera api 1 was used by the app bu default instead of camera api 2
TheWarKeeper said:
Thats because when you downgraded the camera api 1 was used by the app bu default instead of camera api 2
Click to expand...
Click to collapse
Whats the difference between camera1 api and camera2 api
Camera FV-5 fixed. (16Mpix available, etc...)
atherion said:
Camera FV-5 fixed. (16Mpix available, etc...)
Click to expand...
Click to collapse
Which version you use
don_gori said:
Which version you use
Click to expand...
Click to collapse
Latest 3.15.1
I have some issues with RAW capturing on 3.15.1 , on 10 photos only 1 had DNG file ?
Hi!
I'm on stock marshmallow with the august security patch. According the the manual camera test app my phone does not have raw capabilities. What could be causing this? (I can capture raw with the default camera app just fine)
4k issue on galaxy s7 shots 3264x2448 instead of 3840x2160 using Proshot. Please fix this. No 60fps for FHD option as well.
I have been wading through all the YouTube videos trying to get an idea if the ZTE Axon 7 will be my next phone and I find this
I am totally suprised at how good the OIS / EIS is working and it looks to me very similar to the S7 and iPhone 6s+ stabilisation.
If anyone has the phone please let us know what you think and if you can post some video capture in 1080p that would be great to.
The autofocus seems lost too often in this scene...
masterbox said:
The autofocus seems lost too often in this scene...
Click to expand...
Click to collapse
It does. Software issue so could be fixed ? But how about that ois
How many axis OIS and EIS are these?
Is EIS part of camera unit or is it ZTE development?
Does EIS operate in case of 4K and/or 60fps?
obladi64 said:
How many axis OIS and EIS are these?
Is EIS part of camera unit or is it ZTE development?
Does EIS operate in case of 4K and/or 60fps?
Click to expand...
Click to collapse
I don't know as in the UK it's still not released yet
OIS is hardware and EIS is the electronic image stabilisation in the software. It looks floating like an iPhone or Samsung s7 but I would compare it more to the iPhone 6s plus but as someone already commented it is hunting for focus too much. Let's hope we can lock focus at least until they release the promised updates.....lol. Zte updating a phone. I think we will have more luck with custom roms if they unlock the bootloader!
The OIS is performing so well wow. Some of the other videos show really bad performance, wonder if its part of a new update?
ipmanwck said:
I don't know as in the UK it's still not released yet
OIS is hardware and EIS is the electronic image stabilisation in the software. It looks floating like an iPhone or Samsung s7 but I would compare it more to the iPhone 6s plus but as someone already commented it is hunting for focus too much. Let's hope we can lock focus at least until they release the promised updates.....lol. Zte updating a phone. I think we will have more luck with custom roms if they unlock the bootloader!
Click to expand...
Click to collapse
OK it is clear that EIS is software solution for the problem. I don't know too much about phone cameras but look at this article.
http://www.androidauthority.com/sony-announced-imx318-cmos-image-sensor-673495/
It is just about camera device alone and it says "the IMX318 supports 4K capture at 30fps and features electronic image stabilization to reduce camera shake and lens distortion", which means for me that software is included in the camera itself. Or?
Regarding axis I read the following meanwhile "The back of the Axon 7 is where you will find a 20 mega-pixel dual OIS rear camera".
http://www.gizchina.com/2016/08/08/zte-axon-7-first-impressions/
I suppose that dual is the number of axis because A7 has only one rear camera.
obladi64 said:
OK it is clear that EIS is software solution for the problem. I don't know too much about phone cameras but look at this article.
http://www.androidauthority.com/sony-announced-imx318-cmos-image-sensor-673495/
It is just about camera device alone and it says "the IMX318 supports 4K capture at 30fps and features electronic image stabilization to reduce camera shake and lens distortion", which means for me that software is included in the camera itself. Or?
Regarding axis I read the following meanwhile "The back of the Axon 7 is where you will find a 20 mega-pixel dual OIS rear camera".
http://www.gizchina.com/2016/08/08/zte-axon-7-first-impressions/
I suppose that dual is the number of axis because A7 has only one rear camera.
Click to expand...
Click to collapse
The phone has both OIS and EIS, that's why the "dual OIS" part should say "dual IS". Both OIS and EIS mechanisms are built into the sensor module, but while EIS is performed on the sensor, the OIS is performed by the SoC taking the reading from the 2-axis gyro (haven't seen any specs indicating more than that) and driving the (most likely VCM) motors in the module.
The auto-focus hunt in the video is too much, hope it can be locked, it made me nauseated
No info on what sensor it is now that is interesting. Knew the glass would be cheap but that's the way it goes on a cheap phone.
Overall looks quite good to me compared to the op3.
The pocket now review found that OIS is not so good and if you enable EIS, it gets worse. In the end they called it ambitious but flawed.
https://www.youtube.com/watch?v=Un0FJCYKTcM
After google announced that they have no plans to bring RAW support to the device I was curious to see what sort of quality the DNGs would be. Unfortunately I've found that the RAW files from different apps provide different results.
Apps used
Stock Camera App JPEG
Camera NX
Camera FV-5
Test 1: Straight out of camera RAW quality
All camera applications were left on full auto with touch focus on the far buildings.
Stock
https://imgur.com/a/ae575
Camera NX
https://imgur.com/a/UlR4s
Camera FV-5
https://imgur.com/a/ANvw5
As can be seen the RAW from Camera NX though very noisy is pretty standard looking. On the other hand Camera FV-5 is just awful with a stupid amount of noise.
This is interesting as inspecting the photos shows that the ISO for FV-5 was the lowest at 400 whilst NX and Stock used ISO 875.
Test 2: JPEG vs RAW quality
For this test I tried to use Camera FV-5 but it refused to take any pictures in the low light. Based on the previous test it's pretty obvious it would have fared worst anyways.
In this test I have tried to show the dynamic range of the files. Both were brought into Adobe Camera RAW, sliders for shadows and blacks cranked to max with the brightness and whites to lowest. I have also applied some sharpening and noise reduction to both.
The edits to both are identical
Stock Edit
https://imgur.com/a/9WPSy
NX Edit
https://imgur.com/a/UDEs9
The resulting images show that the RAW file is brighter and retains more detail. This can clearly be seen in the roof where JPEG artifacts are visible and the brickwork where detail is lost.
This can more clearly be seen when I brighten the JPEG so that it matches the brightness of the RAW
Stock Edit Brighter
https://imgur.com/a/N7YFz
Conclusions
I'd grown used to shooting RAW on my S7 Edge, luckily the new Pixels fully support Camera API 2. However it is interesting to see that the RAW readout is different per app. In regards to quality I will definitely be shooting the Camera NX in the future when I want a RAW file; however the JPEG quality is very impressive and lives up to it's hype.
Edit: 26/11/17 (From reddit post https://www.reddit.com/r/GooglePixel/comments/7fb9vu/technical_camera_test_raw_vs_jpeg/)
Test 3: LR vs Camera NX
Tried out LR in both 'Professional' and 'HDR' RAW modes. All photos have the same sharpening, noise reduction, white point applied. Blacks and shadows are maxed out with whites and highlights at minimum. LR HDR has exposure boosted to +2.65EV to match brightness.
NX Edit https://imgur.com/a/oUBhd
LR Professional Edit https://imgur.com/a/CsBa3
LR HDR Edit https://imgur.com/a/nuSNa
I was expecting LR RAWs to be significantly better. Unexpectedly the 'Professional' LR RAW looks similar to the FV-5 RAW, very blue with a whole bunch of noise.
The 'HDR' LR RAW looks much closer to the NX RAW, however there are some strange hot(white) pixels spread throughout.
Conclusions 2
I'll still be sticking with the NX RAWs for now, 'HDR' LR files are close but detail isn't any better and those white pixels are pretty noticeable.
Test 1 and 2 Full resolution and dng files: https://drive.google.com/file/d/1e2_sD7D1IiOg9Ety_8IsHAfhcKAVf9Eq/view?usp=sharing
Test 3 Full resolution and dng files: https://drive.google.com/open?id=17EIhsPAX5efHXPiz_cfkov3AKaDkREvg
Anyone got suggestions for more apps for me to try?
For my aesthetically pleasing photographs please visit my Instagram
Interesting post, thanks for sharing. Have you considered doing stock v nx v LR v manual cam & compare in lightroom side by side? I know with my 5X the hdr auto was visibly worse wrt detail than hdr on, and dng was another step up to that, basically incredibly detailed.
Does nx raw use hdr with the new 8.1 update enabling the visual core? Or will say manual camera use hdr+enhanced in it's raw outputs?
randomhkkid said:
Anyone got suggestions for more apps for me to try?
Click to expand...
Click to collapse
Interesting read thanks. Did you try open camera? I experimented a bit and found the dng offered more flexibility in fixing exposure and white balance but needed a lot of noise processing to be as good as the jpg. But have been shooting both just in case I wanted to post process anything. So far haven't.
It never occurred to me that raw differed by app. That seems just wrong.
Linwood.Ferguson said:
It never occurred to me that raw differed by app. That seems just wrong.
Click to expand...
Click to collapse
It does seem wrong. RAW data should be just that, all the data from the camera before anything like an app tweaks it out. So yeah, it makes zero sense.
Hi, good thread!
I have somehow given up on RAW on Android because the implementations are so clumsy and the results are pitiful.
Indeed, to me too, the idea of having different quality raw from different cameras is plain stupid! Though I might admit it could be true given how lame the 3rd party Android cameras are. Such a shame a huge ecosystem such as Android cannot produce a fully featured and functional camera.
Btw you could also try one of the modified GCam versions with RAW enabled. Here is a nice page where you could fetch one such. Go for the stable ones, in red.
https://www.celsoazevedo.com/files/android/google-camera/
Looking forward for your results!
You clearly don't understand what RAW is, or how ****ty phone cams are under the hood
The fact that you think that FV5 is the one giving bad results just shows that you don't understand what RAW files are supposed to be.
Phones, even our allegedly amazing DSLR killing wonders of today have ridiculously tiny sensors and take garbage photos. NO qualifications here, they take garbage photos.
Through magic, detail smearing software processing, we get some usable results.
Camera FV5 is outputting a real RAW file, complete with the stupid amount of noise captures by the tiny, crappy sensor in your phone.
Camera NX is evidently doing almost as much processing as the default engine and not outputting a real RAW file at all.
If you're wondering why Google downplays RAW support, it's because they know that for most people it will just reveal how crappy the camera really is and how much software trickery is going on.
Bingley said:
Interesting post, thanks for sharing. Have you considered doing stock v nx v LR v manual cam & compare in lightroom side by side? I know with my 5X the hdr auto was visibly worse wrt detail than hdr on, and dng was another step up to that, basically incredibly detailed.
Does nx raw use hdr with the new 8.1 update enabling the visual core? Or will say manual camera use hdr+enhanced in it's raw outputs?
Click to expand...
Click to collapse
I haven't tried since the 8.1 update. A little busy at the moment with my Master's unfortunately. I will try to do more comparisons in a few weeks after finals. For now I've updated the OP with some results from Lightroom's camera.
Linwood.Ferguson said:
Interesting read thanks. Did you try open camera? I experimented a bit and found the dng offered more flexibility in fixing exposure and white balance but needed a lot of noise processing to be as good as the jpg. But have been shooting both just in case I wanted to post process anything. So far haven't.
It never occurred to me that raw differed by app. That seems just wrong.
Click to expand...
Click to collapse
pixelsquish said:
It does seem wrong. RAW data should be just that, all the data from the camera before anything like an app tweaks it out. So yeah, it makes zero sense.
Click to expand...
Click to collapse
Don't shoot the messenger! The RAW files are definitely different, unsure why, likely due to API differences and when the RAW files is read in the image pipeline.
dehnhaide said:
Hi, good thread!
I have somehow given up on RAW on Android because the implementations are so clumsy and the results are pitiful.
Indeed, to me too, the idea of having different quality raw from different cameras is plain stupid! Though I might admit it could be true given how lame the 3rd party Android cameras are. Such a shame a huge ecosystem such as Android cannot produce a fully featured and functional camera.
Btw you could also try one of the modified GCam versions with RAW enabled. Here is a nice page where you could fetch one such. Go for the stable ones, in red.
https://www.celsoazevedo.com/files/android/google-camera/
Looking forward for your results!
Click to expand...
Click to collapse
CameraNX is the same as the modded Google camera with RAW support.
lordfarqaud said:
The fact that you think that FV5 is the one giving bad results just shows that you don't understand what RAW files are supposed to be.
Phones, even our allegedly amazing DSLR killing wonders of today have ridiculously tiny sensors and take garbage photos. NO qualifications here, they take garbage photos.
Through magic, detail smearing software processing, we get some usable results.
Camera FV5 is outputting a real RAW file, complete with the stupid amount of noise captures by the tiny, crappy sensor in your phone.
Camera NX is evidently doing almost as much processing as the default engine and not outputting a real RAW file at all.
If you're wondering why Google downplays RAW support, it's because they know that for most people it will just reveal how crappy the camera really is and how much software trickery is going on.
Click to expand...
Click to collapse
Ah this is where you're wrong. The actual RAW files you seem to be talking about are not debayered or processed in any way, the RAW files we traditionally talk about (DNG, NEF, CR2) are all already processed by the app or camera logic in some way to be as flat and neutral as possible whilst containing more info in shadows, highlights etc.
That's why we see difference in the output, the apps are processing the RAW output differently. The camera in the Pixel is still a good sensor, just that the software magic makes it the best in the industry. There is still merit to shooting in RAW compared to the jpeg output.
I am surprised that you guys don't know the difference.
Google's HDR+ captures multiple images (allegedly up to 8 or 10) in order to improve the image quality(noise, colors, dynamic range). But when you take a raw photo with a 3rd party app, you get worse image quality because usually the raw file relies on a single image.
Adobe's HDR raw automatically combines raw files (probably two or three) for a better dynamic range.
The NX app is a modified Google camera app. Therefore the app contains Google's HDR+ algorithm. Apparently Google's camera app has the option to use HDR+ for the raw files (so multiple raw files are combined for a much better image quality), but Google hasn't activated the feature yet. But apparently the developer of the NX app found a way to activate it.
I hope that Google activates this feature soon, so then we don't need a 3rd party apk anymore.
Ah this is where you're wrong. The actual RAW files you seem to be talking about are not debayered or processed in any way
Click to expand...
Click to collapse
A raw file contains, or should contain raw, "undebayered" sensor data. The processing software (lightroom, camera raw, etc, does the demosaicing.
the RAW files we traditionally talk about (DNG, NEF, CR2) are all already processed by the app or camera logic in some way to be as flat and neutral as possible whilst containing more info in shadows, highlights etc.
Click to expand...
Click to collapse
It's true that most camera makers probably mess with their raw data prior to some degree prior to saving the data, but it's not correct to say that the files are already processed by the app. Most apps will apply a default profile when you open the file, but nothing is processed until you, er, process it.
That's why we see difference in the output, the apps are processing the RAW output differently.
Click to expand...
Click to collapse
They certainly are, in that Camera NX is processing it to such a degree that it's can hardly be claimed to be a RAW file anymore, and FV5 is giving something that appears to have been barely touched, as it should.
The camera in the Pixel is still a good sensor, just that the software magic makes it the best in the industry.
Click to expand...
Click to collapse
It's a good sensor compared to other smartphone sensors, but it's still a piece of garbage in absolute terms, which is why it only looks good with that software "magic".
There is still merit to shooting in RAW compared to the jpeg output.
Click to expand...
Click to collapse
Agreed, nothing to do with the point I was making, which is that Camera NX is not giving better RAW output, it's not giving RAW output at all. And if you truly do want to see what the sensor is actually capturing, and work with that, only Camera FV5 in this comparison appears to be giving you that.
Should anyone be following this thread the new Pixel 3 camera apk is available and works on the Pixel 2 - it now has native raw support, and frankly it's great - jpegs still look ****e up close, whereas raw/dng files it produces are so clear it's amazing how Google manages to mangle the jpegs in cam!
Hello.
Could you post two identical photos to see the difference between a photo taken with gcam in 12 mpx and one with the magisk module of 48 mpx activated?
I ask you this because it is the only reason why I could unlock my mi9t firmware.
Thank you.
alessa said:
Hello.
Could you post two identical photos to see the difference between a photo taken with gcam in 12 mpx and one with the magisk module of 48 mpx activated?
I ask you this because it is the only reason why I could unlock my mi9t firmware.
Thank you.
Click to expand...
Click to collapse
In 48px mode, the camera wass lagger, auto focus was slower and hard to focus. The different was only when you zoom.
alessa said:
Hello.
Could you post two identical photos to see the difference between a photo taken with gcam in 12 mpx and one with the magisk module of 48 mpx activated?
I ask you this because it is the only reason why I could unlock my mi9t firmware.
Thank you.
Click to expand...
Click to collapse
Both are 12mp, but the 48mp is a fake mode to render the pics in a higher resolution. But it will lose definition
So you advised me not to unlock my mi9t for that because it is not worth it is it?
Thank you for your advice, but I would still like to give me my opinion so, I will still wait for a comparative photo ?
alessa said:
So you advised me not to unlock my mi9t for that because it is not worth it is it?
Thank you for your advice, but I would still like to give me my opinion so, I will still wait for a comparative photo
Click to expand...
Click to collapse
http://www.mediafire.com/view/vc25nlpx4lr1e4n/IMG_20200216_102919.jpg
http://www.mediafire.com/view/hy3vt6x8tm1hc5g/IMG_20200216_102741.jpg
chuate92 said:
http://www.mediafire.com/view/vc25nlpx4lr1e4n/IMG_20200216_102919.jpg
http://www.mediafire.com/view/hy3vt6x8tm1hc5g/IMG_20200216_102741.jpg
Click to expand...
Click to collapse
Thanks, and what is the 48mpx?
EDITk i saw ? one last little request, can you take a picture of a close object like a flower or a statue etc ...
I hope I don't ask too much ...
alessa said:
Thanks, and what is the 48mpx?
EDITk i saw one last little request, can you take a picture of a close object like a flower or a statue etc ...
I hope I don't ask too much ...
Click to expand...
Click to collapse
http://www.mediafire.com/view/aa9uv1tv2691rn1/IMG_20200326_080108.jpg#
http://www.mediafire.com/view/sh2cdlnffzlpprj/IMG_20200326_080052.jpg#
http://www.mediafire.com/view/v3v9jqbevm7lee1/IMG_20200325_235326.jpg
http://www.mediafire.com/view/tuip7nodnstw9i7/IMG_20200325_235254.jpg#
chuate92 said:
http://www.mediafire.com/view/aa9uv1tv2691rn1/IMG_20200326_080108.jpg#
http://www.mediafire.com/view/sh2cdlnffzlpprj/IMG_20200326_080052.jpg#
http://www.mediafire.com/view/v3v9jqbevm7lee1/IMG_20200325_235326.jpg
http://www.mediafire.com/view/tuip7nodnstw9i7/IMG_20200325_235254.jpg#
Click to expand...
Click to collapse
Thankyou so mutch?
The difference is really minimal, it is especially at the time of the zoom but otherwise the image as a whole is practically identical in quality..
In my tests, using raw files, there was a decent amount of difference. but again, the "need" for the extra detail is very rare. 12mp raw is good enough. I enable the 48mp only in special occasions.
will post a few tests tomorrow
malowz said:
In my tests, using raw files, there was a decent amount of difference. but again, the "need" for the extra detail is very rare. 12mp raw is good enough. I enable the 48mp only in special occasions.
will post a few tests tomorrow
Click to expand...
Click to collapse
What about night mode photos? Is there a difference?
12mp resized 2x bicubic and cropped 100% to make them the same size for comparison. ignore contrast/color/adjustments between raw and jpeg, as it is more about detail then raw processing settings.
raw taken with latest Urnyx05 GCam, jpeg taken with ANXcamera (basically the same as stock camera)
jpeg 12mp:
https://i.imgur.com/1nq8yHw.jpg
jpeg 48mp:
https://i.imgur.com/m3VmSE1.jpg
raw 12mp:
https://i.imgur.com/ASRvvYa.jpg
raw 48:
https://i.imgur.com/LpHl5ip.jpg
alessa said:
What about night mode photos? Is there a difference?
Click to expand...
Click to collapse
will test tonight.
malowz said:
12mp resized 2x bicubic and cropped 100% to make them the same size for comparison. ignore contrast/color/adjustments between raw and jpeg, as it is more about detail then raw processing settings.
raw taken with latest Urnyx05 GCam, jpeg taken with ANXcamera (basically the same as stock camera)
jpeg 12mp:
https://i.imgur.com/1nq8yHw.jpg
jpeg 48mp:
https://i.imgur.com/m3VmSE1.jpg
raw 12mp:
https://i.imgur.com/ASRvvYa.jpg
raw 48:
https://i.imgur.com/LpHl5ip.jpg
will test tonight.
Click to expand...
Click to collapse
kevineddu sei tu?
alessa said:
kevineddu sei tu?
Click to expand...
Click to collapse
????
i only speak portuguese and "half english".
malowz said:
????
i only speak portuguese and "half english".
Click to expand...
Click to collapse
Sorry i thought it was someone else ?
in my tests, night shot does not benefit from using raw nor 48mp raw, as the raw does not have the result of the night shot processing, so the jpeg result is wayyy better and cleaner than the raw.
you need a lot of cleaning and filtering to the raw to make it look good.
also, with the 48mp module enable you get artifacts on the image and preview if the ISO gets to high.
so, in summary, no, 48mp is not useful for low light.
if your scene is "stationary", and you have a tripod, a photo with long shutter time is miles better, as you can get a super clean image from a night scene. But gcam does not have manual options, so another app is necessary, like hedgecam2. also, the 48mp module allow doubling the shutter time (60s from 30s original) so you can take very slow and super clean night images, for stationary scenes and tripod use.
but i don't know if there is an app to allow 48mp raw and manual adjustments, to have a 48mp raw night image. hedgecam can do manual with 48mp jpeg + 12mp raw only, but if you enable the magisk 48mp module and shoot raw, it crashes hedgecam
hedgecam2 + gcam + ANXCamera + 48mp module, are the "almost complete" package to take the best you can from mi 9t