Menu

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.

Show posts Menu

Messages - Pelican

#326
Quote from: RenatoPhoto on January 06, 2013, 11:49:33 PM
I have gone over it many times.  Cannot solve the problem.

thanks
I've just edited my answer. Read it again.
ARM_LIBC_A=cygwin/home/PH/arm-toolchain462/arm-none-eabi/lib/libc.a
#327
I had a same problem.
Follow my instructions in the starting as a developer topic.
This line is the key:
ARM_LIBC_A=../../../arm-toolchain462/arm-none-eabi/lib/libc.a
You should give a relative path.
#328

I've moved some stuff from the 7D info screen.
#329
Tragic Lantern / Re: Tragic Lantern for 6D
January 04, 2013, 05:02:54 PM


Fixed MLU, HTP, ALO and put/relocate things on the info screen.
#330
General Development / Re: Gettings started as developer
January 02, 2013, 06:08:07 PM
So, now I pushed my changed to my fork and made a pull request.
When should I merge or pull the changes from the main?
#331
General Development / Re: Gettings started as developer
January 02, 2013, 04:41:28 PM
Still don't know when should I use hg merge (and exactly how)...

Could anybody give me a clear direction?
Thanks in advance.

I've just pushed my changes and I can definitely write more code if I need to do every development only once and not getting lost in the source managing and resolving conflicts and waiting my code pulled. Now I have several copies of ML in my laptop and copy pasting code pieces from one to another. How do you manage this?
And who will pull my code to the main? Is it Alex's daily routine (I mean when no holiday)?



