1280x560 is maximum i could get on my 650D with UHS-I card. It seems that controller is limited to 30-40mb/s which is poor
but 1280x560 looks great, even upscaled !
but 1280x560 looks great, even upscaled !
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: haysuess on May 16, 2013, 09:15:40 PM
This is so awesome to play with!
I have a Mark II, and a Transcend 400x 32GB card. When I run the benchmarks, my write speed is around 37.5-50MB/s, only at 16384k buffer is it under 40, and with the rest it's usually closer to 50. Read speeds are around 65MB/s consistently.
The anomaly is at 128k buffer it's only 25.5MB/s write speed
I'm trying to record at 1280x720 at 24fps, and it says i only need 36.9MB/s to record, however, I only get a few seconds before it starts skipping bad and automatically stops.
Even at 1280 x 540, which says it only requires 27.6MB/s it starts skipping within 10 seconds.
I can record without skipping at 960 x 540, but I still get a lot of magenta blocking.
I tried with both the May 14, and May 16 nightly builds and the 5D Mark II record module and autoexec.bin that someone else posted.
Is there something I'm missing, or is this normal?
Quote from: Andy600 on May 14, 2013, 11:44:12 PM
Suddenly the 650d looks like a winner based on those card benchmarks (and there are even faster UHS-I cards out there). That will be the BMCC pocket killer... eventually
@Vitos1k - can you run the card benchmarks again with global draw OFF and post the results?
Quote from: Luiz Roberto dos Santos on May 14, 2013, 09:36:36 PM
Quick test with the 600D. I get files 1280x540, but with macroblocks magenta (from time to time), perhaps due to my card "super-slow".
Processing was nil in both sequence (H.264 and RAW).
Quote from: a1ex on August 20, 2012, 02:45:19 PM
?!
All 500D testers said it's not working; some of them got it to work when holding the AF button pressed, but not always.
Page created in 0.067 seconds with 13 queries.