Messages

I found 2 PDFs.
1st one is korean, and only 4 pages.

2nd one is 78K0R/Kx3

Already 1% had a English document?

If you don't have , I'll try to transrate this document to wikia with my poor English.

Cannot be read only... camera sets it... no max value because its a power control register.

I see, Read only is just my guess. forget this.

I just looking lapis-semiconductor web site in Japanese lang.
And checking technical question form.
But it for customer?only,, because it need a "describe product name" and "plan for volume production"....
I guess they are not give us the document. maybe,

Oh sorry, 0x10000 is binary. not HEX....

In the alsa file the registers are even, in camera they are odd but the same thing. We have same value in the even registers but for some reason it doesn't change.

audio_ic_write( ML_PW_SPAMP_PW_MNG | 0xff ); // power speaker amp FF, BF no difference: is amp power 1f is speaker bf is headphone or "AV"
audio_ic_write( ML_PW_LOUT_PW_MNG | 0xff ); // Line out PM to all ON ... I think this is line out amp: same deal?

audio_ic_write( ML_PW_DAC_PW_MNG | 0x02 ); // power up dac  : Dac comes on but I don't think audio is being amplified at all, very very quiet.

These have no maximum value definition in alsa driver. So I guess it's READ ONLY register.

For windows users:
You do not forget to execute "libusb-win32-bin-1.2.6.0\bin\inf-wizard.exe"
If you do not do this command, you can not see USB device from ptpcam.

I'm really confusing... Sorry for can't help you.

In alsa driver  I fond

Code Select Expand


#define DVOL_CTL_DVMUTE_ON       BIT(4) /* Digital volume MUTE On */
#define DVOL_CTL_DVMUTE_OFF      0      /* Digital volume MUTE Off */

static int ml26124_mute(struct snd_soc_dai *dai, int mute)
{
        struct snd_soc_codec *codec = dai->codec;

        if (mute)
         snd_soc_update_bits(codec, ML26124_DVOL_CTL, BIT(4),
         DVOL_CTL_DVMUTE_ON);
        else
         snd_soc_update_bits(codec, ML26124_DVOL_CTL, BIT(4),
         DVOL_CTL_DVMUTE_OFF);
        return 0;
}


So I think , we only to set this bit to 1 when we need to mute like this.

Code Select Expand

audio_ic_write( ML_DVOL_CTL | 0x10000);

But your xmuteav() is a lot of audio_ic_write(). and in your xmuteav() had this:

Code Select Expand

audio_ic_write ( 0x6908 ); // Set Dvol Stuff to "Play"

This means

Code Select Expand

audio_ic_write( ML_DVOL_CTL | 0x1000);

I found matching item for this in alsa driver

Code Select Expand

SOC_SINGLE("Digital Volume Fade Switch", ML26124_DVOL_CTL, 3, 1, 0),

You descrived "Set Dvol Stuff to "Play"" but it means Fade Switch will switching to ON.

How did you know those register values in debug.c?

Just wrote :
http://magiclantern.wikia.com/wiki/600D/Audio#Alsa_driver_analyzing

for easy to understanding.
I will check your debug.c

And I found this on ml26124.h

Code Select Expand


        /* Record/Playback Running Control Register */
        if (substream->stream == SNDRV_PCM_STREAM_PLAYBACK)
         snd_soc_update_bits(codec, ML26124_REC_PLYBAK_RUN, 0x2, 0x2);
        else
         snd_soc_update_bits(codec, ML26124_REC_PLYBAK_RUN, 0x1, 0x1);


It this a something help to understanding rec/play mode handling?

[anybody not guaranteed . At your own risk]

I'm understanding that is ML advantage is not changing boot sequence constantly.
Most cell phones hack is every time build boot sequence , So the brick risk is very high.
But ML change a boot sequence only one time which is installing.

So my understanding:
It's nothing to brick which is broken boot sequence installing with  changing only autoexec.bin .
BTW Cannon firmware does not solve invalid NVRAM config. So If we write a invalid config value from custom autoexec.bin , Canon firmware will not boot.(but recovery method available)

Anyway, anybody not guaranteed . At your own risk when you built your own built.
So you do not take a this risk. Use release version of ML

I'm not perfect understanding.
But now I can use ptp on my win 7 x64.

Let me confirm what you need:
Collect a memory value for each modes(normal,recording, play, palying)


First testing .

DAC (digital->analog) (550D and 600D, bcoz handled by tx19a I think)
StopASIFDMADAC=
0xC05000B0 <- 0
0XC092020C <- 0
-

normal:
<conn> m 0xC05000B0 16
c05000b0  24 00 00 00 00 00 00 00  07 00 00 00 00 00 00 00  |$...............|

