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 5 ... 268
51
General Help Q&A / Re: Need help finding my next film-like camera
« on: September 15, 2019, 02:45:24 AM »
7D: Dual Digic IV, doesn't support Dual-ISO movie, HDR movie, FPS ramping, Gradual expo. No lossless compression and other experimental MLV/RAW movie stuff with Digic V.

52
General Help Q&A / Re: Live View 60d Problem Please Help
« on: September 13, 2019, 10:37:04 PM »
You need experimental "lua_fix" build to use this feature.

53
General Help Q&A / Re: Need help finding my next film-like camera
« on: September 13, 2019, 10:29:11 PM »
and the auto focus sensor is apparently right next to the lens mount

The "AF-assist beam" will not be used in movie mode. See http://gdlp01.c-wss.com/gds/8/0300008788/01/eosm-im-en.pdf page 132.
Continuous AF and M, well ... May some M users have a word here ...

54
General Help Q&A / Re: Host-controlled silent shooting
« on: September 13, 2019, 10:56:37 AM »
Most likely gphoto2 cannot find silent pic because it is labeled *.DNG.
You can work around this problem by forcing silent.mo to write DNGs labeled as CR2 by changing some strings in silent.c source code and compiling a custom build. dfort wrote some - pretty easy to follow - tutorials how to build up a development environment.

55
Camera-specific discussion / Re: Canon 5D Mark III / 5D3 / Firmware 1.3.4
« on: September 12, 2019, 08:25:10 PM »
Quote
Firmware Version 1.3.6 incorporates the following fix:

1. Corrects a PTP communications vulnerability.
2. Corrects a vulnerability related to firmware update.

Firmware Version 1.3.6 is for cameras with firmware Version 1.3.5. If the camera's firmware is already Version 1.3.6, it is not necessary to update the firmware.

When updating the firmware of the camera, please review the instructions thoroughly before you download the firmware.

Notes:
- Once the EOS 5D Mark III camera is updated to Version 1.3.3 (or later), it cannot be restored to a previous firmware Version (Version 1.0.7 through 1.2.3).

"is for cameras with firmware Version 1.3.5."
? I'm convinced "or earlier" is just missing. They don't really suggest to use a staged update for cams with older firmware ... I hope.

And as always with 5D Mark III after 1.3.x: Can someone test if downgrading from 1.3.6 via Canon Utility is still working?

56
Search engine -> CHDK lorenzo353

I don't think devs share your problem. See nanomad's reply https://www.magiclantern.fm/forum/index.php?topic=3096.msg14579#msg14579

57
General Help Q&A / Re: Is this feature still around?
« on: September 10, 2019, 07:25:23 PM »
Nowadays the easiest way to do that is running a LUA script. Load LUA.mo. After restart access Scripts screen and run "Movie delayed start". Then switch to Movie tab and there you have a new item which allows you to determine start delay and record duration.

Now dive into scripting and adjust it as you like. You just need a script to run at startup, waiting for "movie.recording" to become true, waiting for some time (msleep(20000)) and then movie.stop().

https://builds.magiclantern.fm/lua_api/modules/global.html

If you can't make sense of it: Just ask again, maybe we could help.

58
Camera-specific discussion / Re: Canon 750D
« on: September 09, 2019, 09:39:44 AM »
Read post above yours.

59
General Help Q&A / Re: Does speed of firmware card matter?
« on: September 07, 2019, 09:15:26 AM »
Either contact your reseller and let them replace the item with a fast one. Or go Sandisk Extreme Pro known for endurance and performance. Komputerbay may also be an option but mixed experience with reliability.
Haven't heard from users of Toshiba Exceria Pro, though.
See www.cameramemoryspeed.com

60
General Help Q&A / Re: Turn off Rack Focus
« on: September 06, 2019, 07:49:15 AM »
Take a firm grip to the wand, point to cam and shout "focusrackuta dissolva".

Seriously: Give us a chance to understand/reproduce your issue by providing details. Cam type would be fine and some text about what you are trying to do ...

61
General Help Q&A / Re: Does speed of firmware card matter?
« on: September 06, 2019, 07:43:34 AM »
"I know" can mean two things:
- I have tested it and numbers are within expected range.
- Other have tested a card that looks like mine.

