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 ... 264
Camera-specific discussion / Re: Canon 5D Mark IV
« on: July 20, 2019, 02:44:48 PM »
Please do not feed the trolls!

Camera-specific discussion / Re: Canon EOS M
« on: July 20, 2019, 12:15:40 AM » -> "Your camera is not listed?" -> Last item

Camera-specific discussion / Re: Canon EOS R / RP
« on: July 17, 2019, 08:51:18 PM »
First: I'm not a moderator (and have no intention to be one, better for the forum and me).

I cannot imagine a foolproof system to avoid such messages. You will always have an amount of people not reading FAQs or unable to grab the concepts of ML development or just feeling entitled (list not complete) or really, really believing they are helping. And such issues are not exclusive to newbies.

Noise by such users is bearable IMO. In "slow" forum times like this it may appear like an increase. No need for drastic measures (again: IMO).

Camera-specific discussion / Re: Canon EOS R / RP
« on: July 14, 2019, 08:07:56 PM »

Camera-specific discussion / Re: Canon EOS M
« on: July 14, 2019, 07:12:33 AM »
And there is a reddit and Petapixel and there are DPReview forums and Miranda forums andandand. Sounds legit to open a few more, they are all clogged.

H.264 ("native" Canon video format):
Cam will stop recording at 29:59. ML is able to automatically restart the cam resulting in frame loss for about half a second. See -> Movie restart

No time limit but bandwidth restrictions making it practically impossible to record with high resolutions. Without compression, lowering bit depth and overclocking SD card interface you are stuck with 720p25. First two options are available in experimenal 4k_crop build, overclocking requires custom build. Heating up may be another issue.

Lua_fix build allows virtually endless recording. Within restrictions of HDMI-interface as implemented by Canon.

Camera-specific discussion / Re: Canon EOS M
« on: July 13, 2019, 09:56:49 PM »
To enable the card (=make it bootable again) you have to run install from that card or you have to use EOScard/MacBoot/

Camera-specific discussion / Re: Canon EOS M
« on: July 13, 2019, 07:24:32 PM »
That left me wondering if reformatting the card after installing ML was a little known secret or just good practice.

Looks like world record for long jump to conclusions is actually broken.

Camera-specific discussion / Re: Canon EOS M
« on: July 13, 2019, 12:20:19 PM »
So are you suggesting to format a card Twice? Once prior to installing ML and then again after installing ML?

Sorry, where in my answer did I suggest to format a card even once?

Camera-specific discussion / Re: ML on EOS-M2
« on: July 13, 2019, 09:41:33 AM »
Yeah, do not crosspost!

Camera-specific discussion / Re: Canon EOS M
« on: July 13, 2019, 09:38:48 AM »
Sounds like you formatted the card with a cardreader or inside a cam without ML or inside an ML cam with Q option activated -> card no longer bootable.
Easiest workaround: Reinstall ML.

Camera-specific discussion / Re: Canon 5D Mark II / 5D2
« on: July 11, 2019, 09:21:27 AM »
- Safe Magic Lantern Build (no raw video)

I suppose you mean "Stable Magic Lantern v2.3". Outdated, no longer supported and considered to be unsafe for a long, long time.

- Nightly Builds (raw video)
aka: main builds.

(and access to older builds)
Top of page -> Downloads -> Download nightly builds -> Select your cam -> Blue button bar at the bottom "Older Builds"
More compact overview (not an "official" way to access them):

I guess my question is: what 'type' of builds are now available, and where can we find them (and their older versions)?
(safe/ nightly builds/ experimental/ ...)
Main = mostly called "Nightly" -> Top of page -> Downloads
Experimental -> Top of page -> Downloads
And custom builds supported and built by danne, dfort, reddeercity (to name a few). Links found in several threads and (in most cases) in their bitbucket repositories.
Link to reddeercity's 5D2 thread

Also, on the Downloads> Experiments page it says "Therefore, it's important to give it a good try on all functions, not just Lua, so we can include it in the nightly builds." But the nightly build don't seem to have been updated in a long time, or am I missing something?

No, you got it right.

