MLV App 1.14 - All in one MLV Video Post Processing App [Windows, Mac and Linux]

[bouncyball]

could you post samples from the same clip?

+1. Gonna be nice, cut original MLV with mlvapp.

[arrinkiiii]

Hi,

They are from the same clip, the 3 photos, maybe not from the same frame. I can send the MLV if you guys want.


I just install the version that have 14bits lossless compression. Is this better that 10 or 12bits?

Many thanks

[Bender@arsch]

There is maybe a problem with deleting cardspanning Raw files. In my Case MLVapp crashes and delete only one file (MLV file, not the second).

Tested on Windows.

[masc]

Cannot reproduce on my computers. Maybe you could debug this problem and tell us the line where the app crashes?

[Bender@arsch]

Sry, but I don't know how this works. But I'm mean "deleting from disk", maybe this will helps.

[masc]

But I'm mean "deleting from disk", maybe this will helps.

I understood what you did... but if I do the same on my computers, there is no crash and the files to be deleted can be found in trash. Best is to debug on computers which show this error. Here I can't do anything, as long as I can't reproduce.

Sry, but I don't know how this works.

That is quite easy. Installation procedure:
https://github.com/ilia3101/MLV-App#qt-app-windows

Compiling: This is on macOS. But on Windows it is 99% the same.

[mlrocks]

I am optimizing my old desktop with a P8B75M socket 1155 MO.
The old i3 gave the performance of about 45 minutes per min UHD 1x3 mlv footage from 650D.
Changing the import and export folders from an internal SATA2 HDD to an internal SATA2 SSD does not have any improvement.
Changing the cpu from i3 to a Xeon E3-1270V2 improves about twice, now about 20 minutes per min UHD 1x3 mlv footage from 650D.
Will test if the NVME SSD on the PCIE 2.0 X4 improves the speed. Maybe not due to the experience from HDD vs SSD.

Update:
NVME M2 Samsung 970 1 TGB with an IO Crest adapter on PCIE 2.0 X4 does not improve the speed.

So cpu cores is the only critical factor for mlv app processing time. IO RW speed seems not the the bottleneck.
I checked in resource monitor that every cpu thread is 100% full even when one mlv app instance is running.
The only way to shorten the processing time is to have a latest advanced 16 core or 32 core AMD Ryzen workstation, which is expensive, or have a rendering farm comprised of several powerful and power consuming old dual cpu workstations.

[masc]

The calculation is easy: if your footage has maybe 50MB/s and MLVApp shows it realtime, your disk must have a minimum read speed of 50MB/s. That is not much. On CPU side you'll need a ~ QuadCore 2.5GHz on macOS and Linux and a faster machine with Windows for realtime processing. MLVApp processes 100% on CPU - so yes... it is all about the CPU if you want a fast processing. And about an OS which brings this power to the application.

[mlrocks]

The calculation is easy: if your footage has maybe 50MB/s and MLVApp shows it realtime, your disk must have a minimum read speed of 50MB/s. That is not much. On CPU side you'll need a ~ QuadCore 2.5GHz on macOS and Linux and a faster machine with Windows for realtime processing. MLVApp processes 100% on CPU - so yes... it is all about the CPU if you want a fast processing. And about an OS which brings this power to the application.

Thanks for the explanation, MASC. This makes sense.

Intel® Xeon® Processor E3-1270 v2 is quad core cpu; Processor Base Frequency. 3.50 GHz ; Cache. 8 MB Intel® Smart Cache ; Bus Speed. 5 GT/s ; TDP. 69 W. If on linux this cpu can give a realtime processing, this means that on Windows 8.1 the processing time is 20 times slower by my experiments. I will definitely try to set up linux boxes for raw processing improvement.

I will build a render farm using my old servers. Probably will be 8 cpu 64 core xeon e5-2670 totally. All of the workstations will be linux based, except the master desktop is windows 8.1 based. The master is not a true cluster master, just copying files to other workstations manually. It will take some time to build up and test. Finally, I think the planned render farm will render 1 h per h of UHD 1X3 from 650d, or 5 h per h of 3.5k 1x1 dual iso from 5d3. It may take about 20 to 30 dollars electricity by my city's rate per h of 3.5 k 1x1 dual iso footage.

