Messages

inside the fps override function, there are some sub-menus (low light, exact fps, ...) maybe would be good idea to put these new fps inside a new category: "ntsc fps". I calculated them to be multiples and submultiples of 23,976 and 29,97, (values below can be turned into these by multiply by an interger, good to fps conversion) (values above divide by 2 or 1,5 good for slow motion)

0,999
1,998
2,997
3,996
4,995
5,994
7,992
11,988
14,985
23,976
29,97
35,964
44,955
47,952
59,94

This is just to celebrate my post number 100. Now I am a Member. Thanks!

adding 23,976 to be one of the exact fps options inside the fps override feature was great idea.

what about to add:

5,994
7,992
11,988
14,985
29,97
35,964
47,952
59,94

these would be great also to use with raw video in 600d, because different resolutions needs different fps to keep under 21MB/s and using multiples of 23,976 is great for NTSC TV compatibility

I think in terms of stability and reliability you can consider your job done, of course improvements can always happens, but things are already working ok now. I cannot get the first shoot without magenta frames when canon menu is in 1920x1080, but who cares? we all know we need to set canon menu to 640 x 480 25p, picture quality to sraw and reboot camera, these settings solves everything, no skip frames, no magenta frames when keeping fps and resolution combo under 21MB/s.

Go on focusing the job on the overlay (indicators) position as you said, and if you can enable the fps list above in the exact fps override menu it will be great also.

thanks

Hi 1%,

Thanks for all your efforts and great work.
Last build is working ok for me with picture quality in sraw in ml menu, and canon menu in 640x480 25p pal.
I can do 768x432@35p, 960x544@24p, 1344x768@12p, 1664x944@8p all using fps override and global draw "auto off when recording" with canon lv preview
No skip frames, no magenta/pink frames.

Please, remember to set the canon as the default option for lv monitoring in raw menu, it is working flawless with the settings above.

Keep rocking!

Lots of tests yesterday, Sunday, and things are working ok. Just need to keep Picture Quality in SRAW and Canon menu in 640 x 480 25p. So I do a combination of resolution and fps override below 21MB/s and no skip frames, no magenta frames. I can use canon LV preview always,  no problem. The Global Draw off when hit record helps a lot, because I can look at histogram, focus peaking and zebras before start record and it disables when recording and enables again after stop rec. good feature.

go ahead, let us see what you get...

you can also use underline "before and after" in the code:

_5247F_

_3984MB_

_20.8MB/s_

I believe the programing language have solutions to this, but I know nothing about programing...

for the internet this works:

http://en.wikipedia.org/wiki/Markdown

http://en.wikipedia.org/wiki/Punctuation

well, we just give ideas... programing is up to you!...

to avoid numbers contract use two underline between them:

<**.>__5247F__3984MB__20.8MB/s__Jun02-0001.RAW

in the source code like this:
<**.>__
5247F__
3984MB__
20.8MB/s__
Jun02-0001.RAW (between date and number in file name do not use underline, use hifen "-")

take a look in this design:

Remove all the titles and keep just what really matters, just one line at bottom, very low bottom:

<**.>   5247F   3984MB   20.8MB/s   0001.RAW

where:
<**.> is the buffer
5274F is the frame count
3984MB is the file size
20.8MB/s is the datarate
0001.RAW is the filename

Would bee good idea to put Canon LV preview as the default when enable the raw rec, to avoid we keep changing it all the time.

Global Draw goes OFF when hit rec, it is working, but just works in canon option, does not work in auto option, so move canon as the first (default) option will be good.

Also it will be good to enable a STOP button when files are in playback. In file browser, when file is playback, the only way to stop is to press half shutter, then we need to navigate again to go to file browser again. a stop button can stop playback and go back to the file browser folder.

I found 1664 x 944 @ 8fps useful, maximum possible for 8 frames per second.

the 640 x 480 25p Live View Preview does not cover this resolution at the sides, but raw video records ok, no problem.

no skip frames, no magenta frames.

so the overlays must allow to see this white frame from 1664 x 944 also.

overlays in just two lines, one near top and one near bottom will be the solution.

See the 1664 x 944 white frame and the overlays inside the 640 x 480 LV preview:

Hi,

Please, what would be the smallest device to install Canon Utility and connect to camera to change Picture Styles on set location.

The EOS Utility just install in Windows XP and above...

Would be great to have a version of EOS Utility to install on a SmartPhone and connect to camera via USB to change PS

Even a Java version to work in default Cel Phones...

thanks

Overlays in the bottom will be good, maybe you can do it in just two lines instead of three as we talk in previous post.

take a look at these two pictures. they show the overlays inside the 1344 x 768 white frame.

my suggestion is to put the overlays a little more to the top to go out of the recording frame and also a little more to the right to get out of the black area of the LCD.

you can also put some information above the white frame, near the top of lcd and some information below the white frame, near the bottom of lcd.

My request about 3,2:1 aspect ratio is to make possible 1280 x 400 (the maximum resolution for 600d datarate with 1280 width @ 24p)

about make the overlays just two lines, this is to avoid overlays to be inside the white frame when using 1344 x 768 resolution

I found two lines could solve, but if you need to write three lines, try to put them near the top or bottom of LCD, to make them appear outside the 1344 x 768 frame.

when using 640 x 480 25p in canon menu there is image in the top and bottom of LCD so the overlays can be near the top or near the bottom of LCD, leaving the 1344 x 768 white frame clean to see what we are recording.

I think we do not need to worry so much about magenta frames anymore, setting canon menu to 640 x 480 25p and fps override to 24p is enough to solve this issue, at least in the last hours no more magenta frames with these settings.

also auto hide global draw is not so much important, we can disable it in the ml menu.

what about to take a look at the requests I did in last posts? will help a lot. thanks

I replaced the bin and the mo in my card with the alocatte fix version. Maybe my camera is still loading the old one? Is this possible?

I can see a color bar showing the memory when I click Q to see the malloc total.

Allocate Fix build feedback:

same behavior as before shooting 960 x 544:

if canon menu is set to 1920x1080 24p the first shoot is corrupt and second shoot is ok

if canon menu is set to 640 x 480 25p and fps override set to 24p, first shoot is ok

secret is already found: 640 x 480 25p in canon menu + fps override = no more magenta frames!!!

another feedback: global draw was not turned off while recording. I need to turn it of in ML menu

I also have a request to enable 1280 x 400 in 3,2:1 aspect ratio and 832 x 624 in 4:3 aspect ratio
(maximum resolution for these widths considering the data rate)

thanks

I have a request which will be usefull for everybody:

The overlays are inside the 1344 x 768 frame,  so changing it from three lines for two lines and put it a little more up to be above the 1344 x 768 frame. (I would like to use the frame at center to use the center of the lens)

change this:

Buffer usage: <**.>
Capturing frame 765...
M01-1748.RAW 833 MB, 19.3 MB/s

to this, (and a little more above the 1344 x 768 frame):

Buffer usage: <**.>   Capturing frame 765...
M01-1748.RAW 833MB, 19.3 MB/s

or put these two lines design below the 1344 x 768 frame

thanks

more tests using Canon menu set to 640 x 480 25p:

768 x 432 (16:9) @ 37,698 fps (actual fps from 40 fps override) working ok (great for slow motion) 250% scale to fit fullhd, 167% scale to fit 1280. If 37,698 is too much, try 35 fps override.

960 x 544 (16:9) @ 24 fps working ok, best 16:9, 134% scale to fit 1280 (133,33% scale) or 200% scale to fil fullhd

1344 x 768 (16:9) @ 12fps working ok, best highest resolution for 600d, uses almost all the sensor area, 12fps can turn to 24fps in post... also allows a small crop to delete borders to get 1280 x 720 after processing to 24fps, no scaling needed for 1280, 150% scale to fit fulld considering border crop to remove border artifacts after converting to 24p

Did another sequence of tests:

By first shoot I mean the first time you hit record after turn the camera on.

When canon menu is in 1920 x 1080 24p, the first shoot is always corrupt. I did a test moving the camera during the shoot and I can say for sure the magenta frames happens in the same moment when there is a jump in image monitoring in LV while recording.

In 1920 x 1080 24p the second shoot is always ok.

The first shoot is ok when using hacked mode - no preview.

Thanks for the advice about 640x480 preview. I did set the Canon menu to 640 x 480 25p and fps override to 24p. So I reboot the camera and start recording 960 x 544 @ 24p and there was no jump in Canon LV monitoring and no magenta frames in the first shoot. No skip frames also.

It seems things are perfect now!!!

My first shoot is corrupt when I leave Canon LV on

I did a try with canon LV off (hacked no preview) and the first shoot was ok

but I need LV, I cannot work blind!

Thanks @Alia5

My first shoot is always corrupt, but second shoot and others are OK
My settings are similar, but other things disabled...
I do not use fps override, I set 1920x1080 24p in Canon menu.
I used 11,988 fps override to record 1344x768 without skip frames, and 37.8fps override in 768x432 no skip also
It seems your card is slow, I can record 20.8MB/s 960x544 @23,976 fps and no skip frames in 4gb file.
I use Sandisk Extreme 32GB 45MB/s, this card performance is perfect for RAW.

From last install (Squeeze build) until now things are ok for me (from second shoot and so on...)
It seems first raw shoot is something like "heating the tires" in F1 first round drive...

raw recording disabled cpu is 30-32%
raw recording enabled cpu is 38-43%
(before recording)

if raw recording overlay is in bottom of screen we can see cpu usage while recording.