Messages

Hello,

So there is still no solution ?
Me too I love the raw feature of ML but I can't use it if I have to change my card every 10 minutes for 2K recording on 64Gig card (which is not cheap).
This is really what lacks this camera.

Alex

Hello,
I am sorry to post on this thread that is more related to firmware, but I can't find the menu allowing me to set a higher bitrate for h264 on my canon 5D3-113.
Or is it not available like for the audio menu ?
Thanks
alex

I am actually recording with the H4n, I was thinking that I might take the lineout out of it to feed the canon, but I am not sure the necessity of it. I also have a juicy link DT 454 I am just evaluating the options, but there is no much to do with magic lantern and audio now. I also saw that with the smtpe module i could trigger the zoom with the canon.

Hi there,
I have been trying all the feature until I start working with audio. As said in the documentation only the speaker volume and the beep test tone works with ML on this camera.
If have a H4n or a Juicylink, what else other that manually set the canon audio gain to 1 can I do to improve sound ? The volume is recorded only on channel 1 (left) also I send a 2 channel into the canon audio in.
I could not find anything else on the subject, can someone redirect me to the correct documentation for that camera/firmware ?
Thanks a lot.
Alex

Top ! It's working.
I checked the hash.
I used a CF card.
That seems to be it.
Does that mean that I could have problems running ML on the SD card ?

I have done exactly the steps as you described them.
I also did it that way before posting. This time I even changed the SD card in case.
I get the same results, exactly as I described it in my first email. The cam screen goes black and the led slowly blink ad vitam eternam.

Please help !!!!

Edit : may my *Canon* Firmware 1.1.3 corrupted somehow ?

Hello,
I wonder if I am in the right section for this "I can't downgrade" question.

In my 5dmk3 I have 1.3.3 factory installed.
When following procedure to downgrade using EOS utility (1,2 or 3) I manage to go up the step at which on your mac, it tells you to "push SET on the camera to begin".
Then I briefly see the "firmware update program" window at the back of the canon.
That is briefly because then it goes black, never light again. Instead the red led of the canon battery lights up for 5 seconds, then goes out, then lights up again like that, on and on and on.

That is when I wait and I wait.... The EOS Utility has crashed or spit his waiting wheel at my face. I ask the scary question...
How do I simply shut that down ?

So I turn the camera off at some point, remove the battery to be able to put it on again.
I breathe out when I see that nothing has been damaged but my camera is still on 1.3.3

If anyone has experienced that, I'll be happy to hear about how he or she managed to downgrade that bloody firmware.
Thanks
Alex

I'm sorry,
I did not get back to you, as I have a movie to edit and a baaad deadline.
I don't have time to put the files online nor to test anyfurther, but basicaly,

I have a directory of .mlv
I right click on that directory to choose service>MVLFS et choose an empty directory. For 265 .mlv I have 265 .MLV directories which contains
1 _PREVIEW.GIF file
X .dng files
1 .log file
1 .wav file

That is to answer part of your previous questions.
The problem is that for one .mlv that last about a minute in mlrawviewer, I have only 1 .dng produced
and for some others I have the wrong amount of .dng files.

I did move the .mlv files that had not been converted correctly in a separate directory. and I mounted the directory via the services again. To my surprise, the file that used to output only one .dng had about the right amount of .dng this time. I am saying about because when comparing with the output of mlrawviewer, some .dng where still missing.

So I don't know. It changed something to isolate them into a different directory but it didn't really solve the problem.
I am not running mvlfs through the terminal so I am not really sure how to ouput the verbose version of it.

I'll get back to that when I have more time but right now I can't be diverted too much from my editing.
Alex

So you have only one file in the mlvfs output folder when you navigate there? No GIF? No WAV? Screenshot of the folder contents?

heu... that was not for me right ?

Hello,

I did not know where to post this, but I have discovered what I think is a bug from MLVFS and I wanted to report it.
I first used mlrawviewer to convert my mlvs to dngs but as I use the cinelog LUT and that they advise to use MLVFS because of its respect of metadata blablabla, I did another convertion from mlv to dng using mlvfs. And that point is important because I could have never found out about the bug if I had not kept the first export from mlrawviewer.

