A few ideas

Issue #478 resolved
Matthew Kieren created an issue

Here's a few ideas I thought I'd share, I apologize if any of them have already been suggested:

1) CMOS temperature displayed constantly above or below ML menus. I like to keep an eye on the temp.

2) Easier to use/understand rack/stack focus. There's got to be an easier way to implement this feature, a lot of people have trouble figuring it out.

3) It would be nice if we could use a remote shutter switch (e.g. RS60-E3) to trigger the rack/stack focus feature instead of the [SET] button. This would obviously be great to prevent camera shake while recording.

4) Holding down a button to have it advance quicker through the settings rather than having to press it repeatedly (mostly for things like the zebra range and other large value ranges).

5) Finer tuning of CBRe (instead of jumping from 50 to 60 allow selecting 51-59 too).

Comments (6)

  1. Alex

    1. I'll put it in the top bar (and display it when menus are active)

    2. How? You will still need to focus the lens through ML. Right now you focus the lens with any method, say "one end is here", then focus to the other end through ML (so it knows how long is the rack), and run. How it would be easier than that?

    3. I'll think about it, but I need to steal the half-shutter press.

    4. For this, I need to know when a button is no longer pressed. For arrows+set, I can figure out this in certain modes, but not in others. For other buttons... no idea.

    5. Why do you need such fine range? It's good to set it a few mbps under the max possible, to make sure it won't stop. More values in menu = more clicks.

  2. Matthew Kieren reporter

    Hi a1ex,

    1) Perfect, thanks! :)

    2) I'll have to give it some more thought and get back to you on this one.

    3) Having the camera shake while pressing the [SET] button for rack focus during a recording looks unprofessional in my opinion, so I think this would be a great feature to completely eliminate that issue. Thanks for considering it.

    4) It's just a minor annoyance, but it would be nice to have. Actually when I think about it if you can get the wheel working this idea probably wouldn't even be necessary.

    5) To push my memory card to the absolute limit and have as much control over it as possible, isn't that what the bitrate feature is really about in the first place? Idea #4 above would definitely help cycle through the values. A simple compromise would be to make it jump in 5 value steps instead of 10 (e.g. 40, 45, 50, 55, 60).

  3. Matthew Kieren reporter

    Wow, I didn't know you already got the wheel to work, that's awesome! Thanks!

    Here's a few more ideas I just thought of:

    A) How hard do you think it'll be to make the wheel also change values instead of only navigating the menu items? Hmm, I can see how it might be difficult and require a lot more modifications to the code.

    B) Since the wheel requires the user to enter Canon's menu system: How about if when a user presses [ERASE] it first simulates a [MENU] press and then brings up the ML menu, and when they press [ERASE] a second time it does the reverse (closes both ML's menu and Canon's menu). I realize that makes it impossible to see the video in the background, but that's not an issue for me at all. Maybe you could make it optional though.

    C) Would it be possible to swap the [ERASE] and [MENU] buttons? Because of the flip-out screen it can be difficult to reach the [ERASE] button sometimes. I find myself going into ML's menu much more often than Canon's.

  4. Log in to comment