Messages

Is anyone able to record long clips? I got a 1920x1080p23.976 clip with audio recorded to my Komputerbay 1050X 128Gb card, and it appeared to be running continuously ok (except for onscreen messages about "expected frames" that I don't really understand), but recording stopped soon after the 4Gb limit was hit. My card is formatted exFat, and I can record to it with the standard raw recording for 10 minutes and beyond without issue.

I'm processing the file now, it appears to have actual audio (I listened to the wav), but I haven't yet viewed the clip to see if there are any apparent skipped frames.

Got continuous recording working now, with possible skipped frames.

This may be something unrelated to mlv and simply a new (to me) way that the nightly ML is noting skipped frames, but I'm not sure what to make of this "71 frames / 4115 expected" text at the bottom of the frame while recording.

I've got a screenshot I'd be happy to post, but clicking the "Insert image" button in this form just inserts a couple of img tags into my post -- doesn't seem that there's an upload option. Maybe this'll work:
Or just this link: https://www.evernote.com/shard/s1/sh/370ae243-27cf-48dd-9b16-853ebc97ae58/e5767bbf15dc638cf8dba588652309ee/res/ed0c02ff-8f4b-495c-9dc6-73a542de586c/skitch.jpg?resizeSmall&width=832

It appears to be recording fine and the buffer graph at top is not filling past the end, but that text at the bottom alternates between saying things like "00:39.941 frames. continuous OK !" and "58 frames / 5102 expected". I'm not sure how to interpret this.

When I installed the latest nightly I blew away my settings. So I'm not sure what in my previous settings caused it to be recording to SD.

OK, got the latest nightly build and the latest mlv_rec modules installed now and am ready to try again.

Is it wrong that in the ML menu, the descriptive text for mlv_snd.mo is "Adds SMPTE output functionality to mlv_rec"?

1. I loaded the mlv-rec and mlv-snd modules and set it for 1920x1080p23.976 and tried recording some raw video to my Komputerbay 128Gb 1050X CF card. It gets about 48-70 frames in, reports a skipped frame or two, and stops recording. Every time with the same result. I think spanning is off, and there's only files recorded to CF, but I'm not sure (need to poke around and find that setting again). Recording at the same resolution and frame rate using the normal raw recording module works flawlessly to the same card.

I just looked at the SD and CF card and found the answer to this problem -- it was trying to record everything to the SD card. I had the preferred card set to CF, so I figured I had this set properly. Maybe there's some other mechanism to use to tell ML to just never, ever try to record anything to the SD card?

I've run into three problems with the latest (er, yesterday's) build, I figured maybe documenting them here would help development or someone could tell me what I'm doing wrong.

1. I loaded the mlv-rec and mlv-snd modules and set it for 1920x1080p23.976 and tried recording some raw video to my Komputerbay 128Gb 1050X CF card. It gets about 48-70 frames in, reports a skipped frame or two, and stops recording. Every time with the same result. I think spanning is off, and there's only files recorded to CF, but I'm not sure (need to poke around and find that setting again). Recording at the same resolution and frame rate using the normal raw recording module works flawlessly to the same card.

2. I booted the camera with mlv-rec and mlv-snd enabled, and (without recording) hit the zoom button to see a close-up view for focusing. After focusing, I didn't hit the zoom button again to pop back to the normal view and instead just hit record thinking the view would pop back to normal and recording would commence. Instead the view froze, and remained on the screen after I shut down the camera. I had to remove the battery to get it to power off.

3. It's been noted earlier in the thread, but the mac version of mlv_dump claims the .mlv file lacks a header unless the .IDX file is moved, deleted, or renamed out of the application's view. If the IDX is present, no decoding happens. When I renamed the .IDX file to end in .IDX.bak, mlv_dump was able to see the file and I could view the metadata for its contents just fine.

I haven't yet tried the SMPTE module. I've got a 3.5mm dual-mono to stereo splitter cable ordered, and once it arrives I'll try running the camera's headphone jack into 1 channel of my zoom H1 and the videomic into the other. Maybe I can get Resolve or some other program to recognize the timecode track. I've read all the comments here and am not sure if anyone's gotten the module to work for syncing.

I'd love to see the camera play the filename as a series of beeps in morse code (i.e. "MVI1341") in the first couple of seconds after record is pressed, followed by a long solid beep that always hits at 0:00:03:00. That way one could identify the clip to which an audio file belongs and its sync point.

Alright, got the latest 5D3 magic lantern files in there and it's all looking good now. Great to see the rapid pace of development!

