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 ... 250
1
Camera-specific discussion / Re: Canon EOS M
« on: Today at 06:39:37 PM »
You don't really need Magic Lantern to hook up the EOSM to HDMI and get clean output (no overlays). As far as I know it doesn't put out a full HD signal. When I tried it the image had a black area around it on the screen. Another issue is that the camera LiveView goes dark, it doesn't mirror the way the 5D3 does with the later firmware updates.

@DeafEyeJedi has experience hooking up an Atmos Ninja to the EOSM so you might want to contact him about it.

thehaxfactory doesn't own an EOS M. ATM he is thinking about it. And intended use is streaming, thus 30 min timeout without ML is actually an issue. So he is asking about resolution (non-recording modes).

@thehaxfactory:
Another issue is that the camera LiveView goes dark, it doesn't mirror the way the 5D3 does with the later firmware updates.

What dfort is trying to say: As soon as HDMI connection is used M's LCD screen goes black. You can have either cam's monitor *or* external, not both the same time. Which is btw how most ML supported cams work.


I think it would be interesting to know how M's HDMI output is doing compared to cams not hampered by mv720 (if this is an issue at all with HDMI streaming).



2
Hello!

I humour myself using search strings "Magic Lantern Canon" in Google restricting search results to "Last 24 hours" from time to time. Useful to find new stuff related to ML ... once. The last days it seem Google has fallen for SEO of the bad kind: Pages filled with thousands of search strings comes up first and it goes on and on. Okay, for users able to interpret nonsensical strings like "www.blabla.wherethebadboysare/kajdfjaerfk/slakdfjljef/m=sadf/..." without clicking them its just annoying. For other users going to find information about ML it is almost impossible to get linked to ML home and forum page.
Disclaimer: I'm not a web master.
Q: Is there something the web admins can/should do about it?

EDIT: Search strings like "Magic Lantern" without restrictions work just fine.

3
Well, rawtherapee seems to ignore the xmp file altogether :)

Have you contacted rawtherapee dev(s) about this? In the past we had some friendly contact with user heckflosse to solve some issues.

4
Camera-specific discussion / Re: Canon EOS M
« on: Yesterday at 10:05:59 PM »
Can't answer that. Not owning an M and there are some pitfalls with M (mv720 ...) and some exciting new developments.
I hope dfort may have an answer about M's HDMI output in photo liveview and non-recording movie liveview.

5
Camera-specific discussion / Re: Canon EOS M
« on: Yesterday at 06:18:40 PM »
https://www.magiclantern.fm/forum/index.php?topic=20908.msg193014#msg193014
Applies to EOS M running experimental build "lua_fix", too.

6
Camera-specific discussion / Re: Canon EOS M
« on: January 20, 2019, 05:55:03 PM »
@Tullen: Don't get overexcited about "super" moon. It's not that much a difference and blood moons are not that rare.

Source: Wikepedia

Naked eye may not see a difference at all ...

7
General Development Discussion / Re: Portable ROM dumper
« on: January 19, 2019, 10:08:03 AM »
7D.206 here again with updated dumper:
Code: [Select]
Magic Lantern Rescue
 ----------------------------
 - Model ID: 0x250 7D
 - Camera model: Canon EOS 7D
 - Firmware version: ??? / ???
 - IMG naming: 100EOS7D/IMG_0000.JPG
 - User PS: ??? ??? ???
 - Boot flags: FIR=0 BOOT=-1 RAM=-1 UPD=-1
 - ROMBASEADDR: 0xFF010000
 - card_bootflags 109a18
 - boot_read/write_sector 109d54 109d64
 - Patching 104294 from e3500001 to e3500000
 - 104254 Card low-level init => F4240
 - 1026EC Card init => 0
 - Patching 1026FC from e3510001 to e3510000
 - 1026EC Card init #2 => 1
 - Dumping ROM0... 100%
 - MD5: 8206fa3fda73c2ead57297bdea24f9fd
 - Dumping ROM1... 100%
 - MD5: 0de4cc03919f939c4ec691eb5fcfd744
 - No serial flash.
 - Saving RESCUE.LOG ...

ROM0.BIN checksum still not matching results computed by PC:
Code: [Select]
15df32dc1fccf481a812ae0fa19ebfe9 J:\ROM0.BIN
0de4cc03919f939c4ec691eb5fcfd744 J:\ROM1.BIN

Compared both files with those generated by dfort's ML build:
MD5 match for ROM1.BIN but not ROM0.BIN

8
Tutorials and Creative Uses / Re: Let's restore camera help (Help needed)
« on: January 17, 2019, 08:52:16 PM »
Status Expo screen:

Almost done.

To do list:
About to delete ISO -> Color coding. Seems to be gone for good.

Asking for help for modules ETTR, DUAL_ISO and AUTOEXPO.

EDIT (18.01, High Noon):
Basic editing for Overlay screen done.
Missing helpful texts for Histograms, Vectorscope, Waveform.

Think will go into Display next.

9
General Development Discussion / Re: Portable ROM dumper
« on: January 16, 2019, 08:48:58 PM »
You can try to create a < 2 GB partition.


- the portable ROM dumper (you must format the card to a very small size, or dd this 256MB image - howto)

