Messages

1.2.3 quad buffers output, rather than triple buffers.  This is probably related to changes in output capability.  I don't know for sure if this is why things are "slower" (or even if 1.2.3 is slower!  There's certainly no "extra processor" allocated).  You would expect this to increase latency by about a frame, which is unlikely to be perceptible.

ML enables clean HDMI in the same way it works on every other cam, by stopping display of Canon decorations.  Not quite sure what you're asking here.

As always, if you're concerned about changes in performance: you have to measure it.  People are terrible about estimating performance and often think a change makes things worse (or better!) when really it just feels different.

I am not concerned with anything, I was simply asking and projecting my idea of how it works. I did also say "something like that".
 I am not under the "impression" that it is is slower, it is slower, according to A1ex. Not by much, but it does not record raw video as fast as 113, because of the Quad Buffering in 123, one buffer less available for ML tasks (thanks for the explanation).

?
Clean HDMI out-of-the-box requires 1.2.x.
Clean HDMI with ML for 1.1.3 and 1.2.3.

I did not know that ML made Clean HDMI possible on 1.1.3, I thought you needed 1.2.3 for clean HDMI output.
To my understanding fir 123 runs a little slower than 113, because Canon allocates one extra processor to the HDMI module or something like that.
How does ML enable Clean HDMI? Does it also allocate extra processing for the HDMI output?

3) it works but it's not a correct framing even if you stretch it to 2.35:1

I use monitors all the time, they work 100%. As long as they support 1080p, there should be no problem.

But you need to run firmware 1.2.3 or above for Clean HDMI Output. I recommend you update or downgrade to 1.2.3. and the appropriate ML version

Question 1: I also never had a 5D3 overheat, that feature was introduced with the RF line

Yes to all other questions

I would rather do the stretching in the Color Tab. In the Sizing - Input Sizing, under Height, set your desired stretch factor fx. 1.664 for ML line-skipped 60p.

This way, you can mix different source material with different aspect ratios, so you don't stretch 2:35.1 footage to 16:9.

But if the entire project has source footage from same camera and aspect ratio, then set project settings to your desired resolution and stretch to corners.

I also think you should set your project to a standard resolution, like 5k or 6k, because I think you might risk degrading the quality of your uploaded videos, as the host will most likely resize 4800x2040 either down or up to a standard, which can have adverse effects on quality, but ymmw.

I just wanna say that this Update Thread is great! It's really nice getting an overview of the progress here.

I cant hold myself.

This is just plain wrong, you are not increasing the DR, you are just mapping out the data to V-log with an overly complicated workflow changing exif data. There is no magic there, you can do the exact same thing with a color managed workflow.

Even in a Rec709 workflow, your data is all there. Try making a project in rec709, use CST rec709 to V-log.

But I'd recommend the color managed workflow.

Input: Linear
Timeline color space: Vlog
Output color space: Vlog

If you got mixed camera footage, use the Media Color Space input by right clicking on the clips you need changed e.g. You got 5d3 dngs and Sony Slog 3 -s-gammut 3, select the sony clips and right click for the drop down menu and set input color space to Sony slog 3 -s gammut 3 and voila, all footage is now correctly transformed to V-log and its without you having make complicated nodes using CST's to align all footage and bog down performance even more.

And if you want to stay in YRGB "rec709", dont be affraid of pulling those Camera Raw parameters.

Happy he is okey and happy that he found the answer!

Thanks for sharing.

I had a sandisk card reader fail.

It could not finish transfers and therefore I had same issue with mlv files.

Try adifferent card reader.

What lenses are you shooting on?

Iso 200 at f2/2.8 should be a good starting point for bright highlights e.g. Fireworks.

Fireworks are bright, so be careful you don't overexpose them, you ideally want to record the different colours of the fireworks and not just blown out highlights, lol pun intended.

Nearly everything about Magic Lantern EXCEPT raw video is awesome. The recent hype however is all about ML raw video, and that aspect of the hack is absolutely horrid in actual use. Source: pro cameraperson for 25 years who has also been using ML for a decade+

Sounds like he tried rawvideo when it was released and still thinks he has to command prompt the entire processing of the .raw files

@Danne Yes, I can. I will post some examples.

When someone is wrong on the internet     

2 years ago, I unfortunately shot an entire day with 12 bit lossless, not to my knowledge, I had been messing around with slow mo and bits and forgot to reset it to 14 bit lossless..

I didn't figure it out until I was color grading and I kept feeling that the colors were weird, like Reds would solarize and the overall lacking of colour information was weird. I actually thought the Sensor of my 5D was about to die.

The biggest give away was in the colors that are close to clipping, like böue sky surrounding the sun, a huge chunk of the blue sky around the sun will turn Magenta, like really ugly Sensor pattern magenta, that is impossible to key out because of the pattern, so you have to VFX that out. Basically it felt like the highest part of the ETTR range lost its color information