#332
General Development / Re: Gettings started as developer
January 01, 2013, 02:48:12 PM
Until now I can use my fork to develop but now when my commits merged manually to the main repo I've lost.
I've just started a new fork, because cannot fix the old one.
Could somebody write here the whole process of mercurial?
I'm starting with how I did until now and I will update this reply with your comments to make a tutorial for beginners (like me).
----------------------
Step 1. Get your fork to your local folder (don't forget "-r unified" and go to your personal folder first)
hg clone -r unified https://"USERNAME"@bitbucket.org/"USERNAME"/"FORKNAME"
(obviously write your username and forkname instead of "USERNAME" and "FORKNAME")
(maybe you can use https://bitbucket.org/"USERNAME"/"FORKNAME", I'm not sure)
Step 2. Develop the code

Step 3. Get the latest changes

hg pull -r unified https://bitbucket.org/hudson/magic-lantern
hg update
If any conflicts there you should fix that first.  (Is there an easy way?)
Step 4. Commit your changes

hg commit -u "USERNAME" -m "Short description about your changes"
Step 5. Update your fork with your commited changes

hg push -r unified https://bitbucket.org/"USERNAME"/"FORKNAME"
It will ask your username and password.


Until now I can work with these commands but now I couldn't push my changes.
There is a command, hg merge which I never used. When I should use it?
#333
Yes, you can build your own autoexec, but if you want to run it you have to set the boot flag on your camera.
See the starting as a developer topic for how to setup your machine to compile the code.
#334
Quote from: g3gg0 on December 30, 2012, 11:43:18 PM
@Pelican:
thanks for your contribution. i really love the way it looks now.
due to the flood of space changes, i rejected your pull request and added it manually (https://bitbucket.org/hudson/magic-lantern/commits/c5e001352bb0)
maybe you should revert all your space changes to this changeset and continue from there.
Thanks!
Last night I had an idea how to speed up the load of help pages. (My camera  looked  like a cheap chinese toy with this slow screen refresh)
The main idea is to save the vram when the bmh is opened/displayed and next time if the loader finds saved vram, then it loads to the vram directly instead of loading the bmh. Of course we can create all of them in advance and put it in to the distribution.
It's lightspeed now, hundred times quicker even it moves more data. You can load and display all the 153 pages in 3 seconds...  8)
The disadvantage is the bigger doc size (its about 75 MB ~ 3 raw image size on 7D) but in the zip its only 3 MB instead of 2.5 MB (the bmh files) so it will bigger with only half megabyte.

I wanted to merge it right now, but I had to pull the changes, so I'll go home now and make it again.

The load and save is very simple:

void save_vram(const char * filename)
{
    uint8_t* b = (uint8_t *)bmp_vram();
    ASSERT(b);
    if (!b) return;
   
   FILE * file = FIO_CreateFile( filename );
   if( file == INVALID_PTR )
      return;
   else   
    {
   FIO_WriteFile(file, b, BMP_VRAM_SIZE);

   FIO_CloseFile( file );
   }
}

int load_vram(const char * filename)
{
    uint8_t* b = (uint8_t *)bmp_vram();
    ASSERT(b);
    if (!b) return -1;
   
    unsigned size;
    if( FIO_GetFileSize( filename, &size ) != 0 )
        return -1;
   return read_file(filename, b, size);
}


And if you don't have any saved vram (page-xxx.vrm) in your doc folder than doesn't do anything at all.
It instantly works on all the cameras which has the same vram size as the 7D has.

Also I made a togglable page number display (with Set button) so you can't lost during browsing the help pages.

What do you think?
#335
Quote from: Aldeme on December 30, 2012, 09:51:22 PM
First of all thank you for all the hard work on ML.

Unfortunatly I am feeling a bit stressy after I think I found out a bug  :( . My autofocus doesn't work anymore after I tried the focus peaking benchmark in ML. The focus performance test started but ended immediatly with a beep and since then no autofocus anymore (also with another lens). I tried to re update the firmware of the camera but still no autofocus. Any help or tip is welcome.


OK I just found a workaround (erase all camera custom settings). One extra info for debugging: in the viewfinder the bracketing * kept blinking while I pressed the shutter half for focussing.
Similar happened with me, after I played with the ML, my autofocus custom settings have changed, I had have to set them again.
#336
Reverse Engineering / Re: Flash prop
December 30, 2012, 09:23:16 PM
Quote from: scrax on December 29, 2012, 11:23:11 PM
Thank's, I'm stuck now on that, so go on with what you think could be done to make those settings usable.  :)
I suppose like other prop that address is the same and just values are camera specific (for example for wireless flash.)
There are a lot of problem (at least on 7D).
This property only contains data when you are in the Canon flash menu. After that its deleted.
Also when you are in the Canon flash menu, you can see the same data at memory address 7B1A8 and several other places, but when you close the menu then all of them deleted too. I found the property data with memdump in other locations after the menu closed but these adresses changed every time.


Anyway, I fixed all the typos and stuff in the strobo.c/.h so you can compile them and also made a struct to the array.
I can send it to you if you can use it on 600D.


struct flash_info {
   int firing; // 0: enable firing, 1: disable_firing
   int ettl2_meter; // 0: evaluative, 1: average
   int expo_comp;
   int zoom;
   int mode; //E-TTL II, Manual, Multi
   int wireless_func;  // Disable, Ext, Ext (A,B,C), Ext+Int, Ext(A,B,C)+Int
   int wireless_channel; // (1,2,3,4)
   int shutter_sync; // 1st curt., 2nd curt, High Speed
   int multi_freq; // (199 = 0xc7, 1 = 0x1)
   int multi_count; //(hex like before 1 = 0x1 18 = 0x12)
   int internal_output; // Flash power values from 1/1 to 1/128 1/3stop: (2,5,8,a,d,10,12,15,18,1a,1d,20,22,25,28,2a,2d,30,32,35,38)
   int external_output;
   int group_a_output; // 0x00..0x38: 1/1..1/128
   int group_b_output;
   int group_c_output;
};


Another thing about your first post with this
addr   leng   0x29   0x27   0x25   0x23   0x21   0x1E   0x1C   0x1A   0x18   0x17   0x15   0x13   0x11   0x0E   0x0C   0x0A   0x08   0x06   0x04   0x02   0x00
80030038   0022:   aa   00   bc   04   gg   hh   ff   de   nn   k   mm   qq   ii   jj   ss   38   oo   pp   rr   tt   zz

I really don't understand how do you count these numbers.
For example, you positioned the c: flash mode to the 0x25 and actually it is the 0x01
When you see the prop spy data you see this:
80030038 0022: "first longword" "second long word" ... "sixth longword"

Doesn't matter if you see only one zero it is a longword (four bytes) so the byte order is:
03 02 01 00  07 06 05 04  0b 0a 09 08  0f 0e 0d 0c ...
#337
General Development / Re: Development stupid questions
December 30, 2012, 08:59:05 PM
Quote from: Floont on December 29, 2012, 11:10:11 PM
The % sign in C is the modulus operator.  Your code is calculating 0x4860 (18528 decimal) mod 0xff (255 decimal), which is 0xa8 (168 decimal).  What you actually want is the low byte of auto_iso_range, which can be retrieved either by changing 0xff to 0x100 in your existing code or simply using the & operator instead of the "%" operator (my preference), i.e. raw2iso(auto_iso_range & 0xff).
Yes, you are right, thank you!
I've figured out last night...
#338
Quote from: _7D_ on December 30, 2012, 05:36:31 PM
Thank you guys for this awesome second alpha!

Maybe, I´ve found some little bugs.

The first one: I always get a strange sound, if I activate "ALO warning" in "Warnings for bad settings..."

The second one: Quality warning "Other than RAW" isn´t working. Is there a possibility to configure this like I need it? Maybe in the next alpha?

Can somebody confirm the two bugs?
ALO warning was buggy, it always makes false alarm. I've fixed it, it will be in the next release.
Raw warning works fine for me. If I turn off RAW then beeps and write a message.
#339
Reverse Engineering / Re: Flash prop
December 29, 2012, 10:21:46 PM
Wow! I'm working on this too (I want to display the remote flash settings on the info screen), but you were quicker! Congrats!
I'll download your strobo.c and see it.
I want some more readable than a big array, like make a struct for flash settings like lens_info.

But if it is camera dependent we should put it to the platform specific folder instead of src, shouldn't we?
#340
On the 7D it is working fine.
Have you checked the property value with the property spy?
#341
General Development / Re: Development stupid questions
December 29, 2012, 09:43:49 PM
I've tried to print the auto iso range with this line:
bmp_printf(fnt, 455, 92, "%d-%d", raw2iso(auto_iso_range >> 8 ) , raw2iso(auto_iso_range % 0xff));
and I've got strange value for the max.
After I check the raw values I found this
if auto_iso_range is 0x4860
then  auto_iso_range >>8 is 0x48 (good) but auto_iso_range % 0xff is 0xa8 ! (wrong) which is exactly 0x48 + 0x60
I'm not really a hardcore C programmer so I couldn't figure out what circumstances causes this result.
It happens with other values too (between 0x4858 and 0x4878)

Any idea?
#342
I'm thinking to make it configurable what do you want to see in the four corners...
Like:
Header left options (Off, Artist name, Copyright , Date , Lens name, ML version, ...)
Header right, Footer left, Footer right with the same options


#343
Quote from: scrax on December 28, 2012, 05:31:18 PM
I can't find them in property.h diff...
will look at your sources.

Do you think it's hard to find them for 600D? If not can you tell me how, please?
property.h from line 170:
#endif

#define PROP_EFIC_TEMP_MAYBE            0x010100ed
//#define PROP_BATTERY_RAW_LEVEL_MAYBE          0x80030014

#define PROP_ARTIST_STRING      0x0E070000
#define PROP_COPYRIGHT_STRING   0x0E070001

#define PROP_LANGUAGE           0x02040002
#define PROP_VIDEO_SYSTEM       0x02040003


It is in the main source it's not my find.

If it doesn't work on 600D then turn property spy on, go to edit artist name, save it and see which property is changing.
#344
I've answered in the other topic.
It was in the source, in property.h
#345
Quote from: scrax on December 27, 2012, 10:30:56 PM
Have you tried also after using the beep function before?

by the way can you explain me a little where are defined
PROP_ARTIST_STRING
PROP_COPYRIGHT_STRING

I'm trying to add them in the 600D too: http://www.magiclantern.fm/forum/index.php?topic=4001.0
They are defined in property.h and I wrote the prop handler for them to propvalues.c/.h
#346
Audio remote shot works fine for me but I used clapping or whistling to activate it.
The only thing I would change it could be more level setting beyond 20.
#347

http://pel.hu/down/ML7D.png

I've played with the info screen a little, but I've forgot how can I update it to my fork... :(

And one question:

The mode warning is more useful for me if it warns when I not in the Av mode (instead of M), because I mostly use Av, and I use M mode only for (multi)flash photography.
I've changed it to fit my taste, but maybe others don't like it.
So, what do you think?
M or Av or configurable?


Edit: I've made the mode warning configurable, fixed the ALO warning and put the info screen changes to my fork. It will go to the main source when my pull request will accept.
#348
Archived porting threads / Re: First 7D alpha released!
December 23, 2012, 11:37:33 PM
I've just pulled the changes, I hope there are all the stuff from the alpha2 version.

I can't wait for the release (I'm in the rainforest, in a small village near the Costa Rican and Nicaraguan border and my laptop's battery is running out now).

Merry Christmas and Happy 7D ML! :)
#349
Archived porting threads / Re: Canon 7D ML
December 06, 2012, 11:33:59 AM
My 7D* surely a developer model because I use ML from autoexec.bin.  :) 
*D=Developer
#350
General Chat / Re: 5 Week Time Lapse
November 11, 2012, 07:11:21 PM
I'm using a cheap chinese ACK-E6 clone. It is very well built and its overall quality feels like the original Canon.
It doesn't contain any chip so you have to OK the camera's question at every start.
The camera can work with it 24 hours per day without overheating or other problem.
You can charge at least your equipment's rent value for five weeks.