quick follow up, it was bad CF cards. not a problem with ML or the camera.
thanks, all!
thanks, all!
Etiquette, expectations, entitlement...
@autoexec_bin | #magiclantern | Discord | Reddit | Server issues
This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.
Show posts MenuQuote from: RenatoPhoto on October 25, 2013, 01:43:49 PM
I also have read that some card readers can damage your cards, I was asked this question by Lexar when I returned a bad card.
Quote from: bnvm on October 10, 2013, 05:43:34 PM
1.) Every other pixel is not currently possible FF since the data stream that gets sent is already every third and the ML dev's have not found any way to change that.
3.) Ok, the only thing that would get you even close is shooting in RAW and that always requires post processing work. ML cannot do anything to the size of H.264 at the moment. Just I case that wasn't clear.
Who knows what the future my bring, raw video was impossible a year ago.
Quote from: bnvm on October 07, 2013, 10:51:31 PM
Sorry but I don't think it is possible to record that size at 1920. For raw there are only 2 options FF which is a data stream 1920 pixels wide reading every 3rd pixel from the sensor or 3x crop which is 3584 pixels wide without any pixel skipping.
In FF mode you can have just about any crop factor, 1.0 or larger, you want but you crop out resolution, there is no way to maintain 1920 wide. In crop mode your minimum crop factor is 1.6 so you can only have larger crop factors from there but again you crop away resolution.
FF
Any aps-c size you want but you cannot have 1920 wide.
Quote from: 1% on October 07, 2013, 08:04:36 PM
There aren't? 50D and 7D and probably 5DII should.
Page created in 0.083 seconds with 13 queries.