Messages

does it help to disable "image review" in canon  menu? default is 2sec...

7D and others allow user-defined prefix to be added to filename through canon menu. should work for your purposes.

when you say:

"that custom handler should be moved in the same file as the rest of implementation"

should it be moved to movtweaks, or gui-common?

Here is a list of things that don't work (so you can see that I'm trying...)

Code Select Expand

#if defined CONFIG_7D
if (button_code == BGMT_PRESS_RAW_JPEG)
button_code = BGMT_TRASH;
#endif

and this:

Code Select Expand

#if defined CONFIG_7D
if (event->param == BGMT_PRESS_RAW_JPEG)
event->param = BGMT_TRASH;
#endif

menu.c is a really long file, I searched for "trash" and found stuff like what I tried above, but it doesn't work.

I don't really need this anymore, since I now know that I can enter menu with longpress joystick and exit with af-on, but it would be nice to understand it in case I want to remap another button sometime in the future.

That is very helpful,  thank you A1ex! I never knew about "long press joystick" guess I should rtfm.... I will also try in menu.c to get both working

I often use my 7D with a letus MCS camera cage which is great, but it's very difficult to press the trash button to access ML menus. I never use the raw/jpeg button on 7D, (I prefer to do file conversions on a computer instead...) and it's in a comfortable to reach place, so I decided to lie in the gui.h file and tell ML that raw/jpg is actually trash.

Does anyone see a problem with this? I get the desired result, but I'd really like to know the correct way to do this.

I found this thread, which was related, but not very helpful: http://www.magiclantern.fm/forum/index.php?topic=7816.msg70766#msg70766

this is due to srm job memory buffers which were recently added.

I took a stab at this over the weekend, but clearly I'm doing it wrong..... The worst part is I have to wait until 4GB are recorded every time I want to see if my changes had the desired effect.... Does it make sense to raise the bitrate and record a bunch of high-iso noise to hit this 4GB limit faster? or is there a better way?

have you tried ml autoexposure? you can set max iso there...

@ dpjpandone: Thanks for the latest development! I´m using the audio-display of your latest build, it´s pretty amazing! Thank you for your work, that are great news! That´s what I wanted to have the last months ...

Now ... there is one last wish I have: Could it be made possible to send the audio levels over the USB that I can see it within DSLR-Controller from Chainfire? He told me, that the level has to be given out parallel to the other informations, maybe ML can fix this ... if you need testing, I´m here ;-)

Markus, I didn't have anything to do with getting audio working, (other than re-enabling it) I still haven't gotten a clear answer about why it was disabled, so if you can please test ALL the audio features and let us know if you experience any problems, that would be great. I submitted a pull-request to get it in nightly builds, so hopefully it will show up there soon.

audio levels over PTP/USB - don't know if it's possible, but you may want to make a thread in the "Feature Requests" section of the forum. Maybe a skilled coder who uses a different camera will see it there and take some interest. At this point I don't have the skillset to add new functionality like that, but if someone else gets it working, I can copy and paste it, HA! 

One thing you will have to explain is your use case, and a very compelling reason for why you need to see audio levels remotely, somebody will probably say "Just get an external audio recorder...."

Hey guys,

I want to solve issue #2065:  https://bitbucket.org/hudson/magic-lantern/issue/2065/movie-restart-7d-stuck-in-loop-cannot-stop

I have been looking at the following lines for movtweaks.c:

Code Select Expand

#ifdef FEATURE_MOVIE_RESTART
        static int recording_prev = 0;
       
        #if defined(CONFIG_5D2) || defined(CONFIG_50D) || defined(CONFIG_7D)
        if(!RECORDING_H264 && recording_prev && !movie_was_stopped_by_set) // see also gui.c
        #else
        if(!RECORDING_H264 && recording_prev && wait_for_lv_err_msg(0))
        #endif
        {
            if (movie_restart)
            {
                msleep(500);
                movie_start();
            }
        }
        recording_prev = RECORDING_H264;

        if(!RECORDING_H264)
        {
            movie_was_stopped_by_set = 0;
        }
    #endif

