Looking for ways to speed up the development.
How many of you would be willing to support our work?
(also on Twitter)
Server issues | Builds page | @autoexec_bin | IRC: #magiclantern
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.
I don't known about 450D, but in Canon 40D LiveView has no special button, and must be enabled in Canon menu system. Once enabled LiveView can be enabled in some mode when pressing "set" button.
Now i cant figure it out is there any way to shoot video with this camera?
I can't understand why it works ok on 450D and not on 40D since stubs.S are same (with different values)
NSTUB(0xFFCCD344, FIO_SeekFile)
extern int32_t FIO_SeekFile( FILE* stream, int32_t position, int whence );
int64_t FIO_SeekSkipFile( FILE* stream, int64_t position, int whence )
{
return (int64_t) FIO_SeekFile(stream, (int32_t) position, whence );
}
That is as long as you are not looking for ML-specific ‘stuff’ such as Dual-ISO
CURRENT_GUI_MODE should be 2C94
Menu flickering: define GUIMODE_ML_MENU as:It doesn't help.Code: [Select]#define GUIMODE_ML_MENU (lv ? 28 : 2)
You will want to look at crop_rec_4k, as that's the only version working with variable frame sizes, but it will require heavy tweaking on the memory management side. It's a bit more complicated than it needs to be, but... the alternative would be to reinvent the wheel (buffering, speed optimizations and so on).
I'm pretty sure the hardware can deliver MJPEG at full LiveView resolutionBut which framerate?
if (lr != 0xFFAD5870)
{
return;
}
uint32_t lvsize = MEM(0x8304);
char* lvbuf = MEM(0x8308);
if (BUF_SIZE > (len + lvsize))
{
char buff[9];
uint32_t* pnum = (uint32_t*)(buff);
*pnum = (uint32_t)(0x63643030); // "00dc"
pnum = (uint32_t*)(buff + 4);
*pnum = (uint32_t)lvsize;
memcpy(buf+len, buff, 8);
len += 8;
memcpy (buf+len, lvbuf, lvsize);
len += lvsize;
if (lvsize % 2 != 0)
{
char junk = 0;
memcpy (buf+len, &junk, 1);
len += 1;
}
}
return;
RAM:0000A7D4 08 60 F0 C0 DCD unk_C0F06008
RAM:0000A7D8 A3 09 A3 09 DCD 0x9A309A3
RAM:0000A7DC 0C 60 F0 C0 DCD unk_C0F0600C
RAM:0000A7E0 A3 09 A3 09 DCD 0x9A309A3
RAM:0000A7E4 10 60 F0 C0 DCD unk_C0F06010
RAM:0000A7E8 A3 09 00 00 DCD unk_9A3
RAM:0000A7EC 18 60 F0 C0 DCD unk_C0F06018
RAM:0000A7F0 20 00 00 00 DCD 0x20On 32 GB cards, the ML does not load. I tried it on two other cards.You can try this build
I do astrophotography and I need to brighten the view on the display so that I can set the focus on the stars. New versions of ML have this function available. Would you be able to program it into the 450D version? It would help me considerably. If you can do it, I would be willing to pay for that, just name your price.
I've put ML on the card.
3. During update blue led is blinking and nothing happend.
Installer for 450D firmware 1.1.0. : https://bitbucket.org/Ant123/magic-lantern-40d/downloads/ML450D110.fir
It works the same as 40D/5DC installer.
7.) Launch the firmware update process. If you see any red led, then something went wrong. A solid blue led means that the bootdisk is now enabled. A blinking blue led means the bootdisk is now disabled (if you want to completely uninstall ML). Each time you run the firmware update it just toggles the bootdisk to the opposite of whatever it is currently. The installer FIR will make your CF card bootable for you, no further work required here.
8.) Turn the power switch off and pull your battery to turn the camera off. Just turn the camera on (make sure autoexec.bin and ML directory are on the card!) and you're all set. Press the Trash button to bring up the ML menu.
You only need to run the firmware update to enable the bootflag ONCE. Each time after that will only disable, re-enable, disable, re-enable, etc. the bootflag.
But direct font taken from ML doesn't look beautiful...
from 0xBFE00000, size 0x200000 - camera locks up with Err70, no log is saved.
- emulation is able to reach GuiMainTask (after updating the MPU messages and some trivial GDB patches - not yet committed)Have you tried to apply modified EOS M3 patches? (0xFC3F1110, 0xFC3F1114, 0xFC3F1178)
- it gets stuck trying to communicate with Zico/MZRM (as expected)
0xfd8a9640, 0x00021704
0xfd8eb030, 0x00024060
0xfd90f090, 0x00012e60
0xfd921ef0, 0x00056d70
0xfd978c60, 0x0009fe10
0xfda18a70, 0x0001f18c
0xfda37bfc, 0x00024cf4
0xfda5c8f0, 0x0000b9a0
0xfda682a0, 0x00000cc4
0xfda68f64, 0x00000f40
0xfda6aa8c, 0x00000cb8
0xfda6b744, 0x00000854
0xfda6bf98, 0x00000b88
0xfda6dc10, 0x00000cb0
0xfda6e8c0, 0x00000ad4
0xfda6f394, 0x0000113cIf you receive these strings from MMIO hooks, or from breakpoints into certain drawing functions, you will need to store them somewhere in a data structure, until the next display event comes up.
DisplaySurface *surface = qemu_console_surface(s->disp.con);
printfxy(surface, (pos_x >> 16), (pos_y >> 16), "%s", MZRM_str);Do I need to update the display somehow?