Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.

Messages - Skinny

Pages: 1 2 [3] 4 5 ... 8
So the dark frame was recorded in different conditions, after some time? Sensor temperature can make a lot of difference in the noise and patterns.. dark frame should be shot as close as possible to the original conditions. And not only things like themperature, but even battery charge will probably affect some noise patterns. But I don't believe the aperture will make any difference...

Raw Video / Re: Why is my footage so terrible and noisy??
« on: May 31, 2022, 10:36:35 AM »
I think it will be more helpful if you share just 1 frame of the original MLV file, in mlv format (raw). you can exprot just one frame with MLV App. Because it is hard to say anything with already processed footage, especially uploaded to youtube...

M50 is very popular camera now, it is a good choice :)

(I'm also biased) so I'll say something full-frame :D because full frame camera with raw recording is awesome.

I know many people have dreamed about ML on 5D4 for years.
while 5D3 is very developed with latest achievements..
5D2 lack many features possible now for other cameras (doesn't have 1x3 modes working, no lossless compression, no 16x9 mode for 48 fps.. correct realtime preview, CF overclock.. all these things are possible but not implemented yet. for example there is an instruction how to activate 1x3 and it works, but it takes 20mins to do so with registers manipulation)
6D probably can also benefit from some further development
6D2 - people ask all the time.

In general, older cameras are very attractive to many people because of their low price. And stable and good builds for them can stimulate second-hand market which in turns leads to more users with fresh cameras and potentially new developers who can work on new and more expensive cameras also.
Strong support for legacy cameras means loyal community and more sales for new cameras, this is how it works. I think Canon should publish all source code for their products older than 10 years or so, it will bring them new loyal customers for sure. Over the time, of course. But big companies don't think like that obviously..

I suggest someone to record few MLV clips in different resolutions/modes and upload them somewhere.
And if we want to use one MLV file as "standard" for testing, it means it will be downloaded many times. And especially by the people who are new to ML, they just want to see how it looks, how it can be color graded and so on. So it's important to use something that will show ML RAW from the best side.. I think it should be:

1. Something really beautiful and not just test clips with some random stuff
2. It should look nice with default MLV App settings
3. Probably shot with 5D3 because it is the best ML raw camera for now
4. Shot using steadycam or tripod, no shaky footage obviously
5. 1920x1080 resolution because most people want at least true 1920 and at the same time file size won't be too big.
6. Filesize? ~2gb or more?

Just my thoughts.

It would be cool to see a set of results across a lot of different systems.
I like this idea, we need to find some nice short MLV so anyone can benchmark and share the result.. And later it can be used to measure how certain processing algorithms behave on different systems.

@names_are_hard perfect :)

What could be really cool - if one day someone could make proper working in-camera ML help for all fresh builds. I remember first time into ML menu I thought "wow! how many things.. And we have built-in help here, how convenient..." but.. it wasn't there :D  Although now it seems like something absolutely insignificant, for newbies it can make a hude difference.

In this case, the installation instructions seem to lack the details of an important step.
I don't argue with anything you say, of course the instructions and wiki needs an update. There just aren't enough people with deep ML knowledge and free time to edit the wiki.
But.... I just don't quite understand how a very experienced developer can't google such a simple thing when there is even a joke that coding is the ability to google professionally :)
Maybe this is the correct behavior for open source projects, asking developers directly about any little thing.

I just want to say that most likely - everything that you write (or I write) will not have any effect, because people just behave as they behave. And have rights to do so, since the freedom of speech.

About developers -- well.. does ML need them or not?
They are needed, of course. On the other hand, developers who will be offended by everything, most likely, will not stay on the project for long.

By the way, if you watch any YT video with installation process and scroll to comments... You will see that even when there is such a detailed video instruction, people still have a lot of problems. And they ask all sorts of questions, so it's almost impossible to cover everything in any wiki or manual. This requires a forum, but here each user is approved manually (or now it's not the case?)
I think OP didn't answer just because he already forgot about ML forum when his account got approved.

I went to the wiki just to see how this part of the instruction is written.

Step 2. Installation

  • Format the card in the camera (low-level format).
  • Unzip all of the files from Magic Lantern zip archive to the root of your card.
  • Launch the Firmware Update process and follow the messages on the screen.
  • Once you see the green confirmation screen, restart your camera. Done.
  • If anything goes wrong, check the Troubleshooting section.

so... it specifically says: Launch the firmware update. maybe something like "from your camera menu" should be added... although it seems obvious.
It also doesn't say that after copying files to the card, you need to insert it into the camera :D

