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.

Topics - Walter Schulz

Pages: [1] 2
I'm using an Eyefi mobi 8GB in 650D right now and feature matrix shows 650D supports this feature. Checked menus but not aware of any chances.

EDIT: Found it, I think. There should be a new menu item in Shoot tab called Eyefi Trick with some rename options to bypass Eyefi utility file transfer limitations.
Question now: Why does it not show up in dfort's latest build for 650D.105?

Some story about creating a feature film with various cameras (lots of: SONY FS700, Panasonic GH2 (hacked), SONY FS-100, Blackmagic 2.5K, Blackmagic 4K, Canon 5DMK 2 & 3, Panasonic LX100, SONY F5, Canon C300, Alexa Mini) and getting a consistent "look" despite of it.
German only, sorry!

Having an itch because of placement of benchmarks (esp. Card benchmarks), file manager and shutter count in Debug tab.
What about
1) a UTIL tab and
2) hiding Debug tab by default? Most users don't care about Debug tab and with a reason.

Benchmarking a card in cam: Householding duty IMO (yes, I'm a sysadmin).
Filemanager: Necessary to play MLV ... why hide it in Debug?
Shutter count: Some people advise to install ML for the very reason. Lookup some forum posts elsewhere, I'm kidding you not!

General Help Q&A / Q about ML menu layout: Colours, shapes ...
« on: March 15, 2018, 03:43:11 PM »

I'm a little bit confused about ML menu design:
1.) Icon colour "blue": In Expo menu there are several items showing blue squares. I thought blue stood for ML settings interfering with Canon menu settings. White balance, ISO, Shutter, Aperture Picture Style: When changed in Canon menu it will be shown in ML menu and other way round.
But in MLV lite submenu (Movie -> RAW video -> Q) there are blue icons for Resolution, Aspect Ratio, Data format and others. None of these settings exist in Canon menu. Either my premise is wrong or the buttons have wrong colour. EDIT: Well, some kind of Aspect Ratio does exist on some EOS cams but there is no interaction.
2.) Circles and squares: What is the difference?
3.) Submenus/dropdown: Accessing Global Draw settings by pressing Q or SET opens "dropdown style" options to select from. Others like Ghost image open a window style select with a single entry to toggle ON and OFF. Why two different menu styles?
4.) Triangle icon. Used to start an action ("Play Button") and used show/hide menu options. Seen in MLV lite submenu: Playback will start playback and Advanced ... will show hidden items. Not that great IMO.

Minor issue: "Magic Zoom" but "False color". What is ML's take on capitalization?

General Chat / UHS-I 160 MB/s?
« on: February 27, 2018, 08:50:55 AM »
In other news Western Digital/Sandisk introduced another 400 GB UHS-I card with a new SD-card definition called A2 (setting standards for minimal IOPS, defined and documented by SD Association).
Marketing hot air galore:

The thing puzzling me is alleged transfer speed well beyond UHS-I SDR104 definition (104 MB/s): 160 MByte/s.
According to WD/Sandisk you will need a (new?) cardreader able to support this mode.

Never heard about this mode before and unable to find anything resembling a technical specification. Grateful for any hints and - cream on top - about existing devices other than cardreaders able to do 160 MByte/s.


Starting yesterday at home (Telekom DSL) I got the message about 90 second timeout for this IP. Retrying I got a mix of this message and the information I already sent this item.
No post to be seen. Closed edit and hit Reply again, edited reply and hit Post -> Post sent.
Today connected to a *huge* public access point I got this message mix, too. Different PC, though.

Using Firefox ESR 52.5.3 (64-Bit).
Anything going on behind the curtain?

Encountered a bug with EOS Utility and activated MLV/RAW in movie mode for 7D. Working with 650D, though.
Please test your model and reply here.
A1ex expects Liveview broken in 5D2, 50D, 500D, 550D, too.
Should be working in 5D3, 6D, 60D, 70D, 100D, 600D, 700D, 100D, 1200D.

- Load any MLV or REC record module. Don't activate MLV/RAW in movie tab.
- Run EOS Utility and connect cam to PC via USB.
- Activate Liveview option in EOS Utility.
-> EOS Utility will show Liveview as expected.

