Messages

Sounds about right, considering the frame rate in 5x zoom is 30 by default.

Reducing the step size requires special support from the MLV converter (not even mlv_dump has this implemented), so it's not exactly a trivial change.

Ok, thanks for the info!

If you press the joystick multiple times, you can change the speed (though only in multiples of 8 pixels horizontally, or multiples or 2 vertically). Maybe that's why it doesn't react. Preview updates slowly, which can be confusing, but that's what we've got with our current knowledge about how LiveView works.

Modifying digital dolly to cover the full sensor is possible, but non-trivial (Canon recalibrates the vertical noise correction factors with each video mode reconfiguration, including when shifting the scanned area in x5 zoom mode). By default, Canon code scans a non-centered wide area in x5 zoom mode (3584x1320 usable area on 5D3) and moves it around as you move the focus box - notice a slight pause at certain positions on the screen, when it reconfigures the sensor.

You can, however, try something with the crop_rec_4k experimental build (caveat: requires fiddling)

- load crop_rec and mlv_lite
- set crop_rec preset to full-res LiveView
- reduce the vertical resolution in crop_rec submenu until you get the desired FPS (Target YRES = 1039 will give 23.973 FPS)
- recalibrate the CMOS[1] register to get good and centered image (trial and error)
- enable raw video and digital dolly - now it should cover the full width of the sensor.

If useful, I'll consider adding a full-width 1080p preset to crop_rec (maybe it can be pushed to about 5784x1080 at 23.976 FPS, or it might require slightly lower horizontal resolution).

Side note: the MLV spec also has metadata for 1-pixel increments for digital dolly, but would require special support from the MLV converter.

Hi Alex,

thank you for your extensive reply.I might try your suggestions mit crop_rec but for now I want to get the regular digital dolly to work correctly.

So 8px/frame would mean (3584-1920)/8/25 = 8,32seconds maximum or 4,8seconds for vertical movements, right? Is it possible to slow down the horizontal movement to 2px/frame as well? Because I just tested it and it seems like the vertical movement only has a duration of 3-4 seconds and the horizontal movement only around 6-7 seconds.

On the other hand I just figured out, that I always have to press the joystick to times to get it moving, but maybe that's normal.

Kind regards

Hi,

I am kind of able to use the digital dolly-feature, but for some reason it's not always reacting when I push the joystick. As well there is only one speed and it's only working horizontally. On the other hand it's not working over the full sensorrange, it's only using maybe half of the sensor for the dollymove. As I can't really find tutorial or documentation on how to use the feature I am asking here. Can anyone help?

I am on a 5D MK III with 1.1.3 and magiclantern-Nightly.2018Feb04.5D3113

Kind regards

Hi, sadly I can't bring MLVFS back to life. I had it working back in 2017, but now it's not working anymore. Updated both, fuse and mlvfs but the dialog to choose the mountingfolder doesn't pop up and the gear keeps on turning staying at 0%. Any suggestions?

I'm on a mac 10.12.6



Kind regards

It's all good, the dialogbox was hidden somewhere far away. :-)

Hi, sadly I can't bring MLVFS back to life. I had it working back in 2017, but now it's not working anymore. Updated both, fuse and mlvfs but the dialog to choose the mountingfolder doesn't pop up and the gear keeps on turning staying at 0%. Any suggestions?

I'm on a mac 10.12.6



Kind regards

From your description and screenshot, I'm pretty sure you didn't.

You used HDR video, which is a different beast.

Sorry, my fault! That was a stupid one, thought HDR-video was dual iso...

Yes, I'm pretty sure. Both modules (raw and dual iso) are on in the modules-menu. I got them both turned on in the movie-menu. It shows Iso 100/800 on the lcd and it's also changing from 100 to 800 while recording and as you can see in the screenshot of the folder there is one dark frame and one bright frame. The only thing I am a bit curious about is that there are two bright frames at the beginning 00000 and 00001.

I got the same problem as kgv5.

Material was filmed with iso 100 and iso 1600. .RAW was converted to DNG with RAWMagic 1.0 beta 7b. The cr2hdr package was installed and after that I tried to convert the dng-dual-isofiles to cr2, but it didn't succeed. For me it looks like cr2hdr is temporary creating a cr2-file but then deleting it, because right before it finishes there is a .CR2 which is automatically deleted.

I'm on a Mac 10.8.5
cr2hdr is version 1.4

Any suggestions?

Before:

After:

Hey there,

pretty short question I could not find an answer to here.

I got an old nightybuild from June on my 5d MkIII and want to update now to the latest Nighty Build. Do I just have to replace all the contents inside the ML-Folder or do I have to do something more specific? Bootflag and autoexec stays the same!?

Cheers
Fabian

Hey there,

currently I am running the Nighty Build of 17th june on my 5d Mk III and would like to update it now the the newest from june 27th. Do I only have to replace the "ML"-Folder, or do I have take a little more care and do something special?

Fabian

Sadly it's been removed, was it this book?

http://vatly.ucoz.com/_ld/0/36_Elsevier-ARM_Sy.pdf

I'd say that the main limit is the memory fragmentation followed by the data rate of the cad. If memory chunks were bigger (16M?) we would reach higher writing speeds.

That being said, if you have a crappy card there's not much you can do (run the bench as a1ex suggested and you'll see what's the theoretical limit of the card/controller combination)

On my 7D with a 400x Transcend it's 35MB/s... I don't know what's the limiting factor here. I know that the fragmentation is a big factor as well, but if it's not only one factor my thought was that an external ssd which can be plug in the cf-slot via an adapter could be a solution and maybe the chunksize can be improved as well (maybe)... but that was just theoretical thinking without knowing what's possible, that's why I was asking. :-)

Is the datarate limited by internal hardware or by the cf/sd-card?

Maybe there's a hardware workaround, if it's only the card which is limiting? Using some CF-Adapter you can write to ssd with or something?

Anyways, great work so far!

Will there come any new chance with the new firmware in august, or is it a problem which is not connected with the firmware?