[masc]

20 times slower? So you get 1-2fps? With default settings? There must be something very wrong.
With "render" you mean export? Note: exporting is processing + ffmpeg encoding. Encoding might be again slow in dependency to used codec and codec settings. When testing just MLVApp processing, playback the clip. There is a FPS counter which shows how fast processing is. On a iMac 2011 I get around 23fps for 1856x1044 uncompressed. On 2020 MacBookAir M1 I get 50fps for a FullHD clip. On a Windows 10 Core i7 3.4GHz I get 13fps for FullHD.

[mlrocks]

20 times slower? So you get 1-2fps? With default settings? There must be something very wrong.
With "render" you mean export? Note: exporting is processing + ffmpeg encoding. Encoding might be again slow in dependency to used codec and codec settings. When testing just MLVApp processing, playback the clip. There is a FPS counter which shows how fast processing is. On a iMac 2011 I get around 23fps for 1856x1044 uncompressed. On 2020 MacBookAir M1 I get 50fps for a FullHD clip. On a Windows 10 Core i7 3.4GHz I get 13fps for FullHD.

Hello, MASC. Thanks for your reply.
What I mean "rendering" is to export in h264 high quality (I suppose 8 bit) in mp4 format. Sorry for the misunderstanding.
I just tested quickly the mlv app appimage on one of my linux machines, which uses a low passmark amd athlon 5350 dual core apu. The export takes about 80 minutes per min of UHD 1x3 mlv footage. Considering this does not have hyperthreading like an i3, it is very possibly true that Linux exporting speed is similar to Windows, maybe a little bit faster, but not much.

[mlrocks]

20 times slower? So you get 1-2fps? With default settings? There must be something very wrong.
With "render" you mean export? Note: exporting is processing + ffmpeg encoding. Encoding might be again slow in dependency to used codec and codec settings. When testing just MLVApp processing, playback the clip. There is a FPS counter which shows how fast processing is. On a iMac 2011 I get around 23fps for 1856x1044 uncompressed. On 2020 MacBookAir M1 I get 50fps for a FullHD clip. On a Windows 10 Core i7 3.4GHz I get 13fps for FullHD.

I just tested the playback counting. UHD 1X3 12 bit lossless AR 16-9 24 FPS from 650D with audio.
On my Windows 8.1 desktop, Intel Xeon E3-1270 V2 quad core 3.5 GHz, 32 GB DDR3, NVME 1TGB, the playback is about 3 fps, sometimes 2 fps.
On my Ubuntu desktop, AMD Athlon 5350 APU dual core, 16 GB DDR3, SATA2 SSD 256 GB, the playback is 1 fps.
I used all of the default settings, so it is neat processing.

[masc]

80min??? What the hell...
MacBookPro 2018 with i7 2.7GHz: 1min of 4K 1x3 footage to H.264 "high" takes 13:30min with MLVApp default settings. Playback is at 24fps (around 34fps with framerate override). And that is not fast, compared to the passively cooled M1. Do you export with default settings, or do you enable time consuming features in edit or export area? 1-3fps is very strange... even my MacBook from 2010 with Core2Duo is faster.

[mlrocks]

80min??? What the hell...
MacBookPro 2018 with i7 2.7GHz: 1min of 4K 1x3 footage to H.264 "high" takes 13:30min with MLVApp default settings. Playback is at 24fps (around 34fps with framerate override). And that is not fast, compared to the passively cooled M1. Do you export with default settings, or do you enable time consuming features in edit or export area? 1-3fps is very strange... even my MacBook from 2010 with Core2Duo is faster.

Maybe UHD 1x3 playback is slow? I do not know. I use all default settings just now for playback checking to avoid the setting related issues.
Maybe I will try 1080P footage later to see if the results are better.

