Canon 1100D / T3

Started by a1ex, June 14, 2012, 04:50:54 PM

Previous topic - Next topic

0 Members and 2 Guests are viewing this topic.

greg_kennedy

Thanks!  I actually solved it myself by following your steps above - but did it using just one card and EOSCard to disable bootable when going 1.0.5-ml -> 1.0.6.  (Camera crashed when trying to use a Bootable card without a valid autoexec.bin on filesystem)

Next question for @a1ex: I can't find "Show GUI Events" on the Debug menu, otherwise I'd tell you the Q code for 1.0.6.

a1ex

Right, I've disabled a bunch of features to squeeze RAM, including FEATURE_SHOW_GUI_EVENTS.

Here's a test build for 1.0.6 with this feature enabled: https://builds.magiclantern.fm/jenkins/job/1100D.106-test/

dfort

Cool. Good to know my firmware updates are good for something.

Been a while since I worked on it and never noticed the comment about the 600D. Suppose it also applies to the 1100D?

diff -r 9025834982de platform/1100D.106/features.h
--- a/platform/1100D.106/features.h Fri May 04 17:38:44 2018 -0700
+++ b/platform/1100D.106/features.h Mon Nov 26 13:56:02 2018 +0100
@@ -23,6 +23,5 @@
// disabled, because autoexec.bin gets to big and 600D does not boot
#undef FEATURE_SHOW_TASKS
#undef FEATURE_SHOW_CPU_USAGE
-#undef FEATURE_SHOW_GUI_EVENTS
#undef FEATURE_SHOW_EDMAC_INFO
#undef FEATURE_FLEXINFO

a1ex

Quote from: dfort on November 27, 2018, 04:36:42 AM
Cool. Good to know my firmware updates are good for something.

Yeah, looking forward to the holiday season, to... catch up with ML developments :D

Quote from: dfort on November 27, 2018, 04:36:42 AM
Been a while since I worked on it and never noticed the comment about the 600D. Suppose it also applies to the 1100D?

From model_list.c in QEMU source:


    {
        .name                   = "600D",
        .ram_size               = 0x10000000,   /* 256MB */
        ...
    },
    {
        .name                   = "1100D",
        .ram_size               = 0x08000000,   /* 128MB */
        ...
    },


so the issue is much worse on 1100D.

However, out of all DIGIC 2 and newer models, the crown goes to 1000D (64 MB). Even the old 400D appears to have 128 MB.




Edit: apparently the sensor in 1100D might be faster than expected:

Quote from: a1ex on November 28, 2018, 09:12:22 PM
- 1100D might have 128 MPix/s (32 MHz x 4 channels, but default video readout apparently uses 2? I really need to double-check that)

That would be just as fast as 700D & co., if this hypothesis is valid. That is, faster than 600D & co.

Photo mode readout configuration: timer A = 1474, B = 2876, clock = 32 MHz => 7.55 fps at full resolution.

The camera is advertised for 3 frames per second, right? There are 4 pixels read out for each timer A increment, i.e. 4 channels read out at once. There is some overhead too, that's why timer A * 4 is greater than horizontal resolution.

Video readout configuration, from raw_res.txt:
720p25: A = 1000, B = 1280, readout size 1496 x 967 (this includes black borders)
720p30: A = 960, B = 1112, same readout size
Timer A can be pushed to 872 in both modes.

What's interesting: for each timer A increment, only 2 pixels appear to be read out. In other words, the sensor might throttled in LiveView. No other DIGIC <= 5 camera does that, to my knowledge, so I'd like to find out how it works. Will prepare some low-level tests.




Edit Jan 1: false alarm. The 1100D definitely uses 4 channels for LiveView readout. Daniel Rozsnyo took one of these apart and showed me the analog signal from one of these 4 channels in LiveView:



Reducing that overhead might be doable (likely one of the ADTG registers); doing so might enable higher frame rates, up to about some theoretical 80 FPS at 1428x804 (i.e. full-width 16:9) !!!

Quote from: a1ex on January 01, 2019, 10:03:21 AM
1100D, on the other hand, is an interesting beast:

It runs at 32 MHz x 4 channels (i.e. pixel clock is the same 700D & co.), but for some reason, it has a huge overhead. In regular (24/25/30p) movie mode, C0F06084/88 is set to 0x200c3/0x3c903af, i.e. xmax = 1886 (likely rounded to 1888), out of which 390 pixels are cropped from the left side. ML still has to crop 68 pixels of left OB; that gives 1428 active horizontal pixels, 458 (!) for OB width and 2 pixels for rounding (guess); these require "only" 14.75 μs/line. The unexplained overhead would be 12.5 μs/line, or exactly 400 clock ticks. This one is worth fine-tuning, if you ask me.

