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

#301
1. Yes.
2. No
#302
General Development / Re: Flexible info screen
February 27, 2013, 10:58:48 AM
Quote from: g3gg0 on February 18, 2013, 10:21:18 PM
is this element referencing the text as anchor?
Yes.
Quote from: g3gg0 on February 18, 2013, 10:21:18 PM
if you manually hide the text element (using editor) the filling disappears?
No.
Quote from: g3gg0 on February 18, 2013, 10:21:18 PM
can you send me the config array?
<fill name="Pics (clear)" x=540 y=390 z=1 w=150 h=60 anchor=11 color=-33554432 />
<string name="Pics" y=-1 z=2 w=78 h=40 anchor_flags=10 anchor=10 anchor_flags_self=10 string_type=36 fgcolor=1 bgcolor=-33554432 font_type=6 />

Also the 'Save config' is useless because it doesn't read back the saved xml at the start.
#303
Feature Requests / Re: SD/CF Card ID
February 27, 2013, 10:20:49 AM
#304
Feature Requests / Re: SD/CF Card ID
February 26, 2013, 01:10:28 PM
Quote from: NedB on February 26, 2013, 12:13:23 PM
It might be nice to know with which SD/CF card I am currently shooting, without having to A) Turn off the camera and B) take the card out to look at the label. What about displaying this somewhere on the GUI? I have my cards numbered N001, N002, etc. Could we see this somewhere in the GUI, perhaps with a "card" icon?

There could be a very small (read-only?) text file on each card which ML could read to get the "N001" (or whatever) label.

Good idea?

NedB
With the new flexinfo system, you can display the card label, the card maker and the card model info.
#306
General Development / Re: Flexible info screen
February 18, 2013, 09:20:04 PM
Quote from: g3gg0 on February 09, 2013, 10:33:13 PM
well, no idea whats wrong with the version you have - here it works without problems.
Thanks, the bg color works here too now.
I still cannot use the INFO_TYPE_FILL for avail_shot because it's clearing the rectangle even if no text displayed.
#307
General Development / Re: ML UI rationalization
February 15, 2013, 05:08:45 PM
Quote from: stevefal on February 14, 2013, 08:56:17 PM
My goal is to solidify a rational UI model for ML and then promote it across the system. The current system does not implement a consistent model (hence my post). It's very hard in this phase because people are evaluating fragments in isolation, and drops that do not necessarily use the proposals as intended, have not yet implemented them or might not implement them.

I'm glad people are seeing progress, but there's so much more that can be done. I know it can be much better and if we get there we'll be hearing more like scrax's "I found out thing that were not so clear to me even if I'm along time user". (thx scrax.)

working, working...
Agree 100%. Thank you very much for your effort to make ML GUI more rational and professional look.
#308
General Development / Re: ML UI rationalization
February 15, 2013, 05:07:01 PM
Quote from: stevefal on February 14, 2013, 10:29:04 PM
Looking for an 'execute' icon for the center column.
Edit:
#309
General Help Q&A / Re: EOScard / newbie install question
February 14, 2013, 05:02:38 PM
No, you don't have to copy EOScard to your CF card but you have to run it.
And you have to follow the install procedure, you can skip only the "copy files to the card" and "prepare card" parts...

#310
General Development / Re: PtpCam compile error
February 12, 2013, 04:44:46 PM
Quote from: coutts on February 12, 2013, 03:55:58 PM
cygwin should include socket.h, maybe it's a path issue?
Yes, I can fix that.
The problem is the rest (gdb_listen, gdb_wsadata, etc.)
#311
The card is one thing and your camera is another thing...

Lexar Professional 1000x in 5D mkIII


Lexar Professional 1000x in 7D


I'm using a 32 GB Transcend 400x UDMA7 card in my 7D and it has a specification of 60MB/s write and 90 MB/sec read speed, but I can read the data from it with a Transcend USB 3.0 card reader above 110 MB/sec.
#312
General Development / Re: PtpCam compile error
February 11, 2013, 10:37:50 PM
Is there anybody who can compile ptpcam uder windows (cygwin)?
I can fix the missing headers, but not the rest.

