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 ... 14
1
anybody interested in this script :D

Anyway, I implemented in GUI and fix some bugs.
I already satisfied, finished project.

2
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 / Re: Movie autofocus experiments
« on: September 26, 2012, 09:08:16 AM »
d

4
General Development Discussion / Re: Movie autofocus experiments
« on: September 26, 2012, 07:28:36 AM »
d

5
General Development Discussion / Re: Movie autofocus experiments
« on: September 26, 2012, 05:32:51 AM »
d

6
General Development Discussion / Re: Movie autofocus experiments
« on: September 26, 2012, 04:37:32 AM »
d

7
General Development Discussion / Re: How to run Magic Lantern into QEMU?!...
« on: September 24, 2012, 10:50:23 AM »
I'm now watching here.
http://chdk.wikia.com/wiki/GPL_Qemu

I wish this for something help for you.

8
All problem was gone, and made a pull request.
Now need to consider that take out from submenu for fast operations.
I'm changed 600D audio gain/boost from submenu. We don't need to open/close submenu when we change 600D audio volumes!!

9
I thought it has no problem to use it. So I didn't add exception for simple implementation.
But you feel uneasy, I will solve it.
Give me a few time for solving it. More consider for beautiful code design. 

10
General Development Discussion / Re: Change hardcoded beta warning to macro?
« on: September 22, 2012, 09:30:53 AM »
Already merged

11
Feature Requests / Re: exif and
« on: September 22, 2012, 03:51:41 AM »
I'm researched this thing for my Samyan 14mm.
The Exif is variable length. So I guess, no-exif file has no field for adding exif data.
So I need clear space with file copy operation for adding exif data. It's need a lot of time for adding exif data.
This means more battery and time needed,,,,,

12
General Development Discussion / Re: Change hardcoded beta warning to macro?
« on: September 20, 2012, 02:14:36 PM »
sounds good!

13
General Development Discussion / Re: Change hardcoded beta warning to macro?
« on: September 20, 2012, 12:13:44 PM »
I think you need to add y/n style in Makefile.in and Makefile.user.default.
Or specify DCONFIG_RELEASE_BUILD  in Makefile.user.default by comment.
It's better for humans. we are forget a lot of things soon.

If you complete the patch, you make a PM to Alex or nanomad, I think they will merge it.

I also used CVS before development ML. Now my local repo is mercurial . But I don't know how to make a pull request system on my own system now...

14
That, and I would have loved to have separate pull requests for audio and menus. But a1ex just accepted the full pull request it so....
Thanks miyake :P

I made a separate pull request. First I make a scroll menu pull request and then I confirmed pulled.
After that, I make a audio pull request.

Or Do you think that make a your own patch and push it? It's not good , because commit log will be lost.

15
Current menu has no overflow menu items. If you add new menu item and it's will be overflow from display size, You can see vscroll.

16
General Development Discussion / Re: Change hardcoded beta warning to macro?
« on: September 20, 2012, 11:22:13 AM »
+1 !!
Make patch file or make pull request to your repo.

17
Ah, I see.

18
I just clone current repo.
But menu.c has no warning.

19
Nightly Builds / Re: 600D Audio TEST release - 2.3 based
« on: September 20, 2012, 03:32:05 AM »
Merged all of our 600D audio codes to unified development tree!!!
Those codes are leave from our hand. Thankyou very much all testers. It's our developers/testers achievement.
But if you found some more problems, I can support you and if I found/solve bugs, I can push bug fix code to Alex.
Next release or improvement .bin will release from core team. 

20
?? why you need to merge it?
Pulled code a already merged to unified. So you just type "hg pull, hg update" only I think.

21
Forget it. But just tested quickly.
I can't find problems.

22
@nanomad
made pull request.
Please proceed it.

23
68d9dd6d5240 add exception for audio(meter space) and focus(lens info)

I found one more issue from 1%'s comment.
Now lens info is always showing.

and added miner action tweak. More good feeling now.

24
1%
It's same as normal firmware. So I think it is no problem.

25
Nightly Builds / Re: 600D Audio TEST release - 2.3 based
« on: September 18, 2012, 06:38:47 PM »
Never mid, I'm not native too.
Anyway, Try our 600D audio 0.11 version. And If you find bug or had a some advice to us, feel free to comment to this forum.

Pages: [1] 2 3 ... 14