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

Pages: [1] 2 3 ... 77
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.

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.

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.

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.

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:

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

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

Dots can be removed using focus pixel maps. Interpolation method 3 looks nice for this example:

General Development / Re: LiveView hacks (write speed improvement)
« on: April 22, 2022, 07:55:12 AM »
Another thing to consider:

The MLV App processing time for a 4.5k 1x3 dual ISO footage is about 4 times longer than a 4.5k 1x3 without dual ISO, about 10 to 12 times longer than a 1920x1280 1x1 without dual ISO. For fast turnaround time projects, 1x1 2k actually has such an advantage.
DualISO processing is very complex and the actual algorithm is single threaded only. Yes - this is slow, but a lot of math.
But I don't think non-dualiso 4.5K is 2.5x..3x slower than 2K 1x1: the amount of pixels is more or less the same. The only difference is a single 3x stretching - but this is way faster than you write. As soon as you rescale 2K to e.g. 4K and 4.5K to 4K both will need more or less the same processing time.

Is there a script or a way to do frame stacking (For Noise Reduction) from within MLV app?
You can average n frames to one single frame. But this feature is more for creating dark frames. You won't get a video with that.

10bit RAW is a complete different thing than 10bit ProRes. With 10bit RAW there are just a few tones in dark areas, so getting banding is very easy. Better use 12 or 14 bit RAW to avoid this.

Premiere has no real RAW engine - it just shows the DNG "somehow". While AfterEffects uses the Adobe ACR RAW engine. Use AE if you like Adobe colors with RAW footage!

Could i ask, when i import the MLV file, how does MLV app know to connect them if i'm not importing them all together? Is it because they're in the same folder?
MLVApp automatically scans the entire folder for files with the same name and endings M00, M01,... , when opening the MLV file. So MLVApp knows all those files are just one clip.

just a bit suggestion, in MLVapp sidebar I think it's better to put profile tab and lut tab above processing tab
so we don't have to scrolling up and down when choosing different profile or enable creative adjustment and lut.
this is more convenient I think.
That will be different for each user. But things like a LUT or a profile normally can be adjusted once for an entire project. Then Ctrl+C, Ctrl+A & Ctrl+V. ;)

is there an easy way to compile mlvapp?
I couldn't compile using qt6 and got an error like no "make" or "qmake" something like that..
It is very easy to compile MLVApp (if not on Apple Silicon). You must install Qt5 (e.g. 5.15.2) - not Qt6. MLVApp is not compatible to Qt6 and probably will never be. For further instructions, see:

After Qt5 installation, on macOS the entire compile process looks like this (on other OS more or less the same appart from compiler name):

Visual C++ libs are not needed, because it is not really compatilbe with many standard C/C++ libraries - we use mingw+Qt. All needed libraries are included in the package. 1.12 and 1.13 also should have the same dependencies. Maybe 1.13 was compiled with a newer Qt, which often has different system requirements than older versions. If you find a system where it works: in menu->help->about Qt, you can see which Qt library was used to build the release.

For getting more information on Windows systems, I think you'll have to install the entire Qt framework and debug with this. macOS brings a very detailed crash report and tells exactly the reason... unfortunately Windows doesn't do this.

Strange. Never tried such an old CPU. Normally a fresh Windows 10 is okay. No additional library is needed.
I know it working on:
- MacBook and MacBook Pro 2010: Core 2 Duo P8600 2.4GHz on macOS 10.9.5 and 10.13
- MacBook 2008: Core 2 Duo T8300 2.4GHz on macOS 10.6.8, but using Windows 32bit version via Wine, without anything else installed

"LANCIR offers up to three times faster image resizing in comparison to AVIR. The quality difference is, however, debatable. Note that while LANCIR can take 8- and 16-bit and float image buffers, its precision is limited to 8-bit resizing."

--> Yes, but it is just faster. We internally use 3x16bit color information, but this would finally limit the pipeline to 3x8bit, but consuming the time of the 16bit pipeline for all other algorithms. (256 colors of possible 65536 per channel as result)

Raw Video Postprocessing / Re: raw2mlv processing
« on: March 17, 2022, 09:01:02 AM »
These are the sources for the version included in MLVApp (or maybe slightly older, but not "much"... okay... maybe also the tagged release... but in theory it all works the same).
It uses LibRAW, LibMLV. All included in subfolder application raw2mlv. Can't see any virus... but maybe someone else...

@CommanderLake: no idea how to help with this few information. Maybe you should upload your darkframe and a frame of the clip which brings up the problem. So we could analyse and help.

@takoyaki: no idea what other apps do and I never compared this. I just can tell that MLVApp linear funtion does this for linear tonemap: output=input.

Thanks for the request. I could offer realizing something similar to Lightroom - the theme is still dark, but the color of the viewer background could be changed. It would look like this:

Changing an entire theme is difficult - hundreds of line of code and no guaranty it looks good in the end...

Edit: feature commited to repos.

Those minor things should be fixed in latest commit already. But thanks for reporting!

Looks like focus pixels. Currently there is no way to fix them in dualiso footage.

One DNG? I can't compare anything with one single file. And DNG is the output - can't check for bugs or MLVApp behavior with that.

Would be better if you upload the problematic frames as MLV. Can't help with processed frames...

In the end DNG is RAW. MLVApp won't change e.g. exposure. Did you record HDR video? Brightness changes in all frames here.

I can confirm windows version works and linux version too.
I again found 2 bugs and fixed them on renaming function...
On Linux it was possible to rename clips so far?

@ lil4ml: Seems I got it working now also for windows. But would be cool, if you could test on your side. If you have a Qt 5.13.2 mingw64 installed, compiling is very easy. Just load the .pro into QtCreator, select "Release" and hit compile button.

Pages: [1] 2 3 ... 77