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

Pages: [1] 2 3 ... 72
I'd suggest this as a fix for the main branch of Switch but I don't know if the '-s' argument works in non-OSX versions of 'find'.

You know you could submit a pull request in Bitbucket so anyone who wants to test out your suggestions can easily do so and give feedback. Though knowing Danne he is probably already trying out the '-s' flag.

Share Your Videos / Re: VFXish Experimental music Video - 60D 10 Bit RAW
« on: September 17, 2017, 11:40:21 PM »
Ha ha, some of those effects are subtle. Must be fun to watch this stoned. Not that I would know  ;)

It would be great to get lossless compressed on this camera. You can get longer recording times and/or larger frame sizes with lossless compressed than you can with just fewer bits.

Camera-specific discussion / Re: ML on EOS-M2
« on: September 17, 2017, 08:21:39 AM »
@bookemdano -- are you able to use Mercurial (command line or through a GUI like SourceTree) and compile ML? That would be the best way to test, once the camera boot flag is enabled of course. So while we're waiting for that, take the time to set up a testing/development environment. It isn't that hard. I've got a few tutorials on how to get something up quickly on Mac or Windows. If you're on Linux you don't need a tutorial.

Camera-specific discussion / Re: Canon 700D / T5i
« on: September 15, 2017, 07:27:45 AM »
Ok--looks like a1ex cleaned up things when he merged my pull request. All tests passed on the Stubs API Test. Yay!

Inherited an issue from 114, can't save lossless compressed full resolution silent pictures so there's still work to be done.

Camera-specific discussion / Re: Canon 700D / T5i
« on: September 15, 2017, 01:25:21 AM »
@eNnvi - no need for any special build, the selftest module is included in the unified branch. The 1.1.5 pull request was merged recently so we should all update our Canon firmware in order to work with the latest nightly build.

Camera-specific discussion / Re: Canon 700D / T5i
« on: September 14, 2017, 04:44:44 AM »
Need to verify this with another 700D user -- turn on selftest module and try running the Stubs API test. Is it able to complete the test and save a log?

I was trying to run it on the 700D.115 update like I did several months ago but it kept getting stuck. Downgraded to 114 with the same results.

General Development Discussion / Re: How to run Magic Lantern into QEMU?!...
« on: September 14, 2017, 02:14:09 AM »
Hey, I'm happy!

700D.115 running in QEMU:

General Help Q&A / Re: Canon T5i (700D) Firmware 1.1.5
« on: September 14, 2017, 12:29:23 AM »
Spent the day doing stress tests and found no differences in performance or issues between the 700D.115 and 700D.114. CPU usage is the same so there shouldn't be any added battery drain. I also got it working with the crop_rec_4k branch and it behaves the same--hint, notice that there isn't a build for the 700D.114 in the Experiments download page?

So without further ado, here's a 700D.115 pull request for the crop_rec_4k branch:

Note my prior post about crashing with lossless compressed mlv_lite recording but if you like living on the bleeding edge... I recorded a 5 minute clip using 12bit lossless and all was fine until I started waving the camera around like crazy. Yeah, it crashed but the clip was saved and no frames were lost--it even continued recording after the crash!

One more issue worth noting is that it won't save lossless compressed full resolution silent pictures.

I should emphasis that these issues also apply to 700D.114.

General Help Q&A / Re: Canon T5i (700D) Firmware 1.1.5
« on: September 13, 2017, 08:52:09 PM »
So the problem turned out to be more a matter of not making sure all the modules were updated from 700D.114 to 700D.115. I got this working as well as the current 1.1.4 builds which means that unified is pretty much stable and the experimental branches need some more work but it doesn't have anything to do with the Canon firmware update. I'll do some more testing to see if battery drain and other reported issues are reproducible.

One scary moment came when the camera crashed when recording 9-bit lossless and did a core dump.

Code: [Select]
[100] raw_rec_task: NULL PTR (80c3e100,e1a00000)
pc=    c288 lr=    c288 stack=1ac1d8+0x1000
e1a00000 e59ff014 e59ff014 e59ff014
e59ff014 e1a00000 e59ff010 e59ff010

Magic Lantern version : Nightly.2017Sep13.700D115
Mercurial changeset   : 65aede073360+ (crop_rec_4k_700D_115)
Built on 2017-09-13 18:24:04 UTC by [email protected]
Free Memory  : 126K + 2505K

General Help Q&A / Re: Canon T5i (700D) Firmware 1.1.5
« on: September 12, 2017, 06:52:21 AM »
Oops--not working so great. Turns out that I had a bad stub. Somehow the is_taskid_valid stub changed and it wreaked havoc with Full resolution  silent picture. Uploaded a new test build.

