Messages

if i have to spend 2k euro to buy a new laptop because my 1k euro current one is not enough to run a free software (davinci lite)... it is like to take advantage of a free refuelling for lamborghini's cars... for pc's the problem is easy and cheaply solvable, but for laptops is often cheap to buy an alternative software or using one yet bought and stick with it. this is just to point out the unhappy choices that some software houses makes from time to time and to point cheapers alternatives in some situations like having a laptop.

Everyone grades in acr. I prefer using speed grade: it is part of the master suite but nobody seems to take advantage of it. All speak about acr or davinci resolve like there is nothing else. But speed grade is nothing less than davinci, it eats less resources (gpu ram is always not enough) and is windows style at least (try to understand how to import a clip in davinci the first time and how to close a dialog... ahah!). Just my hints contribution...

I put the 1088x480 footage into a 720p sequence in Premiere and simply 'scaled to comp' and then my entire edited sequence into a 1080p sequence and used Instant HD and upscaled it to 1080p. Looks alright I think, though I'd probably just stick to 720p next time.

You did a great job: things that appear blurred are blurred by lens and wanted as is, because the sand touched by waves and waves on the horizon are very crisp and detailed, so upscaling is very good indeed ! Very good, compliments !

Here's my first attempt at shooting RAW. The workflow is a lot bigger, but worth every second I think!

Shot in 1088x480 @ 24 frames per second with a 16GB Sandisk Extreme 45mb/s.

RAW > RAW2DNG > 14-bit DNG's > Adobe Camera Raw > .tif image sequence > Adobe Premiere CS6 > upscaled to 1080p > rendered out to .H264

How did you upscaled it ? What you used ?

what are the technical reasons for which we cannot use 10x crop mode for raw video recording just to help finding a solution?

ginger crashes every time twixtor is applied to the clip

so when u go into 5x mode and u change the raw resolution, the bar that pops up showing u what your recording  area is. Is it showing u the real form factor. I notice its there when your in normal mode, does it adjust for if your in normal mode or 5x mode.
or is it guessing?

never tested it with your requested precision, if you have time to test it, i'm interested in your results, thanks

I don't think it's correct to call it either YUV or 4:2:2. IMHO, of course. Cheers!

Yes, you are perfectly right ! It is simply RAW, so no YUV represented yet, and no chroma and/or luma subsampling at all, right !

I did some qualifiers in resolve for secondaries and by the quality of the keying (no blocking, compresion artifacts etc) I guess is 422 but I´ve to test it with hair in greenscreen to tell you the truth. Or maybe someone can give us a more detailed explanation about chroma subsampling here..

Ok, I figured out from info around the internet and inside the audio narration of this video : http://www.how-to-diy.org/8OFpfFiXrDDLOY/Raw-%22Video%22-on-Canon-DSLRs-with-Magic-Lantern.html

H264 video is YUV subsampled to 4:2:0
RAW video is YUV subsampled to 4:2:2

Great values ! 

Just to be sure: do 550d raw video have a chroma subsamplig 422 or 420 or something else? And do the one of h264 is the same? Many thanks!

Quite cheap greg! I will buy all of them!

So, guys, is the information of the top post still up-to-date?
Where should I start my investigations to dig into that?
Are there any new clues and ideas how to achieve more memory on ours 550d's?

Yes it is kept up to date by me, as soon as devs will inform me about their developments or as soon as I see developments on this or other threads

strange happened to me now.... it seems i cant get the raw video size past 1728

someone have any idea?

i was able to do it yesterday playing with it... (even with 1fps)
damn i still have the raw file in my laptop for 2512x1080 @14fps
now i it keep saying more than 1728 is not supported in video mode

You must activate 5x zoom before going to ml menu to select resolution

Anyone wanting to try out Alex's experimental variable buffer Raw Record, this build is all updated and has AUTO ETTR, File Manager and Pic View Module as well.

http://www.mediafire.com/download/hgiq49uyo3uk7pl/ML_550D_June_20_2013_Update.zip

Wow ! We are among a head-to-head contest here ! what buffer strategy will win ? time will tell !

In the meantime, also your build was put on the headpost ! Many thanks mk11174 !

The new and latest xaint build version with better buffers is ready to download : the headpost is fresh updated ! 
Thankyou xaint, from all of us ! 

Sorting code makes a huge differ on this camera. I added the sorting code to Magic Raw, it was already on the Tragic Raw