- Disconnect USB and activate MLV/REC option in movie tab.
- Run EOS Utility
- Connect cam to PC via USB and try to establish Liveview.
-> Liveview button will not work as expected. -> [Fail]
-> Liveview is working -> [Pass]

Please run test and submit results.

Cam       Liveview

5D2        [?]
5D3        [Pass]
6D          [?]
7D          [Fail]
50D        [Fail]
60D        [?]
70D        [?]
100D      [?]
500D      [?]
550D      [?]
600D      [?]
650D      [Pass]
700D      [?]
1100D    [N. A.]
1200D    [?]
EOS M    [?]

General Chat / 5DSr video on YT ... recorded with ML in 4K slow motion ...
« on: September 13, 2017, 05:54:54 PM »
... just BS or forgetting which cam he/she used?

Hello, out there!

You may have wondered what I'm up to with those postings:;topicseen#msg189627;topicseen#msg189640

Sorry (kind of), TL;DR follows now.
For long time readers it may not come as a surprise: I'm not exactly a friend to sloppy and outdated tutorials (video and text) spread all over the place. ML gives the community wonderful enhancements for free but there is something to be desired concerning documentation. Progress on help texts seems to be stalled. And dreaming of something like "ML 101" - and keeping it up-to-date with devs constantly pushing cam's abilities to unknown shores ...
Audionut put effort in collecting help text but using forum posts doesn't look promising to me in terms of long time support.
How to get out of this mess?
Well, devs have tools for collaborative work and peer reviews. I think it's far from perfect suited for this need but it is there and - I hope - it's useable for non-devs.

That's what I did:
1) Put up a topic I wanted to write about a long time (but doesn't interfere with help text content) and put it into a forum post (using bbcode bells and whistles Audionut pointed me to. Not necessary but making navigation in long posts much easier). THat's the german one.
2) Transfered the "code" to my Bitbucket repository -> Posting
3) Used to auto-translate (yes, with most obvious errors) to create -> Auto-Translate
4) Transfered contents to second forum post (the germish/autotranslate one)

What to do now? Master plan:
-> Find someone (or more people) willing to translate "germish/autotranslate" using Bitbucket branching and pull requests to get a version not so germish. And maybe some suggestions concerning layout, structure, contents ....
-> (If available) ask for peer review.
-> Declare "english" version to be fresh and to be "master document". All further changes will take place in this document first.
-> Transfer content to forum post (replacing previous post).
-> Transfer changes to german document
-> Ask for translators willing to transfer document into other languages.

What do you think? Too much? Too complicated? Too little? Wrong approach? Sounds good, doesn't work ... forget that, please ...

PS: If you want horsing around with bbcode and stuff: I'm running SMF inside a virtual machine. Just download VM file from Bitnami, change database (via web interface in v14) to UTF-8 and Bob is your uncle.

EDIT: Well, you may have a laugh. Explanation follows:
Do *not* reply here (WIP) -> PN


1 Introduction and Summary

2 Flash card Fraud

2.1 Card Speed Fraud

2.1.1 Benchmark (Windows)
2.1.2 Benchmark (OS X/MacOS)

2.1.3 Benchmark using Camera

2.2 Card Capacity (Size) Fraud

2.2.1 Detecting Capacity Fraud (Windows)
2.2.2 Detecting Capacity Fraud (OS X/macOS) f3read/f3write F3X

1) Introduction and Summary

ML places demands on the memory cards that were unpredictable for Canon and that go far beyond the bandwidth required by the manual. Unfortunately, counterfeit products are widespread in flash memories. These can lead to performance problems (premature interruption of the recording) and irreparable data loss.

This text explains what kind of counterfeits exist and how to detect counterfeit products.

2) Flash Card Fraud
More often than we would like to be, flash memories are affected by product counterfeiting. Estimates are based on figures of more than 20 percent. Even reputable dealers are not immune to these scams, as the course of business does not provide for checking tickets before they are sold. Therefore, we advise you to test the cards yourself after purchase.

