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

Pages: [1]
Awesome updates in 1.4, thank you!

I noticed that you're able to have the edit panel floating, would there be a possibility to have the individual panels behave the same instead? Like "Processing", "Details" and "HSL". It would allow for more customization and better utilization of monitors with higher resolution.

Sorry if it's already been mentioned.

Yes right! Black Level = 5111 :o

@FBongcam: That MLV is cut and exported by "MLV App version 0.15 alpha". Can you share the original .MLV? (or .RAW)

I can't believe that "raw2dng" put 5111 black level into the header for 5D3. Not possible! (black = 2048, white = 15000, 5D3 defaults)

Edit: well, it's possible if original .RAW had this wrong black in the footer (I would look at that .RAW)

Yes this is from some of the first builds when raw was introduced. It worked out fine with the newer version of MLVApp though, that I compiled.

Edit: Would you like to have the original .raw file anyway?

No, no such artifacts also for me. What version of MLVApp did you use, and on which OS?

EDIT: STOP! I get the same result you have using v0.16. This version did not completely auto correct wrong black level of your file. The blacklevel of your file is over 5000... but it should be 2048. After correcting black level all is perfect (latest repos revision does it automatically).

Yes I'm using v0.16 on mac os. Looking forward to next release then!  :)

Hmm... and where are those artifacts in the clip posted above? Cleanest image ever, IMHO :)

Do you not get these results in your preview? I get the same result when exported as well.

Could you provide a MLV (shortend to some frames is enough for analysing) please?

This is the mlv file converted from .raw with Switch to .mlv file. Shortened using MLV export in MLVApp.

Yeah you have to follow Danne's advice. We are not going to add .RAW support to MLV App.
I also had bunch of old .RAW files from 60D, that's why I decided to implement RAW to MLV converter into raw2dng utility.

Download it here for any OS (it is command line utility, prints out help)

Thanks, it worked. I do however get weird artifacts on clips where the black level is wrong. When corrected with mlv_dump I don't get these.
It's like pink highlights/dots around edges etc.


I was wondering if there would be any way to process the older .RAW files with this app? I know the format probably is a bit outdated now...

As I'm able to process them in mlrawviewer I thought maybe it's not impossible to incorporate support in this app.
If it's out of the question, would there be any way to convert .RAW files to .mlv?

I have a bunch of old footage I'd really like to process with the workflow that this app offers.

Thank you for the continued development!

Any plans on adding DNG as an export option in the future?

Great progress on the app so far  :)

@FBongcam: thank you. So that works. Can you tell me the framerate of your clips? If there is a "." in the framerate, some qt librarys could make the "." to a "," and so ffmpeg does not run. Before
Code: [Select]
-i in the command I made a
Code: [Select]
-r 25 for 25 fps in the app. In my case it was always the "." (at 23.x fps), but that may be different from country to country.
Does it work with a 25fps file in your case? Or, easier: check in the preferences menu framerate override and type 25! Does it export now?

Edit: tried it with another locale and have exactly your problem :-) Anyway... does 25fps work for you? Then I can fix it!
Clips are shot at 24p.

I can confirm, turning on framerate override to 25p did work  :)

Turning on framerate override to 24p worked as well.
I shoot with fps override set on Exact fps to 24 in magic lantern so the clips should be exactly 24 from the beginning. Just some extra info if it's relevant to your issues with the "." (at 23.x fps).

Okay, if Ilias cocoa app crashes on export, and my Qt App jumps from 50..100% then I am nearly 100% sure that ffmpeg does not work on your machine (whyever). If you see the png files - could you please convert manually using ffmpeg in the application bundle? In the Qt app it is located under "MLV App/Contents/MacOS/ffmpeg". Go to this directory in terminal and type
Code: [Select]
./ffmpeg -i "<path to your pngs>/chosenFileName_\%05d.png" -c:v prores_ks -profile:v 2 "<path to your desktop>/"Does that work? I think it will end with an error. But can you tell us what ffmpeg tells exactly?
The png files also disappear when it's finished but I can see them while it's exporting and as soon as the export says it's finished, everything is gone.

I forced quit MLV App during export to keep some png files it managed to render, just to get a sequence of png files. Then I ran ffmpeg on the files and it created the file succesfully.
Here's what terminal gave me:

Code: [Select]
./ffmpeg -i M12-1835_test_\%05d.png -c:v prores_ks -profile:v 2 ""
ffmpeg version 3.3.2-tessus Copyright (c) 2000-2017 the FFmpeg developers
  built with Apple LLVM version 8.0.0 (clang-800.0.42.1)
  configuration: --cc=/usr/bin/clang --prefix=/opt/ffmpeg --extra-version=tessus --enable-avisynth --enable-fontconfig --enable-gpl --enable-libass --enable-libbluray --enable-libfreetype --enable-libgsm --enable-libmodplug --enable-libmp3lame --enable-libopencore-amrnb --enable-libopencore-amrwb --enable-libopus --enable-libsnappy --enable-libsoxr --enable-libspeex --enable-libtheora --enable-libvidstab --enable-libvo-amrwbenc --enable-libvorbis --enable-libvpx --enable-libwavpack --enable-libx264 --enable-libx265 --enable-libxavs --enable-libxvid --enable-libzmq --enable-libzvbi --enable-version3 --disable-ffplay --disable-indev=qtkit
  libavutil      55. 58.100 / 55. 58.100
  libavcodec     57. 89.100 / 57. 89.100
  libavformat    57. 71.100 / 57. 71.100
  libavdevice    57.  6.100 / 57.  6.100
  libavfilter     6. 82.100 /  6. 82.100
  libswscale      4.  6.100 /  4.  6.100
  libswresample   2.  7.100 /  2.  7.100
  libpostproc    54.  5.100 / 54.  5.100
Input #0, image2, from 'M12-1835_test_%05d.png':
  Duration: 00:00:04.28, start: 0.000000, bitrate: N/A
    Stream #0:0: Video: png, rgb48be(pc), 1920x1080, 25 tbr, 25 tbn, 25 tbc
Stream mapping:
  Stream #0:0 -> #0:0 (png (native) -> prores (prores_ks))
Press [q] to stop, [?] for help
Output #0, mov, to '':
    encoder         : Lavf57.71.100
    Stream #0:0: Video: prores (prores_ks) (apcn / 0x6E637061), yuv444p10le, 1920x1080, q=2-31, 200 kb/s, 25 fps, 12800 tbn, 25 tbc
      encoder         : Lavc57.89.100 prores_ks
frame=    3 fps=0.0 q=-0.0 size=    1889kB time=00:00:00.08 bitrate=193250.8kbitframe=    7 fps=6.3 q=-0.0 size=    4405kB time=00:00:00.24 bitrate=150313.2kbitframe=   11 fps=6.5 q=-0.0 size=    6922kB time=00:00:00.40 bitrate=141740.9kbitframe=   15 fps=6.5 q=-0.0 size=    9442kB time=00:00:00.56 bitrate=138109.9kbitframe=   19 fps=6.6 q=-0.0 size=   11959kB time=00:00:00.72 bitrate=136053.1kbitframe=   23 fps=6.6 q=-0.0 size=   14476kB time=00:00:00.88 bitrate=134747.5kbitframe=   27 fps=6.6 q=-0.0 size=   16992kB time=00:00:01.04 bitrate=133833.9kbitframe=   31 fps=6.6 q=-0.0 size=   19509kB time=00:00:01.20 bitrate=133176.1kbitframe=   35 fps=6.6 q=-0.0 size=   22025kB time=00:00:01.36 bitrate=132662.3kbitframe=   39 fps=6.6 q=-0.0 size=   24543kB time=00:00:01.52 bitrate=132265.1kbitframe=   43 fps=6.7 q=-0.0 size=   27060kB time=00:00:01.68 bitrate=131942.6kbitframe=   47 fps=6.7 q=-0.0 size=   29576kB time=00:00:01.84 bitrate=131673.7kbitframe=   51 fps=6.7 q=-0.0 size=   32094kB time=00:00:02.00 bitrate=131450.9kbitframe=   55 fps=6.7 q=-0.0 size=   34609kB time=00:00:02.16 bitrate=131253.6kbitframe=   59 fps=6.7 q=-0.0 size=   37128kB time=00:00:02.32 bitrate=131094.3kbitframe=   63 fps=6.7 q=-0.0 size=   39647kB time=00:00:02.48 bitrate=130957.6kbitframe=   67 fps=6.7 q=-0.0 size=   42164kB time=00:00:02.64 bitrate=130830.9kbitframe=   71 fps=6.7 q=-0.0 size=   44680kB time=00:00:02.80 bitrate=130716.8kbitframe=   75 fps=6.7 q=-0.0 size=   47197kB time=00:00:02.96 bitrate=130617.7kbitframe=   79 fps=6.7 q=-0.0 size=   49716kB time=00:00:03.12 bitrate=130532.0kbitframe=   83 fps=6.7 q=-0.0 size=   52231kB time=00:00:03.28 bitrate=130447.8kbit[png @ 0x7f8fbc013e00] chunk too big
[png @ 0x7f8fbc014a00] chunk too big
[png @ 0x7f8fbc015600] chunk too big
frame=   87 fps=6.7 q=-0.0 size=   54751kB time=00:00:03.44 bitrate=130380.2kbit[png @ 0x7f8fbc016200] chunk too big
[png @ 0x7f8fbc016e00] chunk too big
[png @ 0x7f8fbc017a00] chunk too big
[png @ 0x7f8fbc018600] chunk too big
frame=   91 fps=6.7 q=-0.0 size=   57267kB time=00:00:03.60 bitrate=130312.5kbit[png @ 0x7f8fbc019200] chunk too big
[png @ 0x7f8fbc010800] chunk too big
[png @ 0x7f8fbc010e00] chunk too big
[png @ 0x7f8fbc011a00] chunk too big
frame=   95 fps=6.7 q=-0.0 size=   59787kB time=00:00:03.76 bitrate=130256.6kbitError while decoding stream #0:0: Invalid data found when processing input
frame=   96 fps=6.6 q=-0.0 Lsize=   60420kB time=00:00:03.80 bitrate=130249.5kbits/s speed=0.263x   
video:60418kB audio:0kB subtitle:0kB other streams:0kB global headers:0kB muxing overhead: 0.002408%

