Messages

Code Select Expand


        #ifdef CONFIG_50D
        skip_top    =  0;
        skip_left   =  0;
        skip_right  = 0;
        skip_bottom = 0;
        #endif


though as i am now reading c code it does look like you could just
#define RAW_DEBUG
in features.h

would be interesting if your DNGs had different borders from the ones JulianH and i shot 2 weeks ago.
many things are changing and they just had to update the values for the 5D2

skip_top = 26 -> correct
skip_left = zoom ? 64: 74 -> wrong, should be zoom ? 0 : idk (all the DNGs were for zoom as far as I could tell)

hey there, remember the procedure now - set all of the skip values to 0, created a build.
shot silent pic DNGs.

we did that 2 weeks ago and got the results here
http://www.magiclantern.fm/forum/index.php?topic=5586.msg46715#msg46715

why is it different today?

it looks easier to just set 
define RAW_DEBUG in platform/50D.109/features.h
but shouldn't that be the same as forcing all of the values to zero in src/raw.c (for the CONFIG_50D near line 348)

i also see that the code for the 5D2 had to change these values a couple of days ago - has something else shifted these values for all cameras?

Andy600 - do you see where in the code a1ex is referring?
the test should be to set skip to 0 (and/or/or only -  define RAW_DEBUG - ask a1ex)
shoot silent mode DNGs then count the blackness.

temperature - usually 43 with some builds i have transiently hit 57.

does anyone have their 50D and computer near enough eachother to shoot some Silent Picture mode DNGs at regular and zoom mode and upload them?

in response to some color issues, 1% asked for current silent picture mode DNGs - it is especially important if you take one and see a black border of any width - so shoot a light color object or otherwise expose in some way so that any potential black border is visible.

perhaps something has changed which affect the calculations using offsets - i see that the offsets for the 5D2 were adjusted again a couple of days ago.

50D new unified build available:
https://bitbucket.org/GregoryOfManhattan/magic-lantern/downloads/mlmod-2013Jun21.50D.109.go.unified.9f26e15d9146.zip
many changes to modules/raw_rec.c and src/raw.c
all cameras join the 50D in being MOS

can this build hit 80MB/s ?

Above, I have this done.
Hmmm... so black level is still wrong, I haven't had the chance to check it yet. Maybe should look at that today.

what in the appearance tells you the black level is off?
JulianH and I both measured the DNG size could that have changed or been shifted this past week?
easy enough to shoot some DNGs and find out.
the pink/ magenta clips seem to be an occasional anomaly of the recent [50]80pt1 build ( 2 out of 34 clips had this and it covered the whole frame unlike KahL issue).

this build showed rates as high as 80.5 MB/s but i wonder about the actual data rate required for 1920x1072p23.976 - isn't that 82.4 MB/s?
is the tragic lantern slowing down the frame rate or is it actually recording at a rate greater than the display?
does 50D at 11 really = 83 MB/s?

thanks for everything - love the look even in very low light - ran out to grab some shots late last night : http://vimeo.com/gregoryo/50d-1080p
if i can get any time tonight to try a grade, i'll repost it.

@xNiNELiVES - relax the video is not fully uploaded and/or converted vimeo will activate the link soon and it handles both http and https requests just fine.

not sure about the 40-41MB/s - i saw 80.4 on 50D tonight - are you quoting 1% speaking about another camera?

and that number may be incorrect - 1920x1072x14bits would be a 3.44 MB frame size time 23.976 fps is 82.4 MB/s
(may be off here - should be sleeping).

EDIT: @xNiNELiVES - thanks yes you are correct -  this forum requires that the 's' is removed - so http only videos - seems out of date - very 2008 like the 50D

1080p 5 out of 34 clips had some error (3 were glitchy frames in the last second, 2 were strangely magenta)
used the [50D]80pt1.zip (tragic lantern 6D) which hit 80.4 MB/s
seemed able to continue and 2 clips spanned the 4GB FAT32 limit.
most clips i stopped recording for content reasons.

shot at night with only available street light - ISO 1600 F2.8 canon 70-200mm lens.
batteries ran out.

