Messages

Hey Ted, got confused a little bit. The new version (1.9.2) is the same as 1.9.1 but with the programs updated. You should extract 1.9.2 and use it as it is, without overwriting, adding or changing any files.. mlrawviewer is external, shouldnt be a problem. One thing, I didnt change the label in the title of the program cause i was too lazy, lol..

tony, have you tested this? Should this replace the one in the tools folder of your app?

I tested it and uploaded a new version of my converter with this version of mlv_dump. But a simple overwrite should work as well But it also happened that I forgot to upload the nconvert.exe for the thumbs (I think) and thumbs weren't being created. So I made a new version.

this is probably a temp issue, and probably because you are updating the file or something but i'm getting the Dropbox error "Nothing Here", Just Wanted to let you know.
can't wait to test it!
Cheers!

Hehe, forgot to update the link in the first page, thanks man!

Hey Tony,

I mean I'm really doing something wrong.
I tried this new version, tried the 1.6 one also.
Everything works perfectly except that i never get a proxy in the end. I selected correctly the 3 programs, i can preview all the footage, well, in resume everything looks ok until the end of the export.

It creates the TIF's but then deletes them and no proxy appear. I tried all ProRes options, no luck with any.
I know this is a bad issue report, but really don't know what to describe.

Hey! This error should be fixed in 1.9.1.. did you decompress the contents of the zip in a separate folder? Because if you mix it with the old one it may create problems... that bug should be over..

So i got this error today while trying to format a 4gb mlv file with proress444 proxies.
Im on windows 8.1 using mlv to dng batch 1.9.1

I tried to send it through again and i got this

Then this


Tried it again, here is what the error message says

See the end of this message for details on invoking
just-in-time (JIT) debugging instead of this dialog box.

************** Exception Text **************
System.ArgumentOutOfRangeException: Value of '-73' is not valid for 'Value'. 'Value' should be between 'minimum' and 'maximum'.
Parameter name: Value
   at System.Windows.Forms.ProgressBar.set_Value(Int32 value)
   at WindowsApplication1.Program.My_BgWorker_ProgressChanged(Object sender, ProgressChangedEventArgs e)

Any one know whats going on?

Grr, still this bug. Will have to put a definite solution to it, it's in my to do list. But I think regardless of that error the programs keeps on going. It's an "interface" error regarding the progress bar. And the ufraw-batch thing, yeah it's done it a couple times for me.. it's not a good program it seems. But I gotta process the tiffs somehow for ffmpeg. I will try with nconvert and see how well it process the dng's. For now I get a pink cast all over the dng's, I can fix it with "autobalance" but it changes a lot of things i don't want. Any help would be appreciated!

v1.9.2:

- Updated version of mlv_dump. it has a bugfix that skips corrupted frames encounter on some recent builds.
- also forgot to include nconvert.exe in previous version, it's the replacement for irfan view.

Download: https://www.dropbox.com/s/7qhncp7pi4t268o/MLV%20Converter%201.9.2.zip

I was just looking in the ML builds and it seems the one I used (March 13th) had problems with MLV header write. So that might be it. Anyone knows about this bug? (I just recorded a whole short with this build)

Ok in response to my posts: it was a mlv_rec bug. The field frameSpace of the first frame was invalid due to a bug in the build. Now g3gg0 fixed it in mlv_dump so it will skip any frame that has an invalid frameSpace. Any chance to incorporate it in mlvrawviewer?

Cheers and sorry for the trouble!

you can use -f a-b  where a is start and b is end frame number.
but i committed a check which should skip a block if its frameSpace is invlaid.
can you try it? (exe)

WOW! Alright g3gg0!!!! That fixed it! I tried with -f a-b argument and it worked, it didn't work with the other version of mlv_dump that I had. And it ALSO works normally, without -f parameter. So wow, couldn't be happier!!!! Is this mlv_dump also faster?

Cheers and trillions of thanks!!

hi, and wow, this software is very useful. i've installed now, first time i use mlv files and trying to experiment about dual iso files also.
all is working fine, but i have some things disabled in the interface (i guess because of the hurry of fixing the proxy bug).
in the specific i have all the "mlv rewrite" and "dual iso" tabs grey and not active. and basically if i export to a dng sequence, the dng files are with the lines (so not processed, i guess).
i don't know if it is about the version of software (tried to download old versions following the links on the thread, but unfortunately they are no more online).
how can i process a dual iso mlv? am i doing something wrong, or simply i have to wait?
thank you so much for the great work

Hey! You have to select the files that are Dual Iso, right click and select "Process Dual Iso", that way the column will change from "No" to "Yes". Should write some manual or something hehe.. The disabled options are like that because they are not finished. Cheers!