Why?
- 720p24/30: 960 / 32 = 30 μs/line
- 720p25: 1000 / 32 = 31.25 μs/line
- FPS override: 872 / 32 = 27.25 μs/line
- theoretical value: (872 - 400) / 32 = 14.75 μs/line! (without altering OB areas)

For a 16:9 frame, which would be just 1428x804, it would require only 11.86 ms!

Assuming one can somehow drop 400 pixels from the left OB, that would free another 100 clock ticks, i.e. 11.63 μs/line, or 9.35 ms for a 16:9 LiveView frame.

aplinhares

Quote from: a1ex on November 26, 2018, 01:56:18 PM
Right, I've disabled a bunch of features to squeeze RAM, including FEATURE_SHOW_GUI_EVENTS.

Here's a test build for 1.0.6 with this feature enabled: https://builds.magiclantern.fm/jenkins/job/1100D.106-test/
What features where disable?

Good to know that there is still develop in this mod, thanks!

DeafEyeJedi

Alright fellas... Been wanting to get myself into this as I've finally borrowed one from work. Definitely feels like an interesting beast needless to say @a1ex!

Compiled from @Danne's branch (crop_rec_4k_mlv_snd_isogain_1x3_presets) and seems I got it to installed just fine (turned off cam and back on) then there goes this pattern of three long intermediate flashes with three additional long flashes 'n vice versa from the orange blinking LED just above the play button on this body.



LiveView does not appear anything. It's pitched black. Battery/Card pull gets you out of it. Any hints? Am I better off upgrading this to 1.0.6 from 1.0.5?   :o
5D3.113 | 5D3.123 | EOSM.203 | 7D.203 | 70D.112 | 100D.101 | EOSM2.* | 50D.109

dfort

Surprising you got that far. The 1100D is a Digic 4 LV State camera and isn't supported in the crop_rec branches. Try the raw_video_10bit_12bit_LVState branch if you want bleeding edge on this camera.

aplinhares

hey there.
Latest night build is magiclantern-Nightly.2018Nov26.1100D106 ?
Why when try to update it, says that expects firmware 1.05?

dfort

What is it that you are looking for? If you click on that link a1ex gave you it points to a build that was done from my repository. Here's that link again:

https://builds.magiclantern.fm/jenkins/job/1100D.106-test/

What a1ex did was to delete the line that blocked SHOW_GUI_EVENTS.

Magic Lantern Nightly.2018Nov26.1100D106
Camera   : 1100D
Firmware : 106
Changeset: 9025834982de+ (lua_fix_1100D.106) tip
Built on : 2018-11-26 12:56:02 by jenkins@nightly

diff -r 9025834982de platform/1100D.106/features.h
--- a/platform/1100D.106/features.h Fri May 04 17:38:44 2018 -0700
+++ b/platform/1100D.106/features.h Mon Nov 26 13:56:02 2018 +0100
@@ -23,6 +23,5 @@
// disabled, because autoexec.bin gets to big and 600D does not boot
#undef FEATURE_SHOW_TASKS
#undef FEATURE_SHOW_CPU_USAGE
-#undef FEATURE_SHOW_GUI_EVENTS
#undef FEATURE_SHOW_EDMAC_INFO
#undef FEATURE_FLEXINFO


Are you saying that this isn't working on 1.0.6? I guess I could update it with the latest lua_fix changes but unless you're testing the 1.0.6 port you should probably be using either the "stable" nightly build or something from the experiments downloads page.

Farangi

Hi,

So something strange has happened to my footage. For some reason some of the videos have been recorded without the sound, which I thought was going to be awkward to match up with my external sound recording but not the end of the world. Thing is though, when I load the footage into premiere with my two clips of seperately recorded external sound, and match everything up with the clap I make at the begining of each shot, the two sound files match up and the but the video quickly finds itself out of synch! Really don't understand what could have happened! I've tried fucking about with the audio and video and using other anchor points to match them up but they always end up out of synch again. Anyone got any ideas what's happened?

I was using my 1100D with whatever the latest version of ML was in february - april this year...

thanks

EDIT 3.35pm: I've just checked another bit of footage that was taken the same day with no change in the settings but this time the camera's own audio was recorded also but even that is out of synch with the video! I just don't understand how this is possible and if I can fix it.

Mike2000

hello, my problem is about 1100D Canon RAW feature, I installed the last experimental ML 10/12-bit RAW video version (2019 Mar 24). I expected something like that: https://www.youtube.com/watch?v=F_zLhgMvpOo

But everytime I record any video, it looks so bad like a super zoom. It doesn't matter if I choose different ratio or resolution the crop/zoom effect is still there. So did I install the wrong version or..?