this is amazing for the 50D and magic lantern!!

thank you - had to do the regular mode first.
855, 448, 1261 frames - yes that is much faster than 300.
why are the module settings included with preview canon?
is that the recommendation?

posted a new unified (the main magic-lantern branch used by many other cameras) based build.
http://www.magiclantern.fm/forum/index.php?topic=6554.msg51887#msg51887
gets 220-250 1920x1080 (23.976) frames.

@KahL - Kahleem - which build were you using when that happened on your shoot?  please report back, so devs and users know where problems and instabilities may lie.

@Andy600 very many changes and the code differences between the tragic and the unified are substantial.

what settings are required to get to the 80s (i liked 90s music much better anyway)?
just tried the tragic [50D] 80point1.zip and i'm getting less speed than on unified - 150-200 frames at 1920x1072 (23.976)

can't wait to see the speed - thanks 1% and a1ex.

EDIT: just recorded 300plus 1920x1080 (23.976) frames with this unified.
earlier build today has really cool graphs - a plot of buffer overflow so you can see it as you hit your maximum.
recommend the most recent build - but if you want to see it -the build with the graphs is: https://bitbucket.org/GregoryOfManhattan/magic-lantern/downloads/ml-2013Jun20.50D.109.go.unified.90c50ab005b7.zip

today's build  from the unified branch
https://bitbucket.org/GregoryOfManhattan/magic-lantern/downloads/mlmod-2013Jun20.50D.109.go.unified.1b42291d5085.zip


@akumiszcza - thank you for your detailed notes - i need to review the ETTR functions myself as i haven't used them for several days.

#KahL Kahleem - you've got an art video not a fashion shoot. which build led to that result?

sounds like the dial is really going to hit 11.

tested tonight that round trips from black magic cinema camera cinemaDNGs to fxpx and premiere work without difficulty.

with magiclantern/rawmagic cinemaDNGs -
i could export a .aaf XML from resolve and import it into premiere.
created a new sequence but could not import it back into resolve getting  "the selected CompositeMOB index is out of bound" error with the import aborting.

Andy600, sounds like 1% is suggesting that we merge the code. lets do that and post a test build tomorrow - separate from unified. try it, see what happens and merge on Friday.

hi coutts - on the bitbucket thread,  i made sure to provide correct instructions for others and noted that a serverfault post is incorrect

truncate or gnu truncate is not included in osx/darwin (strange that it is on freebsd).
if the code used dd it may have just worked on osx, but it is easy enough to install
one way of which is via homebrew

Code Select Expand


brew install coreutils

which places gnu versions of gnu.org/coreutils in /usr/local/bin/ prefixed with a g
since there is no osx version of truncate, i found it simple to symlink

Code Select Expand


ln -s /usr/local/bin/gtruncate /usr/local/bin/truncate


hope that the macports method above works for you.

today's unified build
https://bitbucket.org/GregoryOfManhattan/magic-lantern/downloads/ml-2013Jun19.50D.109.go.unified.7eee493f6fc9.zip

Andy600 - sounds very interesting - do you have any statistics on your two modules
it's hard to measure the 2 MB/s differences.

can you record more frames at 1920x1080 in crop/zoom mode ? (more than 140 ?)
maximum stable continuous recording can you get stable at 1920x880 or larger sizes?

see 1% posting to his 6D repository https://bitbucket.org/OtherOnePercent/tragic-lantern-6d/src/a7df9e2b29f5a4cb4e8c6499a17daa8d992b7226/platform/50D.109/?at=unified

looks like a great deal of progress for the 50D.
https://bitbucket.org/OtherOnePercent/tragic-lantern-6d/src/a7df9e2b29f5a4cb4e8c6499a17daa8d992b7226/platform/50D.109/?at=unified

i've committed the FEATURE_LV_FOCUS_BOX_SNAP_TO_X5_RAW change - found that by comparing the 50D features to its digic iv cousin camera the 5D2 - you've confirmed it working, so lets get it into unified branch