A few files in the end of the sequence were broken obviously so maybe that gave some errors, but the prores file is working.

Thanks! it was useful... figured out from it that Apple must have made a little lie about API support, because I remember reading them saying that was 10.10+, but seems its actually 10.11+, so I've changed it back to what I used before (older API). Could you test again if you find time? It should work now. I'm almost surprised that there was only one error :D
Yes it does work now, thanks  :)
However the app crashes every time it has finished exporting the prores, maybe it's something related to 10.10 or is it a known issue?

@FBongcam: Does someone else have this problem? For me that works. Does the progressbar jump from 50 to 100%? If you see pictures in the app it is not the issue I wrote about. It must be an issue with ffmpeg.
Yes it seems to jump from about 50% straight to the notification that the export has finished, as you described. I can see pictures in the app, yes.

In the last weeks Ilia implemented many new features and I integrated them into the Qt version of MLV App. Here we also have the image profiles now and audio support: we can playback audio on preview, export and draw the audio track in the GUI (maybe audio is not perfectly in sync, but Ilia had already an idea how to fix that...).
Windows version will come if @bouncyball (or someone else) finds some time to build it for you. So here is first the OSX 10.9.5+ version:

This new version (QTv0.7alpha) doesn't output the prores file for me. I can see the png files being created while it's rendering but when it's finished the folder is just empty. I've tried with different settings and also by leaving everything default without any luck.
I'm on OSX 10.10.5.

After reading the app page "Support for mlv_dump uncompressed MLV files seems to be broken", maybe that's what I'm experiencing :), I tried both 10bit and 14bit though.

@FBongcam (If you find time!) Could you please try and compile the app yourself:
Code: [Select]
git clone && cd MLV-App/platform/cocoa && make app && cd - && open MLV-App/platform/cocoa/ && open MLV-App/platform/cocoa/MLV\
I ran this and the app still won't open. It says the app is damaged or incomplete.

Terminal gives me this error (if it's of any help):

Code: [Select]
Initial app name: MLV App (Sep 14 2017 00:14:10)
rm: main.o: No such file or directory
gcc  -mmacosx-version-min=10.10 -O3 -Ofast -m64 -c main.m
main.m:80:40: error: use of undeclared identifier
        | NSMiniaturizableWindowMask | NSWindowStyleMaskFullSizeContentView;
1 error generated.
make[2]: *** [main.o] Error 1
cp: MLV App: No such file or directory
cp: No such file or directory
Archive:  ../qt/FFmpeg/
  inflating: MLV 
   creating: MLV
  inflating: MLV 

The application cannot be opened because its executable is missing.

I'm on 10.10.5 and the native macOS version says 10.11 is required. The app has a crossmark icon and can't be opened obviously.
Reading through the thread it seems people are running this on 10.10 or am I wrong?

The cross-platform version works though.

This is looking very promising, I really like the UI.

Any chance for Yosemite (10.10) support?

Best Regards,


First of all, great application and a great concept!

Sorry if this has been mentioned or asked before but does MlRawViewer correct the vertical stripes? I couldn't find any info about in the feature list.


Fixed my green and pink images, thanks!

Share Your Videos / Re: 5D Mark III RAW vs H.264
« on: August 07, 2013, 02:53:22 AM »
Really impressive, but isnĀ“t the workflow quite complicated.

Not really, what's bothering me is to keep everything organized and to know which clip is which as there's no thumbnails for the dng sequences. :P

Nice comparison mate.

Thanks mate!

That's useful, thanks. I'll try and fix it when I have time.

Great, looking forward to it!

I'm on Mountain Lion 64 Bit (10.8.4).

I get these errors when starting the app:

span error - I click OK


An exception of class NilObjectException was not handled.  The application must shut down.

I never even get in to the GUI.

Share Your Videos / 5D Mark III RAW vs H.264
« on: July 24, 2013, 02:52:39 PM »

Just thought I'd share my comparison of the Magic Lantern RAW vs it's original H.264 format.
More info in the video description.

Share Your Videos / Re: Beauty (5D Mark III RAW Test)
« on: June 02, 2013, 12:02:54 PM »
Thank you alecw!

Share Your Videos / Beauty (5D Mark III RAW Test)
« on: June 01, 2013, 11:22:24 PM »

I'm new to the forum, thought I'd share my first quick test with the RAW Video function using my 5D Mark III.
I used a 32 GB Lexar 800x with the 31st May (1729277) build. Shot at 1920x720. Graded in After Effects and edited in Premiere.

Pages: [1]