I'm trying to understand how it works, and why it is broken on 7D. One thing that stands out to me right away is that 7D does not use the SET button to start/stop recording (unlike 5D2 and 50D, it has a dedicated start/stop button)

any additional information you can provide would be greatly appreciated. I tried to compare to a build where it is working properly, but there are so many changes by now that it's hard for me to track it down. If you can just point me to the parts that are relevant, that would be awesome...

Thanks!

My goal is to find the necessary values to implement HIGH FPS on 7D:  (these are for 600D)

Code Select Expand

   #define NEW_FPS_METHOD 1
    #define SENSOR_TIMING_TABLE MEM(0xCB20)
    #define VIDEO_PARAMETERS_SRC_3 0x70AE8 // notation from g3gg0
    #undef FPS_TIMER_B_MIN
    #define FPS_TIMER_B_MIN MIN(fps_timer_b_orig, 1420)


can I use the procedure described here:  http://magiclantern.wikia.com/wiki/Register_Map/Brute_Force

to find these values? Or is there a different/better way?  Or is it not possible/outside the scope of our understanding with the dual processors?

I can tell you exactly how to do this, as it's the technique I use to generate smpte color bars to calibrate an external monitor from my 7D:

set your cam to jpeg and take a picture. Open this picture in photoshop and paste the "old" image on top of it and then save (don't change any settings, just hit ok)  now you have your old pictures saved in the exact resolution/format that the camera produces natively, so you can view it on the camera and use the ghosting/overlay feature!

you are correct, raw only records native iso, which is 100,200,400,800,and 1600.   

80,160,320,640, and 1250 are made with negative digital gain, so don't use those for raw. However, these are the ones that give less noise with h264 so DO use them for h264.

you are correct, camera is too slow to playback in real time, and adding sound playback would make it even slower. MLRAWVIEWER is an excellent program for reviewing files on set.

I wanted to try this, but I get the following error when I restart the camera with this module loaded:

raw_rec_cbr_stopping defined twice  (from mlv snd and smpte)
also same message for _skip_frame, _cbr_stopping, _mlv_block

and undefined symbol 'module card drive'

failed to link modules.

I know it says "5D3" in the title.... and I tried it on 7D anyways......

maybe we can work on some of this timecode stuff this fall when u have time, I am still REALLY interested in this, I want to build an arduino-based smart slate that could use a canon DSLR as master and vice-versa!

Code Select Expand

#elif defined(CONFIG_7D)
    #define TG_FREQ_BASE 24000000
    #define TG_FREQ_SHUTTER (ntsc ? 51120000 : 50000000) // todo, just copied
    #define FPS_TIMER_A_MIN MIN(fps_timer_a_orig - (ZOOM ? 0 : 20), ZOOM ? 0x262 : 0x228) // todo


Have we settled on these values for 7D? If not, can someone please tell me how to find the correct values?

IME_ROT has some issues on 7D, nothing is displayed at all until I scroll far enough clockwise to select "H" then I can see the rest of the characters, scrolling counterclockwise makes everything disappear again when I reach "G" so "A-G" can be selected, but I have to do it blind by counting. also, when I press "Q" and scroll counterclockwise the same disappearing behavior is exhibited.

IME_STD seems to work fine.

***UPDATE***

I compiled it myself and it seems to work fine.... don't know if the problem is with the pre-built module you posted in this thread, or if it was just a fluke, but compiled from main repository is working well, I really like this BTW!

.
@dpjpandone, I'll test out the audio controls, thanks for the builds. Could you possibly make one with full res silent pics enabled? Would like to test that also.

I haven't looked at this feature yet, but I would definitely like to see it supported on 7D.

[raw2dng]

It looks like the errors you're still having are with building the local executables (raw2dng and cr2hdr), which is why you aren't having any problems with what you are loading on the camera.

OK, thanks! I remember seeing a post about how someone fixed this error with raw2dng, so I'll try that first.

I think the tearing is in fact linked to my monitor as it seems to be gone when using the "force-VGA" option in the "advanced" menu suggested above. Thanks @dpjpandone Your suggestion seems to have done the trick for the 5d mark ii as well.

Ethan,

I have been trying some different edmacs on my 7D that show GREAT IMPROVEMENT with the tearing/hdmi issue. I will borrow a 5D2 asap from my friend to see if the same changes will help. I know how bad it sucks to use your monitor in 480p..... 

***Attention 7D HDMI USERS***

I am trying to fix the image tearing issue that is present when using HDMI monitor with 7D

I have made some very small changes (using different edmacs) and I am seeing a lot of improvement. Can the other 7D HDMI users please test this build and tell me your results:

http://www.filedropper.com/magiclantern-nightly2014aug157d203

Please Use all of the features you would normally and tell me if you experience any problems or instabilities that are not present in current nightly builds. The only thing that should be different is that tearing should NOT be present in the recorded raw video files. As long as these changes do not introduce any new problems I will will submit a pull request so we can have this change in the nightly builds.

Thanks!


PS. here is another build with audio controls enabled, as far as I know the only problem was with "wind filter" which is still disabled, so the rest of these should work fine, please test and report if any new instabilities are found: http://www.filedropper.com/magiclantern-nightly2014aug157d203audio

Just remember, You are using magic lantern at YOUR OWN RISK! and using builds from newbs like me presents a HIGHER RISK than usual........ but I have tested these builds on my own 7D with no problems so I'm sharing them here so they can be tested over a wider range of circumstances/use cases than my own settings.

ln -s /usr/bin/rst2html.py /usr/bin/rst2html

This worked!

Big thanks to:

dmilligan, Audionut, nikfreak, ayshih, and philmoz  - I really appreciate your time and energy guys!

I actually got a zip that looks like a nightly build now!

I did notice some other errors/warnings, if someone has time, can you please confirm that the following is acceptable?

(code too large to post) download a txt file of the output from cygwin here:

http://www.filedropper.com/cygwinoutput


the builds I am generating are working fine on my 7D, and I have already fixed some issues that were bothering me for months now! I really can't thank you enough. I'm so happy to be able to participate now.

~Jon

Audionut - an advanced search only turns up this thread....

I downloaded docutils 0.12 and followed the instructions on the sourceforge page here: http://docutils.sourceforge.net/README.html#installation


here is how I installed it:

Code Select Expand

Jon@Jon-PC ~
$ cd c:/cygwin64/bin/docutils-0.12

Jon@Jon-PC /usr/bin/docutils-0.12
$ python setup.py install
running install
running build
running build_py
running build_scripts
running build_data
running install_lib
running install_scripts
changing mode of /usr/bin/rst2html.py to 755
changing mode of /usr/bin/rst2latex.py to 755
changing mode of /usr/bin/rst2man.py to 755
changing mode of /usr/bin/rst2odt.py to 755
changing mode of /usr/bin/rst2odt_prepstyles.py to 755
changing mode of /usr/bin/rst2pseudoxml.py to 755
changing mode of /usr/bin/rst2s5.py to 755
changing mode of /usr/bin/rst2xetex.py to 755
changing mode of /usr/bin/rst2xml.py to 755
changing mode of /usr/bin/rstpep2html.py to 755
running install_data
running install_egg_info
Removing /usr/lib/python2.7/site-packages/docutils-0.12-py2.7.egg-info
Writing /usr/lib/python2.7/site-packages/docutils-0.12-py2.7.egg-info


can you see where I made a mistake?


btw, here is my makefile.user (in case the problem is there) : http://www.filedropper.com/makefile_1

Now I'm seeing this a lot:

/bin/sh: rst2html: command not found


I googled this and it looks like I need to install rst2html in my arm path, was this supposed to be included with mercurial? or with the arm gcc 4.8.3?