I'm having  a bit of trouble, likely expected with these cutting edge builds. I'd love to have magic zoom but remove the text on the screen that tells me the names of the two files that are being written, as it's covering at least 20% of the video with those names and bitrates. All I want to see is magic zoom and a timer telling me the length of the recording. Haven't discovered the right option though I've explored every possible menu as far as I can tell.

I'm finding that if I set for spanning, I can only record about 10 seconds of 1080p23.976 raw video before it skips a frame and stops. But if I turn off spanning it records continuously just fine. Maybe it's due to the speed (or lack thereof) of my SD card? My CF is a Komputerbay 1050X 128Gb that's been working great for 1080p23.976 canon raw for the past couple of months.

One feature idea: I record second system audio using a r0de videomic plugged into a zoom H1. A pretty cheap, nice=sounding combo. It'd be neat if the camera had a way of outputting a series of beeps at the start of recording that would identify the name of the filename to which the audio recording would belong. Morse code perhaps? Maybe the name of the clip in morse over the first couple of seconds of the clip and then a beep that coincides with the exact frame on the 3 second mark to use to sync? Or a beep that coincides with a little dot in the corner of the frame, fire the flash, darken the frame, something that can be used visually to line up with the beep. Anyway, just throwing that out there in case it makes sense to anyone (or in case it's already in there and I haven't noticed).

It's odd --I have fonts files, was recording raw just fine before, and everything looked fine. Can someone tell me which distribution of magic lantern has the files that are compatible with the mov 2.0 autoexec and modules? The latest? Or do I need to backtrack a few versions?

I downloaded the latest pre-built binary (was at http://upload.g3gg0.de/pub_files/27a867063ed87d2f079cde5f8b577a88/mlv_rec.zip), placed its autoexec.bin at the root level of the SD card and the other files in modules, and am now experiencing a problem with the magiclantern menus in my 5D3 (as well as text displayed on the liveview screen when shooting). It's now as if my camera's screen is cropping its input (looks almost like overscan), as if the buffer for the screen is larger than the screen's resolution and it's just displaying a center extraction. Even the boot screen features text cropped at the edges. And the explanatory text for ML menu options runs on top of other menu items and off the screen.

I've removed my config files and restored defaults, but that didn't help. Perhaps I was using a sufficiently-old set of ML files that I'm missing some new smaller font that would make everything fit? The text all looks huge compared to what it was with my last set of ML files (was recording raw, but didn't have MLV 2.0).

Thanks for any help or info. Here's a screenshot showing what menus look like:

I hooked all my parts together: SATA to mSata adapter (and SATA power connector from my computer), mSata to ZIF, ZIF to Toshiba CF, CF to USB3 CF card reader, Card reader to computer, and got nothing. The LED on the card reader lights up when powered up and a card is recognized, but it remained unlit. The orientation of the ZIF to CF cable wasn't obvious, so I tried it both ways (didn't seem to fry anything, but neither worked).

It'd be nice if I had devices that'd work with each element of the chain (i.e. something that takes an mSata connector, something that takes ZIF) so that I could find the weak link. I'm not sure where to go from here. It seemed like a possible route that might work using available hardware.

The fact that reviews for the adapter I've chosen mention success at using it to connect 256Gb mSATA SSD drives to iPods gives me hope --as far as I know all the iPod classics use PATA IDE drives. So this would mean the adapter is successfully bridging from mSATA to PATA IDE and allowing access to the mSATA drive's full capacity.

Be careful with the zif adapters. There are some that look like they might work but I have read on a few vendors sites specific disclaimers that they are not intended for straight cf-IDE.

I think I'm on track.

If I had an ssd with msata connector, and could figure out a way to power the ssd, I'd be able to test all this gear out right now. But what I've got as a testbed is a crucial m4 sata SSD, so I need a way to connect it to that mSATA to ZIF adapter. And I found it:

Micro SATA Cables - mSATA to 7pin SATA Adapter
http://www.amazon.com/gp/product/B009UDAINW/ref=oh_details_o00_s00_i00?ie=UTF8&psc=1

So that device will go from my ssd drive to the msata connector on the adapter, where it's also bridged to IDE. Then the ZIF to CF adapter connects to the camera's slot. Power? Maybe that SATA to Mini SATA cable with power adapter I'd bought will help, maybe not. I'm still investigating.

I had thought maybe this item:

Micro SATA Cables - mSATA SSD to 40 Pin ZIF Adapter Card as Toshiba or Hitachi ZIF HDD
http://www.amazon.com/gp/aw/d/B009BA5JU6/ref=ya_aw_oh_pit

