Messages

ok, no MLV view in camera 


Thanks wheezl, i got the same card but only 8GB... going try with your settings and with buffer fill method 3 in MLV for see whats happen 

I've also found I can sometimes ride the buffer at 1728x864 (2:1) until the card fills.  So not technically continuous recording but more or less equivalent when you have a smaller card like we do

Card speed is never 100% consistent. I'm surprised it gives you almost full advertised speed.


Card full will cause problems, I'd say stop right before.

I'm actually overjoyed with the speed so I'm not complaining. I'm just trying to figure out if what I am seeing is real and how to most easily replicate it.  Right now 1600x900 manages to hit Continuous after a few seconds so my current "record" of 60.2MB/s peak with this card isn't terribly important to me from a usability standpoint.

I'm just trying to collect information that might be useful to others.


EDIT:   Hahaha "New Record"

I'm curious as to how accurate the reported speed is during recording.  I'm also curious as to wether some frame sizes write to a particular model of card better (sort of like how the cards often perform better in different parts of the benchmark based on write size).

I'm using a Sandisk 16GB Extreme Pro (60 MB/s).

I'm having difficulty producing results with any consistency but using raw_rec with global draw off I have seen writes of up to 59.6MB/s on this card (yay!)

However I'm not really sure how to go about achieving this on a regular basis.  Often a resolution and frame rate that should fall below the maximum performs worse.  For instance if I try to record at 57 MB/s the card will only do 55 but if I ask for 62 it will do up to 59.  Obviously 62 is not possible     I'm just wondering if there is anything obvious I am missing here while I am testing.

I've also noticed that buffer fill method is available in mlv_rec but not raw-rec.   Is this setting unneeded in raw_rec?

If anyone with the same card is interested:

raw_rec.mo
1664x936 (16:9)
Global Draw: Off
Preview: Auto
Card Warm-up: 256 MB
Extra Hacks: On

Framerate: 24
FPS Override: Off

This is 1x from the .bin 

Sometimes it will only reach about 54MB/sec but if I stop it and start again immediately it will go to 59.x   (Perhaps this is working similarly to a warmup?)
On some runs it appears to hit about 59.5 and stay there, other times it seems to go between 57.5 and 59.  It will often start at 54 or so and slowly work its way up to 59.

Like I said I don't know what I should do in my testing to try and get some consistency so any advice would be appreciated.


I just ran another "test" and with the same settings as above but mlv_rec.mo peaked at 59.8MB/sec using Buffer fill method 3.


EDIT:  Added more info.

tutorial
http://www.youtube.com/watch?v=WhiQ9D9vyPI

Yep. Different camera but the same idea.  Just put it into crop mode if you want higher resolutions. 

Today I received a 16gb Lexar 1000x, but I do not understand why I can not get through the video size 1728x972.
This is the message
1984 is not possible in current video mode (max 1728)

It's because the camera skips pixels/photosites in 1x mode. So you only get 1 pixel for every 3.  (this is also why the moire can be bad)

The 7D sensor is 5184 x 3456.  Divided by 3 (every third pixel) you get 1728 x 1152. So you could change your aspect ratio to get more vertical resolution.

If you want to get more overall you need to go to crop mode which is a max of 2512 x 1200 IIRC.

Out of curiosity, what is the possibility of setting DIGIC ISO gain on the 7D?


Is it just something that no one has looked at or is it one of those things that is hard on the 7D?

EDIT: Maybe the wrong thread for this.

You didn't notice it 4 posts above yours?

Be nice   It can be a lot of shit to wade through if one is just getting started.

It claims a 79.9MB/s for 1728x1156 @ 23.976.  I'd be interested to see @ted ramasola test with the latest builds on the cards he has.

I think he was referring to the possibility of 1728x1156 in 1x no?  Possibly useful for anamorphic etc...

EDIT: I actually went back and read that properly... never mind me

On the britom_1% build 1728x786 (2.20:1) is working quite well and 1728x864 (2:1) seems to push the card all the way to 57.5MB/s at peak with the mlv_rec module. After giving that a go ML seems to think my card is good for 57.3MB/s using whatever math is does (avg?) from the last run. Trying 1728x934(1.85:1) *appears* to push the card to 58.2 MB/s but I don't really know how accurate the numbers are during recording.

Because of issues I am having loading all of the modules I only have the ime_* modules and mlv_rec loaded at the moment.

It may be interesting to note that loading the file manager module later seemed to impact write speed for some reason.  Obviously this is just me eyeballing it and not a proper test but I routinely get 55-58MB/sec with it off and 50-55MB/sec with it on.  It might be nothing since obviously I am not doing scientific testing.  I'll see in a bit if it affects anything in playback benchmark.

Sandisk Extreme Pro 16GB (60MB/s)
128MB warmup (Not sure this matters)
Buffer Fill Method: 4

I am having trouble loading the modules from the build of 1%'s work.  Turning on autoload of *some* modules seems to get others to load but there appears to be nothing in the console telling me which is failing. I'll see if I can enable them one by one to find the offender.

Now that I have enabled them one by one, I can get them all to load and can't repro this.

EOSCARD cannot see the CF card ...... how stupid....

Blame Canon.  You will need a card reader for any of this to work.  Luckily they are very cheap.

I'm still hesitant to try the MLV version vs the RAW version of 7D builds.

