Messages

My 600D transformed to humanoid, like this

[MSG added]

A: reproduce the issue

I tried A on my 600D, but nothing problem happen.
push shutter half way-> power on -> boot up and AF is working immediately
That's all.

MSG added
I just understand it. The normal canon firm is ignore CanonMenu and focus point moving when half shutter pressed.
right?

Then I try your autoexec.bin and I can see "0 0" and I can move focus position and open cannon menu when I pushed half shutter.
But I never see black screen in photo mode.

[600D audio autoexec.bin *BETA* Updated]

600D audio autoexec.bin *BETA* Updated
http://chirari.ddo.jp/ml/600Daudio/autoexec8.bin (need rename to autoexec.bin)
History
-Added effect mode control in Digital menu
-Completely split menu item for analog[gain,boost], add these into submenu.

Added control for effect mode. But only working "Notch filter". Because when camera standby,
all Equalizer parameter was reset by canon firm. 

Split contorol menu for Analog gain and boost. boost up is better for getting nice volume with less hiss-noise.
As scrax said befor, boost is lesser hiss-noise.
So It's a "gain+6&boost+25" is better sound than "gain+30&boostOFF"

Try it. You can hear very good sound

[MSG added]

Ah, Isee.
You may put msleep(500) between audio_configure() and playing wav.

MSG added
1%
I just understand, I was miss understanding your message.
And check codes, but already added msleep(500) in wav_play_ex()....
We need to check which is buffer(and inside data of buf) is prepared or not first.

Thankyou very much all testers.

@funkysound
v7's sound diffence made by a Equalizer off. When we turn on the equalizer with default equalizer paramers, the volume go to down a little.(and current recording sound is not natural sound. It's already customized by canon.)
We were thinking our overriding is turn off equalizer at all time. But I found bug on changing equalizer setting. Solved it and then we got little loud soud. So you may volume down and check sound quality.

@1%
Digital is working with no problem on my side.

@jonnyschanny @Rush
In my knowledge, some task is still working(deadlock) then it can't be shutdown.
In this case, you CAN'T see "Sensor cleanning" message. You must BATTERY PULL NEEDED.
Anyway, When it cannot reproduce on my side, I can't solve it.  and use v7.
If you face this issue again, please let me know.

Another thing.
1:Turn power to off.
2:displayed "Sensor cleanning" and finish shutdown.
3:Open the SD-card door.
4:read autoexec.bin (all cameras)
(Normally, it's a really short time. But reading broken autoexec.bin, LED is not finish flashing)

@SDX
Let's solve this bug together.

BTW, I'm using 600D autoexec.bin(make 600D) , then I got 6k bug. In addition, I was transport  platform/all/autoexec.bin. It's 1.7M. But I could transport over 250k. I forgot detailed value. But I can transport about 1.5M.
Ratio is almost same , so I think the code has bug.(loop condition had bug, I guess).

[600D audio autoexec.bin *BETA* Updated]

600D audio autoexec.bin *BETA* Updated
http://chirari.ddo.jp/ml/600Daudio/autoexec7.bin (need rename to autoexec.bin)
History
-merge with current repo
-reduce pop noise and responce up when setting audio chip.
-monitoring lauch timing issue solved(startup related) (@klangdrang reported)
-monitoring off is perfectly working.

Why don't you compile a bin for each camera?
Since it's not good to use the same card for different cameras it won't be a big issue if we had a single file for each DSLR.

I can't understand what you are advice to me .
What relation is existing about "solving PTP codes" and "each camera autoexec.bin" ?

Sorry for my poor English reading.

I don't wanna use SD-reader and , open the SD-card door.

https://bitbucket.org/miyake_t/magic-lanternptpdev/
Current repo's code and ptpcam combination can upload 95% of files correctly.
But it's will stop last 6k with error.(only 600D's autoexec.bin)
transferd 240k is correct values .(confirmed "od -x" and diff)


