| Author |
Super camera driver for k750/w800/w810 |
Kriomag
Joined: Dec 20, 2006
Posts: > 500
From: Poland
PM, WWW
|
Pictures taken with Kriomag_v21.93_BETA
[ This Message was edited by: Kriomag on 2008-01-12 01:09 ] |
|
|
MarkJason
Joined: Dec 03, 2005
Posts: 194
From: Bacolod City, Philippines 6100
PM |
On 2008-01-10 10:44:43, SPU wrote:
MarkJason
MXE is a special case.
In the original driver this is done in SET_JPEG_QUALITY macro:
We have quality value in r2 then we call SET_JPEG_QUALITY
SET_JPEG_QUALITY=
$p1 0e //check out MXE state
$c1 01 //if MXE is on
$s2 32 //override quality value (32 = 50%)
#SET_JPEG_MIN(00,01) //set min size to 1KB to avoid crash
$cx //end if
07 02 00 13 $w2 $w2 $w2 #CMD_END; // finally apply quality settings.
May be you'll find something like this in the modded drivers.
BTW, IMHO, synchronization with MXE also depends on cam_ss_sync value, but i can't check this =( I have no MXE.
Thanks for the info... I have checked the cam_ss_sync value... Yours, Kriomag are the same while Raiderski and Sarmad are the same as well... Yours and Kriomag have the values the same as K800i camdriver... am i right?
One more thing... What do we need to alter so that when we take a pic, the camera will record the shot instantly not about 2 secs where a little movement can alter the final pic? Does it rely on COMPRESSION too? Higher compression means the shot is taken faster? |
brazzuka's
Joined: Nov 14, 2007
Posts: > 500
From: South World-Antartida-Sweden
PM, WWW
|
MarkJason
u r using mxe-60? because they say the distance between the flash and the camera lens should be at least 55 mm in order to avoid red eyes. K750 with MXE-60 manages this fine, about 80mm. well k750=w810 same case the design of this lens in the same distance
Each environment each condition is assigned a response to the sensor environments conducive to use the flash mxe-60 figures of exposure and iso are other has to adjust the values and testing them in environments suitable to the time of exposure and are iso other values
Say for the K750 or W810 and MXE-60 happens to be mobile phone and it's accessory and not proper digicam, we never will get technical specifications about flash duration time and such self-evident facts but i trust you guys.
The flash shoot also with the environment and we must also synchronize the time of the sensor led the camera with the flash mxe-60 then for each environment and conditions features and conditions for the reflection of light is very important and each depends on the hardware and firmware will behave
[Non-flash photo: 1/20s, ISO 500, flash photo 1/15s, Iso 200 and exposure correction] maybe
I donīt know if these features r exactly ,have to test
information:
"bought my MXE-60 last summer while the firmware version R1L002 was the latest. That version could deliver both ExposureTime and ShutterSpeedValue on Exif data. 1/15sec and 1/16sec were the values. (Later firmware versions have dropped that ShutterSpeedValue) But the exposure time of the flash itself is much shorter, as the demonstrative test photos of my waving hand and rotating record players show clearly."
"Verdict: the camera does 1/15s but MXE-60 Xenon flash does it much much shorter...."
"You noticed something essential in low light photography. As you might know, these simple cameras can adjust the correct exposure only by exposure time and sensor sensitivity (film speed) because the aperture is fixed (2.8 on K750)."
"In normal mode the longest exposure time on K750 is 1/20s, in Night mode 1/5s. The highest ISO sensitivity is 800 (after latest firmware)."
"Photographers call lightning situations for Exposure Values, combination of the three above. K750 starts using it's longest exposure time at EV 6, while EV 4 is the darkest, where K750 still manage to deliver correct exposure. At EV 6 the sensitivity is 200, at EV 4 the max 800."
"Here some descriptions of such EV situations:
EV 4: Candle lit close-ups. Christmas lights, floodlit buildings, fountains, and monuments. Subjects under bright street lamps.
EV 5: Night home interiors, average light. School or church auditoriums. Subjects lit by campfires or bonfires.
EV 6: Brightly lit home interiors at night. Fairs, amusement parks.
The moment you want to add more exposure compensation, the only way K750 can obey is by increasing ISO beyound the normal 800 limit, up to 1600. With the MXE-60 mounted on, the output power of the flash is regulated instead.
It's worth opting for Night mode, but then the longer exposure time becomes a problem. Take a look at these examples of noise level in Normal mode vs Night mode, ranging from EV 4 to EV 7"
author: Mark_Q
Well We must explore the functions of the flash and add to the camera sensor do not know if all this that writing is a big silly perhaps a hypothesis or an idea
more information:
source
http://www.xs4all.nl/~wiskerke/artikelen/basic1.htm
http://www.fredparker.com/ultexp1.htm
|
MarkJason
Joined: Dec 03, 2005
Posts: 194
From: Bacolod City, Philippines 6100
PM |
Yes, I'm using the MXE-60 flash accessory... The main problem of it is out of sync in not well litted places... In very dark places they perform very well... I adjust the EV to make the flash stronger... but in some cases that doesn't help me... Sometimes adjusting the angle of the shot would help cause sometimes there's a thing that can block the flash causing the taken shot to be dark...
_________________
YoU tHinK yOu KnOW mE...
K750>W800 CID49 : Sarmad 5.8 camdriver
[ This Message was edited by: MarkJason on 2008-01-11 04:01 ] |
MarkJason
Joined: Dec 03, 2005
Posts: 194
From: Bacolod City, Philippines 6100
PM |
Guys, what will happen if i do this?
seq_set_prop_8_0=06 02 00 01 %0 53 #CMD_END
06 02 00 01 00 08 #CMD_END;
seq_set_prop_8_1=06 02 00 01 01 08 #CMD_END;
K750>W800 CID49 R1BC002 : Sarmad 5.8 camdriver / Hyper v6 + HyperPHF acoustic |
679
Joined: Oct 05, 2006
Posts: 174
PM |
On 2008-01-10 23:38:04, Kriomag wrote:
who uses high ISO ? you must be a masochist 
if you take picture with high iso the detail level are same as low as you would have taken this picture with 640x480 resolution and then resized it to 1632x1224 
Yes you are right, but not completely. I think masohist got pleasure taking picture during near 10s in ENM, trying be steady and breathless .
Realy with "$s0 3a" i got ISO 160, max exp 1s and good result even in night.
Problem for me is that i need '3a' only for ENM, not for EM to, but cant put "40" for EM and "3a" for ENM separately.
Maybe it is possible?
Thx. |
Kriomag
Joined: Dec 20, 2006
Posts: > 500
From: Poland
PM, WWW
|
On 2008-01-11 09:32:15, 679 wrote:
On 2008-01-10 23:38:04, Kriomag wrote:
who uses high ISO ? you must be a masochist
if you take picture with high iso the detail level are same as low as you would have taken this picture with 640x480 resolution and then resized it to 1632x1224
Yes you are right, but not completely. I think masohist got pleasure taking picture during near 10s in ENM, trying be steady and breathless .
Realy with "$s0 3a" i got ISO 160, max exp 1s and good result even in night.
Problem for me is that i need '3a' only for ENM, not for EM to, but cant put "40" for EM and "3a" for ENM separately.
Maybe it is possible?
Thx.
you got point  hehe, but i never take pictures with long exposure holding camera with hands i use selftimer function :]
It is posiible:
With this code You will have value 40 for EM and value 3a for ENM:
Change "$s0 3a" to:
"
$p2 07 <-- place value of property 7 in internal register 2
$c2 00 <-- if value of register 2 is 0 = normal mode is selected
$s0 40 <-- set register 0 value to 40 = best EM
$cl <-- if value of register 2 is other than 0 = night mode is selected
$s0 3a <-- set register 0 value to 3a - best (in your opinion) night mode
$cx <-- end...
"
check my v21.93 driver to get better understanding (now i use simplified EM/ENM/LedEM/LedENM code = only one short macro instead of 2 macros - THX Raider).
[ This Message was edited by: Kriomag on 2008-01-11 10:01 ] |
Kriomag
Joined: Dec 20, 2006
Posts: > 500
From: Poland
PM, WWW
|
On 2008-01-11 07:18:44, MarkJason wrote:
Guys, what will happen if i do this?
seq_set_prop_8_0=06 02 00 01 %0 53 #CMD_END
06 02 00 01 00 08 #CMD_END;
seq_set_prop_8_1=06 02 00 01 01 08 #CMD_END;
if you select black&white in effects menu the SPOT will be enabled, if you turn effects off also SPOT will be disabled.
BUT
with above code the effects function will not work, i suggest you change it like this (if you want other effects working correctly):
seq_set_prop_8=$s0 %0
$c0 00 06 02 00 01 00 08 #CMD_END
06 02 00 01 00 53 #CMD_END $cl
$c0 01 06 02 00 01 01 08 #CMD_END $cl
06 02 00 01 $w0 53 #CMD_END
$cx $cx;
with my code only black&white effect will not work (because its function is changed to SPOT), other effects selected in menu will work fine
[ This Message was edited by: Kriomag on 2008-01-11 10:21 ] |
Raiderski
Joined: Jul 03, 2006
Posts: > 500
From: Poland, Hell, Mountains
PM, WWW
|
you can also try this:
EM_MSS_APPLY=#EM_STATUS
$c1 00
// cut here everything and put:
#CMD(03,01)
$cl
$c7 00
$cl
#MSS_APPLY
$cx
$cx;
final pics with ISO160 and half exposure time of original EM
|
679
Joined: Oct 05, 2006
Posts: 174
PM |
It is posiible:
change "$s0 3a" to:
"
$p2 07 <-- place value of property 7 in internal register 2
$c2 00 <-- if value of register 2 is 0 = normal mode is selected
$s0 40 <-- set register 0 value to 40 = best EM
$cl <-- if value of register 2 is other than 0 = night mode is selected
$s0 3a <-- set register 0 value to 3a - best (in your opinion) night mode
$cx <-- end...
"
Kriomag, Thx
But it is for 21.93, right? May be it is possible to use this part as macro block? Bcs in 21.93 there are some places with "$s0 40".
[ This Message was edited by: 679 on 2008-01-11 10:08 ] |
679
Joined: Oct 05, 2006
Posts: 174
PM |
On 2008-01-11 10:58:17, Raiderski wrote:
you can also try this:
EM_MSS_APPLY=#EM_STATUS
$c1 00
// cut here everything and put:
#CMD(03,01)
$cl
$c7 00
$cl
#MSS_APPLY
$cx
$cx;
final pics with ISO160 and half exposure time of original EM
Raiderski, is your advise for my problem?
Thx. |
Kriomag
Joined: Dec 20, 2006
Posts: > 500
From: Poland
PM, WWW
|
On 2008-01-11 11:03:52, 679 wrote:
Wow. But it is for 21.93, right? May be it is possible to use this part as macro block? Bcs in 21.93 there are some places with "$s0 40".
here is my EM/ENM/LedEM/LedENM Macro:
EM=$p1 05 <-- place value of property 5 in internal register 1 (to check if picute quality is FINE)
$c1 01 <-- if value of register 1 is 1 then proceed with EM/ENM/LedEM/LedENM code:
$p1 0e <-- check if mxe-60 is disabled
$c1 00 <-- if register 1 has value 0 then external flash lamp is disabled
#READ(23,$r2 1 1)
$m0 1 $/0 28
$c0 00
$m0 1 $/0 03
$c0 00
$cl
$s0 40 <--set register's 0 value to 40 (for EM/ENM and LedEM)
$p2 07 $c2 01 $p2 0d $c2 01 $s0 3d $cx $cx (set register's 0 value to 3d only if LedENM is selected!)
$-0 r1 #CMD(04,$w0)
$cx $cx $cx $cx;
[ This Message was edited by: Kriomag on 2008-01-11 10:19 ] |
Raiderski
Joined: Jul 03, 2006
Posts: > 500
From: Poland, Hell, Mountains
PM, WWW
|
679
yep
|
679
Joined: Oct 05, 2006
Posts: 174
PM |
On 2008-01-11 11:22:03, Raiderski wrote:
679
yep
Raiderski, Kriomag
Thx a lot, will try. |
Randolph
Joined: May 21, 2007
Posts: 115
PM |
On 2008-01-10 20:06:13, Tomix wrote:
I see many of you change the cam modules... What is this cam module and where to get it and how to change?
You can buy CID36 Cam modules here:
http://cgi.ebay.de/ws/eBayISA[....]&ssPageName=ADME:X:AAQ:DE:1123
he ships very fast and has good quality cam modules! |
|
|
Posted: 2008-01-11 00:05
