Messages

Can't be the lens. Looks like clipped highlights. Use the expose to the right hint on the exposure control? I try to get it just over zero not too under not too over...

I thought so myself. But since I am also seeing this issue in the HDMI monitor, I guess it has something to do with the firmware and not with anything in my development workflow.

Could it also be related to the White Levels being pushed too far (above 15000)?

I reduced the white levels for testing there is no visible improvement.

I also tested the crop_rec module now. The problem is always around sharp edges to clipped highlights, like lamps or sunlight reflection on water. The problem is not so present when the highlights are a bit out of focus.



Adobe Camera Raw has a defringe tool for magenta and green edges, I am currently trying to add something similar.

I am using the 28mm and 50mm f1.4 non-L Canon primes and the 70-200 f4 L lens. The primes are a bit worse than the L lense, but I get it with the latter, too. And it's always around clipped highlights. Stopping down creates other problems like noise in the shadows.

[BTW]

BTW Here's a short sample of what I am working on right now:



The image on the right has been processed with my internal build. I get those magenta fringes all the time with my 5D MKIII. Is this a problem with the lens? I also get that weird effect when I preview the image on an HDMI monitor, also in Photoshop and Resolve. Anybody have any experience with that? Do you also get this when filming with the crop_rec module?

Latest version: problem on export as Prores. First frame is color corrected, the rest is very , very flat without color correction. Not tried as dng.

Found the problem. It's an bug in the Recovery of Discolored Hightlights. I am currently working on a total new Defringing method. That should fix that. Hang on.

[New Build 0.2.3 (119)]

New Build 0.2.3 (119)

- Fixed frame rate issue in Cinema DNG
- Fixed cancelling Cinema DNG export
- Added exporting audio in Cinema DNG
- Added audio info to metadata view
- Improved 'Discolored Highlights' filter
- Fixed jumping preview images when changing raw sliders
- Fixed a crash

https://rink.hockeyapp.net/apps/3ed6ecf60e684239a6aba3d407cf3935/app_versions/60

@frenchps49

Try to delete the library once more and restart the app. The app should add a default folder called "Roll", which contains all MLV files that are not organised in folders.

@Lars Steenhoff

Great update, it seems that when I export to DNG and try to cancel the export is does not cancel.

Yeah, I'll fix that.

Can you do animated thumbnails?  when hovering with the mouse

Probably not in 1.0. More important stuff to do at the moment.

I was experimenting with the lossless lj92 compression in MLV files. I wanted to see if I can decode the image and reinterpret it as a raw cfa pattern. I came across a number of problems that could also be a problem in mlv_dump. I took the liblj92 implementation by Andreaw Baldwin found here:
https://bitbucket.org/hudson/magic-lantern/src/7a9b6805756c3b86f2174bac00433c544a976501/modules/mlv_rec/lj92.c?at=mlv_rec_lj92&fileviewer=file-view-default

But I could not make it work. I had decoding problems due to the fact that the library is missing some support for multiple components. I then came across the implementation in tiny_dng_loader by Syoyo Fujita here:
https://github.com/syoyo/tinydngloader/blob/master/tiny_dng_loader.h

I then extracted his changes back into a simple standalone .c and .h file and tried that and viola, the decoding result was much better:


I posted the extracted version of the library on GitHub:
https://github.com/martinhering/liblj92

Just saying, if you encounter any decoding problems in mlv_dump with the mlv_rec_lj92 branch, give my version a try.

Can you try this build?

https://rink.hockeyapp.net/apps/3ed6ecf60e684239a6aba3d407cf3935/app_versions/57

Where is it ?

Try Console app:


Should be a report starting with "Footage_2017-04-05..."

@DeafEyeJedi

You may have a lot of files, unfortunately I did not really care to make the database migration really good with UI and such. Try to delete ~/Library/Application Support/Vemedio/Footage and restart app. Sorry.

I'm on 10.12 and it crashes too.

Same crash log message?

Code Select Expand

*** Terminating app due to uncaught exception 'NSInvalidArgumentException', reason: '*** -[NSKeyedArchiver encodeValueOfObjCType:at:]: this archiver cannot encode structs'
terminating with uncaught exception of type NSException
abort() called

I am on it. Should not be a problem on 10.12 though.