$ make
gcc-3 -o ptpcam myusb.c properties.c ptp.c ptpcam.c -mno-cygwin -I"/cygdrive/d/u
til/cygwin/home/Pel/7dml/contrib/ptpcam/libusb-win32-bin-1.2.2.0/include" "/cygd
rive/d/util/cygwin/home/Pel/7dml/contrib/ptpcam/libusb-win32-bin-1.2.2.0/lib/gcc
/libusb.a" -lws2_32 -lkernel32
ptpcam.c:2449:24: sys/socket.h: No such file or directory
ptpcam.c:2450:24: netinet/in.h: No such file or directory
ptpcam.c:2451:23: arpa/inet.h: No such file or directory
ptpcam.c:2452:19: netdb.h: No such file or directory
ptpcam.c:2454:1: warning: "INVALID_SOCKET" redefined
In file included from libptp-endian.h:8,
                 from ptp.h:27,
                 from ptpcam.c:21:
/usr/i686-pc-mingw32/sys-root/mingw/include/winsock2.h:296:1: warning: this is t
he location of the previous definition
ptpcam.c: In function `gdb_loop':
ptpcam.c:2511: error: `MSG_DONTWAIT' undeclared (first use in this function)
ptpcam.c:2511: error: (Each undeclared identifier is reported only once
ptpcam.c:2511: error: for each function it appears in.)
ptpcam.c:2524: error: `EWOULDBLOCK' undeclared (first use in this function)
ptpcam.c: In function `gdb_listen':
ptpcam.c:2561: error: `gdb_wsadata' undeclared (first use in this function)
ptpcam.c: In function `chdk':
ptpcam.c:2992: warning: assignment from incompatible pointer type
ptpcam.c:3017: warning: assignment from incompatible pointer type
ptpcam.c:3027: warning: passing arg 1 of `ptp_chdk_get_memory' makes integer fro
m pointer without a cast
ptpcam.c:3027: warning: assignment from incompatible pointer type
ptpcam.c:3045: warning: assignment from incompatible pointer type
ptpcam.c:3066: warning: initialization from incompatible pointer type
Makefile:12: recipe for target `ptpcam' failed
make: *** [ptpcam] Error 1
#313
Last week I played with a small Canon waterproof compact camera (D20) and it can take 240 fps video in 640x480 (?) which sounds completely useless,  but when I filmed flying hummingbirds it made a wonderful slow-mo movie of their flight...
#314
General Development / Re: Flexible info screen
February 09, 2013, 09:43:31 PM
Could you check the background color and the fill bug please?
#315
I'll go back home at the next week, and I want to spend more time with 7DML developing.
#316
General Development / video_hacks.c compile error
February 03, 2013, 07:11:46 PM
I've just made a fork from the main repo (last: 443aec4) and cannot compile 7D code.
Yesterday, and the day before also cannot compile because the ptp-ml.c


