Messages

define useful, if you are just starting coding then it can be very useful in general... in other words, for noobs like me it can be useful, for experienced devs it can't really tell them anything new... at least for now, probably..

CCTV lens?The idea itself is a laughable

well I actually saw VERY good photos made with c mount lenses, there are some awesome lenses, very fast like 1.2 and you will never guess that the photo was made with c-mount.. I don't really like small sensors though (or small sensor area) but you can actually get very very very good results using c-mount.. Of course there is a lot of different lenses in this category and most of them are probably very crappy. But there are some vintage Japanese lenses that can give you very expensive look with lots of bokeh and character.

Finally, one may like the distortion given by some lenses.

Exactly  I always turn off lens correction

Basically with 1x3 modes you have a lot of resolution, and you can actually make your lens corrections in post, it should look better than canon h.264 with correction made on the fly.. I never tried, but it should be so, because you have more resolution and more processing power with better algorithms (you can use adobe camera raw for example, on DNGs)

It is probably not Motion Cam's bug, because I can take raw pictures with usual built-in camera app by modifying one string in one system file, allowing raw photos, by default they are off. And if I do it, photos look exactly the same with channels swapped so it is the phone itself

Thank you so much again for solving this problem, I can now use this old phone as a little almost magic lantern device in my pocket hehe
It even has crop mode with much bigger resolution than standard 1080p mov recording, "card spanning" to write to the internal storage and SD at the same time, but unfortunately no lossless compression or SD card overclock
So similar in concepts

Awesome! Thank you I did not expected this to be just some tag issue

And by the way what is the purpose of specifying IFD0 before the tag name?

I tried changing CFA Pattern 2 and it works, CFA Pattern also could be changed but the image will still look wrong at least in photoshop. And for CFA Plane Color it gives me an error
Warning: Sorry, CFAPlaneColor is not writable


So editing CFA Pattern 2 seems to be the right option, and after reading exiftool manual I decided to do this:

Code Select Expand

exiftool -IFD0:CFAPattern2="0 1 1 2" -ext dng -r -overwrite_original -progress -pause *path-to-directory*

In case somebody is interested what these options do:
-ext dng is just for safety, process only dng's
-r means recursive so all sub-directories will be processed
-overwrite_original - no backup file copies will be saved
-progress - show how many files left while processing, just for fun
-pause - if I want to execute the command from a shortcut or something, the window will be open at the end.


@ names_are_hard thank you so much!
You guys are awesome, it proves again that ML forum is a really good place when it comes to specific technical knowledge

Nice videos, I remember seeing 2010 shootout maybe about 10 years ago somewhere on YT... but I also remember extreme low light comparison and other things that I can't find on this Zacuto channel now...
Anyway it is very interesting to see this now after all this time

Thanks for the article! There is no proper raws from this phone, they are always like this

I edited config and unlocked raw photo option for standard camera app and they look the same too, switched channels..
Jpegs and usual videos are fine though. I think it is supposed to work this way, just some Chinese engineering

So I looked at histograms and separate channels, and my theory seems to be right, both green channels are almost identical while red and blue appears to be swapped.

Now I only need to find a way to re-write DNGs with correct pixel information..

Hi guys this is not ML related question but I know that people here have a lot of deep specific knowledge about dng format and raw data.

I used android phone to shoot some raw videos (it is possible with Motion Cam app).
And from this app you can export everything to dng sequence and edit in any program you like.

The problem is for some reason raw images from my phone look like they have red and blue channels swapped..

And I can change channels in post-processing, but I'm afraid the whole raw conversion before it will happen with wrong data. For example stuff like white balance will be processed who knows how..


If you know how I can process DNGs to swap red and blue channels before importing them, it would be awesome. If there is no easy solution to this problem, I can code with C/C++ but I am not really experienced with it, wrote stuff for AVR and ARM mostly just for fun.. If you push me in right direction (DNG processing) and it is not too complicated maybe I can figure it out..

I included one dng frame as an example (7 mb), maybe it is not r/b channels problem?

https://filetransfer.io/data-package/z7ss4jYf#link


This is what I see when just open it in photoshop



And this is after some tweaks after I swap blue and red channels

There was a video somewhere on the forum, with 1:1 crop mode on eos m, using h.264 and it was 1080p, so it works but only on some cameras.

And about filters - as far as I can tell by watching old YouTube videos, at least VAF filters for 5D2 were quite popular...

EDIT: If you have some time to spend to dive into history (😄 some ten years ago) I can try to link older videos

That would be great

I really like all your videos, very pleasant colors, cinematic movements and nice depth of field

I still think something could be done at the post-processing stage, like reconstruction to full 5k image while smoothing aliasing here, guess additional pixel values based on something, maybe using gaussian function or other algorithms..
And only then feed this properly reconstructed image to the raw converter.

Edit: I've been reading some old posts and it seems like ML is using the reading modes already available in Canon's firmware. So unless there is some magic register combination to enable this, I guess this is sadly not possible u_u

