Option to disable sound when FPS is overridden.

Issue #1051 resolved
Former user created an issue

Since the instructions for FPS override suggest that the sound should be manually disabled, is it possible to offer this as an automatic option? If technically feasible, perhaps add a submenu for FPS override and add it there.

Comments (12)

  1. Former user Account Deleted

    That was fast! Thanks. Now I've got to learn to build ML or weight for the next release I suppose. Thanks again a1ex!

  2. Former user Account Deleted

    Thanks for the heads up and link Anon. It seems to work as expected, thanks again Alex. Anon, if you read this, can you give me a hint at how I might find these interm (non-supported I assume) autoexe.bin releases so I can try the latest? Do I need to be a developer on the project or is there a reasonably easy way to find them without being a project developer (if not, no biggie)?

  3. Former user Account Deleted

    Alex, I've discovered that the version linked to above does fix the disable sound on FPS override request but it seems to break LiveView profile selection using the display button (at least on my 600d). I returned to a previous version to confirm. Since this isn't an official release, I assume this is the appropriate place to pass this on but if you'd rather I put in a normal bug report (or if there is any details I can add), please let me know (will check back here).

    Ben (original requester)

  4. Former user Account Deleted

    Alex, let me try to clarify. The (md5: d208d8151959f63a12be1463e7992309 / 1359876 bytes) version (linked to above) acts as follows: 1.) set Config->DISP profiles to > 1 2.) in LiveView mode, the Display button makes the screen flash but does not toggle through the available profiles as earlier versions did. 3.) outside of LiveView the Display button behaves normally (without ML) as expected; it toggles the display on and off.

    Effectively, you can't change ML LiveV menu display profiles (unless there's some other way to switch that I'm not aware of). The last version I tested (md5: 59c830de2b8400f114184d6a9816c3e9 / 217088 bytes) does not have this problem (found at https://bitbucket.org/hudson/magic-lantern/issue/954/play-mode-cannot-zoom-in-a-picture).

    Hope that helps. Ben

  5. Former user Account Deleted

    Sorry for the confusing formatting. Should say Config->DISP profiles gt 1 (on it's own line) followed by 2.) (second point)

  6. Alex

    When DISP profiles is set to 1 => INFO/DISP button behaves like in Canon firmware (it toggles Canon info, histograms, etc).

    When DISP profiles is set to 2 => INFO/DISP button switches the profiles.

    Confirmed to work on 550D, 60D, 5D and 500D.

  7. Former user Account Deleted

    Hmm, I wonder what's different with my (or all) 600D(s). I've just reconfirmed it by swapping out the versions I mentioned previously; with the earlier version (in LiveView) selecting the DISP quickly changes the profile but with the newer version it doesn't change (the ML overlay display just blinks). In fact, I'm on mode 3 but with the newer version I'm stuck on 0 (ML displays profile is 0 and it seems to be the case).

    Here is the most relevant portion of my magic.cfg:

    • disp.mode.xxx = 2904145
    • disp.mode.ccc = 557200
    • disp.mode.bbb = 2707457
    • disp.mode.aaa = 2641985
    • disp.mode = 3

    Should I try clearing the rows shown from the config file and try again? I realize this is hard to track down since you don't have a 600d to test with but perhaps someone else will at least confirm this with another 600d/t3i.

    Thanks for your time,

    Ben

  8. Former user Account Deleted

    Alex,

    A small update and correction. I just realized that you can also use the DISP button to switch between display modes within the ML LView menu and that this too is not working (for my 600d) with the referenced version. However, the display mode is not "stuck" on 0 as I reported. I tried again and it's showing 3 (my current mode).

    Ben

  9. Log in to comment