Menu

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.

Show posts Menu

Messages - gnarr

#26
Here is my first version of mlv2dng. It's not finished yet and there is still a lot to be done.

What is not working:
Spanned files (could someone please supply me with some spanned files? I don't have a 5D3 to try it).
Preview image. (it shows random noise)
Dual ISO.
It only shows very limited amount of EXIF data, as I have still to do mappings from MLV to exif tags.
probably much more.

I have a lot of cleanup to do on the code before I submit it online. Will probably be online tomorrow or the day after.

Usage is the same as with raw2dng for the moment:
mlv2dng.exe file.mlv [prefix]
=> will create prefix000000.dng, prefix000001.dng and so on.

https://dl.dropboxusercontent.com/u/3181048/mlv2dng.zip
#27
Quote from: xNiNELiVES on August 12, 2013, 07:25:58 AM
I posted a 5D2 clip a few posts above...

Well I'm still waiting on the IME module. Should I download it from the 5D3 package? Where's this located?

The file has no data in it (it's only 1 kB). But the same is happening for me now.

I just did a "clean install" on my 5D2, that is, I cleaned my CF card and installed the 5D2_Alpha_One package and updated it to the 2013/08/09 version. Then I installed raw_rec.mo from raw_rec_mlv.zip in reply #277 and autoexec and symbol from #221.

It gives me the same results as before. The camera is super slow for ~5 seconds after I press record and then fills the buffer and "stops", but in the raw rec menu it shows "stopping" forever and everything locks up after a few more seconds.

I tried turning on the debug trace, but I can't find the trace file. @g3gg0, are there any log files I can send you or something I can do to help with fixing this? Or are you still focusing on making the 5D3 version work good before looking into debugging other platforms?

Ps.
I still need a 5D3 file :) Anyone willing to upload one for me? It doesn't need to be large.
#28
Could someone here post a small mlv file from a 5D3? I need it to test code that I'm working on.
#29
Quote from: g3gg0 on August 11, 2013, 09:46:35 AM
5D2:

can you try this module version if it is any better?
http://upload.g3gg0.de/pub_files/c73635e82eca629043f7f5d442e82265/raw_rec.mo

It seems to behave in the same way as the other one for me.
#30
Quote from: g3gg0 on August 11, 2013, 02:04:14 AM
5D2: autoexec  symbol

can you try it?

What raw_rec.mo should we use with this? I just tried the one from post #200 in this thread and it freezes the camera. I am currently using the 2013/08/09 build from the 5D2 raw thread.

Here you can see how it freezes:
https://plus.google.com/117039326451584292689/posts/dYB7vPW2FsR
#31
I got pretty much the same performance on my 5D2 yesterday as with the old format. Maxed at 76MBps.

#32
Great job g3gg0! Could you maybe post a tiny mlv file here, so we can start to develop converters? :)
#33
Apparently H.264 has a "High 4:4:4 Predictive Profile":
QuoteHigh 4:4:4 Predictive Profile (Hi444PP)
This profile builds on top of the High 4:2:2 Profile, supporting up to 4:4:4 chroma sampling, up to 14 bits per sample, and additionally supporting efficient lossless region coding and the coding of each picture as three separate color planes.
For camcorders, editing, and professional applications, the standard contains four additional Intra-frame-only profiles, which are defined as simple subsets of other corresponding profiles. These are mostly for professional (e.g., camera and editing system) applications:

And also "High" and "CAVLC 4:4:4 Intro Profile":
QuoteHigh 4:4:4 Intra Profile
The High 4:4:4 Profile constrained to all-Intra use.
CAVLC 4:4:4 Intra Profile
The High 4:4:4 Profile constrained to all-Intra use and to CAVLC entropy coding (i.e., not supporting CABAC).
As a result of the Scalable Video Coding (SVC) extension, the standard contains five additional scalable profiles, which are defined as a combination of a H.264/AVC profile for the base layer (identified by the second word in the scalable profile name) and tools that achieve the scalable extension:

http://en.wikipedia.org/wiki/H.264/MPEG-4_AVC
#34
ohh, I definitely didn't see that. You clearly know what you are doing 8)
#35
It would be awesome if you could reserve a few bytes for bookkeeping information such as:
time : Auto generate with internal clock
Camera # : set manually
Scene # : set manually
Slate # : set manually
Take# : manually set & edit, plus auto count and reset
Ext Sound record # : manually set & edit, plus auto count and reset

and maybe some other info that could be usefull. As was already spoken about here: http://www.magiclantern.fm/forum/index.php?topic=2497.msg60707#msg60707

An option to change the filename according to this info would also be cool, if possible.
E.g.
Scene 1 - Camera 2 - Take 4 - Slate 1 - 2013-07-21 01:05:13.RAW
#36
Here is a test I shot a few days ago:
#37
I want to rewake this topic. This is something I could really use, especially since we don't have in camera sound with raw video recording.

Also, naming the files according to this info could help a lot.

e.g. :

Scene 1 - Camera 2 - Take 4 - Slate 1 - 2013-07-21 01:05:13.RAW

Managing a whole feature done with raw could become a nightmare if all files are named something like M21-0105.RAW.
#38
Canon already does some scaling when converting to h264 in camera. I can't remember exactly how, but if I remember correctly the downscale it from 1880 to a little lower resolution and then upscale it to 1920. Probably to do some kind of crappy demoiré. So by only doing 1880 -> 1920 convertion, you are already way ahead of the h264 video.
You also don't want the video to be aldready squashed and stretched before doing post production. With the raw video you can do all kinds of things to squees every bit of resolution out of the video.

And of course the biggest point. You have 14 bit color space and 4:4:4 chroma subsampling instead of 8 bits and 4:2:0 in the h264 compressed video.
#39
I just found out about the Cineform 16bit RGB codec. It is the only 16bit 4:4:4 "movie file" format that I have found yet, the rest seems to be image sequence based formats. I'm going to do some tests with Cineform 16bit tonight and I'll try to post something here.
#40
Quote from: Redrocks on July 05, 2013, 08:17:51 PM
http://www.authorityfx.com/encoding-videos-in-prores-4444-on-windows/


http://www.magiclantern.fm/forum/index.php?topic=5557.0


http://www.magiclantern.fm/forum/index.php?topic=6021.0

Thanks for the links Redrrocks :)

However, isn't ProRes 4444 only 12bits?

Is cDNG maybe the only 16bit 4:4:4 format available ?

@dariSSight#1
If I've understood correctly what I've read, the CPU in our cameras are pretty much stuck at 96% while recording RAW, so we don't have any headroom for in camera compression. The H.264 compression is probably done using an onchip encoder instead of the CPU.
#41
As the topic says, is there any (preferably free) 16bit 4:4:4 codec that we can use for storing and working with our ML Raw footage? If so, do you know what compression algorithms they use and what programs they are compatible with?

I know of cDNG, but I would like to know of all options :)
#42
I can do 76MBps on my Computerbay 1000x 64GB with the 27th of june build, 1.85:1 at [email protected]8)