Messages

@bouncyball: you remember my mlv file with missing frames I sent you? When exporting this file (lossless cdng), the missing frames end in strange corrupted dngs. Maybe on other systems this could also lead to a crash - who knows.

You can't compare Footage, because this is completely different processing. As I understood Footage uses Apple Standard Functions / Libraries which only work on Mac (not cross platform) and which don't work with all Cameras. My 5D2 did not work at all at Footage. It may be that Apple Functions are here and there better (Apple is a little bigger than us three hobby developpers). In the end, nobody knows what Apple exactly did in this processing functions, so we can't just copy it. If you know a algorithm (best in C/C++) let us know and we add it if we can.

Also when I trying import MLV files mouse freeze only arrows works, the same in previous build.

It needs some time to parse the GigaBytes... quite normal. But we are working on another solution here.

I also noticed sometimes if you copy and paste attributes to another clip, it could stop playing the file at some point, when you bounce this file it bounce just the part that was playing not whole clip.

Haha, sure... the cutIn/cutOut is also in the receipt. So if you copy from a shorter clip, you paste the shorter cutOut. Will think about that...

I can confirm the results of @reddeercity from here on my 5D2.

This time it even works without frame rate override for me @25fps. mlv_lite 1880x1056@10/12bit, mlv_rec+mlv_snd 1856x1044@10/12bit+audio works like a charme (both non-crop). Yeah.

When not recording the liveview was relativly slow, maybe around 2fps and a "BUSY" was written in the corner left below of the screen and in LCD display. Using the standard nightly this is more fluently... But when recording all is fine again (okay... there are nearly no ML elements on the screen...)

Thx @Doofii. Got the file and program crashes on cdng lossless export (Yeay ). @Bouncyball : could you try the same?

@bouncyball: last time when we had nearly the same on Linux, the "Chroma Separation..." was to long. Is it better if you shorten this?

Has one of these two clips you sent me these artefacts? I could try here. (but don't find any artefacts)

M06_1261

Did you try activating Chroma Separation and Chroma Blur Radius around =3 ? The color may become unsharper, bot those dots are away. And activate Playback->Use AMaZE before settings something up (preview may be slower, but quality is better).

If you don't like the presets, you can always calculate your factors and setup export settings. You can stretch to any resolution / aspect ratio you like. (maximum is 9999x9999, hope that is enough  )

Its regular 2x lens. I am shooting in 3:2 mode. So when i choose 2x from menu i didn't  get proper image, i think its because your 2x mode works with 16:9 or 3:2 footage?
So i isn't works like its shoud:(

Just something wrong.

1.67 i know  its wrong its what gets me final image with program.

If you use a 2x lens, you use 2x width stretch! And nothing else! The 3:2/16:9 mode plays no role here. Pixels have an aspect ratio of 1:1. If you use 50/60fps, you additionally need height stretch 1.67x, because here the pixel aspect ratio is 5:3.

Topic sharpness: the clips you sent me were really unsharp. Here you can't make it better using the sharpen slider. You need to focus right, or if you did, you need a sharper lens.

Lets start from first:
The export is really long. 2 small( 16sec. and 10 sec.clips) files took like 7 min. to complete.
I was using my old iMac at home maybe thats why.

The higher the resolution, the higher the quality, the slower the export. Did you ever render a video on your computer using another proggi? For me that is not way different.

2nd. I cannot remove small colorful dots (weird like Moire) In Slow motion 50fps like twice more of them sharpness 100% so u can really see them.

Without sharpness is much better but still.
P.S. i didn't notice them in previous build.

Nothing did change here. That is moiree. Specially in 50fps you'll get more moiree. If you use the sharpen slider you will amplify moiree.

3rd.
Really need 1.67x in width stretch menu.

May I ask what hardware you use? I heard about 1.33, 1.5 and 2.0 lenses.

Questions:

When i increase file resolution on export does the quality increasing? or its just stretched video file?

No it won't. From where shall come the quality? You may not lose so much quality when cutting and reencoding using a cutting tool like premiere or fcpx.

What difference between Amaze and Bilinear on export?

It is the demosaic algorithm used. Mostly AMaZE looks better, but not always.

@Doofii:
You did not expand the groupboxes, so the elements are invisible. Press the triangle.
And what font do you have there?! I can't allign the program for any font used by all users... sry. If you use system standard, it should work.

For cDNG export: @bouncyball: did you have the same problem on Windows? Me not.
@Doofii: you can shorten the file using mlv_dump. Then you upload only some single megabytes.

prorez 4444 Is 8bit?

Who tells that? No, it is 10bit.

thank you @mesebar2!

Next we will change the apps code a little more, so we decided to release a version now... next version will need a little more time. So here comes v0.12:
- Support for spanned mlv
- TIFF export
- Force bilinear export
- Resize resolution on (batch) export (overrides any clip resolution)
- File error handling on import
- Horizontal and vertical stretch per clip
- Cut in & cut out
- New profile "Film"
- Auto load white balance, if mlv was filmed at sunny, shade, cloudy, thungsten, fluorescent, flash or kelvin
- MASXML saves relative path additionally, so a session can be ported easy to different computers/locations/...
- Changed single frame export to (3x)8bit PNG, so libpng & zlib is not needed anymore
- Many fixes and detail enhancements

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

There are some known bugs and maybe you'll find some new ones
Windows version will be compiled and uploaded next. Have fun!

I'm interested to see if those channels work equally well on the 5D2. I don't have one to test but I suggest uploading a couple of 5D2 test builds for someone that does (or I can build/upload).

If you could do that, I could test... not this weekend, but next week I'll find some time for testing... That is so exciting!

Upscale to any resolution you like on export.

The whole internal processing is at 3x16bit in MLV App. If you like you also can export 16bit TIFF.

Great App.. I tried it and it's awesome.  The only feature that I think it needs is a Highlight slider, if you can implement that it would be awesome.

Yes, I miss it too. But how you can get that indirectly: lower exposure and raise lighten. I use that atm and I am satisfied for now :-)

