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 - Meloware

Pages: [1]
General Development / Unable to build ML with Cygwin 32
« on: March 05, 2017, 01:33:33 AM »
I have been all day on this, as well as annoying dfort, and still without progress. I am unable to install Cygwin, etc., according to dfort's post and successfully build ML.

My system is Windows 7 Pro (I7 24GB ram). All of the files I needed were downloaded today. I have followed dfort's instructions for a 32 bit install, copying and pasting all the command line examples he has provided. All appeared to proceed normally, and I presume the install was properly finished once the unified version was cloned out of was done.

Desiring a build for the EOS M, I went to \home\chris\magic-lantern\platform\EOSM.202, with my Cygwin 32 terminal, and typed:
make zip

Dfort tried the same procedure today, and made a successful build. He then emailed me the console report of the build process.

My experience was identical, until after a bit after the message 
Code: [Select]
make[1]: Leaving directory '/home/chris/magic-lantern/tcc
was generated. Trouble seems to begin at the line:
[ LD       ]   magiclantern

Below is my printout following the exit from the tcc directory. Everything prior to the following lines were essentially identical to dfort's successful build. Notice that none of the symbols defined within tcc seem to be understood. HELP! I have attempted a fresh install twice and still get the same error. I am ready to be shamed for doing something dumb, if someone is willing to show a path to success.

Code: [Select]
make[1]: Leaving directory '/home/chris/magic-lantern/tcc'
[ CC       ]   module.o
[ AR       ]   strrchr.o
[ AR       ]   dietlibc.a
[ AR       ]   lib_a-setjmp.o
[ AR       ]   newlib-libc.a
[ CP       ]   newlib-libm.a
[ CP       ]   gcc-libgcc.a
[ LD       ]   magiclantern
module.o: In function `module_load_symbols.constprop.2':
module.c:(.text+0xebc): undefined reference to `tcc_add_symbol'
module.o: In function `_module_load_all':
module.c:(.text+0xf2c): undefined reference to `tcc_new'
module.c:(.text+0xf38): undefined reference to `tcc_set_options'
module.c:(.text+0xf5c): undefined reference to `tcc_delete'
module.c:(.text+0xf98): undefined reference to `tcc_delete'
module.c:(.text+0x11b4): undefined reference to `tcc_delete'
module.c:(.text+0x11f0): undefined reference to `tcc_add_file'
module.c:(.text+0x1250): undefined reference to `tcc_relocate'
module.c:(.text+0x127c): undefined reference to `tcc_relocate'
module.c:(.text+0x12e4): undefined reference to `tcc_delete'
module.c:(.text+0x1350): undefined reference to `tcc_get_symbol'
module.c:(.text+0x1378): undefined reference to `tcc_get_symbol'
module.c:(.text+0x13a0): undefined reference to `tcc_get_symbol'
module.c:(.text+0x13c8): undefined reference to `tcc_get_symbol'
module.c:(.text+0x13f0): undefined reference to `tcc_get_symbol'
module.o:module.c:(.text+0x16e0): more undefined references to `tcc_get_symbol' follow
module.o: In function `_module_load_all':
module.c:(.text+0x1740): undefined reference to `tcc_delete'
module.o: In function `module_load_task':
module.c:(.text+0x1a0c): undefined reference to `tcc_load_offline_section'
module.o: In function `module_load':
module.c:(.text+0x1ad0): undefined reference to `tcc_new'
module.c:(.text+0x1adc): undefined reference to `tcc_set_options'
module.c:(.text+0x1b00): undefined reference to `tcc_delete'
module.c:(.text+0x1b14): undefined reference to `tcc_add_file'
module.c:(.text+0x1b28): undefined reference to `tcc_relocate'
module.c:(.text+0x1b38): undefined reference to `tcc_delete'
module.o: In function `module_get_symbol':
module.c:(.text+0x1b58): undefined reference to `tcc_get_symbol'
module.o: In function `module_exec':
module.c:(.text+0x1b80): undefined reference to `tcc_get_symbol'
module.o: In function `module_unload':
module.c:(.text+0x1cfc): undefined reference to `tcc_delete'
make: *** [../../src/Makefile.src:195: magiclantern] Error 1

chris@melo2 ~/magic-lantern/platform/EOSM.202

General Help Q&A / Silent Pictures with the EOS M
« on: February 22, 2017, 03:14:23 AM »
I transfer and restore 16mm movies using my 650D/T4i with Magic Lantern's and I just bought an EOS M (cheaper and mirror-less) and discovered too late that Canon didn't bother to include a remote shutter connection. The camera STILL has mechanical parts operating with each exposure, so I must find a way to use Silent pictures with this camera.

If I load silent and mlv_rec in the EOS M, it still functions well with the “half shutter” button pressed. I can still use all recording modes by physically pressing this button. Please suggest a way I might do this with a switch closure from my own film controller(as I did with my 650D/T4i).

ML's audio trigger looks promising, and even works with the lower resolution modes of Silent pictures. When I try and use the audio trigger with full resolution video and DNGs, the first exposure is taken and the screen then goes black. No further trigger events are possible until I physically press a “half shutter”. I may then audio trigger one more complete exposure and then everything stops as before. I am a poor coder and have no idea how to write and compile my own version of ML, but it seems like it might be an easy change for someone more experienced.

Is there any other possible solution? Do Lua scripts offer a solution? Any guidance or help in getting my EOS M working with event triggered Silent pictures (full-resolution) would be greatly appreciated.

Thank you for past help and I hope this one is interesting and doable.
(Sorry – had to post here because I can't seem to post in Camera-Specific discussion)

I am getting some wonderful results in my effort to capture 16mm movies using Magic Lantern and my T4i (650D). The camera's shutter mechanism would quickly wear out if cycled for each film frame. Magic Lantern's Silent Picture raw mode solved the problem I had with using my camera. I am now able to take many tens of thousands of pictures, without using the shutter mechanism.
I have a modified 1970s Bell & Howell projector. The original projection lamp, fan, motor and lens, were removed. I added my own optics, a stepping motor (with a $10 Chinese motor controller) and LED illumination to project images directly on my camera's sensor. The camera and projector are automated by a circuit board controller of my own design.
Managing a 31 megabyte DNG file for each movie frame is very demanding on memory and hard disc storage. The worst issue is dealing with the write speed of SD camera memories slowing down as they fill. It is practically possible to only capture 5 or 6 frames a minute. It takes days to transfer a single 10 minute reel of film. It might be faster, if I could get a "camera ready" signal out of my Canon, once it's able to take the next picture. This bottleneck is sad, but it is still possible to do great work.
Please allow me to share the results of using Magic Lantern. Notice the first 4 videos.

Chris (Meloware)
Museum of Our Industrial Heritage, Greenfield Massachusetts, USA

// Adding the first video here.  Audionut.

Pages: [1]