Is anyone aware of a mod that would enable us to save to raw format with full 48 megapixel resolution? That would be amazing.
It's not a "full" 48mp sensor anyway. The color resolution is 12mp only, so I doubt you will get much better images using 48mp Raw :good: Quote:
"The sensor is characterised by its 48MP resolution and ability for 4:1 pixel binning into 12MP. The actual sensor’s colour filter is a quad-bayer setup, meaning the real chromatic spatial resolution is 12MP anyway, and the 48MP mode is enabled via pre-processing on the sensor itself, really only achieving chromatic spatial resolution equivalent to about ~27MP. OnePlus here does things better than a lot of other vendors; the 48MP simply isn’t available outside of the Pro mode, and I suggest users to just avoid using it at all."
(From Anandtech review, it's very thorough, as ever)
Related
For example, "ColorOS Camera for CM11s", "Another ColorOS Camera Port", and "CameraNext Modded."
The developers for these camera ports and mods are explicit about what they do and don't support.
None of them currently support OxygenOS. This bears repeating--"None of them currently support OxygenOS."
It is counter-productive and messy for users of OxygenOS to keep posting in the developer's threads about how their camera ports fall short of the expectations of those who are trying to plug the cameras into rom's for which they were not made.
Please come here and help each other, or be quiet, and leave the dev's alone.
If and when there is support for a camera on OxygenOS, the news will travel like lightning.
I have so far run some superficial tests with "ColorOS Camera for CM11s", and here are the results..., so you can know what to expect should you install it on OxygenOS.
You may add your observations to this thread as you wish.
So here's a list of what did and didn't work in OxygenOS.
What worked:
Normal worked just fine--all I did was leave settings on auto and pressed the shutter.
Burst worked, however each burst photo is only about 1/3 size of Normal photo in megabytes--this might be by design.
GIF worked.
Picture Plus worked.
Beautify worked.
HDR worked.
Colorful Filter worked.
Double Exposure worked.
What didn't work:
HDPicture did NOT work--it took only Normal sized shots at 13mp.
Super Macro did NOT work--it snapped a photo that turned out to be some sort of thumbnail.
Colorful Night snapped a photo, but terribly out of focus--tried several times..
Slow Shutter did NOT work.
Professional worked, but NOT using the timed shutter. I didn't try all the settings out.
RAW showed me the jpg, but I could not find the dng in OxygenOS native file manager app (Files), nor see it in Android Quickpic or in Windows.
Been testing out CameraNext Modded.
HDR worked.
Normal worked.
Macro worked however became difficult to focus when very close to subject, as I've not yet learned the proper place on the screen to tap to offset the parallax.
Variable shutter did not work.
That's as far as I got
Also, in the Normal settings, the only resolution options were 13mp and 10mp--don't remember if that's intentional.
COS12S CameraNext On OxygenOS:
Normal works, focus-Macro works.
Panorama makes a very tiny file, about 500kb.
Slo-mo 1080 @60fps worked. Grainy, but worked.
It might have been the medium light which was fine for 1080, or maybe that's just what happens.
No Slow Shutter available in Scene modes.
ColorOS Camera for CM11s/COS12 on OxygenOS
Video: 4K and 4K DCI recorded at 1920 x 1090. Slo-mo at 1280 x 738, and HDR at 1920 x 1090.
Thank you.
Darn I used HD more all the time.... hope they update it..i doubt it though...
time
tony1208 said:
Darn I used HD more all the time.... hope they update it..i doubt it though...
Click to expand...
Click to collapse
Ya, me too. Give it time.
P.S.--you are welcome to post your experiences with the different cameras here and help fill in the blanks.
10mp (16:9) doesn't work
1) I normally prefer taking pictures in wide resolution. I guess oxygenOs has removed the support for wide resolution at higher mp.
The setting 10mp (16:9) in the camera setting for Colour OS app doesn't take pictures in 10mp, but in a very small resolution. Only the 2mp (16:9) and 0.9 mp (16:9) settings work.
2) Beautify doesn't work on my phone.
Seriously hope someone fixes this.
Thanks
Clear data.
shekhar2989 said:
1) I normally prefer taking pictures in wide resolution. I guess oxygenOs has removed the support for wide resolution at higher mp.
The setting 10mp (16:9) in the camera setting for Colour OS app doesn't take pictures in 10mp, but in a very small resolution. Only the 2mp (16:9) and 0.9 mp (16:9) settings work.
2) Beautify doesn't work on my phone.
Seriously hope someone fixes this.
Thanks
Click to expand...
Click to collapse
Go System->Apps->the ColorOS camera app (might be called "Camera") and clear data.
Likewise for the plugins.
Try Beautify again.
ChronoSnap
Just now tested ChronoSnap on OxygenOS. Indeed, as the developer states, it seems to be a very simple and intuitive timelapse camera.
On OxygenOS though, it snaps only thumbnails.
@Android-Andi
This is information about SultanXDA's ROM regarding the camera.
SultanXDA ROM thread:
http://forum.xda-developers.com/onep...-12-1-t3120259
From the other thread I've learned to NOT flash another camera HAL, that ColorOS Camera has mirrored preview with selfies, and that ColorOS Camera will not show the 1080 selfie option.
Mirrored preview ColorOS Camera:
"sultanxda--Not a real bug. This is an issue with the ColorOS camera, not my HAL. The ColorOS cam was designed to be used by the CM/ColorOS camera libraries, and it's not a part of the actual ROM (it's an outside closed-source app), so I will make absolutely no effort to try and fix it."
1080 front camera ColorOS Camera:
"CameraNext and all other camera apps have the option, but ColorOS doesn't. Have you tried scrolling up in the video size list?"
Also, someone reported a bug switching from camera to pano or sphere:
"macimeister--Photosphere and Panorama mode in google camera app does not work. It is expected to improve this?
sultanxda--Just tested it, and this bug only happens when switching directly from camcorder mode to photosphere. Switching from camera mode to photosphere is fine.
There seem to be other bugs with Google Camera as well. I'll look into fixing them."
Since sultanxda states that many of the ColorOS camera features are closed-source, I gotta figure that for the most part, ColorOS and Another ColorOS will not be fully implemented.
Otherwise, seems to be fine camera-wise.
As many of us know that Google pixel 2 camera uses the dual pixel sensor ability for fast Autofocus as well as to get depth of field. Again face and body recognition algorithms are used to get dslr like portrait not using the dual camera but the same single camera. Dual pixels help in separating the person in focus from background, resulting amazing portraits..
Can the same features be implemented in a camera app that can utilise dual pixel sensors of phones like s7, note 8, x4, g5 plus and others to achieve similar results?
A new app may be.. Or we are waiting to port the pixel 2's camera app?
P. S. Please don't limit to sd 820,830 processors like the Google camera mod for hdr+ app. :laugh:
Here's an extract from petapixel post for better understanding of the new and the best ever Google Pixel camera:
Each pixel on the sensor has a “left and right split,” something that gives the sensor greater capabilities for depth of field and autofocus. This means that the camera’s sensor has two images, from slightly different perspectives, of the world in front of it. Consequently, the Pixel 2 can create a depth map and allow for shallow depth of field effects in its “Portrait Mode.”
Then there’s HDR+, which uses an algorithm that allows the tiny sensor to “act like a really big one,” introducing greater dynamic range. It combines several photos together with different exposures like a standard HDR image, but HDR+ also looks to realign each frame to avoid ghosting.
YouTube video "youtu.be/PIbeiddq_CQ"
Hi everyone. I'd like to know if anybody could get a 48 mp dng file from this phone. It is strange that raw file is only 12 mp. The quality of the 48 mp jpeg image is poor and seems rather an interpolated from 12 mp. How is possible to get a raw file smaller (12mp) than the original (48mp) ? And many camera aps won't give the jpeg 48 mp option but only the 12 mp. Comparing an original jpeg 40 mp from p20 pro with the one that this phone offers, the difference is tremendous on details and structure. Thanks for reading.
non-pro --> fake
pro --> real
TheMrBinary said:
non-pro --> fake
pro --> real
Click to expand...
Click to collapse
For what reason then, it won't give a 48 mp dng file? And also you cannot have from 48mp jpeg the option 16:9 ? If it was the stock camera limitation, why then, all other camera apps behave the same way?
Speaking always for pro model.
Kodagf said:
Hi everyone. I'd like to know if anybody could get a 48 mp dng file from this phone. It is strange that raw file is only 12 mp. The quality of the 48 mp jpeg image is poor and seems rather an interpolated from 12 mp. How is possible to get a raw file smaller (12mp) than the original (48mp) ? And many camera aps won't give the jpeg 48 mp option but only the 12 mp. Comparing an original jpeg 40 mp from p20 pro with the one that this phone offers, the difference is tremendous on details and structure. Thanks for reading.
Click to expand...
Click to collapse
I did not quite understand what you were saying. The 48MP shots are "real" as Xiaomi claims. For non-stock camera apps, just make sure you have Camera2API option available and enabled to enable 48MP mode. For instance, I enabled the same in Open Camera, and I had the capability to shoot "48MP" in RAW dng format.
And I kinda sorta get what you are trying to say, but I do not know enough about the topic to comment.
Here is one shot from RN7Pro with Open Camera app with Camera2API enabled, saved in jpeg and raw. One is the standard jpeg with resolution 8000 x 6000 and 6MB in size, the other is the dng of the same shot with resolution 3984 x 2984 (11.9 MP) as reported by Photoshop with a file size of 22.9 MB:
JPG: https://drive.google.com/file/d/1mKD7i2idv1YBjSFsepTCFShyTJTlPm6t/view?usp=sharing
DNG: https://drive.google.com/file/d/1Y6Xrez8sjFBP3HWI1__HchVtZ7unBTRr/view?usp=sharing
If you plan to compare the RN7 Pro, which costs as much as an early mid-range device, against the Huawei P20 Pro, which is top tier flagship from last year, then you will definitely be disappointed. One phone costs a couple of times the other. So that comparison does not make sense to me.
For a moment I was happy to hear that you were able to shoot 48 mp in raw dng format with open camera, but then I saw the dng file you posted was only 12 mp (a little less perhaps). So, unfortunately, I still am suspicious about what xiaomi claims for the camera since it is not possible to get 48 mp dng file with any app. The size of such a file should be about 45 mb. The quality of images of not 7 pro is excellent but the details are of 12 mp level. I posted an image from mi note 2 (21mp camera) where you can see the difference in details. I wonder if I get such an image from an older phone what should I expect with a newer with the double size of mp in the sensor. I'm afraid we have to do with a xiaomi's trick ......
Ps. Now I see that system made my image much smaller. 243 kb instead of 12 mb (original). you v\cannot get conclusions this way.. sorry.
I had the idea to post a crop of the original image. Take a look.
Ok, I'll explain.
It's a Quad Bayer sensor, what typically results in lack of raw output availability in case of the full res. That's due to the fact that OEMs assume no app would be able to process non-standard array, else they would have to process it on their own, through utilizing stacking (superres?) or simple remosaic. The latter would result in artifacts or loss of quality.
Because of that, all available raw streams come from binning (pixel "merging").
About the quality tho, it's just a Xiaomi thing. All you can currently do is disable the edge mode and denoising in Open Camera. Then your results might get more detailed, possibly at the cost of color fringing. At least, that's the case with Mi 9.
But about RN7 non-Pro, uhh. It has S5KGM1, which doesn't even support any kind of 48 MP mode, so the 48 MP images from RN7, Oppo F11 Pro, Vivo V15 Pro end up being a placebo.
Sorry that I saw your answer after I started a new thread with the same subject. Thanks for all your info. Still I wonder, why we cannot get a 48mp DNG file with any app, like for example on p20 pro that has the same quad bayer technology. And how is possible to get a 12 mp rawfile, from a 48 mp sensor? With p20 pro we can choose between 40 mp dng or 10 mp jpeg with binning technology. Why this is impossible with RN7pro ?
Another question that I have is that: If all available raw streams come from binning, then the 48mp jpeg from where it comes?
Kodagf said:
Another question that I have is that: If all available raw streams come from binning, then the 48mp jpeg from where it comes?
Click to expand...
Click to collapse
Sensor mode itself is a raw stream (typically 10 bit), but drivers are constructed in a way that filters out any quad bayer raw access from third party apps. The 48 MP JPEGs come from processing applied on it by the camera stack.
For further data, you can look on Camera2Test and most importantly, "dumpsys media.camera" command. "sensormode" is the keyword you're looking for in case of the latter. Then you'll get a 8000x6000 mode listed with a third number, which means the framerate, probably around 24 fps.
And anyyyway, disable edge mode and denoising in Open Camera if you want to see something about IMX586 with bare eyes.
j1505243 said:
Sensor mode itself is a raw stream (typically 10 bit), but drivers are constructed in a way that filters out any quad bayer raw access from third party apps. The 48 MP JPEGs come from processing applied on it by the camera stack.
For further data, you can look on Camera2Test and most importantly, "dumpsys media.camera" command. "sensormode" is the keyword you're looking for in case of the latter. Then you'll get a 8000x6000 mode listed with a third number, which means the framerate, probably around 24 fps.
And any way, disable edge mode and denoising in Open Camera if you want to see something about IMX586 with bare eyes.[/QU
Thanks, I can see what you mean. It's a pity thow, that there is no a 48mp dng file which, in bright light might be very interesting , offering hight level of details.... I guess that with 1,75 f and binning, xiaomi's goal is a brighter image in the shortest shooting time. This kind of images are very good for internet media use, but in a big screen they are worse than images from older phones .
Click to expand...
Click to collapse
Kodagf said:
j1505243 said:
Sensor mode itself is a raw stream (typically 10 bit), but drivers are constructed in a way that filters out any quad bayer raw access from third party apps. The 48 MP JPEGs come from processing applied on it by the camera stack.
For further data, you can look on Camera2Test and most importantly, "dumpsys media.camera" command. "sensormode" is the keyword you're looking for in case of the latter. Then you'll get a 8000x6000 mode listed with a third number, which means the framerate, probably around 24 fps.
And any way, disable edge mode and denoising in Open Camera if you want to see something about IMX586 with bare eyes.[/QU
Thanks, I can see what you mean. It's a pity thow, that there is no a 48mp dng file which, in bright light might be very interesting , offering hight level of details.... I guess that with 1,75 f and binning, xiaomi's goal is a brighter image in the shortest shooting time. This kind of images are very good for internet media use, but in a big screen they are worse than images from older phones .
Click to expand...
Click to collapse
Well, as said before, try setting edge mode off with denoising off in Open Camera, with Camera2 mode enabled and 48 MP resolution selected. You'll notice a rather good difference, but be aware of the color artifacts. BTW, the best 48 MP outputs available yet are coming from Honor View 20. Maybe Google will outperform that on Pixel 4, but it's just a guess.
Click to expand...
Click to collapse
ok... so totally crazy idea. Hypothetically speaking, what if there is a way to attach a much larger camera sensor (eg. APS-C size with e-mount) onto a fast SD865 phone (or future) via usb-c? And then would it be possible to have camera apps read data from it via current APIs? obviously there are alot of steps i'm missing here, but the biggest weakness in phone cameras is the sensor and there is simply no physical way to put an APS-C sized one in. The lenses would be humongous.
That said, at SOME times, especially those who are more serious into photography, being able to attach your phone to a big sensor would give you superior gear than anything that exist right now. combining the existing computation techiques with a fast processor WITH a large sensor does not exist. it's one or the other, no one has tried to do both yet (there are some old ones like Samsung Galaxy NX and currently Zeiss, but it doesnt seem like they are going to take advantage of computational tech)
Benefits:
- superior HDR with AI (most DSLRs have multi-stacked HDR but they are not as advanced as Google's)
- potentially AI HDR in video footage (no DSLRs have this , done in post)
- Enhanced artificial bokeh on top of already good bokeh to simulate medium format look
- immediate access to mobile lightroom / sharing direct to sources
- all media creation/library in one source
- utilize superior EIS to have stable footage (again, no DSLR has any good EIS tech. more focus in IBIS and OIS which is beneficial only in photos). ever tried S20 or iphone 11 pro at night? it's a noise party. In this case it would be a clean 4k footage with gimbal like EIS
it's true alot of the above can be done in POST when shooting with large sensor cameras
thoughts?
Hi all, you might know this already but I just found out and it seems like absolutely great news for this phone. The latest Open Camera update allows you to record video using every camera on the phone. Even the monochrome one works. No need to have perfect lighting conditions in order for the camera to switch between main and telephoto. You now have a dedicated camera button which lets you select what lens to use. Did you get the chance to try it out? I didn't have any issues yet.
Link please
Here it is:
https://play.google.com/store/apps/details?id=net.sourceforge.opencamera
Is the recording quality improved?
I'm not sure. You do have to option to record with maximum 80Mbps but I I find it hard to tell if that is any different from the 30Mbps standard rate. Video looks crisp and clear, colors are very good, especially if you lock the white balance.
Quality seems not as good.. Also can not use Camera API 2, for high res to get extra control in manual mode.
I'm not sure why you can't use camera2 api. For me it works and I can select iso and exposure during filming. I have a CLT L29.
boradu said:
I'm not sure why you can't use camera2 api. For me it works and I can select iso and exposure during filming. I have a CLT L29.
Click to expand...
Click to collapse
whats your max resolution for recording video using Camera2 API?
For the 40mp lens and the telephoto lens, I have 3840x2160. The monochrome camera however has a resolution of 3264x1840 for video.
Sorry for necropost, but anyone tried open camera for B&W photos? Does it allow exposure bracketing? Raw or at least png for file saving? I would like to try p20 pro just for that monochrome lens...
You can save RAW with the B&W camera but for some reason the pictures appear purple.