Messages

26

Hardware and Accessories / Re: Compiled list of card speeds

« on: October 15, 2019, 06:11:02 PM »

A Micro-SD adapter contains just a few millimeters wire. Doesn't offer a lot of opportunity to mess things up IMO and according to my limited experience ...

27

General Chat / Re: How many people would like to donate?

« on: October 14, 2019, 05:07:25 PM »

Against it: This is just "testing the water" and as such I think message and response came through and there is enough data for a1ex to come closer to a decision.

Really think it would be more effective/efficient not to make much noise now:
- a1ex made clear legal advice is paramount. Potential showstopper.
- We cannot offer a strategy right now. No straightforward way to spend money *now* for those who are interested. I think it is more likely to let people of the hook and/or frustrate them by splitting "noise" into a non-formal inquiry and - some time after - asking them to put their money where there mouth was some time ago.

28

Camera-specific discussion / Re: ML on EOS-M2

« on: October 14, 2019, 11:02:28 AM »

According to an unverifiable source around 30 percent of all SD-cards offered by non-official dealers are faked.
If you purchase a card from such a source a thorough after-buy check is mandatory (in all other cases highly recommended).

Check for faked speed specification:
- Fast cardreader + PC + a benchmark program like CrystalDiskMark (Windows) or Blackmagic Disk Speed Test (macOS).
  You only need to run sequential R/W. Compare with benchmark runs from reliable sources like www.cameramemoryspeed.com
 
Check for faked capacity number:
- Cardreader + PC + h2testw (Windows) or f3/F3 QT (macOS)
  If capacity info is altered by some crook you will get serious data corruption because cam will overwrite data recorded previously if physical storage limit is reached. Cam's firmware (and your PC, too) rely on card's info set to be correct and will not check if data set numbers and reality match.

29

Camera-specific discussion / Re: Canon 5D Mark II / 5D2

« on: October 13, 2019, 01:52:49 AM »

As of today ML does not offer that much to avoid Canon's ways of generating mushy H.264 output.
Sorry, explaination doesn't go without ML lingo:
5D2 in this mode does (as all ML supported cams but 5D3) line skipping/row binning. Means: Only every third sensor line is used in movie mode. This rises the risk of getting moiré. And this means cam does not record 1920x1080 but 1880x1058 (if I got it right). To fight moiré sensor's anti-aliasing filter won't help much because it is designed for photo mode. Therefore electronic filters are responsible for softening the image to fight aliasing, add some noise reduction, blowing it up to 1920x1080. This is done by dedicated hardware we don't know much about.
For H.264 ML can only enhance ISO performance a bit, allow shutter timing fine-tuning and some more (Dual-ISO, HDR, ...). But H.264 sharpness in general is not in ML's hands.

Lookup http://www.mosaicengineering.com/products/vaf/5d2.html

RAW/MLV on the other hand ...

30

General Chat / Re: How many people would like to donate?

« on: October 12, 2019, 10:52:57 AM »

That would be a large one-off expense spent on a single developer.

So what? I will not be surprised if the only person having a problem with that will be you ... ;-)

The majority of these donations are from years ago - what are we going to do afterwards?

Let's cross that bridge when we come to it ...

(Most likely it will work the same way as before: There was money resting and nobody cared. If there is no money nobody will care.
Edit: Oh, your revenue service will do...)

31

General Development Discussion / Re: The MLV format

« on: October 11, 2019, 10:17:32 PM »

Please compress this file. It doesn't need 6 MByte to show what you want us to see and mobile users data plans will suffer.

32

Hardware and Accessories / Re: Compiled list of card speeds

« on: October 11, 2019, 09:48:42 PM »

Current card SanDisk Extreme 80MB/s U-1 Class-10 64GB (SDHC card)

Picture, please!
Pretty sure there is no card matching this description. "U-1" does not exist, it's either UHS-I (interface type) or U3 (UHS speed class). If it is indeed U1 you should get a faster card easily ...
"U-II" does not exist either. Because there is no U2 designation it can be determined you meant to write UHS-II. But there is no Sandisk card with UHS-II interface and 95 MB/s written on label.

Cam's card interface is SDR50 or DDR50 -> 50 MByte/s transfer rate (theoretical). With overclocking we get transfer rates above 65 MByte/s (benchmark only, not possible in RL recording) compared to about 38 MByte/s write rate for continuous recording.