In the future, to help the project, I want to make YouTube videos explaining common misunderstandings about ML, and other instructional videos. Of course, this will require a little consultation with developers. But so far, my skill is not enough for quality content, and I don't want to make lame videos. I know that I can do it and thus make a small contribution to the project. So more people will know, more people will be interested... For example, Zeek did a great job popularizing ML.

And if someone is ready to spend their time improving the wiki, then they should do it, why not..

What really puzzles me is why people ask this types of questions on forum? So then they wait for 3 days before someone will answer or what if no one will answer at all.. when you can just google and watch any first youtube video with installation process and clearly see the "fw update" step there.

I think sometimes it just happens. Sometimes even a very smart person can stuck on something that even 5-years old can figure out in 5 seconds. I had that moments too and then when you realise it - big facepalm :)

But these days I see more and more questions on forums that can be googled in less than a minute. Sometimes even the first result is the answer. And it is a global tendention all over the internet. Why? I don't know. People have changed..

About attitude - well.. do you need that thing on your camera or not? If yes, then what difference does it make if somebody is not really that "nice" as you imagined he would be.. The question was answered anyway, so it's up to you now.

When you say "ML community should do this, and shouldn't do that" - I don't think somebody will actually listen. Because there is no "team" or something, or company, or corporate ethics. It's just people. Individuals. So someone may listen and someone may not.

When I was registering here, I was waiting for.... maybe a week, and account has not been approved. So I had to contact someone and ask directly. I think this is why we don't see many people here. And almost no new developers then.

It's an interesting idea, but I don't really understand why do you need that 5%. Just compose your shots keeping in mind that stabilize will crop just a little... is it really making any difference? and 5% is a lot, usually when I use warp stabilizer if it goes more than 101-102% zoom then the footage is probably too shaky to be used, you will see rolling shutter artefacts and motion blur where it shouldn't be... and significant quality loss because of zooming in.
Anyway sometimes after stabilizing it requires only 100.5% zoom but sometimes as high as 102-103% and you can not really predict it. So what exact margin do you need then, if it's different all the time?

And... when you really inspect your footage you will find that most camera shakes happens is in vertical direction. So (in theory) you can increase your vertical resolution, for example to 1920x1200 when you need only 1080. Then after stabilization turn off automatic zoom and crop it manually but only watching when left and right sides looks ok, and up and down sides will be with black borders flying around, just crop it to 1080. This should significantly reduce zooming-in, maybe at least two times.
I never tried it though because Premiere doesn't like when you use clips with different aspect ratios, so you need to nest everything and I'm too lazy honestly :)

But the more I use digital stabilisation, the more I want to buy a steadicam. ::) I just always see rolling shutter or motion blur artefacts. And overall less quality image after digital crop-zoom.

General Chat / Re: How did you guys know about Magic Lantern?
« on: May 03, 2022, 02:50:11 PM »
When I bought second-hand 550D and found mentions of ML somewhere on some forums, my friend also used CHDK on his old point and shoot camera so the whole concept wasn't new to me...

But the real RAW video passion and all that came from youtube. I saw a clip which was shot on 50D in raw, it was some sort of amateur short film, just a few scenes actually, but I was stunned by the image. It was so cinematic and absolutely not like typical digital video. All colors and the whole "feel" was completely different from what we all used to see on youtube. So I immediately forgot about 4k and all marketing crap :D It was ~5 years ago, or maybe more.

Is this area exist on the captured footage also? 48 fps preset uses less height so you have part of the screen frozen, it is ok..

Modules will work with builds from the first page:
you need to download this ML build from december:

then, download new
and place it into "modules"

then download new
and also place it into modules

and finally download
and add it too.

All those links are from the first post.
This way you'll get all latest features.. Except the 5k build, which can only be used separately.

how to enable 48 fps with realtime preview:
It could be somewhat tricky... try first start in 3.5k with 5x zoom, make sure everything is ok. then switch to crop-mode "off" (and 5x zoom still active), make sure the preview is working, and then select 48fps. If you still don't get preview, switch again to "off" with 5x zoom, and then back to 48.. try it couple of times, it should work.. maybe it could be done easier, I don't know.

And make sure selected type of preview is "auto"

why don't you put this info in your signature, so more people could see? I mean like link to this post and a brief description

Camera-specific Development / Re: Canon 50D
« on: April 22, 2022, 03:32:03 PM »
All I want is good 1080 p image with great canon  colors. I am in love with colors of 50 d
If you want to use full sensor area, this camera is limited to 1568 pixels wide which is not exactly full-hd 1920... Of course if you are not using crop mode.. and in crop mode you will be using VERY tiny sensor area, so you need really wide angle lenses.
I think this is very limiting. And CF card can be more expensive than the camera itself :)

