Messages

Please,  if you decide to waste shutter actuations, add an option to disable it. Otherwise,  people who care about such things will not use your function.

definitely watch in 4k:

https://youtu.be/Zrm0F4ljv8U

the same technique as the others, first bessel and then 2x "sharp" superscaling.

i can't find any side effects!

watch in 4k, of course!

https://www.youtube.com/watch?v=aaMIy9UrQ_I

Added another video shot and upscaled the same way to the original post.
I'm really liking this setup...

The impulse to be unkind is not a beneficial one, not to the aggressor, nor the "victim", the community, nor the reputation of the project.

People, when belittled and judged simply because they reported their experience,  tend to be harmed as a result.  Is this what anyone wants?

I speak from multiple experiences and I pity all parties involved.

To the original poster: forgive them for they know not what they do.

i deeply appreciate your encouragement!

magic lantern is nothing short of miraculous.

the capabilities it adds to these cameras put them in a league of their own, plus it extends the usable lifetime of consumer oriented devices that would otherwise be in landfills further poisoning the planet.

i'm filled with gratitude and awe when making beautiful footage with a 10 year old outdated camera in this society of gear that is outdated 5 minutes after release...

that being said, it is not for everyone.

it's for everyone who wants to enjoy tinkering and "cheating death" with gear being pushed to the limit.

if you cannot tolerate a single unexpected stop or total crash requiring a battery pull, don't use it.

i've made hundreds of videos over the years with magic lantern (my channel has hundreds and a lot have been deleted over the years, in fact i will be culling them again soon) and i can tell you from vast experience that in the best case scenario you will experience lost takes at least 10% of the time.  sometimes there can be a battery pull failure followed immediately by another.  it's rare, but it happens.  it just did yesterday.  other times, there can be 20 safe recordings in a row.  obviously the longer the recording, the riskier the operation, which automagically makes it unsafe for very serious filming.  the last thing you need is to get increasingly worried about a camera failure the longer (and therefore more important) the scene you are filming...

in the end, it's a trade-off.  only you can decide what's best for you.

i don't care about losing a take.  it's a chance to do it better again.  but it costs me nothing.  i only wish the damned beeps were loud enough to hear.  i don't have a camera operator, and it is a seriously unpleasant experience to walk back to the camera after a 15 minute talk to find that recording stopped long ago.

this is the price we pay to use magic lantern.

i'm happy with it.  i love it.  i'm not interested in changing my camera until it dies.

i find it wonderful to look forward to future improvements in magic lantern.

but for each of us, this is an individual decision and an individual experience.

if you want the power of what magic lantern CAN DO, you must get a good camera such as the 5d3 and be prepared for the hassles and costs involved, but in the end it is capable of producing video that is world class if you can master it.

the quality of my video speaks for itself.

in the end, a camera is just a tool.

i'm sorry, but the files are already deleted.

i don't archive anymore, i've made way too many videos to keep the files!

i needed a break from card spanning hassles so i shot this video at 2880 using only the CF card with the 5d3.

it was a pleasant surprise to see how nicely it scaled to 4k using the settings i've been using lately:

bessel algorithm for basic scaling followed by 2x "sharp" superscaling.

that's it!

it's really hard to see any aliasing anywhere, and it is sharp.
it might work well for even lower resolutions...

EDIT: another video added, shot at the same resolution and upscaled the same way, with really beautiful results.  i haven't yet found a single problem! i even pushed the exposure a bit on this one with some highlight clipping.  it was inside the veranda with occasional sunlight reflecting on the crystal vase.  no problem!

this is a really great setting for quick and easy "4k". 

https://www.youtube.com/watch?v=G9fCoU76R6A

https://youtu.be/EJP-T_w3zks

the goal here was high contrast so to me the dark shadows helped

not truly golden hour because the trees are too tall, but as close as it gets before the shadows cover everything

bessel resize sharpening followed by 2x "sharp" superscaling in resolve with mlvfs using card spanning:

https://www.youtube.com/watch?v=7omYK5dTf9Y

Will do!

Well, it looks like it's the coronal quantum interference...

I tried it again and it worked.

