State of ML RAW Now

Hey Thanks. That reslution should look pretty sharp in 720p as well. On a related note, if one is recording at 1920x672, is the record time longer than 1920x1080 24fps? I am trying to decide between a 128GB card or a 256GB card. 128GB will give ~25min at 1080p. If the 60p mode might yield more time it could sway me towards the 128GB. Thanks

Edit again...Just read you only get 4 second of record time at this resolution. I need to do some more research to see if 720p60 continuous is on the table.
 
Last edited:
Worzel.... You can go back and forth between 1.13 and 1.23 on demand... You are not stuck with either one and litterally takes two minutes to update.
 
A1ex with another mkIII owner are now testing ML for 5d3 for firmware 1.2.3. He'll announce it tonight or tomorrow together with install details.
 
ML Raw, on a 5D3, can do something like 1920x672 at 60p continuous, stretching it to 1080 still looks good.

Are you saying stretching only the 672 to 1080 in height? Wouldn't that look distorted??

Or do you mean scale it up till the height reaches 1080 and then trim the width back to 1920? Does that mean when you are shooting your footage that you have to compose it knowing that you will have to trim the sides when finalized??
 
HUGE NEWS indeed.

First post in this thread: http://www.magiclantern.fm/forum/index.php?topic=11017

Quote:

What's hot:
- bootflag issue solved!
- installation is really easy (simply unzip the files on the card, update firmware and you are ready to go)
- uninstallation is equally easy (update firmware and follow the instructions)
- EosCard is now optional (might be required for 64GB cards or larger; didn't try)
- ML restores itself after formatting the card (man, that komputerbay card is fast!)
- you may install on any card combination you may think of.

Also it was mentioned in the thanks given section.
Quote:

Thanks to:
- chris_overseas for initial porting and testing
- horshack for advice about safely toggling the bootflag
- Audionut for early builds and support in the early porting thread
- marekk, pompeiisneaks, jpaana, rufustfirefly, sinubis and others for early feedback and small fixes
- mk11174 for getting the 700D port in sync in this one
- everyone else who volunteeres their time to make a great community project.
 
Last edited:
I'd just like to remind everyone that money is the mother of invention. You see the thanks above to horshack about safely toggling the bootflag? Well, horshack wanted to sell his 5D3, but he didn't want the bootflag issues to hurt the camera's used value. So... he took a chance and found a way to remove it many months ago so he could sell the camera. LOL, like I said, money money money. And now I say, whatever the motivation, I am glad he found it!
 
Are you saying stretching only the 672 to 1080 in height? Wouldn't that look distorted??

Or do you mean scale it up till the height reaches 1080 and then trim the width back to 1920? Does that mean when you are shooting your footage that you have to compose it knowing that you will have to trim the sides when finalized??

You only stretch the height…. in AE you can "fit to comp". The reason is that 60fps raw is squeezed in the shot…. when you unsqueeze it, it looks fine again.
 
You only stretch the height…. in AE you can "fit to comp". The reason is that 60fps raw is squeezed in the shot…. when you unsqueeze it, it looks fine again.
Are you saying that if you do not stretch the height, it will look funny at 60p?

I don't understand the purpose of making 60p at 1920 X 672 if its meant to look normal at 1080.
 
I don't understand the purpose of making 60p at 1920 X 672 if its meant to look normal at 1080.

line skipping by canon. It actually skips more in 60P than in 30 or 24. Thus if you looked at native h264 1280x720 its heavily aliased. I guess thats how they can achieve the framerate.
 
Are you saying that if you do not stretch the height, it will look funny at 60p?

I don't understand the purpose of making 60p at 1920 X 672 if its meant to look normal at 1080.

Yes... it will look squeezed. I think like Ted says, they had to do it this way to fit the data into the maximum achievable rate of mb/s. You can't tell it's been unsqueezed afterwards. Heck, if you deliver to YouTube or Vimeo, it will be messed up anyways.
 
Back
Top