Messages

1

Other experimental builds / Re: 12-bit (and 10-bit) RAW video development discussion

« on: December 01, 2016, 08:59:13 PM »

Tested Eos M running Crop_rec nov30th build from DeafEyeJedi.

Recording Raw 10 bit @ 1728x692 (2.50:1) using movie crop mode works smoothly, with live view display working great during raw REC.
Playback of the last 10bit raw clip using mlv_play and raw_twk enabled works great, but there are no controls to start, stop, track back or track forward. I can interrupt the raw playback with a half-shutter press, and return to normal liveview. I can play the clip as many times as I want if I keep interrupting it before it finishes, but if I allow the clip to play until the last frame, the camera appears to hang on that frame. A half shutter returns to liveview. Afterward, raw playback soft hangs on a black screen (half shutter returns to liveView). The only way for me to see the raw playback again is to power cycle the camera. The camera is not crashed or frozen, though.

2

Other experimental builds / Re: 12-bit (and 10-bit) RAW video development discussion

« on: November 11, 2016, 07:45:03 PM »

(2016Nov09.EOSM202)

I don't experience any crashing on the Eos M when recording with either zoom mode or 3x crop mode enabled.
Video playback works too, in both color and b&w. Video is scrambled.  Raw @ 10bit. Tried with SRM Job ON and OFF.
I can record multiple clips back to back with no crash, aside from the expected preview frozen only during REC.

If I shoot in (mv720 I believe?) (no crop, no zoom) then I experience the crash mentioned, and have to pop battery. I tried with SRM Job on and off, and the crash still occurred, followed by the invalid header size error when playing back the clip that was attempting to be recording during the crash. I can still play the other clips fine that were recorded using 3x or zoom, but scrambled as expected.

3

General Development / Re: Squeezing the last bit of performance out of MLV Lite (for testers)

« on: April 12, 2016, 10:34:34 PM »

Eos M comparing 4/12 nightly and a1ex's newest raw_rec.mo (MLV Lite 1.1):

Average of 160 frames (5 sample test) at 1728x736 5x @ 23.97 fps (4/12 raw-rec.mo mlv lite 1.1)

Average of 228 frames (5 sample tests) at 1728x736 5x @ 23.97 (raw 1.0 nightly)

Raw rec 1.0 still offering slightly higher performance on Eos M. ML's displayed megabytes/sec was at around 36mb/s for MLV Lite 1.1, and around 40.5mb/s for Raw 1.0. I don't know if that's important all, but thought I'd mention it.

4

Modules Development / Re: MLV Lite

« on: March 08, 2016, 02:06:09 AM »

Eos-M Nightly 2/29/2016

5x Zoom Raw, Frame size: 1728x736 aspect 2:35 @ 23.97 fps (fps override enabled)
MLV 2.0            - 175 to 176 frames (7 seconds)
MLV Lite            - 150 to 160 frames (listed as "zero frames")
ML Raw 1.0    - 223 to 229 frames (9 seconds)

5

General Development / Re: Dealing with Focus Pixels in raw video

« on: February 01, 2016, 07:57:26 PM »

@dfort

I took the simple silent image using simple .mlv, here is a link to the original .mlv file:
 https://drive.google.com/file/d/0B73VZPdpR0_hMHJ6S0VOV0t2UE0/view?usp=sharing

I tried to reproduce the same lighting situation with a simple silent .dng. Link to here:
https://drive.google.com/file/d/0B73VZPdpR0_hdU81ODVRR3BpQlk/view?usp=sharing

The vertical columns on the left and right sides are visible in both files with some fiddling. Let me know if you need any other files.

6

General Development / Re: Dealing with Focus Pixels in raw video

« on: February 01, 2016, 06:22:29 AM »

Compared the Eos M focus pixels from the 80000331_2592x1108 pbm file to the 5x silent image. Coverage looks excellent, and I haven't noticed any out of place pixels yet.

Looked at 80000331_1808x727 in full screen mode, coverage looks excellent as well.

After taking some sample silent pics in full screen mode (1808x727) on my Eos M, I'm noticing some strange extra pixels that appear to be vertical rows of focus pixels. The vertical pixel rows aren't on the 1808x727 pixel map, any idea if these are actual focus pixels or fixed pattern noise? I tried many different color backgrounds, but I have been unable to produce a completely clean example file yet.
It took a lot of contrast and color channel manipulation to spot them.

Small crop preview:


Full size tiff uncropped (7mb, dirty example): https://drive.google.com/file/d/0B73VZPdpR0_hcnVobUhVb2Z0a0k/view?usp=sharing

7

General Development / Re: Dealing with Focus Pixels in raw video

« on: January 31, 2016, 07:37:05 PM »

@dfort

Thank you for the detailed instructions! They worked perfectly and the script executed. The .pbm file is building right now. Success!
I'm using the focus pixel file from your newest bitbucket 2016-01-31_Focus_Pixel_Map_Files_testing.zip archive.

I also corrected my other mistake (I am now using **331 instead of **326.)

8

General Development / Re: Dealing with Focus Pixels in raw video

« on: January 31, 2016, 06:57:54 AM »

@dfort
I'm happy to help test Eos M focus pixels, but sadly I've hit a brick wall trying to output an image file from cygwin.
I seem unable to figure out the proper syntax for executing the script in cygwin. I already formatted it for linux line returns with notepad++, but after running:

$ /usr/bin/fpm2pbm.sh 2592x1108 80000326_2592x1108.fpm
sed: can't read 80000326_2592x1108.fpm: No such file or directory