This is the log: https://www.dropbox.com/s/rtl91lw3ath363x/log.txt

Basically: "[ERROR] File ends in the middle of a block. Processed 0 video frames"

Hey g3gg0, is there any syntaxis in mlv_dump to start converting from a specific frame until the last one? I used March 13th version in a short and a lot of the files have a bug, in which the first frame is corrupted and mlv_dump can't extract anything.. same bug as Ted Ramasola had.

Anyway any help would be useful! Thanks!!

Hi baldand, I wanted to report a simple bug, I don't know if anyone else has it:

Sometimes mlrawviewer won't open some files, it's random. So when you hit Next key, it skips sometimes 1, 2 or 3 files until it finds one that can open. In the folder, you can see the .wav generated that is 1kb, so it failed. There is no way of opening those files with 1.1.3, will look for a log and try with an older version. Using Windows 7 here.

Cheers mate! AWESOME work!!!!!

Here's log: https://www.dropbox.com/s/kj33bt0iihq6ef0/mlrawviewer.log
The files that wouldn't open are there listed in the log, maybe you can take a look.

I was just looking in the ML builds and it seems the one I used (March 13th) had problems with MLV header write. So that might be it. Anyone knows about this bug? (I just recorded a whole short with this build)

Hi baldand, I wanted to report a simple bug, I don't know if anyone else has it:

Sometimes mlrawviewer won't open some files, it's random. So when you hit Next key, it skips sometimes 1, 2 or 3 files until it finds one that can open. In the folder, you can see the .wav generated that is 1kb, so it failed. There is no way of opening those files with 1.1.3, will look for a log and try with an older version. Using Windows 7 here.

Cheers mate! AWESOME work!!!!!

Here's log: https://www.dropbox.com/s/kj33bt0iihq6ef0/mlrawviewer.log
The files that wouldn't open are there listed in the log, maybe you can take a look.

Hello! Was testing today the 7D with the latest March 16th version:

Won't talk about speeds cause they seems awesome, got a 60mbps card and can get continuous full res at 2.35:1, so awesome.

A few bugs:

- The white framing guide shifts down when exiting Play mode. I have to restart the camera to fix it.
- The clip won't be deleted sometimes, it says failed to delete. Restarted the camera and worked.
- If I do slow motion, the canon framing is not correct. It should be narrower vertically. (btw, 1.40x IS the correct stretch factor)
- The up and bottom overlays end up aligning both at the bottom after touching a few settings. Can be reseted at their original positions after struggling with the advanced settings but there's no point.
- Would LOVE to have an option to hide the sound bars, as far as I know there is one in ML. Because I love the other overlays I get without them, and they are distracting for me really as I'm not recording sound, the sound guy/lady is.
- When I tried to change the ISO while recording raw, the interface hung up, I hitted the stop button, it came back after a few seconds but my recording stopped.
- On crop mode, I don't get a proper framing ratio and the 5x icon doesnt go away... I think when I tested it with another version it was all grand.
- EDIT: And the remaining/eleapsed overlay doesn't work, such as also the free card space.

Those are all I think, hope they are of any use... And btw so many interface improvements every time I install a new version. Almost so perfect!

Cheers!

1.9.1:

- Fixed the proxy bug, it was very silly. Sorry about that. Should be working fine now.

You will see more options but disabled, that's because I was in the middle of implementing new stuff and hurried to fix this urgent bug.

Link: https://www.dropbox.com/s/0ljq4dl253sktyi/MLV%20Converter%201.9.1.zip

Cheers!

@Tony
Are there any plans for a os x app?

