| Author |
Number1 4.7 FINAL, K770&T650 camdriver |
nebraska
Joined: Jan 01, 2008
Posts: 241
PM |
hey cool we have a 2nd programeer in da place 
Could you explain what are:
3. Changed watchdog timer to 255.
4. Improved WB range like a SE but with small changes.
thanks!
| |
|
nebraska
Joined: Jan 01, 2008
Posts: 241
PM |
On 2008-03-06 21:16:53, number1 wrote:
maybe the video fps is cauing problems with the sound sync, a couple more test version with increased compression
http://www.mediafire.com/?7t0hw5fzydb
also has any1 tried the night mode, or night landscape yet???? they should both be lighter with less noise.
hi number1
I've just tested your new drv (vers1), quality of videos is still better than beefore (good thing!) but the delay between image&sound is worse!
It is annoying, because pic quality is very good
|
sp4ubw
Joined: Mar 08, 2008
Posts: 5
PM |
Yes of course:
this is first section
//SP4UBW values:
cam_ss_jpeg_buf_size_1=100000; //1MB
cam_ss_jpeg_buf_size_2=100000; //1MB
cam_ss_jpeg_buf_size_3=180000; //1.5MB
cam_ss_jpeg_buf_size_4=200000; //2MB
cam_ss_jpeg_buf_size_5=200000; //2MB
cam_ss_jpeg_buf_size_8=200000; //2MB
cam_watchdog_timeout=FF; // time for watchdog to timeout after recivied frame "DC"
cam_post_processing_11 = 1;
cam_post_processing_19 = 1;
cam_post_processing_20 = 1;
This is a time for watchdog timer to reset camera if receiving frame is to slow.
Second section:
Original SE:
seq_set_prop_0_0 = ;
seq_set_prop_0_1 = ;
seq_set_prop_0_2 = ;
seq_set_prop_0_3 = $p4 10
$c4 07 #WR_REG(0E, 86)
$cl #WR_REG(0E, 86) //-2.0
$cx ;
seq_set_prop_0_4 = $p4 10
$c4 07 #WR_REG(0E, 86)
$cl #WR_REG(0E, 85) //-1.7
$cx ;
seq_set_prop_0_5 = $p4 10
$c4 07 #WR_REG(0E, 85)
$cl #WR_REG(0E, 84) //-1.3
$cx ;
seq_set_prop_0_6 = $p4 10
$c4 07 #WR_REG(0E, 85)
$cl #WR_REG(0E, 83) //-1.0
$cx ;
seq_set_prop_0_7 = $p4 10
$c4 07 #WR_REG(0E, 84)
$cl #WR_REG(0E, 82) //-0.7
$cx ;
seq_set_prop_0_8 = $p4 10
$c4 07 #WR_REG(0E, 83)
$cl #WR_REG(0E, 81) //-0.3
$cx ;
seq_set_prop_0_9 = $p4 10
$c4 07 #WR_REG(0E, 02)
$cl #WR_REG(0E, 00) //0
$cx ;
seq_set_prop_0_a = $p4 10
$c4 07 #WR_REG(0E, 03)
$cl #WR_REG(0E, 01) //+0.3
$cx ;
seq_set_prop_0_b = $p4 10
$c4 07 #WR_REG(0E, 04)
$cl #WR_REG(0E, 02) //+0.7
$cx ;
seq_set_prop_0_c = $p4 10
$c4 07 #WR_REG(0E, 05)
$cl #WR_REG(0E, 03) //+1.0
$cx ;
seq_set_prop_0_d = $p4 10
$c4 07 #WR_REG(0E, 06)
$cl #WR_REG(0E, 04) //+1.3
$cx ;
seq_set_prop_0_e = $p4 10
$c4 07 #WR_REG(0E, 06)
$cl #WR_REG(0E, 05) //+1.7
$cx ;
seq_set_prop_0_f = $p4 10
$c4 07 #WR_REG(0E, 06)
$cl #WR_REG(0E, 06) //+2.0
$cx ;
//SP4UBW values:
seq_set_prop_0_3 = $p4 10
$c4 07 #WR_REG(0E, 86)
$cl #WR_REG(0E, 86) //-2.0
$cx ;
seq_set_prop_0_4 = $p4 10
$c4 07 #WR_REG(0E, 86)
$cl #WR_REG(0E, 85) //-1.7
$cx ;
seq_set_prop_0_5 = $p4 10
$c4 07 #WR_REG(0E, 85)
$cl #WR_REG(0E, 84) //-1.3
$cx ;
seq_set_prop_0_6 = $p4 10
$c4 07 #WR_REG(0E, 84)
$cl #WR_REG(0E, 83) //-1.0
$cx ;
seq_set_prop_0_7 = $p4 10
$c4 07 #WR_REG(0E, 83)
$cl #WR_REG(0E, 82) //-0.7
$cx ;
seq_set_prop_0_8 = $p4 10
$c4 07 #WR_REG(0E, 82)
$cl #WR_REG(0E, 81) //-0.3
$cx ;
seq_set_prop_0_9 = $p4 10
$c4 07 #WR_REG(0E, 01)
$cl #WR_REG(0E, 00) //0
$cx ;
seq_set_prop_0_a = $p4 10
$c4 07 #WR_REG(0E, 02)
$cl #WR_REG(0E, 01) //+0.3
$cx ;
seq_set_prop_0_b = $p4 10
$c4 07 #WR_REG(0E, 03)
$cl #WR_REG(0E, 02) //+0.7
$cx ;
seq_set_prop_0_c = $p4 10
$c4 07 #WR_REG(0E, 04)
$cl #WR_REG(0E, 03) //+1.0
$cx ;
seq_set_prop_0_d = $p4 10
$c4 07 #WR_REG(0E, 05)
$cl #WR_REG(0E, 04) //+1.3
$cx ;
seq_set_prop_0_e = $p4 10
$c4 07 #WR_REG(0E, 06)
$cl #WR_REG(0E, 05) //+1.7
$cx ;
seq_set_prop_0_f = $p4 10
$c4 07 #WR_REG(0E, 06)
$cl #WR_REG(0E, 06) //+2.0
$cx ;
//NUMEBR1 values:
//seq_set_prop_0_0 = ;
//seq_set_prop_0_1 = ;
//seq_set_prop_0_2 = ;
//seq_set_prop_0_3 = #WR_REG(0E, 86) ; //-2.0
//seq_set_prop_0_4 = #WR_REG(0E, 85) ; //-1.7
//seq_set_prop_0_5 = #WR_REG(0E, 84) ; //-1.3
//seq_set_prop_0_6 = #WR_REG(0E, 83) ; //-1.0
//seq_set_prop_0_7 = #WR_REG(0E, 82) ; //-0.7
//seq_set_prop_0_8 = #WR_REG(0E, 81) ; //-0.3
//seq_set_prop_0_9 = #WR_REG(0E, 00) ; //0
//seq_set_prop_0_a = #WR_REG(0E, 01) ; //+0.3
//seq_set_prop_0_b = #WR_REG(0E, 02) ; //+0.7
//seq_set_prop_0_c = #WR_REG(0E, 03) ; //+1.0
//seq_set_prop_0_d = #WR_REG(0E, 04) ; //+1.3
//seq_set_prop_0_e = #WR_REG(0E, 05) ; //+1.7
//seq_set_prop_0_f = #WR_REG(0E, 06) ; //+2.0
In the NUMEBR1 table values are still the same in all modes.
Originally depend at sensor and in my driver too but witch smaller changes to linearity this parametres.
That's all
Nebraska try to change this walues:
cam_post_processing_11 = 1;
cam_post_processing_19 = 1;
cam_post_processing_20 = 1;
enter on the beginning 1 into place 2, Nice effect 
[ This Message was edited by: sp4ubw on 2008-03-12 12:18 ] |
number1
Joined: Sep 12, 2007
Posts: > 500
From: UK,kent,Sittingbourne
PM |
the really big buffers aren't really needed the phone will never take a 2mb photo, i restored the old exposure property to stop doc mode over exposing, also adding more sharpness doesn't work well on this phone. |
sp4ubw
Joined: Mar 08, 2008
Posts: 5
PM |
Aha, i'm increased buffer at the begiining and and so stayed. Buffer from You driver is OK.
[ This Message was edited by: sp4ubw on 2008-03-12 12:27 ] |
number1
Joined: Sep 12, 2007
Posts: > 500
From: UK,kent,Sittingbourne
PM |
increasing the buffers won't make much difference, i think the idea with buffers is that the photo fits in them, the max file size is 908kb i think so really only a 908kb buffer is needed. |
nebraska
Joined: Jan 01, 2008
Posts: 241
PM |
Nebraska try to change this walues:
cam_post_processing_11 = 1;
cam_post_processing_19 = 1;
cam_post_processing_20 = 1;
enter on the beginning 1 into place 2, Nice effect
hi
thank you for your explanations
Is it a modification of the driver to solve my pbl of delay in videos?
I'm afraid I'm not an xpert.. Which part have I to modify??
PS: strange that no other guy noticed this delay on his t650
|
number1
Joined: Sep 12, 2007
Posts: > 500
From: UK,kent,Sittingbourne
PM |
cam_post_processing_11 = 1; <<cam_post_processing_19 = 1; <<< videotelephony
cam_post_processing_20 = 1; << |
nebraska
Joined: Jan 01, 2008
Posts: 241
PM |
these values are already in the driver...
cam_watchdog_timeout=DC; // time for watchdog to timeout after recivied frame
cam_post_processing_11 = 1;
cam_post_processing_19 = 1;
cam_post_processing_20 = 1;
so i don't understand what to do exactely.. (replace 1 by 2???)
|
number1
Joined: Sep 12, 2007
Posts: > 500
From: UK,kent,Sittingbourne
PM |
try replacing
cam_watchdog_timeout=DC; //220
with
cam_watchdog_timeout=FF; //255 |
nebraska
Joined: Jan 01, 2008
Posts: 241
PM |
ok I've just put FF, it is worse I think...veery big delay
anything else doc? |
number1
Joined: Sep 12, 2007
Posts: > 500
From: UK,kent,Sittingbourne
PM |
Try DA |
nebraska
Joined: Jan 01, 2008
Posts: 241
PM |
sorry it doesn't change anything....
around 0,5 to 1 sec delay |
number1
Joined: Sep 12, 2007
Posts: > 500
From: UK,kent,Sittingbourne
PM |
ok have 1 last try use value A5 |
nebraska
Joined: Jan 01, 2008
Posts: 241
PM |
still the same...
is it the only parameter which controls delay?
if you want to see this delay, here is a little video:
http://img532.imageshack.us/my.php?image=mov00938xx4.flv | |
|
Access the forum with a mobile phone via esato.mobi
|
Posted: 2008-03-12 12:57
