Author Topic: Canon 70D (Read 2345774 times)

Walter Schulz · « **Reply #2025 on:** November 26, 2015, 12:28:05 PM »

Please test bitrates for IPB/IPP, too.

OlRivrRat · « **Reply #2026 on:** November 26, 2015, 07:40:33 PM »

@NikFreak

QuickZoom seems to be Functioning As Expected/Quite Nicely.

OlRivrRat · « **Reply #2027 on:** November 26, 2015, 07:50:36 PM »

Transcend 32GB 600X 90MB/s~Read

Put image in Picasa & added URL between img & /img tags ~ That doesn't seem to work either.

ainu · « **Reply #2028 on:** November 26, 2015, 08:26:35 PM »

lubo, my card Kingston SDA3/64 GB SDXC UHS I U3 (R/W marked as 90/80 mb/s) write speed test rezults (Mb/s): 41.6 , 40.8, 40.5, 39, 36.1, 37.9, 31.2, 15.9.
Transcend 32gb 10 class write speed: 30-32 mb/s.

Quick zoom is work fine for me at all it's settings.
May be I'm stupid, but I can't understand what setting ""Image Review" -> "CanonMnu:Hold->PLAY" must do. -> I can't test it. Can anyone tell me what this setting do?

laci.szebeni · « **Reply #2029 on:** November 26, 2015, 08:34:29 PM »

Quote from: ainu on November 26, 2015, 08:26:35 PM

lubo, my card Kingston SDA3/64 GB SDXC UHS I U3 write speed test rezults (Mb/s): 41.6 , 40.8, 40.5, 39, 36.1, 37.9, 31.2, 15.9.
Transcend 32gb 10 class write speed: 30-32 mb/s.

Quick zoom is work fine for me at all it's settings.
May be I'm stupid, but I can't understand what setting ""Image Review" -> "CanonMnu:Hold->PLAY" must do. -> I can't test it. Can anyone tell me what this setting do?

It means that when you set your canon menu to review the image after it's been taken for "Hold" time, you no longer have to press the Play button in order to zoom into the image.

In the Canon menu you can set how many seconds you want your image to be displayed after capture. You can choose between 2, 4, etc seconds and Hold. If set to hold, the image is displayed until you press something else.
Now usually, in order to zoom into a image after capture, you'd have to press the play button first.
But with that ML feature enabled, if you set Hold for the above option, you no longer have to press play and you can zoom into an image as soon as it's been captured.

aedipuss · « **Reply #2030 on:** November 26, 2015, 09:42:38 PM »

Quote

So how does 1 add an image/attach'?

OlRivrRat this appears to be one of those forums that doesn't allow direct uploads of pictures. you have to insert the url of the image from somewhere on the web between the img and /img tags. i use a temp folder in one of my website.

nikfreak · « **Reply #2031 on:** November 26, 2015, 09:59:44 PM »

updated first post. Read changelog.

TechnoPilot · « **Reply #2032 on:** November 26, 2015, 10:21:05 PM »

Quote from: nikfreak on November 26, 2015, 09:59:44 PM

updated first post. Read changelog.

Seems you still have it listed though as having bitrate modifications disabled, is this a new revision from the 2b beta you posted on the 15th? While I know that people seem to found the modified bitrates not to work, they were enabled...

nikfreak · « **Reply #2033 on:** November 26, 2015, 10:28:04 PM »

rec indicators are included in bitrate source. I grabbed 5D3 implementation and replicated it for 70D.This would let me disable bitrate features again but have rec indicator enabled as requested. You better updated to the build from 1st post as it differs from the test-zip posted some days ago

. You might want to always check the bitbucket source to see when the last commits were done.

TechnoPilot · « **Reply #2034 on:** November 26, 2015, 10:31:08 PM »

Quote from: nikfreak on November 26, 2015, 10:28:04 PM

rec indicators are included in bitrate source. I grabbed 5D3 implementation and replicated it for 70D.This would let me disable bitrate features again but have rec indicator enabled as requested. You better updated to the build from 1st post as it differs from the test-zip posted some days ago . You might want to always check the bitbucket source to see when the last commits were done.

That's why I wanted to check! Will update tonight!

OlRivrRat · « **Reply #2035 on:** November 26, 2015, 11:26:22 PM »

      @TAWIMC

   I Am EverSoThankful for NikFreak & All the rest of the M'L' Wizards.

                     ORR ~ DeanB

ainu · « **Reply #2036 on:** November 27, 2015, 10:01:11 AM »

laci.szebeni, thanks for detailed info.

"Image Review" -> "CanonMnu:Hold->PLAY" works as expected.

Maybe I deviate from a discussion subject a little. Whether realization of switching off/on of external flash "fire" by the button of opening of the built-in flash is possible?
In the standard canon menu there is such function at the connected and turned on external flash.
Whether it is possible to process in ML events of pressing of buttons if the menu ML isn't caused?

I found a similar question in this subject, but I can't understand possible algorithm of realization.
http://www.magiclantern.fm/forum/index.php?topic=13043.msg157809#new

It is necessary to find the address of function which is carried out in the standard canon menu in my representation and to write the handler of pressing of the button.
I apologize for the simplified description in advance. I so far only understand as the firmware and ML works.

OlRivrRat · « **Reply #2037 on:** November 27, 2015, 11:34:00 PM »

@NikFreak

Arrow Shortcuts Functioning Nicely ~ Thanks Somemore ~

nikfreak · « **Reply #2038 on:** November 28, 2015, 02:19:51 PM »

Ok, everybody. a1ex implemented a new boot method and here are the zips for you to test:

