Quote from: RenatoPhoto on January 06, 2013, 11:49:33 PMI've just edited my answer. Read it again.
I have gone over it many times. Cannot solve the problem.
thanks
ARM_LIBC_A=cygwin/home/PH/arm-toolchain462/arm-none-eabi/lib/libc.a
Etiquette, expectations, entitlement...
@autoexec_bin | #magiclantern | Discord | Reddit | Server issues
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 MenuQuote from: RenatoPhoto on January 06, 2013, 11:49:33 PMI've just edited my answer. Read it again.
I have gone over it many times. Cannot solve the problem.
thanks
Quote from: g3gg0 on December 30, 2012, 11:43:18 PMThanks!
@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.
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);
}
Quote from: Aldeme on December 30, 2012, 09:51:22 PMSimilar happened with me, after I played with the ML, my autofocus custom settings have changed, I had have to set them again.
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.
Quote from: scrax on December 29, 2012, 11:23:11 PMThere are a lot of problem (at least on 7D).
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.)
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;
};
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
Quote from: Floont on December 29, 2012, 11:10:11 PMYes, you are right, thank you!
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).
Quote from: _7D_ on December 30, 2012, 05:36:31 PMALO warning was buggy, it always makes false alarm. I've fixed it, it will be in the next release.
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?
Quote from: scrax on December 28, 2012, 05:31:18 PMproperty.h from line 170:
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?
#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
Quote from: scrax on December 27, 2012, 10:30:56 PMThey are defined in property.h and I wrote the prop handler for them to propvalues.c/.h
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
Page created in 0.111 seconds with 13 queries.