Or maybe because the video card?
I apply a 2g vram card on the windows desktop and the apu's gpu on the linux desktop. I know they are very basic.
I thought that mlv app does not use vram or high end video card cuda. If video card is the issue, I will buy better cards once the supply is normal.

Thanks very much for your help on trouble shooting, MASC.

[mlrocks]

80min??? What the hell...
MacBookPro 2018 with i7 2.7GHz: 1min of 4K 1x3 footage to H.264 "high" takes 13:30min with MLVApp default settings. Playback is at 24fps (around 34fps with framerate override). And that is not fast, compared to the passively cooled M1. Do you export with default settings, or do you enable time consuming features in edit or export area? 1-3fps is very strange... even my MacBook from 2010 with Core2Duo is faster.

For exporting experiments, in addition to normal adjustment of exposure, contrast, saturation, vibrance, I also did some adjustment of HSL modules, maybe this caused some time. But from my previous experience, without any adjustment, the exporting time was 30 minutes per minute UHD 1X3 on the old i3 socket 1155. Assuming xeon e3-1270 v2 is twice faster, so it will be 15 minutes. Assuming the amd 5350 is twice slower, so it will be 60 minutes.

[mlrocks]

80min??? What the hell...
MacBookPro 2018 with i7 2.7GHz: 1min of 4K 1x3 footage to H.264 "high" takes 13:30min with MLVApp default settings. Playback is at 24fps (around 34fps with framerate override). And that is not fast, compared to the passively cooled M1. Do you export with default settings, or do you enable time consuming features in edit or export area? 1-3fps is very strange... even my MacBook from 2010 with Core2Duo is faster.

I copied the same UHD 1X3 12 bit lossless footage to my MacBook Air 2020, M1, 8 GB. Downloaded MLV App 1.13 App Image. The playback is 13 fps most of the time, but unstable. Export setting is H264 HQ mp4, export time is about 20 minutes per min footage. All settings are default. Is it possible that the footage has details so delaying the processing? The performance is not as good as yours, maybe 50%?
I suspect that MLV App needs a good video card somehow even though it does not use CUDA. I have to wait for several months to buy some good video cards, because the Asian supply is compromised now.

[masc]

On M1 please use the Apple Silicon version of MLVApp. This one is much faster than Intel version on M1. Link for experimental version can be found some pages before in this thread.

MLVApp doesn't need any video card and runs on CPU only. That's the reason it works on nearly any computer of the past >10 years.

[mlrocks]

On M1 please use the Apple Silicon version of MLVApp. This one is much faster than Intel version on M1. Link for experimental version can be found some pages before in this thread.

MLVApp doesn't need any video card and runs on CPU only. That's the reason it works on nearly any computer of the past >10 years.

Thanks a lot for the tip, MASC. I will try the Apple Silicon version. Best regards,

[mlrocks]

On M1 please use the Apple Silicon version of MLVApp. This one is much faster than Intel version on M1. Link for experimental version can be found some pages before in this thread.

MLVApp doesn't need any video card and runs on CPU only. That's the reason it works on nearly any computer of the past >10 years.

Hello, MASC. A quick question: Will MLV App Apple Silicon version have the same performance on Hackingtosh with DIY Intel Xeon workstation/server? 

[masc]

MLVApp Apple Silicon version: was compiled for ARM64 and runs on Apple Silicon ONLY. It won't run on any other CPU architecture.
MLVApp official macOS version: was compiled for Intel and runs on both, Intel & Apple Silicon (via Rosetta, which consumes around 50% of CPU power).
Source code is identical for both versions. (appart from the commits done since last official release...)

[mlrocks]

MLVApp Apple Silicon version: was compiled for ARM64 and runs on Apple Silicon ONLY. It won't run on any other CPU architecture.
MLVApp official macOS version: was compiled for Intel and runs on both, Intel & Apple Silicon (via Rosetta, which consumes around 50% of CPU power).
Source code is identical for both versions. (appart from the commits done since last official release...)

