Updated on 01.03.2021
Latest download link:
https://bitbucket.org/ArcziPL/downloads/downloads/magiclantern-Nightly.2021Mar01.70D112_crop_rec_4k_mlv_lite_lossless_fps_override_focus_stack_sduhs.zip
Tested:
- 1832x1024 resolution 24&25fps: works
- 720p 50fps: works
- full-frame mode: works
- 3x crop mode (this model has it available as option in the Canon menu): works
- audio: works
- Servo-AF: works
- Single-shot-AF (triggered with half-shutter): works (if small hacks disabled)
- 14-bit lossless: works
- 12-bit lossless: works
- 8..11-bit lossless: works
- focus stacking and related functions: works
All in all it looks very promising already. Here a build, so you can use and test it as well. Please feedback. :)
This build
- is based on crop_rec_4k_mlv_lite_snd
- lossless RAW video compression is enabled (thanks to a1ex for help)
- FPS override is enabled thanks to a finding of David_Hugh (there is still a small glitch) (https://www.magiclantern.fm/forum/index.php?topic=25786.msg213467#msg213467)
- does include a custom variation of sd_uhs from theBilalFakhouri (https://www.magiclantern.fm/forum/index.php?topic=25841.msg234228#msg234228) with selectable 160/192/240MHz presets
- focus stacking and related features are enabled, was a just a matter of activating the feature as all work was already done by a1ex (https://www.magiclantern.fm/forum/index.php?topic=14309.msg197404#msg197404)
- uses #undef FEATURE_ARROW_SHORTCUTS, so this feature won't pop-up unexpectedly in LV
- does include a dualiso module with standard register addresses. For my cam I need alternative ones. You can get them here:
https://bitbucket.org/ArcziPL/downloads/downloads/70d_dual_iso_alternative_adress.zip
Disable AUDIO BEEP in Canon menu when using ML on 70D!
Great stuff @ArcziPL and Thanks @a1ex for sharing your inputs on this. Definitely will get my hands onto a 70D once again and test this build out. Miss using the swivel LiveView LCD screen.
good news for 70d users. did a short test. face tracking stil doesnt work well with this build. face tracking dont work as soon as i turn on my camera after installing this build. its like any other previous build when it comes to face tracking.
with the nightly build everything seems to work well until i hit record button. as soon as i hit the record button, face tracking freeze
i can record a video and share if anyone needs what i mean
edit: i did the nightly build test some months agao and hadnt done the nightly build test properly since a friend was using my cam. i wil do more test as i have got my camera back and report
Does turning off small hacks help?
Quote from: Danne on March 08, 2019, 05:58:56 PM
Does turning off small hacks help?
i can turn off small hacks only after activating mlv lite. face tracking dont work well with this new build even if i don activate anything
Quote from: andy kh on March 08, 2019, 05:51:09 PM
face tracking stil doesnt work well with this build. face tracking dont work as soon as i turn on my camera after installing this build. its like any other previous build when it comes to face tracking.
with the nightly build everything seems to work well until i hit record button. as soon as i hit the record button, face tracking freeze
i can record a video and share if anyone needs what i mean
Erm, yes, recording would be nice. Seeing exactly what happens could help.
It is even more interesting because... it works for me flawless. Here I show a video where I activate face tracking and record 14-bit lossless MLV afterwards; just check it out:
https://youtu.be/BMV2jdAEJyA
Quote from: andy kh on March 08, 2019, 07:13:37 PM
i can turn off small hacks only after activating mlv lite. face tracking dont work well with this new build even if i don activate anything
What you mean by "don't activate anything"? Are any modules enabled?
Please empty your SD card completely, copy all files from my build to your SD card and put it into your camera. And that's it. This will be the starting point for the investigation and for your video showing us what happens.
I've just done it on my 70D: emptied the card (with bootflag already set), copied the content of the archive, started the cam, ML loaded for the first time (no modules were activated) and recorded h264-i 1080p 25fps with face tracking. It worked same good as on the youtube video above...
http://www.youtube.com/watch?v=uL4hUGSx0Nw&feature=youtu.be (http://www.youtube.com/watch?v=uL4hUGSx0Nw&feature=youtu.be)
here is the video.
i have been doing the test in selfie mode and here is the result. no problem without ML
it seems to work well so far if it is not in selfie mode
Interesting observation -- with ML loaded the screen doesn't switch to mirror display when in "selfie mode." So it looks like the face tracking is trying to track where the face "should" be on the screen which is on the opposite side. I just took a look on my 700D and in "selfie mode" the LiveView image also does not switch to mirror mode with ML loaded. Never noticed this before. (I'm not a blogger and don't take many pictures of myself.)
Thanks a lot!
I appreciate your hard work!
And I was about to change my 70D to M1 :)
Good luck in further work!
Quote from: ArcziPL on March 07, 2019, 09:28:28 PM
Hell yeah, first 14-bit lossless MLV from 70D! 8)
(https://i.postimg.cc/qtTkyZR4/70d-first-lossless-mlv.png) (https://postimg.cc/qtTkyZR4)
It's amazing what you know about and can do with closed internals of these cams!
The one to be commented out is
//0x5002d,
If too much was commented out (all but first four lines: EDMAC channels and read/write connections) it was still stucking at the same point and additionally locking the camera. LV couldn't be exited. After changing mode between photo/video it thrown Err80.
With only this one line removed I haven't noticed any side effects yet but wasn't focusing on it. I'll test it in the next days/weeks, report back and submit a pull request if all seems to be fine.
Quote from: David_Hugh on September 11, 2018, 12:37:30 AMI could not see/find a C0F0 [6008], but a C0F0 [6014] and [6024] which had the same value. I needed to change BOTH of them in order for the image not to freeze. In this manner, I was able to lower the fps in the crop_rec module AND in regular 1080p, but I could only lower fps, not increase.
Bingo, good work David_Hugh! This opens the doors to FPS override on 70D. I already adapted fps-engio.c to always set both registers for Timer B adjustments according to your find. Result: FPS override finally works (ok, kind of, still one issue to be solved) and lossless compressor for MLV broke again. :P
fps-engio.c
@@ -45,6 +45,7 @@
#define FPS_REGISTER_A 0xC0F06008
#define FPS_REGISTER_B 0xC0F06014
+#define FPS_REGISTER_B_DUAL_PIXEL 0xC0F06024
#define FPS_REGISTER_CONFIRM_CHANGES 0xC0F06000
#define PACK(lo, hi) ((lo) & 0x0000FFFF) | (((hi) & 0x0000FFFF) << 16)
@@ -52,6 +53,7 @@
#define FPS_REGISTER_A_VALUE ((int) shamem_read(FPS_REGISTER_A))
#define FPS_REGISTER_A_DEFAULT_VALUE ((int) shamem_read(FPS_REGISTER_A+4))
#define FPS_REGISTER_B_VALUE ((int) shamem_read(FPS_REGISTER_B))
+#define FPS_REGISTER_B_DUAL_PIXEL_VALUE ((int) shamem_read(FPS_REGISTER_B_DUAL_PIXEL))
#ifdef CONFIG_7D
uint32_t *buf = NULL;
@@ -485,10 +487,7 @@
float shutter = frame_duration * (max - blanking) / max;
return (int)(1.0 / shutter * 1000);
-// ToDo: Cleanup 70D once fps override feature is fixed
-// till then use the fallback. Do it this way to have fast ettr
-// and keep frame_shutter timer enabled in consts.h
-#elif defined(FRAME_SHUTTER_TIMER) && !defined(CONFIG_70D)
+#elif defined(FRAME_SHUTTER_TIMER)
int timer = FRAME_SHUTTER_TIMER;
#ifdef FEATURE_SHUTTER_FINE_TUNING
@@ -750,6 +749,7 @@
timerB -= 1;
written_value_b = PACK(timerB, fps_reg_b_orig);
EngDrvOutFPS(FPS_REGISTER_B, written_value_b);
+ EngDrvOutFPS(FPS_REGISTER_B_DUAL_PIXEL, written_value_b);
fps_needs_updating = 0;
#if defined(NEW_FPS_METHOD)
}
@@ -1050,6 +1050,7 @@
written_value_b = 0;
EngDrvOutFPS(FPS_REGISTER_A, fps_reg_a_orig);
EngDrvOutFPS(FPS_REGISTER_B, fps_reg_b_orig);
+ EngDrvOutFPS(FPS_REGISTER_B_DUAL_PIXEL, fps_reg_b_orig);
EngDrvOutFPS(FPS_REGISTER_CONFIRM_CHANGES, 1);
}
}
@@ -1651,6 +1652,7 @@
{
EngDrvOutLV(FPS_REGISTER_A, fps_timerA_override);
EngDrvOutLV(FPS_REGISTER_B, fps_timerB_override);
+ EngDrvOutLV(FPS_REGISTER_B_DUAL_PIXEL, fps_timerB_override);
EngDrvOutLV(FPS_REGISTER_CONFIRM_CHANGES, 1);
}
fps_timers_updated = 1;
features.h
@@ -11,7 +11,7 @@
// Tried it for a felt hundred hours
// TIMER_B has untraceable problems
// Using TIMER_A_ONLY causes banding / patterns
-#undef FEATURE_FPS_OVERRIDE
+// #undef FEATURE_FPS_OVERRIDE
/* see comments in lens.c */
#undef FEATURE_FOLLOW_FOCUS
internals.h
@@ -125,8 +125,11 @@
/** FIO_RenameFile works **/
#define CONFIG_FIO_RENAMEFILE_WORKS
-// FPS updates from evf state do not work atm on 70D
-// #define CONFIG_FPS_UPDATE_FROM_EVF_STATE
+// FPS override: change timers from EVF state */
+#define CONFIG_FPS_UPDATE_FROM_EVF_STATE
#define CONFIG_REC709
The cam doesn't lock-up anymore and doesn't show any funny effect on LCD when trying FPS override in LV. But the overriden FPS value shortly jumps to the default one every 2s. I think ML task does something with this interval. It also jumps shortly to default FPS for every navigation key pressed when in video tab. This is with no modules loaded. Here see how it looks:
https://youtu.be/ZnNLZ6sgp7Y
But you can nicely increase LCD visibility at night and MLV recording also works with the overriden FPS. However bitrate shown during recording is wrong, it shows just bitrate which would be true with default FPS. And also recording time is counting slower. Seems that the mlv_lite module doesn't get the right overriden FPS value for calculations.
Which function is called approx. every 2s when staying in menu? I must analyze it in details to see what causes the short glitch. Actually the first question shall be: does this value really change only for a short moment when ML is doing something or does ML
realize it only after 2s from the moment when other piece of code changes it? As LV is showing permanent FPS override I hope for the first one.
During initial testing, the FPS was also getting back to default value after few first frames during recording. This seems to not happen anymore, I believe after changing the FPS update mode by
#define CONFIG_FPS_UPDATE_FROM_EVF_STATE in internals.h. But I haven't tested enough.
Here a build, so you can test as well. :) Feedback very welcome!
https://bitbucket.org/ArcziPL/magic-lantern/downloads/magiclantern-Nightly.2019Mar15.70D112_crop_rec_4k_mlv_lite_lossless_fps_override_experimental.zip
And for everyone, who gets "ISOless err xx" when trying to use DualISO, here a modified module with alternative adresses (just move it to ML/modules):
https://bitbucket.org/ArcziPL/magic-lantern/downloads/70d_dual_iso_alternative_adress.zip
As already mentioned above, enabling FPS override caused lossless compressor to break again. I had to remove one more resource to make it work again.
+ else if (is_camera("70D", "*"))
+ {
+ uint32_t resources[] = {
+ 0x00000 | edmac_channel_to_index(edmac_write_chan),
+ 0x10000 | edmac_channel_to_index(edmac_read_chan),
+ 0x30001, /* Read connection 1 (uncompressed input) */
+ 0x2002d, /* Write connection 45 (compressed output) */
+ //0x20016, /* Write connection 22 (for WR2 - not used) */
+ 0x50034,
+ //0x5002d, /* workaround, TTL_Prepare stucks otherwise if called in LV */
+ //0x50010, /* workaround, TTL_Prepare stucks otherwise if compiled with FEATURE_FPS_OVERRIDE defined */
+ 0x90001,
+ 0x230000,
+ 0x160000,
+ 0x260000,
+ 0x260001,
+ 0x260002,
+ 0x260003,
+ };Quote from: a1ex on March 15, 2019, 06:10:04 AM
Then, 70D also needs FRAME_SHUTTER_BLANKING_READ (i.e. the memory address of the shutter blanking register, as printed in adtg_gui). On some models, this address is a moving target, though, so we need to find another way to retrieve it.
On my cam it is different than the already present entry in
crop_rec_4k_mlc_* which is commented out because of some reason.
// see "Malloc Information"
// #define FRAME_SHUTTER_BLANKING_ZOOM (*(uint16_t*)0x40452180) // ADTG register 805f
// #define FRAME_SHUTTER_BLANKING_NOZOOM (*(uint16_t*)0x40452184) // ADTG register 8061
#define FRAME_SHUTTER_BLANKING_READ (lv_dispsize > 1 ? FRAME_SHUTTER_BLANKING_NOZOOM : FRAME_SHUTTER_BLANKING_ZOOM)
#define FRAME_SHUTTER_BLANKING_WRITE (lv_dispsize > 1 ? &FRAME_SHUTTER_BLANKING_ZOOM : &FRAME_SHUTTER_BLANKING_NOZOOM)BTW: why does
FRAME_SHUTTER_BLANKING_WRITE use swapped order of ZOOM and NOZOOM registers?! For other cams it looks same...
On my cam I see the following adresses:
805f: 0x404e6180
8061: 0x404e6184How to see if the shutter_blanking is working or not at all? I've tried uncommenting and replacing with my two addresses but couldn't tell any difference...
goo job ArcziPL. this is fantastic
Great work @ArcziPL & @dfort! Also thanks @a1ex for pointers to get this 70D revived yet once again!
[Here was some pointless whining but I removed it, as it was pointless. I'm on track, analyzing what happens and there will be no whining anymore, promise. :)]
I see that fps_get_current_x1000() is called several times per second in video LV and only in 1 out of 4 cases returns the expected (=override) value. Three others are the default FPS. Need to find out if it's Canon or ML, who keeps overriding the FPS back to default (or maybe just the readback is wrong?).
Next step was to keep FPS override turned off and call fps_setup_timerA() + fps_setup_timerB() once from run_test(), followed by fps_get_current_x1000().
Result without CONFIG_FPS_UPDATE_FROM_EVF_STATE:
- 700D: after one frame the FPS is back to default
- 70D: same
Result with #define CONFIG_FPS_UPDATE_FROM_EVF_STATE:
- 700D: keeps FPS after one call
- 70D: LV and h264 recording stay overriden but fps_get_current_x1000() returns default FPS
Next step: tried to strip vsync_func() from everything but calling fps_update_timers_from_evfstate() but it didn't change anything.
Next step: try to reduce fps_task() to the absolute required minimum. This is still ongoing.
@ArcziPL thank you for your valuable work !
Hi, everyone. I just got a 70D and I want to help out with testing. I tried two crop_rec_4k builds on it and while they work, the camera stops recording and throws an Err 70 after shooting for a while. Here are the builds I tried and the crash logs.
magiclantern-Nightly.2019Mar07.70D112_crop_rec_4k_mlv_lite_lossless:ASSERT: FALSE
at ./ASIF/AsifState.c:448, ASIF:ff2bab88
lv:0 mode:3
ASIF stack: 191760 [191838-190838]
0xUNKNOWN @ ef80:191830
0xUNKNOWN @ 3db8c:191808
0x0003D884 @ ff116e6c:1917e0
0xUNKNOWN @ 3d8b4:1917d0
0xUNKNOWN @ 3d93c:1917b0
0x00001900 @ ff2bab84:191798
0x0044C46C @ 44c4ec:191760
Magic Lantern version : Nightly.2019Mar07.70D112
Mercurial changeset : 02e5918a6ed5+ (crop_rec_4k_mlv_lite_snd)
Built on 2019-03-07 20:10:24 UTC by artur@Artur-VirtualBox.
Free Memory : 215K + 2380KThis Mar07 build seems like the more stable of the two. I had only 'mlv_lite', 'mlv_snd' and 'sd_uhs' modules enabled, using the SD overclock, 14-bit lossless at fullres, 16:9, ISO100. The SD card is SanDisk Extreme Pro 95MB/s, 128GB.
magiclantern-crop_rec_4k_mlv_snd.2019Mar14.70D112:ASSERT: FALSE
at ./ASIF/AsifState.c:448, ASIF:ff2bab88
lv:0 mode:3
ASIF stack: 191760 [191838-190838]
0xUNKNOWN @ ef80:191830
0xUNKNOWN @ 3db8c:191808
0x0003D884 @ ff116e6c:1917e0
0xUNKNOWN @ 3d8b4:1917d0
0xUNKNOWN @ 3d93c:1917b0
0x00001900 @ ff2bab84:191798
0x0044C478 @ 44c57c:191760
Magic Lantern version : crop_rec_4k_mlv_snd.2019Mar14.70D112
Mercurial changeset : 32ac2f15f16c+ (crop_rec_4k_mlv_snd_experiments)
Built on 2019-03-14 22:49:12 UTC by [email protected].
Free Memory : 300K + 1800KASSERT: FALSE
at ./ASIF/ASIF.c:383, raw_rec_task:ff1176b0
lv:0 mode:3
raw_rec_task stack: 1e3ed0 [1e3fe0-1e2fe0]
0x00C27538 @ c2d740:1e3f50
0xUNKNOWN @ c2756c:1e3f40
0x00C3086C @ c309a8:1e3f38
0xFF11758C @ c308e0:1e3f20
0x00001900 @ ff1176ac:1e3f08
0x0044C478 @ 44c57c:1e3ed0
Magic Lantern version : crop_rec_4k_mlv_snd.2019Mar14.70D112
Mercurial changeset : 32ac2f15f16c+ (crop_rec_4k_mlv_snd_experiments)
Built on 2019-03-14 22:49:12 UTC by [email protected].
Free Memory : 300K + 1801KThe Mar14 build didn't have the 'sd_uhs' module, so I lowered the resolution to get >40MB/s writes (everything else was the same), but alas, it didn't work and I still got an Err 70 after even less recording time, than the other build.
EDIT: Now the Mar07 build started giving me Err 70 after just seconds of recording, even in 11-8 bit and 1:2.35 ratio.. I was worried that my new (well, second hand) camera had issues, but taking pictures and shooting h.264 works perfectly fine.
If there's something I could try out, let me know.
You know about Canon's service advisory about Err70 on 70D? (https://www.usa.canon.com/internet/portal/us/home/support/product-advisories/detail/service%20notice%20eos%2070d%20error%2070%20or%20error%2080)
Quote from: Walter Schulz on March 28, 2019, 04:13:07 PM
You know about Canon's service advisory about Err70 on 70D? (https://www.usa.canon.com/internet/portal/us/home/support/product-advisories/detail/service%20notice%20eos%2070d%20error%2070%20or%20error%2080)
Now that you mention it, I think I've read something about that, but I've obviously forgotten about it since. My camera's serial number begins with 24, though. The Err 70 only appears when I record RAW video and I don't even have to turn off the camera or reinsert the battery. After ML's finished writing the crash log, I simply half-press the shutter and the error clears, as if it never happened. This is why I suspect it has something to do with ML.
ERR70 can be triggered by over 1000 different conditions. Some of them are caused by ML, others are hardware issues.
This one looks like something related to sound recording. Is the error still there with the regular nightly build for 70D from the download page? If the error is not present with the regular build, it must be something in the experimental builds.
To narrow down, is the error present with...
- ML defaults (Prefs -> Card settings) and H.264 recording?
- ML defaults and only mlv_rec (without sound)?
- ML defaults and only mlv_lite (without sound)?
- ML defaults and only mlv_rec + mlv_snd?
- ML defaults and only mlv_lite + mlv_snd? nevermind
Unlikely to help, but you could also try restoring Canon settings.
Quote from: a1ex on March 28, 2019, 04:45:33 PM
ERR70 can be triggered by over 1000 different conditions. Some of them are caused by ML, others are hardware issues.
This one looks like something related to sound recording. Is the error still there with the regular nightly build for 70D from the download page? If the error is not present with the regular build, it must be something in the experimental builds.
To narrow down, is the error present with...
- ML defaults (Prefs -> Card settings) and H.264 recording?
- ML defaults and only mlv_rec (without sound)?
- ML defaults and only mlv_lite (without sound)?
- ML defaults and only mlv_rec + mlv_snd?
- ML defaults and only mlv_lite + mlv_snd?
Unlikely to help, but you could also try restoring Canon settings.
Ok, so with the lastest nightly (magiclantern-Nightly.2018Dec24.70D112), this is what happens:
- ML defaults and only mlv_lite + mlv_snd -
module clash error - no go- ML defaults and only mlv_rec + mlv_snd -
records for a few seconds and then Err70- ML defaults and only mlv_rec (without sound) -
I recorded 17 mins of raw footage, no problem (battery drained and I had to stop)- ML defaults and only mlv_lite (without sound) -
recorded raw footage, until my 128GB card filled up - a little over 51 mins - no problemOf course, this nightly not having lossless or sd overclocking, I used something like 1600x600 (1:2.67), if that matters at all. So, it does indeed look like the sound module is causing the issue. Also, I should mention, that when I tested the Mar07 and Mar14 builds, I didn't use the default settings - I turned off small hacks, allowed screen mirroring and used LV Digic peaking with sharpening (that's all, I think). I'll now test the Mar07 and Mar14 builds again, but with the default settings, with and without sound, and report back.
Alright. I assume the sound recording feature works on 70D, otherwise it would have been reported many times.
Not sure what to recommend - maybe checking the same ML card in two different 70Ds, both reset to Canon defaults and running at exactly the same settings, to exclude a hardware issue?
Or, I could try to debug mlv_snd, but... remote debugging is going to be time-consuming for both of us. I might be able to do that on April 7/8 (unless unexpected stuff happens meanwhile), so please remind me then if you can't find what's going on.
I don't have another 70D to test on, but I'll continue testing the different builds with different settings and when I have something, I'll report back.
I hv been shooting 14 bit lossless mlv lite with sound and hv no issues so far
Quote from: mvrck on March 28, 2019, 06:25:13 PM
- ML defaults and only mlv_lite + mlv_snd - module clash error - no go
- ML defaults and only mlv_rec + mlv_snd - records for a few seconds and then Err70
- ML defaults and only mlv_rec (without sound) - I recorded 17 mins of raw footage, no problem (battery drained and I had to stop)
- ML defaults and only mlv_lite (without sound) - recorded raw footage, until my 128GB card filled up - a little over 51 mins - no problem
Hi mvrck, thank you for extensive testing! 1h of recording without an error is a pretty good indicator that there should be no problem with the hardware of your cam (but still not a real proof).
Regarding the sound itself it's interesting, as Mar07 and Mar14 builds are based on two different branches (
crop_rec_4k_mlv_lite_snd and
crop_rec_4k_mlv_snd), which implement sound support in different ways. And they both crash for you...
I have four ideas:
1. There should be some audio settings in Canon menu as well -> auto gain optimizer and wind filter, if I recall correctly. Try to play around with them and see if it has any effect on the crashes.
2. Use the camera without magic lantern, record normal h264 with sound (standard, official feature of this camera). Does it crash then?
3. Use the Mar07 or Mar14 builds with sd_uhs+lossless and disable sound by deactivating mlv_snd. I wonder if these builds also will stop crashing...
4. Restore camera factory settings over Canon menu.
Regarding the other camera settings: I used only 1080p/25fps setting from Canon menu, resulting in 1832x1024 RAW image size. Small hacks: in last year I used the default setting, in last days disabled. Screen mirroring: default. DIGIC peaking: sharpening.
OK, here are the results from my testing.
Mar07 Build
mlv_lite
1776x1000, 14-bit lossless, 16:9
Preview: Realtime
40 min. - OK
--------------------------------
mlv_rec
1792x716, 10bpp, 2.50:1
Global Draw: Allow
40 min. - OK
--------------------------------
mlv_lite + sd_uhs
1832x1024, 14-bit lossless, 16:9
Preview: Realtime
40 min. - OK
--------------------------------
mlv_rec + sd_uhs
1824x1026, 10bpp, 16:9
Global Draw: Allow
40 min. - OK
--------------------------------
mlv_rec + mlv_snd
1792x716, 10bpp, 2.50:1
Global Draw: Allow
Err70, after a few seconds
--------------------------------
Mar14 Build
mlv_lite
1776x1000, 14-bit lossless, 16:9
Preview: Realtime
40 min. - OK
--------------------------------
mlv_rec
1792x716, 10bpp, 2.50:1
Global Draw: Allow
40 min. - OK
--------------------------------
mlv_rec + mlv_snd
1792x716, 10bpp, 2.50:1
Global Draw: Allow
Err70, after a few seconds
--------------------------------
In all the tests I used ISO100, 24 FPS. A run the first test for 40 minutes and decided to run all other tests for as long, not just for consistency, but also to test the camera's stability. All tests were done back to back, using two batteries - one being used, while the other was being charged. The camera was pretty warm throughout, but didn't pass 58*C. According to Canon, Err70 occurs with prolonged use and supposed heat build-up, so I had to test for that. I don't know anything that heats up cameras and drains batteries quite like shooting RAW video, so I guess my 70D passed the test. Anyway, the result is that the mlv_snd module always produces Err70, when activated, unfortunately.
@ArcziPL
1. I tried setting the audio to manual and turning on and off the wind filter and attenuator, but it didn't help
2. There's absolutely no problem with the camera taking pics and shooting h.264 with or without ML loaded
3. I think my test results answer that one :)
4. Tried that, too - doesn't work
http://www.youtube.com/watch?v=KtYcu_YeApI&feature=youtu.be (http://www.youtube.com/watch?v=KtYcu_YeApI&feature=youtu.be)
here is a video showing of my test that mlv lite(lossless 14 bit) with sound works but get some error msg on screen when i record mlv with sound
i hope someone wil understand better by watching the video
If not tested yet I think the latest changes in mlv_snd together with mlv_lite from g3gg0 should be tested. I think it´s in this branch:
crop_rec_4k_mlv_snd. Not sure what branch is working with 70D or not though but anyhow.
Something I noticed on the video is that you have both mlv_rec and mlv_lite modules loaded. Don't don't that! Turn on as few modules as possible when testing and definitely not two modules that do basically the same thing.
I believe that the latest commit for the 70D is this one (https://bitbucket.org/hudson/magic-lantern/commits/91593cabf6c9a97541b7f7de5f633b21ff75ad83) on the crop_rec_4k branch.
thanks dford
now its working perfect. no more problem with audio in mlv rec.
i can find the audio setting in mlv rec after deactivating mlv lite module
So, a funny thing happened. While doing some additional testing, the sound recording started working out of nowhere, as it seems. I did have some issues and I did get one Err70 out of all my extra tests and it was the strangest one yet.
Mar07 Build
mlv_lite + mlv_snd + sd_uhs
1832x1024, 14-bit lossless, 16:9
Preview: Realtime
Small hacks: ON
Auto Mirroring: Don't allow
15 min. - Video OK, sound OK, NO ERRORS!
Additionally tested later:
45 min. - Video OK, sound OK, NO ERRORS!
50 min. at ISO200 - Video OK, sound OK, NO ERRORS!
47 min. at ISO400 - Video OK, sound OK, NO ERRORS!
----------------------------
mlv_rec + mlv_snd + sd_uhs
1824x1026, 10bpp, 16:9
Global Draw: Allow
15 min. - Video OK, sound OK, NO ERRORS!
Additionally tested later:
15 min. - Video OK, sound OK, NO ERRORS!
The mlv_snd module was loaded and turned on, but the sound meter bars didn't show up.
Mar14 Build
mlv_rec + mlv_snd
1792x716, 10bpp, 2.50:1
Global Draw: Allow
15 min. - Video OK, sound OK, but Err70
When I pressed stop at the 15th minute, the recording timer froze, the top display said "Busy" and a few seconds later.. guess what.. Err70! Had to take out my battery this time. The MLV file had sound, though.
mlv_lite + mlv_snd
1600x900, 14-bit lossless, 16:9
Preview: Realtime
Small hacks: ON
Auto Mirroring: Don't allow
15 min. - Video OK, sound OK, NO ERRORS!
Everything went as normal: audio meter bars showing up and working, camera reacting normally, when starting and stopping recording. I should mention, that I tried recording in 1776x1000 with everything alse the same, but the camera stopped after a couple of minutes. It stopped in a normal manner, like when the resolution is just too high - no unusual errors. When I tested that build before, with the higher resolution, it worked for 40 mins., but now with mlv_snd also loaded, it looks like it can't keep up.
Doesn't make much sense to me. In all tests I kept ML at default settings with only the modules, mentioned above loaded. I don't think Canon's menu settings have an effect on RAW recording, but most were kept at defaults (incl. audio), except: image recording set to RAW only, video recording format set to 24fps, IPB, colour profile set to Faithful (from Auto), Beeping turned off. Can't think of anything else. The way I switched from build to build for testing, was without uninstalling ML, just deleting one build's files from the card and copying the other build's onto it. I have both builds with my settings backed up in folders.
I'll keep testing. If anyone has any insight, please share.
Quote from: mvrck on March 29, 2019, 09:05:04 PMI don't think Canon's menu settings have an effect on RAW recording, but most were kept at defaults (incl. audio), except: image recording set to RAW only, video recording format set to 24fps, IPB, colour profile set to Faithful (from Auto), Beeping turned off. Can't think of anything else.
That's the moment, when the bell rang in my head. Was beeping turned off also during your initial tests when sound didn't work at all?
If you take look at the first post in this topic:
Quote from: nikfreak on January 15, 2015, 12:22:15 AM
What's not working:
Check also Changelog history below for all details and disabled features...
(...)
- Disable "Beep" (or set "Touch to...") in Canon menu if you are using MLV_SOUND. Not following this advice will lead to ERR70 crash while mlv recording. (http://www.magiclantern.fm/forum/index.php?topic=14309.msg153275#msg153275)
Every single detail might count. You are doing it very well, mvrck, testing and describing keeping all tiny details in mind!
Quote from: ArcziPL on March 29, 2019, 09:28:09 PM
That's the moment, when the bell rang in my head. Was beeping turned off also during your initial tests when sound didn't work at all?
If you take look at the first post in this topic:
Every single detail might count. You are doing it very well, mvrck, testing and describing keeping all tiny details in mind!
I think I still had it on, when I did the first tests. I can't remember exactly when I disabled it, though. I didn't think such a seemingly inconsequential setting could have such, well, consequences. I'll try enabling it back to see what happens.
EDIT: Yup, with "Beep" enabled, I get 5-20 secs. before an Err70. Thank you very much, ArcziPL, for pointing this out!
So is variable FPS working? what setting and is there a build I can test. Cheers.
Quote from: ShootMeAlready on March 31, 2019, 06:56:03 PM
So is variable FPS working? what setting and is there a build I can test. Cheers.
Reply # 3291
with the fps override enable now i can shoot 4k with my 70D
i wil share a video soon. i may not shoot in 4k but shoot in 3k since rendering takes so much time
http://www.youtube.com/watch?v=_GCCJ2y7ch8&feature=youtu.be (http://www.youtube.com/watch?v=_GCCJ2y7ch8&feature=youtu.be)
fps override not jumping to default
Quote from: andy kh on April 05, 2019, 07:20:49 AM
http://www.youtube.com/watch?v=_GCCJ2y7ch8&feature=youtu.be (http://www.youtube.com/watch?v=_GCCJ2y7ch8&feature=youtu.be)
fps override not jumping to default
Wow! Andy, how did you do that? Which build, which modules loaded, how do you manage to increase resolution to 3k and make FPS not jump back?
Quote from: ArcziPL on April 05, 2019, 08:07:02 AM
Wow! Andy, how did you do that? Which build, which modules loaded, and make FPS not jump back?
its your build. i use sd_uhs and script from danne. i play around with shutter range and timer A. i have tested with different fps like 16,18,20,21 as per my need and all work fine without jumping
its in 5X Zoom mode so i can go upto 3.5k. little problem with the preview as the "framing" in preview dont work sometimes but "realtime" always work
(https://i.ibb.co/6m3vY6T/1.png) (https://ibb.co/6m3vY6T)
Quote from: andy kh on April 05, 2019, 08:31:57 AM
its your build. i use sd_uhs and script from danne.
Can you point me to this script please?
Quote from: ArcziPL on April 05, 2019, 08:33:06 AM
Can you point me to this script please?
the script has nothing to do with fps. i use it to autorun the sd_uhs when i start my camera
So the "playing around with shutter range and timer A" you do with adtg_gui?
Quote from: ArcziPL on April 05, 2019, 08:51:37 AM
So the "playing around with shutter range and timer A" you do with adtg_gui?
No
but by goin to advance option in fps override
Quote from: andy kh on April 05, 2019, 09:02:06 AM
but by goin to advance option in fps override
Can you show exact settings in that menu? For me it rather doesn't work. Timer B and shutter time are jumping all the time, even if I try to change values.
BTW: dfort, I tried your magiclantern-crop_rec_4k_70D_crop_rec_mo.2019Mar29.70D112.zip (copying only crop_rec.mo to my build)
mv720 3x3 binning option can be then activated and results in such footage:
(https://i.postimg.cc/T3GPsD2Y/dfort-70d-crop-rec-mo.jpg)
Not really as expected but seeing your crop_rec.mo already doing something and what andy_kh managed to achieve, it looks like we are just few steps from presets on 70D.
I don't know how to bite it at the moment. Wanting to enable the 720 3x3 mode I
changed in adtg_gui
@@ -1077,8 +1077,8 @@
{
ADTG_WRITE_FUNC = 0x47144; //"[REG] @@@@@@@@@@@@ Start ADTG[CS:%lx]"
CMOS_WRITE_FUNC = 0x475B8; //"[REG] ############ Start CMOS"
- ENGIO_WRITE_FUNC = 0xFF2B2460; // from stubs
- ENG_DRV_OUT_FUNC = 0xFF2B2148;
+ //ENGIO_WRITE_FUNC = 0xFF2B2460; // from stubs
+ //ENG_DRV_OUT_FUNC = 0xFF2B2148;
}
else return CBR_RET_ERROR;
changed in consts.h
@@ -255,4 +255,6 @@
// see "Malloc Information"
// #define FRAME_SHUTTER_BLANKING_ZOOM (*(uint16_t*)0x40452180) // ADTG register 805f
// #define FRAME_SHUTTER_BLANKING_NOZOOM (*(uint16_t*)0x40452184) // ADTG register 8061
+#define FRAME_SHUTTER_BLANKING_ZOOM (*(uint16_t*)0x404e6180) // ADTG register 805f
+#define FRAME_SHUTTER_BLANKING_NOZOOM (*(uint16_t*)0x404e6184) // ADTG register 8061
@@ -258,6 +260,6 @@
-// #define FRAME_SHUTTER_BLANKING_READ (lv_dispsize > 1 ? FRAME_SHUTTER_BLANKING_NOZOOM : FRAME_SHUTTER_BLANKING_ZOOM)
-// #define FRAME_SHUTTER_BLANKING_WRITE (lv_dispsize > 1 ? &FRAME_SHUTTER_BLANKING_ZOOM : &FRAME_SHUTTER_BLANKING_NOZOOM)
+#define FRAME_SHUTTER_BLANKING_READ (lv_dispsize > 1 ? FRAME_SHUTTER_BLANKING_NOZOOM : FRAME_SHUTTER_BLANKING_ZOOM)
+#define FRAME_SHUTTER_BLANKING_WRITE (lv_dispsize > 1 ? &FRAME_SHUTTER_BLANKING_ZOOM : &FRAME_SHUTTER_BLANKING_NOZOOM)
#define MALLOC_STRUCT 0xAFBB8
#define MALLOC_FREE_MEMORY (MEM(MALLOC_STRUCT + 8) - MEM(MALLOC_STRUCT + 0x1C)) // "Total Size" - "Allocated Size"
but the 720 3x3 option still didn't appear in crop_rec submenu. 70D is defined as is_basic, so I thought it should be enough.
Quote from: ArcziPL on April 05, 2019, 09:13:58 AM
Can you show exact settings in that menu?
(https://i.ibb.co/kBSJ4n2/18fps.jpg) (https://ibb.co/kBSJ4n2)
flipcoin (https://freeonlinedice.com/)
(https://i.ibb.co/9gn9960/21fps.jpg) (https://ibb.co/9gn9960)
Quote from: ArcziPL on April 05, 2019, 09:21:30 AM
BTW: dfort, I tried your magiclantern-crop_rec_4k_70D_crop_rec_mo.2019Mar29.70D112.zip (copying only crop_rec.mo to my build) mv720 3x3 binning option can be then activated and results in such footage:
there is a very easy solution for this problem
720mv 3X3 bining 50fps from dfort's build
(https://i.ibb.co/4PLHMsH/Whats-App-Image-2019-04-05-at-13-01-27-2.jpg) (https://ibb.co/4PLHMsH)
Wow, you timer settings do work! You managed 3k on 70D. :o Thanks a lot!
Quote from: andy kh on April 05, 2019, 09:22:27 AM
there is a very easy solution for this problem
Can you elaborate a bit more...? I tried using the complete build from dfort but the cam freezes immediately after powering on...
dfort, can you combine Andy's discovery with crop_rec? You seem to be the right person even without having the cam... :)
Quote from: ArcziPL on April 05, 2019, 09:35:36 AM
Can you elaborate a bit more...? I tried using the complete build from dfort but the cam freezes immediately after powering on...
i use your build and replace crop_rec.mo with dfort's build and wala
for those lines the easiest solution is just scrol to 24fps once from 50fps in canon menu and scroll back to 50fps and wala
i think i have a problem with sd_uhs hack with it. i wil do some more test later as im goin out now....
720mv 3X3 bining 50fps
(https://i.ibb.co/Yhrt6bH/1.png) (https://ibb.co/Yhrt6bH)
Hmm, now I see that 3k is already possible without FPS override (just the datarate is high) but in 5x magnification. Up to now I believed 3x zoom = 5x magnification with fixed live view but apparently it's not like that.
And the FPS timer B still jumps to the original value for me. It just has less influence on FPS if timer A is set to a high value.
Quote from: ArcziPL on April 05, 2019, 11:42:56 AM
Hmm, now I see that 3k is already possible without FPS override (just the datarate is high) set to a high value.
fps override is for longer recording time
My 70D USES magiclantern- crop_rec_4k_70d_crop_rec_mo.2019mar29.70d112.Cannot use MLV _lite.The clear button cannot be used to trigger the ML menu when entering movie mode.MLV_rec is normal.Sorry, English is not my native language, maybe I didn't express it accurately enough
Quote from: ArcziPL on March 07, 2019, 10:27:17 PM
Thanks a1ex once again. Your knowlegde is amazing.
Tested:
- 1832x1024 resolution 24&25fps: works
- 720p 50fps: works
- full-frame mode: works
- 3x crop mode (this model has it available as option in the Canon menu): works
- audio: works
- Servo-AF: works
- Single-shot-AF (triggered with half-shutter): works (if small hacks disabled)
- 14-bit lossless: works
- 12-bit lossless: works
- 8..11-bit lossless: works
All in all it looks very promising already. Here a build, so you can use and test it as well. Please feedback. :)
https://bitbucket.org/ArcziPL/magic-lantern/downloads/magiclantern-Nightly.2019Mar07.70D112_crop_rec_4k_mlv_lite_lossless.zip
This build
- is based on crop_rec_4k_mlv_lite_snd
- does include a custom variation of sd_uhs module: only one setting is used, benchmark is run once upon activation
- uses #undef FEATURE_ARROW_SHORTCUTS, so this feature won't pop-up unexpectedly in LV
- doesn't include dualiso module, as my cam uses alternative adresses of some registers and I've adapted it already. If you need it, take it from any other working build.
Hey yall, haven't checked forums in ages, used old build of ML, used MLrawviewer and was quite happy with quality of recordings. Shot 1600x900 MLV raw video, stretched to 1080p and that was that. Now I found your ridiculously awesome build and was blown away by what I found. Different bitrates! Now im shooting at even higher resolution for 30s using 10bpp. 30 seconds instead of 13. And I didnt see much of a drop in quality, but I guess that would stand out in post processing. Also, tried mlv_snd, which also helps. And 60fps. It only shoots for 11 seconds for my desired resolution of 900p, but man. I wanted to upgrade to sony a7 just for slow mo footage, but now it seems, I can stay with my beloved 70D longer. It's currently 2am in my timezone and I'm just as happy as when I got my camera.
I expect a shoot next next week and this upgrade is just what I needed.
Need a bit more testing, if I find time ill do just that.
Try 14bit or 12bit lossless raw instead of 10bit. You wil be able to record continous.
You can shoot 2.5k continous in 5X with the ush_sd hack
@ Andy KH
Would You Please provide info on which build You use & Detailed Settings
to get "2.5k continous in 5X with the ush_sd hack" ~
ORR ~ DeanB
As of now i hv two builds in two different cards. One is build by Arczipl. This build doesnt seem to work the uhs sd hack in my initial test so i replace with danne's ush sd hack that run with lua script. It give me about 58mb/s write speed
And one important thing is setting the fps override to your desired fps is little tricky in 70D. You cant increase but decrease. After setting the desired fps, i need to adjust it wit timer A otherwise it wil keep jumping to original every few seconds.
I have another build by danne but i need to do more test for this build
Details Please > Build Names & Dates. Also What Settings. Thank You .
https://bitbucket.org/ArcziPL/magic-lantern/downloads/magiclantern-Nightly.2019Mar15.70D112_crop_rec_4k_mlv_lite_lossless_fps_override_experimental.zip
My settings are 12bit or 11bit lossless@ 23.989 with uhs sd hack enable and i dont use the sd uhs hack from this build.
As i have mention fps override is little tricky you need to adjust with timer A. I wil try to make a video tutorial tomorow as im away from home atm
@ Andy
Thanks a bunch, I'll pay attention tomorrow.
@Danne
Just tried "crop_rec_4k_mlv_snd_isogain_1x3_presets_2019May12.70D112", Only Rec's less than 1sec >
SDCard Bench Test shows around 19MB/s, Write & Errors, Read ~
(https://i.ibb.co/VTfLHQq/2-5k-continous-setting.jpg) (https://ibb.co/VTfLHQq)
(https://i.ibb.co/2Sj39c8/2-5k-recording-mlvapp.png) (https://ibb.co/2Sj39c8)
@OlRivrRat these are my settings. i can go little higher than 2.5k and shoot continous
just to show you i recorded for 10 mins
i have to turn off crop rec in modules otherwise i always get realtime preview
Some interesting results > Using "magiclantern-Nightly.2019Mar07.70D112_crop_rec_4k_mlv_lite_lossless"
+ "08May19 "lua.mo" + "08May19 "sd_uhs.mo" + "01Apr19 "SDoverclock.lua" >
Start Cam in Stills, go direct to ML Benchmark OR Start Cam in Stills, go LiveView On then Off, Then ML Benchmark >
Get > 66.1MB/s Write 72.0MB/s Read
Start Cam in Stills & Go LiveView On, Then ML Benchmark >
Get > 19.4MB/s Write 21.1MB/s Read
Start Cam in Stills & Go to Vid'Mode OR Start Cam in Vid'Mode, Then ML Benchmark >
Get > 19.5MB/s Write 21.1MB/s Read
I tried Andy build see May 12th post, reply3342
Not able to get steady 23.9 fps. I put it in 1080 fps 30 and 5X, and try to fps override, but it jumps around 29.9.
What val for timer A? and Timer B? to prevent?
I was getting fast rise in cpu from 41degress to 50 degrees, at 2.5k aspect 2:35.1 and 29.9fps flcikering
- which modules loaded(mlv_lite,_rec_play_snd, file_manager, crop_rec, and uhs_sd???)
In general how does one ensure fps override is on menu??? It seems I lose it from menu???
https://bitbucket.org/hudson/magic-lantern/commits/b54cb4bc17ac/
(https://i.ibb.co/PhD7cG8/2-8k.png) (https://ibb.co/PhD7cG8)
another example of 2.8k continous 10bits lossless 23.989fps
There seems to be a disconnect here. Walter is saying dont fps override, and Andy is doing it to get 2.5k continuous @2:35.1 with 5X. Am I missing something?
The fps at 30, happens automatically whenever you select 5X.
So clearly Andy has a trick to get the fps on menu & adjusted back to 23.9 fps.
Whats up wid that?
Think he goes into advanced and change the A-timer. Try that.
Quote from: Danne on May 14, 2019, 02:42:31 PM
Think he goes into advanced and change the A-timer. Try that.
yeah danne is right. you can lower to any fps by changing the timer A
i wish timer B also works
Quote from: andy kh on May 12, 2019, 06:00:04 PM
As of now i hv two builds in two different cards. One is build by Arczipl. This build doesnt seem to work the uhs sd hack in my initial test so i replace with danne's ush sd hack that run with lua script.
It works for me flawless. What do you do exactly?
You have to go to Debug menu and activate it manually. Combining my build with Dannes autorun script won't work out of the box, as they were not meant to work together. However, you can adapt the script easily -> just replace the menu option name "MAY CAUSE DATA LOSS" with "160MHz fixed". That's what appears in the menu, to easily distinguish which version is loaded.
@Arczipl i did exactly wat you said but it didnt work. I think it crash twice if i remember
I replace the uhs sd and the lua in modules and add his script and it works flawlessly. I need not activate manually everythime i start my camera
I only find fps override on exper build,
magiclantern-Nightly.2019Mar15.70D112_crop_rec_4k_mlv_lite_lossless_fps_override_experimental
The problem is that at 2.5k it only runs for 5s, or 150 frames. There is no overclocking ??? to change the write speed. Also the Timer , will not take 5X back to 23.9 fps.
So what gives?
Quote from: ShootMeAlready on May 15, 2019, 03:37:00 AM
I only find fps override on exper build,
magiclantern-Nightly.2019Mar15.70D112_crop_rec_4k_mlv_lite_lossless_fps_override_experimental
The problem is that at 2.5k it only runs for 5s, or 150 frames. There is no overclocking ???
you read what ArcziPL just said. you have to go to debug in Ml menu scroll down...
you wil see something like this "MAY CAUSE DATA LOSS" with "160MHz fixed
press ok to activate.
Quote from: ShootMeAlready on May 15, 2019, 03:37:00 AM
to change the write speed. Also the Timer , will not take 5X back to 23.9 fps.
first go to 5X and set to your desired fps
Regarding My earlier Post #3346 > Even though it seems that No One Cares >
Virtually Identical results using > "magiclantern-Nightly.2019Mar15.70D112_crop_rec_4k_mlv_lite_lossless_fps_override_experimental"
+ "08May19 "lua.mo" + "08May19 "sd_uhs.mo" + "01Apr19 "SDoverclock.lua" >
Using > "crop_rec_4k_mlv_snd_isogain_1x3_presets_2019May12.70D112" >
The 1st 2 Scenarios are Virt' Same but >
Start Cam in Stills & Go to Vid'Mode OR Start Cam in Vid'Mode, Then ML Benchmark >
Get > 19.5MB/s Write Errors Read
Using "magiclantern-Nightly.2019Mar15.70D112_crop_rec_4k_mlv_lite_lossless_fps_override_experimental"
Was able to get 2560 @ 2.35.1 23.9p 12bit raw lossless continuous in 5X. Global was off, generally. Very slow playback.
Was able to get 1920 @ 2.35.1 59.9p 12bit raw lossless continuous in 5X. Global was off, generally. Extremely slow playback (1minute clip takes about 5 minutes).
In 5X you only have centre box focus, no facial recog., Without focus peaks it brings into question MF choices. But the picture is gorgeous in detail and depth, it feels like the LCD is maxed out.
I notice it showed centre for box location (5X), but it was actually off to the right third of full screen (1X).
If you put global back on, screen loads up with "fix me: malloc errors", and even more if you keep pressing buttons to virtually entire screen.
To make this practical, need global on with rgb & focus peaks and ofcourse errors disabled. The playback needs to occur much faster else 60p is too painful.
Also with 5X my Tokina 11-16mm 2.8 starts to become the goto lens. Ok 18mm on the Sigma 18-35mm never sucks either, its just 5X is a lot.
3X mode with 1864 @ 2.35.1 23.9p 12bit raw lossless continuous, this mode has no moire and will also work same for 60p. 3X loses the AF features.
In regular 1X, 1832 @ 16.9 23.9p 14bit lossless continuous, this mode has full AF capabilities touch screen focus. (the 60p of same is probably continuous I stopped it after 34s but should test to see if it keeps going to say a minute). The picture is gorgeous, and uses most of the LCD screen. This mode is rather sexy and for most straightforward shooting a useful mode, having near 1080p @ 16.9 24 to 60p, in 14bit raw lessens my 5DIII desire. This closest to a broadcast TV quality picture (its not quite 1080p resolution but exceeds TV colour of 10bit).
Quote from: ShootMeAlready on May 16, 2019, 06:02:48 AM
Using "magiclantern-Nightly.2019Mar15.70D112_crop_rec_4k_mlv_lite_lossless_fps_override_experimental"
Was able to get 1920 @ 2.35.1 59.9p 12bit raw lossless continuous in 5X. Global was off, generally. Extremely slow playback (1minute clip takes about 5 minutes).
i dont think you can shoot 60fps in 5X mode. no matter whatever your setting is in canon menu when u zoom in 5X it wil change to 30fps
Shooting 60p raw works with fps override. The problem is the playback takes about 5 (or more) times as long to process the clip. So one really needs overclocking for play back. You need to use in camera playback for focus checks, so until overclocking works on playback, the fps override is effectively crippled. No one will routinely wait 5 minutes (or more) to view a 1 minute clip. On the bright side, we have fps override! Overclocking works! We just have to integrate this into play back.
Quote from: ShootMeAlready on May 17, 2019, 02:41:31 PM
Shooting 60p raw works with fps override.
shoooting 60p raw works with every build in normal mode. you dont need fps override for this. as i have said earlier that fps override can only decrease fps but cant increase on 70D atleast for now
Quote from: ShootMeAlready on May 17, 2019, 02:41:31 PM
really needs overclocking for play back. You need to use in camera playback for focus checks,
press half shutter preview wil change to real time so you can focus easily. playback in realtime in camera is not possible.
Hi , hope to be easy , i just want to ask a too simple and too important question
I have 70D and i want to:
-Raw video
-Focus Features in magic lantern
and I saw 135 pages here ,I tried to read but,,,
I just want to know If that any problem in current build for 70d ?
and may flash ML brick camera ( I mean True Stories) ?
Thanks you too much
@ShootMeAlready
"Using "magiclantern-Nightly.2019Mar15.70D112_crop_rec_4k_mlv_lite_lossless_fps_override_experimental"
Was able to get 2560 @ 2.35.1 23.9p 12bit raw lossless continuous in 5X. Global was off, generally."
Here I Go Again > So What do You suppose I am doing wrong > The most I can get, & I get it consistently, is 7Sec's ~
ORR ~ DeanB
Update > Switching WhiteBalance from Auto to 5200K allows capture of 11Sec's ~
Quote from: Zenmate on May 18, 2019, 12:54:42 AM
Hi , hope to be easy , i just want to ask a too simple and too important question
I have 70D and i want to:
-Raw video
-Focus Features in magic lantern
I just want to know If that any problem in current build for 70d ?
no problem
you dont need to read all 300 pages but try to read last few pages to know more about recent development if you want to shoot 3k ml raw video
Quote from: andy kh on May 19, 2019, 12:17:26 PM
no problem
you dont need to read all 300 pages but try to read last few pages to know more about recent development if you want to shoot 3k ml raw video
I had read it yes , and I'am little Confused
https://builds.magiclantern.fm
Here Nightly builds , for 70D the last file called ( magiclantern-Nightly.2018Dec24.70D112)
that's mean it's updated in 2018 , and last few page here there are versions updated in couples days ago
I Don't what's right , I just want to shoot raw with little tricks like waveform and small stuff not complicated
and of course most safety , is version here less stable and non tested , and nightly builds is tested ?
Too appropriate to you for your help
Can you help me to choose the right version and give me a Link for best versoin and testes , I mean Most Stable And Do small Stuff like focusing etc.
and all of these problems in this pages (Codes and other stuff) , Can i suffer from any of them if I just shoot raw (Not too high resolution like 4k or bit rate , 10 or 11 enough for me) And use Waveform Or False Color?
Thanks you
https://bitbucket.org/ArcziPL/magic-lantern/downloads/magiclantern-Nightly.2019Mar07.70D112_crop_rec_4k_mlv_lite_lossless.zip
try this. you can shoot in lossless if you want small file size
report back if you find any problems.
Quote from: andy kh on May 19, 2019, 03:42:25 PM
https://bitbucket.org/ArcziPL/magic-lantern/downloads/magiclantern-Nightly.2019Mar07.70D112_crop_rec_4k_mlv_lite_lossless.zip
try this. you can shoot in lossless if you want small file size
report back if you find any problems.
Thank you too much
Quote from: OlRivrRat on May 18, 2019, 02:39:58 AM
@ShootMeAlready
"Using "magiclantern-Nightly.2019Mar15.70D112_crop_rec_4k_mlv_lite_lossless_fps_override_experimental"
Was able to get 2560 @ 2.35.1 23.9p 12bit raw lossless continuous in 5X. Global was off, generally."
Here I Go Again > So What do You suppose I am doing wrong > The most I can get, & I get it consistently, is 7Sec's ~
ORR ~ DeanB
Update > Switching WhiteBalance from Auto to 5200K allows capture of 11Sec's ~
Sounds like you need to engage the overclocking.
- Select ML raw video modules, sd_uhs, and crop (the crop was disabled but I selected it anyways ... superstitious)
- Select ML raw resoultion 2560 at 2.35.1 aspect, with framing
- in ML turn global off
- in ML, Sd overclock at 160 MB/s, need to override the warning
- go back check your resolution message, it should be green (or flicker from red to green, I did not always see solid green)
If not reselect the overclock,
- In liveview, on Q menu select 24 fps, ensure AF is not set to facial tracking, I suggest single box
- In liveview, on what is by default the * button on back hit until 5X
- Press liveview, and it may go red, yellow, green, but after about 30s the red disappears.
When you are pre-focus the half-shutter press effects focus/liveview update (play with it)
Hope this helps
&ShootMeAlready
It appears I'm Already doing My SetUp the same as Yours,, Except > I'm unclear on the meaning of this >
"- in ML, Sd overclock at 160 MB/s, need to override the warning
- go back check your resolution message, it should be green (or flicker from red to green, I did not always see solid green)
If not reselect the overclock,"
I don't get any visual indication that SD O'C' is active > 41MB/s is indicated Upper Right during Rec.
I have tried activating SD O'C' both Manually & via AutoRun ~
Its the same issue as in « Reply #3356 on: May 15, 2019, 12:09:01 PM »
I found the override in two places, in ML menu, there is in Video Menu and again in the Overview of settings menu (on top far right, scroll down). Sd module has to be loaded, as well as ML raw modules.
Try clean reboot, set-up, then press it once, exit ML, then 5X/AF and record. That's what I generally did.
@ShootMeAlready
"I found the override in two places" > Are You now Calling SD OverClock "the override" or are You now referring to something else?
In My ML Menus there is no reference to SD O'C' in the Video Menu & I do not have an "Overview of settings menu". The Far Right
menu on All My Cams is named "Modified" & SD O'C' does Not appear in that menu ~ To the immediate Left of that menu is a menu
named "Recent" & SD O'C' does appear in that Menu & when that SD O'C' is clicked it does appear to activate the O'C' & subsequent
Rec's of 2560x1090 2.35.1 23.9p 12bit raw lossless in 5X can be acquired Continuous ~
As was said in previous reply you can read literal message, but it asks you more or less are you nuts for doing this? (russian roulette with your data) Then you click - yes, to override. But you are running an experimental build anyways, and your camera came back from the dead so you are fearless. You should only need to do this once per boot-up.
Quote from: andy kh on May 16, 2019, 07:13:48 AM
i dont think you can shoot 60fps in 5X mode. no matter whatever your setting is in canon menu when u zoom in 5X it wil change to 30fps
I was able in 5X to shoot 24 fps. I was testing 1920x1080 12 bit lossless in 5X, but 5X initially selected goes to 30 fps,
but if you set fps override Timer A to 842 (+170) I was getting 23.9 fps.
I could turn global on, with half shutter press, then set fps override to 23.9 and timer A to +170, and get 24 fps.
Global on you get screen updates every 3s or so. In camera video playback is slow. The big problem now is in camera liveview and playback.
However with 5X cant get higher than 30p. It would be interesting to compare 70D 12bit raw to 80D H264, to see how 80D sensor DR stacks up.
I suppose to answer my own question,
70D 12 bit raw if shot 1/3 over (expose to right) then it should have better detail.
80D probably less noise in low light without processing.
However detail can be traded off, to yield less noise, so it probably is a very fair comparison in the hands of skilled shooter.
I suspect 70D wins via better highlight and overall detail but low light noise about equal for same ISO. Now for someone to check it out.
The 80D probably wins for high ISO shooting (ISO 3200 in H264) as raw tends to max out around ISO 800 (before hot pixels kick in).
Hey ML community.
It's been a while since I lurked on here and I'm trying to understand exactly what everyone is talking about to update myself. Search didn't resolve my confusion, apologies if I missed it clearly laid out, but if someone has a moment would you mind updating me on the 2.5k / fps / 5x mode recording capabilities in a nutshell?
From what I gather, changing between 14 / 12 / 10 - bit allows recording up to 2.5k resolution, but the camera has to be in the 5x screen zoom / focus check mode?
So the actual recording is not cropped to 5x, but without an external monitor you will be viewing your live preview at 5x zoom?
Sorry for the bother, just trying to get myself updated on the latest ML abilities for the 70D.
Much appreciated!
Actually crop mode is 3x and you get same cropped frames everywhere: recorded data, liveview monitor and HDMI.
Ok 5X mode on 70D, is like a magic zoom. You see 5X on live view, but the actual video is 3X, so its a wider frame on playback.
Not sure about HDMI out???? Its been a while.
I think I recall you get all the LCD output, with the magic lantern screen stuff (as I recall).
The HDMI out always required no screen extras, and then you could output to a video recorder.
At 5X and 2.5k @ 2.35:1 24fps, the LCD updates with a lag. So I suspect there's a lag.
with the HDMi you wil only real time preiview in 5X crop mode. in camera you can choose between framing and real time
Got some requests to put up a 70D build with lossless compression. I'm getting this when compiling the current crop_rec_4k branch:
#error FIXME: please define FRAME_SHUTTER_BLANKING_READ
I can either back out the changes that require FRAME_SHUTTER_BLANKING to create a hacked build or if someone with a 70D that knows how to use adtg_gui could look up ADTG registers 805f and 8061 we can do something a little better. Ideally these addresses eventually won't be hard coded.
Think these will work:
#define FRAME_SHUTTER_BLANKING_ZOOM (*(uint16_t*)0x404e6180) // ADTG register 805f
#define FRAME_SHUTTER_BLANKING_NOZOOM (*(uint16_t*)0x404e6184) // ADTG register 8061
#define FRAME_SHUTTER_BLANKING_READ (lv_dispsize > 1 ? FRAME_SHUTTER_BLANKING_NOZOOM : FRAME_SHUTTER_BLANKING_ZOOM)
#define FRAME_SHUTTER_BLANKING_WRITE (lv_dispsize > 1 ? &FRAME_SHUTTER_BLANKING_ZOOM : &FRAME_SHUTTER_BLANKING_NOZOOM)
Arcipl got them from his camera. Don´t remember where to find them but look around. He has his code on bitbucket.
EDIT: Here you go:
https://www.magiclantern.fm/forum/index.php?topic=14309.msg213467#msg213467
Thanks. Looks like @ArcziPL has a test build on his downloads page (https://bitbucket.org/ArcziPL/magic-lantern/downloads/). He did some tests on it so I think it is best if I just redirect any requests for 70D builds.
Would be nice to see a pull request for this.
Quote from: Danne on June 12, 2019, 10:22:52 PM
Think these will work:
Disclaimer: no idea if the addresses of frame shutter blanking times are constant or camera-dependent or maybe even random at power-up. I also didn't test them as I didn't know how.
Not sure if this is still relevant. I've just finished smoking the thread to educate myself about nuances of running ML on my recently acquired 70D. I've come across mentioned a couple of times people having difficulty running SD OverClock module on ArcziPL's builds. I also experienced this - the module giving me malloc errors when trying to run it. In my case it gives the error if Raw video is on. If I turn it off, I can enable overclock and then turn Raw video on.
I also did some quick tests today comparing different sd_uhs modules and it seems the one included is slower than Danne's. I will do more tests to confirm this.
Hey guys, big ups to everyone getting lossless / sd hacks / 3k going on this cam!
I've been checking this thread fairly regularly since it started, and reread the last 5 pages, + searched the 10bit thread, but still a couple of things I can't find info on.
1. Why does 14bit lossless say ISO < 100. To me that means choose an ISO smaller than 100, but that doesn't make sense. Why does ISO matter to lossless anyway?
2. Magenta highlights in 12bit /10bit lossless modes. Is this a known issue? What causes it? I remember reading somewhere way back about incorrect white level, I can alleviate it somewhat by messing with it in MLV App, but I've no idea what I'm doing and it seems to hurt other colors. What's needed to fix this on the 70d now and can I help?
thanks
Is it ok to use this installation method : https://www.dpreview.com/forums/thread/3628812?page=3 ?
I had the same problem. It took me a while to figure out that there are two ways to install dual iso. The second option is downloading another software called Eoscard. It makes any SD or CF card bootable. I took the second option. The steps are as follows:
1. Download Eoscard from here.
2. Unzip it.
3. Download the nightly build (ML and autoexe.bin files) and unzip it. Transfer both files (ML and autoexe.bin) to the root of the memory card (already formatted in camera).
4. Click on Eoscard (memory card still connected to computer). Its interface will open and it will immediately recognize the memory card. Screenshot of the interface is here.
http://chdk.wikia.com/wiki/EOScard
Make sure that only Bootdisk is checked as in the screenshot. Click Refresh. That's it, your memory card is now bootable. You won't have to go through firmware update process. Take the card out of your computer and put it in the camera. You are good to go.
And what should I use - last nightly build or archive from the start msg of this topic? I mean:
nikfreak-magic-lantern-0e6493e8ac5e.zip
or
magiclantern-Nightly.2018Dec24.70D112.zip
It seems that the second one is newer (2018-04-30 vs 2018-12-24)
tnx ahead
PS hmm.. may be from here? But which archive should I use?
https://bitbucket.org/ArcziPL/magic-lantern/downloads/
Looks like @ArcziPL has a test build on his downloads page
Today EOScard's role is mostly reduced to unbrick (semi)-bricked cams after panicking owners formatted their cards prematurely.
Go to top of page -> Downloads -> Download nightly builds
and follow installation instructions.
hey all
just got a 70d
hoping if someone could help
is there a safe build that i can dowload to lossless video with sound
i looked an am not totaly sure
Quote from: berechiah on October 27, 2019, 11:29:44 PM
hey all
just got a 70d
hoping if someone could help
is there a safe build that i can dowload to lossless video with sound
i looked an am not totaly sure
https://bitbucket.org/ArcziPL/magic-lantern/downloads/
Thanks for your help I really appreciate it
https://www.magiclantern.fm/forum/index.php?topic=18443.msg213049#msg213049
https://www.magiclantern.fm/forum/index.php?topic=14309.msg213467#msg213467
Hi,
I am having difficulty recording a resolution above 1864 x 1048 resolution.
My setup consisted of:
Install magiclantern-Nightly.2019Mar15.70D112_crop_rec_4k_mlv_lite_lossless_fps_override_experimental
Sandisk 170MB card
Fresh install and disabled global draw
Enabled sd_uhs and lua script and then restarted camera
Ran SD overclock which reported 50MB max write
Enabled crop rec + mlv_lite/play/rec and restarted camera again
Set camera to 3x
The 1864 res worked great at various aspect ratios for various lengths of time but I can not go above it.
"2240 is not possible in current video mode"
I have read back to last March in this thread a number of times and can't see a solution.
Am I missing something needed to achieve the 2.5k?
Thanks, Joe
Hi there,
Does anyone know if any version of ML allows to have the Liveview working with accurate framing while shooting RAW video on the 70D? Even in grayscale?
I have tried many different Builds without success until now, the liveview is always frozen if in 'framing' mode as soon as the record start
Hi everyone !
I read a lot of pages to know what are the updates for 70D and I'm not sure to understand exactly what is actually working.
From what I understood, we can have 1832*1024, 23,98 continuous in 12 bits lossless right ? Does DPAF works with these settings ?
Is it stable ? Does a VAF-7D also works with DPAF ?
Thanks
Quote from: 12georgiadis on December 30, 2019, 04:35:46 PM
From what I understood, we can have 1832*1024, 23,98 continuous in 12 bits lossless right ?
I was personally always recording 25 fps so far but 23,98 is just a setting from the Canon menu, which should work same good. So: yes.
Quote from: 12georgiadis on December 30, 2019, 04:35:46 PMDoes DPAF works with these settings ?
Yes.
Quote from: 12georgiadis on December 30, 2019, 04:35:46 PMIs it stable ?
From my experience: yes.
Quote from: 12georgiadis on December 30, 2019, 04:35:46 PMDoes a VAF-7D also works with DPAF ?
Never had one but I expect: yes. VAF only blurrs the image. Nothing less, nothing more. I don't see any reason why it should interfere with DPAF.
Quote from: ArcziPL on January 05, 2020, 06:29:44 PM
I was personally always recording 25 fps so far but 23,98 is just a setting from the Canon menu, which should work same good. So: yes.
Yes.
From my experience: yes.
Never had one but I expect: yes. VAF only blurrs the image. Nothing less, nothing more. I don't see any reason why it should interfere with DPAF.
Thank you ArcziPL, that's surprising that this camera has not so much popularity because it seems by far the best APS-C camera because of DPAF.
I'm gonna switch from my 7D to the 70D now.
I'm sorry, I know this is most likely a silly question, but I have been going through several pages of this Forum history, to no avail...
What is exactly limiting the RAW recording to 1832*1024 at this stage? At first I thought it was write speed, but since changing the recording mode (14/12/10 bit, uncompressed, lossless etc) does not change anything (does it?), I guess this is not it?
Apart from this, I am happily RAW-recording using arczipl's build (magiclantern-Nightly.2019Mar07.70D112_crop_rec_4k_mlv_lite_lossless). Thanks to all of ML community for the incredible work!
Sergio
Ps: what am I missing from the magiclantern-Nightly.2019Mar15.70D112_crop_rec_4k_mlv_lite_lossless_fps_override_experimental build?
Press loupe/magnify button to access "crop mode" for higher resolutions.
Quote from: Walter Schulz on January 21, 2020, 01:02:39 PM
Press loupe/magnify button to access "crop mode" for higher resolutions.
Nice and easy, thanks a lot. I thought I needed to use Canon's built-in 3x zoom.
Using ML crop mode as you suggested, instead, I get 5x and 10x (this one for focusing I guess) -- is it the way it is supposed to be?
And, once again, what is exactly limiting the RAW recording to 1832*1024
at 1x? Just for my understanding.
Thanks
Sergio
Quote from: vastunghia on January 23, 2020, 01:47:31 PM
Nice and easy, thanks a lot. I thought I needed to use Canon's built-in 3x zoom.
If your cam has an "Movie Crop Mode" entry in Movie tab you can use this option, too.H
Quote from: vastunghia on January 23, 2020, 01:47:31 PM
And, once again, what is exactly limiting the RAW recording to 1832*1024 at 1x? Just for my understanding.
Like most ML supported cams 70D uses "line skipping" in H.264 and uncropped RAW/MLV recording where only every third sensor line is processed. Lookup terms "native resolution", "line skipping".
I've been lurking in this thread for the past two years, and just want to thank the ML community for keeping the 70D alive.
After shooting raw video for the past couple of years on my 70D, I've got hours and hours of footage - enough that the 70D has become my daily driver for commercial videography. I've had a hard time finding a better alternative at the same price point so far. The learning curve was a bit steep for understanding the majority of the settings, but it has paid off handsomely with the rich colour I get out of the camera.
Some things I've noticed over the years:
- I shoot 14 bit lossless @ 1832x1024 16:9 24 fps continuous for the most part. The buffer usually hovers *very* close to full, but I can usually get away with continuous recording. For bright and visually complex scenes, sometimes it does overrun the buffer and I need to start recording again.
- For sensitive moments like interviews where I can't afford to miss a few seconds due to buffer overflow, I drop the camera down to 12 bit lossless. Perfect continuous recording there without the risk of buffer overrun.
- Running the camera in full Manual mode is critical for getting good images out of it. I set the shutter speed at 2x the framerate: so in my case, that's 24 fps with a shutter speed of 1/48.19
- I run with Global Draw off. I found the extra information useful, but ultimately distracting while I'm filming.
Not much new here, but I just wanted to share for anyone looking to try out ML on their 70D. Without it, I basically wouldn't have a film career. Much appreciated everyone :)
What is suggested/best build for 70D? We have nightly build, 3 experimental builds, somewhere some custom builds ... Is there some list of builds for 70D with some notes, differences, urls,..?
Quote from: lojzik on February 03, 2020, 06:34:45 AM
What is suggested/best build for 70D? We have nightly build, 3 experimental builds, somewhere some custom builds ... Is there some list of builds for 70D with some notes, differences, urls,..?
Quote from: yokashin on October 27, 2019, 11:49:22 PM
https://bitbucket.org/ArcziPL/magic-lantern/downloads/
Hi. I have tried these three builds and have not been able to implement crop rec to record at higher resolutions.
3-10x digital zoom was enabled in the Canon menu but as you see in the images below it says crop mode is not enabled.
croprec4kmlvlitesnd+sd_uhs-2018Aug10.70D112
Mar07.70D112_crop_rec_4k_mlv_lite_lossless
Mar15.70D112_crop_rec_4k_mlv_lite_lossless_fps_override_experimental
Here is a link to some photos of the settings used:
http://imgur.com/gallery/1WzicGN
http://imgur.com/gallery/2nNGxGL
I feel like I am missing some setting. Everything else seems to work perfectly
Only one public pic visible. Second "not found".
Have you tried to disable the crop setting from the menu and pressing loupe/magnify button in liveview instead?
Thats it! Thank you
@stan101 asked me to provide a straightforward walkthrough of ML for the 70D to get him started. I promised a Youtube vid explaining my process and settings, but I'm a little squeezed for time this week so I'll provide a bullet-point form response until I can get to filming a tutorial:
Q: What version of ML do you run on your 70D?
A: I use Magic Lantern Nightly.2019Mar07.70D112 (02e5918a6ed5+ (crop_rec_4k_mlv_lite_snd)) Built on 2019-03-07 20:10:24 UTC by artur@Artur-VirtualBox. This is ArcziPL's build discussed here. (https://www.magiclantern.fm/forum/index.php?topic=14309.msg213074#msg213074) Download here (https://bitbucket.org/ArcziPL/magic-lantern/downloads/magiclantern-Nightly.2019Mar07.70D112_crop_rec_4k_mlv_lite_lossless.zip).
Q: What settings do you use on your 70D?
A: I aim for the highest visual quality I can attain, sometimes at the cost of recording time.
Following are my Canon/70D settings accessed via the 'Menu' button:
Movie1 ->
AF method: Face+Tracking
Movie Servo AF: Enable
Movie2 ->
Grid display: Off
Movie rec. size: 1920/24/All-I
Digital zoom: Disable
Sound recording ->
Sound rec.: Manual
Rec. level: a few ticks past zero.
(I use an external microphone setup that has its own amplifier, so I set the internal amp as low as possible. If you're using your camera's internal mic, just set Sound Rec: Auto)
Below are my ML settings accessed via the 'Trash Can' button:
ML -> Modules ->
crop_rec: OK
mlv_lite: OK
mlv_snd: OK
All other modules are disabled.
These three modules must be enabled before the below settings can be worked on.
ML -> Movie -> RAW video ->
Resolution: 1832x1024
Aspect Ratio: 16:9
Data format: 14-bit lossless
Sound Recording -> Enable Sound: On, Sampling Rate: 48 Khz
All others are left at ML defaults.
ML -> Overlay ->
Global Draw: OFF
ML -> Expo ->
White Balance: Auto
ISO: 100 (As another poster mentions, anything below 640 works well.)
Shutter: 1/48.19, 179* (Following the 180 degree shutter angle rule for creamier motion blur)
Aperture: whatever your lens supports
Picture Style: Cinestyle (I've downloaded the Cinestyle profile for the 70D and installed it as User)
All other left at ML defaults.
Q: How much recording time can I expect from this?
A: It depends on the complexity of the scene, but anywhere from 30 seconds to 5 minutes. The camera pushes to the SD card at 40-40.5 MBps at these settings. This is at the threshold of what the camera can handle.
Q: I need continuous recording. What settings should I use?
A: Drop your ML -> Movie -> RAW Video -> Data Format down to 12-bit lossless. This reliably writes to the SD card at 35-39 MBps, which provides unlimited/continuous shooting.
Q: I *really* need to shoot at 14-bit and want continuous recording. What settings should I use?
A: ML -> Movie -> Raw Video -> Aspect Ratio: 2.20:1 provides a resolution of 1832x832. You will get continuous shooting at 39MBps at 14-bit.
Q: What SD card do you use?
A: I use a SanDisk Extreme Pro 128GB U3/V30 170MB/s card. This card can write at 95 MB/s, which is overkill for the 70D, but it gives me an upgrade path if I decide to get a faster camera.
Q: What speed does the 70D write to the SD card at?
A: The maximum possible speed is 40MB/s. Anything above this will run the camera out of buffer within a few seconds.
Q: My ML menu screen flickers every few seconds. Why?
A: I have no idea. Mine does too.
Q: What program do you use to convert MLVs to another format?
A: MLV App.
Hope that helps @stan101! A Youtube tutorial is forthcoming in a week or two.
Nice one vga256 ....
When I saw your post here - I loaded up ArcziPL's build as well. Terrific! - now I've got sound as well.
Yes, the 'flickering' is a little annoying but it's only on the menu so no big deal. I ended up going with 1832 x 832 and was happy with 12 bit. I see what you mean about running time being dependent on the 'complexity of the scene'. If I use 'fast' camera moves it sometimes causes the recording icon to go yellow, or even red - indicating the buffer's filling too fast - but it always seems to recover and turn green again. My card's only 60MB/sec write speed, which is on the 'lean' side, but overall I still get very adequate recording times - (better than before). Thanks to all the clever folk involved - you're all thoroughly *brilliant* ....
Quote from: vga256 on January 30, 2020, 03:36:53 PM
I've been lurking in this thread for the past two years, and just want to thank the ML community for keeping the 70D alive.
After shooting raw video for the past couple of years on my 70D, I've got hours and hours of footage - enough that the 70D has become my daily driver for commercial videography. I've had a hard time finding a better alternative at the same price point so far. The learning curve was a bit steep for understanding the majority of the settings, but it has paid off handsomely with the rich colour I get out of the camera.
Some things I've noticed over the years:
- I shoot 14 bit lossless @ 1832x1024 16:9 24 fps continuous for the most part. The buffer usually hovers *very* close to full, but I can usually get away with continuous recording. For bright and visually complex scenes, sometimes it does overrun the buffer and I need to start recording again.
- For sensitive moments like interviews where I can't afford to miss a few seconds due to buffer overflow, I drop the camera down to 12 bit lossless. Perfect continuous recording there without the risk of buffer overrun.
- Running the camera in full Manual mode is critical for getting good images out of it. I set the shutter speed at 2x the framerate: so in my case, that's 24 fps with a shutter speed of 1/48.19
- I run with Global Draw off. I found the extra information useful, but ultimately distracting while I'm filming.
Not much new here, but I just wanted to share for anyone looking to try out ML on their 70D. Without it, I basically wouldn't have a film career. Much appreciated everyone :)
How on earth do you accomplish continuous shooting in 14bit RAW on the 70D? Isn't the write limit natively around 40mb/s on the 70D? I only get about 5 secs of running time if i shoot 14bit @1832x1024 16:9 24 fps. Regardless of fast card. Love to hear if you've changed any settings i haven't tried.
cheers
/NC
He is using lossless compression mode.
And please do not full quote...
Quote from: Walter Schulz on March 04, 2020, 07:12:58 PM
He is using lossless compression mode.
Sorry bout fullquoting.
And sorry i yelled out. I could have just read the past 10 or so pages. Found out my sdcard is limited to 38MB/s write speed, so the ML sd-overclock module has absolutely no effect on my cameras ability to shoot longer videos in @1832x1024 16:9 24fps. I get around 60MB/s read speed, so guess i'll have to try a card with faster write speed.
Thanks all for the great work - putting a new glare in my old 70D
Cheers!
/NC
Ciao,
using March 19 ArcziPL build here. Very happy with it, thank you!
I seem
unable to use the intervalometer correctly. My fault, most likely.
The issue is that, after the first shot,
it changes my Tv. Example below.
Initial settings:
- Lens: Sigma 18-35 F1.8 @35
- M mode
- Av f/4
- Tv 1/250
- ISO 100
- Take a pic every: 1s
- Start after: 30s
- Stop after: 15 shots
Don't remember exactly whether I left Live View on or off, but I think it was on.
So
the first shot had correct parameters, then the following 14 shots had a Tv of 1/2000.
Am I doing something wrong?
(And should I post this question in an intervalometer-specific thread, if any?)
Thanks a lot in advance
Sergio
Post content of ML\SETTINGS\magic.cfg
Thank you Walter!
beta.warn = 19
menu.first = -5
lv.peak = 1
bv.av = 32
bv.tv = 101
interval.stop.after = 15
interval.start.time = 30
interval.time = 1
hdr.ev_spacing = 8
hdr.frames = 5
battery.drain.rate.rev = 9
focus.peaking = 1
zoom.overlay = 1
disp.mode.x = 967
Ciao
Sergio
I had a sort of an enlightenment: could this be the Auto ETTR (I set its trigger to double Half Shutter) being triggered by the intervalometer?
This would explain why exposure time was lowered — I was trying to over expose originally.
S
Yes, that's the culprit: Both features use half-shutter to be triggered. See https://wiki.magiclantern.fm/camera_help#intervalometer
Thanks a lot for the feedback.
Btw I put together a short, little tribute to ML. Please find it here:
Thank you to the ML community!
Sergio
Nice work Sergio, and great demonstration of the raw capabilities. Still loving my 70D, although I'm shooting less these days. I've got the same Sigma 18-35 lens - what a fantastic lens for this camera.
What resolution and bit depth are you shooting at? I've been pushing my camera pretty hard at 12 and 14-bit, but it's tough to maintain recording times of more than 30 seconds.
Ciao vga256,
thanks for the feedback!
I'm constantly shooting 1832 x 1024, 14-bit lossless, with FPS override @24 fps (resulting in 23.971 or 23.984 fps, heaven knows why).
For most scenes, this results in continuous shooting for me. In very extreme circumstances, where I have a very very wide dynamic range, I have to turn SD overclock on via the sd_uhs module. With SD overclock activated, in my personal (and limited) experience I have seldom encountered full buffer and abrupt stop in the recording. But still, of course, it may happen, depending on the scene.
Another consideration: I love the Sigma 18-35, although I use it more for stills. For video, after some time (and money) spent trying other (not-too-expensive) glass, I must admit that I find the good old 18-135 IS STM kit lens nearly unbeatable. Its focus accuracy and speed is unbelievable when coupled with the 70's dual pixel AF, its motor is the most silent I've experienced, and it has IS, which is a game changer for video. With it, I shoot constantly at f/5.6, which (apart from providing a nice intermediate focus depth for most circumstances) I find to be the strong spot for this lens (also as confirmed by dxomark tests, see here: https://www.dxomark.com/Lenses/Canon/Canon-EF-S-18-135mm-F35-56-IS-STM-mounted-on-Canon-EOS-70D---Measurements__895 (https://www.dxomark.com/Lenses/Canon/Canon-EF-S-18-135mm-F35-56-IS-STM-mounted-on-Canon-EOS-70D---Measurements__895), particularly for sharpness), with a 3-stop (ND8) ND filter that allows me to have a proper ETTR setting with a ~180° rolling shutter (1/50s shutter speed) in most situations (I may need to stop it down to f/8 with very bright subjects in direct sunlight). I find that its structural lack of sharpness is negligible when shooting video @ 1832 x 1024, while of course other weaknesses, such as chroma aberration, vignetting etc can be corrected during post-prod if you shoot Raw. Would love to hear any comments on this.
Happy (Raw) shooting!
Sergio
Ps: I also tried resolutions higher than 1832 x 1024 via the 5X zoom trick, but I really find it hard to consider this option as anything other than a technological capability demo. I used it to shoot some portraits of very distant neighbors chilling out on their home balcony during peak COVID stay-at-home lockdown past spring, and the 5X zoom was exactly what I needed. But apart from that specific situation, I wish somebody explained me how to use this feature in real life.
I managed to find a March 15 2019 build that has crop_rec and the SD overclock stuff. Found a video where a guy was shooting well over 1920 horizontal resolution, but mine refuses to let me set it higher than 1824x764. Why is that?
Press magnify/loupe button to access "5x view" aka crop mode.
Ciao,
a few days ago I shot some short scenes with the following settings:
- 14-bit lossless Raw video enabled (for some clips @1832x1024, for some other @1920x1080 via 5x zoom)
- FPS override @24 fps (Low Jello, 180d)
- SD overclocking enabled
Everything seemed fine, as always; however, for one particular clip (2266 frames @1920x1080), I see
- MLVFS reporting an fps of 29.986 (instead of something in the range 23.971- 23.989 as expected, and as obtained for the other MLV's)
- consequently, a reported duration of 2266 / 29.986 = 75 seconds
- an audio file lasting exactly 75 seconds
By syncing audio and video (also with the help of a second audio track I captured with an external mic), I can tell for sure that the clip is ~24 fps actually (as expected). So the weird thing seems to be that
- the fps determined by ML is inconsistent (~30 reported instead of actual value of ~24, as set using FPS override)
- the audio file was somehow truncated early by ML to make its duration consistent with the wrong, higher-than-actual fps
Luckily enough, as I mentioned, I was also recording via an external mic, so I did not lost the last 19 seconds of audio (= difference between 2266 frames divided by 30 and same frame count divided by 24).
Anybody else experiencing this strange behavior? Do you think I might be doing something wrong?
Should your answer be 'no' to both questions, please take this as an advice to always use an external mic when shooting Raw, if you care about your audio track.
Sergio
I tested with a fresh SD card and recorded 20 or so videos and about half had audio issues.
I normally dont shoot video but just started for something im working on. I tested again with another card and none had issues.
Im going to do some more testing since I have a few cards but no more time today to record. Ill update with how it goes.
Does anyone have the link to the March 19 ArcziPL build? The one in bitbucket seems to be unavailable. I would love to try out this build after reading Sergio's positive experience. Thanks.
I can find this one magiclantern-Nightly.2019Mar15.70D112_crop_rec_4k_mlv_lite_lossless_fps_override_experimental.zip
from https://web.archive.org/web/20200621151421/https://bitbucket.org/ArcziPL/magic-lantern/downloads/
direkt link:
https://web.archive.org/web/20200621151436/https://bbuseruploads.s3.amazonaws.com/3f5144c4-ac62-40a5-9661-de9d52f6bf3c/downloads/01448683-ef3b-442b-9831-6ee2c668416e/magiclantern-Nightly.2019Mar15.70D112_crop_rec_4k_mlv_lite_lossless_fps_override_experimental.zip?Signature=qh8m4nVuigUnnAJ0cJjmzT0GjiE%3D&Expires=1592754276&AWSAccessKeyId=AKIA6KOSE3BNJRRFUUX6&versionId=D_W7frtkveuNaUux149vjL8R1ZyWIuM4&response-content-disposition=attachment%3B%20filename%3D%22magiclantern-Nightly.2019Mar15.70D112_crop_rec_4k_mlv_lite_lossless_fps_override_experimental.zip%22
Tks for the links but its still down, is anyone could give me a new link?
Thank you LeandroFreitas for the links. I downloaded and tried out the build, it worked wonderfully. I was able to record at 1832 x 1024, 14 bit lossless for unlimited time. I used the same settings as suggested by Sergio. I have found new life for my 70D.
I can download now，tks very much！
Hey guys, does anyone know if Dual ISO is working in photo or video with the March 19 ArcziPL build?
Sergio in response to
"I also tried resolutions higher than 1832 x 1024 via the 5X zoom trick, but I really find it hard to consider this option as anything other than a technological capability demo. I used it to shoot some portraits of very distant neighbors chilling out on their home balcony during peak COVID stay-at-home lockdown past spring, and the 5X zoom was exactly what I needed. But apart from that specific situation, I wish somebody explained me how to use this feature in real life."
The answer that your are looking for is the Tokina 11-16 f2.8 lens (I recall there is a newer version which goes to 11-20mm f2.8 ) .
5X trick means you have 55 - 80mm, which is very good and has a decent image quality. And dont forget the 3X mode as well, as that gets you 33-48mm. So if you think about it, the one lens gets you 11-16, 33-48, and 55-80, all at f2.8 wide open. And the kicker is the lens is parafocal, so its zooming while limited in range, is done right.
Personally I really love the Sigma 18-35mm on my 70D, which is my wide angle lens of choice, I would shoot it wide open at night. The canon 28m f1.8, stepped up to f2.8 is rather good as well. The secret sauce, is that you really shoot fixed focal length most of the time for video. To really use the tracking for moving objects, you generally want a wide focal length, that keeps your subject in frame with some buffer (crop in post), so again its either the Tokina 11-16mm or the Sigma 18-35mm for excellent tracking. Recall the 5X and 3X modes dont support the AF subject tracking, so in general your limited at the 1832 barrier. I think the f5.6 canon zooms, are good for daylight or well lit night shots. Another truth with video, is that its ok to shoot your subject in partial darkness, or silhouette, as you only occasionally need to see their face. Photographers are the ones who have to get max. detail in one shot, so use your f5.6 lens at night as long as your subject periodically is well lit, it can workout fine.
Oh yes, with the 5X, and 3X tricks, the Sigma lens gets you, 18-35, 54-105, and 90-175mm, all at f1.8 wide open, the lens is not perfectly parafocal but its very good, especially if you use the AF tracking while zooming (centre spot focus for 5X and 3X while zooming will allow AF to work).
Hi, I installed the last "official" version for the first time (https://builds.magiclantern.fm/70D-112.html) I have a SanDisk SDXC U3 10 95MB/s card. It shows me around 40MB/s while recording. The problem is that I can't record for more than 7 seconds and set a resolution higher than 1920. I don't have Bit Depth tabs. Can you tell which version will be the best? And how to reinstall? Do you want to remove the current firmware first? And install another on stock? I downloaded: Nightly.2019Mar15.70D112_crop_rec_4k_mlv_lite_lossless_fps_override_experimental.zip Can I just replace all the files on the card?
Delete ML folder, delete autoexec.bin and copy extracted build content to card. Overwrite ML-SETUP.FIR or not, it doesn't matter because they are the same.
BTW: ML is not firmware, it is a firmware add-on. Running on your cam very similiar to an application on your PC or smartphone.
Thanks for your help, but this firmware add-on does not work for me, the menu does not flash every now and then, I managed to record a maximum of 10 seconds in 1920 10bit. Dual-ISO also seems to work incorrectly because it flashes all the time when recording 100 ISO 1sec and 1600 ISO 1 sec and so on. And after two attempts it burst with errors and no rec module wanted to load :( I uninstall ML as for me it does not exist for the Canon 70D. It's a pity, because when I bought it about 5 years ago, mainly with working ML in mind. PS. sorry for my english I use google translator.
You may have sd_uhs disabled. He is responsible for overclocking the sd card driver. I have a 70d myself and later I can see what it looks like for me.
Look here:
Quote from: ShootMeAlready on May 21, 2019, 03:54:01 PM
Sounds like you need to engage the overclocking.
- Select ML raw video modules, sd_uhs, and crop (the crop was disabled but I selected it anyways ... superstitious)
- Select ML raw resoultion 2560 at 2.35.1 aspect, with framing
- in ML turn global off
- in ML, Sd overclock at 160 MB/s, need to override the warning
- go back check your resolution message, it should be green (or flicker from red to green, I did not always see solid green)
If not reselect the overclock,
- In liveview, on Q menu select 24 fps, ensure AF is not set to facial tracking, I suggest single box
- In liveview, on what is by default the * button on back hit until 5X
- Press liveview, and it may go red, yellow, green, but after about 30s the red disappears.
When you are pre-focus the half-shutter press effects focus/liveview update (play with it)
Hope this helps
I uninstalled ML completely. I installed ver. magiclantern-Nightly.2019Mar07.70D112_crop_rec_4k_mlv_lite_lossless, I turned off face tracking and AF beep and so far it works! :)
Hello guys, nice to see the 70D thread's still active.
The 07/mar/19 build is working better than the 15/mar/19? What's not working?
15 March is like 7 March but additionally the FPS override function is available (usable but with a small glitch).
It's a pity I missed THIS (https://www.magiclantern.fm/forum/index.php?topic=14309.msg197404#msg197404) 2 years ago but a1ex is right: focus stacking & related features do work on the lua_fix branch for 70D, just need to be enabled.
Better late than never but this cam really deserves more love and a better maintainer (porting crop_rec presets...). ;)
Please read first post in this topic (https://www.magiclantern.fm/forum/index.php?topic=25786.msg213074#msg213074) for more info. Also here the download link:
https://bitbucket.org/ArcziPL/downloads/downloads/magiclantern-Nightly.2021Mar01.70D112_crop_rec_4k_mlv_lite_lossless_fps_override_focus_stack_sduhs.zip
I reverted also the FRAME_SHUTTER_BLANKING_* addresses to the standard from 4k_crop_rec branch because I don't know what I'm doing here and how to test. Further read on this feature: https://www.magiclantern.fm/forum/index.php?topic=14309.msg213436#msg213436
Quote from: ArcziPL on March 02, 2021, 12:12:45 AM
It's a pity I missed THIS (https://www.magiclantern.fm/forum/index.php?topic=14309.msg197404#msg197404) 2 years ago but a1ex is right: focus stacking & related features do work on the lua_fix branch for 70D, just need to be enabled.
Better late than never but this cam really deserves more love and a better maintainer (porting crop_rec presets...). ;)
Please read first post in this topic (https://www.magiclantern.fm/forum/index.php?topic=25786.msg213074#msg213074) for more info. Also here the download link:
https://bitbucket.org/ArcziPL/downloads/downloads/magiclantern-Nightly.2021Mar01.70D112_crop_rec_4k_mlv_lite_lossless_fps_override_focus_stack_sduhs.zip
I reverted also the FRAME_SHUTTER_BLANKING_* addresses to the standard from 4k_crop_rec branch because I don't know what I'm doing here and how to test. Further read on this feature: https://www.magiclantern.fm/forum/index.php?topic=14309.msg213436#msg213436
thx for the build!!1
REALLY great seeing updates here!
I'll repeat what i posted on the official 70D topic:
I have one 70D and one EOS M right now, if developers (hello ArcziPL) want to test anything, can count on me.
—-
edit: just adding a little request here, if possible: is it possible to add the option to choose if pressing SET will skip or load ML? I find myself using the 70D more like a photo camera and not using the ML that much, so would be great not having to press SET every time i turn the camera on, only when i need ML to boot up.
ArcziPL,
cannot thank you enough for your work!
Tried the 1mar21 build and love it. Only weird thing is, 160 MHz overclock does not seem to work. Not a big deal, but I thought I would report it here.
Here are my tests (write/read figures in MBps):
Build | Preset | PLAY-PH | MV-1080 |
any | No overclock | 42/44 | 39/40 |
15mar19 | 160 MHz | 67/72 | 57/60 |
1mar21 | 160 MHz | 21/22 | 21/21 |
1mar21 | 192 MHz | 78/86 | 67/70 |
1mar21 | 240 MHz | 90/107 | 76/84 |
Using this card: https://www.amazon.it/dp/B01J5RH06K/ref=cm_sw_em_r_mt_dp_YGG81KDGVTB2F6WDW6WZ (https://www.amazon.it/dp/B01J5RH06K/ref=cm_sw_em_r_mt_dp_YGG81KDGVTB2F6WDW6WZ).
Ciao,
Sergio
Thanks for testing and reporting!
Do you really have the 95MB/s version like on the photo on Amazon? So far it was reported, that only the newer one, labeled with 170MB/s, works with the 240MHz preset. And my 95 and 170 follow this rule. But it could be batch dependent.
ArcziPL, thanks for build with sd module.
My Kingston uhs-i u3 64gb card (https://www.amazon.com/Kingston-Digital-64GB-UHS-I-SDA3/dp/B00I3BQJNA) works only with 240 mhz preset. In other presets write speed 21mb/s.
240mhz - Playh-ph write speed about 85-90 mb/s, movie-1080 mode write speea about 78-85 mb/s, but speed mode unstable between turn camera on/off (i.e. start write raw video after turn on - ok, speed 50-80mb. start write another movie - speed drop to 21mb. Result of Sd cart test 95% of try: first write at high speed, first read and write,read - speed drop 21mb. Turn camera off/on and get chance ??% to get 21mb speet until turn off).
Thanks! I confirm the 160MHz to not work on my 70D with SanDisk ExtremePro 64GB 95MB/s.
The sd_uhs module in 2021Mar01 build is directly the module from this topic from theBilalFakhouri (https://www.magiclantern.fm/forum/index.php?topic=25841.0), which is tailored for 700D. I did a bad job not testing the 160MHz preset with 70D at all. I checked only the new ones: 192 and 250MHz, confirming both working with SanDisk ExtremePro "170MB/s" and only 192MHz working with the older "95MB/s" version of the card. Benchmarks shown similar results like vastunghia reported above. I don't know how stable they are during recording, as I don't use my 70D anymore. Would be nice if also others could report about the stability!
Great that Bilal published his code, so I could prepare a build with his great code as base but with registers of 160MHz preset reverted to
static uint32_t sdr_160MHz[] = {0x2, 0x3, 0x1, 0x1D000001, 0x0, 0x100, 0x100, 0x100, 0x1 }; /* overclocked values: 160MHz = 96*(4+1)/(2?+1) (found by brute-forcing) */
Here the new sd_uhs module only:
https://bitbucket.org/ArcziPL/downloads/downloads/sd_uhs.mo
And here a full vanilla ML build with this module already included. The rest stays untouched from 1mar21:
https://bitbucket.org/ArcziPL/downloads/downloads/magiclantern-Nightly.2021Apr04.70D112_crop_rec_4k_mlv_lite_lossless_fps_override_focus_stack_sduhs.zip
ArcziPL, thank you very much for the module.
On my card, the 160 MHz mode works very stable: I can switch photos and video mode, record videos and speed remains high.
At 160 MHz in movie-1080 mode, the recording speed is 48-58mb/s, in play-unk lcd mode, the recording speed is 65-71 mb/s.
192 MHz mode does not work.
The 240 MHz mode works as unstable (as I described earlier): the write/read speed changes directly during the reading process from 0 to 100 (the numbers change slowly).
We've all had best experience with SanDisk Extreme Pro "170 MB/s version" so far. If you want trying higher speeds, grab such one. Be careful, stick to reliable sources to avoid fake cards.
Quote from: ArcziPL on April 01, 2021, 03:37:27 PM
Do you really have the 95MB/s version like on the photo on Amazon?
Yes I do, the only difference being that mine was a refurbished model, so it has a 'REFURB' label on it. Could this mean that originally it was a 170 and it was mis-labelled as a 95 during refurbishment? Heaven knows.
Anyway, thanks a lot for the updated module! Oddly, at 160 MHz now I get good readings (67 w / 72 r) in PLAY-PH mode, but as soon as I switch to movie mode and start benchmarking in MV-1080, speed drops to 20. And then it stays there, i.e. even getting back to PLAY-PH mode will result in 20 MBps.
Oh, well. 192 and 240 presets seem to work fine, even though I still haven't had a real chance to do thorough testing. So bye bye 160. Just hope my new favorite preset (240) will not fry my card ;D
Ciao
Sergio
Hmm, 160MHz preset jumping back to 20MB/s can be reproduced with my card as well... Just randomly, in benchmark in MV1080. Maybe it's possible to find a more stable 160MHz preset. I wonder why I was able to record hours with exactly (? there was one parameter more in a1ex code) these registers' values with the build from 2019. Needs some debugging. Don't hold your breath, no time at the moment.
Hi All,
I think this is my first time posting here, I've searched high and low but can't seem to find a resolution for my issue so hope someone here can help please?
I had sd_uhs.mo on the latest build working great for about a week on my 70D with a sandisk 170MB's extreme Pro SD card, but now for some reason the sd_uhs module has stopped working in MV1080 mode.
Benchmarks in MV1080 mode are as follows:
160MHz = = W/20.2MB/s R/21.1MB/s
192MHz = W/20.3MB/s R/21.2MB/s
240MHz = W/20.5MB/s R/21.2MB/s
Actual video recording bitrates reflect the above too.
play-mv LCD mode:
160Mhz = W/66.2MB/s R72.0MB/s
192Mhz = W/77.6MB/s R/86.0MB/s
240MHz = W/91.3MB/s R/106.6MB/s
Benchmarks without the module loaded hover around the 40MB/s mark.
There is a red dot next to memory patches in the debug menu, I don't know if this means anything?
I've reloaded ML several times now, formatted the SD card too. I've also tried with a second identical card to no avail...
Am I missing something really obvious here?
Thanks in advance!
P.S ArcziPL, Is your source available please? I would love to have a play and contribute if possible?
Many thanks
Just an update from my previous post, sd_uhs seems to be working with the march2019 build so will stick with that for the time being while I try to figure out how to play around with the code, the one thing that baffles me is that it was working, very strange!
I managed to get my dev environment set up on a laptop I have running Ubuntu 20.04 already, I think I'll try to document this process as all the how-to's on the forum are a bit out of date. I also managed to get a compiled ML running in Qemu using my ROM dumps :)
Hi.
Tell me please the exposure log setting (that create mvi_1123.log file) in movie tweaks should work with raw video on?
When I shoot normal video (raw off) with log setting on - file creates.
Hi @ArcziPL
Could you share the source code for your 70D's build?
upd: found the answer myself
To whom it might concern: Bilal (he of the 650D/700D fame) had expressed his interest in working on the 70D build, but lack the camera itself: https://www.magiclantern.fm/forum/index.php?topic=25784.msg236046#msg236046
Hi guys. Why this version: magiclantern-Nightly.2021Apr04.70D112_crop_rec_4k_mlv_lite_lossless_fps_override_focus_stack_sduhs.zip writes "audio stop to failed" when I use "mlv_rec"
When recording with crop mode and some higher resolution the camera doesn't record the center of the sensor but somewhere to the side. Pictures here: https://imgur.com/a/sDEA7n2 (https://imgur.com/a/sDEA7n2)
I noticed I can shift the place it records by changing the zoom area but only up/down. When changing it left and right it kinda snaps to one of the edges of the sensor and never goes through the middle.
I had a 60D since I got it new in 2011 but never did much with ML on it until a few weeks ago thought I would try it out and realized one could shoot RAW, but I couldn't get more than a few seconds of RAW before it stopped. Also, there was the (lack of) auto focus.... so, I was able to trade up to the (3 year) newer 70D, and after past week of trying some ML builds, reading things on forum and here, I am happy to report that the in development ArcziPL's crop_rec_4k experiments for 70D (magiclantern.fm from March 2021 appears to be working for me. I haven't shot seriously yet, but with this build I do find I can record at least over 1 minute continuous, as 1280 res, 12 Bit RAW using SanDisk Extreme 200mbps (ML Benchmarks r/w just over 40mbps). The only issue with this build I seem to notice is when in the ML menus, they jump between ML and Canon (I have seen this reported by at least one other 70D user in forum (with video showing it). Even with that issue, I am very happy with this build on my 70D! Thank you for this work.
Quote from: sonicvision on September 05, 2023, 09:05:19 PM
I had a 60D since I got it new in 2011 but never did much with ML on it until a few weeks ago thought I would try it out and realized one could shoot RAW, but I couldn't get more than a few seconds of RAW before it stopped. Also, there was the (lack of) auto focus.... so, I was able to trade up to the (3 year) newer 70D, and after past week of trying some ML builds, reading things on forum and here, I am happy to report that the in development ArcziPL's crop_rec_4k experiments for 70D (magiclantern.fm from March 2021 appears to be working for me. I haven't shot seriously yet, but with this build I do find I can record at least over 1 minute continuous, as 1280 res, 12 Bit RAW using SanDisk Extreme 200mbps (ML Benchmarks r/w just over 40mbps). The only issue with this build I seem to notice is when in the ML menus, they jump between ML and Canon (I have seen this reported by at least one other 70D user in forum (with video showing it). Even with that issue, I am very happy with this build on my 70D! Thank you for this work.
Do try SD overclocking, you will get twice the speed.
Hi, As I read from other thread, I see it's able to use the SD hack module form Eos-m Crop mood build to Canon 70d, isn't it? Can I just place the .mo file in my canon 70d SD card ML folder?
Does it work that way?
Also can I replace High FPS module from M to Canon 70d to get 48fps 3x3 at full hd resolution.
I think about trying , but I want to ask before that cause might it damage the cam??
Quote from: kytai90 on October 05, 2023, 11:43:08 AM
it? Can I just place the .mo file in my canon 70d SD card ML folder?
Use thsi one:
https://www.magiclantern.fm/forum/index.php?topic=25841.0
Quote from: kytai90 on October 05, 2023, 11:43:08 AM
Also can I replace High FPS module from M to Canon 70d to get 48fps 3x3 at full hd resolution.
Nope
Tks, It worked and with resolution available now, 165hz is enough and stable.
I don't get "resolution available now" bit. You most certainly have resolutions available requiring amounts of bandwidth not possible with 240 MHz.
Here is an incomplete list of cards compatible with highest oc mode:
https://wiki.magiclantern.fm/cards_240mhz
Ah I mean the full hd and 2.5k (5x zoom) 11bit lossless is ok with 165hz.
I have read that thread, then buy e samsung evo plus 256gb using on eos m which is ok with 240hz.
On canon 70d I use a 64gb extreme (no pro) which is just stable with 165hz.
Also, May I ask, at update status thread by kitor, He said that the "ultra fast frame preview" is possible with models not support by crop mood.
Mean 70d is ok with that, right?
Ehm ... not yet.
It should work but needs someone to work on it.
Hi every one and who's considering a 70d for Magic Lantern. 70d does shoot raw in 60fps and in a good resolution (need strect for post)
Here is what I found
(https://i.ibb.co/TYVtMh0/native-menu.jpg)
(https://i.ibb.co/r45VXJ0/ml-setting.jpg)
Result:
(https://i.ibb.co/DKn8hbW/video-specs.jpg)
It took about 60MB/s.
Swear to god, I've search forum for this features on 70d many times, found people said that It can't (years ago) or they said that 60fps is not with raw. Also, I see no updates recently, then today I try and see the result. I need 60fps to learn shooting on my gimbal , now my camera has Autofocus and 60fps and Raw and mounted on a gimbal LOL.
Please correct me if Iam wrong or day dreaming
Would you please so kind to rescale your pics according to forum rules? Thanks!
You are kind of right. But it comes with some disadvantage:
You are in "5x3" (720p) mode. Means: 3 horizontal pixels are binned. But only every 5th horizonal line is scanned. This method is called line skipping.
In standard 1080p mode Canon uses 3x3: 3 horizontal pixels are binned. (Same as 720p). But only every 3rd line is scanned.
That is why frames have to be stretched by 1.67 = 5/3.
5x3 means footage is prone to aliasing. Please compare footage and you will see why most videographers are not using this mode.
Further reading: https://wiki.magiclantern.fm/glossary#pixel_binning and linked https://wiki.magiclantern.fm/pixel_binning
I did a test , Like you said, it's easy to spot moires , especially on metal increase sharpness will help a little bit. I want more fps because Iam learning to create clip with slow movement ,main subject will be Interior designs.
Hope Dev find a way to increase FPS (40fps/48fps) as well as less moire. With 70d sensor and a sharp lens (sigma) iam sastified with FHD resolution.
Also, I find some post and clip showing adjust timer A (FPS override>advance) for a lower fps from 30fps to 22fps or lower in crop mode, May I ask there is any number to adjust on timer A to reduce 60fps to 48fps or 40fps on this mode.