Messages

Lightroom update?
Let me know the plugin version (from plugin manager) and Lr version.
I think the version of the plugin is too old for your Lr version. Please update

More SwissArmyKnife to come! Stay tuned (like Steve Jobs says!)

PEBKAC.

Take a beer!

I noticed a certain latency so that the message appears sometimes

Tof for Houston, everything fine here! 

need more infos (LR + plugin version)



Just checked latest LR SDK doc, tooltip are always presents and have same action as before. Maybe a bug with LR Win?
Try to reload the plugin :

• On Lightroom, open the Plug-In Manager (shortcut Win: Ctrl + Alt + Shift + , (comma), Mac: Command + Option + Shift + , (comma))
• Select Dual ISO Converter
• Click on reload plugin

Please shake me by PM

Just tried now and everything is fine for me. (LR CC 7.4 on macOS + lr_cr2hdr version 3.0-170316-02-MLV-DEV)

Which version of LR and plugin do you use?
Try to move the cursor over checkbox/radio fields, normally you should see a message with all informations from cr2hdr. Otherwise, you could have the docs with a terminal/cmd.

Yeah thanks for that! Glad to see some great stuff for photographers!    i'm excited to test (most probably during the coming days)

Yeah we're on the same way 
I would like to see a help structure like that! But... I don't know if bitbucket allow navigate links like ../ (need to test)

So I could look in modules, see dual_iso, and click the link that takes to the dual_iso help page.

What about modules who add multiple features in more than one menu? Multiple links? For the moment I get the name of the function and the name of the menu, I could links to it but ... same thing: navigation links. Need some tests

Can you add links to the bold headings?

Hm, maybe I didn't understand what you mean on your last post. Do you want a global/menu page including all headings with links to specific explanations ?

I guess it would be good to have the modules also listed in the modules section.  I like how they are in their respective enabled menu, but could be confusing for some to not see modules in the module section.

Sure! I forgot to move modules sources to modules help folder! I'll update soon ... I remember why I didn't do it before. Modules add features to other menus (the modules menu offers no options other than activating/deactivating modules)

taking a look at this

Done. Look at this

New way to parse source files (4x faster: 1s vs 4s). (hectic brainstorm  )

Needs further navigation to extended information.

Yes, the parser need some enhancements to extract multi-lines. Add .choices options could also be added

Code Select Expand


.choices = CHOICES(
    "Simple",
    "Burst",
    "Burst, End Trigger",
    "Best Focus",
    "Slit-Scan",
    "Full-res",
),
.help = "Choose the silent picture mode:",
.help2 =
    "Take a silent picture when you press the shutter halfway.\n"
    "Take pictures until memory gets full, then save to card.\n"
    "Take pictures continuously, save the last few pics to card.\n"
    "Take pictures continuously, save the images with best focus.\n"
    "Distorted pictures for funky effects.\n"
    "Experimental full-resolution pictures.\n",


If it could be useful, I'll spend some time to enhance it

Have you noticed that the script can now install QEMU from soup to nuts?

Yeah! works well! 