Thank you for your time anyway.

Walter Schulz

Without details about settings, workflow any answer is right, wrong, irrelevant.

Mike2000

Quote from: Walter Schulz on November 24, 2019, 01:48:00 AM
Without details about settings, workflow any answer is right, wrong, irrelevant.

Hello, I'm using the 2:35:1 ratio, resolution: 1280x326, 14 bit. 25 fps, shutter speed 1/50, RAW.
I'm using the EFS 18-55mm III. When I select the 1280x326 resolution it also says "stretch by 1.67x to get the full 1280x544 resolution in post". When I convert the mlv files the video doesn't look squeezed as it should be. It's just a perfect look video in 1280x326, it's like a crop in 1280x326 more than a squeezed version of the 1280x544. That's why the video looks wrong when I stretch the height by 1.67x. I saw many tutorials online and their videos looked squeezed (vertically only) so they can apply the stretch by 1.67x in post, anyway my footage is just already perfect regarding the ratio but the resolution is totally wrong. I hope it makes sense, thank you for your time!

Walter Schulz

No workflow info for post. Try again.
Which modules in use?

Mike2000

Quote from: Walter Schulz on November 24, 2019, 01:53:07 PM
No workflow info for post. Try again.

I used MLV app, default settings, no stretch applied, exported in Prores4444. Then I tried the MLV Converter, default settings, exported in DNG. I use after effects but it doesn't matter because the problem is not in the comp settings, it's probably in some step before the post process in after effects. With these two Apps I get the same results: a perfect 1280x326 footage where there's no need to stretch the height. I don't undestand why. Thanks.

a1ex

If I understand well, the 1100D operates in "720p" mode by default, but using a 3x3 pixel binning (with line skipping). All other models use 5x3 binning in this mode, so their videos need to be stretched, but this doesn't apply to 1100D. The generic code assumes 5x3 binning in 720p for all models, so it has to be added as an exception. It needs to be corrected here:

https://bitbucket.org/hudson/magic-lantern/src/d318f774b24ecc7d533ab79dd9418d097442fd81/src/raw.c#lines-905

PR welcome, but I may not be able to look into it until holidays.

Mike2000

Quote from: a1ex on November 24, 2019, 02:13:09 PM
If I understand well, the 1100D operates in "720p" mode by default, but using a 3x3 pixel binning (with line skipping). All other models use 5x3 binning in this mode, so their videos need to be stretched, but this doesn't apply to 1100D. The generic code assumes 5x3 binning in 720p for all models, so it has to be added as an exception. It needs to be corrected here:

https://bitbucket.org/hudson/magic-lantern/src/d318f774b24ecc7d533ab79dd9418d097442fd81/src/raw.c#lines-905

PR welcome, but I may not be able to look into it until holidays.

Yes the 1100D operates in 720p, but I didn't touch anything regarding binning or other settings, plus in many 1100D videos they didn't talk about pixel binning, they just wrote in description the same settings I wrote in the previous post. Thanks again!

a1ex

And you did not touch the source code either, which was what I was talking about ;)

Quote from: a1ex on January 29, 2018, 11:03:50 AM
There is an experimental raw video build, but other than a few snapshots from Danne, I have no idea how it works in practice => please report back.

Apparently you were the first person trying to use raw video on 1100D :)

Why? If anyone else would have tried this before, they would have noticed this issue, as it's too obvious. Since they didn't... QED.

FYI, I don't have this camera, so I wasn't aware of the issue.

Mike2000

Quote from: a1ex on November 24, 2019, 02:28:05 PM
And you did not touch the source code either, which was what I was talking about ;)

Apparently you were the first person trying to use raw video on 1100D :)

Why? If anyone else would have tried this before, they would have noticed this issue, as it's too obvious. Since they didn't... QED.

FYI, I don't have this camera, so I wasn't aware of the issue.

Hello, thanks!

I just paste one of the links I found on YouTube:



Maybe they just crop the footage, I tried to avoid the problem in this way:
I want to get 2:66:1 ratio, 1280x481.
But I record in "16:9" with a 960x324. Then I make a new composition in after effects using the 1280x481 resolution and I just change the scale till the height fits the composition, obviously I cut the edges a bit, but since I'm using 2:66:1 instead of 2:35:1 it's not a big deal. Not sure if it's wrong but it works, and the ratio is correct.

Josde

Hey, I have a 1100D available to test whatever if whatever is needed. I'll try to see if RAW recording works later these holidays and update with results.

By the way, thanks for all the effort put in by the ML team, you guys are amazing  ;)

rmp

Hello everyone,