I recommend you stick to 14 bit, unless you are okey with losing close to a stop of usable dynamic range.

I cant speak for mlv app, but working with dng in resolve, any clip with log conversion applied with the sun directly in shot will most likely give you "black sun" (pink) artifact.

Color managed workflow:
Input: Linear
Output Color space: <C-log2, Log-c or <slog 2 etc
Output Timeline color space: <C-log2, Log-c or <slog 2 etc

Basically any log conversion that stretches the dynamic range beyond its input will show pink sun artifact.

I usually counter it by tracking a power window on the sun with Lens Blur and increasing green channel output until the magenta turns white(neutral).

Edit: those DNG's have already been darkframe subtracted, not sure if that is causing the black sun artifact.

Very nice!

I like the song too, but I don't think it fits for this video. Its to pumped up compared to the motion and images you portray. I would have went with a more melancholic soundscape.

Other than that, I love your colors, really nice, natural, vibrant and Saturated colors.

What gear did you use? Lenses?

Can you share more details like recording settings?

Are you running any kind of hz Speed hack?

Are you buying from a reputable seller? There were a lot fake CF cards around when ML RAW came a long. You should check card read/write speed before putting it in camera next time. If you get a new one that is.

Also you say your older cards are still fine?

What did you format your card to? Is it exfat? FAT32? I think that 5d2 does not read exfat.

I used my lexar cards on my 5d2 back in the day and my brother used it for years after with his lexar cards and never had any issues. I just got it back from him and it still runs with ML and shoots RAW like there is no tomorrow.

I take it one further..

Atomos Footage is like a bright candle, its bright and pretty.

Magic Lantern is the sun 

Care to share some details?

Lenses, lighting etc.

Looks like you shot everything wide open, intentionally I suppose, though I have to admit it is not my cup of tea.

Anyways, congratulations! The 5D3 truly is more than good enough.

That did the trick, you're an expert to me! Thank you.

Code Select Expand

exiftool -IFD0:DefaultCropSize="1952 1112" *.dng

Code Select Expand

exiftool -IFD0:DefaultCropOrigin="0 0" *.dng

I put the command in ExiftoolGUI and it changed the Metadata of all the DNG's in the folder. I had to also change DefaultCropOrigin to 0 0 to make the DNG's viewable in Windows Photo Viewer and Photos and probably other software.

And thanks to everyone else for helping out!

Thank you all for looking in to this.

I had some issues with my cloud yesterday, here they are: https://drive.protonmail.com/urls/W1XSGHAEVC#Wn4Gtp4spxRD
Its 12 frames cut out, you can look at the printed dots in the notepad and see the crop/uncrop.

I will try your suggestions now.

EDIT:

@ArcziPL The GUI does not work, the Save button remains greyed out. Is the metadata locked somehow? is that possible?

@Danne I tried using that Exiftool command, but replacing with "-defaultcropsize" instead, but I probably need something else to -overwrite_original with.. I am so dumb with this stuff.

Yes, but the extra vertical resolution is proportionally higher than its corresponding horizontal resolution. So if you set up a 16x9 Project and you have the full sensor width resolution (1952) you gain extra Vertical wiggle room for stabilization. Something I have been a profound user of with 5D3's 3:2 1920x1280 resolution. When tracking headshots and you want that headline to stay close to the top border, it is an amazing tool for controlling your compositions or for post stabilization.

After playing with different Exiftool GUI's, I think I need to get a command for Exiftool(-k) and somehow remove DefaultCropSize. The GUI ones don't seem to be able to do that, even tried removing all Metadata and that did not remove anything.

I forgot, if you want sample DNG's I will WeTransfer to you in PM.

So I found ExiftoolGUI https://exiftool.org/forum/index.php?topic=2750.0 I actually thought this was ML forum 

But I can't figure out how to use it, maybe I should join that forum..

I know this is ML forum, but you guys normally know stuff about EXIF and Metadata and the BM Forum is really hard to get answers on anything that isn't the newest new new.

I bought the BMPCC (BlackMagic Pocket Cinema Camera) original or first edition what have you, the not-4K one. In package, never used at my local photo store for a good price and it shoots RAW, so I of course had to have it. And I've really been interested in the Super 16 look of lately and B4 Zooms and so on, so its a nice package.

I noticed that when playing the DNG's in MLRawViewer (which somehow works with Compressed DNG's from BM cameras) that the camera actually shoots 1952x1112 and not 1920x1080 as shown in Resolve and other software- Not a big Crop, but none the less a crop on an already heavily cropped camera. The DNG's contain metadata that tell the software, like Resolve to Crop to 1920x1080. See Exif. I don't know why, maybe for easier calculations or just to adhere to a standard, but I see no artifacts with the extra resolution.
I opened a DNG in Rawdigger Trial version and I have no idea what I am doing or if this is the right tool. But got the exif data. What I need help with, is a way to change or remove the crop, preferably on all the DNG's, like Batch uncrop if possibe or Change Metadata of all DNG's on the SD card.