Looked as though it might accomplish the bridging between SATA and IDE, and then this item:

Micro SATA Cables - 40 Pin ZIF to 50 Pin 1.8 Inch CF Toshiba HDD Adapter
http://www.amazon.com/gp/aw/d/B009BG1ETA/ref=ya_aw_oh_pit

...could go from the previous adapter to the cf connector.

So the net effect would be the ability to connect a sata ssd drive to the cf slot in the 5d3. I ordered both items, but unfortunately I don't recognize the actual connector on that msata to ZIF adapter and am not sure how to connect anything to it.

I also grabbed one of these, thinking it might come in handy for powering the ssd and going between a couple of common sata connections.

I still figure the first two items above may be promising, but have hit a wall for a moment with the msata connector.

As long as we're offering up feature suggestions:

Frame numbers based on time-of-day timecode, generated using the file creation date as a starting point if no metadata is available.

Each dng sequence written to its own folder.

Addition or alteration of the dng files such that they'll work in davinci resolve. That software works with dng sequences ok, but not ours.

I plan to have a look at the source code and see if I can't contribute, but am not the best coder and might as well list those ideas here first in case they spark the interest of a developer who's already up to speed on the project.

The last link should be:
Syba SATA to Mini SATA Cable with Molex Power Adapter (CL-CAB40042)
http://www.amazon.com/gp/aw/d/B005BCNAWM/ref=ya_aw_oh_pit

I had thought maybe this item:

Micro SATA Cables - mSATA SSD to 40 Pin ZIF Adapter Card as Toshiba or Hitachi ZIF HDD
http://www.amazon.com/gp/aw/d/B009BA5JU6/ref=ya_aw_oh_pit

Looked as though it might accomplish the bridging between SATA and IDE, and then this item:

Micro SATA Cables - 40 Pin ZIF to 50 Pin 1.8 Inch CF Toshiba HDD Adapter
http://www.amazon.com/gp/aw/d/B009BG1ETA/ref=ya_aw_oh_pit

...could go from the previous adapter to the cf connector.

So the net effect would be the ability to connect a sata ssd drive to the cf slot in the 5d3. I ordered both items, but unfortunately I don't recognize the actual connector on that msata to ZIF adapter and am not sure how to connect anything to it.

I also grabbed one of these, thinking it might come in handy for powering the ssd and going between a couple of common sata connections.

I still figure the first two items above may be promising, but have hit a wall for a moment with the msata connector.

For what it's worth, raw2dng.exe is unable to convert my 5.16Gb raw file to dng, comes up with "this ain't a lv_rec"... error. So I'd guess maybe no footer was recorded to the file due to the sleep/shutdown.

I looked at the 5.16Gb raw file in a hex editor (hexfiend), and it definitely has a footer. I also tried overwriting its footer with that of a known working raw file, but raw2dng.exe still gave me the "ain't" error. If anyone would like to take a look at the original raw file to see if they can figure out why it can't be converted to dng, I've shared it from my dropbox here:
https://www.dropbox.com/s/aaxl01lptoqbywp/plants-exfat-nolvrec.RAW

So after entering all of those values and finally getting that clip set up properly, is there a way to apply those settings across a set of imported clips? I've got approximately 10 30-second clips that were shot in one session, they're all going to get the same settings. Selecting all of them and then clicking on those panels and setting the settings only seems to have stuck for the first clip in the list. The inability to apply to a batch of clips these input and output curves, demosaic type, white balance, and LUT settings, well that's going to be a bit of a pain.

And beware, double-clicking the "Protune" thumbnail to set the LUT to CStyleLUT also pops the COLOR MATRIX back to 'SOURCE'. So after setting the LUT one has to go back up to the COLOR MATRIX panel and set it back to CUSTOM.

I've given up on setting the RED, GREEN, and BLUE settings in WHITE BALANCE. Setting TEMP and TINT to the values in the screenshot seems to leave the clip looking all right, with RED at 1.7330, GREEN at 1, and BLUE at 1.3179. Changing the individual colors to match the screenshot has had some weird effects on the value of TEMP and TINT and the overall look of the image.

To be honest, when I let the color matrix setting go back to 'SOURCE', but keep all the other settings specified in the thread, the resulting image looks a lot more like the sort of flat log curve that I'm used to working with. How were the set of color matrix settings for that screenshot derived, what was the intent?

This workflow has promise, but the software seems to want to fight me. Maybe I'll get used to it and figure out the workflow.

