Messages

 

i had that problem and all i did was upgrade my display driver to the latest version. I am using the internal HD4000 from my CPU for graphics display.

http://www.magiclantern.fm/forum/index.php?topic=8825.msg82955#msg82955

I know g3gg0 has been putting tons of time into MLV.  I haven't tried it on the EOS-M. 

1. So is MLV stable on the EOS-M (I only tried it on my 50D)
2. What benefits does/can it give us?

1- yes, for me it has.
2- i also want to know.

Gary

yes, it is faster. can you add in some extras like creating a new folder using the name of the original raw file and then apply raw2dng or raw2dng_cs2x2_ahdlike_noise to extract the dng files in that new folder?

Gary

I just tried the 1.4.6 and 1.4.5 on windows 7 and I cannot get the drop to work at all. It does the drag of MLV raw files and shows the + sign icon on the mouse pointer, but nothing gets dropped to process?? I am using TL ver Nov 23 on the M camera

Gary

TL ver Nov 23, I shot a little bit of 720p24 raw and then I used the ML view function in the File Manager. The data is displayed along with the video, but at the top left it shows the date 25,10,2013 and today is 25,11,2013. I do have the camera set correctly for 25,11,2013??

Gary

Hi Max,
I like this newer version being an exe. I tried it on one raw file from The M and it seems to work okay. It does hang at the start showing only a black screen with a blinking tiny white box at the top right. It took about 25 seconds before it started showing action. I almost gave up thinking it was not going to work. Can you make it so some text pops up saying "Processing now" or something similar so people know it's working and that we should be patient.

Gary

I want to know how your new Pocket works out. What lens(s) did you get for the Pocket?
You have my email, so write me on it.

I have tried using exfat on the M and it does work, but it also brings back the shutter bug and I have not seen anyone fix that bug so far. I can fix the bug by reformatting with a Canon menu in camera, but it then reverts back to fat32... but I do get rid of the shutter bug this way. 

where you at with it, Max? On hold, progressing, given up? I hope you succeed with it for the M so I can shoot raw easier and quit trying to sell my M.

Gary

Dude, I liked watching your movie. Good work. I was wondering how you did all those camera tracking shots that moved to various positions following the guy on his bike? Like around 5:20 or so in the movie. 

Gary

A table with optimal picture quality setting for each camera would be nice, and I think it deserves a separate topic.

yes, that would be nice.

just download the mlv_rec package and use the modules from there

that is what I have been doing. I always get the no free buffer message. i go to ML File manager, navigate to the MLV file i just shot and then select view. It shows building index and then saving index and goes blank and the error message pops up about not getting a free buffer. The M hangs and i have to pull the battery and reboot.

didnt try lately.
can you try the current version?

i have the current version ML. is that what you mean? if not, where is the current version you want me to try.

Gary
I found this=
https://docs.google.com/spreadsheet/ccc?key=0AgQ2MOkAZTFHdHJraTVTOEpmNEIwTVlKd0dHVi1ULUE#gid=0

but i don't know how to use all of that. I was expecting a simple mo file to add to my ML modules folder. I always get the daily builds for the M off of http://tl.bot-fly.com/

Thanks Gary

BTW I think EVERYONE knows you're selling your EOS M. I've counted at least 4 threads where you mention it

thank you.

gary

sounds like exposure is locked. make it manual exposure.

good shot to demonstrate raw and DR

the M

Added color playback support. If it's too slow, press SET to switch back to grayscale.

Do we need a separate thread for mlv_play.mo?

I get an error message when I try to view an MLV file thru the File Manager on my M cam using Nov 13 version. It says "Failed to get a free buffer." I have to pull battery since it freezes thre cam.

Gary

 

... I'm the first idiot on this forum.  Get in line ...

u r def not an idiot.

 

I don't believe the camera devs have any control over which sensels they read from.  They intercept the RAW stream that goes to the LiveView.  I've thought about analyzing nearby pixels for lines, but not what I think you suggest, which is an interesting idea, that the corrupted sensels may "inform" what kind of image is surrounding them.

This problem is not very high on my list anymore because ML, in general, is too disorganized and unprofessional.  This problem would require a team effort, and that's not ML's strong suit.   I don't mean that in a mean way.  It just is what it is.  The Black Magic Pocket Cinema cameras seem to be in supply now and that, and similar cameras, make ML worth some effort, but not too much

I have been following it.