AFAIK there are at least 2 different versions of this card and there is - at the moment - no way to tell them apart but to run a benchmark test and draw conclusion. One has superior write performance > 100 MByte/s (tested with ML's benchmark module). The other will do just about 81 MByte/s.
If you have a decent cardreader you may test/confirm with PC you got the fast one. Or use ML's bench.mo.

62
You set the "boot flag" on your cam. It will now check for a bootable card each time battery hatch is closed and each time the cam is powered up from powersave. If you insert an incompatible card (very, very old EyeFi cards) cam will get stuck. If a bootable card is found it will check for autoexec.bin. If no autoexec.bin is found cam will get stuck. Just don't use bootable cards without autoexec.bin.
You haven't flashed a custom ROM to your card. Your firmware wasn't replaced. ML runs from card, not from NVRAM.

And you may consider not going somewhere without checking the consequences of your actions. Maybe consider asking before doing something if you're unable to check the consequences.
Just saying ...

63
----------------------------------------------------------------
%F in (*.MLV) do mlv_dump_bruteforce.exe %F -o R-%F
----------------------------------------------------------------

Code: [Select]
For %F in (*.MLV) do mlv_dump_bruteforce.exe %F -o R-%F

64
Wanted to add 2 or 3 cents and an aspect I think missing in the discussion.

What happened (IMHO)?
A person took his tools and grey matter together and dived into something unknown to discover something. That's what engineers/developers do. We have tools, some busy brain cells and - sometimes - a goal to achieve. Fine. What differs from ML development is POV. He is in the security business and where other people may see a mere bug he saw an opportunity.
Once the attack vector (in PTP) was discovered he may have stopped here. Mathematicians would have: Solution exists -> back to sleep. Okay, telling Canon about it is good practice and within job description. But he didn't stop at this point. Outside the very small community of security geeks such bugs in PTP will not make news. So he thought about something sounding threatening and make people listen. And ransom attack on flash memory content sounds plausible enough and triggered the bigger photog/movie community as intended. (Let's not discuss how far-fetched this scenario is, it is news and therefore solid enough).
As written before: ML offered some kind of paved way to make this happen. Least amount of work compared to other cam manufacturers. Keeping the encryption key hidden was successful and not. As mentioned in the article: Another example security by obscurity doesn't always work.

What will happen (IMHO)?
Pure speculation. Well, ML community may get collateral damage by Canon's action (discussed earlier). It's more difficult for Canon to officially act like ML doesn't exist. We have no saying in the upcoming events.

What are we missing in this discussion(IMO)?
We have no official contacts to Canon. The person discovering the vulnerabilty does now. Maybe we can learn a bit by his approach.
Let's explain my train of thought: A1ex offen mentioned (if I'm remembering correctly) various flaws and potential risks in some firmware routines. Bricked cams by writing nonsense into cam's memory via some not-so-intelligent tools are pretty familiar to him. Canon has no bug-report/bounty program for developers. Maybe they should have.
IMO Canon will have to open up cams to the internet. People want easier access to social media, clouds and other services of their choice. Today they are not well suited for this demand.

May I suggest to think about what ML dev team can do/acchieve by adding security POV into its scope?

Yes, I know there is a major issue within: ML development is endangered by Canon's action against vulnerabilities because ML - somehow - relies on them. It can blast back badly.

But let's give it a try: Take a security POV on firmware/SDK, check for vulnerabilities and if discovered something not exploiding in our face (I have no doubt there are) let us "write home about" (home= Canon). VoilĂ : Houston, we made contact!


And let us hope Canon doesn't throw ML baby out with the bathwater.

65
Camera-specific discussion / Re: Canon EOS M
« on: September 02, 2019, 03:31:59 PM »
In particular, is there something that provides crop modes for photos?

Why?

66
Camera-specific discussion / Re: Canon EOS M
« on: September 02, 2019, 03:09:49 PM »
Any particular reason(s) specifically why you're asking for this build @uEOSM?

He is asking for any build ("Can be earlier or later"). Maybe he is not aware of Danne's Bitbucket download folder location?
https://bitbucket.org/Dannephoto/magic-lantern/downloads

67
General Help Q&A / Re: MLVFS Default Naming Scheme // Feature Film
« on: September 02, 2019, 02:27:37 PM »
Good to hear you found a solution!
Maybe there are other users facing similiar issues. Consider sharing your code chances. ;-)

68
Camera-specific discussion / Re: Canon EOS 4000D / 3000D / Rebel T100
« on: September 01, 2019, 03:23:03 PM »
It may help telling what skills you have. Unicorn level:
- C and Assembler for embedded systems (preferable ARM architecture) and lots of time.

For starters: Making QEMU run in your environment. See sticky tweet.

69
Non-working mlv_play is a known issue. Use search field on upper right corner for more info.

70
AFAIK Windows version does not support wildcards, at least ATM. You won't be able to use it this way and command line length is limited in Windows. 2047 or 8191 characters, haven't tested cr2hdr limit yet.
For "terminal": In Windows terms it may be called "Command prompt", "command line", "CLI" (command line interface), "cmd" ... Startup search engine of your choice ...

72
Raw Video / Re: CANON 7D advice
« on: August 28, 2019, 02:54:20 PM »
Depends on your needs/expectations/budget. If you care to share yours someone might come up with a not-so-generic answer.

73
Raw Video / Re: CANON 7D advice
« on: August 28, 2019, 12:25:29 PM »
Pro: CF write rates with fast cards at least as good as overclocked SDs. Sturdy beast.
Con: Digic 4 -> No 4k_crop mode. No Dual-ISO video. No HDR video. No articulating display.

Frankly: My 100D offers a lot more RAW video options with 4k_crop builds delivered by Danne and dfort. And M offers mounting a lot of manual lens types via passive adapters.

74
Camera-specific discussion / Re: Canon 6D
« on: August 27, 2019, 04:08:39 PM »
I think we have a problem understanding and reproducing your issue.
Can you please explain in detail the expected/wanted behauviour/feature set and what is actually happening?

75
General Development Discussion / Re: Portable ROM dumper
« on: August 07, 2019, 07:47:12 PM »
Code: [Select]
md5sum ROM?.BIN -c ROM?.MD5

Pages: 1 2 [3] 4 5 ... 268