Recent posts

#1

crop_rec and derived builds / Re: 3K/UHD 5D2 Raw development...

Last post by names_are_hard - Yesterday at 09:36:56 PM

Nice info, and good to hear you're still progressing   Doesn't make too much sense to me yet, but I'm sure it will be very useful next time I'm dealing with a CF cam.

#2

crop_rec and derived builds / Re: Crop mood - WYSIWYG Editio...

Last post by Felipe - Yesterday at 06:05:19 PM

First that all I'm impressed of the reliability from this Crop mood, Is just great.
Found 2 little bugs: As we all know the speeds on 650D no big deal, on the 700D not the 650D When in crop mode
and zoom 10x it stays on zoom despite presing the zoom reset, no big deal just open canon menu do nothing and comeback to ML, Over all is a Fantastic build

#3

crop_rec and derived builds / Re: 3K/UHD 5D2 Raw development...

Last post by reddeercity - Yesterday at 04:55:33 AM

I been researching the CF card structure on how it communicates with the controller , is seem that
there a header (just like a Hard Drive) in that header is written configuration files & at what mode
it accesses , (e.g. mode 0-4) these mode are related to write/read speed & timing.
this is the

Code Select Expand

CISTPL_CONFIGConfiguration Tuple is stored in the cf card header and is
determent mostly by the device in this case the 5d2 canon write the table for dryOS uses.

Code Select Expand

pLStorage=0x685504is the reg on the card as seen in the start up log I've posted , & the mode it run at
is in "ns" nano seconds , so in a nut shell that the timing for read/write plus in this mode theses
more then write & read i/o there wait times
here a list what going on

Code Select Expand

t0 -Cycle time (min)
t1 -Address Valid to -IORD/-IOWR setup(min) (Mode3= 180ns Mode4= 120ns)
t2 -IORD/-IOWR (min)(Mode3= 30ns Mode4= 25ns)
t2 -IORD/-IOWR (min) Register (8 bit)(Mode3= 80ns Mode4= 70ns)
t2i -IORD/-IOWR recovery time (min) (Mode3= 80ns Mode4= 70ns)
t3 -IOWR data setup (min) (Mode3= 30ns Mode4= 20ns)
t4 -IOWR data hold (min) (Mode3= 10ns Mode4= 10ns)
t5 -IORD data setup (min) (Mode3= 20ns Mode4= 20ns)
t6 -IORD data hold (min) (Mode3= 5ns Mode4= 5ns)
t6Z -IORD data tristate (max)(Mode3= 30ns Mode4= 30ns)
t7 Address valid to -IOCS16 assertion (max) (Mode3= n/a ns Mode4= n/a ns)
t8 Address valid to -IOCS16 released (max) (Mode3= n/a ns Mode4= n/a ns)
t9 -IORD/-IOWR to address valid hold (Mode3= 10ns Mode4= 10ns)
tRD Read Data Valid to IORDY active (min), if IORDY initially low after tA (Mode3= 0ns Mode4= 0ns)
tA IORDY Setup time (Mode3= 35ns Mode4= 35ns)
tB IORDY Pulse Width (max) (Mode3= 1250ns Mode4= 1250ns)
tC IORDY assertion to release (max)(Mode3= 5ns Mode4= 5ns)
the whole process can not take more then the total "I/O Pulse width" which is 1250ns
This where we/I can alter the timing band width for increased frequency ....... etc. ... more to come this
 
