Messages

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?
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.

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 Expand

./ffmpeg -i "<path to your pngs>/chosenFileName_\%05d.png" -c:v prores_ks -profile:v 2 "<path to your desktop>/test.mov"
Does that work? I think it will end with an error. But can you tell us what ffmpeg tells exactly?

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.

@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.

@Ilia: Thanks. Qt on OSX is also just wrapped cocoa... I'll try that with the default profile.

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:
https://github.com/ilia3101/MLV-App/releases/tag/QTv0.7alpha

Yes, you'll need this for the latest revisions. I started implementing audio playback. But... it still a bit buggy ;-)

On OSX that does not work out of the box. It would work if you install ffmpeg, but I wanted to have it in the application bundle, because for most users that is the easiest way (because the user hasn't do install anything but the app itself). For windows I am not sure, but I expect the same.

Edit: I could make a define which takes your string for Linux, and the other string for the other platforms. Would that be easier for Linux?

Edit2: Did that now. I think that should be better for Linux users.

Do you think this can be fixed?  I would love to try out version 6 due to all the new features and faster speed.

I really do not know what happens. So I don't know how to prevent the crash and can't say if it can be fixed. Sorry. This needs more research. But I can't do that here on my MacBook.

I tried installing the Windows version into Wine on OSX. Also with that I can export your MLV. The crash appears starting version 0.4? The main difference between 0.3 and 0.4 is the use of libpng, to have 16bit PNGs instead of 8bit PNGs Qt supports only.

Okay, thank you very much, I downloaded the file. It is not a general problem, because on OSX I can export your file without issue.
@bouncyball: could you please download the file as well and try on your Windows PCs?
@IDA_ML: happens the same with the 32bit version?

It is a single MLV file of about 300 MB size (109 frames).  Regardless of the export format that I set in the Preferences, when I press Ctrl+E, it opens the export window and allows me to select the folder for export.  When I press Save, the software crashes and I get a message saying: MLVApp.exe has stoped working. 

Unfortunately, I have a very slow internet connection and cannot send you the file now but if you wait until tomorrow, I can try to send it from work where the net is way faster.

You can use mlv_dump to shorten the clip to some frames, then the file is only some MBs. Does this happen with any MLV file for you?

Just shorten a file with mlv_dump:

Code Select Expand

mlv_dump -f 5 -o OUTPUT.MLV INPUT.MLV
Gives you a 5 frame MLV file.

Unfortunately, version MLV.App.v0.6.alpha.x64.Win crashes when I try to export a 14-bit MLV clip from the EOS 100D.

How do you export (setting & single file or batch) and when does it crash? Can you chose the file/folder name, crashes it just after pressing save, at 50%,... ? Can you provide a small file which provokes the error please (best if only some single frames inside)?

Thx :-) It was not to complicated. It is added to the repos. But there is a tiny bug... Ilia, please check my log :-)
But in general it seems to work fine. Good work Ilia!

I hope I'll find some time to add it also to the cross platform version in the next days... Started my 3 weeks holidays today. But internet connection seems to work :-D

Another thing

I use MLV-videos for nothing else than my astronomical stuff. Autostakkert, the program, which I use to stack the videoframes, need uncompressed avi-files as input. It does not run with prores. It would be nice to can export such avi-files with MLVApp sometime in the future.

For my needs I did a workaround, quick and very dirty. Looks like that:

I changed MainWindow.cpp line 636 ff

Code Select Expand

QString program = QCoreApplication::applicationDirPath();
    program.append( QString( "/ffmpeg\"" ) );
    program.prepend( QString( "\"" ) );
    program.append( QString( " -r %1 -i \"%2\" -c:v rawvideo -pix_fmt %3 \"%4\"" )
                    .arg( getMlvFramerate( m_pMlvObject ) )
                    .arg( numberedFileName )
                    .arg( "yuv420p" )
                    .arg( output ) );
                   
And I replaced all .mov strigs, i found in MainWindow.cpp with .avi.

Edgar

