Messages

Hm... strange. I have MLVApp running on Win7 64bit Core i3 4GB RAM, Win8.1Pro 64bit Core i7 8GB RAM, OSX 10.9 16GB RAM, 2x OSX 10.11 8 & 24GB RAM and Ubuntu 12.04LTS VM without that problem. It is bad, that Windows never tells the reason for a crash...
Do you activate "AMaZE Cached"? This crashes Windows 32bit versions on my systems.

Having problems with both apps now. MLV app and mlv_dump os   

Could you be more precise please? Maybe you can provide a small MLV for debugging as well?

Sure. But I had to search for a while. Here you have: https://www.dropbox.com/s/xw260tdkmalnja6/M25-1225s.MLV.zip?dl=0
When reducing speed to 50% there happens this: (left original frame, right generated frame, happens in the end of the clip)

Unfortunately there is not much aliasing in the clip... maybe the glass border line?!

Scenes with water also nearly never work with optical flow.

I agree with bouncyball and Danne: if we want a nice solution (with preview, without memory mess, without external programs which always bring problems,...) we only can implement a in-program-solution. This means implementing optical flow and aligning... yeah... if there is someone out there who can help with that... we are here and waiting for you!

Btw: how good is the script solution working with moving objects and wide angle?! I always have big problems when using optical flow for slowmotion with my clips - that nearly never works (brings missing or double objects flimmering in the clip; tested with FCPX & Resolve).

A work in progress
http://www.magiclantern.fm/forum/index.php?topic=21089.msg193622#msg193622

Ah okay, that was this story, I remember. Is there a way to use this with pipes or something like that? ATM I am happy that we don't need temp files. Using these programs would make a big mess again. Do you see a possibility?! 
What you could do: combine the two solutions: take MLV App first to get AMaZE debayered TIFF and then take (a part of) the script fullfilling the antialiasing. That should bring nice results!

Hello ilia3101 and masc,
Do you think it's possible to implement an antialiasing script like the one used by danne and the one used by a1ex? A lot of people there doesn't have money to pay a vaf-filter, so it can be a good alternative to process it and then export from mlv free of aliasing to ProRes.

Edit :  it can also allow us to check the before/after in real-time for more accurate comparison

I can't tell you, if we can implement that, because it is the first time I have heard about antialiasing in SW here. Do you or does anyone else (@Danne?!) have/has more information? That sounds interesting... Or is it just this ffmpeg antialiasing? Then we can't show it in realtime and can't export to "real" prores.
The best algorithm I knew until now is AMaZE against moiree: not perfect, but way better than most others...

Yeah... just switch it on and all should be fine. Can you upload the file (at least some frames of it)? So we could analyse what is going wrong. What was the setting used, and on what camera? Are you on Win/OSX/Linux?

Hi, no sry. ATM we still do nothing with H264 Proxys. You only can open MLVs and look at them, cut them and build new proxies. With the same cut settings but processed, you export ProRes or whatever then and exchange the files in FCPX or whatever you use. A workflow can be then:
1. Open files in MLVApp, sort out bad ones (delete them).
2. Create proxys
3. Cut in FCPX, Premiere, ...
4. Color-Correct MLVs in MLVApp
5. Export ProRes4444
6. Relink files in FCPX,...
7. Export final video

