Messages

What features is that? I don't really care about slowmotion, sometimes I do 30 to 25 fps for a subtle effects, but that's it. And I don't go for crop modes or higher resolution. Besides AF and swivel screen all I want is continuous recording for a few minutes since I like longer takes.

You can actually shoot 50/60 FPS with the 70D at 1832x616 and then stretch it in post. Here's a clip I shot at 50 FPS and slowed it down to 25 FPS. I think it looks pretty good aliasing-wise.

Does the 1x3 mode compensate for the lack of an AA filter in the 6D? I mean, does it hide the aliasing as well as when used on AA-filtered cameras?

Very interesting results. Thank you for tackling this!

There are definitely aspects of the RawTherapee versions that look better (pillows) but certain things that don't look as good (light fall-off on lamp, colour cast and light falloff on window).

Will give the recipe a try and see about adjusting the workflow overall in these cases.

Side note: Increasing the Color noise reduction in LR can remove most of the color aliasing / artifacts with little to no impact on the rest of the image.  I discovered that with another scene I had shot elsewhere that has strange artifacts due to a funky bed sheet pattern and it works decently well here too. The only side effect I've seen so far is it removes some saturation is areas that have only small patches of colour (like the spine of a book on a shelf if it's very small in the frame overall). Will be interesting to see how RawTherapee handles that same situation.

Again very appreciative to have such great help in the community. Thanks!

I can confirm that the Color noise reduction does help a lot with false color artifacts. I usually crank it to 100 and also lower the Detail to 0, if it's really bad. Yes, it does affect saturation a little, but the benefits far outweigh the cost, imo.

[EDIT: Yup, with "Beep" enabled, I get 5-20 secs. before an Err70. Thank you very much, ArcziPL, for pointing this out!]

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!

[Mar07 Build]

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.

[Mar07 Build]

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

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.

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 problem

Of 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.

You know about Canon's service advisory about Err70 on 70D?

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.

[magiclantern-Nightly.2019Mar07.70D112_crop_rec_4k_mlv_lite_lossless:]

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:

Code Select Expand

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 + 2380K

This 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:

Code Select Expand

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 + 1800K

Code Select Expand

ASSERT: 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 + 1801K

The 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.

[C700d]

C700d, if you get a small external HDMI monitor for your camera, you'll get accurate monitoring in 1:1 crop mode, without the issues you see with the built-in screen in LiveView. Also, try limiting the FPS to 24 (they seem to default to ~30) and lowering the bit depth for a more stable recording. The SD hack needs to be turned on, of course.

@ theBilalFakhouri I think it was the mlv_lite module that made the difference. The error disappeared even without this new version of mlv_lite, when only crop_rec and mlv_lite were enabled. Enabling anything else produced the same error. Anyway, I followed your advice, did all the things and now it works. LiveView is pretty much unusable, but it works! I'll be playing with settings, resolutions, etc. When I have something, I post a video. Thanks a lot for the help. Newbies like me really need it.

@IBIRRU

Okay my bad. I compiled a build from crop_rec_4k branch and in the experimental page it's from crop_rec_4k_mlv_snd and it has some differences so Try this Build which I use.

Hi and congrats on the great advancements. Unfortunately I have exactly the same problem as IBIRRU and the build above produces the same errors as the July 22nd build I previously tried it on. It's probably something very simple we're missing, but I can't figure out what. Any help would be much appreciated.

Something weird happened with the latest March 10th build on my 700D. MLVProducer (3261) couldn't properly remove the focus dots in my footage and was completely incapable of removing false colour artifacts. I switched back to the February 24th build and everything worked correctly with it. I have no idea where the problem could be exactly, but I thought I'd report.

I want to mention something that I don't think is a bug, but I still wonder if something can be done about it. I'm talking about the Reduce False Color function of MLVProducer, which is pretty necessary with RAW video. It works fine.. unless there are saturated reds in the frame, such as flowers, clothes, etc. It absolutely destroys the reds and it can make the footage unusable. Can something be done about it at all, or is it perhaps too complicated to fix?

I can confirm the disappearing workspace panels issue, although it stopped happening when I changed some (unrelated) settings (Ctrl+S) and applied (saved) them. Also, the first couple of times I tried to render (export) a video, the program stopped responding. I found out it was because it was looking for the default 'output' folder in the main directory, but since it wasn't there, it just froze. I created an 'output' folder and that fixed the issue. Of course, pointing out to a different existing folder would also work.

Otherwise everything works.

[Preview version]

Preview version
sourceforge is lagging.
bmber.in/download/mlvp.alpha.build3151.PREVIEW.zip

changelog

This is awesome! I'll do tests tomorrow and share my experience. Thanks again for your work!

AWPStar, thank you for developing this software! I've been playing with it for some time and I have a few questions and suggestions.

When I open an MLV file, the exposure is nothing like what I've seen on the camera screen (700D) - it's a few stops darker. However, If I export the video to Cinema DNG, without touching anything, the exposure of the dng files is correct. What could be the cause of this? Also, is it possible to make importing image sequences as video in MLVProducer?

I like exporting MLVs in image sequences, then correcting and grading one in Camera Raw/Lightroom, sync the settings with the others and then import into a video editor. The trouble is, the hot pixel removal and the false color reducing doesn't work when exporting the MLV as Cinema DNG image sequence, unless I then encode the sequence into a video format (in Premiere Pro), then import it back into MLVProducer, correct the false color and then re-encode again. That's a lot of steps where things can go wrong.

Another thing is the Cinema DNG files from MLVProducer aren't recognized in Photoshop or Premiere/After Effects as an image sequence. Probably something to do with missing metadata. If I convert the DNGs into JPGs, then the sequence is recognized. Can you suggest something to try and fix this?

Thanks! BTW, obviously I'm excited about the new version with compressed raw support. Keep up the good work!

@burgerkrieg When you open the .mlv file in MLVProducer, make sure to check 'Scale 3X5'. That should fix the squished footage when using crop mode. I just want to ask, do you have the same problem with focusing pixels as I have (see above)?

Hello, everyone! Got a 700D with 1.1.4 FW here and I'm willing to cooperate for testing things out. I'm very interested in this 'crop mode' and it's potential to get RAW video with enough resolution to upscale to 1080p with good results). I tried this build: "magiclantern-crop_rec.2017Jan31.700D114" and it works, however, I can't seem to get rid of the focus dots in MLVProducer (latest rev. 2722 alpha). They appear even in h264 video, if crop mode is enabled. Here's a screenshot: