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

[andy kh]

No crash on my win 10 64bits so far

[yokashin]

Everything works fine on windows 10 x64.

Thank you very much for the new version!
Greetings to creators and helpers.

[theBilalFakhouri]

P.S. Windows 64bit users please report back your experience.

No crashes here , Windows 10 x64 1903 , it works fine

[visionbyeric]

I finally got a chance to record what is happening
Usually as soon as I import a MLV file it will crash, as shown in the video below. The last Win64 Version i could user was 1.08

I tried using 1.10 Win32 version and to my surprise, works just fine, not sure if there will be any issues using the Win32 version on a Win64 PC?

Thank You,
Eric

[yokashin]

As we are already with error messages ...
It was while on vacation that I encountered something like this:

I kept the movies on an external disk together with photos in the "zdjęcia" catalog (in Polish).
After returning from vacation, I discovered why all the files did not open

[masc]

@yokashin:
thanks for reporting. Opening files from "zdjęcia" folder is a Windows only issue. Works fine here on Mac. Maybe I can debug this when I am back on a Windows PC.

@visionbyeric:
Also thanks for reporting: I remember (it was a very long time ago) we had such issues sometimes - also on Windows only. In past, Windows did not want to give us some kB of RAM memory, even when there were GBs of free memory left. Whyever. It will be hard to debug this, because this only happens sometimes on some single Windows PCs. On exactly these PCs someone must run a debugger and have a look for the line of code, which crashes the app. But even then I can't guaranty that we are able to fix this.
Did the 1.9 64bit (non static) version run? If not, you could try to install Qt with MinGW64 compiler + Debugger, compile the code, run via debugger and tell us where it crashes. No coding skills needed.
There is no issue running the 32bit version on a 64bit system. It just is not the optimum, so you'll loose one or two frames per second in maximum render speed.

[bouncyball]

Yes @masc's right. Please try 1.9 non static 64 build and report back.

[visionbyeric]

I installed Qt Creator 4.10.2 (Community), I don't know what to do next. I don't know how to compile and debug it. If someone is wants to tell me what I need to do, I'm willing to compile and debug it.

Thanks,

Eric

[2blackbar]

you mean you want to compile windows version ?
Its easy just download qt 13.2, thats the one i have, and open mlvapp.pro in it, then set it up so its using mingw, it will probably do it on its own afair.
Its preconfigured for you.
ITs about 7GB of data.
Mi pomogl uzytkownik cmh ale w sumie samo sie wszystko poustawialo tylko rzy instalacji qt trzeba zaznaczyc mingw

[Walter Schulz]

you mean you want to compile windows version ?

See reply 3705. I think he's following imstructions given there.

[masc]

I installed Qt Creator 4.10.2 (Community), I don't know what to do next. I don't know how to compile and debug it. If someone is wants to tell me what I need to do, I'm willing to compile and debug it.

Its easy just download qt 13.2, ...

Did you install also the framework or only Creator? You'll need (only) Creator+MinGW64+Qt5.13.2(this one I tried and it works fine over here for MLVApp).
To compile:
- Download source archive here: https://github.com/ilia3101/MLV-App
- Unzip, and open MLVApp/platform/qt/MLVApp.pro
- Creator will ask howto configure... make sure a MinGW64 toolchain is checked (at least with Debug and Release)
- at the left bottom there is a "computer" icon: choose "Debug"
- at the left bottom there is a green "play" icon: press it, now it compiles, when successfully finished MLVApp starts automatically
For debugging:
- press the green "play" button with the bug insteady of the button without bug
The debug version will be way slower then the release version, but you're able to get the line of code where the app crashes.

[domasa]

I have problem with import file. How can I fix it?

Code: [Select]

MLV Error
Invalid blockSize '0', corrupted file:  V:\video\M21-1645.MLV
Thanks for the help!

[masc]

I have problem with import file. How can I fix it?

Code: [Select]

MLV Error
Invalid blockSize '0', corrupted file:  V:\video\M21-1645.MLV