And colors.. I don't think you get "Canon" colors in mlv raw, it's all in your hands though. Raw is terrible when you first open it in MLV App for example, but it is RAW so you can do any corrections and basically make colors look exactly as you want.
Is mlv's from 50D looks really better than from EOS M for example? Maybe you just like particular color grading from someone, and not the camera colors itself?

could you post samples from the same clip? because on last two you have background in focus, while on first it is not..

General Development / Re: LiveView hacks (write speed improvement)
« on: April 20, 2022, 02:49:59 PM »
less noise and a cleaner image in the darks compared to the EOS-M
It could be better power filtration, different dc/dc converters and all analog stuff around the sensor and a/d conversion. EOS-M is so compact they could sacrifice some performance in order to fit everything in that tiny form-factor..

For example, in audio world two different audio interfaces with identical chips inside can have different characteristics. And it is mainly because of a difference in power, shielding and all that stuff. Basically, analog stuff around the digital chip.

Reverse Engineering / Re: SD investigation on DIGIC 4
« on: April 18, 2022, 06:50:03 AM »
ok, it was fun experience :) no result doesn't mean no progress, now we know something.

by the way,
because I am applying them when 0xC0400008 = 0x363110f
I just remembered, with previous builds when applying the patch with "print values" activated I can see 1363110f for a very short time, in the moment when patch applies or may be right after it. So  maybe it is the problem if you are waiting for 363110f

Reverse Engineering / Re: SD investigation on DIGIC 4
« on: April 17, 2022, 05:41:14 PM »
can't apply, first time does nothing and second time camera freezes with card red light on, so I have to pull the battery. Doesn't matter in photo mode or in live view, or video... second time is always freeze

Reverse Engineering / Re: SD investigation on DIGIC 4
« on: April 17, 2022, 03:14:39 PM »
ok.... something strange happens. three possible ways:

so initial value is 3000003
then I apply the patch, now it is 18003
benchmark? unrealistic numbers same as with 0 instead of 3,
4970 etc
I reboot the camera, "shutdown not clean and so on", reboot again
select "2" apply the patch - the value is 2010003 now

second scenario:

I reboot the camera,
apply the patch first - the value is 18003,
select "2", apply the patch again - the value is 10003
benchmark - same unrealistic results,
but the value now switched back to 18003.......

the same thing if I select "1", value switches back to 18003.

third scenario - I don't reboot the camera after the first test,
then "2" - 10003,
benchmark - unrealistic speeds 4800, 4900, without 93.
check value? 10003. so value holds.

and everything the same with "1", 8003 holds.

Reverse Engineering / Re: SD investigation on DIGIC 4
« on: April 17, 2022, 01:51:10 PM »
I think it didn't work..

so, initial value was 3000003 of course.
after the patch - 3018003
benchmark  - usual default speeds, and after benchmark new value still holds
"set C0400004 to 2" - 3010003
benchmark  - usual full speed again, the value 3010003 as it should
"set C0400004 to 1" - 3008003
benchmark - everything the same again, value 3008003

So no half speed or anything.. maybe it will work without 3's?

Reverse Engineering / Re: SD investigation on DIGIC 4
« on: April 17, 2022, 01:27:45 PM »
cool, but the link is broken

I downloaded it anyway, using the old link address with new file :)

Reverse Engineering / Re: SD investigation on DIGIC 4
« on: April 16, 2022, 08:04:19 PM »
I can only confirm the same result, red led on and it's not responding. It was very interesting anyway, thank you for trying to achieve something for such old cameras. I have to go too :)

Reverse Engineering / Re: SD investigation on DIGIC 4
« on: April 16, 2022, 07:47:17 PM »
the same, first time camera rebooted by itself with "camera was not shut down cleanly", second/third time it got frozen so I need to pull the battery.

Reverse Engineering / Re: SD investigation on DIGIC 4
« on: April 16, 2022, 06:01:40 PM »
Could you try enabling "Print values" while running card benchmarks, 0xC0400008 should be 0x1363110F all/most of time, can you confirm this?
confirmed! stays 1363110f

it switches back to 363110f between the writes/reads, and it's back to 363110f after the test is finished.

Reverse Engineering / Re: SD investigation on DIGIC 4
« on: April 16, 2022, 05:56:00 PM »
Get a decent cardreader. See cardreader test list at for starters.
About SDR (sorry about the typo) and DDR:
Sure, it is good to have a decent cardreader. Maybe when times will become better.. For now, I already have 3 indecent cardreaders :) So I guess I'll stick with them for now.. Thanks for links.

Pages: 1 2 [3] 4 5 ... 8