also in 5D2 is #define FEATURE_LV_BUTTON_PROTECT // works even without the Q menu present
which doesn't compile cleanly unless we get the correct values for
//~ #define BGMT_Q 0xE
//~ #define BGMT_Q_ALT 0xE
(or see more of how this works for the 5D2.212 )

do you or 1% have that code somewhere visible on the net?
if you are getting values for constants from a legitimate dump of the firmware, they should be fine.
again comparing with the 5D2.212/constants, we see that
50D.109 is missing the HIJACKs and it looks like many of the already commented out YUV422_HD_ lines should be deleted as the constants are not used elsewhere in the code.

RE 6 star vs. 5 star - is stable recording speed a better metric than counting stars? of course loosing a buffer (if its really lost and not a display glitch) would be expected to decrease maximum stable recording speed.

absent deeper knowledge of magic lantern, i'd continue to compare 50D.109 with 5D2.212 to see what is different in the code.  the .h files are the lowest hanging fruit because adding correct values for constants should simple enable other parts of the magic lantern code.

can we find anything else which should be enabled.
and what about QR_MODE - we still need the correct values in src/raw.c

sounds good - exposure override working for manual focus lenses. what happens with a manual focus lens with a dandelion type chip?

new build from later in the day

https://bitbucket.org/GregoryOfManhattan/magic-lantern/downloads/ml-2013Jun18.50D.109.go.unified.d55f33a1d395.zip

https://bitbucket.org/hudson/magic-lantern/commits/d55f33a1d3956affce79f542b55ec5af7e2a6ffa

renaming folders and files to match the bmcc conventions seems to help - making clips viewable at the library folder level (where you can see many clips at a time) instead of seeing only folder names (M16-1204) and having to click into the folder to see the clip.

log files have messages:
The clip "" is linked to "M16-1204_[00000-00476]"
which is a clip not even used in the XML being imported.

I posted what I have so far, I dunno if the graphics play nice with GD on, but GD off I get more speed, also hacked no preview doesn't correctly work but for some reason starts off faster from the get go.

just a few more MB/s could make the EU anamorphs very happy as they'd be able to shoot 1584x1080 at 25 fps.
right now we are almost there with stable 70-71MB/s need a little more overhead to get consistent takes of any length.
in crop mode 1920x880 is close to this limit as well. 1920x1080 seems a bridge too far.

@GregoryOfManhatten - I think you should include bolt_rec in your builds. Seems stable enough

You probably already know this but the new modules compilation fix works but rename Makefile.modules.default to Makefile.modules.user and include modules in ML_MODULES_DYNAMIC ?= (if you leave the default the user one is ignored)

yes - someone requests bolt_rec - i had it in my camera last week when we had a few storms here, easy to include.

will try the new module make later - didn't work for me a couple of days ago, so i have a shell script go through the module dir's individually.

if anyone has a working roundtrip from cinemadng to resolve to proxies and external editor and back, can you please post your working XML.

is the following an accurate summary of what is happening?

Davinci Resolve does not re-linking correctly when importing the XML from an image sequence round trip.
Import image sequences into resolve
Create Proxies
Edit in something (premiere, fcp7, fcpx, ...)
in the external editor export XML
Resolve Conform window - Import XML
displays an imported timeline but with incorrect clips associated with the edit points.

latest build:
https://bitbucket.org/GregoryOfManhattan/magic-lantern/downloads/ml-2013Jun17.50D.109.go.unified.f4a7ab821357.zip

more fixes for the 50D
raw_rec: 5D2/50D: grayscale is better than pink, right?
raw_rec: force left not working on 5D2/50D/500D
raw_rec: fix black level autodetection (especially for 5D2/50D zoom mode)

a1ex - thanks - black levels off in the zoom because we didn't call raw_set_dirty ? they were computed on the pink version?

forking the new build posts to another thread to make it easier for developers to follow technical issues and bug reports.

for known issues with recent builds of the 50D we have:

• crop mode (zoom mode) - framing problems
  
• crop mode  - pink cast to the view.
• HDMI out - are the issues different on 50D from on other cameras 50D bug report http://www.magiclantern.fm/forum/index.php?topic=6471.0 and 5D3 http://www.magiclantern.fm/forum/index.php?topic=6302.msg48407#msg48407