The above mode is for the CF card in "True IDE Mode" the cf card can run in 3 different configurations
 True IDE Mode,PC Card Memory Mode,PC Card I/O Mode(this is from specification 2.0 so there's more then likely the more mode in the newer spec.
So to find the block that has the configuration on the CF card was my next step , so i made a CF card image (like a ISO) and read it in HxD Hex editor , didn't find that block yet but found something interesting , appertainy  there more head timers involved then i thought .
I see 4 in total but we only use 2 so are we missing them ? or do we need them ?
this what i found

Code Select Expand

mv=1 res=0 crop=0 task=? pc=ff986cc4 addr=82d0 HEAD1 timer (start?).c0f0713c:     476 ISO=200 Tv=50 Av=56 lv=1 zoom=5 mv=1 res=0
crop=0 task=LiveViewMgr pc=ff8e1830 addr=8328 HEAD3 timer (ticks?).c0f07134:       4 ISO=200 Tv=50 Av=56 lv=1 zoom=5 mv=1 res=0
crop=0 task=LiveViewMgr pc=ff8e1830 addr=8330 HEAD3 timer (start?).c0f07150:     49c ISO=200 Tv=50 Av=56 lv=1 zoom=5 mv=1 res=0
crop=0 task=LiveViewMgr pc=ff8e1844 addr=8370 HEAD4 timer (ticks?).c0f15084:   10000 ISO=200 Tv=50 Av=56 lv=1 zoom=5 mv=1 res=0Right now we use (this is crop mode)

Code Select Expand

c0f0713c (offset)475
c0f07150 (offset)49c

Code Select Expand

c0f07134
c0f15084are not being modified , could be causing more overhead ? in write speed .
I've seem data from a1ex on 5d2 with 120Mb/s on CF card in a write test in a low level access
so there must be a lot of overhead going on.
There's 2 direction I'm looking at here reduce overhead (turn off unnecessary resources like "DFE face detection (must be part of the auto focus) e.g. and set it to UMDA7 (or over clock the cf bus)
If i can turn off some resources i can get 75-80Mb/s to go to at less 100Mb/s or 120Mb/s that the speed for UDMA 6 , UDMA 7 pushes that to 150Mb/s . The 5D3 is on a exfat which can access larger blocks of data so the 5D2 will never see UDMA 7 speeds without overclocking , fat32 will not allowed access speed in exfat file structure . Now that being said the theoretically fat32 is limited to 133Mb/s so 120Mb/s should be reachable

More to come ............    
https://engineering.purdue.edu/ece477/Archive/2004/Spring/S04-Grp07/documentation/cfspc2_0_compact_flash.pdf
My sources of information

#4

Camera-specific Development / Re: Canon 80D

Last post by papajo - Yesterday at 03:17:05 AM

First of all thank you for your response also I am sorry if  I seemed abrupt or for some things that didn't get through as I thought, it is because I am not a native English speaker.

Who said that?

I can't remember his handle cause this discussion was months ago or at least a few weeks but I think he avatar had a joker face (from some cartoon version of the Batman series) and posts a lot or at least he did wen I went to discord.

There are no intentions. Digic 6 is just hard to get working due to its unique design. It is just easier in later models running Digic 7 and 8.
Remember this is just a hobby project of a few people. We work on it when we feel like it, and work on what we want. I have a pile of 10+ Canon cameras and tbh I favour EOS R as it was my re-entry into Canon ecosystem - and also my entry into Magic Lantern / camera hacking world.

Yes I understand that and I am not entitled or something it's just that since I saw your posts I got my hopes up but after a year I didn't see any other progress+ the discord "confirmation" I got for it never being released that made me ask you in person since maybe that guy's reply might have been just his opinion

When I used the word "intentions" I meant if that guy from discord was right saying that you quit the efford or if you feel like it would be plausible for you to get back at it some time.

Thanks also for mentioning that the digic 6 is has a unique design that hinders the porting sounds interesting and I will research more on that.

Also I respect your stance about wanting to focus more on R series and obviously I don't want to give you directions or anything with what I'm about to say but I just want to share my opinion which is that mirrorless cameras getting updated more frequently now and substantially because they are the new tech...
But DSLR cams don't get the same firmware attention and also have a lot more "juice" to squize out of them cause (given the capabilities added "post mortem" for cameras as old as e.g the 50D) their features plausibly were undercut by canon so that they not "eat up" sales from the more expensive models in the same line.

So in that sense getting magic lantern for older models will produce more "bang for the buck" where "bang" is the gap given by increased capabilities compared to stock firmware and "buck" the time an engineer gives to port magic lantern to it.

Again just my piece of mind I don't try to imply or assert something.

Then you are wrong - right now they exist just two "builds" of Magic Lantern for newer models: one for EOS M50 - which does nothing except card benchmark. And one for 200d which also doesn't have almost any features - it was released as a proof of concept that project is still alive.

I think you should get familiar with Current state of Magic Lantern project. This will answer many of your questions.

I meant the magic lantern version was ready in less time (since a camera's release counting up to when it got a magic lantern version ready for it ) I didn't specifically mention "camera models newer than 80d"

If it seemed like that I'm sorry as I said I'm not a native English speaker and I usually post to forums a little bit before going to bed 

Thanks again for taking the time to respond 

P.S @mods would it possible for me not to have to paste that 3 line text security question along with the handle etc cause I have to log out because somehow if I log in with one browser in my tablet and check to "keep me logged in" I am some how logged in any other browser I have too and the same goes for logging off...

Now for example I was writing my reply in chrome and opened Firefox (where I never logged into your forum from there before ) and I was already logged in, I logged out in order to select the account creation option and copy the huge text "I am no spammer etc etc ..."

And that lead to me not being able to post on chrome cause it logged me off from there too and I had to rewrite the entire reply on my tablet with my thumbs which was mentally and physically exhausting thanks 👍

#5

crop_rec and derived builds / Re: Danne's crop_rec_4k, 5DIII

Last post by fanfzero - May 01, 2024, 04:18:27 PM

A video of the band Crypta I shot with the 5DIII with this build,anamorphic mode. Topaz video A.I noe has a very useful tool to fix slightly out of focus videos, which is a great help because on low light it's pretty hard to get good and fast autofocus. The only drawback with this video is that I got some vertical banding, more noticeable on bigger screens, can I fix that? I tried turning pattern noise on with mlv app and then exporting to dng, but it looked exactly the same

#6

Camera-specific Development / Re: Canon 80D

Last post by Walter Schulz - April 30, 2024, 10:25:17 PM

Who said that?

Well, if taken literally: You. https://discord.com/channels/671072748985909258/844581352082898975/1206757404230942721

Let's taken it for granted papajo is not accustomed dealing with questions to engineers/programmers and mind set embedded in their answers. ;-)

#7

Camera-specific Development / Re: Canon 80D

Last post by kitor - April 30, 2024, 10:11:42 PM

So I went to discord and asked about it and they told me that there never will be a 80D version of magic lantern

Who said that?

Could you please update us of your intentions about the 80D firmware ?

There are no intentions. Digic 6 is just hard to get working due to its unique design. It is just easier in later models running Digic 7 and 8.
Remember this is just a hobby project of a few people. We work on it when we feel like it, and work on what we want. I have a pile of 10+ Canon cameras and tbh I favour EOS R as it was my re-entry into Canon ecosystem - and also my entry into Magic Lantern / camera hacking world.

I think quite a few models got magic lantern a lot sooner than 80D

Then you are wrong - right now they exist just two "builds" of Magic Lantern for newer models: one for EOS M50 - which does nothing except card benchmark. And one for 200d which also doesn't have almost any features - it was released as a proof of concept that project is still alive.

I think you should get familiar with Current state of Magic Lantern project. This will answer many of your questions.

#8

Share Your Videos / Re: 5D3 5.7k Anamorphic, 16mm ...

Last post by PaulHarwood856 - April 29, 2024, 02:49:08 AM

Awesome video! Where can I find the 16mm Grain Overlay?

#9

Share Your Videos / Re: Eclipse 5d iii 4k raw vide...

Last post by PaulHarwood856 - April 29, 2024, 02:44:51 AM

Very nice!

#10

Camera-specific Development / Re: Canon 80D

Last post by papajo - April 28, 2024, 08:22:05 PM

After a quick test I have a bad stub or two (tasks view doesn't display names properly[1], in LV our menu closes almost instantly[2]), other than that seems on par with 750D.
That was a quick (< 3 hour) job after i learned how to use Ghidra Version Tracking, thanks to @reyalp.

Ok, it took a week prior to that as I took the opportunity to create a proper loader script for Ghidra that should improve ghidra project quality a lot. More on that later.

E:
[1] Turns out one of task related structs is different.
[2] Fixed, wrong Canon dialog used in background.

Hi Kitor I bought a Canon 80D back when it was newly released and anxiously waited for years for a magic lantern version for my camera the years passed by and nothing but I am still using my 80D

And apparently so are other people too

When I first saw your posts about trying out the firmware on the 80D I was happy like as if I was a child on Christmas 

But a year has passed and no new posts on the subject from you or any other dev

So I went to discord and asked about it and they told me that there never will be a 80D version of magic lantern

And I wonder if this is true or if you just don't had the time to finish your work but plan to eventually

Could you please update us of your intentions about the 80D firmware ?

Also is the 80D for some reason (if so which ? ) hard to "crack" and put magic lantern on it? I am asking because I think quite a few models got magic lantern a lot sooner than 80D
And 80D is a really good camera for both amateurs and even professionals (aside it not being FF ) so I can't see why it's so much neglected..