Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.


Messages - miyake

Pages: 1 2 [3] 4 5 ... 14
51
Nightly Builds / Re: 600D Audio TEST release - 2.3 based
« on: September 10, 2012, 07:20:25 PM »
OK! catch it!

audio05 is HPF on and just startup
audio08 is just recording.

Code: [Select]
$ diff /cygdrive/i/ML/audio05.LOG /cygdrive/i/ML/audio08.LOG
18,19c18,19
< ML_MIC_IN_VOL 10
< ML_MIC_BOOST_VOL1 10
---
> ML_MIC_IN_VOL 37
> ML_MIC_BOOST_VOL1 20
34c34
< ML_FILTER_EN 03
---
> ML_FILTER_EN 83
36c36
< ML_DVOL_CTL_FUNC_EN 00
---
> ML_DVOL_CTL_FUNC_EN 2e
41,42c41,42
< ML_EQ_GAIN_BRAND0 e7
< ML_EQ_GAIN_BRAND1 e7
---
> ML_EQ_GAIN_BRAND0 dd
> ML_EQ_GAIN_BRAND1 dd
46,54c46,54
< ML_HPF2_CUTOFF 07
< ML_EQBRAND0_F0L 00
< ML_EQBRAND0_F0H 00
< ML_EQBRAND0_F1L 00
< ML_EQBRAND0_F1H 00
< ML_EQBRAND1_F0L 00
< ML_EQBRAND1_F0H 00
< ML_EQBRAND1_F1L 00
< ML_EQBRAND1_F1H 00
---
> ML_HPF2_CUTOFF 00
> ML_EQBRAND0_F0L 0d
> ML_EQBRAND0_F0H db
> ML_EQBRAND0_F1L 0c
> ML_EQBRAND0_F1H 1b
> ML_EQBRAND1_F0L 6d
> ML_EQBRAND1_F0H 08
> ML_EQBRAND1_F1L 41
> ML_EQBRAND1_F1H ed

Override failed. However, It's late night , I will write code tomorrow. Good night!

52
Nightly Builds / Re: 600D Audio TEST release - 2.3 based
« on: September 10, 2012, 05:55:50 PM »
I'm testing only WAV recording.
Anyway, now I can't compile your repo. Are you using gcc 4.7 linaro?
Give me your newest bin.

53
Nightly Builds / Re: 600D Audio TEST release - 2.3 based
« on: September 10, 2012, 04:54:34 PM »
Quote
but first start problem isn't gone.
I can't reproduce it.......

54
Nightly Builds / Re: 600D Audio TEST release - 2.3 based
« on: September 10, 2012, 03:29:42 PM »
https://bitbucket.org/miyake_t/magic-lantern600daudio

f7924146caf9
Now we don't need to use override_audio_task()!!!!!,It means audio_configure() is enough faster!
Then record start/stop has no delay to override!!!