I added export to uncompressed AVI in my latest commit. Hope it works :-) Thanks for your code!

I can compile with QT creator without problems and don´t have to chance anything. Maybee, QT Creator adds the paths itself?

I don't think Qt adds paths (at least it does not do that for me ). But maybe there is set a system variable with that path.

For my needs I did a workaround, quick and very dirty. Looks like that:

That does not look so quick and dirty. That patch should do the job. Maybe I add this in future to the other codecs. What does this codec "rawvideo" exactly? Does it convert the png to tiff and adds it to the avi?

The histogramm of Mars is now OK. I uploaded a comparition between MLV App and darktable on my website: https://seescho.wordpress.com/fotos/ml/

btw. What is this for in MLVApp.pro?

Code Select Expand

#Linux
linux-g++*: INCLUDEPATH += /usr/local/include/
linux-g++*: LIBS += -L/usr/local/lib/ -lz -lpng

/usr/local/include and /usr/local/lib are empty on my system.

Edgar

Hey cool... the simple trick seems to work in the histogram.

How can you compile when that is empty? That's strange.  In the repos under platform/qt/ there is a folder: libpng. Here you find the source for this library - unpack, compile and install. Zlib should work if you install the dev version with apt-get or whatever you use. If not, you can download this in the internet, compile and install.

Done

Thanks!

@bouncyball:
I think anywhere in the near of getMlvRawFrameFloat() in video_mlv.c would be right then (or where this one gets called).

Cool stuff at the repos! I made a new release and counted up to v0.6 alpha. Would you please compile and upload the windows version(s)?
https://github.com/ilia3101/MLV-App/releases/tag/QTv0.6alpha

@all:
New in v0.6 alpha:
- Bugfixes for >2GB file support on Windows
- Changed histogram algorithm (cuts peaks at very low and high end, and is something between linear and log now) @escho & @DeafEyeJedi: please try out if shows better would you like to see
- Preview pictures in sessions (list mode and picture mode)
- Scrolling and dragging support at 100% zoom in picture viewer
- Small bugfixes

Btw I noticed that FPS, while playing MLV, differs for Win and Linux builds (no matter 32 or 64 bit):

Win ~7-10 fps
Linux ~15-18 fps (even 20 sometimes)

Tested on the same PC with the same hardware and MLV files.

Haha... with Windows it is so slow... yes, I have seen that too, so I am not alone:
- Win 8.1 Pro [email protected] (PC from 2013): 10 fps
- OSX 10.9 Core2Duo 2.4 GHz (MBP 2010): 10 fps
- OSX 10.10 i5 2.5 GHz (iMac 2011): 17 fps

@masc: I pushed my latest stuff to repo. I think you'll appreciate commit 1aadb46

I'll check that out this evening!

@masc I see you added mlv dump sources to the repository. I will try and implement them, although some of them will probably need to be moved from src/processing to src/mlv, as they work mostly with bayer data, not RGB which the processing module does.
Caching rewrite still on the list ugh
I'm back and more stuff is coming.

We also need a really nice icon.

Oh yes! A nice icon would be cool. I just created this ugly thing for having anything... but I don't like it!

I added the mlv dump sources because I was playing around. I tried to add chroma smoothing, but without luck. Maybe I did not call it at the right step. When do we have to call it? I thought before the debayering when I understood the code and the comments right. Is that right? But it works with integer and Ilia implemented float. Is that a problem?

I tested an MLV clip with sound last night. w10 64bit version.

Video exported fine, however there is no sound and/or no separate audio file created.

When reviewing the app preferences Export Audio is ticked but greyed out.

Audio is not implemented, that is the reason why it is still greyed out. Ilia wants to implement audio read out, I also wait for that

Hi Masc, i'm on MacOS, i'm currently using the 0.5 alpha version.. the latest version on the download page, just tried finder to select multiple MVLs to import, but when i go to "open with", the MLV app is grey'd out and won't let me select it, to open with, guess i'll wait for the app to be updated, again fantastic work, thanks.