Do yourself a favor and benchmark your card with a decent cardreader and programs like CrystalDiskmark (Windows) or BlackMagic Disk Speed Test (macOS).

Browse www.cameramemoryspeed.com for some benchmark numbers. For UHS-II cards you have to find out which cardreader does not support UHS-II to get the numbers for UHS-I compatibility mode.

33

General Chat / Re: How many people would like to donate?

« on: October 11, 2019, 06:14:47 PM »

Has Canon ever "gotten mad" before?

Offtopic and IMO: "Before" implies Canon is mad now. Cannot follow this conclusion.

34

Camera-specific discussion / Re: Canon EOS M

« on: October 10, 2019, 07:24:01 AM »

There is no generic firmware for Canon cameras. A firmware fits exactly for the camera type it was designed to fit and nowhere else. ML project does not alter Canon firmware files.

An ML build for a camera fits exactly for that cam *and* a designated firmware version. If there is a new firmware version published you can't use ML created for the previous firmware version.

If we talk about "EOS M" this does *not* mean we talk about all cameras with an EF-M mount. From a programmer's viewpoint each cam type is unique.

And M10 won't be covered by ML project (highly unlikely) because it runs on code for the PowerShot series. Which is CHDK's area: https://chdk.fandom.com/wiki/M10

35

HDR and Dual ISO Postprocessing / Re: Lightroom plugin cr2hdr v3.0 DEV (WIP)

« on: October 09, 2019, 11:29:51 AM »

The question is if you have the latest plug-in version:
https://bitbucket.org/kichetof/lr_cr2hdr/downloads/
Replace plug-in's cr2hdr with your version.

Computer's OS version?

36

General Help Q&A / Re: Canon 600D Flash Live View

« on: October 09, 2019, 08:06:58 AM »

I suppose you already tried
Shoot tab -> Flash tweaks -> 3rd p. flash LV

37

Shoot preparation / Re: 550D

« on: October 08, 2019, 05:40:47 PM »

Sentence missing at least a verb.
Please clarify!

38

General Help Q&A / Re: Need Help to decide what to get T5i or T7i

« on: October 08, 2019, 05:37:28 PM »

You know there is no ML for T7i/800D?

30 minute limit an issue or not?
Are you vlogging from home (or other static environment) or are you doing videos moving around? Means: Is autofocus an issue or not?
Do you want to record to card or stream via HDMI?

39

Camera Emergency Department / Re: 60d can it be fixed?

« on: October 08, 2019, 05:05:16 PM »

Remove battery, insert card, insert battery, close compartment lids.
If it doesn't work:
Remove battery, insert card into cardreader, backup and delete contents in ML\Settings dir. Insert card, insert battery, close lids and report back.

40

General Help Q&A / Re: Why Can't I Shoot Raw on Canon 700D (Magic Lantern)?

« on: October 08, 2019, 04:47:42 PM »

Some of your issues have been properly answered in Reddit https://www.reddit.com/r/MagicLantern/comments/des095/why_cant_i_shoot_raw_on_canon_700d_magic_lantern/

If you're running "standard/main" nightly build (last official build: magiclantern-Nightly.2018Jul03.700D115) and want to get continuous recording upper limit is somehow 720p25 (1280x720 pixel, 25 fps). That will require about 38 MByte/s bandwidth in 14 bit raw and it is "cropped".

You can try an experimental build (latest official: magiclantern-crop_rec_4k.2018Jul22.700D115.zip) with lossless compression:

EOSM, 650D, 700D, 100D:

•     1736x696 @ 50/60p with 3x3 pixel binning (actually column binning / line skipping)
•     Lossless compression: 1736x976 @ 24p continuous (this is the maximum 16:9 resolution with 3x3 sampling)

There is a very bleeding edge custom build available in Danne's Bitbucket repository: http://bitbucket.org/Dannephoto/magic-lantern/downloads
If I'm right it offers a SD-card overclock which gives extra boost for recording with a risk of getting your card fried.

