Messages

[upon the timer_A]

Guys, disabling it for next update doesn't mean it will be completely lost. Check again my post. I stated there's hope but really all fps features you tried til now were based upon the timer_A. I never got timer_B (needed for exact fps, 180d...) to work. But there's a way I got timer_B to work. The adtg module has an option to force low fps and that works by only using timer_b. To find a proper solution or at least a hint I have to talk to a1ex at a later time and this is why I will disable it on next update. It will be back again once I get timer_B to work! Then, fps override will be back and that time fully featured w/o dirty implementation. At the actual state it was rather hacky but always prepared for a merge into unified. Think of it seeing it from the ML codebase's view. 70D wouldn't be enough to justify some dirty implementation, right? So let's focus on making the build as stable as possible. Work on 70D will continue. Now and also in future....

btw: hdr video has been confirmed by DeafEyejedi to work.so will be back again with next update as well as gradual exposure and atm I am also re-investigatin bitrate options...

Okay, awesome to hear Nikfreak!  See you give us features we like and we tend to panic when you hint at maybe taking them away. [emoji14]

It makes sense though what you mentioned and I have to give you kudos on your work around using timer A then, as it felt quite solid and not at all cludged together.

Awesome to hear that the HDR and gradual exposure features will be coming back in the next build, I can't wait!

Amazing work as always Nikfreak, thank you for all the hard work and time you put into this port for the 70D!

      @JohnnyG_71 & @DeafEyeJedi & @NikFreak

   Just tested FPS-Overide @ 7, 8, 9, 10 - H264 From 24All-I & I get Vert' Streaks @ 7 & 8 but Not @ 9 & 10 ~

It seems a shame to disable a Very Useful Function because it displays an issue in a Very Small (Possibly even Seldom Used) Portion of its Functional Abilities.

It could be argued that if that path is to be followed, the whole ML Project should be disabled because it has a few bugs.

                    Why not just make note of the issue in "What's Not Working" & move on to other Fixable Stuff.

I quite heartedly agree OlRivrRat, it would be a real shame to disable this feature when I feel it is quite useful and usable in its current state, though I do understand your sentiment on not wanting to hear about banding issues.  I would however point out that the 70D is not the only camera to experience it and it seems to be present even in the 5DIII build from the research I've seen on the banding issue.

@shakenda, I'd have to echo @nikfreak on that feeling.  I've been running it non-stop since alpha5b through multiple gigs and have experienced no showstoppers, with the newest build being the most stable yet.

I have a problem with magiclantern-Nightly.2015Aug15.70D111B
When navigating in the ML menu it closes the ML menu (after a random number of seconds betweeon 5-20 seconds). It is very annoying because you try to change some settings and boom, no ML.

I also had this problem with previous versions

@EvoX - Please ensure you read the first post.  This is a known problem with ML in general on multiple cameras when using LiveView and can be worked around by opening the ML menu while the camera is not using LiveView.

You might not have luck with h264 with the earlier linked solution. I thought the patterns were only appearing while raw recording (see below)!?

http://magiclantern.fm/forum/index.php?topic=14309.msg152546#msg152546

I highly doubt I will have any luck doing anything like what you linked with the h264, I mean I'll see what my results are with using it with a RAW undercrank video.  I'll also offload those h264 3 & 6fps videos I took at the airport and see what the banding is like on a large monitor, honestly it appears no where like what I'm seeing with others using it with RAW and will probably disappear with grading from the flat Cinestyle profile.

I know the arrow keys would work but as written in changelog I want to finetune it so that it's really a single button press (maybe unpress) and cannot be activated by another button. It's a lil bit of hard work but we can always switch back and use the last implementation.

regarding banding / possible fixed pattern noise:
You written you captured the banding with lens cap on, right? Please read the following message up to the end and try this if ou got time:
http://magiclantern.fm/forum/index.php?topic=7122.msg152597#msg152597

Fair enough and definitely makes sense on the arrow shortcuts point.  I think I am getting what you mean on that point of only a single point of trigger (admittedly though I never stumbled upon another in my testing and use).

I will see what I can do on the link you sent which I have now read through.  I had not yet tried capturing a dark frame (lens cap on), though my testing and experimenting with undercranking had been in ALL-I h264 and not in RAW, as most of my video work does not warrant the extra work in post or storage requirements of RAW video.  I will let you know my results though when I have a chance to sit down and run through the steps listed in the link.

Just to confirm since you implemented the feature in this build at my request:

Record button shortcuts - Working, both with and without hold in all testing (Still have to try with remote trigger port after I finish rewiring my handle to not use Lanc) [emoji14]

Thanks again for implementing that for me!