History and knowledge
-based on g3gg0's patch
-added libptp-chdk-win32(It's a GPL so we can redistribute with source)
-src/ptpcam.txt is described how ptpcam is working(how extending ptpcam by chdk guys).
-(solved)enum value is different ML and ptpcam
-(solved)current ptpcam code is not supported over 1000byte files to transfer
-(solved)current ML codes are not used callback function for receiving from USB.(If we dont use it, got hangup receive process)
-(solved)current ML codes not handle USB ack packet(Simply discarding now.)
*it's 12byte data adding each after part of USB_BULK_WRITE data.
-USB_BULK_WRITE is sending 500byte data .
-console_printf added for debugging


I'm coding for this code 1week . But I can't solved lask 6k issue. So please help me to find bugs in this code, if you interested in this.

Are you sure that it will affect clipping?
I think that if you get clipping sound with analog gain - you will get clipping even with applied "minus digital gain". Or am I wrong?

Does something different of analog and digital gain for final recorded volume?(Actually noise is different. )
I'm not expert of Audio.
Now we found only Digital gain is able to control LR separated.

And if you know good article of this thing. Please let me know URL.

@xaled
You can do by Digital gain LR.
But range width is tight.

Just added code for copy config file together. Not tested, someone test it please.

[@scrax]

Is it possible to solve problem with stuttering of audio in first seconds of record?
I thought that on 550D/60D there are no stuttering...

currently , I can't.


@scrax
Please add this picture and Headphone youtube to first post.

@nanomad
Are you telling me that is it's not enough. right?

In this time, this code doesn't need config file values(don't need to use CONFIG_INT).
Because, all submenu values are getting from actual AE_*.BIN files(name).

--------
Ah, I just understand it. Now this code has no handring config files.
You mean copy AE_600DA.BIN and AE_600DA.CFG together. right?
It's easy to adding codes , but now I'm writting PTP codes. So some one please help me to writting codes.

[600D audio autoexec.bin *BETA* Updated]

600D audio autoexec.bin *BETA* Updated
http://chirari.ddo.jp/ml/600Daudio/autoexec6.bin (need rename to autoexec.bin)
History
-Solved issue #15(taken picture preview in movie_mode)
-startup/preview response up.

Nothing any updates.
Because I'm making a X5(600D) audio function and "On camera bin selector" now.

I just added make file tweak for on/off "bin select" in Makefile.inc

I think all testing version of autoexec.bin must turn on this func. Then all testers will get happy when they bring testing firmware to venue.

How do you think?

@Rush
Thankyou

@wichmaster

Really nice work with this, thank you all developers! I have a question though. I tested version 0.4 and when I override the audio settings I still get the same noise as when recording with override: off. Is there something I'm missing or does these changes not affect the poor audio recording quality of the 600D?

The normal canon menu is using "mic vol","Mic boost", "Digital gain" combination with only single control bar. and these parameters are fixed ratio.
So it's time to find best combination ratio for getting lesser hiss-noise. But we already know Juiced-link is one of better solution for it.
it's up to you.

Basically our codes are only provide more controlling ability on audio settings.

[Nightly build 0.5 (test version)]

Nightly build 0.5 (test version)
http://chirari.ddo.jp/ml/600Daudio/autoexec5.bin
History
-meter sencitivity issue . may be solved

Maybe solved it. Please Please test this build


MSG added
I forgot to update version number string on this autoexec.bin....

[MSG added]

@klangdrang
Thank you for your testing.

1st meter sencivity thing. I will test it.
2nd monitor blackout thing. See this YouTube

MSG added
hmmmmmmmm...
It's a little difficult to finding reason for it.
Actually cpu is a little high load, then meter_task is slow down.But I can't find the reason yet.

Thank you. It's not my specialty part. I just learned it.
I mean only overview of  loading style.

Ah, I see, Now I clearly understand what you are thinking.
Thank you for explaining.
First, I imagine linux micro-kernel architecture.
Architecture is similar to linux micro-kernel. But objective is different.

@g3gg0
I think
a) plugin architecture will cover big size autoexec.bin issue.(But it's good at increasing a capability)
bc) uncompress need more time? and autoexec.bin reading is not so slow now. and ROM selecter need a timeout like a linux grub or lilo. So more time will need boot sequence. I guess

Please let me know bc) things.

On the other hand, your idea have no risk to change autoexec.bin. And It's most safety. Also ROM dumper is attractive.

My function is really compact and we can be default hidden, then user not get a confusing. I guess advanced user will use it  until you create boot loader function.

I think now we can use combine both ideas

Good idea, now I can load a bunch of different bins without so much card swapping.

Yes, me toooooooo. Keep our SD card door

Just remember that I forget to implement "no AE_ files" exception.
One more thing, this extension need a supported this function on all installed autoexec.bin. Then we can return back to previous autoexec.bin.

Finally, Is this implementation need to change a plugin style?  If so, all autoexec.bin only need to enable plugin function.