Related
Since I have succesfully activated HAL3 on our device, I started getting amazing pictures with the help Google Camera. The noise reduction is off, the quality is crystal-clear, which means that we haveamazing sensors on both our cameras, the rear and front one.
But even with this feature turned on, the quality of the built-in cameras of Instagram, Skype, Google Duo , Whatsapp and Viber offer a very low quality of the image even when taking photos but most important - when making a video call. The quality is awfull, just like the stock camera with it's noise reduction on. Blury image and very low FPS while in a videocall. We have great camera modules on our phone, so how to find in the ROMs a way to make these apps use the best quality available of our cameras? Is it related to HAL1 or HAL3 or is there a code in the kernel that can be modified? Or what is the key to make it work better?
When opening the video camera of the stock camera app - the image is clear and the noise-reduction is off...so it is amazing, even the fps is high, no glicthes. As soon as I switch the camera back to the photo, I get a blury image and low fps in of the viewfinder.... exaclty the same is within any of the above meantioned apps. How to make a better camera quality when using them? I haven't found any solution anywhere on the XDA forum not even on the 4pda forum.
Am I the only one concerned about this fact?
The front camera of this device is OV5675 Sensore and read on their page, it says it can handle video recording of Full HD at 60FPS
Than why did the MIUI limit it's capabilities so low? To make it look like a cheap sensor and sell the phone as budget?
Anyone?
1: Does s10 supports log v2 ?
2: How about autofocus, is it working correctly ?
3: Is it posible to use all three lenses ?
4: Does it have droped frames in extreeme quality ?
Thank you.
My first testing is horrible, tried all qualities:
4k 60fps (not working fine) -> 58.62fps, 58,26fps (the same even quality low)
4k 30fps (fine)
1080p 240fps (not working fine)-> 231,88fps, 228,77fps, 230,51fps
1080p 120fps (not working fine)-> 118 fps
Edit: You can shoot video in HDR+ which results in a flat profile, that can be graded in Premiere very heavily. First it looks completely overexposed, as soon as I check HDR in the lumetri effect in Premiere and bring the kurves down all highlights start coming back. Don't know what log v2 is...
None of the formerly awesome video/editing apps work correctly on the S10+ so far. Very irritating
Then at least there is hope it can be fixed on the Software Side later on... I hope next update will fix things. Of which Video Editing Apps are you talking? My first Samsung.
And back to your question, found this: reddit.com/r/galaxys10/comments/b4x57d/samsung_s10_zhiyun_smooth_4_filmic_pro_log/
I got the S10 plus Exynos and I get an ugly frame drop with Filmic Pro. Don't know what to do anymore.
Tele lens is not working..
Wide angle front and back is working pretty good
So now that it is 2020, have things gotten any better with Filmic and the S10+ ? thx.
Currently app supports 4K 24p Wide, and ultra Wide on S10+ Exynos, and 1080p on front camera. Video recording from front is wider than on stock cam. I'm noticing though issues with the sound - it's not working on internal mic, only at external but not always.
Hello,
Sum up
I'm looking for a good way to record 4K 60 FPS with an external microphone, and possibly using any camera of the phone.
Why
I'm trying to find a convenient way to record good quality videos with speaking subjects (interviews and such) on the phone.
I aim the best possible quality for comfort and durability. I am therefore trying to film 4K 60 FPS with an external Lavalier microphone plugged in the jack port of the phone. (I'm also using a gimbal and stands depending on the context).
I also want to sometimes use the main camera, and sometimes the wide angle lens.
Phone
I'm using a stock ROM Xiaomi Mi 9T Pro (8GB RAM/256GB Storage, Global version).
Issues
As simple as it seems, I'm encountering a few issues/limitations.
Default video app :
- doesn't seem to take an external microphone
- has mediocre but OK audio compression quality
- has an 8 minutes limit when filming 4K 60 FPS (don't know about other formats).
(My 8 minutes 4K 60 FPS video is 2.2GB, so it doesn't seem to be a file size limit)
- and it's also the only one that seems to support video recording with any lens/camera on the phone...
I'm willing to sacrifice on audio quality if someone can think of a way to use an external mic, and get rid of that 8 minutes time limitation with the default camera app.
Issues with other apps
I've tried a lot of alternate video apps, but none allowed me to record videos using the wide angle lens, or they were bugged or wouldn't take the external mic or woulldn't do 60 FPS in 4K...
- OpenCamera : Works great for everything, most stable so far, OK with external mic, no time limit and all, but no wide angle
- 4K Camera Pro : No 4K 60 FPS (limited to 30 FPS), crashes a lot, no option for using wide angle camera, takes external mic
- Cinema FV-5 Lite : No option for more than 30 FPS, 4K is limited to the pro version, no option for wide angle camera
- HedgeCam2 : Unable to even select 4K anymore after testing the app, couldn't find an option to select another camera, should take external mic, not tested that much.
- Google Camera (from Pixel) : Supports wide angle for photo, but not video. Stopped testing there.
- DJI Mimo : This is the app from my gimbal, no 4K 60 FPS (no framerate option), and won't take external microphone... So it's OK for making footage, but not interviews.
Question
For now, my best option is to forget about the wide angle and to just use Open Camera which is not 100% satisfying...
So my question is this:
Does anyone see a better option? Maybe even a ROM or an addon that could force microphone selection? I'm willing to go to custom builds at this point.
Thank you
UltimateByte said:
Hello,
Sum up
I'm looking for a good way to record 4K 60 FPS with an external microphone, and possibly using any camera of the phone.
Why
I'm trying to find a convenient way to record good quality videos with speaking subjects (interviews and such) on the phone.
I aim the best possible quality for comfort and durability. I am therefore trying to film 4K 60 FPS with an external Lavalier microphone plugged in the jack port of the phone. (I'm also using a gimbal and stands depending on the context).
I also want to sometimes use the main camera, and sometimes the wide angle lens.
Phone
I'm using a stock ROM Xiaomi Mi 9T Pro (8GB RAM/256GB Storage, Global version).
Issues
As simple as it seems, I'm encountering a few issues/limitations.
Default video app :
- doesn't seem to take an external microphone
- has mediocre but OK audio compression quality
- has an 8 minutes limit when filming 4K 60 FPS (don't know about other formats).
(My 8 minutes 4K 60 FPS video is 2.2GB, so it doesn't seem to be a file size limit)
- and it's also the only one that seems to support video recording with any lens/camera on the phone...
I'm willing to sacrifice on audio quality if someone can think of a way to use an external mic, and get rid of that 8 minutes time limitation with the default camera app.
Issues with other apps
I've tried a lot of alternate video apps, but none allowed me to record videos using the wide angle lens, or they were bugged or wouldn't take the external mic or woulldn't do 60 FPS in 4K...
- OpenCamera : Works great for everything, most stable so far, OK with external mic, no time limit and all, but no wide angle
- 4K Camera Pro : No 4K 60 FPS (limited to 30 FPS), crashes a lot, no option for using wide angle camera, takes external mic
- Cinema FV-5 Lite : No option for more than 30 FPS, 4K is limited to the pro version, no option for wide angle camera
- HedgeCam2 : Unable to even select 4K anymore after testing the app, couldn't find an option to select another camera, should take external mic, not tested that much.
- Google Camera (from Pixel) : Supports wide angle for photo, but not video. Stopped testing there.
- DJI Mimo : This is the app from my gimbal, no 4K 60 FPS (no framerate option), and won't take external microphone... So it's OK for making footage, but not interviews.
Question
For now, my best option is to forget about the wide angle and to just use Open Camera which is not 100% satisfying...
So my question is this:
Does anyone see a better option? Maybe even a ROM or an addon that could force microphone selection? I'm willing to go to custom builds at this point.
Thank you
Click to expand...
Click to collapse
Try filmic pro, it's not free but has a huge amount of options when it comes to resolutions, compression/container method, camera and fps, there's actually too much for me to mention, the ui is a little cluttered but I think it's down to having so much stuff
sofir786 said:
Try filmic pro, it's not free but has a huge amount of options when it comes to resolutions, compression/container method, camera and fps, there's actually too much for me to mention, the ui is a little cluttered but I think it's down to having so much stuff
Click to expand...
Click to collapse
Just got the Filmic Pro app, really great even though it doesn't solve the camera switch issue. Thanks for sharing.
Sent a few suggestions to the devs, we'll see.
One boring thing is it gets back to the default (internal) mic after unplugging the external and does not go back to external when you plug it back. No big deal but might lead to errors. Also, it doesn't support the DJI Osmo Mobile 3 yet, but since the 1 and 2 are supported, it's likely a mater of time. That's awesome already that it supports some gimbals at all.
For the rest, it's pretty cool, I like the interface and ease of use, that's the most professional video app I've seen yet.
We'll see, I'm glad I've got this app in my library anyways.
I found out that 108 MP mode only works with ISO <=100 on the Redmi note 10 pro.
Attached are crops from 108MP with ISO 100, 108 and 125. It is clear that after SO 100 the quality drops significantly. I shot the photo in 12MP as well and upscaled the photo in the PC. The resulting picture corresponded to the 108 and 125 ISO.
It would be nice to shoot 108MP at least up to ISO 400 or 800.
Moreover it seems that sometimes the 108MP is fake even though the iso is below 100. I did not find the cause of that yet.
Finally, the 108MP photos often have a green cast. It would be nice if that could be fixed as well.
The ISO_100_cr photo has a lot higher quality than ISO_125_cr and s_1_400_cr photos.
The ISO_100_a and ISO_100_b are taken about 3 minutes appart using the same settings and the same lightning conditions. However one of them uses the fake 108MP. I have no explanation for that so far.
I reported the bug using the Xiaomi Services & feedback. So far I did not get a reply.
xseryd said:
I found out that 108 MP mode only works with ISO <=100 on the Redmi note 10 pro.
Attached are crops from 108MP with ISO 100, 108 and 125. It is clear that after SO 100 the quality drops significantly. I shot the photo in 12MP as well and upscaled the photo in the PC. The resulting picture corresponded to the 108 and 125 ISO.
It would be nice to shoot 108MP at least up to ISO 400 or 800.
Moreover it seems that sometimes the 108MP is fake even though the iso is below 100. I did not find the cause of that yet.
Finally, the 108MP photos often have a green cast. It would be nice if that could be fixed as well.
The ISO_100_cr photo has a lot higher quality than ISO_125_cr and s_1_400_cr photos.
The ISO_100_a and ISO_100_b are taken about 3 minutes appart using the same settings and the same lightning conditions. However one of them uses the fake 108MP. I have no explanation for that so far.
I reported the bug using the Xiaomi Services & feedback. So far I did not get a reply.
Click to expand...
Click to collapse
Use pro mode. Its there.
In all of the photos above I used the pro mode. Otherwise I would not be able to set ISO manually. However the issue is in both normal and pro mode.
The phone acts like using 108MP, but in some cases it indeed used 108MP, in other it just upscales the 12MP photo.
Try clearing system cache and cam data.
Try rolling cam back to factory load if it's been updated.
blackhawk said:
Try clearing system cache and cam data.
Try rolling cam back to factory load if it's been updated.
Click to expand...
Click to collapse
I do not think the cam itself got updated, just the system to 12.0.10 MIUI Global. I cleared all the caches and the issue persists. Using pro mode 108MP with fixed ISO 100 and 125 there is a huge drop in quality in the 125 ISO.
xseryd said:
I do not think the cam itself got updated, just the system to 12.0.10 MIUI Global. I cleared all the caches and the issue persists. Using pro mode 108MP with fixed ISO 100 and 125 there is a huge drop in quality in the 125 ISO.
Click to expand...
Click to collapse
What about using it in ISO 200?
The drop in image Q is very small or should be.
blackhawk said:
What about using it in ISO 200?
The drop in image Q is very small or should be.
Click to expand...
Click to collapse
The pictures look almost the same for ISO 50-100. Then there is a sharp drop in quality and than the pictures are almost the same for ISO 125-500. ISO 1000 is noticeably softer, but that is to be expected.
xseryd said:
The pictures look almost the same for ISO 50-100. Then there is a sharp drop in quality and than the pictures are almost the same for ISO 125-500. ISO 1000 is noticeably softer, but that is to be expected.
Click to expand...
Click to collapse
If it's native ISO is 100, don't drop below that unless the ambient light is too bright.
Use at it's native ISO # or higher whenever possible. Its native ISO is probably 100 but never assume...
blackhawk said:
If it's native ISO is 100, don't drop below that unless the ambient light is too bright.
Use at it's native ISO # or higher whenever possible. Its native ISO is probably 100 but never assume...
Click to expand...
Click to collapse
The automatic mode tries to use ISO 50 if there is enough light, so I guess that is the native ISO. However that does not solve the issue that for ISO > 100 the photo looks suspiciously similar to what I get when I shoot 12 MP and upscale the picture in the pc. And unfortunately even for <=100 it is not guaranteed to shoot the true 108 MP.
xseryd said:
The automatic mode tries to use ISO 50 if there is enough light, so I guess that is the native ISO. However that does not solve the issue that for ISO > 100 the photo looks suspiciously similar to what I get when I shoot 12 MP and upscale the picture in the pc. And unfortunately even for <=100 it is not guaranteed to shoot the true 108 MP.
Click to expand...
Click to collapse
You need to see what its native ISO is speced at to know.
Poor focus* and cam shake can be factors.
The 108 MP file size should be significantly larger than the 12 MP one.
*the wrong AF lock on point can trash images taken with a fast lense; the focal range is quit narrow at close range. Try some shots at 50 feet out.
All the photos mentioned above are at least 50 feet away and all have shutter time 1/300 or faster, so shake should not be an issue. The two last photos with the cherry tree even have ~1/1700s time and the issue is still visible.
Finally the picture size of the real 108MP files is 23-25MB, whereas the picture size of the faked ones is 14-18MB. Even there there seems to be something wrong.
xseryd said:
All the photos mentioned above are at least 50 feet away and all have shutter time 1/300 or faster, so shake should not be an issue. The two last photos with the cherry tree even have ~1/1700s time and the issue is still visible.
Finally the picture size of the real 108MP files is 23-25MB, whereas the picture size of the faked ones is 14-18MB. Even there there seems to be something wrong.
Click to expand...
Click to collapse
Size of the file varies by the content, sometimes drastically. It still could be an AF issue, try manual focus if you have that option.
Cam shake can happen at almost any shutter setting; brace the cam on something solid.
Because there is no weight to the phone compared to 2-7 pounds of a pro- cam means little inertia to over come and no good handholds... cam shake is more an issue.
You can get cam shake at 1/1000 @Sec with a pro cam if your technique is sloppy.
Review the cam settings carefully and double check them.
I don't know, you could be right. It seems like it be a poor business plan though. It may be an inadvertent flaw on that production run and/or the firmware for it.
blackhawk said:
Size of the file varies by the content, sometimes drastically. It still could be an AF issue, try manual focus if you have that option.
Cam shake can happen at almost any shutter setting; brace the cam on something solid.
Because there is no weight to the phone compared to 2-7 pounds of a pro- cam means little inertia to over come and no good handholds... cam shake is more an issue.
You can get cam shake at 1/1000 @Sec with a pro cam if your technique is sloppy.
Review the cam settings carefully and double check them.
I don't know, you could be right. It seems like it be a poor business plan though. It may be an inadvertent flaw on that production run and/or the firmware for it.
Click to expand...
Click to collapse
Just to be sure I did the test again using a tripod and a self timer. Still the same results. I could not use the manual focus mode, because the "infinity" seems to be only a few feet and my objects came out blurry.
The file difference was on the same scene, taken 10s apart. 24MB real 108MB, 14MB faked 108MB.
I have taken several photos in 108 in low light and the behavior of the Iso is correct.
It always maintains 108 and the Iso obtained go from 581 to 12800, I suppose it can go up a little more.
Logically, the higher the iso, the lower the quality and more with such small objectives.
I am very happy with the camera results and I come from a Pixel 2.
Well for one thing use solid objects that aren't able to be moved by the wind as subjects preferably with the light source in back of you rather than in back of the subject.
A wrought iron fence maybe.
24 mp is actually a lot. It's not just the pixel count but also the quality, grey depth, color accuracy that the individual pixel can capture.
blackhawk said:
Well for one thing use solid objects that aren't able to be moved by the wind as subjects preferably with the light source in back of you rather than in back of the subject.
A wrought iron fence maybe.
24 mp is actually a lot. It's not just the pixel count but also the quality, grey depth, color accuracy that the individual pixel can capture.
Click to expand...
Click to collapse
I selected branches because there the difference was the most obvious. There was no wind at all. I attach different part of the picture with a solid object.
jmfb55 said:
I have taken several photos in 108 in low light and the behavior of the Iso is correct.
It always maintains 108 and the Iso obtained go from 581 to 12800, I suppose it can go up a little more.
Logically, the higher the iso, the lower the quality and more with such small objectives.
I am very happy with the camera results and I come from a Pixel 2.
Click to expand...
Click to collapse
The camera reports all of the 108MP photos to be 108MP. However I believe that sometimes the picture was taken using 12MP and then just upscaled to 108MP using a software.
Good obsevation. I can't get my phone to make 20+mb pictures. I tried with your setting so: 108MP & iso 50 but no luck. Photos still come out between 14-17mb.
FakedAce said:
Good obsevation. I can't get my phone to make 20+mb pictures. I tried with your setting so: 108MP & iso 50 but no luck. Photos still come out between 14-17mb.
Click to expand...
Click to collapse
Sometimes I get the fake 108MP even with small ISO. I don't understand that. Or maybe your scene is not that complex and the file is smaller even though it is the real 108MP. Try using ISO 125 if you see a size and quality difference. You can also try shooting 12MP and upscaling the picture in PC to see if it is the same as what you shot in 108MP.
FakedAce said:
Good obsevation. I can't get my phone to make 20+mb pictures. I tried with your setting so: 108MP & iso 50 but no luck. Photos still come out between 14-17mb.
Click to expand...
Click to collapse
MP=megapixels
MB=megabytes
The correlation between file size and the number of megapixels is a not strictly a ratiometric one.
Without the manufacturer's white papers it's hard to know exactly how they are processing the image. Companies like Canon and Denon usually exceed their specifications, and often share detailed information beyond just the specs.
♤Does the cam allow you to shoot in RAW mode?
Try that if so. That should give a more revealing look at what's going on. RAW's have the least post processing and contain much more of the image data.
Hi,
I wanted to know if this is normal on Xiaomi mi 11 Ultra, but
when I shoot in 4k 60 fps in HDR10+ (10 bit colors), I'm getting weird artifacts in the video. Look at: StockCamera10Bit.jpg
It's such an unusable mess. I'm shooting at PRO. It doesn't matter what ISO, shutter speed and white balance is selected. It's always this. Subject has to be moving.
If I select 8bit, it's ok, just normal motion blur.
Is it normal on this phone? Can anybody confirm it?
I have the same problem in McPro24FPS in anything over 30 FPS even in 8 bits, so that's troubling me a bit.
I have the phone for a few weeks now and it's just amazing how the video footage degrades, when you do not want to film in AUTO
And even, if you satisfy with AUTO and only lock exposure and focus, it's also crap, when you move the camera or something is moving in front of it
I can see, that the only thing that manufacturers are interested in is AUTO mode which gives you nice HDR, but is always changing exposure, so it's interesting only for YouTube reviewers and DXOMark I guess. But for semi-serious video shooter I'm still amazed how they market 8k video and I cannot get even decent 4k 60 fps for slow mo (not even usable Full HD in 60 FPS).
I would satisfy with 8 bit, but it's unusable in stock app, because it's changing exposure even if it's locked and other app give me these artifacts anyway...
wait... did they convert 8-bit to 10-bit using bad dithering?
GuyWithRootedPhone said:
wait... did they convert 8-bit to 10-bit using bad dithering?
Click to expand...
Click to collapse
Alexander from McPro24FPS said, that it is a bug in HDR merging. It should have phones with HDR on by default.
It is some setting, that can be be turned off programmatically, but it's the matter of finding it.