Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.

Messages - Walter Schulz

Pages: 1 [2] 3 4 ... 253
No problems with 128 GB cards here or ever reported.
Format card in cam, copy extracted nightly build content to card and redo installation.
If your problem persists:
Your error description is not very precise. Can you record the install session? Quality don't matter that much.

And check your card with h2testw (Windows) or f3/f3GUI (macOS).

Sorry for the confusion.
Top of page -> Downloads -> Downloads (drop down menu) -> Experiments. Pick your Lua_fix build and copy contents to card.

Raw Video / Re: shooting raw affect shutter count?
« on: February 06, 2019, 01:04:15 PM »
One point: fps*record time shutter actuations a session might confuse Canon and void claims of warranty (if any).

Wording in conjunction with text on the bottom is confusing. At least I fell for it.
What about "Override 30' limit" ON/OFF?
OFF: Stops after 30 min
ON: Don't stop

Don't know if the most recent 1200D build contains the changes to make this happen.
First check Prefs tab -> Powersave in LiveView. Is there an menu item "30-minutes timer"?
If yes: ON is what you want
In not:
You have to write the Lua file yourself:
Open editor, copy script contents (found in thread linked above) to file and save it as pwrsv.lua into ML\scripts
And -as written above - I do not know if it will work with your build.

General Help Q&A / Re: Am I being really silly ..
« on: February 05, 2019, 10:35:37 AM »
Trashcan button -> Movie tab -> FPS override

Camera-specific discussion / Re: Canon 7D Mark I
« on: February 03, 2019, 05:56:14 PM »
If freeze is reproducable:
Document steps to reproduce the issue and create an issue report.
Cream on top: Test this procedure in 2.0.3
If it happens in 2.0.3, too:
Create a bug report here instead. After checking if it is a new and not reported earlier.

Camera Emergency Department / Re: help!!!!!
« on: February 03, 2019, 02:44:24 PM »
Remove battery, remove card.
Insert battery. Do not insert card. Close all compartment doors. Try to power up cam.
Report results. Cam coming up? LED blinking?


Camera-specific discussion / Re: Canon 100D / SL1
« on: February 02, 2019, 08:08:34 AM »
Workaround in reply #365.

Thanks for clarification!
Well, 7D user here and until moto season begins there is some time for testing.

Steps to reproduce:
Start photo mode with ML defaults.
Take a pic.
Switch cam to bulb mode.
Open ML menu. Go to Shoot screen -> Bulb mode -> Q
Set Exposure duration to 40 seconds
Set Display during exposure to Show previous pic
Leave menu by half-shutter press.
Press half-shutter for > 1 seconds. Cam should make a beep and beginn to take a pic.

Expected result (with bug):
- Screen turns dark (no pic shown) and remaining time counts down. (Upper left area).

After bulb mode terminated you will see the pic in review.

Now take a second pic in bulb mode. Expected result (with bug):
- Screen turns dark (no pic shown) and remaining time does not show up at all.

Please test (owners of other D4 cams as well) and report back!

EDIT: Found time to downgrade to 2.0.3 and build #3 (2013Dec22). Did not work either. Third shot with option Show previous pic: No countdown line written. And clock (counting up exposure time, showing lower right corner) doesn't show up at all. Missing pic, too.
More to debug:
Option "Display during exposure Don't change" doesn't show any message. 650D shows clock incrementing.
Awaiting reports from other D4 owners before opening Bitbucket issue.

650D, option "Display during exposure Don't change"

v2.3 outdated and not supported

Not sure if here or Tutorials and Creative Uses is the right place to ask.

Came up with an idea for future tutorials. I think users might want to have some kind of reference for the things written to Quick Control screen by ML. Could be in written/non-interactive form with pics like this (incomplete):

or interactive for electronic devices (no example here).

Question 1: I looked into source code trying to find out which features are interacting with Quick Control. But I suck as a programmer and couldn't make sense out of it. Is there a list of features writing to QC screen?

Question 2: There a some differences in QC screen between my 650D (Digic 5) and 7D (Digic4).

Examples:            7D        650D
Battery level:       yellow    none
MLU:                   yellow    white
Adv. Bracket         none     white
intermediate ISO  alligned not alligned/artifacts
Date                    none     white

No lens info, no build info displayed in 7D's screen.
May a developer drop a word about those differences? Has to work this way because of Canon or something lost/gained in transistion? I kind of like ML's interaction highlighted. Personal issue, of course.

