Messages

Here is a sample video I just made using 720p@50fps in RAW (when Vimeo will finish to render it) : https://vimeo.com/97605568
[UPDATE] I don't know why but Vimeo seems to not offer HD resolution for this video (why ?)

Another test, this time in Full HD@25fps (1920x1080) recorded in crop mode : https://vimeo.com/97607131

Didn't know this : "Vimeo allows Basic members to upload only one HD video per week, so if you upload two HD videos within the same week, only the first will show in HD. The other will appear in SD only."

I'll try to repost these videos in HD...

Here is a sample video I just made using 720p@50fps in RAW (when Vimeo will finish to render it) : https://vimeo.com/97605568
[UPDATE] I don't know why but Vimeo seems to not offer HD resolution for this video (why ?)

Another test, this time in Full HD@25fps (1920x1080) recorded in crop mode : https://vimeo.com/97607131

Yes I updated the code yesterday and asked for a review. I hope it'll be ok this time. O

The 7D has "5x" (about 3x) crop mode which is essentially free of aliasing artifacts and can reach fullHD resolution and above (not necessarily continuously...), I don't know if 50D also has this feature ?

I already saw some posts about 50/60 fps footage on 7D here.
However, I just tried it on a nighty build and it seems to work ok but you have to :
- set the video mode in the Canon Menu to 720p (1280x720@50/60fps)
- you can adjust the real capture resolution in ML menu (MLV), I could record continuously using 1344x540@50fps
- the recorded footage is stretched vertically by a factor x1.4 (or x1.666 ?), you have to fix it in post prod which may introduce some more aliasing.

Today I updated the pending pull request I pushed some time ago with fps override in RAW recording. This code is ported from TL and there are parts I don't fully understand, but now it is working for me. For example I was able to record in 5x crop mode in 25fps continuously in 1728x972 when the default 29.97fps isn't continuous.
I hope this could be soon integrated in the main branch.

Yes, i saw that, THANK YOU SO MUCH !!!   Why it's taking so much time to validation?  The dev's need to try the code first? 

Yes.

Do you think back porting the audio also?

I'll try to look at it but before that I need to figured out how this work in hardware... Do I need to build a custom audio cable ?

Yes, that 2  features are very important and needed very bad.


Essential features not yet implemented.
1. FPS over ride

Last week I back ported FPS over ride in RAW rec mode (not H264) from TL, I pushed a pull request to the main that await validation.

Anybody has a idea how external USB/Bluetooth GPS connected to a WFT grip should be acceded from ML code ?
I have a WFT-E5 7D grip with a tiny bluetooth dongle connected to it (not the Canon one which is very big and expansive !) and a BT GPS. When all is connected the pictures I take are geotagged and I can see the coordinate when reviewing them but it could be useful to read the location in realtime for the use cases you have mentioned.

I have run some tests with the last nightly build for the 7D and wend i preview the files in camera and return to Lv the box have move down. Need to turn off and on the camera for return to the right frame in Lv. Im recording at 2.35:1.

Same here, the box move down after preview. I used 16:9 ratio (7D).

Very nice, loved it ! I think it capture and depicts very well the feelings and what I saw when I was visiting Tokyo and Kyoto last year.
Also great images, editing and music.

We need a volunteer with skillz to compile an updated version for the 7D. Anyone?

Fixes to make audio working are still pending to be incorporated in the mainstream ML, the pull request https://bitbucket.org/hudson/magic-lantern/pull-request/377/back-port-some-code-from-tl-to-make-audio awaits...

I pushed a new pull request for 7D audio recording fix because the issue g3gg0 had with the previous one. It was working fine for me but it may be a case with wave recording with the things I read there so this time I left out the wave recording, only focusing on mlv_snd.
I hope it's ok this time !

The first benches with the usb hard drive as target aren't glorious, I could only achieve 864x486 at 23.976fps continuous recording (about 16MB/s) but it works ! I'll check this again with a "real" USB hard drive because actually I only used a USB to SATA adapter, maybe this is not optimal speed wise...

I have checked that the USB hard drive is seen as "C:" when connected !
I'll try to substitute the 'A:' used in mlv_rec filename with 'C:' and do some bench... I'll also try the 5DMkIII disk spanning substituting the 'B:' drive with 'C:'.
Even if the USB connexion is too slow for realtime recording I can imagine this could be used to move RAW files from CF to HD, making room on the CF card for more recording.

Why not ? As USB 2.0 should give around 30MB/s write speed, perhaps I could record 720p continuously.
It should also be possible to do write spanning on CF and HD like it is possible on 5DMkIII with CF and SD !

Hi !

I own a 7D and a WFT-E5 grip that can be used to plug USB device like USB key and hard drive (and Bluetooth adapter for GPS).
I tried to record RAW video with mlv_rec but alas it insists to record on the compact flash and not to the hard drive when this one is connected and configured to be used as the default target (it works with pictures, they are well recorded on the USB drive).
I think the USB drive may have a dedicated drive letter or mount point that mlv_rec should use to redirect the writing there, but how to discover this ? Does somebody have some experience with WFT and Magic Lantern ?

You missed CONFIG_AUDIO_CONTROLS in internals.h

Thanks ! I updated the pull request.

merged and looks fine, thanks

You're welcome, thanks for the merge.
I pushed another pull request with what I think is minimal changes to make audio recording works in mlv_snd with 7D (I left out 6D, EOS M because I can't test on this plateform).
The audiometers are only working when recording for now and not when idle, I must have missed something...

[Magic Lantern]

thanks for your effort. but please do that for Magic Lantern, not Tragic Lantern.
TL is no longer being supported and merged back into ML.

create a fork of ML using bitbucket, add your changes there and create a pull request.

I just back ported this to ML, a pull request await there !

The first thing I noticed when trying the latest ML instead of TL in my 7D is the lack of audio recording with mlv_rec, I think it'll be the next thing I'll look at.

I also saw this behavior with the latest build I compiled yesterday, I don't measured it but it took several seconds (perhaps 15s-20s) between the instant I push the rec button and the instant it start effectively recording.
Actually I only have a "slow" 16Go CF card because I had to send back my flaky 1000x 64Go CF and still wait for the replacement...

[Edit] I don't want to add fuel to the fire in any way but I only tested this on the latest TL code because I'm using a 7D
[Edit] I'm also ready to join the force to do back porting from TL to ML

Hello,

I somewhat ported from raw_rec to mlv_rec the clean display showing a camera icon in green/yellow/red when recording :

https://bitbucket.org/vyskocil/clean-mlvrec-display/commits/20d535cb39056f03cddc56d3f57dee7239926f63

There is now a menu setting that let one choose between no status display at all, camera icon and time of recording and the debug display we are used to until now.

How this could be merged in TL if it is of some interest ? [EDIT: I just made a Pull Request toward TL]
I'm also interested to do some back porting to the official MagicLantern from the TL branch.

Try CMD+I on Resolve App then check Prevent App Nap

This looks great m1ke !
I also been fed up of the debug display while raw recording, but for now I just commented it out in the code...

From time to time the CF card where I installed Magic Lantern is "trashed", all seems to work but when I power cycle the 7D, it don't boot ML anymore, the camera says that the card is not formatted (the Mac also) then I must format it, re-install the boot and ML.
This seems to happen when it happens just after I had installed a new version of ML (compiled from Tragic Lantern repos) and tried some modules but  mainly raw_rec.