I think it can be done but there will be some limitations.. For example it is possible to read the whole sensor at low FPS, so it should be possible to do it but just skip (not record) every two pixels, saving half of the card space.. So if 10/12 bit recording is possible, it is just lsb truncated? Maybe not recording some pixels also could be done.. But the fps will be limited to the sensor speed probably. Which still can be a good option for recording things such as calm scenes, timelapses and so on. Because full 5k recording takes A LOT of card space..

p.s. I don't really know how it all works so maybe I am saying some total nonsense 

Sometimes you have no time to do 100% correct ETTR especially if there are some very bright light sources in the frame, and sometimes there are just some deep shadows which will benefit from extreme shadow recovery.. So in real world scenarios at least 12 bits won't hurt. That's just my opinion

By the way as you can see even in these examples if you push the shadows you will get mostly a red noise.
You can desaturate only dark reds and only in deep shadows, which will help. And then use your favorite noise reduction with less aggressive settings

By the way if you compare these two images you will notice that MLV App version has some kind of yellow tint over the image, at certain areas it is more visible.. While LR does not have this issue. It is always present in the mlv raw footage opened with MLV App. So I usually start tweaking white balance to add blue but that will break other colors and the whole balance.. I can fix it to some degree with LUTs but sometimes it is just so hard to do it, especially if you want warm image but without this unpleasant color..

So guys (and Ilia) if you will have some free time, could you look at MLV App color science and maybe tweak some things here and there? This is probably the number one issue I always have with MLV App, this yellow cast..

If you look past "wow the noise is gone" you'll notice it looks like smeary computer shit.

I know, but other examples look better.. For example here:



Why not, after all...

I am more interested in removing aliasing but can't find a photo where it is noticeable  and could be open in this program

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

This is a software that can do extreme denoising of RAW images with some new cool algorithms and so on.

And I also saw in some youtube video that it can also remove aliasing, which is a huge deal for users of Magic Lantern But I can't find this video again for some reason, and no information about this option unfortunately.

So this software takes RAW images, do processing and you can save them as RAW again. Which is perfect for MLV App workflow, I thought of converting MLV to DNG, do processing and convert DNGs back into MLV to proceed as usual with MLV App...


But at least version 2 of PureRAW can't process DNG files extracted from MLVs... I searched the internet and it was suggested that it can be because of the wrong metadata,
for example here is the method of changing two fields (make and model)
https://tutodxo.com/en/exifs-modification/

I tried this but in my case it was not enough... So any thoughts?

I hope he is alright, his channel gained so many views in the last year but he stopped uploading.. I was worried that something might have happened

  the demo looks so real

If you want to know how to color correct mlv raw files to match other cameras, you may look at what photoshop does with it's camera profiles..
For example, if you convert mlv to dng and open it in photoshop, it will look almost the same (or the same) as usual cr2 file from the camera.

So it is obviously the same raw data. I don't know what adobe software does with color, but they have profiles for all cameras somewhere in folders, you can find there your canon camera profile. Maybe this profile can be converted to some LUT or something somehow...

it is good to have some experience with regular .mov files before moving to RAW, because then you will understand and appreciate the quality of RAW

by the way if you use iso 1600 and bring down the exposure in post by -1, you will probably get less noise than what you have with iso 800.. of course it means less dynamic range (maybe clipped highlights) in exchange for less noise.

So guys why don't you release 14.1 beta with these new dual iso corrections? It won't hurt anyone It's been a long time since the last release..

Hi! very nice video are you using an anamorphic adapter on some shots?

In audio if you sum two tracks with the same content (have 2x amount of data), you will get only 1,414 better signal to noise ratio.
Digital image is probably the same thing..


Colors could be different because of the chromatic aberrations.. Some vintage lenses have a lot of them even in the middle of the frame (with wide open aperture) and on crop-sensor it will be more noticeable. And it can slightly affect colors of bright objects. 
On the other hand, if you have clean center but a lot of aberrations closer to edges then crop sensor will provide cleaner picture and maybe slightly different color again.

And if you compare full-frame sensor and very tiny sensor like some phones or web cameras, then things like diffraction limited aperture can become visible. And usually DLA is considered limiting sharpness, but it also affects color even before the sharpness, at least I can see it usually...

@Grognard it is because with full frame mode you are using pixel binning (for example 1:3 mode) where the information from three pixels averaged in one, so less noise.

In this mode you are actually using all the pixels, but some of them are averaged on hardware level. But you are still using the whole sensor area.
So we are collecting more light if you think about it.
I don't know if it's really two stops better though.

It is true, at least in my experience full frame video looks better even if it is compressed by youtube to such crappy quality as 240p or 360. I can notice it sometimes... I don't know exactly how, but details are more defined and all things are separated and clearly visible.
And if you look at the video from camera with very small sensor (phone for example) everything will just blur to some colorful mess.

The difference is small and sometimes not as visible, but I think it exists. It is just a matter of perception. And I don't want to argue about it, there is no point.. I can see it and for me it is enough.


And also with FF camera you have more options for vintage lenses. With crop sensor you almost always need wide-angle lenses which are less common.


I could be wrong of course, maybe I am just imagining stuff.. it is not really scientific or anything