Posted by jomateixa
On 2008-01-16 17:43:19, pietropizzi wrote:
OK I tried:
seq_set_prop_0 =
$s5 %0
$-5 09
$p1 08 // put Effects-Property into Reg1
$c1 04 // Is Black-White Effect selected then
#COM_EVENT(43,$w5) // Set FOCUS with Stick (thx number1)
$cl
$c1 02 // Is Solarize Effect selected then
#COM_EVENT(58,$w5) // Set Colorgain with Stick
$s5 00 // Set 0 in Reg 5 so Exp wil be 0 ?
$cl
$c1 01 // Is Negative Effect selected then
#COM_EVENT(56,$w5) // Set Sharpness with Stick
$cl // IF other Effect or Normal do normal EV operation
#COM_EVENT(06,$w5)
$cx
$cx
$cx;
I did (almost) what you both advised.
Good news:
Setting FOCUS with stick is --> WOOOOAAAAAHHHHH !!!
In combination with Zoom you get great Preview !
Now If we just can HOLD that Focus because on HalfPress the AutoF sets in and overwrites the manual setting.
Maybe some command to disable AutoAF then ??
Bad news:
The $s5 00 I did by myself because I thought I should just fill the Reg5 with 0 so Exp. will also be filled with 0. Doesn't work.
It seems you're right ans stick acts not like a PC-Joystick to "recenter" back to 0, it simply stays where it was before.....
Some other trick to reset before choosing another property ?
I'd like to play with some FORCE ISO but these values arent linear so it will be tricky to calculate
For EV 0.0 you should put $-5 09 (09 is 0EV)
Posted by number1
to disable autofocus set the camera focus to infinity, or you could try
#SET_REG(32,80) focus off?????
Posted by jomateixa
This is getting interessant
Posted by pietropizzi
Focus to infinity works ! The picture is made with focus manual set by stick !
#COM_EVENT(43,$w5)
#SET_REG(32,80) // AutoFocus OFF ???? --> didn't work
Interesting improvement and easy to implement !
Ill try to force a 8x Zoom along with Focus setting.
Something like #COM_EVENT(61,80) should do it.....--> doesnt work
The Focus range seems only to wor from 0 to +2 EV.
Maybe some calculation on offset would increase range, needs investigation....
Exp. still sets to last stick position, no matter what I force it to be
also with $s5 09. It has to be set manually after settin all other properties.
And I look for WB on(Auto) / off and ISO forcing......
[ This Message was edited by: pietropizzi on 2008-01-16 17:23 ]
[ This Message was edited by: pietropizzi on 2008-01-16 17:26 ]
[ This Message was edited by: pietropizzi on 2008-01-16 17:31 ]
Posted by jomateixa
Exp. still sets to last stick position, no matter what I force it to be
also with $s5 09. It has to be set manually after settin all other properties.
I told you $-5 09, at the end before #COM_EVENT(06,$w5)
Posted by pietropizzi
Yes, I knew but putting that again subtracted twice ! Because that sutraction is at the beginning (for normal EV operation) and 9 is subtracted again !
But I tested it and it was like this: pictures got even darker and with +2EV they were almost normal !
It should be really the joystick that should be resetted and not EV because stick position / actual EV value will not fit each other after Effects operation !
$c1 04 // Is Black-White Effect selected then
#COM_EVENT(43,$w5) // Set FOCUS with Stick (thx number1)
$"Cam_mag_value_80"
#COM_EVENT(61,80) // 8x Zoom ???
doesn't work, it doesn't seem to be the correct Zoom 8x - command
***edit*** i see that should be Hex, I'll try (61,20) better..
Yes that works:
#COM_EVENT(43,$w5) // Set FOCUS with Stick (thx number1)
$"Cam_mag_value_20"
#COM_EVENT(61,20) // ~10x Zoom !!!
This is Setting Focus including Zoom Preview in Black White !
Setting Effects back to normal sets Zoom back to normal !!
...as it should be !!!!
Manual Focus also works in Macro but the range is different. Of course because Macro extends range, so I have to lower the offset.
[ This Message was edited by: pietropizzi on 2008-01-16 19:30 ]
Posted by Raiderski
why with joystick and ev+effect?
what about zoom keys instead? for example:
- macro off = AF
- macro on = manual focus (and set bit in some register as flag to block AF)
ok, i will do some changes on my big K
Posted by number1
@Raiderski have u got you k800i yet????, and would you mind helping me with EM mode for my k550i driver, i pm'ed you but you don't respond
Posted by pietropizzi
Hi !
I PNed you my code on Zoom Keys some weeks ago, you asked me to, remember ?
/***************************************************
// Zoom, property 6 *****
//***************************************************
SM_TEST=#COM_EVENT(55,$w4);
seq_set_prop_6 = $s4 %0 $-4 0a #SM_TEST;
The Change settings on Zoom keys didn't work for me.
So I take another approach on Effects+EV-Stick.
I would of cource appreciate whet you get it with Zoom Keys !
But we found out that Zoom Keys are very sensitive and it's hard to tell the amount of steps it will take on press
As there isn't a scale on ZoomBar you'll probably need something like this:
I replaced the ZoomBar-Graphics with numeric Indicators (1 - F)
-->
I don't know if you're brave enough to mod your brandnew K
[ This Message was edited by: pietropizzi on 2008-01-16 20:57 ]
Posted by killerPK
Hmm now that pietropizzi has got manual focus going, and Raiderski also seems to have K800 now, looks like K800 modding scene is going to get turbo-charged
.... welcome to the club Raiderski.
Posted by stat5bot
Anybody knows how to know the current camera driver installed in k800i?
Posted by pietropizzi
OK, this is the code I'm satisfied for today
//************************************************
// Exposure property 0 *****
//************************************************
// 3 => -2 EV, 9 => -(0) EV .... f => 2 EV
//---------------------------------------------------
seq_set_prop_0 =
$s5 %0
$s4 %0
$-4 03 // Extend range for settings >=0
$-5 09 // Normal EV range
$p1 08 // put Effects-Property into Reg1
$c1 04 // Is Black-White Effect selected then
#SET_REG(32,01) // Extend to full range
#COM_EVENT(43,$w4) // Set FOCUS with Stick (thx number1)
#COM_EVENT(61,20) // 8x Zoom
$cl
$c1 02 // Is Solarize Effect selected then
#COM_EVENT(58,$w4) // Set Colorgain with Stick
$cl
$c1 01 // Is Negative Effect selected then
#COM_EVENT(56,$w4) // Set Sharpness with Stick
$cl // IF other Effect or Normal do normal EV operation
#COM_EVENT(06,$w5)
$cx
$cx
$cx;
Forget about sharpness and Colorgain.
This does:
On Setting Effect Black White:
Viewfinder zooms in 8x
The Focus Range is extendet to Macro (Full) no mather what the Focus is really set to ! Set to Infinity will help deactivate AF !
Use stick to set Focus
Set Effect back to normal
Set EV Value (get Stick to 0 EV for normal operation)
Use it, play with it, port it on Zoom keys, do whatever you like !
[ This Message was edited by: pietropizzi on 2008-01-16 22:46 ]
Posted by jomateixa
On 2008-01-16 23:45:53, pietropizzi wrote:
OK, this is the code I'm satisfied for today
//************************************************
// Exposure property 0 *****
//************************************************
// 3 => -2 EV, 9 => -(0) EV .... f => 2 EV
//---------------------------------------------------
seq_set_prop_0 =
$s5 %0
$s4 %0
$-4 03 // Extend range for settings >=0
$-5 09 // Normal EV range
$p1 08 // put Effects-Property into Reg1
$c1 04 // Is Black-White Effect selected then
#SET_REG(32,01) // Extend to full range
#COM_EVENT(43,$w4) // Set FOCUS with Stick (thx number1)
#COM_EVENT(61,20) // 8x Zoom
$cl
$c1 02 // Is Solarize Effect selected then
#COM_EVENT(58,$w4) // Set Colorgain with Stick
$cl
$c1 01 // Is Negative Effect selected then
#COM_EVENT(56,$w4) // Set Sharpness with Stick
$cl // IF other Effect or Normal do normal EV operation
#COM_EVENT(06,$w5)
$cx
$cx
$cx;
Forget about sharpness and Colorgain.
This does:
On Setting Effect Black White:
Viewfinder zooms in 8x
The Focus Range is extendet to Macro (Full) no mather what the Focus is really set to ! Set to Infinity will help deactivate AF !
Use stick to set Focus
Set Effect back to normal
Set EV Value (get Stick to 0 EV for normal operation)
Use it, play with it, port it on Zoom keys, do whatever you like !
[ This Message was edited by: pietropizzi on 2008-01-16 22:46 ]
Well done pizzi
And what about the contrast? We can put it in Sepia effect
Posted by alvink83
What does "Set sharpness with stick"?
Posted by pietropizzi
It sets sharpness with stick
I THINK it does because colorgain also works so why shouldn't sharpness work. But I I was so happy playing around with FOCUS that I forget everything around....
I'd like to know HOW number1 found the Focus command, I mean that it accepts other parameters than (43,00), just by try and error ?
What would be the max then, because for now max=F because of EV+ doesn't go any further.....
@jomateixa
Of course you could put other properties (Contrast...) on Effects, but from what I learned from you and number1 its better to keep contrast low (except DOC Mode, where it is raised) so I don't see any need....
I'd really like to see some kind of noise reduction by possibility to fast WB ON/OFF and ISO FORCING.
I mean look an http://www.esato.com/board/viewtopic.php?topic=135737&start=8160 where Kriomag shows the difference between AutoWB OFF / ON on K750.
[ This Message was edited by: pietropizzi on 2008-01-17 06:31 ]
Posted by reggiele
Thanks for the good message Peter!!
Posted by brazuka
Guys
Whats chip model you are using is based? and that frequency of the clock are u working on? k800
Good job
Posted by Raiderski
pietropizzi
i remember, sorry for no response but without the phone i couldn't test this. today i will start to mod K800 driver and if zoom keys will be ready to use i will post recipe
BTW.
number1 found command 43 in k750/w800/w810 drivers
we know about cmd43 from long time. modded 2mp drivers are the best source of knowledge and solutions
Posted by number1
yea i know, command 43 is under the autofocus property in the k800i, can you reccomend me a value for #COM_EVENT(57,00) the colour hue,
Posted by Raiderski
HUE doesn't work as we expected. we have access to only small part of full colors slide area. probably HUE is cooperating with other (unknown) register. you can try biggest possible values for 8bit:
0x7F - red to orange
0x80 - red to light violet
BTW.
for 2mp phones, cmd 43 can have this values:
00 = infinity
...
32 (0x20) = closest focus
Posted by number1
colour hue works i used #COM_EVENT(57,80), and everythings violet coloured lol, have do you use the colour hue to the best advantage to get better colour.
Posted by jomateixa
On 2008-01-17 07:26:58, pietropizzi wrote:
It sets sharpness with stick
I THINK it does because colorgain also works so why shouldn't sharpness work. But I I was so happy playing around with FOCUS that I forget everything around....
I'd like to know HOW number1 found the Focus command, I mean that it accepts other parameters than (43,00), just by try and error ?
What would be the max then, because for now max=F because of EV+ doesn't go any further.....
@jomateixa
Of course you could put other properties (Contrast...) on Effects, but from what I learned from you and number1 its better to keep contrast low (except DOC Mode, where it is raised) so I don't see any need....
I'd really like to see some kind of noise reduction by possibility to fast WB ON/OFF and ISO FORCING.
I mean look an http://www.esato.com/board/viewtopic.php?topic=135737&start=8160 where Kriomag shows the difference between AutoWB OFF / ON on K750.
[ This Message was edited by: pietropizzi on 2008-01-17 06:31 ]
I think disabling WB is not a good idea, but the possibility to switch off it when we want yea it's perfect, I will test some mods I'm thinking, but I don't have time grrrr
Cheers
Posted by number1
no whitebalance is better than the k800i's awful whitebalance 90% of the time it got the colours and everthing wrong & some pictures had a cloundy bluish effect,
Posted by Raiderski
i used 00 because in my opinion HUE is good only as optional function (in supermode when user has manual control and want to change HUE value) but of course my opinion don't have to be the the best
auto WB can be locked - #COM_EVENT(11,01) (or in number1 way: 80 instead of 01)
Posted by number1
so #COM_EVENT(11,01) is locked &
#COM_EVENT(11,80) is off, i prefer it off so it doesn't spoil my pictures
Posted by LaurensB
Hacked Number12.95 with manual focus and the other WIP code :
http://files.myopera.com/LaurensB/files/camdriver0.dat
Credit's go to the authors, not me.
An example with manual focus :
[img]
http://files.myopera.com/LaurensB/files/DSC00597.jpg
[/img]
Yes, yes it's not the best picture so go out and make some better
We do now have the tools!
Posted by pietropizzi
auto WB can be locked - #COM_EVENT(11,01) (or in number1 way: 80 instead of 01)
Oh I got it wrong then I thought:
#COM_EVENT(11,01) is "OK, calculate and lock the WB to what is in VF right now" and
#COM_EVENT(11,80) is AutoWB is not in use, just do nothing
This is my new code, cant upload, forgot bluetooth stick
Yea, patching got easier !:)
seq_set_prop_0 =
$s5 %0
$-5 09 // Normal EV range
$s4 %0
// Now we do some calc tryout (thx Raiderski)
$-4 03 // Extend range for settings >=0
$*4 08 // Extend 12 EV-Stick steps to 32 Focus steps
$/4 03
$p1 08 // put Effects-Property into Reg1
$c1 04 // Is Black-White Effect selected then
#COM_EVENT(61,14) // 3.2x Zoom for closer view
#SET_REG(32,01) // Extend Focus to full range
#COM_EVENT(43,$w4) // Set FOCUS with Stick (thx number1)
Posted by killerPK
Anyone tried changing the 13Mhz(32C8) clockspeed to 15(3A98) or 20Mhz(4E20) ?
Posted by number1
over clocking the MHZ will allow for higher fps bugless video recording but will also heat up the phone, the phone will get very hot.
Posted by pietropizzi
On 2008-01-17 14:29:51, LaurensB wrote:
Hacked Number12.95 with manual focus and the other WIP code :
Credit's go to the authors, not me.
An example with manual focus :
Yes, yes it's not the best picture so go out and make some better
We do now have the tools!
Good to use it ! But iI took Standard driver because there arent any colorgain or sharpness setiings hidden.
But if you mod already modded drivers, take care if the 55,56,58 parameters aren't used somewhere else again, so your manaul stick setting will be overwritten then ! Do a search for thhem first!
I think MF could be used for mybe take spider on water surface, how would you AF that
Posted by LaurensB
On 2008-01-17 14:35:18, killerPK wrote:
Anyone tried changing the 13Mhz(32C8) clockspeed to 15(3A98) or 20Mhz(4E20) ?
Just tried that
Didn't work.
On 2008-01-17 14:41:46, pietropizzi wrote:
On 2008-01-17 14:29:51, LaurensB wrote:
Hacked Number12.95 with manual focus and the other WIP code :
Credit's go to the authors, not me.
An example with manual focus :
Yes, yes it's not the best picture so go out and make some better
We do now have the tools!
Good to use it ! But iI took Standard driver because there arent any colorgain or sharpness setiings hidden.
But if you mod already modded drivers, take care if the 55,56,58 parameters aren't used somewhere else again, so your manaul stick setting will be overwritten then ! Do a search for thhem first!
I think MF could be used for mybe take spider on water surface, how would you AF that
It's not ment to be used as a serious improvement, just a quick way for those that love to try out new features! I'm sure number1 and the other great camera coders are following your developments with an eager want to use it! And they can implent it way better than I can
Just tested your new code btw! Works great, the 32x zoom works as far as I can tell (no way to say for sure if it's really 32x
) and I can get a really nice out of focus picture so I think the settings are saved
[ This Message was edited by: LaurensB on 2008-01-17 13:52 ]
[ This Message was edited by: LaurensB on 2008-01-17 13:56 ]
Posted by killerPK
On 2008-01-17 14:41:30, number1 wrote:
over clocking the MHZ will allow for higher fps bugless video recording but will also heat up the phone, the phone will get very hot.
So how much do you think we can increase the clockspeed so that it doesnt get too hot? 15 or 16Mhz fine?
Posted by Raiderski
#COM_EVENT(11,00) is realtime WB update (that's why it's called auto)
#COM_EVENT(11,01)
#COM_EVENT(11,80) both are WB lock (can be used as permanent auto WB off)
ok, i know that auto WB isn't ideal but locking it permanently? i don't know... for now i will not touch WB settings
Posted by jomateixa
On 2008-01-17 14:59:53, Raiderski wrote:
#COM_EVENT(11,00) is realtime WB update (that's why it's called auto)
#COM_EVENT(11,01)
#COM_EVENT(11,80) both are WB lock (can be used as permanent auto WB off)
ok, i know that auto WB isn't ideal but locking it permanently? i don't know... for now i will not touch WB settings
I agree, for me the only good solution is the ability to put it off/on on the fly
Posted by number1
#COM_EVENT(11,80) is OFF not lock or anything, i got it from the t650 camdriver, loads of things are turned off, this is from the t650i driver
sharpness off #WR_REG(21, 80), whitebalance off #WR_REG(14, 80),
see
//**************************************************
// Digital Sharpening, property 21
//
// 0 => Off <<<< OFF 1 => +1 2 =>+2 3 => +3
// 4 => +4 5 => +5 6 => Auto
//**************************************************
seq_set_prop_15_0 = #WR_REG(21, 80); <<<<< OFF
seq_set_prop_15_1 = #WR_REG(21, 00);
seq_set_prop_15_2 = #WR_REG(21, 01);
seq_set_prop_15_3 = #WR_REG(21, 02);
seq_set_prop_15_4 = #WR_REG(21, 03);
seq_set_prop_15_5 = #WR_REG(21, 04);
seq_set_prop_15_6 = #WR_REG(21, 40);
Posted by Mike2
On 2008-01-17 14:29:51, LaurensB wrote:
Hacked Number12.95 with manual focus and the other WIP code :
http://files.myopera.com/LaurensB/files/camdriver0.dat
Credit's go to the authors, not me.
An example with manual focus :
[img]
http://files.myopera.com/LaurensB/files/DSC00597.jpg
[/img]
Yes, yes it's not the best picture so go out and make some better
We do now have the tools!
I can't take a colour pic with this driver.
How did you take a colour picture?
Enabling B&W allows me to MF, but the resulting pics are always B&W
Posted by pietropizzi
Works great, the 32x zoom works as far as I can tell (no way to say for sure if it's really 32x
) and I can get a really nice out of focus picture so I think the settings are saved
Take care its in fact 3,2x (look at the code)
EDIT: Enabling B&W allows me to MF, but the resulting pics are always B&W
Of course ! The BW Effect itself isn't disabled (easy to do that if you want). You have to switch back to Normal (no effect) after setting !
[ This Message was edited by: pietropizzi on 2008-01-17 14:51 ]
[ This Message was edited by: pietropizzi on 2008-01-17 14:52 ]
Posted by Raiderski
T650 sensor is Foxconn. most of registers and values are different thus they cannot be applied in Sony sensor with the hope that they'll work for sure exactly as in Foxconn. this is very simple thing for me and there is no reason to discuss about this. if you permanently set 01/80 no matter of value result will be the same - auto WB doesn't work after camera open. so "lock" or "off" naming conventions are unimportant in this case
Posted by Mike2
On 2008-01-17 15:22:25, pietropizzi wrote:
Take care its in fact 3,2x (look at the code)
EDIT: Enabling B&W allows me to MF, but the resulting pics are always B&W
Of course ! The BW Effect itself isn't disabled (easy to do that if you want). You have to switch back to Normal (no effect) after setting !
Aha, thanks for the information
Would it be possible to disable the B&W effect only on document mode?
Posted by Kriomag
im just curious: what is the buffer limit in k800? in k750i its ~616kB
Posted by Mike2
On 2008-01-17 16:51:26, Kriomag wrote:
im just curious: what is the buffer limit in k800? in k750i its ~616kB
Posted by number1
yea 906kb, it's limited by the main firmware i can easily increase it beyond 906 in the driver but it would just crash the cam, can't someone make a patch to remove the photo size limit.
Posted by Kriomag
On 2008-01-17 16:59:43, number1 wrote:
yea 906kb, it's limited by the main firmware i can easily increase it beyond 906 in the driver but it would just crash the cam, can't someone make a patch to remove the photo size limit.
is there any "master patch-er" who can do this for k750@w800?
Posted by number1
i'm surpised no1's done it for the k750i yet, k750i has a slower older processer with less ram, so i'm not sure if it could handle larger file sizes, the k800i is a db2020 with more ram it can view and edit 3mb 5mp pictures, so it should be able to make 1.5mb 3mp pictures with the camera.
Posted by geroldbravo
what's the exactly ram of a normal k800i??
Posted by Kriomag
On 2008-01-17 17:32:56, number1 wrote:
i'm surpised no1's done it for the k750i yet, k750i has a slower older processer with less ram, so i'm not sure if it could handle larger file sizes, the k800i is a db2020 with more ram it can view and edit 3mb 5mp pictures, so it should be able to make 1.5mb 3mp pictures with the camera.
w810 has the same processor? (maybe even the same amouth of ram) and it can take over 800kB pictures... thats why i think its possible for k750i too
Posted by number1
a raw uncompressed 2mp photo will be about 1mb in size a raw uncompressed 3mp will be about 1.5mb in size, i reccon the phones can handle this but photo saving time might be a little bit longer, but i'd rather a uncompressed.
Posted by brazuka
Killer
Anyone tried changing the 13Mhz(32C8) clockspeed to 15(3A98) or 20Mhz(4E20) ?
number
over clocking the MHZ will allow for higher fps bugless video recording but will also heat up the phone, the phone will get very hot.
-----------------------------------------------------------------------
Some chips support up to 24 mhz to 27 MHz master clock but in case but this case is different because the k800 works in 15 fps in high resolution full resolution well can do a test by increasing the frequency of the clock display screen and the frequency of recording video continues it can be a test but not exceeding the 27 mhz in both clocks, each processor chips supports a limit and am not sure what is the limit to the k800 resolutions but in the low resolutions limit is 27 MHz master clock above that value the burden on the hardware may damage.
example:
cam_i2c_address=[n]; //Micro Sensor
cam_i2c_clock_freq=[6978]; //27Mhz
cam_vf_clock_freq=0,[BB80]; //48MHz Video screen display speed
cam_ss_clock_freq=0,[32C8]; //13MHz frequency Sensitive the photos and video and high luminosity of the times the sensor camera does not support taking photos with making mistakes or overlapping photos but that each sensor works in a way
cam_ss_clock_freq_d=0,[5DC0]; //24 MHz yuv-mode formats (progressive scan)
I donīt know really what that the processor chip can be k800 works
OV3640 or MCB881 or KNC
[ This Message was edited by: brazuka on 2008-01-17 17:39 ]
Posted by number1
i over clocked it to 14mhz, seems fine phones not overheating i'm not going any higher cause i fear i might damage the hardware, 21fps is too slow for video and bestpic is two slow, everything else seems fine
Posted by number1
over clocking it is a bad idea, it overexposes and the cam can't focus and runs to slowly.