Yes, I have that on Mavericks too, on El Capitan it works for me, whyever. There is a option "Show only recommended" or something like that (have never seen the english version ), and when you uncheck that, it also works on Mavericks.

Terrific Progress guy's, amazing work, quick question though.... anyone know how to batch import?? i can only seem to import one clip at a time, or am i missing something?

I am not sure, if the latest version we uploaded as binary had already a filedialog for multiple files. Are you on Windows or OSX?
Windows: take the version from bouncyball, that should be new enough, select as many files you want in the dialog.
OSX: if it is new enough, try the same. If that does not work: select the files in Finder and chose "Open with..." -> MLV App.

Hey guys patched - frame number not reported correctly for 2GB+ MLVs in the info dialog.

Download 32bit and 64bit versions again.

Both 32/64bit versions should hopefully work for everyone now

Tested the 32bit version emulated in Wine on OSX without problems Could also open a 2.3GB file.

@Edgar: na das triffts doch ganz gut! I always wanted to write that, and I even should do that. Some remarks:
1.: The app does not search for ffmpeg. I told the app, it is located exactly next to the executable, because on Win&OSX this was the easiest to do. So for Linux, if the location is anywhere else, we can add this special path.
2.: MLV App does not only need ffmpeg. It also needs libpng 1.6 and zlib. Otherwise it won't compile. On Win&OSX this was the most difficult part (at least for me).
3.: The histogram thing: I even think it is not wrong, I wrote it some messages above. There is just this peak in the very left (that is the black in your picture)... but if anyone has an idea how to cut peaks without making the histogram to flat... pleeeaaase tell me... this problem drives me crazy! 

Anyway... thanks for this very good installation manual! I like it

@mascI forgot that in addition to 'fseek' there are lots of 'ftell' used in 'video_mlv.c'. And of course they also should be replaced by 'ftello64' for mingw .

I have to test this code also for Linux (if it works for Linux it should work on Mac without change) and then I will push changes to repo (thanx to Ilia, he gave me access).

Perfect! Thx! :-)

Succeeded to run it under Linux. A first feedback:
1. Exporting to prores results in png. The number of pngs is correct, but the progress bar stops at 50%.
2. I see nothing in histogramm, looking at a small object like the planet mars. Histogramm of the big moon looks fine:
   Histogramm mars: https://seescho.files.wordpress.com/2017/08/mars1.jpg
   Histogramm moon: https://seescho.files.wordpress.com/2017/08/mond.jpg
Edgar

Thanks for testing on Linux! I think the histograms are both right. The picture with the mars is really dark, so the black in the histogram is so huge, that you nearly can't see the rest. Atm we are anywhere between linear and log scaling on the y axis. Log would be good for pics like that, but "normal" pictures would result in a line. Linear is good for normal pics but if there is a peak, you'll see only the peak.

Woooow, 2 days off and so much feedback. Thank you guys.

@Bouncyball: I'm sorry, I won't see a Windows PC for the next 4 weeks, so I hope other members of the forum will test and help to get feedback until then.

Somebody was asking for resetting the sliders: Menu -> Edit -> Reset receipt does the job.

@reddeercity: you think the exposure is wrong in MLV App? I always thought it is wrong in MlRawViewer and MLVProducer, because when opening any of my clips there I always get a "near to black" image, and I start seeing anything when doing something like exposure +3EV - then it looks near to what I saw on my camera. I don't have that problem when opening files in Resolve. But if I am right, we don't use metadata for processing, so it may be wrong... don't know what Ilia says about...

@Ilia3101, @masc
Intermediate PNG export is a huuuge waste of space, for 1920x1080 one PNG frame is ~10MB (imagine size for 3K). Had to free some space on my SSD to make this export.

Yes, you're right, I know. I already tried to get the ffmpeg library working... but... after some days I gave up. I did not understand that library interface - it is really huge. But if you know how to do that, we could try another time. That should be faster and consume a lot less temp memory. And that would be much more elegant.

And... what did you change for your last upload?