Messages

ah! thats stupid of me! ok i'll fix it

Its the same - no sound in the converted film but a seperate mp3 with it in the folder.

An idea: If it works with you ... could it make a difference that you may act with NTSC films and me with PAL?

I'm not sure what you mean. I just updated the script, so grab it again: http://tl.bot-fly.com/misc/kit_hdrvideo_v.02.zip
it should now figure out whether files have audio and detect original framerate, whatever it may be, then act appropriately. let me know if this helps.

ps thanks for testing!

Just tried the new one. I did throw my test HDR MOV in the folder an started - but it just sais "There are no *.MOV files in ...
I tried the old one again with the same file and he does find the film.

Update: I renamed the folder from "kit_hdrvideo 2" to "kit_hdrvideo2" and it finds the film ... will start now ...

sure thing! EDIT: i just tried audio and HDR. it failed after several frames, have you had any luck on getting audio+hdr on the nightlies?

Now when you mentioned it I realized that audio is NOT happening in the processed video (there is only a single MP3 in the folder). I was filming a more or less silent test scene and didn´t really care about audio - just watching the HDR result.

Hi to all !
I've received my analog video out cable...
I've managed to plug it keeping the video monitoring on the camera but the sounds seems not to go out... ?

Hi vprocessing - how do you manage to keep the monitoring on the cam with the cable pluged in?

maxotics and mac users,

I've made a couple scripts

1: http://tl.bot-fly.com/misc/kit_hdrvideo.zip
This one converts HDR videos to avi's with ffmpeg and enfuse on mac os! you shouldn't need anything but this zip and a bunch of alternating ISO HDR clips. Everything runs in parallel, including enfuse, so this is pretty useful

If you like these let me know. I could work on a raw movie script next...

Hi jerrykil - I just tried it and it works great!
In germany we use PAL 25fps and I realized that the video comes out with around 30 fps NTSC. Is there an easy way for you to make a PAL version?

do u guys use raw or do you adjust the bitrate?

No I didn´t use both of them till now. I never really tried because there was no time - so this may change in the future. But I guess its too time consuming for use in daily business with the M.
I would prefere the 5d mark 3 for raw video. But still it´s good to have these options on the M too because you never know whats happening and most people do not have a 5d.