https://drive.google.com/folderview?id=0B9Mu66yg5QzRSVhOVnBHWkFCRDA&usp=sharing

What to look for?

just test-drive the build. Anything wrong?
The only thing I added on top of the new boot method is Dual Iso support in movie mode. I now need someone to take some time and simply retry it again. If it still causes problems (which I expect but who knows..): Upload a few dng frames of the dual iso movie and post a link here so we can point a1ex to have a look at those dng's.

aedipuss · « **Reply #2039 on:** November 28, 2015, 05:10:03 PM »

the test build hard crashed my 70d. i was in movie mode, brought up magic lantern menu, menu closes cam starts recording and won't respond to any buttons including the off switch. removed battery to stop it. repeated a second time to verify. now removing test build.

here's the crash.log - ASSERT: 0
at ./Memory/Memory.c:575, task AeWb
lv:1 mode:3

Magic Lantern version : Nightly.2015Nov28.70D111A
Mercurial changeset : 15be51f3ac34+ (70D-merge-dryos-hooks) tip
Built on 2015-11-28 12:52:56 UTC by ml@ml-pc.
Free Memory : 238K + 2992K

OlRivrRat · « **Reply #2040 on:** November 28, 2015, 06:14:30 PM »

@NikFreak

It Seems To Be Quite Functional ~ Have not had time for any InDepth tests but in light of Aedipusss post I did attempt to replicate & encountered

No Issues. Actually tried to see what might happen if activating M'L'Menu During Rec' & was surprised that it Did Display & Continued to 'til I Manually

deactivated it (No AutoShutOff as it Normally does in Movie & LV).

ahsan · « **Reply #2041 on:** November 28, 2015, 06:47:53 PM »

@Nikfreak Please kindly fix ML menu. It disappears after some seconds.

nikfreak · « **Reply #2042 on:** November 28, 2015, 06:51:19 PM »

Ok guys before it gets lost: try dualiso movie mode and share some dng frames as requested earlier

@aedipus: your problem is a known and old one to me. Might happen to others on 70D.111A using the test build too. Why? I was playing around with fps override feature and it's enabled on the 70D.111A build only but is broken and causes your crash. So nothing to worry. Update: Can you redownload the test build again please. Your problems should be gone now.

nikfreak · « **Reply #2043 on:** November 28, 2015, 08:51:48 PM »

Important update: everyone having installed the test build from earlier today please redownload (same link) and install them NOW again or you might get issues.

TechnoPilot · « **Reply #2044 on:** November 28, 2015, 09:20:48 PM »

Rolling up to most recent Beta 2c, will let you know if I run into anything and I will see what I can do to provide the dual ISO test.

TechnoPilot · « **Reply #2045 on:** November 28, 2015, 09:28:10 PM »

Okay bad news...instant crash as soon as I engaged liveview in movie mode when I turned on the camera after it warned me that my bag had slightly disengaged the lens. I locked the lens back on, hit the liveview button, heard the mirror flip up and was instantly presented with the crash notice on screen.

Code: [Select]

ASSERT: 0
at ./Memory/Memory.c:575, task AeWb
lv:1 mode:3


Magic Lantern version : Nightly.2015Nov28.70D111B
Mercurial changeset   : 15be51f3ac34+ (70D-merge-dryos-hooks) tip
Built on 2015-11-28 19:44:03 UTC by ml@ml-pc.
Free Memory  : 146K + 2176K

Please note that I had copied my settings over from the Beta 2b, so I will retry with a vanilla build and update this post with my results.

nikfreak · « **Reply #2046 on:** November 28, 2015, 09:36:35 PM »

yes keep me updated

TechnoPilot · « **Reply #2047 on:** November 28, 2015, 09:46:56 PM »

To update what I posted above, sadly, as soon as I turned on the camera in movie and C mode (what I use for movie settings), the camera drew the ML overlays and as soon as it finished, it crashed again on a vanilla copy of Beta 2c. Same crash log essentially, but in case included below:

Code: [Select]

ASSERT: 0
at ./Memory/Memory.c:575, task AeWb
lv:1 mode:3


Magic Lantern version : Nightly.2015Nov28.70D111B
Mercurial changeset   : 15be51f3ac34+ (70D-merge-dryos-hooks) tip
Built on 2015-11-28 19:44:03 UTC by ml@ml-pc.
Free Memory  : 231K + 2434K

Rolling back to Beta 2b for now...

nikfreak · « **Reply #2048 on:** November 28, 2015, 09:54:05 PM »

Quote from: TechnoPilot on November 28, 2015, 09:46:56 PM

Magic Lantern version : Nightly.2015Nov28.70D111B
Mercurial changeset : 15be51f3ac34+ (70D-merge-dryos-hooks) tip
Built on 2015-11-28 19:44:03 UTC by ml@ml-pc.

the built time doesn't match! Please just try again. To be rest assured there was no mistake on my end I re-updated the zips in the link.

TechnoPilot · « **Reply #2049 on:** November 28, 2015, 10:02:23 PM »

Okay I re-downloaded the build and yes I can see a later build time, but sadly I see this in the crash log. Same exact crash as previous:

Code: [Select]

ASSERT: 0
at ./Memory/Memory.c:575, task AeWb
lv:1 mode:3


Magic Lantern version : Nightly.2015Nov28.70D111B
Mercurial changeset   : aae92eae46f1 (70D-merge-dryos-hooks) tip
Built on 2015-11-28 20:50:58 UTC by ml@ml-pc.
Free Memory  : 231K + 2435K

News:

Author Topic: Canon 70D (Read 2345774 times)