@dfort no need to symlink ggrep (https://bitbucket.org/hudson/magic-lantern/src/4895777de907c24ffd6332bcee23a7608450f6bd/contrib/qemu/install.sh?at=qemu&fileviewer=file-view-default#install.sh-103)

And if grep need -P, update script to use in same way 

Brew checks if Xcode commandline are already installed https://bitbucket.org/hudson/magic-lantern/commits/b145d5f6489d3d960d2a8d17a031748c5980684d?at=qemu

Done  think different, acts simply.

Parser is now written in python and does what I expected. What do you think ?

https://bitbucket.org/kichetof/magic-lantern/src/7f853a28906fd9e57ddc3bee703382f229f556c7/help/?at=help_files

(Maybe some bugs with modules who enhances some menu/submenu)

Start playing around to understand (hum... trying to...) a little more ML magic!

Disassembling with disassemble.pl and reading .dis file inside Xcode (> 4Mio lines, Brackets crash )
If I've been following well every steps from first post, I think that I found some stubs for 5D3.113:

Code Select Expand


hg diff stubs.S
diff -r fef4323ae312 platform/5D3.113/stubs.S
--- a/platform/5D3.113/stubs.S  Fri Oct 20 13:16:05 2017 +0300
+++ b/platform/5D3.113/stubs.S  Tue Oct 24 22:21:24 2017 +0200
+//NSTUB(0xff195844,  GUI_SetLvMode)                         /* not used with 5D3.113; 5D2/50D */
+NSTUB(0xff138a54,  PowerMicAmp)
+NSTUB(0xff1388f4,  SetAudioVolumeIn)
+NSTUB(0xff1111f4,  SoundDevActiveIn)
+NSTUB(0xff111410,  SoundDevShutDownIn)
+NSTUB(0xff138cf4,  UnpowerMicAmp)
+NSTUB(0xff349784,  GUI_GetCFnForTab4)
+//NSTUB(0xff4cd5f0,  StartPlayProtectGuideApp)              /* not used with 5D3.113; 5D2 */
+//NSTUB(0xff4cd22c,  StopPlayProtectGuideApp)               /* not used with 5D3.113; 5D2 */
+NSTUB(0xff2718dc,  ptpPropSetUILock)


I think (and I really need to learn), that only one could be useful: PowerMicAmp to start audio_meters_step from audio-common.c (I try to add defined(CONFIG_5D3) but nothing changes)
Time to cool brain!



I'll try Hopper Disassembler https://www.hopperapp.com in demo mode to watch if it's "more simple" that .dis file.
Did you try this app?

I've tested the first build with this feature (Aug 20), but didn't notice any speed difference...

Some tests and you're right! I'll try to test some builds from September, I noticed a difference, that's why I've been so enthusiastic

Some changes from last build (17oct16); always with qDslrDashboard

• No problem in photo mode
• No problem with RAW video (assert when stopping video)
• Unable to get LV display on iPad and unable to start video with RAW video with Crop rec enable (3K and more) and get a crash and LV on iPad freeze in pink

Code Select Expand

ML ASSERT:
0
at mlv_lite.c:2493 (compress_task), task compress_task
lv:1 mode:3

compress_task stack: 1ae538 [1ae5c0-1ad5c0]
0x00069FF0 @ a6a26c:1ae568
0x00069868 @ 6a05c:1ae538

Magic Lantern version : crop_rec_4k.2017Oct16.5D3113
Mercurial changeset   : 8ee7858f0d7e (crop_rec_4k) tip
Built on 2017-10-16 20:22:35 UTC by jenkins@nightly.
Free Memory  : 127K + 3065K


Code Select Expand

ASSERT: fInitialize == TRUE
at ./System/PostPostman/PostPostman.c:243, Epp:19210
lv:0 mode:3

Epp stack: 17bb90 [17bca0-17b0a0]
0xUNKNOWN  @ de48:17bc98
0xUNKNOWN  @ 17bbc:17bc70
0x000178B4 @ ff0de5ec:17bc50
0xUNKNOWN  @ 178e4:17bc40
0xUNKNOWN  @ 1796c:17bc20
0xFF33E01C @ ff183f1c:17bc10
0xFF508348 @ ff33e0a4:17bc00
0x000191D8 @ ff50837c:17bbf0
0x00001900 @ 1920c:17bbc8
0x00069868 @ 69c1c:17bb90

Magic Lantern version : crop_rec_4k.2017Oct16.5D3113
Mercurial changeset   : 8ee7858f0d7e (crop_rec_4k) tip
Built on 2017-10-16 20:22:35 UTC by jenkins@nightly.
Free Memory  : 128K + 3088K


Personally I don't use video mode, so no problem for me, only a bug report

FRSP in photo mode with Full-res LV mode and Lossless DNG is now really fast! Preview for 2s, just a little stripped pink flash (before it was a long flash). I don't know if it's this commit (842e25f) but really appreciate!! (last build 17oct16 used)

First attempt with Lightroom Classic CC (v7), everything works as expected

Same issue with qDslrDashboard with 5D3 113 crop_rec_4k build

Cam crash when I try to record video from qDslrDashboard app on iPad. Err70
When I leave LiveView from qDslr, console on screen with assert message.

crash logs : https://pastebin.ubuntu.com/25745110/

assert (always the same message):

Code Select Expand

ML ASSERT:
measured_compression_ratio
at mlv_lite.c:764 (measure_compression_ratio), task shoot_task
lv:1 mode:3

shoot_task stack: 1c48e8 [1c4a10-1c2a10]
0x000B71B8 @ 9657c:1c49b0
0xUNKNOWN  @ b7210:1c4998
0x00A94FBC @ a988cc:1c4928
0x00069FF0 @ a9513c:1c4918
0x00069868 @ 6a05c:1c48e8

Magic Lantern version : crop_rec_4k.2017Oct07.5D3113
Mercurial changeset   : 1a47ac994cc5 (crop_rec_4k) tip
Built on 2017-10-06 22:55:40 UTC by jenkins@nightly.
Free Memory  : 129K + 2812K


Modules loaded: adtg_gui, dual_iso, mlv_snd, crop_rec, ettr, mlv_lite, pic_view, silent, file_man, mlv_play, raw_diag, iso_regs, mlv_rec, raw_twk

Thanks kichetof

Glad to help you    minor contribution for all your great works!

Happy to see Mac development on top level!

[EOS Utility 2 on macOS High Sierra]

EOS Utility 2 on macOS High Sierra (v2.14.31)

Canon 50D (109; build Nighlty 2017Aug18)

mlv_rec loaded : LV window ok
mlv_rec loaded and activate (Move Record enable, RAW video (MLV) ON) : LV window on EOS Utility doesn't start

Canon 5D3 (113; build crop_rec_4k 2017Oct7)

mlv_lite loaded : LV window ok
mlv_lite loaded and activate (Movie mode, RAW video ON) : LV window ok



EOS Utility 3 on macOS High Sierra (v3.7.0) _{(50D doesn't work with v3)}

Canon 5D3 (113; build crop_rec_4k 2017Oct7)

mlv_lite loaded : LV window ok
mlv_lite loaded and activate (Movie mode, RAW video ON) : LV window ok



On 5D3 after closing LV window on EOS Utility, some warning on cam screen:

Code Select Expand

ML ASSERT:
measured_compression_ratio
at mlv_lite.c:764 (measure_compression_ratio), task shoot_task
lv:1 mode:3 # <-- some logs with lv:0

shoot_task stack: 1c24d8 [1c2600-1c0600]
0x000B71B8 @ 9657c:1c25a0
0xUNKNOWN  @ b7210:1c2588
0x00A2C21C @ a2fb2c:1c2518
0x00069FF0 @ a2c39c:1c2508
0x00069868 @ 6a05c:1c24d8

Magic Lantern version : crop_rec_4k.2017Oct07.5D3113
Mercurial changeset   : 1a47ac994cc5 (crop_rec_4k) tip
Built on 2017-10-06 22:55:40 UTC by jenkins@nightly.
Free Memory  : 130K + 2821K


Maybe same issue here http://www.magiclantern.fm/forum/index.php?topic=20696.0




edit "off topic":
Some tests with qDslrDashboard:

5D3: LV ok but some warning on Cam screen and finally had an Error 70 (error log same as above)
Try to record videos... crash log: https://pastebin.ubuntu.com/25745110/

50D: LV ok in photo mode but unable to have both (LV on qDslr and cam screen); no LV in movie mode with raw

First attempt

https://bitbucket.org/kichetof/magic-lantern/src/db9634046274/help/?at=help_files

Need some works

edit: for the moment, I don't see how to get menu parent items from block like this:
https://bitbucket.org/hudson/magic-lantern/src/30db46575511dc13093c1557ea00b92184264ab7/src/af_patterns.c?at=unified&fileviewer=file-view-default#af_patterns.c-385
https://bitbucket.org/hudson/magic-lantern/src/30db46575511dc13093c1557ea00b92184264ab7/src/zebra.c?at=unified&fileviewer=file-view-default#zebra.c-2676

I only need .name from parents, not inside .children. If you know how to parse that, generator will do the job!

Added language
https://api.bitbucket.org/1.0/repositories/hudson/magic-lantern/raw/default/help/en/sound/Analog gain.md
                                                                                                        ^       ^   ^   ^       ^
                                                                                                    branch    |    |    |        |
                                                                                                      help folder  |    |        |
                                                                                                            languages  |        |
                                                                                                                     ML Menu    |
                                                                                                                              specific help

it's not in the same place as the source code.

Yes, two visions: one from developper: it's more easy to keep doc up to date to update comments in same place; second one from contributor: where's the doc files to update ? inside the code ? Difficult to see everything between every files/lines

What about storing both versions (menu-like directory structure vs embedded in source code) and syncing from both places? That is, whenever one of these two copies gets updated, the other one is auto-updated by some scripts.

I like this idea! Developper updates the doc inside source --> Doc updated; Contributor updates the doc inside help folder --> Source code updated. Cross update may be the solution to keep doc up to date in every plateform.

[Help]

What do you think about something like that:

One repo or branch inside ML, with a structure like ML menus on cam (with an example it'll be more understandable ) and wrote in markdown syntax or plain text.


Help (folder)

• Sound (folder)
  
  
  
  • Analog gain.md
  • Digital gain.md
  • ..
• Expo (folder)
  
  
  
  • White balance.md
  • ISO.md
  • ..
• Overlay (folder)
  
  
  
  • Global Draw.md
  • Zebra.md
  • ..
• Movie (folder)
  
  
  
  • Bit Rate (CBR).md
  • REC key.md
  • ..
• Shoot (folder)
  
  
  
  • Advanced Bracket.md
  • Intervalometer.md
  • ..
• Focus (folder)
  
  
  
  • Trap Focus.md
  • Follow Focus.md
  • ..
• Display (folder)
  
  
  
  • LV brightness.md
  • LV contrast.md
  • ..

Inside each markdown files, we could add the compatibility for each CAM. Exemple: works on: 5D2,5D3,40D,.. (goal: add the possibility to filter the help by cam)

On a help page from magiclantern.fm, we could parse (php, js, python) the markdown inside a static page:

Tab/section/accordion: Sound
https://api.bitbucket.org/1.0/repositories/hudson/magic-lantern/raw/default/help/sound/Analog gain.md
                                                                                                        ^       ^      ^       ^
                                                                                                    branch    |       |        |
                                                                                                          help folder |        |
                                                                                                                     ML Menu  |
                                                                                                                              specific help

With this structure, it's possible to have a help for any branches
Maybe a script could generate the whole structure (folder/md files)

It's my idea of the day 

[≥ 32Gb]

Lexar Professional 1066x

To be sure, ≥ 32Gb (see the write speed for 16Go)