Posted by SonarikK510
This topic is for camdriver modding discussion
I think it is better for us to discuss in one topic different refinements of camdriver modding (best params and settings, share experence and so on).
I'll hope that cammodding guys (Number1, Kriomag, Raiderski and others) agree with me.
Posted by strong
Good idea ''the modders corner'' well done my fried
Posted by number1
a place to share our ideas yes a good idea
Posted by SonarikK510
This software are for editing language files http://www.filehoster.ru/files/m5848
You understand that a have in view?
Now we can fully rename menu of camera! And called scenes and etc correct names!
For example, i can change in my camdriver name of Effect Solarize to LiveColours! That's brilliant!
And with help of other soft (for changing gfx of db2020) we can draw new icons and many others!!!!
The camdriver modding step to next stage of evolution!
I am congratulate heartily all you, my colleague!
Posted by Raiderski
ok, i'm in. my posts about code will be here
Posted by DarkEternity
Hi, i'm new to this and i was wondering if this was possible. I have a k750 and a k550 and the camera on my k750 is much better. Is it possible to take my k750 camera driver and put it on my k550? or is there anyway i could mod my k750 camera driver to work with my k550?
Thanks
Posted by strong
I think this is not possible
_________________
k750@w800 R1BC002 www.camdrivers.wz.cz/
[ This Message was edited by: strong on 2008-01-27 22:06 ]
Posted by jomateixa
Hey Pros, there's a little bug when using the force flash code:
seq_set_prop_e_2 = $sb 04 // Forced ON, for service menu and production tests
$c9 08 // R5 camera version?
#COM_EVENT(5a,83) // Forced xenon 0b10000011, slow sync at beginning
$cl
#COM_EVENT(51,00) // Sensor scene "Auto 00"
#COM_EVENT(5a,9b) // FLASH_MODE 0b10001011: Flash on, RER off, sync on beginning.
$cx;
When switching to doc mode, #SET_REG(40,01) in doc macro is overrided, being AE_XENON_ISO 320 or wherever but only the first pic. If we semi-press the camera button for take another pic ISO is 100, but not in any other case. I putted a macro to force xenon ISO 100 if doc mode selected but it does nothing.
In two or three days I can spend time on it, but now I don't have the time. It should be very easy to force flash changing some register values in property 23, and it will be more elegant.
I just want to inform about that bug.
Cheers
[ This Message was edited by: jomateixa on 2008-01-27 22:48 ]
Posted by alvink83
On 2008-01-27 21:01:03, SonarikK510 wrote:
This software are for editing language files http://www.filehoster.ru/files/m5848
You understand that a have in view?
Now we can fully rename menu of camera! And called scenes and etc correct names!
For example, i can change in my camdriver name of Effect Solarize to LiveColours! That's brilliant!
And with help of other soft (for changing gfx of db2020) we can draw new icons and many others!!!!
The camdriver modding step to next stage of evolution!
I am congratulate heartily all you, my colleague!
How to use the software? Thank you
Posted by SonarikK510
$s5 %0 $-5 08 #COM_EVENT(56,$w5);
Anybody can explain to me that code? ( i know, that is a sharpness param)
I don't know this codes (with $s5, $-5 and so on), only macroses such as #COM_EVENT(56,$w5), #SET_REG, and others....
So, anybody can explain what does mean
$s5 - ?
%0 - ?
$-5 - ?
08 - ?
Where i can get manual about this commands?
@ alvink83
Open main programm, open the *lng file, search a necessary text, change it, click apply, save as..... and upload to your phone, to a hidden FS
Posted by pietropizzi
On 2008-01-28 18:17:31, SonarikK510 wrote:
$s5 %0 $-5 08 #COM_EVENT(56,$w5);
Anybody can explain to me that code? ( i know, that is a sharpness param)
I don't know this codes (with $s5, $-5 and so on), only macroses such as #COM_EVENT(56,$w5), #SET_REG, and others....
So, anybody can explain what does mean
$s5 - ?
%0 - ?
$-5 - ?
08 - ?
Where i can get manual about this commands?
@ alvink83
Open main programm, open the *lng file, search a necessary text, change it, click apply, save as..... and upload to your phone, to a hidden FS
$s5 %0 $-5 08 #COM_EVENT(56,$w5);
can also write as
$s5 %0
$-5 08
#COM_EVENT(56,$w5);
$s5 %0 --> put the selected param into local Reg 5 (set)
$-5 08 --> then subtract 08 from Reg 5
#COM_EVENT(56,$w5); ---> the result will be the sharpness parameter ($w5 reads it from Reg 5)
Posted by SonarikK510
pietropizzi, Ok, thanks, but what does mean Reg5? Where i can see it in a camdriver?
Posted by number1
if you mean
seq_set_prop_15 = $s5 %0
$-5 08
#COM_EVENT(56,$w5);
it's digital postprocessing settings this is the main value that can be changed 08, 08 is off
Posted by pietropizzi
On 2008-01-28 18:44:45, SonarikK510 wrote:
pietropizzi, Ok, thanks, but what does mean Reg5? Where i can see it in a camdriver?
From what I think is
that Reg 5 is a LOCAL Reg which is just used in that property to help calculation... So Reg 5 can be used more often
What I learned from Raidersky is that there are Regs that are stored GLOBAL like he used RegE in his protoptype. But I' not sure about that.....Raidersky help me !
Posted by jomateixa
On 2008-01-28 18:44:45, SonarikK510 wrote:
pietropizzi, Ok, thanks, but what does mean Reg5? Where i can see it in a camdriver?
These regs (all from 00 to 0f I think) are used for store temp values 4 make math operations or check conditions or wherever...
If there's any stored globally I don't know.
$sX ----> 's' from 'Set'
$cX ----> 'c' from 'Check'
$dXXXX -----> 'd' from 'Delay'
...
...
etc...
$-a XX ----> Substract 'a' from XX
$+a XX ----> Add 'a' to XX
...
...
etc...
With some conditional operators and these regs you can do a lot of things
[ This Message was edited by: jomateixa on 2008-01-28 20:33 ]
Posted by jomateixa
Oh sorry pizzi already answered you
Posted by petkoxray
How i can add or edit color corection to original driver ?
Posted by jomateixa
On 2008-01-27 23:31:00, jomateixa wrote:
Hey Pros, there's a little bug when using the force flash code:
seq_set_prop_e_2 = $sb 04 // Forced ON, for service menu and production tests
$c9 08 // R5 camera version?
#COM_EVENT(5a,83) // Forced xenon 0b10000011, slow sync at beginning
$cl
#COM_EVENT(51,00) // Sensor scene "Auto 00"
#COM_EVENT(5a,9b) // FLASH_MODE 0b10001011: Flash on, RER off, sync on beginning.
$cx;
When switching to doc mode, #SET_REG(40,01) in doc macro is overrided, being AE_XENON_ISO 320 or wherever but only the first pic. If we semi-press the camera button for take another pic ISO is 100, but not in any other case. I putted a macro to force xenon ISO 100 if doc mode selected but it does nothing.
In two or three days I can spend time on it, but now I don't have the time. It should be very easy to force flash changing some register values in property 23, and it will be more elegant.
I just wanted to inform about that bug.
Cheers
[ This Message was edited by: jomateixa on 2008-01-27 22:48 ]
Fixed the bug very easily just implementing FF by forcing Reg 5 to value 03 in Property 23 (00 for R5).
Cheers
[ This Message was edited by: jomateixa on 2008-01-28 21:52 ]
Posted by Raiderski
1. all register are general purpose registers - some of them are used to store data, some are free or used for calculations
2. SE called them 'platform' registers
3. we have 16 registers reg0 - regF
4. probably they are 32bit registers but in compare command ($cR VV) only first 8 bits are compared
5. you can reorganize and use them as you want
in K800 driver:
// 0, Used for macros
// 1, Used for macros
// 2, Used for macros
// 3, Used for macros
in macros like COM_EVENT, SET_REG, CHANGE_MODE etc. so, they can be used for calculations but in limited way. you will loose all values in this registers if you call any code operation or event (CO&E) macro. if you will not use CO&E macro before calculations then registers can be used for normal arithmetic operations
// 4,
it's free
// 5, Used in Property 6
looks like reserved but it's not. it's free
// 6, Used for resolution ids
reserved but can be freed. resolution ID can be retrieved by command $zR (R = platform register) and then compared with ss/vf_config_NN value
// 7, Used ACM abort flag for synchronized viewfinder images.
// 8, Used to remember ISO setting since one has to change to AE_MODE to "auto" for IS.
// 9, Firmware version, checked in init_sequence
all are reserved but can be moved to different free registers
// a,
it's free
// b, Used for Flash
// c, Used for sensor scenes
all are reserved but can be moved to different free registers or squeezed to one register only
// d, 0 => normal, burst 1 => read out pict 1 ...
// e, Image stabilization 1 => ON, 0 => OFF
// f, Image format 1 => JPEG, 0 => YCbCr
all three registers are reserved but 2 of them can be freed. all values are 0 or 1 - this is normal boolean state and only 1bit value. bit operations come in handy ($bR):
$bR BB S L
R = platform register
BB = set of bits
S = index of first bit to replace
L = amount of bits to replace
this command will copy L bits from BB (from right to left). first replaced bit will be S in register R
r1 = 0bXXXXXXX
after $b1 03 2 4
r1 = 0bX0011XX (03 = in bit notification: 0b0011)
_________________
K800 R1KG001 (driver in development)
W800 CID36 R1BD001 (driver 6.7.2)
raider.4shared.com
flickr.com/photos/raiderek
[ This Message was edited by: Raiderski on 2008-01-28 22:10 ]
Posted by jomateixa
5. you can reorganize and use them as you want
Posted by SonarikK510
whoa........ thanks for the answers, guys... To my mind, at present time i'm newbie in cam modding.. Shit..... How you teach all it?!
How you think: a bigger file size give more quality or not?
For example, i set average size up to ~700 kilobytes, but original (from SE) average size is ~450 kilobytes.
So, 700kilobytes gives more quality then 450?
And what best value of quality compression? To my mind, 92-94%
_________________
W610 + M2 512Mb + HBH-DS970 + Patches + Flash menus + Language edit + Most High Quality camdriver ( by me
) + many other......[ This Message was edited by: SonarikK510 on 2008-01-29 16:17 ]
Posted by jomateixa
On 2008-01-29 17:14:37, SonarikK510 wrote:
whoa........ thanks for the answers, guys... To my mind, at present time i'm newbie in cam modding.. Shit..... How you teach all it?!
How you think: a bigger file size give more quality or not?
For example, i set average size up to ~700 kilobytes, but original (from SE) average size is ~450 kilobytes.
So, 700kilobytes gives more quality then 450?
And what best value of quality compression? To my mind, 92-94%
_________________
W610 + M2 512Mb + HBH-DS970 + Patches + Flash menus + Language edit + Most High Quality camdriver ( by me
) + many other......
[ This Message was edited by: SonarikK510 on 2008-01-29 16:17 ]
In JPEG compression quality is given by the Q factor (but it's not standarized). The size is directly proportional to Q. In most cases, for values since Q=75 it's very difficult to see any quality difference, but this depens on the JPEG implementation. Q=90 does not mean 90% compression free. If you put it greater than Q=95, size will be several times bigger and the quality gain infinitesimal. JPEG is based on the Huffman coding (as well as gzip, mp3, png...)
Posted by SonarikK510
ok, and what a Q-factor param do you use?
I know that it is a variable, no constant.
If i set Q=95, 95 was a max value
[ This Message was edited by: SonarikK510 on 2008-01-29 19:20 ]
Posted by Sator1973
I'm using "Ultimate 2.11 vivid color" right now, and color and sharpness are pretty good. But I must say it takes a lot of time comparing all available mods, so I just use them for a week or so, and then try another.
@ jomateixa: I wouldn't mind bigger files if this resulted in higher quality pics; Ultimate 2.11 pic sizes are from about 700 kB to 900kB large. Does it have the best compromize for size and quality?
@Sonarik: Could you please start a topic on how to edit language packs with the software you use? I think a lot of modders would be very grateful to you (and it would keep this topic "on topic").
Posted by number1
On 2008-01-29 20:18:21, SonarikK510 wrote:
ok, and what a Q-factor param do you use?
I know that it is a variable, no constant.
If i set Q=95, 95 was a max value
[ This Message was edited by: SonarikK510 on 2008-01-29 19:20 ]
file sizes are limted by the main firmware so increasing the file size beyond the limit will only make the phone crash
Posted by tylerhill
that is a good idea thank you a lot
FLORIDA people search
[ This Message was edited by: tylerhill on 2008-01-30 04:30 ]
Posted by SonarikK510
i know, that the file size beyound size limit phone crash.
For example, limit for k550 - about 915-920kb
Posted by number1
so you know the limits so try this in the k550/w610 driver for 2mp low compression
900 800
#SET_JPEG_MIN(00,00) #SET_JPEG_MAX(03,84) #SET_JPEG_AVG(03,20) #SET_JPEG_QUALITY
Posted by SonarikK510
thanks.
Raiderski or Kriomag - bigger file size (bigger than orginal) gives more quality, or we can not see this on photo by eyes?
Posted by jomateixa
On 2008-01-30 18:06:41, SonarikK510 wrote:
thanks.
Raiderski or Kriomag - bigger file size (bigger than orginal) gives more quality, or we can not see this on photo by eyes?
It's really hard, or impossible, to see it. But it's cool
Posted by number1
it would probley take about 200kb to notice a small difference, i prefer having bigger file sizes.
Posted by SonarikK510
This code of a saturation #COM_EVENT(58,02) gives a real colours?
What original value of him? 00?
And what best value of contrast - 00 or 01? To my mind, for post-editing (for example, in any software for work with images - Photoshop, ACDSee...)
best is 00
Posted by number1
#COM_EVENT(58,02) <<<
on most new se phones cid:50 and above incresing the contrast also increases the brightness/exposure causing over exposed pictures,
best value is 00, 01 gives real colours but sometimes washed out colours
01 works well in older se phones k750i/w800, older w810i.
for newer se phones best value is 00
Posted by sadeghi85
On 2008-01-30 18:18:22, jomateixa wrote:
It's really hard, or impossible, to see it. But it's cool
On 2008-01-30 19:11:31, number1 wrote:
it would probley take about 200kb to notice a small difference, i prefer having bigger file sizes.
pick one of your pics, open it with MS Paint, without any touching just go to File->Save as... save it with another name. you will notice that file size is about 1/3 to 1/5 of original without any noticeable diffrence. jpeg compression will remove components(higher frequencies) that human eye can't see. decreasing compression has only one advantage: higher quality after postprocessing.
for whom that don't want to do postprocessing or don't know about it, decreasing compression has not any advantage but disadvantages, bigger file size means less memory to use and longer transferring time.
Posted by brazzuka's
@Number1
it would probley take about 200kb to notice a small difference, i prefer having bigger file sizes.
----------------------------------------------------------------------------------------------------
Number1 is correct of course, even as a matter of using the maximum capacity that enables us to the hardware, memory because if we do not use it, but the effect of increasing the file is noticeable at resolutions up from 1.3 mb in the pictures.
The larger the file size will be the best possibility of final composition of the photograph leave better.
@sadeghi85
pick one of your pics, open it with MS Paint, without any touching just go to File->Save as... save it with another name. you will notice that file size is about 1/3 to 1/5 of original without any noticeable diffrence. jpeg compression will remove components(higher frequencies) that human eye can't see. decreasing compression has only one advantage: higher quality after postprocessing.
for whom that don't want to do postprocessing or don't know about it, decreasing compression has not any advantage but disadvantages, bigger file size means less memory to use and longer transferring time.
-------------------------------------------------------------------------------------------------
The postprocessing can be obtained better results depending on the response of the hardware, photos with larger files and with a good response processing that is taking less time to process it and not lose quality would be the ideal has to be a balance "equilibriun".
In fact is that the larger the file buffer better because we lost so many details of the photo.
Because if we do M2 memory card why not use it
[ This Message was edited by: brazuka on 2008-02-01 19:53 ]
Posted by SonarikK510
Buffer - only for maximal photo size or for some else?
Max size of photo in my drv - 910kb. I set buffer to 1024kb. Is it a big or small?
Posted by SonarikK510
Any body change JPEG HEADER CREATION from one driver, to other driver? I don't know, are this values are similar all on SE phones.
Posted by brazzuka's
Sonarik
Filesize 910kb unless otherwise stipulated, and I believe 1024kb in programming? rigth??
The size of the files this course, the bigger better not lose anything with it but also has the limit that I think it should be by ranging from 900kb to 1000kb for each model and as a table-creation.
For the table of Rai can make sense because in other models of sony ericsson depending on the resolution the table and increase the file has no answer has no effect.
Possibly the jpeg files should be related to the videos not sure about that but I committed a mistake saying that the processing for this property cam_post_processing could accelerate or not the save of the file or buffer wherever but I am wrong because that property cam_post_processing defines the axis of rotation at 0/90/180/270 degrees degrees depending on the table, only managed to rotate the display on the video recording for horizontal but the hardware is not supported.
If you could rotate the VF display screen synchronized with the display of recording maybe could shoot pics or recording videos in horizontal and vertical but I think the hardware don´t support
One idea for you!!!
// cam_post_processing_x=
// Post processing for size configuration x:
// 0 = 0 degrees rotation
// 1 = 90 degrees clockwise rotation
// 2 = 180 degrees clockwise rotation
// 3 = 270 degrees clockwise rotation
// rotation setting for VT
cam_post_processing_19=01; // for VT 96 x 128 @ 15fps
cam_post_processing_20=01; // for VT 144 x 176 @ 15fps
//Rotation setting for VF
cam_post_processing_14=01; // for VF 320 x 240
Posted by LaurensB
Hey,
Have we found the K800i shutter time command yet? If not this topic might be a good way to discuse a strategy to discover it. I assume we have tried :
- Using known shutter speed command's (k850I, K750I, k550, K770, etc)
- Brute Force it? (try ALL possible commands)
- It get written to the EXIF information right? So it has to be read from memory before the phone can write it to the EXIF information.
Any other good method's? We could really use this information!
Posted by SonarikK510
brazuka, hardware don't support this
LaurensB, Using known shutter speed command's
#COM_EVENT(03,xx), when xx value of shutter speed in hex (1/value) * 2!
Example
#COM_EVENT(03,04) - 1/2 sec; #COM_EVENT(03,3C) - 1/30 sec; and others.......
Posted by Raiderski
good news, bad news...
shutter speed command equivalent:
#SET(29,xx) // shutter speed value
#CMD(02,02) // AE shutter speed priority (ISO fixed at 100)
values for xx can be found on raider.4shared.com in manual_by_SPU.html. they are for K750 but should also match in K800
at the moment this find is for nothing. you cannot build EM code in K800 because every changes (exposure, contrast, saturation etc.) in cam_ss_start are not applied! haha! ok, at least we have manual shutter speed control for supermode drivers
_________________
K800 R1KG001 (driver in development)
raider.4shared.com
flickr.com/photos/raiderek
[ This Message was edited by: Raiderski on 2008-02-06 17:13 ]
Posted by pietropizzi
Your're the man !
But I did't get the bad news right....maybe because I don't know much about EM as K800 is my first.
What you mean with "applied". I see from protoptype that I set specific settings in color, ISO, focus etc. to my needs and shoot. And in the shot taken, they are applied.
Do you mean the values for "special custom programs" like for example
NIGHT Portrait (1/20, ISO 200, Focus=1.8m, color=1)
aren't called at a EV/ZoomStep combination ?
Of course with that #COM_EVENT(02,xx) must be set to wanted prority first or conflict occurs.
Edit: OK, I see there's difference between Supermode and EM. For SM it should work, I'll try that. EM I don't know but I'll try to learn....
[ This Message was edited by: pietropizzi on 2008-02-06 18:26 ]
Posted by Raiderski
my mistake, not everyone have to know how typical EM is working
so, small explanation...
snapshot sequence looks like this:
seq_ss_start
seq_ss_take
seq_ss_verify
seq_ss_stop
sequence with EM:
seq_ss_start <--- here #EM_SET (shutter speed calculations and setup)
seq_ss_take
seq_ss_verify
seq_ss_stop <--- here #EM_UNSET (restore no shutter speed priority AE)
in this way EM is enabled only in snapshot process as it should be
---
the problem is in seq_ss_ because you cannot change parameters in it. for example: you can add to seq_ss_start/take code to change contrast before snapshot but it won't take any effect - contrast command is 'unvisible' and not only contrast but almost everything else too
oh crap
_________________
K800 R1KG001 (driver in development)
raider.4shared.com
flickr.com/photos/raiderek
[ This Message was edited by: Raiderski on 2008-02-06 19:24 ]
Posted by jomateixa
OMG
Posted by Raiderski
my top list of most irritating problems
1. impossible changes of image parameters in seq_ss_X
2. AE lock doesn't work on landscape scenes (infinity focus)
3. AF macro range only scan doesn't exist
4. bilinear filtering (zoom) cannot be disabled
Posted by number1
this
#SET(29,xx) // shutter speed value
#CMD(02,02) // AE shutter speed priority (ISO fixed at 100)
is completey useless for a few reasons,
iso is always 100, it also slows down the viewfinder fps to achieve the shutterspeeds like #COM_EVENT(03,xx), it also clashes with the iso
might aswell just use #COM_EVENT(03,xx)
Posted by Raiderski
sorry number1 but you wrote bullshits!
before you call something "useless" learn more about that thing or if you're so smart then do something more "useful". you don't have to be photography expert to understand how something is working but you shouldn't be ignoramus or fake expert. dude, get k750 in your hands and try 6.7.2 with manual shutter speed and manual shutter speed preview. after this experience you should understand how manual shutter speed can work in perfect way without disadvantages. ISO100 is problem? don't be ridiculous
i'm waiting for your discoveries mr. "smart"...
Posted by number1
On 2008-02-07 11:40:08, Raiderski wrote:
sorry number1 but you wrote bullshits!
before you call something "useless" learn more about that thing or if you're so smart then do something more "useful". you don't have to be photography expert to understand how something is working but you shouldn't be ignoramus or fake expert. dude, get k750 in your hands and try 6.7.2 with manual shutter speed and manual shutter speed preview. after this experience you should understand how manual shutter speed can work in perfect way without disadvantages. ISO100 is problem? don't be ridiculous
i'm waiting for your discoveries mr. "smart"...
i broke my k750i due to a stupid error shows how smart i am, but i used to use 1 of kriomags driver with manual shutter speed yes it was very useful i could set my own iso and shutter speed, no the shutter speed had no disadvantages on the k750i, but in the k800i it's stuck with iso 100 it is a problem it will be too dark most the time so you will need to always use a lower shutter speed to get a brighter picture, also it seems to be slowing down the viewfinder to achieve the shutter speeds which it never did on my k750i.
Posted by Raiderski
in the k800i it's stuck with iso 100 it is a problem it will be too dark most the time so you will need to always use a lower shutter speed to get a brighter picture
1. ISO100 isn't SE engineers fiction. only with ISO100 you will achieve exact shutter speed (SS). if you set 1/500s then picture will have 1/500s of exposure time
2. SS in k750 was equivalent of real SS. you can set SS but final effect isn't exact exposure time because it was always compilation of your shutter speed and automatic ISO. final effect - faster shutter speed but higher ISO. beautiful noise and not exact exposure time - this isn't real manual SS. i don't need mess, if i set 1/500s then i want 1/500s. first time real SS in k750 was in 6.6.1
3. maybe you won't believe but most users of k750 demanded ISO100 pictures
also it seems to be slowing down the viewfinder to achieve the shutter speeds which it never did on my k750i
1. you set SS to 2s and you want 15fps viewfinder refresh rate? from what if image samples are ready to display after 2s gaps? if your k750 was insensitive for this effect then it was magical phone
2. slowed down viewfinder is annoying and disturb AF (if focusing is longer than 5sec then you can't take pic). that's why i created manual SS preview:
with it you can virtually change SS as you wan't without any influence on viewfinder. if you want to take pic then you're doing half press to focus and full press to snapshot. short before snapshot process (when viewfinder refresh isn't active) manual SS is enabled and final pic has exact exposure time. after snapshot automatic SS is restored
with preview you can even see how selected manual SS looks like on viewfinder - you can enable/disable preview with half press
Posted by jomateixa
with it you can virtually change SS as you wan't without any influence on viewfinder. if you want to take pic then you're doing half press to focus and full press to snapshot. short before snapshot process (when viewfinder refresh isn't active) manual SS is enabled and final pic has exact exposure time. after snapshot automatic SS is restored
with preview you can even see how selected manual SS looks like on viewfinder - you can enable/disable preview with half press
That's perfect