Messages

mothaibaphoto, you got me. there probably isnt one. but what is your point? that you wont be able to use the camera to its full potential once it is released? thats not news you know...

haha, thank you LRF

no, your opinion is not disappointing by any means.

the beta will cost 2300 for backers. thats half the retail price. you then need an external recorder and viewfinder or monitor and batteries. that means you can get a cheap (or expensive) atomos product or you can use a laptop with a hdmi or sdi to usb external interface. those sony batteries are cheap. also for sound you need an xlr (or not) mic preamp. all of the above according to your needs. all of the above are not that expensive and many people, including dslr shooters already have some of them or all of them.
do you want links for these solutions to check their prices?

i think the total sum of the above are a fair price to pay for a camera that we will be able to hack like never before, like no hacker or developer or engineer could ever imagine on proprietary products. thats what made the magic lantern developers to support this project.
and we can follow them to the core of image acquisition.

the picture quality we can see now is only a fraction of the quality the beta is set to achieve.
and why should the beta camera overheat?
these issues you address are actually a matter of the amount of trust you can show to the developing team.
and if you dont feel like trusting them thats of course totally understandable.

but trust is a complicated issue.

you trust the manufacturers and the engineers and the developers of airplanes and cars and operating systems and software and mobile phones and mobile apps and laptops and computers and tablets and many many more to do what has to be done so that their creation works for you and works safely.

why dont you trust these apertus (and ML) people as much? because the work under a different business model?

maybe they are going to add a super35 3rd batch.

the media refuse to mention the campaign and the beta in general. they seem to be more interested in paid advertisement.

a1ex, maybe insert one of these images on top of the news text in the ml homepage?
https://images.indiegogo.com/file_attachments/845780/files/20140909142617-features-blueprint.gif?1410297977
https://images.indiegogo.com/file_attachments/845540/files/20140909123250-image1.jpg?1410291170

ok a1ex i will, but only if you answer in detail to this:

can i pull out the 550d sensor and install a cmosis or a red sensor inside my camera?

is there a possibility mjpeg can store all 14bit data so we may get something like compressed raw?

yes i tried that.
i wanted to shoot 640*534 with a 2x anamorphic so i can get 1280*534. i did that with a lot wider lens than i normally use and the results are ok but it is like having a quite smaller sensor so i dont get nice dof.
anyway. i think i have to forget about raw after all

is it possible, for low end cameras like 550d, to skip lines and rows or something like that, so as to record the whole FOV in the small raw resolution these cameras can record?

i guess what im trying to ask is, can we record full sensor raw? (no matter what resolution)
5d3 does that and with resolution close to full hd, right?

here is what i havent figured out.
does raw recording work the same way foe every canon eos camera?
you set the resolution and you get a crop of a line skipped  frame?

all i can do with my 550d is record small resolutions cropped but some people here are comparing  h264 1080p full sensor videos with upscaled sub1080p resolution0s. but the fov is the same. even with 550d.
how do they do that?

ok so is there any way that raw_rec records the whole lv (even in small resolutions) or it only works in "crop mode"?

anyone tried the lv_rec module? what does that do?

i am very pleased by the results of 4:3 640*480 raw when shooting with a 2x anamorphic lens
stretching horizontally and getting 1280*480

http://postimg.org/image/7o1xbkj1z/
although its out of focus or motion blured

for freeing more memory, 1% told me this:

http://www.magiclantern.fm/forum/index.php?topic=5634.msg40011#msg40011

but just reading it makes me dizzy.

mk11174 can i try your bin too? i dont know what feature to disable

you just dont like me. admit it

are you talking about the recorded hdr video?
i am talking about the camera on screen preview.

maybe its time for me to remind you to do that. add a parameter that controls the frequency of the switch between under/over exposed areas in fast luma algorythm.

also the switch between the two exposures in hdr video will be controlled by the same timer, right?

anyway

if making it controllable is impossible for whatever reason, please just make it faster.
thanks

sorry. i am not sure i understand what you are saying.

maybe we could set the frequency of the switch between underexposure and overexposure of the fast luma algorithm?

is this possible or is this frequency fixed?