51
Camera-specific Development / Re: Porting ML to XSi (450D)
« on: July 02, 2020, 02:51:38 PM »Is it possible to use the feature "Dump image buffers" on the EOS 450D??
Not yet.
News:
Etiquette, expectations, entitlement...
@autoexec_bin | #magiclantern | Discord | Reddit | Server issues
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.
Not yet.
52
Camera-specific Development / Re: Porting ML to XSi (450D)
« on: June 23, 2020, 02:59:17 PM »I was wondering if it is possible to install modules in this camera?
It's possible if you have enough programming skills to develop(adapt) and recompile modules.
Most likely, most modules will not work on 450D because this port is slightly abandoned...
53
Camera-specific Development / Re: Porting ML to XSi (450D)
« on: May 17, 2020, 08:23:02 AM »Any Ideas PLEASE??
It looks like your SD card is not bootable or don't contain ML files or incompatible with ML.
You can also try a newer build
54
Camera-specific Development / Re: DIGIC 8 'PowerShot' development (M50, SX70, SX740)
« on: May 11, 2020, 11:55:54 PM »None of them has anything to do with ARM.No. Some modern Arduinos already contain ARM Cortex-M0.
55
General Chat / Re: Web video conferences and eye contact: Any solution?
« on: May 05, 2020, 09:21:50 PM »
56
Camera-specific Development / Re: Canon 40D
« on: April 21, 2020, 04:51:18 PM »
heder
Maybe you will commit changes to your repository?
Maybe you will commit changes to your repository?
57
Camera-specific Development / Re: Canon 40D
« on: March 25, 2020, 04:49:50 PM »
Did you manage to get the image using "lv_save_raw" ?
58
Camera-specific Development / Re: Canon 40D
« on: March 22, 2020, 07:07:40 PM »We can utilize this in magic lantern and save each mjpeg into a file, which will result in a motion-jpeg stream.
https://www.magiclantern.fm/forum/index.php?topic=8119.msg212429#msg212429
59
Camera-specific Development / Re: Canon EOS M6
« on: March 03, 2020, 10:48:25 PM »
AFAIK there are no developers with M6 on CHDK forum.
60
Camera-specific Development / Re: Canon 40D
« on: February 25, 2020, 05:54:11 PM »Currently stuck in finding adgt/cmos read/write function as they're not the same as the digic4 and newer platforms.
What about function names registered in sub_FFB24D68 (40D111) ?
61
Camera-specific Development / Re: Porting ML to XSi (450D)
« on: January 13, 2020, 05:57:18 PM »
There are no significant canges since reply#23
Runing ML GUI doesn't mean ML functionality.
So I think this topic should be removed from "Sticky Topics".
Runing ML GUI doesn't mean ML functionality.
So I think this topic should be removed from "Sticky Topics".
62
Camera-specific Development / Re: [UNMAINTAINED] Canon 40D
« on: September 03, 2019, 04:51:27 PM »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.
EOS 450D also uses "Set" button to turn on LiveView.
for your camera see page 161
63
Camera-specific Development / Re: [UNMAINTAINED] Canon 40D
« on: September 03, 2019, 12:07:09 PM »64
Camera Emergency Department / Re: Canon 7D - Black vertical lines on images/video/live view
« on: September 01, 2019, 02:52:57 PM »
Probably there is a bad contact in cable connection between image sensor and mainboard.
(shown on picture #8 at center)
(shown on picture #8 at center)
65
Camera-specific Development / Re: Canon EOS R / RP
« on: July 17, 2019, 12:14:00 PM »
2 Walter Schulz and other moderators
Why don't you oblige new users to read the FAQ before they can post? And then delete dumb messages / ban them.
There is no advertising on this forum. So why do we need to see their useless posts?
Why don't you oblige new users to read the FAQ before they can post? And then delete dumb messages / ban them.
There is no advertising on this forum. So why do we need to see their useless posts?
66
Camera-specific Development / Re: Porting ML to XSi (450D)
« on: May 10, 2019, 10:11:22 AM »Now i cant figure it out is there any way to shoot video with this camera?
There is only one way which works at the moment.
Recording MJPEG video on SD-card is not ready yet. I'm not sure that this will be completed ...
67
Camera-specific Development / Re: [UNMAINTAINED] Canon 5D Classic Firmware ** Beta 4 **
« on: March 30, 2019, 06:25:21 PM »
Maybe you are loading fonts too early:
https://www.magiclantern.fm/forum/index.php?topic=8119.msg190359#msg190359
https://www.magiclantern.fm/forum/index.php?topic=8119.msg190359#msg190359
68
Camera-specific Development / Re: [UNMAINTAINED] Canon 5D Classic Firmware ** Beta 4 **
« on: March 25, 2019, 04:01:09 PM »I can't understand why it works ok on 450D and not on 40D since stubs.S are same (with different values)
Because of this line
I did not found 64bit function FIO_SeekSkipFile:
Code: [Select]
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 );
}
69
Tutorials and Creative Uses / Re: Reflections on ML & CHDK
« on: February 28, 2019, 09:44:59 PM »That is as long as you are not looking for ML-specific ‘stuff’ such as Dual-ISO
FRSP & Dual-ISO can be implemented on EOS-M[3,5,6,10,100] cameras runing CHDK(and maybe without CHDK).
70
Camera-specific Development / Re: Porting ML to XSi (450D)
« on: February 24, 2019, 09:46:51 PM »CURRENT_GUI_MODE should be 2C94
Already found it by myself. But it doesn't help.
71
Camera-specific Development / Re: Porting ML to XSi (450D)
« on: February 24, 2019, 08:05:23 PM »Menu flickering: define GUIMODE_ML_MENU as:It doesn't help.Code: [Select]#define GUIMODE_ML_MENU (lv ? 28 : 2)
This video was made with #define GUIMODE_ML_MENU (RECORDING ? 0 : lv ? 49 : 2)
https://filebin.net/f1akbgb5uprvkrxp/MVI_7190.MP4?t=3h26fipc
Quote
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).
Unfortunately vxworks branch is too old and has no mlv_lite and crop_rec_4k modules.
72
Camera-specific Development / Re: Porting ML to XSi (450D)
« on: February 24, 2019, 07:13:38 PM »
How to avoid the flashing(flickering) of ML menu and OSD in LiveView mode?
It also changes the colors of Canon's OSD elements.
Was the lv_rec module replaced by mlv_rec? I'm trying to choose the reference for MJPEG recorder.
It also changes the colors of Canon's OSD elements.
Was the lv_rec module replaced by mlv_rec? I'm trying to choose the reference for MJPEG recorder.
73
Camera-specific Development / Re: Porting ML to XSi (450D)
« on: February 23, 2019, 12:56:20 PM »Quote
I'm pretty sure the hardware can deliver MJPEG at full LiveView resolutionBut which framerate?
Current LV-JPEG resolution 848x568 used by EOS utility, EOS SDK and eos_movrec. The framerate is around 20-22.
Do you think it's limited by USB throughput?
74
Camera-specific Development / Re: Porting ML to XSi (450D)
« on: February 22, 2019, 10:51:31 PM »
Got MJpeg video by inserting this code into dm-spy function:
https://filebin.net/f1akbgb5uprvkrxp/DM.TXT.AVI
Is there better way to get LV JPEG data than intercepting debug messages?
Code: [Select]
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;
https://filebin.net/f1akbgb5uprvkrxp/DM.TXT.AVI
Is there better way to get LV JPEG data than intercepting debug messages?
75
Camera-specific Development / Re: Porting ML to XSi (450D)
« on: February 19, 2019, 04:00:46 PM »
I've compiled ML with FEATURE_LV_DISPLAY_GAIN.
But it doesn't work out of the box.
It seems that Digic 3 has no ISO_PUSH_REGISTER (0xc0f0e0f8).
Some registers are present (0xc0f08030, 0xc0f08034) but their modification has a very short effect. Probably camera refresh their values periodically.
Another problem is the lack of shadow memory. FPS override doesn't work either, but there are signs of FPS timers:
But it doesn't work out of the box.
It seems that Digic 3 has no ISO_PUSH_REGISTER (0xc0f0e0f8).
Some registers are present (0xc0f08030, 0xc0f08034) but their modification has a very short effect. Probably camera refresh their values periodically.
Another problem is the lack of shadow memory. FPS override doesn't work either, but there are signs of FPS timers:
Code: [Select]
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 0x20