10
General Development Discussion / Re: Portable ROM dumper
« on: January 16, 2019, 07:56:57 PM »
7D.206 with SanDisk  Extreme 60 MB/s, 32 GB

Contents of ROM0.MD5 and ROM1.MD5:
Code: [Select]
994fce5ee9ea3bb6df3ba0eaddf3e46f  ROM0.BIN
0de4cc03919f939c4ec691eb5fcfd744  ROM1.BIN

MD5 check on ROM0.BIN and ROM1.BIN running by PC:
Code: [Select]
50838bbf29aec4c6e62bee320d5c9138 J:\ROM0.BIN
0de4cc03919f939c4ec691eb5fcfd744 J:\ROM1.BIN

MD5 check for file ROM0.BIN differs.

BTW: No timestamps for ROMx.BIN and ROMx.MD5.


11
General Development Discussion / Q on LV Display Presets (@a1ex?)
« on: January 16, 2019, 03:39:02 PM »
Curiosity again:
Settings for each display (numbered 0-3) are stored in MAGIC.CFG in lines disp.mode.a, disp.mode.b, disp.mode.c and disp.mode.x into a number. Decimal number interpreted as binary where each bit represents a setting (or combined bits for items with more than 2 options). Right?

12
Duplicate Questions / Re: Magic Lantern & [email protected]
« on: January 15, 2019, 09:18:01 PM »
No. Because it won't work it doesn't make any sense to try. Programming a port simply don't work this way.

13
Camera-specific discussion / Re: Canon EOS M
« on: January 15, 2019, 07:33:04 PM »

14
General Help Q&A / Re: Dual-ISO for video for a low-lit scene
« on: January 14, 2019, 06:45:57 PM »
Do you have browsed the links in Camera Help -> ETTR.mo section?

15
Tutorials and Creative Uses / Re: Let's restore camera help (Help needed)
« on: January 14, 2019, 02:19:14 PM »
Feedback time:
Debug tab help ready to be reviewed.

To discuss: Help text made for mere users. I omitted all the "nerdy" stuff. Q: Add a line for each menu item to tell users not to pay attention to that man behind the curtain?

Missing: RL numbers for benchmark runs for each cam.
Broken: Format for listings and sub-menus ... See "Benchmark"

16
Camera-specific discussion / Re: Canon 6D
« on: January 13, 2019, 11:01:22 AM »
Reset ML to defaults (Prefs tab -> Config Files -> Restore ML defaults)

Retry in photo and movie mode. If the error occurs you have to restore ML defaults again.
Report results.

17
Camera-specific discussion / Re: Canon EOS M
« on: January 11, 2019, 02:57:44 PM »
@jacquaviva:
Crop factor calculation into 35 mm terms:

(Sensor horizontal pixel count / ML horizontal resolution in ML crop mode) x 1.61

It's not exactly rocket science, you know?

18
Think about getting g3gg0 involved, too. He had the suggestion to sync the other way round using camera's LED to trigger stepper motor. Short mention about it in linked thread.
Requires a custom build, though.

19
Camera-specific discussion / Re: Canon 650D / T4i
« on: January 09, 2019, 09:49:10 PM »
I haven't been able to find out what triggers it yet. Will look into it, though.

EDIT: First hint: Happens after powersave mode.

20
Camera-specific discussion / Re: Canon 650D / T4i
« on: January 09, 2019, 07:58:22 PM »

Occasionally this (lower right corner) happens to me. Scrollwheel function not affected (or I missed something).
Can I help to corner this one?
Older nightly and experimental builds affected, too.

21
Okay, old one but what's the status?
Im mean: (Almost) no one missed it since. Gone for good? Can live with that ...

22
Camera-specific discussion / Re: Canon 60D
« on: January 09, 2019, 06:02:27 PM »
Module tab -> bench.mo OK -> Restart (photo mode) -> Debug tab -> Benchmarks -> Card Benchmarks -> Quick R/W benchmark (1 min).
Open card's root directory and convert bench0.ppm to png or jpeg. Upload it to a file/pic like picload.org and link image here.

And retry H.264 recording with Global Draw OFF.

23
Camera-specific discussion / Re: Canon 60D
« on: January 09, 2019, 04:42:42 PM »
Before going into analysis: May I suggest to get another card and retry? 60D's limit is about 25 MByte/s (without overclocking) and such cards are affordable. Get your pick from cameramemoryspeed.com -> Reviews -> SD-cards and Micro SD-cards or any other reliable source offering write rate benchmarks.

24
Here is how another user solved sync problems. Requires some additional hardware + experimental build: https://www.magiclantern.fm/forum/index.php?topic=19300.msg190023#msg190023

25
General Help Q&A / Re: Canon 7D Live USB Audio Monitoring
« on: January 09, 2019, 03:52:21 AM »
With MagicLantern Build Ver. 2018.Jul03 installed, the Canon 7D does not have a function for live audio monitoring. I did buy a USB to RCA cable, and an RCA to 3.5mm. Audio worked fine, but the display went black. Is there a module I'm missing somewhere that I need to turn on? Or has it been disabled until (hopefully) ver. 2.0.6?

https://builds.magiclantern.fm/features.html -> Audio -> HEADPHONE_MONITORING not supported in 7D. Same in 2.0.6.

Pages: [1] 2 3 ... 250