recording:
<conn> m 0xC05000B0 16
c05000b0  24 00 00 00 00 00 00 00  07 00 00 00 00 00 00 00  |$...............|

play mode but not play:
<conn> m 0xC05000B0 16
c05000b0  24 00 00 00 00 00 00 00  07 00 00 00 00 00 00 00  |$...............|

playing :
<conn> m 0xC05000B0 16
c05000b0  27 00 00 00 00 00 00 00  07 00 00 00 00 00 00 00  |'...............|


Are these correct understanding? Is it a helpful for you?

Good night

@1%

Did you write document which is clear thing?
I just want to help you mapping(confirm) register value and Alsa driver's value.
But I don't know which one is clearly understanding.

I created a wikia account and let me know which part is confirmed in source code.
I wil write to our understanding to wikia.

deleted

@Alice,

Screw is mm. not inch in my country. But the camera is inch....
So it's hard to find 1/4 inch screw and nat....

orz.. OTZ...

If we can record overlays. we can easy to debug .Because  the value is too fast to showing.
Slomo will help to understand , relation of the debug value and real live view display such as focus, expo, and so on.
One more thing, If the problem is not reproduce our side, but we can see real problems from recorded files.

Anyway, It's really hard to shoot live-view from another camera.
My arm had a limit to hold those two cameras.

Please tell me how to shoot live view from another camera with valiangle(lol

Current movie AF status.

Focus stepping part is not optimized yet.
But a little bit good to suspend focus action when come into focus.
Sometime you can see STOP LED.

one focus action with one LED brink.

and current good parameter for me is:
noise 2
aggre 8
thresh 4

Today's experiment result

PROP_LV_FOCUS_DATA has 8 int value

buf[0] // has dynamic value but ?
buf[1] // has dynamic value but ?
buf[2] // higher dynamic value
buf[3] // lower  dynamic value
buf[4] // always same value on 600D
buf[5] //always zero
buf[6] //always zero
buf[7] //clocking? almost 0 but sometime had a value

buf[2] and buf[3] values are moving when we touch focus ring.
buf[2,3] is higher value when I got good focus.
So I added focus threshold value in menu. The thresh value from 10000-19000.
threshold evaluation code will do the "stop focus" action when the buf[2,3] is higher than specified value.

Then sometime AF is suspend when I got focused . But the buf[2,3]'s value is depend on the scene. It means a ISO, material, how far.  So I need one more function for calculating threshold dynamically.

P.S. Let me know how to say the situation which is "focus is perfect" in English.
I'm using "focused", is it correct?   Can I use "focus peek" for this?

MEMO
??
miss the point
?
out of focus
??
defocused image

?
defocus
?
?
refocus
??
be brought to a focus
come into focus?

in focus

msg_queue imported.
and a little bit step up.

movie_af=1 : HOLD=>working. focus unstable, had "Focus error" . * Crash free now!"
movie_af=2 : Cont =>same as =1
movie_af=3 : CFPk =>working. focus unstable

focusunstable = (not stop when focus is almost good distance)

I can't see crash screen when I select 1 and 2.

Thanks
I almost understood what you are explaining.

I already knew 1st sentence when I read code and some web document.
2nd is very helpful for me.

my working is here
https://bitbucket.org/miyake_t/magic-lantern-miyake/overview

Anyway, already sleepy today.  Envy European and American peoples. We Japanese have a lot of time difference. orz...

Today's experiment result

movie_af=1 : HOLD=>not working
movie_af=2 : Cont=>not working
movie_af=3 : CFPk=>working. but still not unstable(not stop when focus is almost good distance)

movie_af=1and 2 is got "Focus error". focus_done is not comming specified waiting time.
I guess, more dependency needed when we use LensFocus().

@vBlack
Never mind.
I am newbie too.

help me.
I'm finding to PROP_LV_FOCUS_DATA's meaning.
It has 8 integer blocks. Where describe it means.
Thanks

1%
I just testing my movie AF codes.
I'm using sigma 30mmF1.4 and 18-200mm. These are extremely noisy(lol
So basically speed is not so bad, but we can't use sound with movie AF without extra audio recorder or separated microphone.

I've lost my move af code yesterday by my miss operation.Now I recover and just adding few codes.

I just understood old one is not unified.
So it's not a easy to fit current unified codes.

Currently, the code is not working with unified code.(hangup)
I just disable some lines now, then I can test few movie AF functions.

I guess YouTube video is most better case, and author hide a bad behavior.
Need more codes for stable operation, I think. So it's disabled now.

Alex-san

hmm, I see.
It's long term project for me.
I need to read and understand focus.c and focus_peak function.

If I made a good code , I will post the diff file to this community.

Thanks.