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 - coutts

Pages: [1] 2 3 ... 11
1
Archived porting threads / Re: [UNMAINTAINED] Canon 100D / SL1
« on: May 29, 2014, 09:35:47 PM »
Great work, sorry for not replying I've been busy with school and I just graduated and got a job so I am busy with that all day now.

Good to see you got this far. My advice to you is choose an existing port that is most similar to the SL1 (hardware wise) and use that as your base.

I prefer to keep the 5d3 as the lead port when I worked on ML so I copied all coding styles from that, I suggest the same.

Good job here

2
Feature Requests / Re: Inter-modules framework or code samples?
« on: September 27, 2013, 03:58:19 AM »
Hm good idea.

Sent from my Nexus 7

3
Archived porting threads / Re: Canon 100D / SL1
« on: September 24, 2013, 04:39:18 PM »
Hi guys - sorry there's been no development on this, I'm busy with my final two semesters of school so I've been devoting my time to studies :)

I promise to work on this in the near future - again I apologize for the delay in updates.

4
I like it. could probably be integrated with main website too since I kept the <div> tag layout pretty structured / easy to implement.

:D looks great!

5
Great news!

6
Reverse Engineering / Re: ADTG and CMOS registers
« on: August 14, 2013, 02:51:44 PM »
How do I find these values ​​for the 500D?
Code: [Select]
ADTG_WRITE_FUNC
CMOS_WRITE_FUNC
CMOS16_WRITE_FUNC
CARTRIDGE_WRITE_FUNC
you have ida right or arm console for firmware analysis

7
stubs are done, needs consts checked and probably lots of other little things updated.


some notes from when I found these couple months ago:
Quote

5D3 v1.2.1 change notes:
- Much code added: about 60kb worth (~15,000 lines of ASM).
- Some added very early in ROM, early enough to cause shift in cstart's location (I don't recall that ever happening in new firmware updates from other cameras).
- InitializeBitmapDisplayDevice has changed drastically, quite a bit of code missing (24 lines of ASM removed).
- Every stub changed.

http://pastebin.com/sMjiN7Ei

8
Raw Video / Re: Raw video on 5DMK2
« on: July 19, 2013, 09:24:03 PM »
Here's a raw video I filmed with my Canon 5D Mark II:
I filmed this two weeks ago while I was on a holiday in Kenya. This was my first time filming raw, read about it 2 days before I left.
My first time really working with Magic lantern as well.

- I feel like youtube isn't doing the video justice, most parts are so much better quality on my computer...
would love to see a download link for this.

9
Camera-specific discussion / Re: ML for the C300
« on: July 16, 2013, 04:22:07 PM »
falls outside of the scope of ML:
http://www.magiclantern.fm/about

10
Archived porting threads / Re: Canon 100D / SL1
« on: July 16, 2013, 05:09:09 AM »
I'm just waiting for my copy of ida pro and I can get to work on this, have my new computer finally - so now I have a dev environment again

11
Afaik it's advised to just add PROP_HANDLERS in modules when needed - but can I predict in which order they are executed, for example the core PROP_HANDLERS before the modules?

In my current case I'd like to add a PROP_HANDLER(PROP_ROLLING_PITCHING_LEVEL) to auto-switch the af points from portrait to landscape and vice versa by reading the "struct rolling_pitching level_data" that is initialized in the core PROP_HANDLER.
Think of a prop handler as inert until its property changes, then it fires (runs).

Sounds like you just need a simple if statement in that prop handler, so when pitching level changes, check if it's over some threshold to detect moved to vertical/horizontal, and if it's over that threshold, call your function to switch AF points and update some status variable so you know the current state (vertical or horizontal).

This sounds like a feature already implemented by Canon in the 6D (and 5d3 probably too).

12
General Development Discussion / Re: 4k Filming
« on: June 25, 2013, 10:19:51 PM »
Oooops, Sorry.
I totally understand now. Thanks for explaining - I didn´t do my math...
So ML is taking the full readout of the sensor (?) and applies some pixel binning to reduce the data?
Or are lines/pixels skipped on the 5D3?

Thanks again for clarifying and now I´m sorry for the confusion I didn´t want to create!


canon does all of the pixel binning / line skipping and outputs an image to a buffer, updated at the framerate of live view (24fps, for example). all we do is save the image at the buffer 24 times a second to the card to make the video. the image is 14-bit raw data.

13
https://bitbucket.org/hudson/magic-lantern/commits/e01856b86df6

Confirming the other comments on the commit from 'Gregory O'Connor', can't compile ML on OS X anymore due to missing `truncate` command.