Is there any way to fix rolling shutter in MLV?

Not yet. If you know how to do (image processing)... please help...

Would be nice to have all shoot info at the Botton like this:

You can open the "Information" dialog and have it always at the side. I think that is sufficient...

And in Footage if your WB at the moment of the shooting was 5600, when you open the file it opens with same value it was shoot, very handy. than you can change if you want, or reset to defaults. 

Yeah, would be nice... but I have not found out how exactly to read that atm. When I understood the mlv header right, that won't work for automatic and custom mode.

If you can do "reset to default settings" for all buttons would be nice too!

Edit->Reset Receipt.

Hej, I played a bit around again with your latest version for 5D2. I have some news:
- 640x360, 25fps, 10bit -> OK!!!
- 960x540, 25fps, 10bit -> OK!!!
- 1280x720, 25fps, 10bit -> not OK
- 1600x900, 25fps, 10bit -> not OK
- 640x360, 25fps, 12bit -> OK!!!
- 960x540, 25fps, 12bit -> not OK
fps override:
- 1856x1044, 2.5fps, 10bit -> OK!!!
- 1856x1044, 20fps, 10bit -> OK!!!
- 1856x1044, 22fps, 10bit -> not OK
- the very first frame is always OK
- if the screen freezes while recording, the file was not OK. If the file was OK, I had a preview while recording.
Maybe that helps... 
Unfortunately I don't have installed the toolchain needed for compiling...

Is it a combination of anamorphic and high framerate stretch? We also need to be able to handle that together with anamorphic. I think best way is to have anamorphic ratio options: 1.33, 1.5, 1.75, 2.0, and an On/Off for additional vertical 1.67x (5:3) stretch

Exactly that I implemented.
Edit: 1.8x is added too.

@a1ex: I think @OlegK uses a special lens for that...
@OlegK: 1.75x horizontal stretch looks right for my eyes. Yes, you can select the factor in the clip receipt now. So each clip can have another factor here. It is also exported with the factor (png & ffmpeg export, not dng). As I wrote, we still have some bugs to fix... when we have a solution here, we will make a release.

Tried out again with latest allocate version. I did not change the mode (3x / 10x zoom). Switched on, LV enabled, record, stop. While recording, picture on screen is not refreshed.

5D2, 1856x1044, 25fps.

I now have downloaded your files. I tried out with the actual revision and v0.10. In v0.10 it crashes when switching between these files - so I can reproduce. The last days bouncyball, Ilia and me, we were searching many bugs and also found+fixed many bugs. Good news: with the latest revision it does not crash. The bad news: we still have some small bugs on the list to fix before we release next version.

Could you please tell me, which horizontal stretch factor is needed to have M06-1260 in the correct aspect ratio? In the actual revision I build a combobox where you can select 1.0x, 1.33x, 1.5x and 2.0x as factor. I am not sure if it is 1.5x, 2.0x or something between...

Tried your allocate-raw-lv-buffer.2017Dec06.5D2212.zip:
- I activated mlv_rec
- after restart and LV enable, in the left corner below is a "BUSY"
- I activated 1856x1044 again
- start recording - picture on screen is no more actualized
- stop recording - live view is back
Then I watched the clip on the computer: it looks corrupted in the same way as the other 10/12/14 bit clips.

Great progress! I tried out your version for 5D2.
Tested standard setting + mlv_rec enabled + 1856x1044 + 10bit/12bit/14bit.
Unfortunately, the picture on the screen starts flickering when starting recording. It is okay again, when recording is stopped. I watched the clips on the computer: it looks the same as on the cameras screen. That happens in all 3 bitdepth modes.