Still having problems after merging crop_rec_4k. Need some time to look into it.

Code: [Select]
at mlv_lite.c:753 (measure_compression_ratio), task shoot_task
lv:1 mode:3

shoot_task stack: 1c5cf8 [1c5e20-1c3e20]
0x000CCF58 @ ac67c:1c5dc0
0xUNKNOWN  @ ccfb0:1c5da8
0x00AB5540 @ ab8dfc:1c5d38
0x0007F620 @ ab5738:1c5d28
0x0007EF68 @ 7f680:1c5cf8

Magic Lantern version : Nightly.2017Sep11.700D115
Mercurial changeset   : 45b5dd1a852e+93e177a2b6e9+ (crop_rec_4k_700D_115) tip
Built on 2017-09-12 04:42:03 UTC by [email protected]
Free Memory  : 126K + 2523K

Feature Requests / Re: Assign lens focal length and name for non cpu lenses
« on: September 11, 2017, 01:54:59 AM »
What's the best way to make a build that combines the crop_rec_4k experiment with the manual lens info branch?


I did that a while ago and it seems to work fine. Seeing your message I thought I'd update it. There were some conflicts that I'm pretty sure I resolved properly. The branch is here:

It would be nice to add manual_lens_info to crop_rec_4k sort of like how raw_video_10bit_12bit was merged into crop_rec_4k. Only a few cameras are working with crop_rec_4k so those other branches are not going away any time soon.

As far as posting to the experiments page, I believe only a developer can do that. Of course if you can compile ML you can post your own test builds. Hint.

General Help Q&A / Re: Canon T5i (700D) Firmware 1.1.5
« on: September 10, 2017, 11:56:06 PM »
I hoped to play with a 700D for a week or two...

I'd be glad to send you my 700D to play for as long as you want.

Revisited the 700D.115 pull request, updated with the latest unified changes and confirmed that it is working great. However, I tried merging the crop_rec_4k branch and none of the good stuff works. No crop_rec, lossless compression, etc. It even freezes up without any modules active. Ugh!

Camera-specific discussion / Re: ML on EOS-M2
« on: September 10, 2017, 09:54:23 PM »
I'm not rushing--just feeling that I lost the momentum.

Last night I built a new QEMU testing environment with all the latest changes and that's when I discovered that wasn't building in my EOSM2 branch. Digging deeper I found the same problem existed on all the other cameras. Now that I'm a little more familiar with the ML code thanks to this porting project, I was able to submit a fix instead of just submit a bug report.

Of course I'd like to get the camera boot flag turned on and start playing around with ML on this camera but that's the little kid in me wanting to play with his toy.

General Chat / Re: Magic Lantern Book will be released this autumn?
« on: September 08, 2017, 03:17:08 AM »
If you click on the link in that first post you'll get:

Oh ...
Die von Ihnen aufgerufene Seite
existiert leider nicht.

Sounds more dramatic in German but basically, don't hold your breath for the book much less for 10% of the profit.

Camera-specific discussion / Re: ML on EOS-M2
« on: September 08, 2017, 02:57:36 AM »

Don't want to be a pest but the EOSM2 port is feeling a little jealous lately. Any hint on what the next step should be? Maybe turn on the boot flag?

@Teamsleepkid - you probably have Preview set to Real-time. Try the default, Auto. Yeah, it probably looks crappy but it isn't dark!

Tried proxy filming as well but files came out corrupted and early stop etc...

Flashback to when mv1080 (via H.264 proxy) was almost working on the EOSM:

Just tried it and it looks like an Adobe dynamic link bug to me. Adobe Camera Raw opens before After Effects which is probably expected with a DNG image sequence but then only the first frame shows up in the composition even though it seems to indicate that all the frames were imported.

My point is that it's propably useless to have proxys with MLV_Lite right now since there is no time code or a consistent way to get them in sync for post production.

Have you tried using Danne's switch? It trims the H.264 proxy to the same length as the DNG image sequence along with matching timecode. (Danne also replied while I was still writing this post but he didn't mention his awesome program.)

Forgot to mention - 700D and EOS M will need an extra constant (easy to find).

The SRM_BUFFER_SIZE for the EOSM and 700D were pretty easy to find. An interesting difference between these cameras was that on the EOSM the SRM_BUFFER_SIZE wasn't visible until I pressed record or took a silent still while on the 700D it was available as soon as the camera booted up. Maybe this is related to the EOSM not getting into mv1080 mode until it is recording H.264?