55
General Help Q&A / Re: L: ext (external) and R: int (internal)
« on: September 10, 2012, 08:04:21 AM »
I'm 600D audio developing now.
Maybe I can do this request (I'm not checked another cameras, Because chip-set is different).

BTW, You can do this request on post processing.  Why you need to this on camera?

56
Nightly Builds / Re: 600D Audio TEST release - 2.3 based
« on: September 10, 2012, 05:22:42 AM »
hmmm, I used your binary. But it's correctly override at all times.
I checked volume and watch meters.

The Canon volume is 1(most small).
Then I changing our gain+boost . It's correctly override volumes at 1st time.


57
Nightly Builds / Re: 600D Audio TEST release - 2.3 based
« on: September 09, 2012, 05:10:20 AM »
Quote
Do you notice it change volume when starting sound recorder first time? It doesn't start running override until the 2nd wav is recorded. But works first time for movie wav for some reason. I added some more override audio . beep.c but it still doesn't override first time.

hmm, I can't confirm this problem on my repo. Volume setting is correctly overridden.
Let me clarify your confirm method.
1: Turn on the camera
2: record wav  <--- can't override

Is this a correct?

58
Nightly Builds / Re: 600D Audio TEST release - 2.3 based
« on: September 08, 2012, 08:42:49 PM »
meter and audio_level tasks are 18 is best. and override is 17.

Oh, tragic-lantern has some limitations? If so, my repo has same issue.
Then we should use override_audio_task(). Then it func will override when started recording.
I just  inspiration hit me.

59
Nightly Builds / Re: 600D Audio TEST release - 2.3 based
« on: September 08, 2012, 07:25:28 PM »
I'm tested with your tragic-lantern binary.
So I also used your stereo codes. And I can't find problems....

60
Nightly Builds / Re: 600D Audio TEST release - 2.3 based
« on: September 08, 2012, 04:58:30 PM »
I got it.
First I will try to reproduce it.

Can I confirm one thing?  Your audio recording means stereo WAV recording, right?

MSG added
Some problem fixed, and pushed your repo. But I can't reproduce it.
I'm testing 1KHz sound generated from my PC and insert mic input on my 600D.
Then testing HPF on/off but it has no problem. actually, I got distortion when input volume really high(red zone).
But I can't find any difference of HPF on/off.....

I think, beachtech input is already had a distortion(check your volume settings on your beachtech.),,,, Just my guess.

61
General Development Discussion / Re: [MERGED] Makefile with user prefs
« on: September 08, 2012, 09:59:11 AM »
@nanomad
Anyway, Thankyou , I'm deleted all difference  in Makefile.inc on our 600D audio repos.


62
Nightly Builds / Re: 600D Audio TEST release - 2.3 based
« on: September 08, 2012, 08:42:58 AM »
hmm, I still not understanding what you are thinking a problem.
 -Are you investigating a hiss noise?
 -What is problem with HPF ?

I already investigating hiss noise.
http://chirari.ddo.jp/ml/?p=934

Amplifer generated noise is really small. It's depend on which mic we will use.
So I think, We don't need to find best setting for end users.
May be forum users will find best parameters for it.

However , If HPF has some bugs, We must solve it. So please describe detail of HPF issue.

63
General Development Discussion / Re: [MERGED] Makefile with user prefs
« on: September 07, 2012, 06:42:12 PM »
Code: [Select]
%.o: $(SRC_DIR)/%.c
        $(call build,CC,$(CC) $(CFLAGS) -c -O3 -o $@ $<)

Then I used platform/600D.102/autoexec.bin.

Code: [Select]
[miyake@MLdev32 magic-lantern600daudio]$ ll -h platform/all/autoexec.bin
-rwxrwxr-x. 1 miyake miyake 2.4M Sep  8 01:18 platform/all/autoexec.bin
[miyake@MLdev32 magic-lantern600daudio]$ ll -h platform/600D.102/autoexec.bin
-rwxrwxr-x. 1 miyake miyake 420K Sep  8 01:17 platform/600D.102/autoexec.bin

result
23sec => 43fps

Without -O3
Code: [Select]
[miyake@MLdev32 magic-lantern600daudio]$ ll -h platform/all/autoexec.bin
-rwxrwxr-x. 1 miyake miyake 1.8M Sep  8 01:39 platform/all/autoexec.bin
[miyake@MLdev32 magic-lantern600daudio]$ ll -h platform/600D.102/autoexec.bin
-rwxrwxr-x. 1 miyake miyake 308K Sep  8 01:38 platform/600D.102/autoexec.bin

result
25sec=>40fps

64
General Development Discussion / Re: [MERGED] Makefile with user prefs
« on: September 07, 2012, 04:26:00 PM »
+1 .. but global CFLAGS don't seem to be that useful, I tried a compile with global -O3 and it was much larger & didn't run.

-O3 is optimized flag. So I think it will provide "loop spread" and so on. So binary  will bigger...
Anyway, You can add alex's code like this....Maybe....
Code: [Select]
diff -r cac1f529216b Makefile.inc
--- a/Makefile.inc      Fri Sep 07 22:43:03 2012 +0900
+++ b/Makefile.inc      Fri Sep 07 23:23:32 2012 +0900
@@ -158,6 +161,8 @@
 %.bin: %
        $(call build,OBJCOPY,$(OBJCOPY) -O binary $< $@)

+zebra.o: $(SRC_DIR)/zebra.c
+$(call build,CC,$(CC) $(CFLAGS) -O3 -c -o $@ $<)

 zip: prepare_zip magiclantern-$(VERSION).zip



Anyway, I'm using -DCONFIG_600D_AUDIO_DEBUG flag. It's very good to adding a specific code all over the repository.

65
General Development Discussion / Re: [MERGED] Makefile with user prefs
« on: September 07, 2012, 03:54:19 PM »
@nanomad

One more .  Now we can add CFLAGS like this.

Code: [Select]
diff -r cac1f529216b Makefile.inc
--- a/Makefile.inc      Fri Sep 07 22:43:03 2012 +0900
+++ b/Makefile.inc      Fri Sep 07 22:51:21 2012 +0900
@@ -130,6 +130,8 @@
        -I$(PLATFORM_INC) \
        -I$(SRC_DIR) \

+CFLAGS += $(CFLAG_USER)
+
 ifeq ($(CONFIG_PYMITE),y)
 CFLAGS += $(PYMITE_CFLAGS)
 endif
diff -r cac1f529216b Makefile.user.default
--- a/Makefile.user.default     Fri Sep 07 22:43:03 2012 +0900
+++ b/Makefile.user.default     Fri Sep 07 22:51:21 2012 +0900
@@ -46,3 +46,6 @@
 CONFIG_PLUGINS                 = n
 CONFIG_CONSOLE         = n
 CONFIG_DEBUGMSG        = 0
+
+#CFLAG_USER = -mlong-calls \
+


66
General Development Discussion / Re: [MERGED] Makefile with user prefs
« on: September 07, 2012, 10:32:08 AM »
Confirmed .Thankyou  and good work!!

67
General Development Discussion / Re: Makefile with user prefs
« on: September 07, 2012, 04:27:37 AM »
Why didn't you push it yet?
I think you have a permission on main repo.
It's really easy/small-time things.


68
General Development Discussion / [MERGED] Makefile with user prefs
« on: September 06, 2012, 06:28:40 PM »
@all deveropper
Sometime we developer push each environment specific Makefile valiable.
So I think
 -separate User prefs to another file.
 -load from Makefile.inc
 -Do not add Userprefs.inc to repo
 -Only add Userprefs.inc.default
  -> all user cp Userprefs.inc.default to Userprefs.inc and edit it each environment.
Then , We never touch Makfile values on the repository.

patch added

Code: [Select]
diff -r 048012c0f7ad Makefile.inc
--- a/Makefile.inc      Tue Sep 04 12:37:49 2012 +0200
+++ b/Makefile.inc      Fri Sep 07 01:28:45 2012 +0900
@@ -1,50 +1,5 @@
 #generic makefile
-
-# for yagarto or the official ARM toolchain use ARM_ABI=none-eabi otherwise use ARM-ABI=elf
-ARM_ABI=none-eabi
-
-ARM_PATH=~/arm-toolchain462
-ARM_BINPATH=$(ARM_PATH)/bin
-GCC_VERSION=4.6.2
-CC=$(ARM_BINPATH)/arm-$(ARM_ABI)-gcc-$(GCC_VERSION)
-OBJCOPY=$(ARM_BINPATH)/arm-$(ARM_ABI)-objcopy
-AR=$(ARM_BINPATH)/arm-$(ARM_ABI)-ar
-RANLIB=$(ARM_BINPATH)/arm-$(ARM_ABI)-ranlib
-READELF=$(ARM_BINPATH)/arm-$(ARM_ABI)-readelf
-ARM_LIBC_A = $(ARM_PATH)/arm-$(ARM_ABI)/lib/libc.a
-LD=$(CC)
-HOST_CC=gcc
-HOST_CFLAGS=-g -O3 -W -Wall
-PYTHON=python2
-
-# Naming convention for Magic Lantern builds:
-# General rules:
-# - Always specify the camera and its firmware version number in the build name (e.g. 550d.fw109)
-# - For non-release builds, specify the build date and author's (nick)name.
-# - For experimental builds, add a short keyword indicating the particular feature tested.
-
-# Examples for experimental builds:
-# magiclantern-2010dec07.550d.fw108.cropmarks.a1ex.zip
-# magiclantern-2010nov23.550d.fw108.selectable-audio.piers.zip
-
-# Example for pre-release builds:
-# magiclantern-2010dec17.550d.fw109.PRERELEASE.alex.zip
-
-# Release builds:
-# magiclantern-0.2.0.rc1.550d.fw109.zip
-#~ VERSION=0.2.0.rc1.550d.fw109
-BUILDVER=$(shell whoami).$(shell hg id -i -r .)
-VERSION:=v2.3.NEXT.$(shell LC_TIME=EN date +'%Y%b%d').$(MODEL)$(FW_VERSION)
-
-CONFIG_PYMITE          = n
-CONFIG_RELOC           = n
-CONFIG_TIMECODE                = n
-CONFIG_PTP                     = n
-CONFIG_PTP_CHDK        = n
-CONFIG_PTP_ML          = n
-CONFIG_PLUGINS                 = n
-CONFIG_CONSOLE         = n
-CONFIG_DEBUGMSG        = 0
+include ../../Userprefs.inc

 UNAME:=$(shell uname)

diff -r 048012c0f7ad Userprefs.inc.default
--- /dev/null   Thu Jan 01 00:00:00 1970 +0000
+++ b/Userprefs.inc.default     Fri Sep 07 01:28:45 2012 +0900
@@ -0,0 +1,48 @@
+# for yagarto or the official ARM toolchain use ARM_ABI=none-eabi otherwise use ARM-ABI=elf
+ARM_ABI=none-eabi
+
+ARM_PATH=~/arm-toolchain462
+ARM_BINPATH=$(ARM_PATH)/bin
+GCC_VERSION=4.6.2
+CC=$(ARM_BINPATH)/arm-$(ARM_ABI)-gcc-$(GCC_VERSION)
+OBJCOPY=$(ARM_BINPATH)/arm-$(ARM_ABI)-objcopy
+AR=$(ARM_BINPATH)/arm-$(ARM_ABI)-ar
+RANLIB=$(ARM_BINPATH)/arm-$(ARM_ABI)-ranlib
+READELF=$(ARM_BINPATH)/arm-$(ARM_ABI)-readelf
+ARM_LIBC_A = $(ARM_PATH)/arm-$(ARM_ABI)/lib/libc.a
+LD=$(CC)
+HOST_CC=gcc
+HOST_CFLAGS=-g -O3 -W -Wall
+PYTHON=python2
+
+# Naming convention for Magic Lantern builds:
+# General rules:
+# - Always specify the camera and its firmware version number in the build name (e.g. 550d.fw109)
+# - For non-release builds, specify the build date and author's (nick)name.
+# - For experimental builds, add a short keyword indicating the particular feature tested.
+
+# Examples for experimental builds:
+# magiclantern-2010dec07.550d.fw108.cropmarks.a1ex.zip
+# magiclantern-2010nov23.550d.fw108.selectable-audio.piers.zip
+
+# Example for pre-release builds:
+# magiclantern-2010dec17.550d.fw109.PRERELEASE.alex.zip
+
+# Release builds:
+# magiclantern-0.2.0.rc1.550d.fw109.zip
+#~ VERSION=0.2.0.rc1.550d.fw109
+BUILDVER=$(shell whoami).$(shell hg id -i -r .)
+VERSION:=v2.3.NEXT.$(shell LC_TIME=EN date +'%Y%b%d').$(MODEL)$(FW_VERSION)
+
+CONFIG_PYMITE          = n
+CONFIG_RELOC           = n
+CONFIG_TIMECODE                = n
+CONFIG_PTP                     = n
+CONFIG_PTP_CHDK        = n
+CONFIG_PTP_ML          = n
+CONFIG_PLUGINS                 = n
+CONFIG_CONSOLE         = n
+CONFIG_DEBUGMSG        = 0
+
+
+#Additional CFLAGS here
\ No newline at end of file


69
Nightly Builds / Re: 600D Audio TEST release - 2.3 based
« on: September 06, 2012, 06:16:07 PM »
1%
I just found zippyshare is able to hear the sound directoly on the site.
And hear it, but I don't know what point is wrong you are thougt.

70
Nightly Builds / Re: 600D Audio TEST release - 2.3 based
« on: September 06, 2012, 09:09:36 AM »
hmm, qfpost issue again? The file is broken....

Anyway, I think the best way to talk about WAV stereo  is in the WAV forum . 
And I don't wanna import WAV related code in 600D audio repos. If I wrote codes , I will make a patch like wav queue.
It's will make a  confusing to check the codes when mergeing.

71
Nightly Builds / Re: 600D Audio TEST release - 2.3 based
« on: September 06, 2012, 05:58:31 AM »
1%
Can you share snapping finger with distortion video? I want to know what Hz affect by filter settings.
My finger don't make a sound :-[

Does "piggybacking" a function on ML? Do I have something to do  on our 600D audio codes?

72
Nightly Builds / Re: 600D Audio TEST release - 2.3 based
« on: September 05, 2012, 07:21:07 PM »
Hi! In this release, is it possible to turn audio recording off completely in order to record video with higher bitrate on a slow SD card?
No.
Faster card needed.

73
Feature Requests / Re: smartphone gps
« on: September 05, 2012, 06:15:41 PM »
Maybe you can enable PTP_ML on source code and build your self.
And buy cheap Android(Need supported USB host mode).
Then, you need to add code for
 -transfer the GPS location by USB-PTP on Android side.
 -Receive it and write location to pictures on ML side.

Then you can do it. Try it.
I don' t know iPhone is USB host mode supported or not.

74
Reverse Engineering / Re: High ISO needs more HW resource
« on: September 05, 2012, 06:01:36 PM »
I see. Thanx!

75
Nightly Builds / Re: 600D Audio TEST release - 2.3 based
« on: September 05, 2012, 05:55:55 PM »
Yeah I think it's the canon one!
I'll try to reproduce it and catch it on video, will upload as soon as I accomplish it.

Ah, OK....
Maybe I can't solve it. It's not do a negative effect to us. So never mind it.

Pages: 1 2 [3] 4 5 ... 14