General Chat / Re: Fake SanDisk Extreme pro 64GB 95MB/S - Help needed
« on: July 10, 2019, 08:17:22 PM »
Speed integrity test: CrystalDiskMark (Windows) is mostly used. A decent cardreader is recommended. OS X/macOS may use Blackmagic Disk Speed Test.
Storage size integrity test: H2testw (Windows) or f3 (fight flash fraud) for Linux and macOS. See for details. There is a GUI available mentioned in this link: F3 X.

Most reliable source (IMO) to compare your results:

As mentioned here there is a chance a laptop's internal cardreader may be able to read card's CID.

Answered in
Top of page -> User Guide -> FAQ -> Troll Questions

General Help Q&A / Re: Dual ISO and Topaz Adjust AI
« on: July 10, 2019, 02:05:43 PM »
I suppose you're exporting your unconverted Dual-ISO files. Should be pretty easy to test by exporting the files you want to land in Topaz AI to a file/directory instead and checking those.

Camera-specific discussion / Re: Canon 750D
« on: July 10, 2019, 01:35:51 PM »
There is no ML for your cam.

General Help Q&A / Re: Canon t5 focus box
« on: July 09, 2019, 09:15:43 PM »
ML menu -> Display screen -> Clear overlays
Using HDMI and LCD at the same time is not implemented.

I described two solutions: Disabling sleep/hibernate by batch and tools triggering some event to reset sleep timer. And it's up to masc to implement some kind of system event inside MLV App as a third solution (or not).

It's just a few clicks away in Windows, too. And there are several tools for Windows just to prevent sleep/hibernation while running: Don't sleep, Caffeine, No more sleep, ...

Or something like this batch (source: stackoverflow)
Code: [Select]
@echo off
powercfg.exe -x -monitor-timeout-ac 0
powercfg.exe -x -monitor-timeout-dc 0
powercfg.exe -x -disk-timeout-ac 0
powercfg.exe -x -disk-timeout-dc 0
powercfg.exe -x -standby-timeout-ac 0
powercfg.exe -x -standby-timeout-dc 0
powercfg.exe -x -hibernate-timeout-ac 0
powercfg.exe -x -hibernate-timeout-dc 0

Scripting Corner / Re: Simulated Q Button for EOSM
« on: July 05, 2019, 07:33:56 PM »
Enter this in google:
Code: [Select]
"eos m" "q button""" = match string
site: = restrict to given location (and sub URLs)

Compressed dng is 3x compression. So you are looking at 81MB

As a1ex wrote: Depends on scene. See
*) Continuous recording for the above resolutions can be achieved as long as you can get a LJ92 compression ratio (compressed / 14-bit uncompressed) of about 50-55%, with preview set to Frozen LV (previously known as Hacked Preview) for an additional speed boost. Otherwise, you'll have to reduce the resolution or the frame rate.

The following table shows how compression rate changes with ISO and bit depth; please check the figures for your particular scene in the raw video submenu, as they can vary a lot, depending on the scene content.
Bits per pixel      14  12  11  10   9   8
ISO  100 1/100     61% 53% 50% 48% 46% 43%
ISO  200 1/200     62% 54% 51% 49% 47% 44%
ISO  400 1/400    63% 54% 51% 49% 47% 45%
ISO  800 1/800     65% 55% 52% 50% 48% 46%
ISO 1600 1/1600    67% 56% 53% 50% 48% 46%
ISO 3200 1/3200    70% 57% 53% 50% 49% 47%
ISO 6400 1/6250    76% 60% 55% 52% 50% 48%
ISO 12800 1/12500  79% 63% 57% 53% 50% 49%

I suppose you can get 33% compression rate shooting white sheets at ISO 100...
Prove me wrong and show some footage with that ratio.

Horizontal resolution x vertical resolution x bit depth x frame rate  / 8 = uncompressed data rate in Bytes/s

Because ML uses
1 MB = 1024 kB = 1024 x 1024 B
(virtually nobody uses the correct term KiB to tell binary based k (= 210 = 1024) from decimal k (= 103 = 1000) and its the same for MiB and GiB.
And that's why an empty 32 GB card is showing 29.8 GB (=GiB) available in ML's screen. Storage manufacturers are using decimal G = 1000 x 1000 x 1000 for some time (was different when I started in IT).

4096 x 1770 x 12 x 24 /8 = 249 MByte/s.
Pipe dream about required compression rate IMO.

Pages: [1] 2 3 ... 264