@Technopilot: I'll have a look and try to enable "Gradual Exposure" with the next update again. Those patterns you talking about seem to be interesting topic too. I've posted some link to a topic covering such things here.

That would be awesome if it can be made to be implemented without having to enable another non-functional component.  The only issue I found was with large rapid exposure changes as a reported before, but even then, it was only with the reported current ISO not with the actual gradual image change (incorrect ISO being displayed in the ML overlays compared to actual ISO value).

I read through a lot of what you linked to and I have to agree it does seem to be fixed pattern noise, probably caused by the CMOS sensor itself that is creeping in, even in h264 recording, though most of the reported problem seems to be when undercranking in raw. I feel like a lot of the discussion seems to focus on, might require customized dark frame subtraction on a per camera basis to be implemented to properly eliminate it and is probably beyond the 70D specific development that you are doing.  That is my two cents.

I also just noticed last night, the removal of the arrow key shortcuts (I really need to read the release information closer from now on).  I am assuming you have some ideas for better implementation of this function by your comment?  Overall, the previous implementation worked pretty well in my experience and was only hurt by the initial Canon menu appearance overtop of the ML overlays on the initial press of the AF button.  Is there anything that we can do to help further development of your preferred solution for this?

Admittedly, I tried both 6fps and 3 fps overcrank at 100iso the other day while I was sitting at the airport, and while the banding was present and agree that it is consistent, it was not super visible (i.e. not really visible on the back screen without looking for it).  What I really miss and actually spend probably 10mins looking for when I first upgraded and noticed it has not rolled over in my transfer of the settings file was the gradual exposure, this a really miss and was a huge feature to me.  I know it was part of another item in the build that was disabled, but it really on its own was a significant feature that to me was huge and worked extremely well (sorry I felt it was well reported it's solid functionality and I didn't personally submit its effectiveness).  I never had an issue.

I'll submit an official report tomorrow, but what I see has been improved though still not perfect is the record mode picture profile.  I had issue with it not reliably switching to my record profile of Cinestyle over Standard for when not recording.  While this is improved and the second video after boot reliably switches to Cinestyle, the first almost guaranteed never switches out of standard.

(Yes I have not updated my sig on the computer yet, I'm writing from Tapatalk on my Note 4, but I'm on build B with my 70D)

Regarding audio bug reported by @tomtom91:
http://www.magiclantern.fm/forum/index.php?topic=14309.msg152532#msg152532

Next update will include the fix (props @walter for the hint) and audio meters + remote shot will work, too  [emoji14]

YAY!!! So awesome to hear you have the audio meters functional Nikfreak!  Great work!

[commited]

@Technopilot: I will enable the button assignment functionality on next update. It's already commited but needs a merge. It will then be up to you to test it. But I guess (read: no promise) that it will work.

@DeafEyeJedi: as always thanx for taking time and providing those vids. I really appreciate it.

@nikfreak - I'll test on next update then and confirm.  Thanks!

@Nikfreak - A question for you, is there any chance we can get the "Movie Record Key" button assign functionality into the next ML build for the 70D?  I'd like to wire in the remote record button on my Tilta Wooden Grip Handle to trigger the record start/stop function of the 70D without hacking into the body and this seems like the best way I've seen, by assigning it to the half shutter press and some very basic wiring to the remote plug on the camera.  Here is the link to the article that I found referencing this function http://www.diyphotography.net/dslr-rig-video-remote-record-button/

Hey guys,

I can't find the maximum video resolution of the 70D in Raw mode. Someone could tell me Please ?

Hi Antholight, this is somewhat dependent on the card you are using (what speed it can sustain write if it is below the SD slot limit of 45MB/s) and the very dependent on the aspect ratio you are wanting to use.  The best bet is to experiment with your setup and see how long it will record before it starts skipping frames and stops recording.  There are many examples of what other people have managed to achieve is further back in this thread.

Very cool use of MLV video!  Gorgeous work!

Truthfully I'm sure it will come eventually, especially considering it is the only Canon DSLR that can shoot 1080/60p right now, I would just caution you have to be very patient.  A number of us have been waiting for a 70D ML build since that glorious camera first came out and that has just made steam at the end of Q1 this year with the first alpha, in part thanks to amazingly generous people helping a developer with some free time, get his hands on the body.

My two cents,
TheTechnoPilot

Quote from 1st post:

Hi Nikfreak,

Sorry about the lack of that, I'll boot up my computer tomorrow, login and add it.  For now, just know I'm running the 111B firmware.

I've been noticing a lot more inconsistency with the latest 6b build and 6 from the 5b switching from a display picture style to the record picture style.  It used to reliably switch, but the new versions don't always, especially for the first recording after a bootup.

Remove SD-card and format it in your PC.

Hi hate to say, but that is probably not the best option as it would leave the boot flag intact on his 70D.

