Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.

Messages - Colemar

Pages: 1 [2]
Dunno, what is the biggest file you've processed?

4.27GB on Windows build of raw2dng..just installed the new build but haven't tested yet.

Nope.. over 4gb file didn't process.. the 10gb didn't either.

just exits immediately or throws a message?  I've noticed on Mac OSX it will not recognise filepaths that are not contiguous.  any spaces and it throws an error message with the requested filepath truncated at the space..that could also be an issue in the Windows build..Linux ok?

It errors for me on >4GB files in windows..

is that a build in-development?  The latest Windows build from a1ex worked fine for me all day on any filesize I threw at it..

Does anyone have a suggestion as to why I am getting the error message: "This ain't a lv_rec RAW file" when trying to convert my .RAW file with raw2dng on a Mac?

the devs are working on it.  It looks like a problem working with 64bit integers as opposed to the 32bit current build, but a developer can possibly give more info

I've updated the file in the link so osx user try and report back, if now it works.

stevegalle is correct, it is the same error message:
Error: This ain't a lv_rec RAW file

ls: *.dng: No such file or directory
Nothing converted

it happens on any .raw file I have tried larger than 2GB

So for 4GB converter has to be modified for 64 bit integers too?

yes but more specifically to run in the 64bit kernel I think, because I have unrecognised .raw files that are ~2.1GB also.

Change the converter source so it uses 64-bit integers

I bet you're right, scrax do you have time to recompile for 64bit OSX?

Are these files larger than 4GB or they are cropped at 4GB?

The metadata is at the end of the file, so if it's missing, all you can do is to fill in the metadata yourself or hack the source code of the converter.

they are larger, usually ~4.28GB according to OSX Finder properties.  It seems like a corrupt header because I also have a couple ~2.07GB .raw files that are not recognised in the same manner.  Is this a quick fix or do you want a smaller file Alex?

   raw2dng for Mac is not able to resolve filepaths with name spaces.  Once I copy the .raw dataset to a contiguous filepath name, converter works great.

EDIT:  Unrelatedly, has anyone noticed .raw files that record to 4GB or larger won't convert in raw2dng?  On Mac OSX I get an "this ain't a lv_rec file" error.


5DmkIII preliminary basic Compact Flash card speed tests yield:

Sandisk Extreme Pro 128GB 100MB/s UDMA 7 CF burst ~82MB/s with ~73MB/s sustained write speed @ 1920x960.  It would randomly drop frames at 1920x1080 but did complete the 4GB size limit before ceasing.  It was the only card of the trio that could record 1920 vertical lines whilst simultaneously recording the 1920x1080 H264 "proxy" to the same card.  In fact, it's sustained speed did not waiver whether or not the H264 files were being written.

Lexar Professional 32GB 1000x UDMA 7 CF burst ~87MB/s with ~82MB/s sustained write speed @ 1920x1080.  It was the only card that could repeatedly sustain full 1080p for the duration of the 4GB size limit.

Delkin Devices 32GB 1000x UDMA 7 CF burst ~69MB/s with ~63MB/s sustained write speeds @ 1920x840.  It was the poorest performer with random dropped frames above 840 horizontal lines.  It would complete the duration of the 4GB size limit at 1920x840, but no higher.

None of these cards' write rates seemed affected by panning or tilting or complicated visual patterns in frame.

Global Draw was always on, but only for information overlays, all of the graphical overlays within frame were turned off.

The camera got warm, but not hot, and when the cards were pulled, they were likewise only warm.  Nowhere near as scalding as an SSD mag removed from a Blackmagic camera.  Never a temp or buffer warning from Canon firmware or Magic Lantern software.

In the next few days I will post a blog with test footage for those that are interested:

Thanks so much to the committed ML dev team and the forum members who contribute!

-Colemar Nichols

In my brief testing the Lexar 1000x  is not stable at higher than 1920x1080 @23.976 

thank you lourenco, I will be testing the Lexar 1000x, Sandisk 100MB/s, and Delkin 1000x on the 5DmkIII tonight and will post back results asap

the filename says 5d2, of course it won't work on the 5d3.

very good point.

use the autoexec.bin in that zip.

on the 5DmkIII with that autoexec.bin the camera will not start up.  When reverting to lorenco's autoexec.bin and using the modules you provided, the error messages appear.  When reverting everything to lourenco's build, the camera functions properly but there is some image tearing.  Just to make sure, the autoexec.bin and modules you kindly provided are for the mkIII ?

This should work for 5d2, double buffering enabled:

extract the MODULES directory into /ML/ on your card

  thank you for the post.  unfortunately that was a small step backwards for me as now an error message is generated when attempting to load the module.  I do not know how to attach things or I would include a .422 screenshot...

ASSERT: IsSuiteSignature( hSuite )
at ./PackMemory/PackMem.c:599, task RscMgr
lv:1 mode:3

Magic Lantern version : v2.3.NEXT.2013May13.5D3113
Mercurial changeset   :
Built on 2013-05-12 21:25:54 by magiclantern@magiclantern-VirtualBox.
Free Memory  : 145K + 3731K


at ./Memory/Memory.c:568, task RscMgr
lv:1 mode:3

Magic Lantern version : v2.3.NEXT.2013May13.5D3113
Mercurial changeset   :
Built on 2013-05-12 21:25:54 by magiclantern@magiclantern-VirtualBox.
Free Memory  : 145K + 3874K


   will you please post the compiled modules with the double-buffering commands?  I would like to begin framerate testing on different card makes and speeds asap.

many thanks,
-Colemar Nichols

I think they are recognised only by LR and ACR. Davinci Resolve also sees them as 128x96 (most likely a preview incorporated in the headers)

Thanks Kuky, you must be right.

Shooting on a 5DmkIII, why are the DNG's converting as 128x96 resolution?  They are almost 4MB each and the .raw file hasn't dropped a frame..I have access to 1000x cards from Delkin, Lexar, and SanDisk, and would like to test them all for members' information, but cannot get useable video from the process..will anyone help me?

-Colemar Nichols

I would be most grateful if a current compilation would be posted for the 5DmkIII.  Many thanks!

Pages: 1 [2]