The only difference is the passing of a couple of days.

I power cycled the PC and it failed again.

I power cycled again and it worked.

Random...

The moral of the story is any windows users having a similar issue should just power cycle until it works!

It seemed OK, but it's extremely sensitive to highlights, and there's NO preview!!

@names_are_hard
I'm not sure how to extract to produce new mlv and m00 files?
card spanning is the key here...

any tips appreciated!

here's a video i shot at <> 3400*1700, and there is a single frame "glitch" at about 7 or 8 minutes from mlvfs.  using separate card readers for each card definitely helped, but it is still not perfect.  this "bad frame" happened repeatedly, no matter how many times i rendered, and also across reboots of the pc.

the strange thing is that the frame is correct when scrubbing in resolve, but rendering always results in the error.

this setup is so precarious that it isn't surprising there are such issues.  it's a real drag, because it is such an amazing timesaver when it is working...

i may try different versions of dokan again to see if there's a "solution" but it may be related to so many other factors, including the peculiarities of this particular build of windows, or card reader drivers, or quantum effects due to the sun's corona, etc.

i was considering rendering the single frame as a tiff and then surgically inserting it, but even rendering as tiff resulted in the error!

https://youtu.be/We7suAl_X-w

i'm using a sandisk extreme pro 170mb/s sd card and komputerbay 1066x cf card

i recently did a few experiments of shooting at lower resolutions and trying to get similar quality via tricks such as using superscaling twice (resolve), and although the results were really quite good, maybe even indistinguishable to the viewer, when i returned to shooting at 3400*1700 for this video, it was just great...

simple resizing to 3840 using sinc algorithm:

https://www.youtube.com/watch?v=H4hS_uBehH8

Fascinating stuff! Thanks for the update.

Silly question: does this potentially expose computational resources that could somehow be used for arbitrary purposes?

Either way, nice find!

After shooting this video at a little over 3400*1700, I simply used 2x superscaling (sharp, sinc) in resolve to easily and quickly bring it up to 3840 with beautiful results!  Take a look at the beautiful sharp mesh around the subject tree in the opening scene...

https://www.youtube.com/watch?v=lO1I4UJr2kE

There was a sudden stop during the second shot, and although I was only 6 feet from the camera, I couldn't hear those few short quiet beeps in a forest full of singing birds, and I kept talking without knowing the recording had stopped.

Can someone PLEASE add an option for a continuous tone when the camera suffers a stop?

I asked years ago, and was ignored.  I know it's fashionable to ignore me, but is there really no one out there who also needs a better alarm when the recording crashes?

really?

The speeds are only similar in this mode. In every other mode the majority of the data goes to the CF card.
I wonder if it is related to the extra horizontal resolution somehow providing more time for each scanline,  if that's somehow applicable?
Just a thought...

This was shot in the forest, and I know from experience that it would have stopped suddenly if i was using the 3.X "x5" modes.

I'm wondering if the uhd 1:1 mode is more reliable because of the better data balancing between the two cards?

I find it to be almost equal data written to the SD and CF cards.

I'm really liking the look I'm getting in this resolution, including the DOF!

https://youtu.be/aPTMbGr1g-I

Yes, it was 14 bit!

and yes, this is a pretty amazing thing...

I really like how the writing is more balanced between the cards in this mode.  I wonder if there's a way to make this happen with the other modes too?  It might be the reason this seems to be more reliable?

I noticed during a recent video shoot that 3840*1536 in UHD 1:1 mode seemed to be quite stable for recording with card spanning, overclock and bilal's hacks enabled, at least for a short clip.

Here is a video using only that mode.  It worked perfectly!

One thing to keep in mind:  This mode is quite good at balancing the data between the 2 cards, so you either need a 256GB SD card, or be prepared to run out of recording time pretty quickly...

No upscaling!  MLVFS straight to resolve.  Edited, graded and output to NVenc HEVC 10 bit 4:4:4 in record time!

I never thought I'd see native 3840 raw video from the 5d3...

https://youtu.be/t16bqfoqhbY

OBVIOUSLY watch in 4k!

Hopefully we will get faster options soon!