And another one:
AFAIK option "LCDsensor Remote" is the only one where menu icon changes this way. I think it is redundant and should be dropped to maintain user interface standard.

Requires experimental lua_fix build. Top of page -> Downloads -> Downloads (drop down menu) -> Experiments

Tutorials and Creative Uses / Re: Let's restore camera help (Help needed)
« on: January 31, 2019, 10:11:56 PM »
Write permissions fixed, thanks!

@a1ex: If you have time to look into menu issue (replies 5-7): "Mirror Lockup" shares the same problem. In Shoot screen you can toggle by SET button but only between OFF and either "SelfTimer (ON)" or "HandH, 1/2-1/125" or "Always ON".

Shoot and Focus are almost done. Exception: Everything about modules Silent, Deflickr, Adv_int hasn't been touched yet.
I'm about to enter Movie tab but I'm (as almost a novice to movie tab) gonna have to work through all the options the hard way. Will cost lots of time. If there is anybody able to put the burden from me ... Help, please!
Same for ETTR and Autoexpo!

EDIT: Working on Silent pics ...
11.02.19: Silent pics almost done. Missing: FRSP (gradient, time-lapse workflow, limits, interaction issues) and naming with/without intervalometer/bracketing.

and the rest of miket's posts. Also lookup g3gg0's offer in this thread about implementing another sync method.

But especially for long periods you have to pay attention to the Arduino too (millis () overflow after 49 days).

True, but there are routines to master this issue and - as in most such devices - there is a proper watchdog on board.

Camera-specific discussion / Re: Canon 650D / T4i
« on: January 30, 2019, 03:11:44 AM »
Not available on 650D: See -> Prefs -> sticky_Halfshutter

Camera-specific discussion / Re: Canon 100D / SL1
« on: January 30, 2019, 03:09:47 AM »
Just saw an offer for 100D + 18-55 STM for 220€ and another (body only) for 180€. Shipping not included, though.

Oh, forgot to mention: 600D runs by Digic 4 and 100D/650D by D5. Makes a difference for some AF related features. Trap focus not running. And - at the moment - Dual-ISO not working on 650D.
Feature list:

Camera-specific discussion / Re: Canon 100D / SL1
« on: January 29, 2019, 10:41:15 PM »
I own a 7D, 650D and 100D.
What I like about 100D:
- Lightweight
- ML feature set (apart from some lesser used features it works quite well for stills)

What I don't like
- Handheld it is sometimes too small. Not well suited for bigger lenses. Grip could be improved.
- Battery life. Boy, that is a small battery! 650D is covered with Amazon Basics but 100D is not.
- I work with tripod a lot. There is not that much room for plates if you don't want to block battery/card compartment.
- A swivel screen would come handy for tripod/macro work.
- Buttons, lack of.

Doesn't sound convincing. Not the whole truth because:
This cam is fun to use, easy to go with and a very good choice for going handheld /street photography with a not-so-bulky lens. Very, very good price-performance ratio IMO! (Mint condition: 165€, Germany)

I would go and check ergonomics first. Grip might be an issue for not-so-medium hand sizes.

There are indeed key differences.
An external intervalometer has no problems to access the cam and thus ending powersave mode. ML's intervalometer however has to run all the time to do its job. It can not end powersave on it's own. Cam will not even enter powersave mode while intervalometer is active.
Therefore - in your use case - a tremendous difference in power consumption and battery life will occur.

But a word of advice: As an engineer I will never ever trust any software to run unattended over such a period. Proper engineering would involve something called a watchdog to act on software stalling or power failures. They are designed to restart a device in a proper manner after such mishaps. Unfortunately consumer devices are not designed to work with watchdogs in a pleasant way (for an engineer's paranoid mindset).
Instead I would recommend some single board computer (Arduino for example) with control to power input in your setup. It is able to turn on and off power as wanted (requires almost no programming skills) and trigger events (=actuations) as needed.
As long as cam is working and there is some kind of external power supply you are covered.

EDIT: Just realized there is a way to trigger a watchdog by intervalometer. Just by using cam's LED. But it makes little sense to me to use this option if cam's power supply will be switched on and off by this very external device.

If you don't understand a word I'm saying contact your local maker facility (I hope there is) or a friendly tech wizard you may know.

Pages: 1 [2] 3 4 ... 253