Messages

I found!
I was sure my 5To hdd has 1To left, but yesterday he became full in the middle of a mass convert!
Thoses MLV and DNG take so much space, I did not realize my holiday put an end to any remaining space on this HDD...

Thanks you for your help!

Ok thank you, I don't know what this problem is but since it happen with me using the kimsnot I was drawing some quick conclusion.
Windows also heavily updated 3 days ago, just to say.
I'm still needing to convert those files. I will continue to investigate tonight in calm without the kids everywhere.

Yesterday I was filming like pretty everyday in a classic 1920x1080 all the afternoon.
It seems that I can't convert the half end of the day, never saw this, and I'm pretty sure it's when I flipped my lexar CF to the chinese Kimsnot 128Go to test it one more time (this card worked 2 times before, i rarely used it because I'm not confident).
I can play the videos in MLVApp and in rw2cdng, but can't convert any of them in DNG.
I tried as usual with mlvdump.exe, and after the fail i also tried exporting in different format from MLVApp (DNG, prores, etc...) and with raw2CDNG 1.7.9.
The results are always 1 blank dng or 5 zero ko DNG, or in the case of proRes a zero Ko .mov file.

here is a sample with a 294Mo MLV file that doesn't convert, if someone want to try.
https://mega.nz/file/ndhHWI6K#EvaPX8CRapZG03kRsyhcgkYKGrrWbzyycSEzgMmX8fo

In my mind MLVFS was essentially for mac users, with some stranges things to do to be able to mount one video at a time on windows, but maybe I have misread somewhere.

And for editing in Resolve I don't know, I love resolve and really would like to do it in there, but I know premiere equally well and have my habits, but it's something to try one day.

By reading some recents posts I just saw that adobe had finally added ProRes to their codecs, i tested it, and it solved my issue. But if someone has an explanation or a workaround i will be glad to hear it, because I worked so many years with DnxHD/HR, and I don't know ProRes much...

Hello,

I tried different things for the past months to solve this issue, but now I come to ask some help:

-Everything is fine as always in Resolve with my DNG's converted with mlv dump from the experiment page, export every clips in DnxHR 10 bits 3072x1320 native format
-In Première, once my montage is finished I export the result in h264 as always
-The problem come when I want to export a master of the same montage in Première in DnxHR 3072x1320: the result is squeezed horizontaly