There are 2 types of counterfeiting which can also occur together. The counterfeiting method is relatively well known to pretend a higher data transfer rate than expected by means of an incorrect label. This leads to an unplanned interruption of the recording when the data rate is exhausted (e. g. with RAW video). It is relatively unknown that there is another type of counterfeit, in which the computer is pretended to have a higher memory size. This case is not so obvious, but in case of an error it can lead to the irretrievable loss of data!

2.1 Card Speed Fraud
For the counterfeiters, it is lucrative to indicate a higher transfer rate on the label than actually exists, as cards with a higher data rate are considerably more expensive. For the user, there is no easy way of reliably detecting the writing and reading speed with operating equipment. For Windows and OS X/MacOS there are free add-ons for this purpose. The associated term is "benchmark".

For the purpose of testing whether the memory card you have purchased meets the specifications, I believe there are a few conditions:
An internal or external card reader that can also exploit the speed of the card. It's z. For example, there is no point in using a card reader connected to USB 2.0 if the transfer rate of the memory card exceeds the speed of USB 2.0. USB 2.0 is theoretically capable of transmitting 60 MByte/s. In practice, with luck you get values of 48 MByte (plus/minus x).

Special care is recommended for CF cards that conform to the "UDMA 7" standard. Card readers that do not master UDMA 7 can destroy these cards!

(On you will find a selection of tested card readers.

The computer should not be under high load by other applications for this task. Open applications are not a problem in themselves, but if the processor is busy with other tasks, no reasonable benchmark results are to be expected.

Keep your eyes open. A slight deviation between benchmarks on different computers is normal.

2.1.1 Benchmark (Windows)
CrystalDiskMark "is a popular program.

For the maximum data rate, the test "Seq" (sequential reading and writing) is sufficient.

EDIT: Well, great! Who was convinced that all the snapshots necessary for the text were on this computer and not on the computer that is 1,124 km away from the crow flies?

So there is data for the stick...

2.1.2 Benchmark (OS X/MacOS)

A popular program is the "Blackmagic Disk Speed Test", available at the Apple Retail Store.

<Fensterbild BDST>

2.1.3 Benchmark using Camera

ML has its own benchmark program. It's a so-called Module (Bench. mo), which can be loaded via the "Modules" tab.

After restarting the machine, it is then ready for use in the "Debug" tab. For the card test, select Card Benchmarks -> Quick R/W benchmark (1 min).

<Snapshot Benchmark>

Of course, ML must be installed on the card.
To determine the maximum possible transfer rate for the card under ML, I recommend the photo mode without additional activated modules.
Sufficient free space (> 2 GB) on the card. ML does not check whether the space required for the benchmark is available. If there is not enough free space, the Benchmark produces fantasy values!
I recommend to carry out this test even if the card reader test is in the green area. In very rare cases, there are compatibility problems between camera and card that lead to drastic performance degradation (independent of ML).
This test cannot achieve the maximum possible transfer rates for very fast cards that are possible with decent card readers! One of the reasons can be the bandwidth of the integrated card connection.

2.2 Card Capacity (Size) Fraud
With this scam, the card pretends to have a higher storage capacity than actually available. So instead of z. For example, with the actual 8 GB available, the card presents itself with 64 GB of storage space. The dangerous thing is that when writing over the real memory area, the card is *overwritten* from the beginning. This leads to irretrievably lost data!
The operating system of the computer and camera have no way to detect this fraud. You assume that the physical memory size information provided by the card is correct.
To detect the fraud, there are programs for Windows/OS X/MacOS that describe the card for testing and then determine whether the data was written correctly.

2.2.1 Detecting Capacity (Size) Fraud (Windows)
For Windows there is the program h2testw, which works with English and German user guidance.
In principle, the test works non-destructively. No existing data will be overwritten if no fraudulent card is available.

Please note that this test can take a long time! And the achievable read/write speed is about 2/3 of what benchmark programs use. Testing a 128 GB card takes about an hour with fast CF cards (1066x).

And the test data will not be deleted by the program, you have to do this yourself! The files with the name *. h2w are located on the top directory level (root) of the map.

2.2.2 Detecting Capacity (Size) Fraud (OS X/macOS)

The implementation for Apple computers was developed F3. F3 = FFF = Fight Flash Fraud = Fight Flash Fraud.

In principle, the test works non-destructively. No existing data will be overwritten if no fraudulent card is available.
Please note that this test can take a long time! And the achievable read/write speed is about 2/3 of what benchmark programs use. Testing a 128 GB card takes about an hour with fast CF cards (1066x).

And the test data will not be deleted by the program, you have to do this yourself! f3read/f3write
f3read and f3write are open source programs for the terminal (aka: command line, CLI).

Don't worry, but the programs are available in source code and must be compiled before use. Just go, if you have done it once, the instructions are available on the website. If you absolutely do not want to or cannot compile: -> F3X F3X
There is a program derived from f3read/f3write with a user interface called F3X and it is also available as an installable package.

Do *not* reply here (WIP) -> PN
Masterplan explained here:

1 Einführung und Überblick

2 Produktfälschungen bei Flash-Speicherkarten

2.1 Falsche Geschwindigkeitsangabe

2.1.1 Benchmark unter Windows
2.1.2 Benchmark unter OS X/MacOS
2.1.3 Benchmark in der Kamera

2.2 Falsche Speichergröße

2.2.1 Falsche Speichergröße unter Windows erkennen
2.2.2 Falsche Speichergröße unter OS X/macOS erkennen f3read/f3write F3X

1) Einführung und Überblick
ML stellt an die Speicherkarten teilweise Anforderungen, die von Canon so nicht vorhersehbar waren und die weit über die laut Handbuch benötigten Bandbreiten hinausgehen. Leider sind Produktfälschungen bei Flash-Speichern weit verbreitet. Diese können im Einsatz zu Performance-Problemen (vorzeitigen Abbrüchen der Aufnahme) und nicht behebbaren Datenverlusten führen.
Dieser Text erklärt, welche Art von Fälschungen existieren und wie man Produktfälschungen entdecken kann.