But you need a faster card. Undisputed champ for 700D (and other Digic 5 cams with SD slot): Sandisk Extreme Pro 95 MB/s. Sandisk 160/170 MB/s seems to be a tad slower but haven't caused a problem (yet).
Seems to be pure overkill but if you want to play safe ...
We simply have not enough experience with other (cheaper) cards in this performance class to offer worthy and cheaper replacements.

"Clean" footage is a bit disputable.
Non-crop with binning/line-skipping is prone to aliasing. Quite expensive VAF anti-aliasing filter is able to fight this but will be restricted to full-screen setting only.

And to answer a question not asked: Nope, nobody here made a statement about RAW with ML being straightforward.

41

Tutorials and Creative Uses / Re: Firmware Update/Downdate?

« on: October 04, 2019, 08:51:51 PM »

Haven't you read? Canon CPS is able to downgrade your cam. Depending on your support status (CPS membership or not) you may be charged or not.

42

General Help Q&A / Re: Dual ISO interpolation - really low resolution

« on: October 04, 2019, 08:20:40 AM »

No proper input -> Unable to reproduce -> no thoughts.

43

Camera-specific discussion / Re: Canon EOS R / RP

« on: October 04, 2019, 08:15:09 AM »

Get yourself a cam suitable for your needs.

44

Tutorials and Creative Uses / Re: Firmware Update/Downdate?

« on: October 03, 2019, 10:15:08 PM »

Never heard about people getting problems with support because of ML. Most users are unaware of the bootflag (which is easily detectable by support) giving away cam being "MLed".

@a1ex: Can you add some text regarding this downgrade option into Twitter and install instructions?

45

General Help Q&A / Re: Is one shorter camera-card-slot pin an issue for RAW recording?

« on: October 01, 2019, 11:36:44 PM »

Sorry, I gave wrong information! Pins of a CF connector should indeed vary in length (according to specs, for example 2.0):
1, 13, 38, 50 (power pins): 5 mm
25, 26 (detect): 3.5 mm
all other: 4.25 mm

46

General Help Q&A / Re: Is one shorter camera-card-slot pin an issue for RAW recording?

« on: October 01, 2019, 07:35:17 PM »

Pins should not be of different length and operation may suffer (or not) depending on pin's designation in short/medium/long time (after additonal wear and tear) or never. There are pins transfering picture data and there are other pins controlling card's status/data transfer and there are power supply pins.
Maybe some info about which pin is affected would be helpful...

Worst case: Card slot replacement is not unheard of. Any soldering wizard able to fix a modern mobile phone will do it with reasonable costs.

47

General Help Q&A / Re: Upgrading from ancient version pre0.2.2

« on: September 30, 2019, 11:17:27 PM »

Backup those files first. Then proceed as you described.

48

Tutorials and Creative Uses / Re: Firmware Update/Downdate?

« on: September 29, 2019, 11:55:15 AM »

Good! A1ex has a ROM dump from a working cam.
Let us hear if there is anything to do for non-coders like me.

49

Tutorials and Creative Uses / Re: Firmware Update/Downdate?

« on: September 29, 2019, 11:22:46 AM »

@Danne & dfort:
Would a spare 5D3 in your hands help?

50

Tutorials and Creative Uses / Re: Firmware Update/Downdate?

« on: September 29, 2019, 09:34:35 AM »

[rant]That's the nonsensical FUD BS swept through the internet in January 2015 showing clearly people have no clue how things work and how far away from good journalistic practice most news aggregation sites are. This BS almost never got corrected.[/rant]

Accuracy and standards for factual reporting


• Reporters are expected to be as accurate as possible given the time allotted to story preparation and the space available and to seek reliable sources.
• Events with a single eyewitness are reported with attribution. Events with two or more independent eyewitnesses may be reported as fact. Controversial facts are reported with attribution.
• Independent fact-checking by another employee of the publisher is desirable.
• Corrections are published when errors are discovered.
• Defendants at trial are treated only as having "allegedly" committed crimes, until conviction, when their crimes are generally reported as fact (unless, that is, there is serious controversy about wrongful conviction).
• Opinion surveys and statistical information deserve special treatment to communicate in precise terms any conclusions, to contextualize the results, and to specify accuracy, including estimated error and methodological criticism or flaws.

Source: https://en.wikipedia.org/wiki/Journalism_ethics_and_standards#Accuracy_and_standards_for_factual_reporting
Highlights by me.