So if someone could point me at the right tool or Command, I would be very happy.

Just some extra info, in my test I found out that the camera LCD shows the cropped 1920x1080 area and not the full 1952x1112 recorded resolution.

---- ExifTool ---- ExifTool Version Number      : 12.36 ---- File ---- File Name                    : super16 raw_1_2022-02-10_1144_C0020_000000.dng Directory                    : I:/super16 raw_1_2022-02-10_1144_C0020 File Size                    : 2020 KiB File Modification Date/Time  : 2022:02:10 10:44:55+00:00 File Access Date/Time        : 2022:02:10 10:44:54+00:00 File Creation Date/Time      : 2022:02:10 10:44:55+00:00 File Permissions             : -rw-rw-rw- File Type                    : DNG File Type Extension          : dng MIME Type                    : image/x-adobe-dng Exif Byte Order              : Big-endian (Motorola, MM) ---- EXIF ---- Subfile Type                 : Full-resolution image Image Width                  : 1952 Image Height                 : 1112 Bits Per Sample              : 12 Compression                  : JPEG Photometric Interpretation   : Color Filter Array Orientation                  : Horizontal (normal) Samples Per Pixel            : 1 Planar Configuration         : Chunky Tile Width                   : 976 Tile Length                  : 1112 Tile Offsets                 : 9216 1084480 Tile Byte Counts             : 1075262 984166 CFA Repeat Pattern Dim       : 2 2 CFA Pattern 2                : 1 2 0 1 TIFF-EP Standard ID          : 0 0 0 1 DNG Version                  : 1.2.0.0 Unique Camera Model          : Blackmagic Pocket Cinema Camera Linearization Table          : (Binary data 20799 bytes, use -b option to extract) Black Level Repeat Dim       : 1 1 Black Level                  : 256 White Level                  : 51080 Default Crop Origin          : 16 16 Default Crop Size            : 1920 1080 Color Matrix 1               : 1.31197 -0.49679 0.01156 -0.41723 1.44237 0.04528 0.06723 0.2171 0.72651 Color Matrix 2               : 1.00885 -0.27351 -0.08258 -0.48997 1.34441 0.11174 -0.06406 0.32997 0.53917 Camera Calibration 1         : 1 0 0 0 1 0 0 0 1 Camera Calibration 2         : 1 0 0 0 1 0 0 0 1 As Shot Neutral              : 0.6306 1 0.7728 Baseline Exposure            : 2.1 Camera Serial Number         : BC5D3219599F4337BFA39329B572099A Calibration Illuminant 1     : Standard Light A Calibration Illuminant 2     : D65 Time Codes                   : 11:44:55.00 Frame Rate                   : 24 ---- Composite ---- CFA Pattern                  : [Green,Blue][Red,Green] Image Size                   : 1952x1112 Megapixels                   : 2.2

Video is private.. i really liked this video and his cover of Wicked Game in this one is the best one I heard.

Anyone remember the name of the artist? Maybe I can find the artist somewhere else?

Thank you.

I try to record 1920x1050 48fps, which keep giving me errors when recording on CF cards. So I've tried to record it directly on SD card.
I've tested SD patch with my SanDisk Extreme PRO 95 MB/s with no result as ML always says my Card is Full, but it isn't.
So I've tested to record without the patch and only succeeded for 70 frames each time.
Is it possible to record longer takes ?
If I buy a 170 MB/s will I have more chances ?
And does a Lexar HC II 300 MB/s makes a difference ?

Thanks for the help...

S/.

No, a higher speed SD card will not help because the SD interface is limited to about 20 MB/s. You getting 70 frames is your buffer filling up and then writing those 70 frames to your sd card, because the sd card has no chance to keep up. If you shoot 24 fps fullHD, you'd typically get around 124-140 frames before recording stops.

Try reducing the resolution slightly.

And only record to CF card.

You should get almost continues, depending on luminance and detail in the scene, mind you the lossless compression will compress less in complex scenes e.g. wide shots with hyperfocal focus and vice versa a 85 mm with only a face in focus and the rest a blur.

Happy shooting!

Ultimate ISO with highest DR is iso 100. The higher the ISO, the less DR it can capture.

Also remember to only shoot in the Analog ISO e.g 100, 200, 400, 800 etc for accurarte exposure control.

The intermediary iso's are digitally pulled from their analog counter parts e.g iso 160 is a digital pull from 200, 320 is pulled from 400. So if you record in 320, you are actually recording in iso 400.