Those who tried it, does it offer higher resolution over the raw version in 1x and in crop mode?

On my Sandisk Extreme Pro 16GB (60MB/s) I get over 3MB/s more.  This works out to a bump to 2.20 from 2.35 for me in 1x.  It would be interesting to see how it works with the Komputerbay cards you have.

Using mlv2dng is easy enough as well.

Btw, what do all y'all use in the buffer fill method and CF-only buffers?

I find my fastest combination is with buffer fill method 3 and CF-only buffer 8.

The best fill methods for me have been 2 and 4.  2 seems slightly better but that could just be my imagination.   I haven't done any testing where I've isolated the CF-Only buffers and actually properly tested it.

This version has faster write speeds to my card (Sandisk Extreme Pro 60MB/s)    Previously I was right around 50MB/s and now I am getting about 54MB/s.   The card actually benches higher than it performs saving video I'm not sure if playing with "Buffer Fill Method" would change any of that.

I have Small Hacks on and Warm up of 128MB if that matters to anyone.

EDIT:  I am able to go from 1728x736 to 1728x786 23.976p continuous with this build.  Yay for tiny victories

@wheezl @juanmelchor
It's KomputerBay Professional 32GB 1000x UDMA7 CF
with RAW video 1728x972 it's writing 65-70 MB/s  , continuous without breaking a sweat ;-)

Very cool, have you run the benchmark on it to see what it tops out at there?

New Komputerbay 1000x works like a charm! Coninous RAW, no corrupted frames for now. AMAZING! I also did a little stereoscopic test with ML RAW, it looks amazing! ;-)

What kind of write speeds are you getting?

The thing is, I haven't actually changed any of the image processing stuff, I've just changed the way it creates the threads to process the image AND I also cant reproduce the problem on my PC. Your files are fine when I make them.

I was hoping it might be related to the fact that both arrinkiiii and I have the 7D.  But if it works fine on your machine that would be ruled out.

I,d like to try this app on my mac but i crashes before start. I,m on a mac os X version 10.6.8

This pops up in the report

"Exception Type:  EXC_BREAKPOINT (SIGTRAP)
Exception Codes: 0x0000000000000002, 0x0000000000000000
Crashed Thread:  Unknown

Backtrace not available

Unknown thread crashed with X86 Thread State (32-bit):
  eax: 0x8fe44400  ebx: 0x8fe04f4e  ecx: 0x8fe0b83d  edx: 0x00000001
  edi: 0x8fe46dcc  esi: 0x8fe44440  ebp: 0xbfffd8b8  esp: 0xbfffd89c
   ss: 0x00000023  efl: 0x00000246  eip: 0x8fe01065   cs: 0x0000001b
   ds: 0x00000023   es: 0x00000023   fs: 0x00000000   gs: 0x0000000f
  cr2: 0x00001000

Binary images description not available"

As I recall Snow Leopard is a bit odd about 64 and 32 bit as it is a hybrid system.   Right click on the application, select "Get Info" and make sure you are running it as a 32-bit application.  If that doesn't help we'll have to wait for TheUnkn0wn to target your platform.  Though you should be able to upgrade to 10.8 without much pain.

I was so excited to try out the app but it doesn't open up on Macs, if there is an Mac user that got to open up I would like to hear from them because it does nothing on my MacBook Pro.

I just started it and it worked.  What error did you get when you tried to start it ?

You can see the dude with the  blue shirt in the left arm is almost, if not all, in grey.  Also the shoulder and shirt from the dude that got the ball is kind of orange. In the 1.0.0 versions of ml raw didn't give me this strange colors/ghosts.

If you see the trees in the left side is all green you don't see the branches that are brown. Also in the  park bench on the left, the first plank are all green.

https://www.dropbox.com/sh/f4gef0lgmps124z/7s8ZYitJqF

That appears to be the same issue I am having.

Runs fine now on my machine  OS X 10.8.4


Prcoessed a raw file. I'm going to compare the output to rawmagic.

Update:  The output is quite different than RawMagic.

update2: Here are two example frames.  The output is similar wether I pick force linear or uncompressed/lossless.

https://www.dropbox.com/sh/l98j41n4i224at4/3aDsarFWzE




I made no effort to find a decent light

Relevant info from OS X crash report:

Application Specific Information:
dyld: launch, loading dependent libraries

Dyld Error Message:
  Library not loaded: /usr/local/Qt-5.1.0/lib/QtWidgets.framework/Versions/5/QtWidgets
  Referenced from: /Users/USER/Downloads/Magic Lantern RAW - 1.0.0.app/Contents/MacOS/GUI
  Reason: image not found

Looks like the Mac version doesn't include its own copy of Qt5.  Since it is a 322kb zip that is a pretty safe bet.  I'd try to install the package version but I already have Qt in my dev environment and have no more room on this pesky SSD.

u welcome 

Uhmmm... with this build/version never go above 600. In this moment im able to record continuous 1728x 576 by 3:1  My card is also slow for raw, it's a sandisk 8Gb 60mb/s   ...but even with a 1000x the record speed/frame rate is almost the same because of this build/version for the 7D. Hope this limitations and the Lv freeze will be fix soon.

Actually I get 1472x626 on my Sandisk 16GB 60mb/s    I haven't managed any higher than 626 though.

Thanks. And whats the best ISO using for photo/video/raw video for now?

I have been getting the best results from 160  YMMV.