Messages

@funkysound
Thank you for your comment. I hope your work successfully finished.

Thanks johndb.
Does any other problem available??? Feel free to post any bugs. and you can feel free to ask questions.


Only 7 peoples tracking the updates.

Code Select Expand

[root@chirari miyake]# cat /var/log/httpd/access_log | grep autoexec.bin | wc
     76    1493   16559
[root@chirari miyake]# cat /var/log/httpd/access_log | grep autoexec2.bin | wc
     25     538    6641
[root@chirari miyake]# cat /var/log/httpd/access_log | grep autoexec3.bin | wc
      7     151    1855
[root@chirari miyake]# cat /var/log/httpd/access_log | grep autoexec4.bin | wc
      8     160    1963


http://www.magiclantern.fm/forum/index.php?topic=2032.0

come here and find newest autoexec.bin.

Now I implemented on camera autoexec.bin selecter.

Situation:
1: usually using ML2.3 release
2: added new function or solved bug at new beta autoexec.bin
3: installed new one , and forget it.
4: bring camera to venue for shooting
5: ** new bug or problem found at veneu. also no PC situation**
6: ===>  on camera selecter is good!!!

https://bitbucket.org/miyake_t/magic-lanternselectautoexec


It's tested on my 600D and working fine.
this code is:
1: browse SD card root and find "AE_" prefix files.
2: add AE_ files to "Select bin" submenu.
3:when push bin name in submenu,  copy original file to BIN.TMP file.
4: remove autoexec.bin and rename BIN.TMP to AUTOEXEC.bin

I think the critical point only 4. and 4 is really short time, so I think it has no critical.

If you interested in "select bin" please try and test it.

[MSG addedNightly build 0.4]

@johndb
Thanks , Found one more problem. Now solving and testing.

MSG added
Nightly build 0.4
http://chirari.ddo.jp/ml/600Daudio/autoexec4.bin
History
-solved override exception handring

[Nightly build 0.3 is out]

Nightly build 0.3 is out
http://chirari.ddo.jp/ml/600Daudio/autoexec3.bin
History
-solved taken picture preview on shoot mode
-solved recording stop issue
-added msg when overridden.

Please test it.

johndb and 1%

Thank you for your advice. added NotifyBox() when finish overriding.

Also I found one more bug.
https://bitbucket.org/miyake_t/magic-lantern600daudio/issue/12/recording-stop
But now , already solved it I guess.

@jhondb
Please check on next 0.3 version. I will upload sooon.

I'm now investigating gain and boost values.
See this.
http://chirari.ddo.jp/ml/?p=934#more-934

Now confusing what is best method to change a volume with gain and boost values........

I have been doing some record testing and find that there is a gap of audio for about a second immediately after pressing the record button.

It's actually overriding.   Now we can only overriding only after starting record.
see this

@3ao
Thanks. If you find problems, let me know .

I had no complaints. I hope people are reading threads when downloading the bins, I would. I use the bin I compile day to day. But I don't always shoot audio because I'm testing bit rates.

@1%
This audio functions are based on your knowledge. And now I got baton from you. I will make a C code and maintenance it.
You may use your specialty for bit rate and 4Gig limit things are most better.

Tested Beta .2 and all functions seem to be working! Recording and Monitor work fine.
The Wind Filter effect is very subtle. Possible have a sub menu with cutoff frequency, roll-off slope, and -gain level?

Push "Q" !

I found one more bug in shoot mode.
When we turn overridden audio, taken picture preview is not working .

I guess, easy to solve it.  I think it will solved on Build version 0.3.

@scrax
I think scrax and 1%'s confirmation is most better. But I know you two are busy now.
So I think that a little different of testers report and your report, But testers report is helpful in current situations.

I thought  you and 1% are good work for this part. and I don't need want to establish a position of superiority in this part.
Just only I want to "quick development" and "smart development".

quick means a, we are not huge company, opensource software development project. Our footwork is most flexible. I think we should not do same thing with huge company. (a lot of allowing from company ) It means a slow down the development speed.

smart means , .,,  we are sharing code on mercurial. and a lot of coding style existing.
I just only want to coordinate for  best usage of mercurial and to make a efficient codes.