are there other issues which should be on a 50D bug list?

please keep using this current thread for general 40D and 50D raw video questions and discussions.
if you have identified specific issues with a build report them to the 50D build thread:
http://www.magiclantern.fm/forum/index.php?topic=6554

many features added today for the 50D have posted 2 builds.

https://bitbucket.org/GregoryOfManhattan/magic-lantern/downloads/ml-2013Jun16.50D.109.go.unified.15694a53cfa3.zip
a1ex:

raw_rec: quick'n'dirty hack for fixing pink preview in x5 zoom on 5D2 and 50D. Image quality should not be affected.

the earlier build has been tested with one report of stable 71MB/s with Graphics Draw (GD) off.
https://bitbucket.org/GregoryOfManhattan/magic-lantern/downloads/ml-2013Jun16.50D.109.go.unified.b93d6ae2b30d.zip
includes modules: raw_rec and ettr

includes a1ex's edit today for:
etter
frame alignment on 4:3 screens - hey that could help the 50D
removed "Memory Hack" only known to work on 5D3 and 6D
and potential help for pink frames

[Update 26 June 2013]

This topic is for discussing specific 50D builds for raw video. A build is a specific set of collection of compiled code and modules packed up into a zip file.  Raw video is under active development and the behavior of various features and functions is rapidly evolving.
Update 26 June 2013 - there is a new "Small Hacks" feature in the raw_rec module.  in the Raw Rec Detail Menu enable Small Hacks.  50D builds hit 81MB/s for hundreds or more frames at 1920x1080 in crop/zoom mode only. The goal is 83/84 MB/s as this would permit continuous 1080p24 recording. 

Latest builds:
pick the most recent from the download locations below:

based on hudson/unified, the main branch for all cameras from the code in: bitbucket.org/hudson/magic-lantern: https://bitbucket.org/GregoryOfManhattan/magic-lantern/downloads/ sporadic builds from me until 9 July 2013 as i will have limited internet access.

1% is posting tragic lantern the latest high speed builds to
https://bitbucket.org/OtherOnePercent/tragic-lantern-6d/downloads
these could contain advanced settings so be prepared and have fun.

Andy600 is producing hybrid builds for testing some new code based on tragic lantern and unified
https://bitbucket.org/andy600/andy50d/downloads/
read thread posts for notes on specific test builds.

Users / testers: please include the build file name when reporting results bugs.
for a good example of a detailed bug report which led to a resolved issue, please look at http://www.magiclantern.fm/forum/index.php?topic=6976 and note the care with which user @platu describes exactly how to reproduce the error.  a1ex directs people to http://www.chiark.greenend.org.uk/~sgtatham/bugs.html

If you are a new user, go through the guides.
RAW video & ML -- Beginners Guide, FAQ & Useful Links -- READ FIRST
http://www.magiclantern.fm/forum/index.php?topic=5520.0

PostProcessing -- Beginners Guide
http://www.magiclantern.fm/forum/index.php?topic=5654.0

General discussion of  Raw video on 50d and 40d  is on the thread http://www.magiclantern.fm/forum/index.php?topic=5586.0
For the super speed builds from Andy600 and 1% please be sure to read the latest information.

Build your own
If anyone wants to build hudson/unified 50D releases and add them to this thread or otherwise share them with your friends, please go ahead.

• - hg clone https://bitbucket.org/hudson/magic-lantern
• - create Makfile.user  - enable modules CONFIG_MODULES = y, CONFIG_TCC = y, CONFIG_PICOC = n, CONFIG_CONSOLE = y
• - create modules/Makefile.modules.user - ML_MODULES_DYNAMIC ?=ettr raw_rec pic_view file_man bolt_rec
• - make modules then make zip in the platform/50D.109 directory (i posted a very simple shell script to do this, simply edit for the directory where your source code is https://bitbucket.org/GregoryOfManhattan/magic-lantern/src/a678cd4f9539619acbb4b2e08b895b34d6902a45/build50Dwithmodules.sh?at=50DrawNow )