Your file contains data, but no header. So MLVApp has no information what to do with all the data. Some months ago someone had the same problem and there was a (modified?) mlv_dump way to insert some header info...

[2blackbar]

I installed everything you mentioned.
Just opened mlvapp to do changes to h264 compression ( gave it 13 instgead of 14)then compiled release , thanks !

[domasa]

Code: [Select]

MLV Error
Invalid blockSize '0', corrupted file:  V:\video\M21-1645.MLV

I fixed it with mlvfs.exe (version "May 6 2017").

[bouncyball]

I fixed it with mlvfs.exe (version "May 6 2017").

Strange. Give me that MLV to debug this issue please.

[a1ex]

@a1ex: Bouncyball was working on a fix for this problem and you could try if it works. It is not yet in the release, but the source is commited to the repos - are you able to compile?

Yes. The fix appears to work; here's a sample file, exported twice:

Code: [Select]

Block: VERS
  Offset: 0x0000023c
  Number: 8
    Size: 119
    Time: 18446744073709552.000000 ms
  String: 'exported by MLV App version 1.10 on 10:08:23 Dec  2 2019; export mode: MLV_FAST_PASS (audio: OFF) '
Block: VERS
  Offset: 0x000002b3
  Number: 9
    Size: 119
    Time: 18446744073709552.000000 ms
  String: 'exported by MLV App version 1.10 on 10:07:33 Dec  2 2019; export mode: MLV_FAST_PASS (audio: OFF) '
Block: VERS
  Offset: 0x0000032a
  Number: 10
    Size: 40
    Time: 18446744073709552.000000 ms
  String: 'MLV App version 1.9'

I had some trouble figuring out how to select a part of the MLV file for export, but eventually found the Cut In & Cut Out dialog on the right side

Thumbs up for now

[domasa]

Strange. Give me that MLV to debug this issue please.

Just MLV? All files are 15 GB...

[bouncyball]

Just MLV? All files are 15 GB...

Yes, that exact MLV which causes this error. Do not cut it, I need the original.

Edit: if you meant one clip is .MLV and subsequent .M01 ... .Mxx = 15GB, then eh... yup, I need whole clip

[ilia3101]

@bouncyball glad you are going to investigate this. Can't wait to find out what causes that error so I can also know to avoid it in libMLV.

[Luther]

Hey, I saw the github issue about a new logo. How about a homage to the horse in motion? There's some nice icons here, as inspiration.
I don't like much the idea of using magick references... it was overused by many already (imagemagick, g'mic, etc), IMO.

[Kharak]

Hi,

I just noticed on 1st post it says “if you want to process DNG’s, use dngapp.com” the link is broken. I never heard of Dng app? Is it a joke?

If it is a joke, then jokes on you cause now i can process dng’s in MLV App 

[ilia3101]

Yes its a joke, and you just made it seem so much funnier

[ilia3101]

Hey, I saw the github issue about a new logo. How about a homage to the horse in motion? There's some nice icons here, as inspiration.
I don't like much the idea of using magick references... it was overused by many already (imagemagick, g'mic, etc), IMO.

My thoughts:

- You have a good point about the 'magic' thing

- I want the colour scheme to be based on mostly Red, Green and Blue (because bayer filter has those colours)

- I don't want it to look like an iPhone app (MLV App's name containing 'App' is not enough to justify that)

- I like reflections and 3D-ness, I also the icons in macOS

I would like a new icon.

My original logo is not amazing. It does not relate to MLV or video or image processing in any way, but I think it looks quite nice. And because it is made in Blender you can do stuff like this:



(from 1.0 release)

[Luther]

- I don't want it to look like an iPhone app (MLV App's name containing 'App' is not enough to justify that)

I agree 100%.

- I like reflections and 3D-ness, I also the icons in macOS

I like it too, but for logos 3D is not very practical, because it must be something simple enough to be readly recognized. Also, it must be in vector (.SVG), in case you want to apply to other resolutions (print in some tshirt, stickers, etc).

My original logo is not amazing.

I actually like it. Maybe you guys could keep it simple and just stay with the original logo, but redraw on inkscape and try to simplify the design...