It seems the codec don't want this format, and apply a pixel ratio of his own or something.
I tried force the pixel ratio of the clips and/or of the sequence in première to "square pixel", but the result is always the same once exported??
I also played with other pixels ratios to trick the codec, but not working as I wanted (right click on a clip, modify, métrage (in french, second choice), conform to square pixels

I think it's the codec in Première Pro, and the problem is the same with direct export or sending to media encoder

Since I would like to duplicate or make space if needed on my CF flash if needed, I bought an adapter USB3 to USB-C to connect the lexar reader ton my Huawei phone. The phone can see and copy from the sdcard, but everything I tried for the lexar 1066x CF give no result (un app to read OTG exfat, some others app to my other card un FAT32...)+ it seems risky for my CFcard because unlike windows I don't see a way to be sure to have ejected properly the card, and after some test i was anxious to deconnect the reader with the led alternatively on or off.

With this method it works! I remember doing this the first time I installed magic lantern maybe 6 years back, and since everything works great never have to, or wanted to update the firmware, because all my sd cards with differents versions were rendered bootable with EOSCard.
It's not something I like a lot to rewrite a working firmware only to make a card bootable, but for this 2 particulars cards I will have to.
EOSCard was a better solution for me, but it seems to have problems with "kimsnot" cards.

I tested the two card and there is no errors.
I'm using EOSCard 1.4 with admin privileges, the cards are not physicaly locked and i'm ticking the 2 box EOS_DEVELOP 0x047 and BOOTDISK 0x05C.
I never receive a message or something that's validate that the operation was successful.

Hello,

I bought 2 sd card on aliexpress with "kimsnot" brand, but EOSCard seems not able to make them boot.
Since I rarely use EOSCard, and after hours of trying only to make an sdcard bootable I'm asking the question:
Does Chinese card have an impossibility to boot??
I have the autoexec.bin on the card, who was formated before in the 5d3, and I put the last build for 4K video that's working on 4 others "normal" cards.
I also bought a CF 128Go at 50 euros from same brand....Benchmark seems good, I just hope this card will last more than a year.

Marvelous shots and the filmic grading is superb! Love this work. Some ACR presets like "indian earl" or something like that I presume.

Is anybody know how to achieve 3072x1920, I can't find the good set up in the camera to go up to 3072x1320?

If I understand correctly my bug was a very low probability one that help you discovering another really old one that now make ML even more stable?I'm glad to have been useful!

Thank you for your patience g3ggo, it works! You are my savior 

With --visualize --skip-xref:

Mode of operation:
     - Input MLV file: 'M18-1317'
     -Verify file structure
File M18-1317.MLV opened
File M18-1317.M00 not existing
Processing...
[MLVI]
[RAWI][RAWC][IDNT][EXPO][LENS][RTCI][WBAL][VERS]+++++++++++[ERROR]  Invalid block size at position 0x000009fc
Processed 0 video frames at 23.98 FPS (0.00 s)
Done

And for my smallest file (295Mo):
https://mega.nz/#!Ho1mAJoA!0jBg5yctKbnn1_9MKifXKRlRC8Vc6-RAGp8zTdmgtIw

With --visualize:

[ERROR] Invalid block size at position 0x000009fc

I have a total of 4 files on 26 with the same error, exactly the same setting 3072x1320 23.976 all the day.

[mlv_dump --dng --relaxed input.MLV]

@Danne:
For mlv_dump --dng --relaxed input.MLV, i got the exact same error for all the corrupted files:

[ERROR] invalid block size at position 0x000009fc

@g3gg0:
I tried the code in the same cmd prompt but maybe I don't understand something, "./mlv_dump is not recognized as internal command" (translated from french).
Also tried without the point at the beginning and other things. Sorry.

Edit: I succeed:
Last update:  37426e9 on 2017-06-01 21:58:33 UTC by g3gg0:
mlv_dump: fixed dependency order
Build date:   2017-06-02 22:06:19 UTC

I have some corrupted mlv with the new crop_rec_4k, about 1/10 of the files can not extract with the new mlv_dump. I tried putting those files in an hex editor to compare with others, but i don't know what to do next...

Thanks for any help

Really, it open fine in acr??I was pretty upset by the black preview I come here too quickly...
(You're right, all open fine in acr, it's my viewer, picasa viewer the culprit)!
Thanks for the quick reply Danne!

Sorry to annoy you,

I don't know what I'have done with the latest build (pretty sure a bad choice in bit depth in the hurry) but half of my converted mlv's are just blacks dng (latest mlv dump).
I'm asking just to be sure, but I think this shots are lost?

A sample of the problem:
https://mega.nz/#!vxkkGQJT!8GjEWu1dzUq3yVL7siRQI_u7TuPnFIm-vDmFCELu594

Thanks! All seems to me so saturated this day I was sure when filming I will use acr instead of resolve with a bit of vibrance, and with this music.
Maybe I should have tested the grade on a tv before uploading to see if the vibrance was not to much.

Hello,

-3072x1308 23.976 with new crop_rec
-Graded in ACR
-Lens: Sigma Art 24mm, Sigma 18-200 for aps-c (no vignetting when fully zoomed)
-some shutter speed too high!

I can't made to work any other format than the 3.5k, but i'm very happy!
There is no audio when recording I think it's normal?

http://www.youtube.com/watch?v=hGSgSbdLdt0

Edit: My embedded link seems not working, I don't know why.

crop_rec_4k Apr29 not working here. I have followed exactly the video tutorial, but it result in random multicolored pixels (viewed in Mlrawviewer and raw2cdng1.7.9). also tested with and without fps overide.

dng sample:
https://mega.nz/#!DocmzRJJ!-A96kskYpm7ZqzFynl_4MZH9yd0cfc9O9bNCcrPlM5k

Edit: Ok sorry, I succeed with mlv_dump.exe

That's Worked!
The problem was crop_rec.mo from my last stable release. As soon as i put it into the new build, the error message appear. So I'm going back one more time to "magiclantern-crop3x.2017Jan13.5D3113", because I need the crop mode. I juste wanted to test the 5K 7fps, but not possible with the new build for now apparently, unless I'm missing something.

Edit: Ok I have found the 4K version, "magiclantern-crop_rec_4k.2017Apr29.5D3113", in the experiments tab of the nightly downloads page, for those like me who never had noticed this tab before...

Hello,

First time it happens to me, I can't update to the latest Nightly (and the one just before) because i have an error message at launching:

tcc: error: undefined symbol 'unpatch_memory'
tcc: error: undefined symbol 'patch_hook_function'
  [E] failed to link modules.

I have returned to my last stable version, magiclantern-crop3x.2017Jan13.5D3113. But I was curious about testing the new features...