Does anybody know what type of CF card is actually able to record this much data? I have the Lexar Pro, that says 160 MB/s. I quickly tested 3k, but I need a CF card that is at least twice as fast.

@hyalinejim
What did you use?

[Version 0.2 Build 111 (Alpha 2)]

It took me a while, because I need to work on a different project at the moment to earn some money. Developing this app is more complex than I thought. Anyway here's a new version:

https://rink.hockeyapp.net/apps/3ed6ecf60e684239a6aba3d407cf3935/app_versions/57

Version 0.2 Build 111 (Alpha 2)

- Export to Cinema DNG
- Improved folder support
- Added grid of thumbnails to preview folder content
- Added showing file metadata in grid view
- Improved multi-selection support
- Improved focus pixel maps for 100D, 650D and 700D
- Support for Lossless JPEG compression
- Added "Reveal in Finder"
- Added "Move to Trash" for deleting files from the disk
- Fixed crashes and improved performance

First startup can be slow, because the database has to be migrated from the Alpha 1. All subsequent app starts should be fast though.

Also here's a screenshot of the new grid view:

@Walter Schulz

OK, thank you. I'll check it out.

However,  alex has just released a new amazing update with the option to compress the raw data in camera, (60% lossless)  i have tried to view the files in your app, but it crashes everytime.

Alex did say that the windows mlv dump app did need tweeking to be able to decode the MLV file,

Will you be able to update this app so these new MLV files can be read?!

Where can I find more information about this build?

[I made a hotfix update 0.1.4 for the problems you mentioned:]

@DeafEyeJedi

I made a hotfix update 0.1.4 for the problems you mentioned:

- Added focus pixel map for mv720 mode on 100D
- Improved focus pixel maps for 650d and 700d
- Fixed hang when exporting with no audio
- Fixed some memory leaks

https://rink.hockeyapp.net/apps/3ed6ecf60e684239a6aba3d407cf3935/app_versions/41

Currently working on 0.2, which includes all those fixes, but takes a couple more days to finish.

@lostfeliz @reddeercity

There might be a problem with audio. If I save the file in QuickTime player again, the saved file does not have audio, but opens correctly in Photoshop and Compressor. The original .mov file does not. I am currently downloading the MLV to reproduce the problem and see what's going wrong with the export. Make take a day or two. The MLV is huge.

Looks like you're doing the same thing so I don't understand why the EOSM is different from the 650D/700D/100D -- that doesn't match what I came up with.

The pixel maps as such are not different, but the crop rectangle logic is different. The various buffer modes are centered around a specific point and that point is differently offset. On the EOSM its 16px more to the right and 16 px more up. You only need this logic for reverse calculating the original raw buffer size for the auto-detection. You don't need it for the correction, as cropX/Y parameters are enough for that. Not saying that my maps are perfect yet. I am not confident yet that they are, but so far they are working. I'll update them as needed.

When you implement LUT support can you make it so that two luts can be stacked on top of each other?   for example the first LUT is SLog3 as the input LUT and the second a Color grading LUT like Filmconvert.

Makes sense.

@dfort

You can very easily find many of the focus pixels that are not the pixel map files that you created by shooting a frame with the lens cap on.

I bought a used 700D of eBay and could verify this with some dark frames and I updated my pixel maps. Also had to update my auto-detection code for the 700D.

