Related
HKLM\Software\HTC\Camera\P2\MainCamSupportCapSize = dword:0x0A (10)
change to dword:0x3A (58) and you will have Large & CIF resolutions.
Dmitry
can u explain better how to do it because when i go in i cant change the dword value and its # is 10 for me
bwxd said:
can u explain better how to do it because when i go in i cant change the dword value and its # is 10 for me
Click to expand...
Click to collapse
Use any registry editor (like Resco Registry Editor or PHM Registry editor) and going to the HKLM\Software\HTC\Camera\P2\MainCamSupportCapSize . Default value is 10 decimal (0xA hex). Change value to 58 decimal (0x3A hex).
I modified the registry for these values and it does seem to increase the quality but not the image size of the pictures or video.
f00dl3 said:
I modified the registry for these values and it does seem to increase the quality but not the image size of the pictures or video.
Click to expand...
Click to collapse
After registry patch the L & CIF resolutions will be available in video camera mode. Try to click on resolution icon on top bar or select it in options.
the new resolutions are
L = 320x240
CIF = 352x288
which are much better than
S = 128x96
M = 176x144
thanks for the info
i made the edit and it enabled the two resolutions in the options, but when i actually tried to take a video with those settings (either large or CIF) it came out as the same low resolution it normally does, but the video quality is even worse (very choppy). is there a way to get around this?
hamstarz said:
i made the edit and it enabled the two resolutions in the options, but when i actually tried to take a video with those settings (either large or CIF) it came out as the same low resolution it normally does, but the video quality is even worse (very choppy). is there a way to get around this?
Click to expand...
Click to collapse
No problem. HKLM\Software\HTC\Camera\Recparam\MP4Large\Bitrate
default value 128000. I chaged it to 1024000 and now video quality is better.
hey, thanks for the reply...did what you said, and picture quality is better, but video is still very choppy and still much below the framerate id get while recording in medium. id be happy if I can just get it up to 15 frames per sec at this quality.
MJPEG @ 15FPS seems to be the sweet spot with Dmitri's tweak
Thanks for this tweak Dmitry! After spending few hours testing various settings, I found that using MJPEG @ 15 FPS got me the best results in both visual quality and framerate consistency (FPS for MJPEG can be set under Recparam\AVILarge although 15FPS is the default, if I recall right). Anything higher than 15-20 FPS with high motion videos will result in erratic captures.
Note also that you'll want a fat MicroSD card to store MJPEG videos as these can become large fairly quickly.
This is an amazing reg tweak, i knew it was a matter of time before this leaked out. This camera is more powerful than whats let on and i know it
Now if only we can get some frame rate tweaks in here that work
Well I actually got the frame rate to not be so choppy by just changing HKLM\Software\HTC\Camera\Recparam\MP4Large\FrameRate to 5 Hell you may even be able to go lower. Because that's all I kept doin an it just seemed to get better each time I lowered it.
Changing the framerate to 5FPS for Mpeg4 yields horrible playback results. It's not even worth taking videos with the setting at 5 because of the slow, jerky movements.
--James
xtreme929 said:
Well I actually got the frame rate to not be so choppy by just changing HKLM\Software\HTC\Camera\Recparam\MP4Large\FrameRate to 5 Hell you may even be able to go lower. Because that's all I kept doin an it just seemed to get better each time I lowered it.
Click to expand...
Click to collapse
5 frames per second? That is REALLY choppy, maybe you meant 15?
i've done some testing and it seems like mpg4 just uses too much processing power to do the compression and that motion jpeg (AVI) at 15fps yields pretty good results. will try and do some more testing and report back.
robbyroy;1548515 said:
i've done some testing and it seems like mpg4 just uses too much processing power to do the compression and that motion jpeg (AVI) at 15fps yields pretty good results. will try and do some more testing and report back.
Click to expand...
Click to collapse
my only problem with using motion jpg is that audio stream format doesnt work with tcpmp, so all my beautiful movie automaticly become silent films out side pocket media player
help
I messup. I changed the maincamsupportcaptsize and dont remeber the org setting. the 2nd problem is that i could not add change to dword:0x3A (58) it would only let me change from 8 to 58 but not the 0X3a?
Not sure if changing this messed up my MMS but I haven't changed any other feature. Right now after doing this hack, my MMS won't send out, giving me an error that says my image size of 16k or whatever is over the 0k limit?
Reseting to default
thanks for the info but I have tried that reg hack and it will stay at 58 until i launch the camera/camcorder function then i go back in and it is back at 10. don't know if i need to soft reset before i launch cam? any help would be a appreciated.
phatstud said:
Not sure if changing this messed up my MMS but I haven't changed any other feature. Right now after doing this hack, my MMS won't send out, giving me an error that says my image size of 16k or whatever is over the 0k limit?
Click to expand...
Click to collapse
Same thing happened to me. Just uninstall your mms and re install it. It will work.
Hey guys just got a slick HD2 from Tmobile, and I wanted to check out Coreplayer. I started playing a few WVGA videos with decent bitrate, and towards the first 10seconds video played fine than started to lag and drop frames, then when I skip to a different part, it plays smooth for another 10secs than lags. When I run benchmarks, the video scores 120%.
I am using these settings for optimal playback.
Tools:
>Settings:
>Video:
Video Output: DirectDraw
Video Quality: High
Smooth Zoom: On
Dither: Checked
--
>Direct Draw:
Uncheck Both “Overlay with colorkey” and “Use blitting instead of overlay”
Check “Use device stretching for blitting”
Overlay format: YUY2 (or RGB to enable Dither)
--
These settings give me best visual quality, tell me if there are better settings.
However, the above problem occurs, in many different configurations.
I believe the process priority is the concern here, I think Coreplayer auto ranks up the priority during benches but doesent seem to do so while playing, most likely to conserve battery life.
I was reading a long time ago about a program that increases process priority in Windows Mobile, and was hoping that it may do the trick. So can anyone lead me to the rite softwares???
---Edit: I tryed to change the priority but it is always set to highest, in benchmark mode and in normal playback. Does anyone know what could be the problem.
roteplex said:
These settings give me best visual quality, tell me if there are better settings.
Click to expand...
Click to collapse
I think those are pretty much optimal. (RGB overlays are definitely slower than YUY2).
Try putting the phone in "airplane mode" and then rebooting it; that sometimes helps. If it's doing something like checking for emails in the background it starts to judder badly.
if core player has a buffer size setting try setting it higher try setting it to 32864kb. or do what i do and use TCPMP for videos. it has that setting and it works great for all vids. oh and its free! search the forums for TCPMP if core player ends up not working for you.
I've found that CP benches don't mean Sh*t, I can get 175% in a bench but play it back normally and it still drops frames
DMAND said:
I've found that CP benches don't mean Sh*t, I can get 175% in a bench but play it back normally and it still drops frames
Click to expand...
Click to collapse
Yeah, the benchmark obviously displays average frame-rate; what you need to know is the time taken to render the single slowest, most complicated frame.
If I choose DirectDraw my device.exe locks up. I have had to stick to GDI. I only drop 1 frame every 300 to 500
sancmat said:
If I choose DirectDraw my device.exe locks up. I have had to stick to GDI. I only drop 1 frame every 300 to 500
Click to expand...
Click to collapse
That is probably because you are not using the other settings correctly: YUY2 overlays, etc.
sancmat said:
If I choose DirectDraw my device.exe locks up. I have had to stick to GDI. I only drop 1 frame every 300 to 500
Click to expand...
Click to collapse
Selecting DirectDraw alone will make CorePlayer crash. You need to make sure you set all the other settings in the 1st post too and then it runs much smoother than GDI.
Going to try to explain this... When I'm using the stock Camera app, the picture is normal. But when I switch to Camcorder, it seems to be automatically zoomed in quite a bit. And when I try to zoom out, it says that since I'm recording in HD, zoom functions are not available.
This is kind of annoying because now I have to step back probably 5 feet to fill the same frame of when I was taking photos.
Is this normal for everyone else too? Or do I have some weird glitch on my unrooted and pure stock ROM?
Yep, mine does it too (stock rom). It only does that in FullHD resolution. I guess the only use middle part of the sensor to read the data to achieve greater speeds, and thus it's gonna be a hardware limitation.
Who need HD anyway ? The lens hardly catch with it. I record 720x480 and I'm very pleased with teh quality.
Change the video recording resolution in the settings pane to 1280x720 and that should fix your problem.
hank00k said:
Change the video recording resolution in the settings pane to 1280x720 and that should fix your problem.
Click to expand...
Click to collapse
Yeah I noticed that.
But that doesn't make sense. In photo mode, same resolution as video mode but in video mode it's zoomed in. Like Dr. Sid said, it seems that it uses a smaller section of the image sensor to capture video. Which again doesn't make sense. Weird.
This is definetly a speed optimization - scaling down the whole resolution of camera sensor from 3264*2448 -> 1080p is much more expensive operation than just cropping the central pixels, i assume someone at samsung was VERY lazy to have done the camcorder mode in such a lame way, it's still ok for recording outside scenes but useless for in-room recording.
I find this quite annoying also. At first I was wondering if it is a ROM glitch or something, since some of the people here stated that even in stock ROM it is present also.
I hope there is some kind of patch to this, full HD recording is really awesome and I hate to see the 'zoomed' effect.
Yeah noticed the same thing just last night.. Seems to also affect the camera's ability to focus properly in video capture mode as well... Shame on them, I wish I had noticed this sooner.
Hello
I was wondering can we improve camera quality on our Redmi Pro, especialy video recording. I am very pleased with this device, except camera quality. This is not bad hardware or sensor, this is just bad software implementation and optimization. I hope that Xiaomi will improve something in future updates.
I have tried to change some settings in camera app. For best still picture quality you can set saturation and cotrast to high, and sharpness leave at medium. With this settings pictures will look more punchy and vibrant. When you put sharpnes also to high, picture look to much artificial with some artifacts.
For Video we do not have similar settings like sharpnes, saturation and contrast. It is shame that with Sony IMX258 we have such soft video recording.
I have tried to use some other camera apps, and no camera app can improve video recording quality. With Cinema FV5 you can change bittrate to 30Mbps but quality stays the same.
I noticed that in low light conditions video recording drops to 15FPS and a bitrate around 10-12Mbps with stock camera. This is awfull image quality. With google camera, recording video in low light is better, bittrate is 17Mbps and FPS is 30. Image is a little bit darker, but much much smoother than stock camera.
I have question now. What libs and settings google camera is using for video recording? It is for sure something different from stock camera.
I Have tried to edit omega.xml in system/etc/device_features. I have copied gemini.xml, edited vendor string from qcom to mediatek, set permisions like the original file. Then I renamed original to omega.xml.old and gemini.xml to omega.xml. Rebooted and camera app worked just fine. In video modes I got audio zoom feature, and in manual picture mode unlocked everything. But there is no 4K recording, regerdless that in xml file 4k was set to 'true'.
So where are the others settings stored?
I have read something about editing lib files, shared objects *.SO files. And this is very hard to edit or do somekind of reverse enginering. Maybe someone have knowlege to do this? Or we do not need to edit lib files at all?
I am ready to test everything on my phone, so if someone have idea how can we edit camera app, google camera app, or something else to enable 4k, to improve qulity of 1080p recording, or even enable 1080p 60FPS mode.
Also I have tried to edit build.prop and add line persist.camera.HAL3.enable=1 and this will do nothing. In system lib and lib64 folder I have found files with names HAL3a.V3. I dont know is this mean something.
I am just thinking that is a shame to have very capable helio x25 and a solid sony sensor and such a mediocre image quality.
Thanks everyone in advance, and I hope that we will find some good ideas for improving our Redmi Pro
You have unlocked manual camera mode including long exposure/shuttertine and manual focus? Have you tried these two features? For me just the buttons are unlocked, but no changes if you shoot a photo or used the manual zoom has no effect. Could you explain "edited vendor string from qcom to mediatek"
You are wright, I forgot to mention that those two functions do not work. I have decompiled stock camera app from system to see xml and smali files. I dont have enough knowlege to do some mods and recompile it. Maybe someone can help. So far, i have seen in those file that camera app recognize if your vendor is mtk or qcom and base on that unlock 4K video recording and other functions. We need help from someone to look at that app and try to modify it, to change some values etc.
Mr.Nice.ba said:
Hello
I was wondering can we improve camera quality on our Redmi Pro, especialy video recording. I am very pleased with this device, except camera quality. This is not bad hardware or sensor, this is just bad software implementation and optimization. I hope that Xiaomi will improve something in future updates.
I have tried to change some settings in camera app. For best still picture quality you can set saturation and cotrast to high, and sharpness leave at medium. With this settings pictures will look more punchy and vibrant. When you put sharpnes also to high, picture look to much artificial with some artifacts.
For Video we do not have similar settings like sharpnes, saturation and contrast. It is shame that with Sony IMX258 we have such soft video recording.
I have tried to use some other camera apps, and no camera app can improve video recording quality. With Cinema FV5 you can change bittrate to 30Mbps but quality stays the same.
I noticed that in low light conditions video recording drops to 15FPS and a bitrate around 10-12Mbps with stock camera. This is awfull image quality. With google camera, recording video in low light is better, bittrate is 17Mbps and FPS is 30. Image is a little bit darker, but much much smoother than stock camera.
I have question now. What libs and settings google camera is using for video recording? It is for sure something different from stock camera.
I Have tried to edit omega.xml in system/etc/device_features. I have copied gemini.xml, edited vendor string from qcom to mediatek, set permisions like the original file. Then I renamed original to omega.xml.old and gemini.xml to omega.xml. Rebooted and camera app worked just fine. In video modes I got audio zoom feature, and in manual picture mode unlocked everything. But there is no 4K recording, regerdless that in xml file 4k was set to 'true'.
So where are the others settings stored?
I have read something about editing lib files, shared objects *.SO files. And this is very hard to edit or do somekind of reverse enginering. Maybe someone have knowlege to do this? Or we do not need to edit lib files at all?
I am ready to test everything on my phone, so if someone have idea how can we edit camera app, google camera app, or something else to enable 4k, to improve qulity of 1080p recording, or even enable 1080p 60FPS mode.
Also I have tried to edit build.prop and add line persist.camera.HAL3.enable=1 and this will do nothing. In system lib and lib64 folder I have found files with names HAL3a.V3. I dont know is this mean something.
I am just thinking that is a shame to have very capable helio x25 and a solid sony sensor and such a mediocre image quality.
Thanks everyone in advance, and I hope that we will find some good ideas for improving our Redmi Pro
Click to expand...
Click to collapse
Hey I think you get de wrong command on build.pro, the right one in "persist.camera.HAL3.enabled=1"...
And about 4k video... I don't think it's gonna work cause the processor maybe can't handle this. And 1080 at 60fps maybe it's possible.
MathePro said:
Hey I think you get de wrong command on build.pro, the right one in "persist.camera.HAL3.enabled=1"...
And about 4k video... I don't think it's gonna work cause the processor maybe can't handle this. And 1080 at 60fps maybe it's possible.
Click to expand...
Click to collapse
1080 at 60 fps maybe work
So, any one knows what exactly on Android system handle all this?. It's on encoder? It's on camera driver? I don't think of just a "app" will change anything. It's has something like a encode line or a lib. Any modder? I had looking for a mod for that sensor but until now, the only thing what works is about Hal3 on build.prop.
Anyone know how to get 60 fps 1080?
Hello,
I recently purchased an AXON 7 and really enjoy using it. I was in the camera app and noticed that the slow motion quality is much worse than it should be. I went to the settings to change the quality, and the option to change the quality was greyed out and stuck at 720p. I've already tried wiping the cache and resetting app settings, and nothing has worked. If anyone could help me fix this issue it would be really appreciated!
There's nothing wrong with your phone. The Axon 7 only shoots slow motion 120 FPS and 240 FPS at 720p. In the normal shooting mode, you can set the video to 60 FPS at 1080p if you want a crisper image but with less room to slow down the footage. Otherwise, that's it.
z28camaroman said:
There's nothing wrong with your phone. The Axon 7 only shoots slow motion 120 FPS and 240 FPS at 720p. In the normal shooting mode, you can set the video to 60 FPS at 1080p if you want a crisper image but with less room to slow down the footage. Otherwise, that's it.
Click to expand...
Click to collapse
Thank you for the speedy reply! I would change the options but i can't since the drop down menu doesn't allow me to change it. Is there any other way to fix this issue?
To change the "slow motion" options, you press the fractions on the bottom left of the slow motion screen, i.e. 1/4 or 1/8. These determine how slow the 720p footage goes.
For 1080p 60 FPS, go to the regular video recording accessed by a swipe to the right, or by pressing video, on the main camera page and then press the gear cog on the top left. Then select 1080p 60FPS. You will have to slow it down yourself in a video editor but it is an overall better image.
Hope that helps.