2) Produktfälschungen bei Flash-Speicherkarten
Häufiger als uns lieb sein kann, sind Flashspeicher von Produktfälschungen betroffen. Schätzungen gehen von Zahlen über 20 Prozent aus. Auch als seriös bekannte Händler sind vor diesen Betrügereien nicht gefeit, da es der Betriebsablauf nicht vorsieht, Karten vor dem Verkauf zu prüfen. Daher sind wir gut beraten, Karten nach dem Erwerb selbst zu testen.
Es kommen 2 Fälschungsarten vor, die auch zusammen auftreten können. Relativ weit bekannt ist die Fälschungsmethode, durch ein falsches Etikett eine höhere Datentransferrate als erwartet vorzuspiegeln. Dies führt dann beim Ausreizen der Datenrate (z.B. bei RAW-Video) zum ungeplanten Abbruch der Aufnahme. Relativ unbekannt ist, dass eine weitere Fälschungsart existiert, bei der dem Rechner eine höhere Speichergröße vorgespiegelt wird. Dieser Fall ist nicht so offensichtlich, kann im Fehlerfall aber dazu führen, dass Daten unwiederbringlich verloren gehen!

2.1 Falsche Geschwindigkeitsangabe
Für die Fälscher ist es lukrativ, eine höhere Transferrate auf dem Etikett anzugeben als tatsächlich vorhanden, da Karten mit hoher Datenrate deutlich teuerer sind. Für den Anwender besteht mit Betriebsmitteln keine einfache Möglichkeit, die Schreib- und Lesegeschwindigkeit verläßlich zu erkennen. Für Windows und OS X/MacOS gibt es für diesen Zweck erstellte kostenlose Zusatzprogramme. Der zugehörige Begriff ist "Benchmark".

