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 - Danne

#5276
Are you on windows? Otherwise the other programs would work. The audio file needs to match amount of dng frames. At least cannot be longer. Second a template metadata which must match frames per second in the dng file. I do this with bwf meta edit to put in ixml info and shorten audio with ffmpeg. Both programs exists for windows if you don,t want to do it in c-code.
It,s mainly row 32-50 that needs to be put into the wav file. Framerate must be in 5 numbers(e.g 24fps will be 24000, 23.97 will be 23970)
https://bitbucket.org/dmilligan/mlvfs/src/9f8191808407bb49112b9ab14c27053ae5022749/mlvfs/wav.c?at=master&fileviewer=file-view-default

Bwfmetaedit
http://bwfmetaedit.sourceforge.net/
#5277
Raw Video Postprocessing / Re: cr2hdr for macOS Sierra
February 01, 2017, 12:19:11 AM
Worth mentioning some recent progress on handling focus pixels coming from MLV files. Until now this has been taken care of only when piping through dcraw to different formats ProRes in MLP and cr2hdr.app leaving the dng file still full of pixels.
I,ve been discussing the possibilites together with Bouncyball about utilise cold pixel code in raw2dng, used in mlv_dump somehow to also account for x,y coordinates created in dforts focus pixel script for those cameras affected. This was possible and Bouncyball used his magic fingers and created som real nice list handling through mlv_dump. Now the vital piece of the puzzle is the actual coordinates generated in dfort,s focus pixel script which are used also in mlvfs so I married the "allbadpixel.map" code from Bouncyball and the focus pixel script from dfort and I let them both live and prosper in cr2hdr.app in a nice multithreaded way :). It,s all taken care of automagically so just run cr2hdr.app and let dngĀ“s be baked.
In this version I also put in chroma smoothing code from raw2dng since cr2hdr cs code code seems to not work so good in blown highlights for now.

Code here
https://bitbucket.org/Dannephoto/magic-lantern/branch/ml-dng-unified_4_chroma_smooth

Focus pixel code(dfort)
https://bitbucket.org/daniel_fort/ml-focus-pixels

A picture that says it all. Dng file with and without allbadpixels.map file generated.



#5279
Wav file needs certain metadata. It,s also working in cr2hdr.app and MLP.(thanks to dmilligan)
#5280
Yes, that would be nice. I have put in raw2dng code for the time being in mlv_dump and it works very good. What,s your take on this @g3gg0?
#5281
raw2dng appears to handle it properly.

Ok, mlv_dump produce corrupt chroma smoothing in highlights. Just tested with disabling vertical stripes and no pixels. Then tried converting the file to legacy RAW. How do I even apply cs2x2? Don,t seem to be automated so can,t check this but I take it raw2dng and chroma smooting is working as it should according to a1ex. Any ideas about what,s up with mlv_dump?

I got raw2dng chroma smooth to work and that code is working good with blown highlights. Not mlv_dump.
#define CHROMA_SMOOTH

Copy paste raw2dng chroma smooth void code into mlv_dump works so there is something fishy going on with chroma_smooth.c probably.


#5282
I was just thinking it might be caused by vertical stripes and now see your settings. Didn,t run with vert stripes off before.
Gonna check later.
#5283
I,ve been having issues with chroma smoothing in mlv_dump. It,s always occurring in and around blown highlights. Doesn,t matter if shooting 10/12/14bit. When trying to understand what is going on I,m checking chroma_smooth.c it seems the calculations around green is what causes it. So I check against MLVFS and although it seems to be using the same chroma smooth code the output is free from corruption. Could it be related to focus pixels? Maybe those pixels needs to be handled before applying chroma smooth? The good thing about cs2x2 is that when it works it almost completely removes focus pixels. WIth darkframe subtraction it completely removes all focus pixels.

MLV file
https://bitbucket.org/Dannephoto/magic-lantern/downloads/broken_cs2x2.MLV
DNG file
https://bitbucket.org/Dannephoto/magic-lantern/downloads/broken_cs2x2.dng

Chroma smooth set to cs2x2

Examples