So, do this can be inserted in the raw rec module with a conditional compile statement only for 550d? If the conditionals are not implemented for this module, do we can implement them? So, we can take advantage of different strategies on different cameras! Let me know!

Well.. small formatting quirks for the new wiki (which seems down anyway)

Do the new wiki is this ? -> http://magiclantern.wikia.com/wiki/Magic_Lantern_Firmware_Wiki     ...Or it's another one ?

I can see now it's online...

All the scripts are in the doc directory (mkdoc.py is for pdf, mkdoc-cam for help bmp's, wikidoc for wiki output - but needs some tweaks).

Your work is Amazing ! but often the best things are not so evident to all people, so now I hope to give it the right spotlight on this ! I just changed the head post to reflect all your precious infos given here, many thanks !

Also, can you tell me the problems to the wiki script, so we can see if someone (or myself maybe) is able to solve them ? Many thanks !

Here's how the document is split:

Code Select Expand


include(o, "FEATURES.txt");
include(o, "MANUAL.txt", 1);
include(o, "MENUSTART.txt");
include(o, "MN-AUDIO.txt");
include(o, "MN-EXPO.txt");
include(o, "MN-OVERLAY.txt");
include(o, "MN-MOVIE.txt");
include(o, "MN-SHOOT.txt");
include(o, "MN-FOCUS.txt");
include(o, "MN-DISPLAY.txt");
include(o, "MN-PREFS.txt");
include(o, "MN-DEBUG.txt");
include(o, "MENUEND.txt");
include_indent(o, "FAQ.txt");


Great ! Do we can add menus to this list ? Where is located ?
What visual editor can be used to edit this manual ?

Very good ! So, i have some questions just to clarify (excuse the stupid questions, but so many more contributors can come in) :

- Do "manual.txt" is the root, and all the Others txt's are linked inside this ? Or all are separated from each others ? How they are organized ? And what files will be included in the nightly build and which not ?
- I can see we can modify the txt's, but how to add images inside the repository ?

make docs

This will make PDF and BMP files.

If you don't like that feature, let me know and I'll just delete it. Two years of work gone out of the window.

Don't upset like this ! We are here to discuss and to clarify ! So, do this will produce a PDF file with BMP files embedded ?

if the road man wants to print a manual, must go to repository, find the right txt among a myriad of other files, and print it ? or, worse, compile the txts together ? How ?

Do you agree this ready-readable format is better ? And you can add images inside. Or how to render the repository manual more user friendly ?

Let's start, boys  --> http://www.magiclantern.fm/forum/index.php?topic=6594.0   

This is to unify all the ML informations into a unique collaborative manual.

In the official ML repository there is the official manual. It's located here :

https://bitbucket.org/hudson/magic-lantern/src/tip/doc/

This is in different pieces: txt's, png's, bmp's, jpg's, drawings and so on. They are all organized into a precise structure, with chapters and so on, and this structures is as follows (but changes continuously as the manual develops) :

include(o, "FEATURES.txt");
include(o, "MANUAL.txt", 1);
include(o, "MENUSTART.txt");
include(o, "MN-AUDIO.txt");
include(o, "MN-EXPO.txt");
include(o, "MN-OVERLAY.txt");
include(o, "MN-MOVIE.txt");
include(o, "MN-SHOOT.txt");
include(o, "MN-FOCUS.txt");
include(o, "MN-DISPLAY.txt");
include(o, "MN-PREFS.txt");
include(o, "MN-DEBUG.txt");
include(o, "MENUEND.txt");
include_indent(o, "FAQ.txt");

This structure is controlled by scripts, so you can add chapters to it. All the scripts are in the doc directory (mkdoc.py is for pdf, mkdoc-cam for help bmp's, wikidoc for wiki output - but needs some tweaks). You need latex to compile them.

Each TXT file is plain text, you can edit it online, or offline and then commit it. The syntax is RST (http://docutils.sourceforge.net/docs/user/rst/quickstart.html) and can contain references to images (living in the same directory of the txt)  in this way :

.. figure:: 02.expo.png
    :align: center
    :width: 5cm

To add images, commit them like normal files to the official ML repository.
You can add files, sections, whatever.

The good of this system, is that, by modifying this manual, it's modified the help PDF in the nightly builds, it's modified the BMP ML help system inside the cameras and, if anyone fixes the wiki scripts, we can update the online version as well, all from a single source !

this one is up to date even more

Top post updated ! Thanks !