Für den Test, ob die erworbene Speicherkarte den Spezifikationen entspricht, gelten - meiner Ansicht nach - ein paar Voraussetzungen:
   - Ein interner oder externer Kartenleser, der auch die Geschwindigkeit der Karte ausreizen kann. Es ist z. B. sinnlos, einen mit USB 2.0 angebundenen Kartenleser zu verwenden, wenn die Transferrate der Speicherkarte die Geschwindigkeit von USB 2.0 überschreitet. USB 2.0 ist theoretisch in der Lage, 60 MByte/s zu übertragen. In der Praxis kommt man mit Glück auf Werte von 48 MByte (plus/minus x).
   Bei CF-Karten, die dem Standard "UDMA 7" entsprechen, ist besondere Vorsicht angeraten. Kartenleser, die nicht UDMA 7 beherrschen, können diese Karten zerstören!
   (Auf findet man eine Auswahl an getesteten Kartenlesern.)
   - Der Rechner sollte für diese Aufgabe nicht unter hoher Last durch andere Anwendungen stehen. Offene Applikationen sind an sich kein Problem, aber wenn der Prozessor mit anderen Aufgaben ausgelastet ist, sind keine vernünftigen Benchmark-Ergebnissen zu erwarten.
   - Augenmass wahren. Eine geringe Abweichung zwischen Benchmarks auf verschiedenen Rechnern ist normal.

2.1.1 Benchmark unter Windows
Als verbreitetes Programm gilt "CrystalDiskMark".

Für die maximale Datenrate reicht der Test "Seq" (Sequentielles Lesen und Schreiben).

EDIT: Na, super! Wer war wohl felsenfest davon überzeugt, alle für den Text notwendigen Snapshots auf diesem Rechner zu haben und nicht auf dem Rechner, der 1.124 km Luftlinie entfernt ist?
Also gibt es Daten für den Stick ...

2.1.2 Benchmark unter OS X/MacOS
   Als verbreitetes Programm gilt Blackmagic Disk Speed Test", das im Apple Store verfügbar ist.