#5284
Feature Requests / Re: mv1080 on EOSM
January 27, 2017, 07:33:14 AM
Movie crop mode is the only mode giving 3x zoom.
crop_rec is a smart way of binning mv720p footage so it gives same quality as mv1080p. Caveat. You get lesser height.
#5285
Feature Requests / Re: mv1080 on EOSM
January 26, 2017, 05:49:46 PM
"bnn"
Yes.
#5286
Feature Requests / Re: mv1080 on EOSM
January 26, 2017, 11:42:39 AM
I don,t know about the rename. It,s kind of established in my brain now.
bin_crop_rec.mo?
bin_rec.mo
I would however have nothing agains metadata as suggested here :).
http://www.magiclantern.fm/forum/index.php?topic=17021.msg173941;topicseen#msg173941
#5287
Feature Requests / Re: mv1080 on EOSM
January 26, 2017, 12:02:00 AM
Crop_rec in 10bit gives continuous output. And it looks really great.
#5288
Raw Video / Re: Working mlv-raw file recovery tool?
January 23, 2017, 06:04:08 PM
Paranoid mode, hehe, funny.
#5289
Interesting.
How are you subtracting darkframes? Can you upload a darkframe and a clip with banding?
#5291
Modules Development / Re: MLV Lite
January 20, 2017, 06:31:22 PM
Yes, padding, remember dmilligan,s solution from before.
Anyway. Tested push and working.
Thanks.
#5292
Modules Development / Re: MLV Lite
January 20, 2017, 02:55:36 PM
Performance is zero since processing breaks, but when working this has nothing to do with performance, you,re right. Maybe should have posted this in some other thread or maybe over at bitbucket.
Sidenote.
Seems to be an issue with flatframe processing as well. Have a few more tests to do.
*yes, flatframe processing takes a hit as well.
#5293
Modules Development / Re: MLV Lite
January 20, 2017, 01:47:51 PM
I encountered a bug with mlv_lite today when trying to work with dark frames. In short it seems to be a mismatch in how frame sizes are produced going through darkframe subtraction in mlv_dump. After filming and creating a darkframe this error message appears when running the averaged darkframe with the footage. Error message occurs even though files are filmed with exactly the same settings in cam.

Processing...
[ERROR] Error: Frame sizes of footage and subtract frame differ (1494976, 1494720)Processed 0 video frames
Done


command in test with averaged darkframe.
mlv_dump -o a_M20-1342.MLV -s avg_EOSM_res_1728x692_iso_400_fps_24.002000.MLV M20-1342.MLV

Test files here(shortened)
https://bitbucket.org/Dannephoto/magic-lantern/downloads/darkframe_mlv_lite_issue.zip

Bypassing the break in the error message will create fine darkframes but that won,t change the mismatch issue of course.
#5294
General Help Q&A / Re: FRSP
January 19, 2017, 08:15:44 PM
#5295
General Help Q&A / Re: FRSP
January 19, 2017, 07:48:23 PM
garry23, are you on mac?
Coud you test this version?
http://www.magiclantern.fm/forum/index.php?topic=5601.msg178746#msg178746
#5297
Is this happening with or without raw_twk enabled? Try with raw_twk disabled.
#5298
Raw Video Postprocessing / Re: MLVProducer
January 19, 2017, 09:45:36 AM
#5299
QuoteGreat! However I still find batch calling mlv_dump much better then mlv-fs. Is there any way how to make real cdng from mlv_dump?
You can process cdng files with this
http://www.magiclantern.fm/forum/index.php?topic=15108.msg146822#msg146822

The program works with a mlv_dump version which has code mixed in from a specific ml-dng branch version. Code updated to latest 10/12/14 bit the same as latest mlv_dump(g3gg0/a1ex). Works with resolve(audio embedding).
When installed head over to the mlv_dump menu (m) from the main menu and you can do setting changes from there such as black/white level etc.
#5300
Mlv_dump, the more powerful tool imo. Strong features. Now working with 10/12/14 bits without the need to specify black/white level. And also:
- darkframe handling
- flatframe handling
- Possible to parallelize exporting processing
- and more...