Messages

Hi guys.

First of all I'm not sure if I have the same issue as the rest of you, but too seeing crazy pink corrupted frames.
I recorded this on the latest Nightly (magiclantern-Nightly.2015May03.7D203) on my Canon 7D on a Transcend 1000x 64GB.
For more details on settings check the images. The RAW files with corrupted frames are mostly in the beginning, and the later recordings the same shoot are all free from pink frames.
To recover the files I've tried the rawcover.py script, holding my thumbs, however the file came out as corrupted as the input.
I can see that most of the information seem to be in the image, although offsetted and pink, I can imagine it would be possible to restore frame-by-frame....
Any ideas what can be done to restore? And further to avoid the same issue from happning again (i didnt see any warning about dropped or corrupt frames while recording).

http://i.imgur.com/34PwBYB.jpg
http://i.imgur.com/MhgOS1w.jpg
http://i.imgur.com/CM3EeGy.jpg
http://i.imgur.com/BEs9CLr.jpg

Thankful for any input here!

Cheers,

Here we go, finally our first 4K RAW video test made with the Canon 5D Mark III.  Following our 5D Mark II previous tests, we have exported the dng sequence in 3840x 2160 jpeg files directly from Lightroom. No moire and aliasing. We will make a tutorial about all of this soon, stay tuned!

Actually this was quite annoying. And really quite confusing for most people. 

IMHO this has nothing to do with ML 4k RAW footage.
You should consider renaming the title of this thread as it is now receiving a lot of pointless attention.
And, do you really think you are the first person to upscale 2k footage? Like the FIRST EVER attempt, really? Pretty naive.

How about this topic: "Another attempt at upscaling 2K RAW Canon 5D Mark III footage in ACR" 

Thanks.

hello, I'm seriously going in the 7D direction (my indecision is between buying 7D or 600D) but I wish to ask you first one last question please if it's possible. it's about moire and aliasing during RAW shooting on 7D (without cropping) are aliasing and moire the same that we can see with h.264 or are them worst? more ugly?

for aliasing I mean those two effects:




and is that true that shooting with 5x zoom eliminate aliasing and moire for 7D RAW?

do you believe that future implementation of the firmware could further improve the situation?

thanks.

p.s. how many gb heavy is 10 minutes videos in raw?

Moire is an effect of the sensor, compression doesnt change that. You can decide which is uglier, RAW moire or moire with h.264 compression.
There are optical filters that are placed in the camera house to solve this, they cost a few hundred bucks. Moire will not go away with firmware updates.

Btw, most of your other questions are already on the forum, no need to ask them here.

Can you tell in which direction you should focus, from focus peaking data? How? (math please, not speculation)

There are of course no pure analytical ways to know which direction to focus, since the "blur kernel' for a given pixel is the same for both directions.
However, it would make sense to use linear quadratic estimation (a kalman filter) , or a more simple feedback system.
If this system would be stable or not in the end depends on many variables like physical constraints such as min/max focus step size, focusing speed, and much more, but since the potential payoff is great it might be worth a shot. This system would only work for tracking focus of a subject that is not changing too much frame to frame, but a walking person etc could perhaps work.
What do you guys think?

Thanks for reply.

What are the limitations of controlling the AF motor from ML?
Is the Bracket focus function based on the same limitations?

Since focus peaking works and bracketing works, seem like we could have a very basic (although slow) continuous AF by just using this?

Ok so taking out the lithium battery fixed it - not sure what this has to do with the shutter , but in case you run into the same thing that was the solution. Will pray i dont need to pay for a new shutter anytime soon. Living in Japan would probably make it convenient though.

It ran out of memory for some reason.

I still have to check some stuff out, its only been 48hrs, lol. Did it work on other modules?

Play fixes it, I even recorded with the 10x blacked out like that. I think flipping fast between the display filter and not might be a problem with this sync method, I need to add the warning too that you'll come back to flickery magic zoom after using it.

Was going to check it now, unfortunately i got a Canon 7D error code 30 "shooting is not possible due to an error". Probably it's not MLs fault , just very coincidental as i havnt seen it before i started using ML. Unless ML is using the shutter in some way of course - anyone knows?

Let's just put some good comments in the help section for this feature. And ignore people who cant read that.
Even if its not applicable to all type of scenes it would still be a MAJOR help for a lot of people.

I see, press play when that happens.

1%, BTW, the dolly mode (let you dolly with arrows) in RAW is very interesting. unfortunately it doesnt work in crop mode. I think right now its intended only for lower resolution , but would be awesome if it could be used in crop (as in crop even full HD is just 1/3rd horizontally and vertically so lets of space for some dolly action!). What do you think?

I should clarify the zoom issue I'm having. In the MLV raw module when the preview is set to Canon, it will freeze when cycled to 5X and then back to 1X. It doesn't seem to freeze when the preview mode is set to Hacked.

I had the same issue that it would freeze, most of the time i had to restart the camera, but to come around this for now, just disabled the 10x zoom mode so it only "cycles" between 1x and 5x. Try it.

Alex and 100%,

This is my first post, though im hoping to get more involved from now.

I have a lot of programming on embedded devices experience behind me, image processing and analysis and porting to various products including cell phones and cameras (worked R&D on stuff like image stabilization, face recognition etc). Although i know little about the 7d architecture as of now im learning quickly and since im a 7d owner since 4 years I'm like most other very interested in a continuous focus feature. Since I know that ML dev team have tried and now consider this impossible, more so I dont want to labelled a troll from my first post, i will try to ask more out of curiosity rather than a pure "feature request" approach. Could you try to be more precise in what was causing you to give up implementing this, the way I picture this would work would be to ignore the physical auto focus feature and go more for an algorithm that detects if an area is in focus (this is possible) and then tries to maintain this area being in focus by using the already existing ML follow focus feature. I understand this part is a bit slow, physically, so there will be limitations to all this and definitely no close ups of course, but the type of shots when you follow focus on someone walking in a distance could perhaps work. If you could let me know what made you quit the development, and why my approach would be unfeasible then that would be awesome.

Again, thank you very much for making ML possible. I had faith in you when everyone said 7D raw is impossible because of the unique architecture and decided to wait half a year before putting it on ebay. That paid off dearly to say the least.

Cheers,