I wish, but for now I have no idea how.. and I have a lot planned. Maybe when I'm finished I'll do the full port, but for now doesnt make sense to me because there are a lot of features missing (and I don't have a mac for now hehe)

@Tony, this aplication looks like will match perfecly my transition from the .RAW to .MLV (leaving Rawanizer behind), but I'm having trouble getting the proxies.

I followed the first post from start to ending. I do state each folder correctly, i selected the proxy type (tried all of them), it extracts the DNG's, then exports the TIF's but in the end it just deletes the TIF's and says convertion done, with no proxy file generated.

I'm pretty sure something is wrong on my side, but I would love to get your help on this.

Thank you

Hey Hugo! As I said above, there seems to be a simple bug in 1.9.. will fix it today and upload 1.9.1!

Maybe it's a simple bug as I changed stuff and really didnt test proxies in 1.9.. cause i thought they would be fine, as I touched nothing from them.. but apparently something caused a chain reaction in the code.. will look into it, thanks for noticing.

Hi, Tony

Yeah, that's the tool. And there are two methods to clear up pink dots. Using that special tool and using chroma smoothing thingy. The PDR tool is best but you have to know the exact resolution of the frame since the dots are manually programmed according to the position of the PDAF on the sensor.

The chroma smoothing sometimes leave artifacts on magenta colored stuff.

the Raw Therappee cleanup is basically the same as running a magenta defringing on lightroom/ACR, but you'd need a strong defringing, causing artifacts on the fringe of everything magenta. Plus sometimes it leaves black dots when you sharpen the pic a bit

This is applicable with cameras that has EOS-M hybrid AF sensor like the 650D and 700D. (and the eos-m itself) since MLVs recorded from them also records the AF points.

Would be nice to have this function batch executed when waiting for the DNGs to complete.

Btw, did you get the jar from the github? (I think the one linked in the post is outdated)

Also, for clarity: Alex's PDR is the raw2dng cs2x2 and it works great too (I think this is the latest one: http://acoutts.com/a1ex/raw2dng_cs2x2_ahdlike_noise.exe)

PS: MLV has --cs2x2 too (no idea how good it is though. Never tried it.)

Any of which gets implemented would be great though. (I guess MLV's --cs2x2 would be easiest?)

MLV chroma smoothing is already implemented in 1.9, it's under DNG options. You can choose between None, 2x2, 3x3 and 5x5. Anyway I think in mlv_dump cs2x2 is the default setting.

That's the issue: it only works with certain cameras and resolutions, for which the exact location of these pixels is known.

This is why I wrote chroma smoothing, because that algorithm removes all pink pixels with no prior info about them. However, some may argue it reduces image quality by doing that.

Oh ok! That's great a1ex! Thanks!

So, for the people who are asking for Pink Dot Remover, you do not like chroma smoothing? Do you still have pink pixels?

As far as this new information, I see no point in implementing it..

I have a question regarding the MLV header. I'm trying to read the metadata in it, which until so far I have *almost* success. What happens is that the header is not always exact, it varies sometimes by camera model and always varies if you have 'text' or 'take' entries (also depending on the lens model length). What my converter does is to read for example byte number 34, which is the ISO, and boom I get the value. Now, if some entry from 'text' field is present (for example), all bytes in the header shift because of the 'text' length, so the ISO isn't now on byte 34 but on 40 (for example), that causes in erroneous reads of the metadata.

Does anyone know any logic or workaround for this? I'm a rookie programmer but I can manage... But I just don't understand how can it be done. How can I identify a byte that can be anywhere?

Thanks and hope someone could point me in the right direction.
Cheers!

Tony.

I don't quite understand the Pink Dot Remover thing yet.. cause I never experienced it. I found this thread: http://www.magiclantern.fm/forum/index.php?topic=6658.0

Is this it? This program that I download from the first post will fix the pink dots for ALL cameras affected by it? I just notices there is a .jar inside, so have no clue.

Anyone can point me in the right direction so I can implement it?

how many space do we save? 30% imho the savings are not worth the time it needs. its too easy buying another hdd with 2tb.. if i want to archive the dngs, then i'd do a simple zip-compression on the folders. done. but nonetheless, its now built in and some are thankful for that..

I think 50% with lossless. Indeed it is veryyyy time consuming. But you gotta sleep at night.. hehe..

speed gains in Mar 13 but slightly lower max resolution.

CROP MODES
From 2512 , now its 2496 horizontal max.

2496x1200 - 23.976fps- 6" / 16fps- continuous
2496x1134 - 23.976fps- 8" / 17fps- continuous
2496x1062 - 23.976fps- 9" / 18fps- continuous

2048x1152 - 23.976fps-18" / 19fps- continuous
2048x1024 - 23.976fps-52" / 22fps- continuous
2048x930   - 23.976fps- continuous

1920x1080 - 23.976fps- 37"/ 23fps- continuous
1920x960   - 23.976fps- continuous

Higher Framerates 1X mode    48fps / 50fps / 60P

1728x694- 10" / 9" / 5"
1728x560- 1'30" / 57" / 13"
1728x516- continuous / 1'12" / 13"

1664x540- 2'10" / 56" / 13"
1664x506- continuous/continuous/17"

1600x520- continuous/continuous/18"

1536x548- continuous/continuous/17"

1472x568- continuous/continuous/20"

1344x540- continuous/continuous/1'

1280x514- continuous/continuous/continuous

Nice to read this.. which aspect ratio is the 48fps continuous? 1728x516? Hence, which is the de-squeeze factor on 7D also?

yep, results in the same quality, but less storage is needed. Only thing is... takes time to compress it. I don't know how it performs in Davinci/AFX compared to non-compressed DNGs in terms of speed

I didn't do an extensive test.. but I tried different compressions in AE and it was the same in terms of speed.. at least I didn't notice one.