If you are just trying to roll back simply delete all the ML files from the SD card and replace them with the version you are wanting to load.  Just remember to ensure it is the correct A or B build.

If you are wanting to uninstall ML then simply go to the update firmware option in the Canon menu and wait for the timer on ML to run out (60 seconds).  If that is not working on the newest build then try rolling back first as I know Alpha5b worked for this.

@NikFreak

Okay so I took the time to run through some temperature testing on my 70D.111B.

Alpha 6
Idle: 184
5:00min: 194
5:45min: 197
10:00min: 202
15:00min: 206

Alpha 6b
Idle: 192
5:00min: 208
5:45min: 211
10:00min: 211
15:00min: 213

Overall I found it ran hotter than Alpha 6, this was with the same settings (manually setup).

One thing I did find different is that with the old Alpha 6 build, if I hit the ISO button while recording video, nothing happened, now in 6b it highlights the ISO value and the control wheel now changes the value and it does not error, however using the AF Mode button while recording does during rapid changes.

If there is anything else I can do to help, let me know.

[These are not °celsius / fahrenheit. Just raw values but thx for testing. Looks like a placebo on my side]

These are not °celsius / fahrenheit. Just raw values but thx for testing. Looks like a placebo on my side 

FRSP is working nice over here. No problems saving as DNG / MLV. Can't reproduce your issue atm.
Grip: use w/o to see if it works. I guess it would also happen with original grip

I'll give it a test when I get home as well for a richer dataset of cameras, though I'm also revB.

      @NikFreak

   Figuring that it was something in My Settings (PilotError) (as I usually do in these sorts of Situ's) I gave the ML Menu another OnceOver

& noticing that I had Gradual Exposure "On", decided to turn it "Off" to see if that would resolve the issue - It Did.

Interesting, since I am shooting with it on for those tests, I haven't tried it with it off since it was working.

6b shouldn't change that behaviour but thx for the detailed report (either it hasn't been reported that way til now or I didn't see it til now - it's new to me). That means I need to take a look again at arrow keys but anyways I recommend everybody to update as the log files (links on bitbucket) show no errors with 6b. if you have time please do a comparision of raw temperatures as stated above:

Yeah, truthfully I didn't notice the issue until now as I have not had to change my exposure often after the start of recording.  The questions queued me to try it out.

Sure thing Nikfreak, I'll compare some extended runtime temps tonight before upgrading and after, does it matter to you if it is extended recording temps or just camera running temps, do you have a preference?

Just to comment on my side, I was pretty sure it was working for me and on my 70_111B running Alpha6 I had no issue when not recording, however while recording I have to press and hold the AF mode button to keep the arrow buttons active and I can then change it.

I did notice however that the ISO value displayed often errors and shows an erroneous value (a value from the other direction of the change) when the ISO is change rapidly up or down while recording and remains showing that erroneous value until the smoothing completes or the value is changed again with the arrow keys.  This similar thing happens less frequently while not recording, however the value corrects itself in this case before the smoothing completes, usually in what seems like one second.

I'll move up to Alpha6b later today and see if this changes the behaviour.

Bummer, thanks TechnoPilot for the update before I did anything. Guess I'll wait and keep using my 60D till a version is ready with the audio features. Thanks again!

No problem, glad I could help!

Just so you know however, while some have reported issues using DSLRController with ML, I use both personally and haven't yet had issue.

Cheers,

I have a 60D which I installed ML on years ago but have been waiting for a stable release for my 70D. I can't wait any longer, I'm ready to install the Alpha because I need audio monitoring very badly but have a question that I did not see answered yet. I purchased the Manfrotto Digital Director for my iPad in hopes that it would allow audio monitoring and while it does have VU meters, it will not play the audio through the iPad. So my question is, after installing ML will the features of the Digital Director all still work? And if they don't, will the uninstall ML procedure work to put the 70D back to the way it was? Thank you!

Unfortunately to tell you, the audio monitoring, control and meters are not yet implemented in this Alpha as there is a new audio thread that has yet to be merged into the main ML build and it makes sense not to duplicate work, they will then have to be debugged before inclusion.  I was talking with Netfreak on the matter about a month ago when I was asking what I could do to help push the audio development on this Alpha along as even just the meters was all I found missing from ML for my normal workflow.

If the iPad device connection functions using similar forks into the Canon hardware as DSLRController, you might run into some issues as I believe people have reported conflicts running both the external device connected to USB and ML.

As for removal of ML, it is functioning perfectly well with the firmware install, & wait 60secs to uninstall function.

Hope this helps!

in Alpha6 how can se the Temperature of my 70D?

You can still access the raw sensor values however from the Magic Lantern menu, though this is the raw value and not a true unit.