I have both my fpm2pbm.sh & 8000326_2592x1008.fpm files located in the usr/bin/ folder. Pretty sure I'm doing something wrong, but I'm inexperienced with cygwin. Can you instruct me on how to execute the script properly?

9

Camera-specific Development / Re: Canon EOS M

« on: December 31, 2015, 03:49:24 AM »

Follow up for ML Movie Crop Mode timer values:

1920x1080 @ 30 fps (ML Movie Crop Mode)

Desired FPS: 65
Actual fps: 30.720

FPS Timer A: 532 (FT-8)
FPS Timer B: 1958 (FT+622)

Shutter min: 1/34.18
Shutter max: 1/3538.20 and 1/3759.40 (idle variance)


1920x1080 @ 24 FPS (ML Movie Crop Mode)

Desired FPS: 65
Actual fps: 24.581

FPS Timer A: 532 FT-8
FPS Timer B: 2447 (FT+1111)

Shutter min: 1/34.16
Shutter max: 1/3538.20 and 1/3759.40 (idle variance)

Side note: While testing FPS Timer B values above FT+1120, ML interface froze and I was unable to shut the camera off. I ejected the battery, and the problem occurred again. After quickly accessing ML menu and lowering Timer B, the problem did not happen again. I attempted to reproduce, but was unable to get it to happen a third time.

@Licaon_Kter You were right about the FPS, thank you!

10

Camera-specific Development / Re: Canon EOS M

« on: December 30, 2015, 08:48:10 PM »

Yes, artifacts begin to disappear as the Timer B is increased.  Below are the lowest safe limits I could find that keep the maximum shutter speed below 1/4000. At the high shutter speeds, there is still an alternating variance that occurs, causing the video to rapidly flutter between  exposure levels. It is not noticable at low shutter speeds, as the variance is 0.02. At shutter speeds in excess of 1/3000, the variance is over 1/200.

1920x1080 @ 30 fps (Canon Menu)
Desired FPS: 65 (from 30)
Actual fps: 30.389

FPS Timer A 520 -8 (no user change was made)
Fps Timer B 2025 (FT+55)

Shutter min 1/33.79
Shutter max 1/3619.80 and 3846.20 (idle variance)



1920x1080 @ 24 fps (Canon Menu)
Desired FPS: 65 (from 30)
Actual fps: 30.389
Fps Timer A 520 -8 (no user change was made)
Fps TImer B 2025 (FT+55)

Shutter min: 1/33.79
Shutter max: 1/3619.80 and 3846.20 (idle variance)


1280x720 @ 60 fps (Canon Menu)
Desired FPS: 65 (from 30)
Actual fps: 30.389
Fps Timer A 520 -8 (no user change was made)
Fps Timer B 2025 (FT+55)

shutter min: 1/64.84
Shutter max: 1/3619.80 and 3846.20 (idle variance)

ML FPS Override menu still displays "From 30" even when resolution is set to 1280x720 @ 60 fps in the canon menu, maximum actual FPS idles at 30.389.

11

Raw Video Postprocessing / Re: MLVProducer for Windows

« on: December 29, 2015, 10:12:05 PM »

I did some further testing, and it appears that the preferences for "Default Codec" aren't saving until the program has been quit and re-open. I tried "ProRes 4:4:4 FAST" again, set the prefs, quit and relaunched the program. This time I got a ProRes encoded video file after exporting, but it was ProRes 4:2:2.  Hope that helps.

Have a happy new year!

12

Camera-specific Development / Re: Canon EOS M

« on: December 29, 2015, 01:45:49 AM »

magiclantern-Nightly.2015Dec21.EOSM202

Ran the following FPS tests. Max user selectable FPS topped at 70. Tests run at both 65 and 70, no change between them.
Resulting displayed fps results:

1920x1080@30 (no crop mode)
Actual fps: 31.237
Lowest shutter I can select is 1/34.85. The next step after that results in flashing video with horizontal pink bands, and a shutter speed of 0" -6 degrees.
Highest selectable shutter speed: 1/8791, 1 degree.

1920x1080@24 (no crop mode)
Actual fps: 31.237
Lowest clean shutter: 1/34.85. Next step also results in flashing video with horizontal pink bands, and a shutter speed of 0" -6 degrees.
Highest selectable shutter speed: 1/8791, 1 degree.

1280x720@60 (no crop mode)
Actual fps: 31.237
At this setting, I was unable to reduce my shutter below 1/68.91 @ 163 degrees. Shutter speed idled between 1/68.83 and 1/68.91.

1920x1080@30 fps (Movie Crop Mode)
Actual fps: 45.022
Lowest clean shutter: 1/52.81. idles to 1/52.86. Next step, shutter 0" -162 degrees. Flashing video with horizontal pink lines.

1920x1080@24 fps (Movie Crop Mode)
Actual fps: 45.022
Lowest clean shutter:1/92.54 idles to 1/92.68. Next step, 0" -293 degrees. Flashing video with horizontal pink lines.

13

Raw Video Postprocessing / Re: MLVProducer for Windows

« on: December 27, 2015, 06:56:26 PM »

Hi, new to the forum. I would like to thank you for all of the hard work that you have put into MVLP.  It is a fantastic program, and it produces beautiful results!

The only problem I have encountered, is that I can not seem to export as ProRes when I have "ProRes FAST 4:4:4" or "ProRes 4:2:2" selected in the settings menu: Default Codec. The video files created are AVCHD .mov files. If I select "TIFF" as the default codec, the resulting exported .mov files are ProRes 4:4:4.

Running: MLVP Alpha 1944.
Windows 7, 64 bit.