AHA! It seems one can enter all of those specified values for WHITE BALANCE and not have them cancel/modify each other if one specifies the Protune LUT in the LOOK panel (the LUT is actually named "CStyleLUT" in that panel's drop-down menu and Protune in its thumbnail preview, or at least clicking the "Protune" thumbnail applies the "CStyleLUT", which is confusing enough that I'd call it a bug).

So set that LUT first, then change the WHITE BALANCE values, I guess.

This workflow looks very promising.

I'm finding it impossible to replicate those settings in the WHITE BALANCE panel. I can type the value for TEMP and TINT, and then as soon as I type the value for RED the TEMP value changes, same goes for BLUE. Is there some way to actually enter the values from that screenshot without other values changing along the way?

Look if "Power saving" is set to "Disable" on Canon menu. If it is, that shouldn't happen.

I'll check that setting when I next try. If it fixes it, I'll add that to the list of settings I have to double-check or change before recording.

For what it's worth, raw2dng.exe is unable to convert my 5.16Gb raw file to dng, comes up with "this ain't a lv_rec"... error. So I'd guess maybe no footer was recorded to the file due to the sleep/shutdown.

Is anyone else finding that their 5D3 goes to sleep in the middle of recording? I've formatted my 32Gb Lexar 1000x CF card as exFAT and enabled >4Gb recording, and the longest recording I've managed (at 1928x1080 raw) before the screen shuts down and the mirror locks back into place is 5,159,790,912 bytes (5.16Gb). Hitting the start/stop button wakes the camera back up, but it's as if it's doing a full boot from shutdown as far as Magic Lantern is concerned (I see the card speed test happen, and then I have to go re-enable the modules and configure raw and audio before recording).

I'm not sure what's going on. Maybe somehow ML is taking over to such an extent that the Camera OS doesn't know there's activity going on, so it goes to sleep? It happens every time.

It's amazing how quickly this hack is developing into a useful feature, btw.

I took my AdobeDNG files and moved them into a replication of the CinemaDNG directory structure (following the 'MyMovieNickPatonIkonoskopDNG' example supplied on Adobe's CinemaDNG page). I then imported that folder into Davinci Resolve's media pool. The result was the same as when I imported the DNG sequence into resolve without the directory structure -- the sequence came in and had the right number of frames and duration, but Resolve thinks each 1920x1080 frame is 128x96 and renders them as a super-low-resolution low bit depth image (looks to be posterized down to about 4 colors).

Maybe there's something needing a tweak in the dng headers created by Raw2dng.exe? The dng files load just fine in Adobe Camera Raw, but DaVinci Resolve sees them as 128x96.

still this is a *theory*, but i expect the consumption and the temperatures not to raise at all.
bitrate hack on 7D in contrast did both: massive CF access and H264 encoding, but noone who calls himself one that is "talking with canon engineers on a regular basis" cried about sensor temperature there

people who have no clue what is happening in the circuitry are telling us what can go wrong?
so yes, i call it bullshitting.

That'd be my guess, but speaking as someone who has no knowledge of how the sensor actually operates, I wonder if setting it to record to the live-view buffer at high resolutions may possibly heat the sensor more than is normal during recording (given that normal h264 recording is probably only using every third line of the sensor at some absurdly low res, or some such thing).

I figured I'd just pass long these reservations just to see how easily they can be knocked down by people who understand how the sensor and camera actually operate. I don't myself expect that heat will be an insurmountable problem for the sensor, and as I've said, I've cast my lot by buying a 1000x CF card.

Two questions:

1. I see a decent number of samples on the net of the new feature recorded using Technicolor Cinestyle. Is there a better S-log profile to use with 14-bit raw than Cinestyle, or is a style even necessary with raw? Isn't Cinestyle designed specifically to compress both the shadows and the highlights within the range of exposure that would otherwise be truncated by h264 compression -- and now that we're skipping h264 altogether we can take advantage of that extra space in which to record shadows and highlights? Cinestyle may be compressing the range more than necessary, it may be a waste to use it with raw.

2. There are a bunch of indirect warnings from Canon engineers popping up in this twitter feed (note: Mr. Sutton is not a troll, and is undoubtedly trying to pass along what he deems useful info from the source, so please give him the benefit of the doubt):
https://twitter.com/mns1974/status/334132774132908032
I'm skeptical, as I would expect that there'd be safety shutdown procedures in the firmware on the sensor that don't depend on the proper behavior of applications running on the camera's OS, but who knows. I guess we'll all know within a couple of weeks. I've ordered my 1000X 32Gb CF card, and will definitely be shooting some raw in the near future unless peoples' cameras start exploding.

Thanks so much A1ex and all Magic Lantern contributors. As if magic zoom wasn't enough!