Messages

I really wish that, one day, somebody will, accidentally maybe, find a way to change that LV's line skipping from taking out 2 lines out of 3 lines to taking out 1 line out of 2 lines, then we can have more resolutions.

Great work. This thing is getting sweeter and sweeter.

I don't understand the fps overide mechanism very well, but it seems to me that it will drop fps and even shutter speed to suit its purposes, so I just choose "exact fps" hopefully to lock on the fps.

14-16mins, but your camera is probably getting overheated first.

We can see that the 7D's video capture ability is more and more formidable. Congratulations.

But I encounter two problems since the last build:
1) When the card record to its full capacity, the screen freezes to its last screen with that black screen and a square, and it is still there even I pull the camera's power slider to OFF position. The phenomena happens in the first 2 times of the total 4 test runs. And I have to pull the battery out.
2) The 0908 build permanently changes the camera's firmware, and in Canon's menu, 1920x1080@25fps option is gone.
3) It is not a problem, but when the camera's writing continuously, frame skipping suddenly appears, so I have to preload a very large file into the CF card while booting up (like warmup with 256mb--I haven't tried other settings yet), and then the CF card can, miraculously, have 0 frame skipping while recording continuously.

I know very little of programming. When looking through  fps-engio.c and fps.c, I have seen that there are some definitions for some cameras like 600D, 6D...but I couldn't find the likewise for 7D, which definitions are like these:

fps-engio.c: (line 272 - 298)
#ifdef CONFIG_600D
    #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)
    static const int mode_offset_map[] = { 3, 6, 1, 5, 4, 0, 2 };
#elif defined(CONFIG_60D)
...

fps.c: (line 16-32)
#ifdef CONFIG_600D
#define SENSOR_TIMING_TABLE MEM(0xCB20)
#define VIDEO_PARAMETERS_SRC_3 0x70AE8 // notation from g3gg0
#define CARTIRIDGE_CALL_TABLE 0x8AAC
#define AEWB_struct_ptr 0x1dcc
#endif

I do not know if it is important.

fps-engio.c:
https://bitbucket.org/hudson/magic-lantern/src/608e4b7437881d8cb8fc7e2c6c703fa4827f2606/src/fps-engio.c?at=unified

fps.c:
https://bitbucket.org/hudson/magic-lantern/src/608e4b7437881d8cb8fc7e2c6c703fa4827f2606/src/fps.c?at=unified

Just 2 cents.

I have found that the camera is less hot with its original metal handgrip, one of my CF card cannot shoot to all the way to be full without a handgrip (it will show "skip frame"), but with a handgrip it can shoot all the way.

The Digic4 sounds like a 80086(that is Intel's processor before 286) without a floating-point co-processor.

When C100 becomes C500, all I can imagine is hearing some 4 letter words from Canon......

A bit away from the current topic. 7D's write speed is only around 63% of its theoretical speed. I am wondering if it is due to the fact that the ML is booting from the slave CPU, and I think that it might be writing faster from the master CPU saving the penalty of overhead from communicating between the CPU?

@Britom: I think that I owe you at least a test. Your latest build, have to say, didn't bump the resolution one stop higher, but surely is one step towards stability. Thanks.

BTW, I keep only raw_rec.mo module only in the modules directory, that seems a little more stable.

@JCBEos: The numbers are very exact and very close to the performance of my CF 800x, seemingly it is sth to do with the camera, rather than the program. Great tks.

@arrinkiiii: I will rather stay with the older version for now. Thanks. But I also get that "pink" garbage pictures in the image chain, like some others. I suspect that it happens more with higher write speed. 

mlv2dng is so hard to use. With another program, I can specify which directory to put the DNG files, click GO, and it will convert by itself, and put different shots into different directory by itself, so I just need to put CF card into the card reader, choose a directory and click GO, then I can stay away from the program. But with mlv2dng, I need to copy all the files in the CF card root directory, deselect some ML files, copy all the files into mlv2dng's directory, drag and drop all the files on mlv2dng.exe(sometimes not working), and sort all all the footages and cut and paste to another directory.

BTW, one time I have got a very large like 600M size .m0 file with .mlv files, which I could not process and know not what it is.

I found that my 7D has unusual low write speed.  Is it possible to multi channelling the EDMAC? Like assign every individual RAW a different EDMAC? But do remember to clean the buffer memory address when moving file away from the buffer.

Britom's version is about 9-12% faster, so I can bump up the resolution 1 stop with the same CF card.

You probably have heard, 7D's supported file system for the CF card is FAT32 which has a maximum allocatable sectors of 2^32, so that, which I have heard, translated to the maximum allocatable partition that is 32gb.

There might be a hack to this, that is to format the CF card manually assigning a very large sector (but that will mean waste some space), just format with "format /?" in Windows command promt to see what options you can get. I haven't tried this on my camera, the camera might not recognize the file system.

It is also heard that if you don't format the CF card in the camera, the camera's write speed will decrease over time, so you need to perform the format operation from time to time.

My 2 cents.

Please ignore reply #420. I turned off the LV power saving in Canon's menu.

Great job.

I have got a problem. When zoom in to 10x, my 7D still freezes, but it is only a small glitch that I can solve it by switch off 10x zoom in the menu.

BTW, when shoot with raw, the 7D often goes into sleep mode, could not find a way to stop it. It is driving me nuts. Helps needed. Thanks in advance.

#elif defined(CONFIG_7D)
uint32_t edmac_read_chan = 0x19; 
uint32_t edmac_write_chan = 0x04;
#else
uint32_t edmac_read_chan = 0x19;
uint32_t edmac_write_chan = 0x11;
#endif

This looks a little bit better to me.

TKS, Britom. Maybe I should zip my mouth.

Maybe we can completely disable that "key press" block( a little bit violet though)

BTW, I use the AF-ON to focus, when I press that key, 7D freezes too.

I am no coder. Looking through the raw_rec.c, I have got a feeling that 7D freezes while pressing that + key might have something to do with the fact that some EOS models uses the + key to start recording RAW, so there might be a possibility of conflict. Just my wild guess.

I am wondering whether there is a way to change these two lines in the RAW_REC.C. It is worth a try I guess:

line 2025-2029:

  /* start/stop recording with the LiveView key */
    int rec_key_pressed = (key == MODULE_KEY_LV || key == MODULE_KEY_REC);
   
    /* ... or SET on 5D2/50D */
    if (cam_50d || cam_5d2) rec_key_pressed = (key == MODULE_KEY_PRESS_SET);

PS:
Can we change line 2025 to this?
/* start/stop recording with the LiveView key */
    int rec_key_pressed = (key == MODULE_KEY_REC);

I don't know, it might work, say worth a try

the great g3gg0 is busy with the mlv writing. his goal is probably writing 2.5k to cf only. when that is achieved. we might hope that the write module can be used to write lv to cf.

the most promising thing for me is to compress lv to 10bit..then all camera will have decent 2.5k raw output. but g3gg0 is too busy.

so we can only be patient

The power management thread seemingly keeps tremendous amount of CPU cycle to itself. There might be some ways to stop the power saving thread while running ML tasks, because the camera is running tasks, no point to do power saving.

I think their Q/DQ methods tie up the CPU too much, these tasks are really slow to complete, and on a slow cpu the things get even worse. There might be ways to free up the CPU from these seeking jobs to let it do what CPU is supposed to do -- like compressing files. I still sturbbonly believe that the DIGIC4 is fast enough to do something like /4 an interger.