However, I know that my English may be  poor.  I think I couldn't tell you all of my thought ....
And If you and 1% got bad feel from me, I'm sorry for it.

[Testers are also our development team members.]

I'm totally misunderstanding our relations. Testers are not customer. Their are also volunteer like us.
We developer is volunteer too.
So I don't need to think customer impact issues such as a normal software development.
Testers are also our development team members.
 
So I will upload more quickly , before all developer confirmed new build .

Nightly build 0.2 is out
http://chirari.ddo.jp/ml/600Daudio/autoexec2.bin
History
-added Shortcut support Audio control
-Digital gain mute is displayed -100 dB now
-Solved Monitoring frees issue
-Solved Monitoring high level noise issue

I think more test needed in monitoring. Please check it.

[MSG added]

Also if Override Setting is OFF and you switch headphone OFF you will have noise probably, i see the bar full red.

Maybe solved it. Please check it.

And, hangup issue was reproduce my 600D. and I understand the reason. But thinking now. So time to solve it.

MSG added
Also hangup issue was gone.


-How to reproduce.
Override on , monitor on
1: connect/disconnect AV cable
2: finally keep connected AV cable
3: monitoring turn off

Then, the audio_monitoring_update() is not updated correct status.  Current code is timing sensible.
So I changed to delayed update .

[Cought hangup]

Cought hangup
Also this video will show behavior of AudioMoniter ON/OFF

volume function thing.
Oh really?
Canon menu is changing
    1:analog gain to max
    2:mic boost to max
    3:digital gain LR to max
So I implemented 1&2. If you said correct thing , we can get more clear sound by our ML audio menus. We don't need to use volume level 1.
Great thing.

full red thing
OK , If you reproduce it. Get regdump!
Then we are easy to solve it.

Anyway, 3am in JP, Good night.

Problem 2 is a bug in switching off monitor maybe, will look at it.

I think Problem 2 is also correct thing.
If you turn off monitor, LCD output will move to RCA yellow. So you can't see LCD .
Then you can pull out AV cable , you can see LCD again.

Also, You may blind touch the Trash->SET.
It means a
1: ML menu open
2: monitor trun on(because ML menu remember the position of last things.)

So please confirm, Problem2 and pull out AV cable. And then monitor turn on and push in the AV cable.
Also you can check push the REC button when your LCD off.  You can see SD access lamp. Therefore you can check actually camera is hangup or not.

Anyway, Thankyou for your report.

You may try to find best setting your self.
First, you may set all Digital values to 0.
Touch only "Analog gain" .

I guess, if you can't record any sound in recording, you had miss taken in input select settings.
check it.

Did you switch on the "Audio override" ?
and analog gain or digital gain setting is correct values?

Code Select Expand

# cat /var/log/httpd/access_log | grep autoexec.bin | wc -l
32


2 Known issues are already solved next release ver.0.2 .

How about it?

VMware ESX is great!

Anyway, I think a start-up splash screen is a little bit un-readable , I'm tunning now.
I will show you by you tube. check it.

[MSG added]

@ miyake
If you can compile without -mlong-calls I think that after 2.3 release you can open a new post asking for testers where to post the autoexec.bin

64bit arm gcc need a mlong-calls. main repo doesn't use it. So I moved to 32bit dev environment now. So I don't need mlong-calls.

Anyway, I can't follow your work. Where you push something?

MSG added
Ah, I see. you pushed your repo.  And what do you think how to use it on testers? I can't find autoexec.bin anywhare.

MSG added2
Why you pushed your repo? You can directory push my repo.  I can't understand it's reason. You make a merge work to me.
And, I can make autoexec.bin when I do "make 600D". So we don't need limitation code for another cameras. we also manage those limitation codes until  merge to  main repos.
One more , your order is  checkout your repo and compile it and finally release autoexec.bin , right?
Let me know your considerations.

MSG added3
scrax: Sorry for my confusing, merge is easy way, on bitbucket web functions. Made a pull request myself and accept it.
I can ready to make it.

[MSG added]

Ah, I see Thanks for your confirming.
Then I will add to NotifyBox() and it will show "600D audio test release" on startup.

MSG added
pushed.