As I were editing, I found a shot of only one frame. I found that strange so I decided to compare that dng (produced by MLVFS) to the dng produced from mlrawviewer. I found out that the shot was actualy a minute long. I did another export from MLVFS just in case and it did produced the same one-shot DNG. A few hours laters similar problem with a shoot a few second long whereas I remembered having at least 2 minutes of ongoing action. I exported the DNG again from MLVFS and had the same shot with the same short length. I compared with the dng from mlrawviewer and found out that my clip was -as I thought it would be- 2minutes long.

My conclusion is that for some reason (that have nothing to do with the computer performance while exporting) MLVFS produced shorted DNGs. This looks clearly like a bug because if I repeat the export, the produce DNG is exactly the same, it is not a random stop.

I thought some people would know about it. This is very bad since, you really don't know if your shot is shorted or not.

Thanks.
Alex

If someone could confirm me that the prores files will only be used for editing and that I will swap them with the DNG at the end, that would be cool.

Andy,

I am working with cinelog and am following your guide.
I am at the stage where I can fine tune my WB. You say it is time to get it right as this will be permanent.
This is something I am not sure about.
We are preparing prores export to be able to edit in our favorite NLE. Okay
But when the editing is done, we will come back in Resolve and get rid of the prores to work again on our DNG files, right ?
It is then not that a big deal if we dont set the WB correctly at this stage, right ?

Or am I missing something ?
Alex

Hello all,

I have tried to export my DNG from my MLV through mlrawviewer and MVLFS.
The DNG produced by MVLFS is twice as big as the DNG produced by mlrawviewer.
Each frame is around 4,2Mb with MVLFS against 2Mb with mlrawviewer.

Can someone explain this to me  ?

Thanks a lot.
Alex

I guess my question is :
is there a difference in quality of the DNGs resulting from either one of these converters ?
MLVSF is interesting since it does not really convert but instead gives you a real time access to DNG, which is indeed very good.

As it is the first time I work with CINELOG, I just want to make sure I don't do something bad in the process.
Alex

Is there a reason why you don't recommend mlrawviewer ?
Thanks anyway.
Alex

Andy,

I am about to buy your cinelog colorspace.
I have shoot raw using magic lantern on a Canon 5D mark III. I kind of understood there were problem with RawMagic converting into DNG. What is the best option to convert from .mlv to DNG ?
How about Mlrawviewer ? Is there some special settings to use ?

Thanks for your input.
Alex

Just want to be sure :

Using one of the LUT (LOG-C, C-LOG, Rec709, etc...) when exporting into DNG is totaly useless, right ?

Alex

Hi DeafEyeJedi,

Thanks for the advice, but maybe my question was not clear enough.
I did not ask what was log but which one to choose in order to keep the original data from mlv to dng.

Thanks
Alex

Is it possible to add the links of the download page on the first post of this thread ?
I have difficulty to find the last version.

Beside, I have a question to all users. I find it difficult to choose the colorspace that I really need. If I convert to prores, I will be safe with a rec709 or a lut near that. But when going to DNG, I always wonder. I'd like to keep it original and I am not sure what log it is. (if it is a log) can someone tips me on that please ?

Thanks
ALex

Hello,

I am going to be the second pita to ask dummies questions, but the fact that the sticky post on the raw guide is not up-to-date (the first thread), a lot of things confuses me.

I have a canon 5Dmk3 initialy 1.2.3
I install ML and had no problem to record mlv execpt that my card would not record more than 1 minutes (exfat and MLoption Checked) and the video zoom x5 was all pixel grey, unusable.
I read that downgrading to 1.1.3 could fix some problems and be faster and that is was that was suggested right now. So, I downgraded to 1.1.3  and install ML again.

Now I can't record mvl files without skipping frames althought the Wspeed is around 90MB/s and my card is 160MB/s (x1066).
The zoom is still not working
The play back of the footage is quite slow (but I did not expected it to be better)


I'd like to be sure on a few points :
- 1.1.3 is still to be prefered to 1.2.3
- the question of the bootflag is not a question anymore since you can remove it if you want.
- do I have a bootable card ? I read to use EOSdisk, but that is no more a concern right ? (it is still on the first thread of the sticky post "Raw recording guide for beginners"

Thanks a lot for your time.

Alex