@masc What do you think of making it default profile? I think it looks better on 97% of images. (Edit: didn't we already do this? Default seems to be standard for me on every version I open so I might be going insane)

Tonmapped is the default profile. You'll see when importing a file.

Hm, but MlRawViewer is far away from real realtime as well. I would say MLRV bilinear = MLVAPP AMaZE cached and MLRV AMaZE = MLVAPP bilinear in terms of speed on all of my systems, no matter if Win or OSX.

Wow! This app looks so promising!
I'm wondering, is it possible to implement different fps playback function? For example, I have 50-60fps footage, but I'd like to preview it at 25fps (in slow motion). It would be great to have some options like:
- native fps (as it is now)
- custom fps (speed playback options)

This is implemented. Go to export settings and set fps override. That also works for playback.

MLV-App: Compiling for Linux openSUSE
I just finished the english version of my tutorial:
https://seescho.wordpress.com/tutorial-englisch/
I hope, I didn´t forget to much...

Thank you!

And... funny: on none of my computers MlRawViewer feels faster as MLV App... am I doing something wrong?! How do you get it so fast?

What??? That should be way faster! Have you found the caching option? Let it cache until it says "Idle" again and then play. You should get around 15 frames with an i7!!!

When I delete some video, first video is always selected. It will be better select next video with nereast index

Was already done.

Oh, I wonder how it was done on mlrw, preview it's an important thing but I guess it's still usable at 5-8 fps.

So slow?! On my 8 years old Core2Duo MacBook I get something between 10-12 fps with v0.13... that looks not so bad...

Please, can you add more key shortcuts?

Sure...

I used this key shortcut in unsupported application  MlRawViewer:
- Cut In/Out (e. g. Shift+I/Shift+O when 'I' is used for Info)
- go to previous/next video (e. g. K / J)
- delete selected video from session (e. g. Del)

Done.

Thanks, yes that is the same I got the crash now to... but only each 4th or 5th try, but it happens. I also think I found the reason why, but I have to clearify with Ilia, because I don't understand the code 100% there.

Okay... I think I have it. Got the crash now too and can debug.

Thanks a lot for the information and the nice words.
Does it even crash when you have just one MLV to export, or does it happen for batch? Do you load/save sessions, or just import -> adjustments -> export?

Hi, Masc, ilia, bouncyball, Merry Xmas to you all. Noticed a bug when i try to export, using apple AV Foundation, it crashes when i hit the export button, although for some strange reason it always seems to crash when i hit export for the first time, then i re-boot the app, and it seems not to crash after that, only sometimes..

Here's the crash report https://www.dropbox.com/s/s4mvlijbb72toch/crash%20report%200.13%20mlv%20app.rtf?dl=0

Merry xmas!
Please be exact and write more information. The report tells, that the app crashed while building a frame. This does not happen when pressing the export button, that happens between filedialog and export ready. Then: what format did you export, there are 3 AVFoundation formats. The MLV which causes the problem would also be a nice to have for debugging.

Right, MLVFS does only bad pixel fix, see it. Then try another tool.

You forgot to write which camera you use and which programs. But I think these dots are focus pixels. Try to fix focus pixels with the mlv converter tool you use and it will be fine (mlv_dump, MLVFS and MLV App can do this, maybe many others too).

Is it possible to upload the MLV which causes this problem? I tried with some of my MLVs and this does not happen.
Edit: is your rar archive corrupted? I tried to unpack with 3 different proggis... no success. But the MLV would be more interesting for us.

Works great. Just set export settings to av foundation and boom prores4444 comes flying out.

Yeah, that is as it should be. Cool if it works.

Here comes a next release of the Qt version of MLV App with some new features:

• Apple AVFoundation export on macOS: 12bit ProRes 422, 12bit ProRes 4444 and 8bit H.264, without audio only for now, and without resize
• New bad pixel removal option, which analyses all instead of one frame
• Performance on MLV bulk / session import improved
• Create and load MAPP files (this files include all required information from the original MLV, plus video and audio frame index. If .MAPP file already created, importing is lot faster especially on slower HDD)
• Some BugFixes

https://github.com/ilia3101/MLV-App/releases/tag/QTv0.13alpha

Thx! I used resolve with MLVFS and the results look better than the pro-res 444 output with bilinear. Maybe the Amaze option is better? I saw the bokeh problem and thought to use Bilinear.

You can't say that any way is better than another before having seen the result of the special clip. I also did many tests with bokeh clips (using my lenses), but had never an issue as OlegK - not with Resolve, not with bilinear and not with AMaZE. Watch each result and than decide which fits best for the clip!

A reason may be that the frames in your MLV are not in the right order. In v0.12 we did not care about this yet, what could result in black frames. Some days ago bouncyball fixed that by replacing the false frames in the right order. This will come with the next release.
With this few information you gave, I don't know if it is really this reason. Best is, if you upload some seconds of your MLV (the seconds where you get the problems), so we can debug.