Messages

Any chance that we can use a * button as a back focus button on 5D3 to focus rather than taking the silent pic (halfway shutter works well) but if I had the * back button set as a focus (it still takes the silent photo as if I had pressed the shutter but didn't) I remember seeing @Licaon_Kter provide a fix copy of FRSP to being able to use * button for the M or did I read that one from another thread earlier?

It's already fixed, well on my M1 is, does it work on your M1 but not on 5D3?

You mean if you press * it takes a picture
BUT if you press * AND HOLD IT it does not focus and just takes a picture?

And you have custom function set up like this with 1 or 3 selected (or equivalent for your camera), right?



And most important, you need to select a point FIRST ( touch the screen on your M1) before holding * !!! I keep forgetting this too.

/LE: looks like it's working without a point mostly anyway so your results may vary, per focus mode I guess.

On my M1 I get the ML menu by 2 finger touching.


When not using ML I leave the camera on CreativeAssist mode ( means basic ) so anyone can pick it and it just works, but since one is able to enter ML menu even from here it makes things confusing.


Can this be disabled so it _only_ works when the ML mode is selected?


Thanks

They want you to use Marvel instead hence the warning 

[a1ex]

I merged this in my FRSP build (with those 3 tweaks by a1ex too), but there is an issue (at least on my M1):
1. Switch to movie mode ( non raw; crop mode or not, it works the same )
2. dof is displayed ok
3. start recording
4. dof is displayed ok while it AFs by itself
5. now select a focus point
6. *-hold to AF, during focus time dof is displayed ok
BUT, as soon as AF locks on, the dof display yields 0cm | 0cm while the original ML dof still shows an ok value

While recording, this can be repro from step 5 every time.

recording is paused, and it's resumed cleanly (!) after this screen goes away.
Furthermore, during that pause, a fake shutter sound gets recorded in the video

Normal (non raw) picture taking (non silent) during filming yields that for me.


/LE: Updated to 6e3bdba and it's working nicely, I see you raise the cycles to 10 (I keep forgetting to select a focus point before shooting, but after selecting one it AFs fine with *-hold) and you fixed the movie mode bug. Thanks


/LE2: But now I've hit another one unrelated.

- ML Menu just closes on it's own

Known issue, I have it too on M1, kinda annoying: https://bitbucket.org/hudson/magic-lantern/issue/1974/6d-in-live-view-mode-ml-menu-times-out

- Well, I guess this isn't a bug, but where is raw video? I saw some YouTubers recording in raw and I can't find it.

In the video menu of ML, kinda last?

Is this page: <removed>

Nope, no sense since so few added feedback here too, and there are plenty of issues before this will get merged.

Do feel free to give feedback regarding these issues: https://bitbucket.org/hudson/magic-lantern/pull-request/609/fullres-silent-pics/diff

- Profile: i'm on neutral, just 0000. Has to set the best for color correction in post, so neutral, but is there something better, or should i touch some parts of neutral? Just an advice, from your experience.

http://prolost.com/blog/2012/4/10/prolost-flat.html ( no computer needed )


or


https://marvelsfilm.wordpress.com/marvels-cine-canon/


or


http://www.technicolor.com/en/solutions-services/cinestyle

Bumped into an issue on my M1 (at least using my modified build with 10 cycles): forget FRSP on (MLV or DNG it does not matter) and switch to Movie mode (normal one not RAW)

And now 2 things might happen when you press/hold * for AF
1. When not recording you get a black screen with "Manual (M) mode required" warning
2. When recording you get the same black screen with "Manual (M) mode required"
BUT then the led blinks orange fast and camera shuts down!

Trying to start it again yields led flickering green slower, lens activating and deactivating ( the 22mm is noisy) and then the camera stops. (it did not show anything anyway)

Removing the battery fixes it.

The card has no MOV recorded but there's a 0bytes CRASH.LOG.
Yep, this is why this needs more testing: more users digging up AND reporting issues and avoiding merging in main 'till it's good enough, chicken and egg all the way.

Testing the other silent modes while movie is recording:
1. simple - takes the pictures but stops recording when it's done.
2. slit-scan - stops the recording, shows a black screen until you press a button again.

commandline is for power users not for normal users like 90% of us guys

this line... on a forum for a custom software that piggybacks on the Canon firmware and adds features and stuff, really?

You have the latest nightly http://builds.magiclantern.fm/ ?

whats the deal with the voucher?
thx. sw

This: https://www.apertus.org/axiom-beta-after-campaign-end-article-2014


But: https://www.apertus.org/en/faq#Can_I_sellgive_my_voucher_to_a_friend_

I know that using LV display gain with say 3 EV get's things on par though, so maybe this is the solution.

On a second thought... LV Display Gain is no solution as it will disable: Zebras, Spot Meter, False Color, Histogram, Waveform and Vectorscope. :-|

@Licaon_Kter: I've updated autofocus detection code; can you check whether it still requires 10 iterations, or fewer of them are enough now?

Tested a bit more and the current 5 works ok _most_ of the time, but not always.
I bumped it to 10 and it works better (at least on my M1), I find it's kinda hard to miss press * and have it take a picture now, while with 5 I had to be careful to hold it quickly enough.
Regarding AF slow down, I don't see any but then again, my 22 is rather slow, I'll retest with the 18-55 when I get a chance.

@a1ex: Any chance to have the AF wait cycle count selectable in ML menu? It's 5 now, but I feel it might need a bit longer and compiling, extracting card, card reader, copy, card reader, insert card and test is getting tiresome.
And you've got a PM.

I don't think it wouldn't be that hard to implement something like this, but you would need to precisely quantify this curve on every camera. This data would also be quite useful in other ways, for example getting the exposure metadata exactly correct.

So I need to run this: http://www.magiclantern.fm/forum/index.php?topic=12523.msg120758#msg120758 and that would help?


/LE: Compiled 5D v1.2.3 also, hopefully it merged ok from commit c7655e9


Same link: <removed>

/LE: use nightly

Great. But i can not find a build for 5d mk3 fw123 ??

eh http://www.magiclantern.fm/forum/index.php?topic=12523.msg143101#msg143101
see below

[silent]

Compiled all the platforms supported by the silent module so maybe more testers help.

Some notes:
1. Up to commit 5ce2235
2. Added the Depth of field display patch plus these three tweaks.
3. Bypassed the dual_iso/raw_rec module build error introduced in commit 9e99764 ( info here )
4. For the 5D3 1.1.3 build I got the .FIR from the nightlies.
5. Both the 550D and the 600D build have no .FIR, not even in the nightlies.
6. For 7D there are 2 builds, maybe 7D owners know why/how.
7. 650D was build too this time since a1ex fixed it

Link: <removed>


/LE: use nightly

At least on my M1...

I can switch the role of the wheel by pressing wheel-right (BGMT_PRESS_RIGHT), say I can control Shutter speed or Aperture, on Canon the box around the current selected variable has bright green corners, on ML it looks like this:



Which one is selected?

Can the mode be detected by ML and the correct text highlighted ( eg. different color ) ?

Thanks

/PS: I had to upload my own ML picture mode screenshot since I could not find any recent one on Google, but there were some in movie mode.

It explains why your numbers don't match. 8<-------------8<-------------8<-------------8<-------------

Thanks, although I do understand how things work, I do want to have a useful LiveView for FRSP too, hence my question.
Is there a way ( I initially thought Exp.Override was it, but it's not ) to see in LV what you will get when you use FRSP?

I know that using LV display gain with say 3 EV get's things on par though, so maybe this is the solution.

@a1e: So no dark/bias frames on M1 since LV is always on?

http://www.magiclantern.fm/forum/index.php?topic=12523.msg120758#msg120758

I've seen that but I don't know how that helps.


Later I'll try to run the program too.

Technical issues aside, those look mostly ok, can you point me to a post where maybe the correct workflow is explained?


As of now it look like I'm always some stops wrong
if I set = I get
1/125 = 240ms ( 1/4 )
1/4 = 500ms ( 1/2 )
0.5" = 789ms

I can never get the chance to see what I will get, even with Exp.Override the result is over exposed compared to what I previously seen on screen.

What am I doing wrong?

[silent]

Compiled all the platforms supported by the silent module so maybe more testers help.

Some notes:
1. Up to commit 3082908
2. Added some lv_focus_status printing maybe it helps troubleshooting.
3. Added the Depth of field display patch plus these three tweaks.
4. Bypassed the dual_iso/raw_rec module build error introduced in commit 9e99764 ( info here )
5. For the 5D3 1.1.3 build I got the .FIR from the nightlies.
6. Both the 550D and the 600D build have no .FIR, not even in the nightlies.
7. For 7D there are 2 builds, maybe 7D owners know why/how.
8. 650D was not build because

Code Select Expand

[ CC       ]   raw.o
../../src/raw.c: In function 'raw_update_params_work':
../../src/raw.c:538:10: warning: #warning FIXME: are these values correct for 720p and crop modes? [-Wcpp]
         #warning FIXME: are these values correct for 720p and crop modes?
          ^
../../src/raw.c:573:47: error: 'RAW_PHOTO_EDMAC' undeclared (first use in this function)
         raw_info.buffer = (void*) shamem_read(RAW_PHOTO_EDMAC);
                                               ^
../../src/raw.c:573:47: note: each undeclared identifier is reported only once for each function it appears in
make[1]: *** [raw.o] Error 1
make[1]: Leaving directory `/magic-lantern/platform/650D.104'
make: *** [650D] Error 2


Link: <removed>

@a1ex:
1. src/focus.c is missing an S in line 24 at dof.diplay
2. *-hold AF works as expected with the default 5 iterations now.

/LE: use nightly

Updated my M1 build again


@a1ex: What's holding this branch from merging in master?


If there's a need for more testers I can build it for some cameras, as needed ( well except off branch ones like 5D3 1.2.3 )

Updated again, this plus these three tweaks


Link:


/LE: use the nightly, it's merged in main already

[ljpeg = "True"]

MlRawViewer supports the "lossless compressed" mode of the DNG spec, which makes the files smaller without losing any information.

And you can force it to export uncompressed by editing ExportQueue.py at line 471 by changing ljpeg = "True" to "False" save, exit and delete ExportQueue.pyc.
I need them uncompressed since darktable (see comments) does not (yet?) support compression.

@baldand: Any chance to have compression option-able? I'm afraid that in the future it might not be this easy to disable it and the darktable devs did not say anything about supporting it in the future ( although as I point them out in the comments there this is in the standard at least since DNG v1.1 ).