Code Select Expand


    NSInteger rawBufWidth = 0;
    NSInteger rawBufHeight = 0;
    NSInteger rawBufWidthZoomRecording = 0;

    switch (_idntInfo.cameraModel) {
        case kMLVCameraModelEOSM:
            type = kFTRawImageFocusPixelsTypeEOSM;

            rawBufWidth = (block.cropPosX > 0) ? 80 + raw_info.width + (block.cropPosX-80)*2 : raw_info.width;
            rawBufHeight = (block.cropPosY > 0) ? 10 + raw_info.height + (block.cropPosY-10)*2 : raw_info.height;
            rawBufWidthZoomRecording = (block.cropPosX > 0) ? 128 + raw_info.width + (block.cropPosX)*2 : raw_info.width;
            break;
           
        case kMLVCameraModel650D:
            type = kFTRawImageFocusPixelsType650D;

            rawBufWidth = (block.cropPosX > 0) ? 64 + raw_info.width + (block.cropPosX-64)*2 : raw_info.width;
            rawBufHeight = (block.cropPosY > 0) ? 26 + raw_info.height + (block.cropPosY-26)*2 : raw_info.height;
            break;

        case kMLVCameraModel700D:
            type = kFTRawImageFocusPixelsType700D;

            rawBufWidth = (block.cropPosX > 0) ? 64 + raw_info.width + (block.cropPosX-64)*2 : raw_info.width;
            rawBufHeight = (block.cropPosY > 0) ? 26 + raw_info.height + (block.cropPosY-26)*2 : raw_info.height;
            break;

        case kMLVCameraModel100D:
            type = kFTRawImageFocusPixelsType100D;

            rawBufWidth = (block.cropPosX > 0) ? 64 + raw_info.width + (block.cropPosX-64)*2 : raw_info.width;
            rawBufHeight = (block.cropPosY > 0) ? 26 + raw_info.height + (block.cropPosY-26)*2 : raw_info.height;

        default:
            break;
    }


    if (rawBufWidth == 1808) {
        if (rawBufHeight > 1000) {
            type |= kFTRawImageFocusPixelsType1808x1190;
        } else {
            type |= kFTRawImageFocusPixelsType1808x728;
        }
    }
    else if (rawBufWidth == 1872) {
        type |= kFTRawImageFocusPixelsType1872x1060;
    }
    else if (rawBufWidth == 2592 || rawBufWidthZoomRecording == 2592) {
        type |= kFTRawImageFocusPixelsType2592x1108;
    }


I could not verify yet, if it's really working on the 650D. I just hope so.

@togg

I get this:

Best thing would be to provide the file somewhere for me to download.

By the way, extraction of dngs isn't planned right? Especially compressed dngs as in MlRawViewer.

I dont know about compressed yet, but export to CinemaDNG is planned. Somewhere around Alpha 3 or 4. Here's my current roadmap:

Alpha 1: Basic proof of concept (is public already)
Alpha 2: Browsing of files with thumbnails and metadata as well as batch export
Alpha 3: Better development tools like histogram, zebras, rgb parade, better sharpening etc.
Alpha 4: CinemaDNG export, LUT support

@reddeercity

Yes your black level off  , I'm betting it 3x crop mlv_lite ? it's a known problem with 5d2 use full mlv

Would a black-level compensation help here? Is this a problem with writing the wrong black levels into the mlv file?

@lostfeliz

Have you tried re-encoding the file with Compressor or ffmpeg or something? Does this help?

Here is some footage I took with my 5D Mark III today (Full-HD 12bit). Rendered to ProRes 4444 in Footage for Mac and then treated colors with FilmConvert. I definitely want to be able to ditch FilmConvert some day. Working on it :-)

http://fs.footageformac.com/?dir=clips

(Sorry for the micro shakes in the footage. It was very windy today and I don't have the best tripod).

@dfort @marcb

If the app crashes on launch, try to delete this file:
~/Library/Application Support/Vemedio/Footage/Database-v1.bplist

Could be that I messed something up during database layout migration. I need to change the internal database format anyway. It's more like a prototype as of now. You could also send me the crash logs located at: ~/Library/Logs/DiagnosticsReports starting with "Footage...". Normally, I get the crash reports automatically using Hockey, but when the app doesn't launch, the Hockey framework can't upload the crash reports.

@squig @Teamsleepkid

About the sharpness filter: Since it has problems on some machines (not mine), I will try to replace it with my own implementation. It's not a good filter anyway. It increases noise by a lot, because it doesn't seem to have edge detection. What do you think about this method?
https://www.gimp.org/tutorials/Smart_Sharpening/

Seems to give better results.

@Lars Steenhoff

can you make a 4k output option?

Do you have any 4k MLV file? I can't produce something like that, because my 5D3 is only doing Full-HD.

@timbytheriver

Crashes and pink tint now fixed in El Capitan 10.11.6

When does it crash?

However, playback at any real speed of 14bit files not happening on my system MacMini mid 2011

Playback is not possible at all at the moment. Or do you mean playback of the exported movie? MacMini from 2011 should do a Full-HD no problem. If you are exporting to Prores, maybe you're hard disk speed is the problem. Maybe you need an SSD or export to H.264.