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.


Topics - miyake

Pages: [1]
1
I can't find similar script on this forum, then I made it , but this is very cutting edge script.
I'm using CS 5.5 on windows
Once launch the afterfx script,
1:mlv_dump to dng
2:import dng footage to AE
3:create composition
4:added render queue for proxy

Does anyone tell me , if you know more comfortable work flow.

Current limitation:
-GUI is not yet finished to implement.
-Can't use multi-byte char for folder name
-Script has no progress bar , so we need to check output folder for current mlv_dump progress.

Preparation:
-AE General settings->general->check "Permit to file and network access by AE script"
-edit mlvdumpPath,strInDir,strOutDir,mlvdraft and H.264 parametars for your environment
-put script file to AE script dir

When something wrong, launch file>script>script editor from AE, and load script file and run it. Then you can see error messages.

https://github.com/kotyatokino/mlvimport

3
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


4
Reverse Engineering / High ISO needs more HW resource
« on: September 05, 2012, 08:54:46 AM »
Is this a well known things?
I just understand it.

CBR 3.0 + ISO3200 = recording stop immediately
CBR 2.6 + ISO3200 = recording stop immediately
CBR 2.4 + ISO3200 = sometime recording stop
CBR 1.0 + ISO 3200 = no problem

CBR 3.0 + ISO200 = no problem
Then push ISO button and ISO change dynamically, will recording stop when we changed to over ISO 1600

5
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.

6
General Development Discussion / On camera Autoexec.bin select
« on: August 16, 2012, 04:39:34 PM »
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.

7
I'm not native English speaker  , so we are little difficult to know all of things.
So I want to write FAQ page for Japanese speakers.
How to login it?

8
General Development Discussion / Movie autofocus experiments
« on: July 17, 2012, 03:53:50 AM »
I guess , this function's position like "50D video shooting". Basically we can't use MovieAF in our old cameras.But this function will provide capability for it. So more supporter will participate to this project.

Anyway, I'm interested in this function, and now I'm acquire and tuning the codes. AF moving is more faster than original. Still not perfect  but working. and It's a extremely noisy and battery eater (lol
But it is not converge to AF point. So this function need to apply more good formula for calculating focus distance from live view buffer. Or need a converge code.

Does any other developer existing who is interested in this function  ?

I can coding by C , but I'm not expert for analyzing graphic.

Pages: [1]