Menu

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.

Show posts Menu

Messages - Walter Schulz

#5476
Sorry, but not clear what you have done (past) and what you are about to do (future).
Please clarify!

- Did you use EOScard utility to make card bootable? If not: You can only test plain Canon firmware without ML's diagnostic tools. BTW: All diagnostic tools are a1ex' work.
- If card is bootable there should be some LED blinks

Another question: Do you have a second SD-card?
#5477
Downloads -> Download Nightly Builds -> Features
Same link as above.

And there is a new sound system in development but dormant right now.
https://bitbucket.org/hudson/magic-lantern/branch/new-sound-system
#5478
What exactly is the problem? Won't start? Stopping before sequence is completed? Exposure going wrong?
Please tell your ML version (date).
#5479
Did you try to start cam in C mode (mode dial)?
#5480
To get a bootable card again:
Use EOScard or MacBoot to make card bootable.
Wipe all contents from card.
Copy extracted nightly build contents to card. Or use the "Debug" Autoexec.bin.
#5481
That's the way it works. The card is non-bootable now.
If you format the card in a cardreader or a cam without ML on it
card will get non-bootable and Autoexec.bin will not be loaded at startup.
That's intended.
But cam should start with and without blank card inserted.

To get a bootable card again:
Use EOScard or MacBoot to make card bootable.
Wipe all contents from card.
Copy extracted nightly build contents to card. Or use the "Debug" Autoexec.bin.
#5482
https://builds.magiclantern.fm/#/features
Wiki covers v2.3. We're talking about Nightly Builds ...
#5483
Quote from: Thobias on October 16, 2015, 04:26:59 PM
Will try google what you mean by that=D

Mark directory where MLV_DUMP.exe in explorer, keep shift key pressed and open context menu. You will see a new item "Open Command Prompt here ...". Now you are in command line.
Type
MLV_DUMP "<path>\<the name of yor MLV file>.mlv"
You can copy name and path of your MLV file by marking it in Explorer and opening context menu while shift key is pressed. There is an option to copy path to clipboard.
In command line you have to use context menu to copy clipboard content. CTRL-C and CTRL-V won't do Copy&Paste.
#5484
Try to run mlv_dump from commandline and see what happens.
#5485
@chrisfrancia:
If the cam is not enabled for ML (bootflag not set):
Nothing will happen. Canon menu will start up and you are on plain Canon firmware.

If the cam is enabled for ML:
Either cam won't start up (old builds) or an error message will be seen.
#5486
General Help Q&A / Re: Screen recording?
October 15, 2015, 05:52:23 PM
HDMI out -> external HDMI recorder. Done.
#5487
General Help Q&A / Re: Dual ISO causes funny colours
October 15, 2015, 01:35:55 PM
cr2hdr version? Camera type? ML version? Downloadable CR2?
#5488
Which of those issues haven't been cleared by KB support here or elsewhere?
#5489
No. Devs decided some time ago not get involved with Canon's pro gear. And that means everything with a C and all EOS 1 stuff. Period.
If you find people willing to do this be aware there are some signals from Canon willing to go to war about it.
#5490
Delete ML directory and Autoexec.bin from card. Copy extracted nightly build contents to card.
Insert card into cam and try to start cam. Report back.
#5491
Insert your ML card into cardreader. Rename Autoexec.bin to Autoexec.ml and copy autoexec.bin found here to card. Insert card to cam and just close compartment door. Do you see the display test screen? You don't have to turn on the cam!

After testing remove battery and remove card from cam!
#5492
Remove battery, remove card. Insert battery, do *not* insert card and startup cam. Results?
#5493
Quote from: miramez on October 13, 2015, 11:02:44 PM
Walter, i´m just looking for a help without irony!

Good luck, then!
Read first post of this thread, you got it all wrong.
"Allthough showing Version 1.1.1 in menu some camera dumps showed a different revision. Therefore I had to port ML twice to 70D (70D.111A / 70D.111B)"
#5494
Bandwidth = Vertical resolution * horizontal resolution * bit depth * frame rate / 8
2704 * 1352 * 14 * 24 / 8 = 153543936 Byte/s = 146,5 MByte/s
Continuous recording limit for 100D is about 41 MByte/s (or less).

Sorry, this just won't work for longer than a few seconds and even 5D3 won't do it continuously. Mission impossible.
#5495
Read the title of this thread ...
#5496
You won't find this info and you don't have to. Download version A and try to install it. If it fails install B.
#5497
Camera-specific Development / Re: Canon 50D
October 13, 2015, 10:07:16 PM
Remove card and battery. Insert only battery and startup cam.
#5498
You got it wrong.

If (if!) v2.3 and the nightly build you intend to use do have to run on different Canon firmware version things will get complicated.
If both ML versions are compatible with the same Canon firmware version (the one you are running now) you may switch cards as you like.
#5499
ML is not firmware. It's much more like a program loaded after Windows/OS X startup.
So: If there is a nightly build running on the same Canon firmware version as you are using now you will be fine with two cards with different ML versions. If not: Much more complicated ...
#5500
Version? OS you are running? CR version? You haven't tested all the RAW editors in the wild, so please tell which one you tried.
And a DNG for downloading and testing would be fine, too.