1 FOCUS PEAKING
it works, it is usable, but I find it much more effective and easy to use on my mark II than on the M, is that normal? is there something you can do about it? this is my (and I think, all filmmaker's) first concern about the M.

2 SHUTTERBUG
in my opinion, not a priority. if you shoot video (and this is what ML is all about, isn't it?) you couldn't care less about this. M mount lenses have unpractical focus rings and are not so interesting for video, (especially the 18-55, not fast enough and without constant aperture, which makes it in real use an f5.6 lens...).
I personally shoot with my old nikon AIS lenses, which found new life after a ten years' sleep in a box. EOS M, EF adapter, nikon/canon ring and a set of old manual lenses which I modify so that I have a clickless aperture ring. a handle, a viewfinder and you have a digital bolex on a shoestring.

3 RAW !!!
well, I understand the technical interest of the thing, but let's look at the facts: if you shoot raw, your workflow is time-consuming, cumbersome, labour-intensive and then extremely expensive. if you have this kind of budget, you will not shoot with an EOS M.
the real game-changer would be PRORES, but I guess that is not possible, is it?

Actualy I don´t agree with point 1+2.
I´m using the M for professional video work too and I´m using the 18-55 more often than any other lens with the M. It depens on what you film under what light conditions.
Because the M is so small its perfect for putting it anywhere as the second cam like many people do with a gopro for example. Or let´s say if you do an interview and you need more choices for editing. Place the cam beside, zoom in until the picture fits and be ready for action in a few seconds.
Also if you have to be fast and flexible while filming on the go. It´s very usefull to use the 18-55 under those conditions because you don´t have a fisheye effekt (gopro in example 1), its small, light and doesn´t look professional which helpes some times with getting pictures you won´t get with big cams. Its because people change their behavior if they feel beeing filmed by professionals.
18-55 combined with the crop mode gives you a big range and makes it possible too to place yourself somewere in a corner and still make close ups without beeing noticed - perfect for documentary use. And so on ...
To say it short - there are tons of situations were the 18-55 could be a good choice to use - if there is no shutter bug!

For me there is nothing wrong with the focus peaking. I use it all the time and it works perfect for me (the overlay one) together with zebra in any situation. If I do "real" filming like image films (with other lenses than the 18-55 or also other cams) or other work as mentioned before.
So, I´m pleased with it.

You may have turn the camera out of P Tv Av and M modes.

... or you may have to change to "Release shutter without Lens" under "Custom Functions (Nr. 7)". This helpes if the camera doesn´t realize that there ist is a lens in use - which might be the case here. If so it has got nothing to do with ML.

Oh didn´t see that maxotics mentioned this already.

I´m very glad that I never really had a problem which I couldn´t solve with this f... shutter bug that goes on every bodys nerves - hope it will not come to me one day like it happened to some people as I did read here.
Just wanted to mention that I highly respect all the efford which you all put into making this beautiful little cam work!

That autoexec simply jumps to Canon firmware (so obviously, no ML). I'm asking you if the shutter bug is present when you are running it, or not.

NO shutter bug

Can you confirm the findings from post #43?

Hope I did understand right what you mean =
I installed the latest ML version but changed to the "minmal" autoexec.bin you posted.
I got strange pictures on the screen when I installed. After restarting there was no ML.

But ... then I changed back to "normal" autoexec.bin and installed again ... again strange pictures ... and after a restart ML was back again and I have NO shutter bug with the latest version from http://ml.bot-fly.com/

For me it´s getting too confusing but it´s the way it is. The newest version which didn´t work like I wrote in post #45 is working without shutter bug now after using one time the "minmal" autoexec.bin and changing back to the normal one.

I wrote a few times that I don´t have the shutter bug with using the compiled old version from Rootwang.
Now I just installed the newest version from http://ml.bot-fly.com/ ... and here we are with the bug!
So I tried to use the old version again ... but the shutter bug still stayed whatever I did.

I had to uninstal bootflag, then to format the card, install the old version again, instal bootflag ... and it works again - no shutter bug!
There has to be an important differnce between these versions. I think it may be interesting that I had to unistal the bootflag and to format the card to make the old version work again.

I hope this helpes.

funky, try the latest on ml.bot-fly.com, it has everythign you need in the zip. also, do you have a 64gb+ card?

Thanky jerrykil I will try this one later this week. I use the sandisk Extreme 45 MB/s 32gb card 

Is there any new ML compiled version for the EOS M?
I still use the one from Rootwangs post on side 45 which may be outdated.
I do read more or less everything here but I don´t understand what to use and how to compile things. I tried to test the "Latest Build" but couldn´t make it work on my M.
If there is something new which is more or less working it would be nice if someone could compile it again for testing.

If 1280 x720 is related to writing speed of the card this alone should not be entirely bad news. I believe/hope there will be faster SD cards announced soon. Lets see and hope .

Hi pizmon
I´m afraid it has got nothing to do with the speed of the card  - the EOS M writer/reader isn´t fast enough. Around 45 mbits if I remember it right.

This is not good. Please let us find a way to put this behind us. Gary, Alex, 1% and all can we make new beginnings please.

Gary - managing the forums is a big task and everyone is trying to do their best. Please don't take things personally - the forums are about learning and enjoying the process.

- definitly enjoying the process and loving all the wonders that do happen here! Wouldn´t be able to use my privat 600d in a professional manner too without ML. Same will happen to the cute little EOS M. 

2.0.0 on the 18-55mm
1.8.0 on the 22mm

Me too ...

This is the first time I installed ML, as I upgraded to 2.0.2 vanilla firmware before ML was ready so had to wait.

I then held off and watched this thread while the bootloading issue was going on, and then the 18-55 issue. So for me, I've never had the shutter bug. I'm using the rootwang firmware that funkysound pointed me to on the previous page.

That sounds interesting to me so far!
It looks like it really got something to do with installing 2.0.2 on 1.0.6 when ML was still installed on the EOS M because on Gary´s M this version didn´t work without shutter problems. The bug was still there he wrote.

@ Gary: Did you upgrade your M from 1.0.6 to 2.0.2 without uninstalling ML before?

But now I better shut my mouth again because I don´t really know and understand how all this works what the programmers do here.
I´ll come back if I realize something which could be helpful for you all to know.

Hi funky,

I haven't yet installed ML, but I have both the 22mm and 18-55mm EF-M lenses. My camera came with the 1.0.6 firmware, and I updated it to 2.0.2 before taking the plunge with ML. As such, I think I could be in the perfect position to test your theory.

Please could you give me newbie step by step instructions on how to get ML installed the way you have done it? Then we can see whether I experience the bug (hopefully not).

Thanks,

Wigglr

@ Malakai: Wiggir tries to test if there is this bug with Rootwangs version too or not - I didn´t update to any other version until I tried this one and I have no bug. Let´s find out first if this is only happen with my M.

Hi Wigglr,
sounds like a good idea to me.
If I remember it right it´s easy to do. You just download the compiled version from Rootwang (post #1110 on side 45) and do the normal ML instalation which you can find here (even if EOS M is not mentioned because there is no official version till now - the procedere is the same) :
http://www.magiclantern.fm/install.html
Malakai explaned it too.

Funky,
I just tried the Rootwang you speak of and it took one pic at first on the camera, but then I turned the camera off, waited and then turned it back on and the shutter bug is still there. The Rotwang version does not get rid of the shutter bug. I am not sure why your camera does not have that problem. You are the only one that has said that using these EF M lenses with IS.

Gary

Hi Gary - I have no idea too.
Just checked it again, did a few photos and filmed. Turned it of and on, photos ... filming, ... a few times ... still no problems with the shutter. Only focus peaking stops working some times.
Maybe I did something different then you all did. When I changed to the new EOS M fimware, I reseted everything back to 0 before (uninstal ML bootflag on the M, format SD card, ...). That´s why I couldn´t use ML after installing 2.0.2. and had to wait till Rootwang gave me/us his compiled ML version. Since than I didn´t change a thing.
I did read here that you could update to 2.0.2 from 1.0.6 without uninstaling ML before and that many people did it this way - but I didn´t do so. I guess that´s all I can say about what I may have done different.
I have no idea if this made the difference because I do not really understand what you do and how you program all this fantastic ML stuff - but it´s a fact that I didn´t face any shutter problems with the 18-55 efm till now.

I hope this helpes you!

which 18-55 are you referring to? the efm or the efs?

gary

... the efm.

How does DM log work. Does it log everything after you hit it until it reaches its max filesize? Does log everything from the time you boot?

you found the same thing in Malakai's logs a few pages ago. is there anything else that we could do to help illuminate whats goin on here?

I just tried ML with the 18-55 and I have no shutter problem.
If this helpes:
I still use the old download from Rootwang #1110 on side 45. Longer ago I installed the new EOS M firmware and then the Rootwang ML download as it was. Since then I did´nt change anything.

I have to go to work but I'm planning on EOSM full pack with autoexpo (need *other AE_VALUE maybe) and I wanted to do dual ISO but I'm stuck on logging the regs still. I thought someone posted a full release earlier in the thread.

Is there any chance that dual ISO works also in the normal video mode or does it only work for RAW Video? (if it works on the M one day)
Even if the RAW video thing is really great ... I guess 90% or more of filming will still be H264

could anyone please tip me off on how to compile ML for EOS M 2.0.2? I have the toolchain and everything and can compile it just fine for my 700D, but the EOSM target in the unified branch seems to be for the 1.0.6 firmware. How do I get an autoexec.bin for 2.0.2?

thanks a lot,
-d

Look here: page 45, post 1110

It seems that there are several versions of a release that works with intervalometer, but none is gathered in one place.
There is a link at page 45, post 1110 wich contains a link.. but this zip file is pasword protected.
I am in spesific after intervalometer funtion... as i am about to put my camera in a multicopter.

Just tested the download link again and for me the zip file is not pasword protected - all works fine ...