Canon 70D

Started by nikfreak, January 15, 2015, 12:22:15 AM

Previous topic - Next topic

0 Members and 4 Guests are viewing this topic.

andy kh

I also tried dford's build. When i preview with raw2cdng , all i can see is noise
5D Mark III - 70D

lozw

Quote from: nikfreak on January 02, 2017, 02:29:05 PM
Did you try one of those "camera shutter count" online services? What do they show to you?

I tried the ones that allow you to upload an image and they extract it from the exif, but they all report the 70D as not supported.

I didn't trust any of the downloadable utilities.

So I just wondered whether other ML 70D users here saw with their cameras? Does the shutter count look correct?

nikfreak

I never noticed unreliable shutter count info on my cameras. Also I use photoshop to verify EXIf info as well as "EOS Camera Info" on Windows. You sure that your camera was 0 shutter count when you bought it  :P :o ??
[size=8pt]70D.112 & 100D.101[/size]

andy kh

Done resetting, now face tracking works well
5D Mark III - 70D

lozw

Quote from: nikfreak on January 03, 2017, 09:36:46 AM
I never noticed unreliable shutter count info on my cameras. Also I use photoshop to verify EXIf info as well as "EOS Camera Info" on Windows.
Thanks.
I downloaded EOS Camera Info from sourceforge as I was a bit happier about trusting that.

And sure enough it reported the shutter count as 19k.

So I must be grossly underestimating just how many images I have deleted.  :-[

Also I guess the image number probably threw me - doesn't it start back at 0 after 9999?
Hence why the lastest images have something like 8800 - so that would indicate something more like the 19k

Quote
You sure that your camera was 0 shutter count when you bought it  :P :o ??

Not unless Canon took lots of test shots at the factory. It was purchased brand new  :)

So at least that is cleared up now.  Looks like ML is accurate.

bakersdozen

Good news for everybody

Sent from my E6653 using Tapatalk

EOS M + 5D3

nikfreak

which news are you referring to?
[size=8pt]70D.112 & 100D.101[/size]

bakersdozen

The fact that ML is accurate

Sent from my E6653 using Tapatalk

EOS M + 5D3

lojzik

what is blocking approval PR for 70D into unified?
70D.112

a1ex

Detailed reports that should let me (without a 70D in my hands) know everything is alright. Check first post and first item from this sticky. For example, did any of you run the built-in tests (selftest module, api_test.lua)?

I also want to fix the raw overlays in photo mode, or just disable all of them. Currently there is a workaround for zebras only.

Check the PR page as well for a few more suggestions.

lojzik

luatest.log: https://drive.google.com/file/d/0BzVC_OegsMJXbXI0a3ZxWjBicEk/view?usp=sharing
stub api test:
  with lua enabled: err 70: https://drive.google.com/file/d/0BzVC_OegsMJXbkwzQndORE1tMFE/view?usp=sharing
  without lua: 6402 passed, 0 failed 
Generates "quick test" some protokol? (edit: after some time it stops on some photo preview)
70D.112

nikfreak

@a1ex: +1 for disabling the raw overlays completely. No problems when LumaFast is used - neither in QR mode nor in LV.
+1 also for some 100D love.
[size=8pt]70D.112 & 100D.101[/size]

nikfreak

[size=8pt]70D.112 & 100D.101[/size]

XsMagical

Can't wait to give it a try. Thanks!

Sent from my SM-G930T using Tapatalk


X-STATE

Quote from: nikfreak on January 06, 2017, 12:37:34 PM
Just compiled a fresh build based upon the latest 10/12bit raw recording changes. Have fun:

https://drive.google.com/file/d/0B9Mu66yg5QzRRHZDR20xSEZ4RGM/view?usp=sharing
not one of the options for recording 14,12 or 10 do not work correctly
when I play file on the body i can see only vertical stripes
https://yadi.sk/i/sp4YO2MD37KLz3
Body: Canon EOS 70D Lenses: Sigma 18-35mm f1.8 DC HSM Canon EF 85 f/1.8 USM
70D.112

lojzik

luatest - ok
stub api test - ok
SRM memory test - if I make some pictures during test, I get Err 70 or Err 80 (my first run of this test, maybe in the previous version)
Err 70

ASSERT: GetMemoryAddressOfMemoryChunk( GetFirstMemChunk( pMem1AllocateListItem->hMemSuite ) ) == pMessage->pAddress
at SrmActionMemory.c:1862, task RscMgr
lv:0 mode:2


Magic Lantern version : Nightly.2017Jan06.70D112
Mercurial changeset   : d6d295491c1e (raw_video_10bit_12bit_70D) tip
Built on 2017-01-06 11:28:24 UTC by ml@ml-VirtualBox.
Free Memory  : 226K + 1809K

Err 80

ASSERT: 0
at ./Capture/Capture.c:522, task EventMgr
lv:0 mode:2


Magic Lantern version : Nightly.2017Jan06.70D112
Mercurial changeset   : d6d295491c1e (raw_video_10bit_12bit_70D) tip
Built on 2017-01-06 11:28:24 UTC by ml@ml-VirtualBox.
Free Memory  : 224K + 1836K
70D.112

nikfreak

Quote from: X-STATE on January 06, 2017, 01:22:51 PM
not one of the options for recording 14,12 or 10 do not work correctly
when I play file on the body i can see only vertical stripes
https://yadi.sk/i/sp4YO2MD37KLz3

Try on your PC/Mac and only use MLVFS with that. In body won't work atm.
[size=8pt]70D.112 & 100D.101[/size]

Frarike

Does updating to 112 reset the boot-flag?
70D.112

nikfreak

I am unsure. It shouldn't. But you are safe. 112 contains the ML-SETUP.FIR to enable/disable whenever you want
[size=8pt]70D.112 & 100D.101[/size]

Frarike

70D.112

nikfreak

X-State can you give it another try. I updated my post with a new link.
[size=8pt]70D.112 & 100D.101[/size]

X-STATE

Body: Canon EOS 70D Lenses: Sigma 18-35mm f1.8 DC HSM Canon EF 85 f/1.8 USM
70D.112

pontius

Nikfreak, just tested your Jan06 build.
First one produced just garbage on all bit depths and updated build is pretty much the same.
And resolution got limited to width 832 on updated build. I'm using MLVFS & Darktable.
Here is a sample what it looks like.
70D.111B

nikfreak

No problem, let's try a last time this one:

https://drive.google.com/file/d/0B9Mu66yg5QzRYkNjbTZvVFZ0NjQ/view?usp=sharing

If it fails then you have to wait until I return.
[size=8pt]70D.112 & 100D.101[/size]

pontius

Now it works, at least for me. Thanks!
70D.111B