2.1.3 Benchmark in der Kamera
   ML hat ein eigenes Benchmark-Programm. Es ist ein sog. Modul (, das über den Reiter "Modules" ladbar ist.

Nach Neustart der Maschine steht es dann im Reiter "Debug" zur Anwendung bereit. Für den Kartentest die Option Card Benchmarks -> Quick R/W benchmark (1 min) wählen.

- Natürlich muss ML auf der Karte installiert sein.
- Um die maximale mögliche Transferrate für die Karte unter ML zu ermitteln, empfehle ich den Foto-Modus ohne zusätzlich aktivierte Module.
- Ausreichend freier Speicherplatz (> 2 GB) auf der Karte. ML prüft nicht nach, ob der für den Benchmark notwendige Platzbedarf vorhanden ist. Bei unzureichendem freien Platz produziert der Benchmark Phantasiewerte!
- Ich empfehle diesen Test auch dann durchzuführen, wenn der Test am Kartenleser im grünen Bereich liegt. In sehr seltenen Fällen gibt es Kompatibilitätsprobleme zwischen Kamera und Karte, die zu drastischen Performance-Einbrüchen führen (unabhängig von ML).
- Dieser Test kann bei sehr schnellen Karten nicht die maximal mögliche Transferraten erreichen, die mit anständigen Kartenlesern möglich sind! Einer der Gründe kann die Bandbreite des integrierten Kartenanschlußes sein.
- Der kamerainterne Benchmark hat 2 Durchläufe. Im 2. Durchlauf zeigt sich, wie stark sich die Erwärmung durch die Schreib-/Lesevorgänge auf die Transfergeschwindigkeit auswirkt. Sollte sich ein signifikanter Zuwachs der erwärmten Karte zeigen, kann man sich z. B. die Option "Card Warm-up" im Untermenü "RAW video (MLV)" anschauen.

2.2 Falsche Speichergröße
Bei diesem Betrug spiegelt die Karte vor, eine höhere Speicherkapazität zu haben als tatsächlich vorhanden. Also statt z. B. mit den tatsächlich vorhandenen 8 GB stellt sich die Karte mit 64 GB Speicherplatz vor. Das gefährliche dabei ist, dass beim Schreiben über den real vorhandenen Speicherbereich die Karte von Anfang an *überschrieben* wird. Dies führt dann zu unwiederbringlich verlorenen Daten!
Das Betriebssystem von Rechner und Kamera haben keine Möglichkeit, diesen Betrug zu erkennen. Sie gehen davon aus, dass die von der Karte gelieferten Angaben über die physikalische Speichergröße korrekt ist.
Um den Betrug zu erkennen, gibt es Programme für Windows/OS X/MacOS, die zum Test die Karte beschreiben und danach ermitteln, ob die Daten korrekt geschrieben wurden.

2.2.1 Falsche Speichergröße unter Windows erkennen
Für Windows existiert das Programm h2testw, das mit englischer und deutscher Bedienerführung arbeitet.

Der Test arbeitet im Prinzip nicht-destruktiv. Es werden keine bestehenden Daten überschrieben, wenn keine betrügerische Karte vorliegt.
Bitte unbedingt beachten, dass dieser Test sehr lange dauern kann! Und die erreichbare Schreib-/Lesegeschwindigkeit beträgt etwa 2/3 dessen, was Benchmarkprogramme verwenden. Eine 128 GB-Karte zu testen, dauert bei schnellen CF-Karten (1066x) schon mal ein Stündchen.
Und die Testdaten werden vom Programm nicht gelöscht, dies muss man selbst tun! Die Dateien mit Namen *.h2w befinden sich auf der obersten Verzeichnisebene (Root) der Karte.

2.2.2 Falsche Speichergröße unter OS X/macOS erkennen
Die Umsetzung für Apple-Rechner wurde F3 entwickelt. F3 = FFF = Fight Flash Fraud = Bekämpfe Flash-Betrug.

Der Test arbeitet im Prinzip nicht-destruktiv. Es werden keine bestehenden Daten überschrieben, wenn keine betrügerische Karte vorliegt.
Bitte unbedingt beachten, dass dieser Test sehr lange dauern kann! Und die erreichbare Schreib-/Lesegeschwindigkeit beträgt etwa 2/3 dessen, was Benchmarkprogramme verwenden. Eine 128 GB-Karte zu testen, dauert bei schnellen CF-Karten (1066x) schon mal ein Stündchen.
Und die Testdaten werden vom Programm nicht gelöscht, dies muss man selbst tun! f3read/f3write
f3read und f3write sind Open-Source-Programme für das Terminal (aka: Kommandozeile, CLI).

Nicht erschrecken, aber die Programme liegen im Source-Code vor und müssen vor der Verwendung selbst kompiliert werden. Geht einfach, wenn man es mal gemacht hat, die Anleitung gibt es auf der Webseite. Wer absolut nicht kompilieren will oder kann: -> F3X F3X
Es existiert ein von f3read/f3write abgeleitetes Programm mit Benutzeroberfläche namens F3X und es steht auch als installierbares Paket zur Verfügung.

Found something about an automatic translator in a German IT-news aggregator (Golem) which may be usefull for foreign readers having troubles reading/understanding English language and review sounds too good to be true. I tested it using an article found in an Italian newspaper and ... well ... it's amazingly different from Google Translate because translation makes sense. It's called DeepL and offers translations from/into English, French, Spanish, Italian, Dutch, Polish und German. Other languages will be added, according to Golem.

May I ask for some native french, italian, spanish reader to test if - at least - it works well for english and your native tongue?

Apps for iOS and Android are announced.

General Chat / Magic Lantern Book will be released this autumn?
« on: June 14, 2017, 06:38:33 PM »

Somehow it went under my radar: An announcement for a book covering Magic Lantern. Release date 10/2017 (well, it was to be released in 2016 ...).
German author Martin Schwabe has written some helpful stuff about ML in and for magazine "c't Digitale Fotografie" issue 05/2015. He got some things wrong (IMO), though and I took the liberty to write something about it in this forum.
Don't know if he is going to cover nightly builds now (nope, he covered "stable" until now).
I'm sceptical about the plan to cover ML in print. Either he covers outdated "stable" or must take a stand and will not be able to keep up with developer's take on April Fools Day (and other newer developments).
My 2 cents, of course.

@dpunkt-verlag: Ihr könntet ja mal g3gg0 kontaktieren, was er für inhaltliches Gegenlesen angemessen hält.

General Chat / Obituary: 7D
« on: April 07, 2017, 07:32:40 PM »
During today's outdoor shooting in cold weather my 7D stopped working.
Replacing battery doesn't help and there was no sign of electrons floating.
Diagnostic autoexec.bin didn't work either.

It took long to get ML for this cam and now it ends.

The cam is survived by 350D and 650D.

General Chat / April Fools Day prank. Put it down or go with it?
« on: March 28, 2017, 08:10:12 PM »
Hello, fellow regulars!

April, 1st is about to land and regulars know what will happen. As a german, known to "go to the cellar for laughing" and a master there I'm not exactly a friend of this running gag.
A short step away of rising a pull request to get rid of it I hereby ask regulars about their opinion on this.

Feature Requests / MLV file generator for benchmarking/baselining
« on: February 21, 2017, 08:37:35 AM »
Abstract: Generates valid MLV files. Output file size adjustable.

Purpose (in short):
1. Baselining
2. Benchmarking
3. Pre-Flight testing

This tool will generate MLV files with adjustable file sizes. Main purpose is using output files for testing own equipment's performance/function without generating footage files or transfering real big files via internet on site.
Secondary: Can be used to build up a list comparing different PC architectures. Example is/was Gigapixel Speedtest (defunct).

G3gg0, what do you think about it?

PS: Links to defunct Gigapixel Speedtest

Feature Requests / "Pokémon Go" overlay
« on: July 17, 2016, 10:00:24 PM »
I hereby ask to implement a Pokémon Go overlay in liveview and movie mode.

(S)CNR and it has to be asked once. Nope, not into Pokémon at all ...

Could be wrong but looks like ITA (Information Technology Agreement) expansion eliminates tax tariffs for cameras/camcorders. In other words: Camera manufacturers all over the world don't have to limit recording times to 29:59 anymore to avoid cams treated as camcorders (= add tax). Effective July, 1st.
See Item 080 in attachment A:
"080, 852580, Television cameras, digital cameras and video camera recorders "

General Development Discussion / Linking a pic stored in Bitbucket?
« on: June 23, 2016, 10:35:43 AM »
Couldn't find a working solution for this one.
- Pic file stored in Bitbucket/Mercurial.
- Want to link it into a forum post (BBCODE or else). Not just as a download link (which works) but displaying the file's content.

Should be doable in GitHub, though.
Any help appriciated!

General Chat / "Official" ML intro for ML video tutorials?
« on: June 17, 2016, 02:58:28 PM »
We already have a ML logo.
Do we have some sort of intro (animation or else, ML jingle) for video tutorials?

Feature Requests / Level Indicator: Menu location and layout
« on: April 12, 2016, 10:06:13 PM »
May I suggest to get "Level Indicator" moved to "Overlays"? Right now it's located in Display for whatever reasons.

And I have a hard time with those thin lines turning green on 7D. May I opt for thicker lines and some sort of animation effect if alligned?

Scripting Q&A / Canon settings not saved with camera.reboot
« on: April 03, 2016, 11:50:29 AM »
Hi, Dan and Gerry!

Using "camera.reboot" cam settings will not be saved under certain circumstances.
Reproduced in 7D and 650D. April, 1st build + tonights

How to reproduce:
Photo mode M.
Open Canon settings screen by pressing Q button.
Select WB settings and change using wheel.
Now press Half Shutter to exit.
Open ML screen by pressing trashcan button.
Run Lua script with "camera.reboot".

After reboot open Canon settings and check WB setting: Change undone.

After changing WB exit screen by pressing Q.
-> Setting persistent after "camera.reboot".

Script used:
Code: [Select]
-- Unsophisticated reboot (Modules)

function main()

keymenu =
    parent = "Modules",
    name = "Reboot",
    help = "Reboots cam. Will not ask for confirmation!",
    select = function(this) task.create(main) end,

WB is not the only setting affected. But it is one of the settings reproducable on both cams.

How to prevent this? Which function/command will force settings to be stored before "camera.reboot"?

Magic Lantern Forum and Site Discussion / Just a little test ...
« on: March 15, 2016, 06:37:04 PM »
... how to bypass IP logging.

General Help Q&A / gphoto2: "Segmentation fault 11" trying to upload file
« on: February 24, 2016, 09:18:17 PM »

Followed this instruction to make gphoto2 work on Hackintosh (El Capitan).
Was able to delete files but file copy PC->Cam gives "Segmentation fault 11" on 650D and 7D. I heard about PTP not being the world's most trustworthy protocol but ...
Well: Anyone out there making it work?


EDIT: Dang! Wrong forum. Should be General Chat, of course.

Pages: [1] 2