Raw Video / Re: Can't Record RAW Footage longer than 3 seconds on 700D/T5i
« on: September 05, 2017, 03:46:49 AM »
...even though my camera shoots in 1080p. My highest is 1728x972

When shooting full frame mode that's your highest resolution. The reason that you can record 1920x1080 H.264 is because the image is being uprezed by the Canon hardware. Like Walter said, you can shoot higher resolution using one of the crop modes, though you won't be using the full height and width of your sensor.

Your best bet for recording MLV with this camera is to download the 4K raw video recording; lossless compression from the experiments download page.

700D and EOS M will need an extra constant (easy to find).


Feature Requests / Re: Assign lens focal length and name for non cpu lenses
« on: September 02, 2017, 03:16:02 AM »
A while back we discussed the possibility of adding an optional block that could take more than 32 characters, actually 31 characters terminated by a null (0).

Note the truncated name (...ZF.2)

Code: [Select]
Block: LENS
  Offset: 0x00000164
    Size: 96
    Time: 0.806000 ms
     Name:        'Zeiss Makro-Planar T* 2/100 ZF.'
     Serial:      ''
     Focal Len:   100 mm
     Focus Dist:  0 mm
     Aperture:    f/2.00
     IS Mode:     0
     AF Mode:     3
     Lens ID:     0x00000000
     Flags:       0x00000000

Any progress on that yet?

Camera-specific discussion / Re: Canon EOS M
« on: August 29, 2017, 01:52:20 PM »
Ah yes, the shutter-bug. A few weeks ago I thought that maybe if we can come up with a different way of booting up the camera, like the AllocateMemory pool method, it would solve this issue. Sadly it didn't resolve the shutter-bug. The best work around I have found is to use a SanDisk Extreme PRO card that is 32GB or less.

Anything over 32GB (SDXC cards) will most likely exhibit the bug. Other cards 32GB or less may work, some intermittently. Note that it doesn't have to do with the speed of the card because I've got an old and very slow Kodak 1GB card that works fine.

The shutter-bug is only present with EF-M zoom lenses. A quick, though annoying, "fix" is to break the lens/body by twisting the lens off and on while the camera is turned on. This kills the shutter-bug until the next time you restart the camera. There are other work arounds but if you use this card you'll never have to deal with it.

There is no ML-SETUP.FIR for the 5D3.134 so unless you already had ML installed with the camera boot flag set, you won't be able to install ML onto your camera without downgrading the Canon firmware.

So, i want to downgrade my firmware, but pc see the camera but eos utility not. Why it's the question, but I don't have any answer for this.

Your pc can "see" the camera but EOS Utility cannot? So that means that your USB connection is working. What might be happening is that you have an older version of EOS Utility that isn't compatible with the 1.3.4 firmware. You can get the latest version from the Canon website.

I really need it for my work.

Please understand that ML is more of a hobby project and that the 1.3.4 port still has some issues and not yet part of the main code base. I'd think twice before betting my job on it.

Nice find @Licaon_Kter -- so does that mean we can have a choice of the latest mlv_lite developments or the legacy mlv_rec with mlv_snd in the same build? I want it!

However -- not all is rainbows and unicorns in EOSM and 700D land.

The 700D saved a crash log and made a core dump when recording 10-bit lossless:

Code: [Select]
[2] raw_rec_task: NULL PTR (80c3e100,e1a00000)
pc=    c288 lr=    c288 stack=1abdd0+0x1000
e1a00000 e59ff014 e59ff014 e59ff014
e59ff014 e1a00000 e59ff010 e59ff010

Magic Lantern version : crop_rec_4k.2017Aug26.700D114
Mercurial changeset   : cffeb4898221 (crop_rec_4k) tip
Built on 2017-08-26 21:27:15 UTC by [email protected]
Free Memory  : 128K + 2524K

The EOSM didn't save a core dump but created this assert log when recording 10-bit lossless with H.264 Proxy (the only way to get mv1080 on the M):

Code: [Select]
slots[slot_index].size < max_frame_size
at mlv_lite.c:3344 (raw_video_rec_task), task raw_rec_task
lv:1 mode:3

raw_rec_task stack: 1ded20 [1dede0-1ddde0]
0x0009EBBC @ ab9178:1ded50
0x0009E548 @ 9ec1c:1ded20

Magic Lantern version : crop_rec_4k.2017Aug26.EOSM202
Mercurial changeset   : cffeb4898221 (crop_rec_4k) tip
Built on 2017-08-26 21:27:48 UTC by [email protected]
Free Memory  : 148K + 2722K

Logs and core dump uploaded to dropbox.

Pages: [1] 2 3 ... 72