[ CC       ]   bmp.o
[ CC       ]   video_hacks.o
../../src/video_hacks.c: In function 'bitrate_flushing_rate_display':
../../src/video_hacks.c:41:30: error: 'MNI_WARNING' undeclared (first use in thi
s function)
../../src/video_hacks.c:41:30: note: each undeclared identifier is reported only
once for each function it appears in
../../src/video_hacks.c: In function 'bitrate_gop_size_display':
../../src/video_hacks.c:67:30: error: 'MNI_WARNING' undeclared (first use in thi
s function)
../../src/video_hacks.c: At top level:
../../src/video_hacks.c:159:17: error: unknown field 'display' specified in init
ializer
../../src/video_hacks.c:159:17: warning: initialization makes integer from point
er without a cast [enabled by default]
../../src/video_hacks.c:159:17: warning: (near initialization for '(anonymous)[0
].min') [enabled by default]
../../src/video_hacks.c:160:17: warning: initialized field overwritten [-Woverri
de-init]
../../src/video_hacks.c:160:17: warning: (near initialization for '(anonymous)[0
].min') [-Woverride-init]
../../src/video_hacks.c:167:17: error: unknown field 'display' specified in init
ializer
../../src/video_hacks.c:167:17: warning: initialization makes integer from point
er without a cast [enabled by default]
../../src/video_hacks.c:167:17: warning: (near initialization for '(anonymous)[1
].min') [enabled by default]
../../src/video_hacks.c:168:17: warning: initialized field overwritten [-Woverri
de-init]
../../src/video_hacks.c:168:17: warning: (near initialization for '(anonymous)[1
].min') [-Woverride-init]
../../Makefile.inc:641: recipe for target `video_hacks.o' failed
make: *** [video_hacks.o] Error 1
#317
General Development / Re: ptp-ml compile error [ce2d748]
February 02, 2013, 07:43:38 PM
The code in the main repo is not consistent (I noticed yesterday, and today).
I can't compile the 7D code, I've got the same error message.
#318
General Development / Re: Flexible info screen
January 25, 2013, 05:41:39 PM
The INFO_COL_BG is the same black as the INFO_COL_FIELD (instead of gray on 7D).
The INFO_TYPE_FILL still doesn't work for me (it always clears the area even if the anchored string doesn't displayed).
I would like to display the avail_shot only when it is over 999, because the original Canon font is bigger (easier to read).

In the menu it could be better if you don't display all the options which you cannot reach (because it goes to the gray screen) just make an info like X: 100, Y: 200, Z: 2, etc. so it can fit on the screen. The option to change the string type would be great too.
#319
I'm a big fan of ML but I not recommend to anybody to use 7DML for anything except testing.
I'm using it from the beginning (from autoexec.bin) and I took about 20.000 images with it but it is not safe for production work, I lost a lot of good actions because somehow the camera's settings changed. So before a final or a beta version we should fix those things.

(It's not a complain, I know what I'm doing, I took the risk to use the ML on my camera.)
#320
Quote from: angelom on January 23, 2013, 05:00:21 PM
No, you can't, at least not changing the version.
If you've upgraded to 2.x you're no longer able to downgrade to 1.x, sure not with EOS Utility, checked it time ago.
You can only downgrade whitin the same version, for example you can downgrade from 2.0.3 to 2.0.1.

I repeat, that is not correct, I did it a few times without any problem (from 2.x.x to 1.x.x).
Quote from: angelom on January 23, 2013, 05:00:21 PM
About the number of firmware upgrades I remember I've read on Magic Lantern site, months ago, that they d id too many firmware upgrades on the 7D, used for test/development, and suddenly the camera refused to do other upgrades so maybe there's really a maximun number of firmware upgrades (probably higher than needed for standard users waiting only for official updates but not so higher for developers).

Maybe there is something, but I did so many fw upgrade in the last three years so I should reach that limit but I didn't.
I can imagine for example a failed fw upgrade counter, but I don't believe if there is a limit for the normal fw upgrades.
#321
Quote from: Walter Schulz on January 23, 2013, 09:08:59 AM
The only limit I'm aware of: Canon doesn't support downgrading firmware v2.x back to v1.x.

Ciao, Walter


That's not correct, you can downgrade with EOS Utility.
#322
General Development / Re: Flexible info screen
January 20, 2013, 03:53:21 PM
Quote from: g3gg0 on January 18, 2013, 12:57:46 AM
already implemented. choose the string field as anchor item in the clear item.
then the clear item will only get drawn if the string item is printed (i.e. length > 0)
It doesn't work for me.

The aligning also doesn't work as I imagine. If the anchor is center or right it puts to left side of the string to the center or right instead of the center of the string or right side of the string.
For exmaple:
item 1: abcdefghijkl
item 2: 1234
item 2's anchor  is item 1,

anchor type: left
abcdefghijkl
1234


anchor type: center
abcdefghijkl
      1234


anchor type: right
abcdefghijkl
            1234

Instead of

anchor type: left
abcdefghijkl
1234


anchor type: center
abcdefghijkl
    1234


anchor type: right
abcdefghijkl
        1234

And now  the aligning is different for the different fonts.
#323
General Development / Re: Flexible info screen
January 18, 2013, 12:30:05 AM
The idea is good, I like it but I think it needs a little more work to be usable.

For example the avail_shot needs to show if it is above 999. You can program this condition to INFO_STRING_PICTURES but the INFO_TYPE_FILL have no condition so it will always clear the area. It would be a better solution if every item has a fill property which execute only when necessary (when the programmed condition is true).


Also it could be useful if every item has a show/hide property to easily turn on/off so you can put all the available options, and everybody can customize it (so you can display infos in the header/footer).


Also instead of using ifdefs in flexinfo.c I would put the camera specific info_config definition to a file in the platform folder (to 'misc' or a new file) so if two or more developer works on the info screen of the different cameras there is no conflict when they merge into the main repo.


#324
You should make your card bootable... (EOScard). I used a 16 GB.
#325
Quote from: scrax on January 06, 2013, 11:48:01 PM
Pelican, what are the green boxes for? And the number after the battery?
The green/gray boxes are the battery performance.
The number is the actually used battery from battery history table.
If you register your batteries there are 1-6 battery info in the battery history.
You can see the same info on Battery info menu, but you should navigate through the Canon menu system to see it.
I have 4 batteries and when I put one of them into the camera I can see right then which one is inserted.