Anybody figure out a work-around? I went macports last time I re-installed OS X (not brew) and it's kind of a big project to install brew (more work than practical just to install one thing).

14
General Chat / Re: Kickstarter Campaign
« on: June 11, 2013, 09:31:11 PM »
I believe some of krashnik's suggestions can benefit a lot of people, not just himself. I'm open to hear more ideas :) let's not shut down somebody just because he has radical ideas (change is good).

15
Archived porting threads / Re: Canon 100D / SL1
« on: June 11, 2013, 08:28:28 PM »
I have the 100d now, seems they've updated LV focusing speeds as it's quite fast now compared to how the EOS M was. I think it has the changes that are gonna be applied to the M with the firmware update coming at the end of this month.

16
Camera-specific discussion / Re: Canon 40D
« on: May 27, 2013, 04:28:03 PM »
http://www.eoshd.com/content/10507/it-lives-5-year-old-350-canon-50d-becomes-raw-cinema-monster

Wow......will this happen on 40D ?
I found the required function stubs for it, so in theory it should work if somebody is still working on this port ;)

17
Reverse Engineering / Re: AFMA 500D
« on: May 27, 2013, 03:23:32 PM »
The 500d like the other cameras with no microadjustments, is missing the property back end code with PropMgr for this. The property is inert and won't change anything. I don't think it will be possible.

18
Feature Requests / Re: Password protection ?
« on: May 27, 2013, 05:29:40 AM »
If you block gui task then no buttons can be used, so should keep camera locked until you enter some kind of password.

19
General Development Discussion / Re: 12-bit (and 10-bit) RAW video
« on: May 23, 2013, 04:15:33 PM »
I messed with that function... but was trying for H264.. I wonder if it cuts bits out of the "debug" raw we're using.
at first test with 5d2, the location is empty (0), maybe i need to call lv_save_raw first.

20
General Development Discussion / Re: 12-bit (and 10-bit) RAW video
« on: May 23, 2013, 04:02:33 PM »
Just curious, does Canon hard code 14bit raw processing? Is it possible to change bitdepth in some native way to change the RAW AD converter to do 12bit or even 10 bit? I know on Nikon D600 you can choose between 14bit or 12bit. Wonder if that can be easier?

Thank you for the great work.

There's a factory function named "FA_SetCRawBitNum", located at 0xFF47C0D8 in the 6D.113, seems to just store a number at 0x82734 . It can be called via the Call function, maybe this will work?
Code: [Select]
call( "FA_SetCRawBitNum", 10 );

21
Found required edmac stubs in 40d:
https://bitbucket.org/hudson/magic-lantern/commits/cf080443d8ffcbf3cfc21c06aa3bb95d2e341ca9

I don't think TCC or Modules work yet with the 40d so someone will have to port raw_rec.c into the main code, but looks possible (alex says it has lv_save_raw too). Amazing that even a 6 year old VxWorks camera possesses the ability to shoot raw video.

22
General Development Discussion / Raw Burst on 40D
« on: May 22, 2013, 02:45:38 PM »
At first glance it appears it will be possible. So, it appears even vxworks will do it :)

23
Raw Video / Re: Raw Burst on the 50D
« on: May 22, 2013, 02:36:12 PM »
The 40D has lv_save_raw inside, so it's likely to work.
Cool - I'll get to work finding the edmac stubs now.

24
Raw Video / Re: Raw Burst on the 50D
« on: May 21, 2013, 09:24:25 PM »
It looks like raw_rec hasn't yet been ported, only silent pic bursts?
I pushed the stubs for the 50d yesterday, someone try it out

25
Raw Video / Re: Raw Burst on the 50D
« on: May 20, 2013, 09:04:25 PM »
The sensor is read at a specific size from what I understand. A1ex mentioned earlier in this thread that the 50d is 1592x1062 in 1x mode and 1992x1080 in crop mode so 1080p should be doable in crop mode only. The 1x mode will need to be upscaled.

I think this is probably on par with the 5d MkII for write speed but as the files will be smaller it might get a little extra push in the fps dept etc but not much.

It has the same processors as the 5d MkII and likely the same CF interface. A fast UDMA 7 card should let this run at full transfer speed in the same way as a UHS-I does for SD to it's maximum but we'll see.

Not sure about the moire being any less.

It would be great if this had 720p H.264 enabled some time as a fallback. I've seen some of the 50d footage at 24fps 1080p (H.264). Not too bad. I think the 600d has the edge though slightly + audio which the 50d hasn't got ... not that any of this is relevant now  ::)
From my testing with the 5d2 it can only do 1880x840 so the 50d should cap out somewhere around this as well (slow CF interface).

Pages: [1] 2 3 ... 11