Messages

Especially if you can't bother reading the manual, i'd say.

[recent]

please use a recent version of magic lantern.
you are using an outdated custom build.

There is none in the nightly builds for the 6D anymore, as you might know.

What camera?

Still no luck.
I get FFT graphs but apparently no audio is recorded. I am playing MLV files on the viewer with everything on low so it's fast.
I also got a crash, i am trying to reproduce it.

ASSERT: FALSE
at ./ASIF/ASIF.c:444, task beep_task
lv:1 mode:3


Magic Lantern version : Tragic.2013Nov09.6D113
Mercurial changeset   : a315c155c985 (unified) tip
Built on 2013-11-09 17:19:15 UTC by User@PC.
Free Memory  : 302K + 1694K

Also i am getting "audio failed to stop state 4" in the middle of a recording sometimes.

Oh, that's what i am missing.
I thought it was in the zip file but indeed it isn't.
Am i missing something again?

Has anybody worked out how to get 255M of buffer instead of 155 while recording?
Seems like it's similar to 5DIII where you can allocate more memory with LV off.

I just tried on my 6D and i can see the meters but apparently i can't hear any audio recorded.
Am i doing it wrong?
I am viewing the MLV file in MLV viewer but can't hear anything.
Suggestions?

what is the current rez and fps for shooting raw, "continuous" on the 6d using ML? Can it do 1920x1080 30fps? 24 fps? If not, then what rez is the highest that comes close to those fps?

1536*614 at 24 fps is continuous.
6D is limited to around 40MB/s by its controller and you need a decent card to use all of that.
I use i Sandisk 45MB/s, 16GB capacity.

And i am pretty sure many users got the point but as many can't do anything about it either.
It is up to you all to find a "compromise" and try to work in the same direction.
That is what is missing, i am pretty sure you don't lack the user base, especially the professional one, to get things tested quite quickly.

Well, you have to admit sometimes it is hard to find the correct version to test or the exact thread in which to find information.
Yes, i am using TL right now but that's because i am not using my 6D much and TL has a few more things on it than the rest.
I am not saying that you should announce every 6D nightly as if it was breaking news but i guess i understand why some people come on the forum and are confused about what to install and who's responsible for its maintenance.

The thing is, A1ex, users like me can just test features and give you feedbacks, contribute with donations and not much more. I am too uneducated to start coding now and when i tried it was always because you explained me what to do (and it was never something complicated, just basic things) .
I have been a lurker for months now, i moved country and i am having a hard time even taking a couple of decent pictures. Still, i like the project and i have been a supporter of it since the first 50D port started to take shape.
So, again, as i said and as you know, you developers can agree on what things to do and how to do them but what is exactly that you expect from users?
Most of the users haven't understood the principle behind ML and they will hardly do in the future.
Myself and others are surely willing to hear any suggestion that you can give us, provided that is something that we can actually do.

Just remember that a stable and decent port requires ONE developer with that camera in their hands so they can try whatever is needed to improve the port.
The first thing that needs to be done, in my opinion, is a general agreement between the developers so they all go in the same direction as far as development and objectives.
I am pretty happy with my 6D and its ML right now altough i would love to see it a bit more stable and improved.
Like many, i do not see the point in keeping some older branches active as i would rather buy a "new" camera rather than a very old one right now (50D, 500D, 550D, 40D, 5D) .
People can't expect older cameras to have all the gizmos and stuff that newer cameras have (Canon is fast in not supporting "old" products anymore) .
Again, it seems that ML was going well in one direction and the user base and developers were in a good relation whereas now my feeling is that somebody is quite pissed, some are too demanding, some are lazy and bla bla bla.
Without pointing fingers, i would love the whole project to revive once more and pleasing us for the years to come.

Is this a case of me confusing megabit with megabyte?

It is.

I was under the impression that Canon actually utilized this small amount of extra space to move glass close to the sensor (allowing a slight optimization of the optical design). Looking at my 10-22 this seems to be the case. If you are zoomed all the way out, the glass sticks out as far as the baffle. It is not just to prevent mounting on FF.  I guess none of the 3rd party manufacturers take advantage of this space in their optical designs.

Yes, hence why i am saying it's only the EF-S lens series that is purposely made for APS-C cameras.
Indeed, people have removed that baffle at the back of the lens and lenses like the 10-22 can only be used up to 16mm. Anything past that will touch the mirror when shooting stills.
So, finally, you can actually use third party lenses that are designed for APS-C but you have to deal with less coverage of course.
Not worth for me (i only buy FF glass anyway) but someone might want to experiment a bit.

The Sigma is not an EF-S lens.
Only the Canon lenses touch the mirror because they have a baffle that purposely put there to prevent their mounting on FF cameras,
People then remove it (as with the 10-22) and use it on APS-H or FF anyway.
So yes, you should be able to mount the 50-150 to the 5DIII, then crop in post.
Easy.

ML does not like you

Because there is 8 bits in a byte, not four.

Come on people, i understand being on a budget but you are talking about a camera that is 10 years old.
I am not suggesting you to buy 5DIIIs or 6Ds but try and give yourself a hand first.

It doesn't matter.

I don't think you realize that this doesn't really make sense. Yes you don't want to have multiple threads on the same thing i completely understand that and don't think that would happen. I challenge you to goggle the same question and find the answer quickly. It won't happen because of the way goggle indexes pages. a lot of people want the highlighted answer because they don't have the time to read through 20 pages to find a answer that is two sentences. Your response is also a little insulting because the same thing happens on the internal search.

So why should he provide you with a search that you could easily do yourself?
If you think that scrolling through 20 pages to find your answer is too much then you should steer off ML and similar.
If you can't be bothered why should somebody else do the job on your behalf?
Don't be surprised if some threads get no replies, if the answers are already here you should be able to find them yourself.

I got the Samyang on my 6D and it's a blade.
It's sharp from 2.8 and mantains impressive quality throughout the corners even on FF.
I would have no hesitation, just remember that the Samyang has no chip for Canon, i guess, so aperture can't be read by the camera.

Huh?

Are you from Melbourne?
Nice corner of the city, i should do something there too.

There are triggers on ebay.
No real need to DIY anything.

For raw? You can record H264 with embedded audio, just don't turn on stuff like FPS override/flush rate

I am using the nightly builds and i am missing the BR controls and all the stuff.
Why?