Posted by Randolph
Changing Cam 49 to Cam 36 improves quality - the modules are different - especially on distance and details. But I have noticed that there also must have been made some changes to fimware or phones mainboard because also after changing the cam module back to CID36 I could not get back the quality of my old CID36 phone....
Posted by Raiderski
6.7 will be available tomorrow or day after tomorrow. sorry but i have very strange personal problems
Posted by Kriomag
hello world!
my virtual drive at 4shared.com: http://kriomag.4shared.com - i will place my drivers there (also beta versions).
I've made beta version of 21 series: 21.93 - simple driver based on 21.9/21.91 - cid36 for now (but it may work on cid49).
Some changes:
- jpeg from Raiderski 6.6.1 (its stable as far i tested it so i've used it
ofc jeśli nie masz nic przeciwko Raiderski? ).
- 3VR modes are back
- WB on EV +
- Saturation on EV - (if you want use WB with saturation you have to change WB from cameras menu and then saturation with EV -).
- sharper pictures in day mode
- removed zoom x2, now its default x4 (if macro is off)
- in version 20071212 i added new feature: now you can set focus (macro on) and then turn macro off and set zoom - the focus will stay as you've set it with macro on
[ This Message was edited by: Kriomag on 2007-12-12 18:20 ]
Posted by SPU
I want to say two things =)
1. Comparison operation ($cl) uses (compares) only the first byte of the register.
2. Anybody uses "back light" function in his driver?
I mean following (manual ISO 100):
Normal AE
Spot AE
"Back light" AE
It really can help when you don't want to set up exposure manually or in non supermode drivers.
Posted by DarKMaGiCiaN
@Raidersky,SPU and Kriomag ,lpachuong
nice to see you again here
^_^
Posted by Kriomag
On 2007-12-12 18:57:08, SPU wrote:
Anybody uses "back light" function in his driver?
Can You tell me more about this function? thx
Posted by Raiderski
SPU
1. you mean $cN (N = reg num) right? what is the full size? 2 bytes right? funny but i never think about this
2. nope, is this value for command reg 8 (this one for spot on/off) or something different?
Posted by SPU
Kriomag
Indeed =) It's not a secret, i discovered it last summer, but i think i heard about it before that.
Command: 07
Parameter: == 00 - disable, != 00 - enable (i does not check any dependency on this value yet)
It works like a "back light" function in the old VHS camcorders, just stops to properly exposure very light objects, so darker objects does not turn black (like a finger on the last shot).
I'm not sure, but it seems like a hard limit on the shutter speed, so shutter speed can't be set by AE higher then some fixed value. I need to check this out =) If so, this function will be usable only indoor, because it will give total overexposure on the bright sun... if there is no settings for shutter speed limit.
Raiderski
1. Yes $cN. Actually all registers 4 bytes long, but even 2 bytes are used very rarely (in some math operations).
2. See above. Command reg 7. And this effect works together with AE modes (independent).
[ This Message was edited by: SPU on 2007-12-13 10:51 ]
Posted by krzychu
pikszel, Randolph
thanks for help!
i'll change it
Posted by Raiderski
riddle:
as we know command reg57 is HUE control. this reg is a bit strange, look:
of course we can reach range -127 - +127 without any problems but if command registers are signed 8bit then we are unable to go over 8bit limit. in this case ~70% of HUE table is unavailable for us
pity, don't you think?
the question is: how they (SE) resolved this? one more command reg to extend value? or maybe HUE control is corrupted? what do you think?
[ This Message was edited by: Raiderski on 2007-12-13 11:30 ]
Posted by number1
On 2007-12-13 12:29:22, Raiderski wrote:
riddle:
as we know command reg57 is HUE control. this reg is a bit strange, look:
of course we can reach range -127 - +127 without any problems but if command registers are signed 8bit then we are unable to go over 8bit limit. in this case ~70% of HUE table is unavailable for us
pity, don't you think?
the question is: how they (SE) resolved this? one more command reg to extend value? or maybe HUE control is corrupted? what do you think?
[ This Message was edited by: Raiderski on 2007-12-13 11:30 ]
is HUE #COM_EVENT(57,00)????, recommend me a value and i'll try it on the k800i
Posted by 679
Hi to wise camdriver modders!
I've found command $t0020 in camdriver.
There is no this command in I2C command list. What does this command mean?
It is just a curiosity...
Posted by Raiderski
number1
maybe, i don't know how K800 is working. you don't have big choice in values, they are the same as in 2MP phones
679
exactly what this mean nobody knows but this looks like: "everything is ready, take snapshot and reprocess"
Posted by number1
i tried #COM_EVENT(57,09) i didn't notice any difference what is colour hue range of colours or something init.
Posted by pram_zx
YES !!!
ALL CAM MODDER HAS COMEBACK !
YIPPIEEE.....!
Posted by pram_zx
@Kriomag
Is there any manual for your latest 21.93 beta 1213?
Posted by Kriomag
On 2007-12-14 04:12:00, pram_zx wrote:
@Kriomag
Is there any manual for your latest 21.93 beta 1213?
Its pretty the same as for 21.91:
--= Thx to Cheng Rong, Andeo & Raiderski =--
Kriomag v21.93 BETA
- Driver File Size 17kB
- Based on 7.7 Final
- Very sharp pictures in Day Mode
- Zoom with Manual focus! (Turn Macro ON and set focus, now turn Macro OFF and set Zoom)
- Light CC (in FINE Mode)
- EV- for VIVID or EV+ for quick WB change (Turn Macro OFF for normal EV change)
- 3 Video Recording Modes (Normal Mode= max 15fps, Night Mode= max 10fps, Night Mode + Macro= max 5fps)
- 2 Photo Modes (Picture Quality NORMAL: Default 7.7 Final, Picture Quality FINE: 7.7 Final + Automatic EM/ENM/LedEM/LedENM)
- Stable JPEG 89% (Normal & Fine Picture Quality)
- Manual Focus with Zoom Preview (Macro ON: 1.0 Autofocus, Manual Focus Range 1.1-4.0 with Zoom preview, 1.1 = Infinity, 4.0 = Macro)
- 3 Zoom Modes (Smooth Linear x16 for NormalMode VR, Linear x6 for NightMode VR, Linear x4 for Photo)
- AE Lock
- SPOT for Manual Focus (when Zoom Preview is enabled)
http://kriomag.4shared.com
Instructions:
Manual Focus:
Turn Macro ON.
When in range 1.1-4.0 (+/-) click half-shutter for zoom preview (you can ON/OFF zoom preview by clicking half-shutter),
now (when zoom is on) you can adjust focus very precisely (+/-),
when picture is most sharp you can:
- press shutter to take picture with SPOT (very useful with macro shooting)
or
- click half-shutter again (the zoom will go off and SPOT will be disabled)
and now press shutter to take picture. enjoy!
2 Photo Modes:
Picture Quality NORMAL:
- Normal Mode / Night Mode = Default 7.7Final
- Normal Mode / Night Mode + Macro = 7.7Final with Manual Focus
Picture Quality FINE:
- Normal Mode / Night Mode = Enhanced Mode / Enhanced Night Mode
- Normal Mode / Night Mode + Macro = Enhanced Mode / Enchanced Night Mode with Manual Focus
[ This Message was edited by: Kriomag on 2007-12-14 10:04 ]
Posted by pram_zx
Thanx Kriomag...
Posted by Suda
Hi Kriomag, Nice to see you back.
Can you plz upload your driver somewhere else? Like MySpace which is mostly accesible from anywhere.
Thanks.
Posted by Raiderski
number1
values are on image. to slide across whole HUE table we need something like range from -400 to +400. value 9 in this case is nothing
Posted by number1
On 2007-12-14 14:38:56, Raiderski wrote:
number1
values are on image. to slide across whole HUE table we need something like range from -400 to +400. value 9 in this case is nothing
sorry if i'm being dum, but i don't understand what your saying are you saying i should use #COM_EVENT(57,7F) which is 127
[ This Message was edited by: number1 on 2007-12-14 13:45 ]
Posted by lpachuong
Hello everyone.
Nice to see everyone is back. I hope we will get the best results for our "little camera". I have had some problems with my computers so it took me a while to remember how to mod
Today, I have just completed a new driver: A4A-11.00. I hope A4A's fan will be happy with it.
http://www.freewebs.com/ict2006_2007/camdriver0%2011.0.dat
Here are some changes:
- Pictures functions:
--- Improved exposure measuring method (if it too bright please tell me)
--- Compression @ 95%. If the size is over the limit, the camera will save the picture at lvl 85% (If it crashes, please report me as I don't know the Error value on w800i/w810i and k750i cid36)
--- FPS viewfinder is lowered than the previous version for better Colour Correction and Exposure Correction: there are 4 different values for FPS for 4 mode: Fine/Normal/Night mode on/Night mode off
_________
- Videos functions:
--- I hope that the videos will be more smoothly recorded (As I can see the result from my phone)
_________
At the top of the code, you can change/edit the value of the contrast/sharpness/brightness for the best result on ur phone
I'm looking forward to hearing your comments.
Have a nice weekend.
_________________
To be or not to be !!!
Please save our world. Save our world to save our lives and our generation.
There is no place as good as your house with your family. Home sweet home.
[ This Message was edited by: lpachuong on 2007-12-14 13:52 ]
[ This Message was edited by: lpachuong on 2007-12-15 10:54 ]
Posted by Sombra
New shots with Strong's SuperFunction 5.6 camdriver:
Moto
Green life
+ Green life
Shots taked with phone K750i CID49 (R1BC002)
Sorry for my poor english.
Posted by wickedsick
On 2007-12-14 14:50:23, lpachuong wrote:
Hello everyone.
Nice to see everyone is back. I hope we will get the best results for our "little camera". I have had some problems with my computers so it took me a while to remember how to mod
Today, I have just completed a new driver: A4A-11.00. I hope A4A's fan will be happy with it.
http://www.freewebs.com/ict2006_2007/camdriver0%2011.00.dat
Here are some changes:
- Pictures functions:
--- Improved exposure measuring method (if it too bright please tell me)
--- Compression @ 95%. If the size is over the limit, the camera will save the picture at lvl 85% (If it crashes, please report me as I don't know the Error value on w800i/w810i and k750i cid36)
--- FPS viewfinder is lowered than the previous version for better Colour Correction and Exposure Correction: there are 4 different values for FPS for 4 mode: Fine/Normal/Night mode on/Night mode off
_________
- Videos functions:
--- I hope that the videos will be more smoothly recorded (As I can see the result from my phone)
_________
At the top of the code, you can change/edit the value of the contrast/sharpness/brightness for the best result on ur phone
I'm looking forward to hearing your comments.
Have a nice weekend.
_________________
To be or not to be !!!
Please save our world. Save our world to save our lives and our generation.
There is no place as good as your house with your family. Home sweet home.
[ This Message was edited by: lpachuong on 2007-12-14 13:52 ]
Thank you for your new driver. WIth your new driver, I just tested it in the evening. The pictures indoor are fantastic. They are very good. I will test it tomorow. Good night.
Posted by nocky
hi Kriomag,
does your v21.93 BETA cam driver sounds great does it work for w810?
Posted by Kriomag
On 2007-12-15 00:03:14, nocky wrote:
hi Kriomag,
does your v21.93 BETA cam driver work for w810?
You tell me, i dont have W810i to check this
I think it works fine.
Posted by rawilson91
@Kriomag I tested your driver on w810i - it's ok
Posted by SPU
lpachuong
"Compression @ 95%. If the size is over the limit, the camera will save the picture at lvl 85% (If it crashes, please report me as I don't know the Error value on w800i/w810i and k750i cid36)"
Actually quality will fall to 80%, not 85%, because
#SET_JPEG_ERROR(0F,d8)
and 95-15=80 =)
Posted by Raiderski
what will happen if you have phone + beer + girlfriend in one place in the same time? my phone in on "compulsory rest" for some days...
small initiative...
Chengrong created "periodic table" with descriptions of some registers but today we know a bit more registers - it's time to update table!
a bit updated table is here:
http://downloads.wow-info.net[....]a/registers/periodic_table.jpg
do you know something more what should be placed on table? isn't this top secret? post message on forum or send me PM - i will place your information on image from above link. if you know better solution, let's discuss about this
Posted by lpachuong
@wickedsick: thank you for your comments. That driver is still a test version of A4A_v11.
@SPU:
Poor my maths I uploaded a wrong compression. But, thank you for pointing it out.
@Raiderski: thank you for your time and work.
=> I always appreciate your contribution.
@All modders: Do you know what method can we use to reduce noise with algorithm? If you have time, please have a look at w200i's driver as I dont fully understand the pixel_noise_reduction and row_noise_reduction functions. The problem is: how can we find out those registries'value. Thank you.
Posted by ukaszek
On 2007-12-15 00:45:10, Kriomag wrote:
On 2007-12-15 00:03:14, nocky wrote:
hi Kriomag,
does your v21.93 BETA cam driver work for w810?
You tell me, i dont have W810i to check this
I think it works fine.
Hello everybody !!
Have u photo from nev Kriomag driver v21.93 BETA ?
What photo is better v21.93 BETA or 21.91 ??
krio 21,91
[ This Message was edited by: ukaszek on 2007-12-15 17:21 ]
Posted by ukaszek
Posted by Kriomag
On 2007-12-15 18:17:46, ukaszek wrote:
What photo is better v21.93 BETA or 21.91 ??
Quality should by similar, only quality change are different jpeg settings (only size of picuter may be different) and saturation is disabled by default (in21.91 was set to 02), in 21.93 beta you can change saturation as you need
[ This Message was edited by: Kriomag on 2007-12-15 17:31 ]
Posted by Kriomag
On 2007-12-15 14:09:26, SPU wrote:
Actually quality will fall to 80%, not 85%, because
#SET_JPEG_ERROR(0F,d8)
and 95-15=80 =)
can you explain it to me
0F = 15 ok
but d8 ? is not 95, i dont understand it at all
Posted by number1
5a=90
5b=91
5c=92
5d=93
5e=94
5f=95
it's hex values, use the windows caculator to convert decimal to hex
Posted by Kriomag
On 2007-12-15 19:53:07, number1 wrote:
5a=90
5b=91
5c=92
5d=93
5e=94
5f=95
it's hex values, use the windows caculator to convert decimal to hex
i know that, im camdriver modder ;P
what i ment is d8 is not 95 - so where he get this 95? compression level defined in jpeg quality? then what is d8 for?
Posted by SPU
Kriomag
I don't know =)))))
Seriously... first number seems like a step value for quality downgrade. In lpachuong's conditions: init quality 95%, and 0f d8 values (with my own size limits) i always got 80% quality, but... it's not true when starting quality is 90%.
So... may be this is coincidence, and this registers are not working ones, but may be we really need to analyze this registers... very complicated task.
lpachuong
Where did you find this values, and why you call them Error (why they are called Error in "periodic table"?)?
Raiderski
Btw, "periodic table" was created for k750/w800/w810 and k790, so some items are useless for k750/w800/w810.
I know some missed commands/registers, but i need some time to make a list of them =)
At a first glance... (additions and corrections)
Registers:
03 - 06 - actually... all of them are Event registers
0B - 0C - JPEG time-out (not the retry time)
20 - 21 - need to rename... may me WB Tint and WB Temp
24 - ??? it works in our cammodules?
29 - WB mode (for Exif)
2A - Distance range (for Exif)
2B - Xenon state (for Exif)
36 - module version
3D,3E,40,43,44 - ??? for k790?
Commands:
1 - may be "AE lock" is better?
2 - ??? k790?
6 - may be "Exposure bias" is better?
7 - "backlight"
13 - Set WB correction
31 - AF start (start AF process in all accessible for AF modes)
34 - VF frameskip
72 - refresh Exif???
[ This Message was edited by: SPU on 2007-12-15 22:08 ]
Posted by lpachuong
@SPU:
Here is the code:
SET_JPEG_ERROR=05 02 00 16 !0 $f 05 02 00 17 !1 $f;
If we have look carefully at the code, there are two parts. The main values are 16 and 17 which follow the values in Max, Min and Average. I found these values by incident when I tried to test the Average values (11,12). It took me a while to fully understand these
Therefore, I thought beside Max, Min, Average, there would be a safe value and I named it SET_JPEG_ERROR.
#SET_JPEG_ERROR(0F,D8)
As you said, 0F=15 and 05 02 00 17 0F $f will be compared with 5F => 95-15=80. On my phone, I use 06 => 95-6=89% If you try this value, you will see the number of large-size pictures will be higher than that with the previous value.
Meanswhile, D8 is a value which define the size of the picture. If the camera can't save the picture, it will reduce the compression and recaculate the file size which much be less than 216kb. I tried with different values and it seems: (95%, 600kb) - (6%,216kb)= Safe value. (So far, my biggest picture is 606kb and smallest picture is 403kb after taking more than 100 pictures)
If u change D8, you will see the different in the size. However, I am not sure about this fomula so I wonder D8 is suitable or not on my last post.
I posted this code a long time ago but I havent heard any comment about it. I am glad to have you here. It is really nice to see everyone back.
Hope you understand what I meant (Sorry for my bad English)
_________________
To be or not to be !!!
Please save our world. Save our world to save our lives and our generation.
There is no place as good as your house with your family. Home sweet home.
[ This Message was edited by: lpachuong on 2007-12-15 23:30 ]
Posted by brazzuka's
Sorry for the matter reviewed here that has nothing do with what you are talking about guys but the processor chip can be a major inhibitor of hardware limiter and the camera driver? For raiderski or chengrog i donīt know or for anyone who knows if these arguments are related?
Even with a relatively good hardware processor seems that restricts the activities and functions of the system, I ask that because some processors cam Some models are similar and the same processors same driver each camera has its identity by its hardware.
Tnks
Posted by mattsw810i
Kriomag's latest driver wont do manual focus on my w810.. Any one else having this trouble?
Posted by Kriomag
On 2007-12-16 08:12:47, mattsw810i wrote:
Kriomag's latest driver wont do manual focus on my w810.. Any one else having this trouble?
All beta versions or just last one?
Posted by SPU
lpachuong
Thank you for an explanation =)
But register 17... if it is some size limit, why it only one? All size parameters has 2 bytes. If 17 is a deviation value (may be only in one direction), it is not so strange.
I'll try to figure out some formula after tests on my W800i.
Btw, if you are interested in... try to write something into the registers 1c,1d,1e and 1f =) All of them seems to be connected with JPEG but... at quick testing a half year ago i got only halts and crashes.
Posted by lpachuong
SPU
I know it is a strange value for registry 17 but it is JPEG Error HH and this may be posible.
About the other registry, 1b is about Qvalue and to be honest, I dont know what 1c-1f are. I aslo tested and had these result: the viewfinder kept focusing when I pressed the shutter and the pictures coulnd't be saved. However, I am interested in what exactly registries 3* are, as I think they may relate to noise reduction. However, I haven't got any progress with it. If you have time, please suggest me some ways to reduce noise. Thank you.
_________________
To be or not to be !!!
Please save our world. Save our world to save our lives and our generation.
There is no place as good as your house with your family. Home sweet home.
[ This Message was edited by: lpachuong on 2007-12-16 10:05 ]
[ This Message was edited by: lpachuong on 2007-12-16 10:08 ]
Posted by lpachuong
By the way, Good morning everyone and have a nice day.
Posted by SPU
lpachuong
I have tested your compression settings (quality and sizes) on my W800i with 06 for reg 16...
got one crash and the next quality values: 94, 92, 67, 82 and 88.
At a first glance... it seems like Step value is not working...
PS: The best way to get a crash - to get a macro shot of LCD display with a contrast text (like a driver source code).
My "adaptive" compression algorithm passes this test easily, but this algorithm is very sensitive to hand shaking... because of built in algorithm in cammodule (it does not have a memory buffer) =( It takes a shot, estimates target quality value, and takes ANOTHER shot that finally will be compressed and saved =( easy to understand that shots may be slightly different (as it mentioned by developers), but may be very different (if the first picture was a little bit blurry and another one was sharp). And this is why my algorithm takes more time to get a shot and is not compatible with MXE.
With MXE we must use such low quality value that cammodule will not retry to take another picture.
Posted by stingjoel
@Kriomag,
I have no trouble at all with your camdriver...it's great and I am still test it
Posted by wickedsick
SPU, Raiderski, Lpachuong, what do HH and LL stand for?
Posted by SPU
wickedsick
Bytes of the machine word. High and low.
Posted by loucostanza
@raiderski,kriomag,spu,lpachuong
may the heaven bless you all
lets show to the world 2mpx era hasn't ended yet.
let the other phones fight each other for the best title, but there is one thing they shouldn't forget: we'll never ever give our crown of this class up to the other phone easily.
show them how the hell is feels
just do your part, and we'll do our part to show them how good your drivers are.
BRAVO!!
[ This Message was edited by: loucostanza on 2007-12-16 18:38 ]
Posted by lpachuong
A4A 11.00 Reloaded
http://www.freewebs.com/ict20[....]driver0%2011.00%20reloaded.DAT 95%
http://www.freewebs.com/ict2006_2007/camdriver0%2011.00%2091.dat 91%
Hope you are pleased with this. I'm looking forward to seeing pictures and comments from you.
Have a nice day.
_________________
To be or not to be !!!
Please save our world. Save our world to save our lives and our generation.
There is no place as good as your house with your family. Home sweet home.
[ This Message was edited by: lpachuong on 2007-12-17 10:44 ]