Thanks, MASC. If I set up my workstation as dual Xeon E5-2670 socket LGA2011, 128 GB RAM, which OS do you think is better, Ubuntu or Hackingtosh for MLV App macOS version?

[mlrocks]

Computer: MO P8B75M, Socket 1155
CPU: E3-1270 V2, 4 core no hyperthreads
RAM: 32 GB DDR3
VRAM: 2GB
OS: Windows 8.1
App: MLV App 1.13
Setting: default
Export: mp 4 h264 hq


Footage from 5D3
1. Anomorphic 1x3, 1920x2340, 14 bit lossless, 24 fps, playback 5 fps, export time 25 min/min footage
2. 3.5k 1x1, AR 2.67, 14 bit lossless, 24 fps, playback 5 fps, export time 10 min/min footage
3. 3.2k 1x1, AR 16-9, 10 bit lossless, 24 fps, playback 4 fps, export time 10 min/min footage
4. 3k 1x1, 1920x1920 AR 1:1, 14 bit lossless, 24 fps, playback 6 fps, export time 7 min/min footage

Footage from 650D
5. UHD 1x3, AR 16-9, 12 bit lossless, 24 fps, playback 6 fps, export time 12 min/min footage
6. Movie crop mode, 1800X1000, AR 16-9, 14 bit lossless, 24 fps, playback 9 fps, export time 4 min/min footage (This is the closest to 2k 1x1 in my previous tests, used as a baseline here. My previous experience of 2k 1x1 was 10 minutes per min footage on an i3 cpu, very possibly 5 minutes on this quad core cpu.)

So, 5.7K 1x3 is about 5 times slower than the 2k 1X1, 3.5k 1x1 about 2 times slower. UHD 1X3 is almost the same as 3.5k 1x1, about 20% slower. 5.7K 1x3 is about 2 times slower than the UHD 1X3.

A render farm composed of 4 dual cpu Xeon E5-2670 workstations with 16 cores each using Ubuntu LTS may do 1 hour processing time per hour 5.7k 1x3 footage. Electricity bill may be 10 dollars per hour 5.7k 1x3 footage. This kind of render farm makes 5.7k 1x3 ml raw processing practical. An equivalent spec Mac Pro may be $15k to $20k, if DIY with AMD Ryzen CPUs, may still be $7k to $10k.

Hope the dual ISO processing be multithreading in the near future, this kind of render farm will make dual ISO footage routine too.

[masc]

1min RAW 1x3 5.7K (1920x2340) 24fps on M1 MacBookAir:
- playback 11fps
- export with ffmpeg to 5760x2340 H.264 high with MLVApp default: 14:20min
- export with AVFoundation to 5760x2340 H.264 with MLVApp default: 11:00min

1min RAW 1856x1044 25fps on M1 MacBookAir:
- playback 50fps
- export with AVFoundation to 1856x1044 H.264 with MLVApp default (AMaZE): 1:20min (edited: 1:00min was wrong here, measured again, so no realtime)
- export with AVFoundation to 1856x1044 H.264 with MLVApp default (bilinear): 0:30min (more than realtime, good enough as proxy)

1min RAW 1x3 1440x1836 24fps on M1 MacBookAir:
- playback 21fps (with alexa log-c preset 24fps)
- export with AVFoundation to 4320x1836 H.264 with MLVApp default: 5:20min

[mlrocks]

1min RAW 5.7K 24fps on M1 MacBookAir:
- playback 11fps
- export with ffmpeg to 5760x2340 H.264 high with MLVApp default: 14:20min
- export with AVFoundation to 5760x2340 H.264 with MLVApp default: 11:00min

1min RAW 1856x1044 25fps on M1 MacBookAir:
- playback 50fps
- export with AVFoundation to 1856x1044 H.264 with MLVApp default: 1:00min --> Realtime export

This is really good, considering the electricity bill is almost negligible.

[mlrocks]

Hello, MASC. Just a quick thought.
Is it possible to add a new tab in MLV App for 1x3 processing. This way the workflow is optimized for 1x3 footage, the sharpening can be put anywhere it is proper.
Not sure if this is practical.