Menu

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.

Show posts Menu

Messages - angelsl

#1
Archived porting threads / Re: Canon 70D
December 05, 2014, 05:13:48 PM
Quote from: ShootMeAlready on December 05, 2014, 03:05:09 PM
It feels like Stripes, where we have to complete basic training ourselves.  That's a joke.
So without any offense to A1EX or G, who have done great work and spent long hours on the common code base which we presently enjoy,
lets enlist a guide on the .fir build process.   I think most want a ML drop under the xmas tree to play with over the holidays ... and things only get busier as the fat man's date night approaches, so lets organize the troups.

Inspiration here's two 700D raw videos, which if shot on the 70D, we hope could have been even better (not that he didn't do a great job).
http://vimeo.com/111512507
and
https://www.youtube.com/watch?v=clcVjGrqBr4


The hard part isn't figuring out the .fir structure, really. In fact it's already documented on the ML wiki. The thing is finding the encryption keys. Those will likely never be published publically.
#2
Archived porting threads / Re: Canon 70D
December 05, 2014, 05:16:24 AM
Quote from: DigitalVeil on December 04, 2014, 09:11:16 PM
Is Alex the only person here capable of making a .fir?  I mean, it's almost seemed like he's been oddly against even the idea of a 70D port from the beginning for some strange reason. Doesn't make sense, but his early comments seemed to give off that vibe.  I think he's also kind of drifted away from working on ML as a whole lately, like he was fed up with it or something.

He's not the only one, but not everyone can. .fir files are AES-encrypted (and signed somehow IIRC?) and although the keys for some older models are available online, as far as I know those for the more recent cameras are not. But the .fir format is documented, you just need to find the AES key somehow, if you want to create a .fir.

I'm sure he will create an installer .fir once ML becomes usable on 70D. The code for that already exists.
#3
Quote from: tjrobinson on November 08, 2014, 10:51:30 PM
My phone (Samsung Note II) can record in slow motion at 1/8 speed so in theory that's 240fps. I'm not sure whether it's actually capable of recording individual frames at 240fps though - there's probably some fakery going on as it is just a "toy" compared to proper cameras.

That video you had was about 30 minutes at 29.97 fps, so if the real duration was 15 minutes then seems like it only recorded at 59.94 fps? Unless you sped up the footage when editing.

Anyhow, I'll be around if there's any way I can help. I can't seem to subscribe to this topic though.. (or any topic in the Using ML section).
#4
I wrote a little utility to deblink it programmatically, using ffmpeg to convert your video to frames and then detecting the LED blinks from there.

Here is the result. 8519 (8480 actual data) bits read from 53391 frames.

      init:ff071ffc:00:01: [PM] DisablePowerSave (Counter = 1)
      init:ff0122e4:8b:16:
K287 ICU Firmware Version 1.1.1 ( 3.3.7 )
      init:ff0122f8:8b:05:
ICU Release DateTime 2012.05.14 13:18:25
      init:ff02b744:00:03: [SEQ] CreateSequencer (Startup, Num = 6)
      init:ff02b994:00:02: [SEQ] NotifyComplete (Startup, Flag = 0x10000)
      init:ff02b9f8:00:03: [SEQ] NotifyComplete (Cur = 0, 0x10000, Flag = 0x10000)
   Startup:ff02b664:00:05: [SEQ] seqEventDispatch (Startup, 0)
   Startup:ff012624:8b:05: startupEntry
   Startup:ff1b9340:81:03: Initialize Adjective & Situation
   Startup:ff0125e4:8b:05: startupPropAdminMain : End
   Startup:ff02b994:00:02: [SEQ] NotifyComplete (Startup, Flag = 0x20000000)
   Startup:ff02b9f8:00:03: [SEQ] NotifyComplete (Cur = 1, 0x20000002, Flag = 0x20000000)
   Startup:ff071ffc:00:01: [PM] DisablePowerSave (Counter = 2)
   Startup:ff07206c:00:01: [PM] EnablePowerSave (Counter = 1)
**INT-50h*:ff071ffc: 0:01: [PM] DisablePowerSave (Counter = 2)
**INT-50h*:ff07206c:00:01: [PM] EnablePowerSave (Counter = 1)


The code I wrote, as well as the deblink result is here. There is a missing zero bit at index 0x647 that I added when converting to ASCII to get the result above. The corrected result is also there.

#5
Archived porting threads / Re: Canon 70D
November 05, 2014, 05:45:13 AM
Quote from: nikfreak on November 03, 2014, 05:43:23 PM
Nothing new besides that all is running fine in qemu. Waiting for nanomad to return. I would do the job but i have no options to buy a 70d atm.

Would you consider pushing your changes somewhere so others can collaborate? (i.e. Hg)

Thanks.