I own a 1100D and have been using it as a beginner tool for the raw video workflow.

There are two main ways you can get it to record short clips or continuous raw video in the 16:9 -> 2.xx:1 aspect ratios.

The first one, my current way of using the camera, is to shoot in 4:3 and 1.2:1 aspect ratios then avoid stretching in post since you already have 2.22:1 and 2:1 videos. In this mode, you can use the ML live view overlay with all it's active features you selected from the menus ( histogram, waveform, focus peaking, zebras, etc ). This works only for composition. As soon as you press record, the overlay is gone untill the clip stops. I recommend using AF Live; this will allow you to back-button autofocus or zoom to focus, and not mess up the overlay when you exit zoom.

By not cropping and using this workaround, you can shoot:
3:2 - 2.49:1 actual a/r
4:3 - 2.22:1
1.2 - 2:1
1.175 - 1.95:1 ( new smartphone standard )
1:1 - 1.66:1 ( taller than 1.77:1 then corresponds to 16:9)

Here is what you can expect with a fast sd card ( Sandisk ExtremePro 95 Mb/s in my case )

25p

1.95:1 1408x720 10bit - 5 Sec 6 frames
           1408x720 12bit - 3 Sec 4 frames
           1408x720 14bit - 2 Sec

2:1 1408x704 10bit - 5 Sec 17 frames
       1408x704 12bit - 3 Sec 6 frames
       1408x704 14bit - 2 Sec 3 frames

2.22:1 1408x634 10bit - 8 Sec 7 frames
           1408x634 12bit - 4 Sec 11 frames
           1408x634 14bit - 3 Sec 2 frames

25p Continuous: 1248x562 10bit 2.22:1 ( I tested up to 12 min - 20.9 MB/s required )


24p

1.95:1 1408x720 10bit - 6 Sec 2 frames
           1408x720 12bit - 3 Sec 13 frames
           1408x720 14bit - 2 Sec 7 frames

2:1 1408x704 10bit - 6 Sec 8 frames
        1408x704 12bit - 3 Sec 15 frames
        1408x704 14bit - 2 Sec 8 frames

2.22:1 1408x634 10bit - 10 Sec 5 frames
           1408x634 12bit - 5 Sec
           1408x634 14bit - 3 Sec 9 frames

24p Continuous: 1280x576 10bit 2.22:1 ( untested - 21.0 MB/s required )


The second way to shoot the actual aspect ratio that you want, but the one that is not really reliable if you need to record clip after clip ( like a paid job ), goes something like this:

- set the autofocus to (-: AF ( not AF Live ) and the lens to AF - this is very important
- go into the settings and turn off 5x zoom from the zoom tweaks ( in my testing, 5x zoom results in artefacts on live view )
- select all your raw preferences ( bit depth, resolution, fps )

now, you should have a cropped live view image with that weird resolution ( lets say 1408x476 - the max 16:9 available ), but still retain overlays

- press display untill you get the ML overlay ( combo it with Av for the ML menu if it doesn't show up at first )
- while in live view and the ML overlay, press the zoom button once and the overlays should disappear, giving a clear full display ( you can only do your horizontal framing, since you miss out on the remaining vertical part of the frame covered by the black crop )
- press Av to go back to the ML menu, and you should see that it says 1408x792 or any full aspect ratio resolution that you have selected and you can start recording

This method is prone to fail after recording 1-2 clips, and you have to repeat the zoom-procedure to get back to full a/r recording, as the software switches back to the cropped resolution and overlays.


As a reference, you get about 7 seconds worth of video in 1280x720p 10bit 25p


Well, I hope I got everything right; I hope someone finds this useful and let me know if I can help with any other info regarding the 1100D. I ain't no expert, but I'll try to help.

Cheers

lane

Hello all,

I recently decided to do some live streaming for a project. I have this old Rebel T3 that's been tucked away in a bag for years. I was wondering if there was any added benefit to using ML on it for my purposes? There seems to be a number of features it unlocks including RAW video capture but as I'll be indoors, with the camera using the HDMI output to a capture card, is there any value I would unlock using this firmware?

Walter Schulz

For starters: Unlimited streaming duration via HDMI if using lua_fix experimental build.

lane

That alone is worth me giving it a shot.

I'll be playing with it later today. Thank you for the feedback!

snopeep

Quote
Quote from: lane on September 03, 2020, 11:03:39 PM
That alone is worth me giving it a shot.

I'll be playing with it later today. Thank you for the feedback!


Lane, I was wondering if you had any luck? I'm in the same boat. Have a Rebel T3, hoping to use with EOS Webcam Utility but that 30 minute mirror timeout isn't going to let it happen. If ML's experimental build can make it possible, I'd love to find out!