Messages

Well, you can push your 5D above 1080 and then scale your way to 4K and surely achieve a better "4"K result than many consumer "4"K solutions, but that's not what you're after I suspect

Thanks Walter, had a feeling that I was missing something Amazon.co.uk sells the KB 64GB x1000 at 55GBP incl. shipping so that seems to be the best deal I think.
I have been rather inactive on the forum in 2015 and this thread leaves me wondering if the KB x1000 64 really still is the king of CF for MLraw? The 128GB x1066 are rather cheap but I seem to remember that they were less stable than the x1000?

Been using KB 64 1000x from one of the first batches since ML RAW came out.
Need some more cards now and noticed that Lexar 1066 64GB appears to be cheaper (~110$) than the cheapest 64GB x1000+ KB cards (~135$) (I am in Copenhagen and all the cheap KB cards are sent from outside EU meaning that they are subject to high import tax/VAT)
At 110$ vs 135$, have I missed a reason to not go with Lexar?

What kind of latency are you seeing with qslrdashboard + ipad + MR3040?

+1 from here as well
Canons implementation of wb controls has always been one of my main frustrations when it comes to DSLR video

Been using the Transcend reader for a while.
After half a year a pin got bend but I managed to carefully correct it. After switching to a rMBP from my trusty TP, the reader starting acting up and today, 2 months later it is completely dead, less than 2 years old. Been transferring less than a TB in its lifetime, kinda disappointing. Had issues with corrupt ML raw a few times and Corrupt RAW stills once shortly before it died, not sure if the reader is to blame. Been using it with Transcend, lexar and KB cards.
Looking for a replacemtn atm, is the pixelflash worth the extra cost compared to the transcend?
EDIT: Just realized that I had the transcend rader since the beginning of the ML raw revolution. Time flies I guess.
In that case it is less disappointing that it died I guess.

No sure if this thread is dead and being continued elsewhere.
I am wondering if ppl are still using the XQ version for ML workflows?
Also, It seems that the 2015 version of the CC apps exhibit the same problem as the 2014 version (getting error on render)
Did anyone ever find a solution for this or do you still have to install the pre-2014 version to encode XQ?

I find it really odd that this thread keeps devolving to ppl telling us that we actually don't need the requested feature at all
I can totally accept if the implementation is impossible/difficult/time-demanding and/or if the ppl with the actual knowledge to find a solution have no interest in spending their time on it.
However, I think it goes against the nature of a feature request (besides deffinately not stimulating development on the feature in question) to keep telling us that we either don't need it or that we can just use a different feature (which all seem to fall at least as short as the default canon options for me when shooting theatrical dance and movement where the light is subject to sudden and extreeme changes at any given time (spots, costumes, backdrops etc)
I know from my collegues and from personal experience that the implementation of EC in M mode as seen on 1Dx is really really usefull for such situations.

Controller SM2236AB is a bit outdated. (...) order one more up to date (SM2236AC or newer).
Just learned that different controller types for this card seems to be significant.

Any advice on how to identify controller versions based on card revisions or serial numbers?
I have been talking to 7 different sellers as well as using my inferior google skills to no avail

@ Walter
Cards are still crunching, my initial observation however is that with GD off in Playback mode Sequential write is around 107mb/s for the Komputerbay card and 80-81mb/s for the Lexar.
I guess that now I know why they where cheap (91$ per card)
Thanks alot for your analysis and swift help Walter.
I guess I am sending them back and in the future I will remember to pay attention to revisions and controller versions.
EDIT: results

[Crystal Disk Mark:]

@ Walter
Thing is, the KB card seems to work ok and I am not new to benching.
I have also tried the different variable I could think off (eg. cluster size, format type, file-system, bench apps)
As you can see below, the KB card eats the Lexr.
Crystal Disk Mark:
Lexar 64-1066
           Sequential Read :   144.711 MB/s
          Sequential Write :    84.624 MB/s
         Random Read 512KB :   135.211 MB/s
        Random Write 512KB :    39.826 MB/s
    Random Read 4KB (QD=1) :     8.275 MB/s [  2020.3 IOPS]
   Random Write 4KB (QD=1) :     1.545 MB/s [   377.1 IOPS]
   Random Read 4KB (QD=32) :    10.513 MB/s [  2566.8 IOPS]
  Random Write 4KB (QD=32) :     1.800 MB/s [   439.5 IOPS]
  Test : 1000 MB [E: 0.0% (0.0/59.6 GB)] (x5)
Lexar 64-1066 (second copy)
           Sequential Read :   145.494 MB/s
          Sequential Write :    85.570 MB/s
         Random Read 512KB :   137.307 MB/s
        Random Write 512KB :    31.296 MB/s
    Random Read 4KB (QD=1) :     8.373 MB/s [  2044.1 IOPS]
   Random Write 4KB (QD=1) :     1.574 MB/s [   384.3 IOPS]
   Random Read 4KB (QD=32) :    10.605 MB/s [  2589.0 IOPS]
  Random Write 4KB (QD=32) :     1.821 MB/s [   444.7 IOPS]
  Test : 1000 MB [E: 0.0% (0.0/59.6 GB)] (x5)
Komputerbay
           Sequential Read :   149.989 MB/s
          Sequential Write :   131.285 MB/s
         Random Read 512KB :   142.877 MB/s
        Random Write 512KB :    37.196 MB/s
    Random Read 4KB (QD=1) :     9.305 MB/s [  2271.8 IOPS]
   Random Write 4KB (QD=1) :     2.206 MB/s [   538.6 IOPS]
   Random Read 4KB (QD=32) :    11.672 MB/s [  2849.6 IOPS]
  Random Write 4KB (QD=32) :     2.502 MB/s [   610.8 IOPS]
  Test : 1000 MB [E: 0.0% (0.0/59.6 GB)] (x5)
AS SSD:
KomputerBay 64GB-1000x =          65mb/s;95mb/s;125mb/s,125mb/s,125mb/s,125mb/s;126mb/s
Lexar 64GB-1000x=                              80mb/s;82mb/s;81mb/s;81mb/s;81mb/s;81mb/s;81mb/s
Lexar 64GB-1000x(second copy)=      80mb/s;81mb/s;81mb/s;81mb/s;81mb/s;81mb/s;81mb/s



Initial thoughts: The KB card seems to benefit from "warming up" whereas the Lexar is more constant.
I find it interesting that the READ speed on the Lexar is is on par with the KB whereas the write speed is horrible. This reminds me of my Lexar 800x which similarly benches at 140mb/s read - 47mb/s write
[All cards tested with identical settings, eg. clustersize, filesystem, camera settings ]

@KHMihail

No, photo mode.
Movie, 24fps, GD OFF: 90W/120R.
Movie, 30fps, GD OFF: 85.5W/115R.
All on 1.2.3.

Could you share your settings?
---
I just got 2 of those Lexar 1066 64GB cards and they are both almost identically peaking at 63mb/s when running in-camera benchmark.
In Playback mode they get a bit above 80mb/s - similar to the results I get from them in "AS SSD" and Chrystalmark.
Seems that they are too fast to be fake but also too slow to be real - any thoughts
Actually, performance wise, it seems to be closer to my Lexar 32GB 800X than I'd like

Nice concept

I loose a job for the stripes and noise.

I didn't see any stripes in your 5D shots, do you have any advice in terms of lighting or other to avoid it?

Sorry to go off topic..

Seems that the best workflow for me is still to grade in ACR, render HQ 444 DNxHD proxies, edit in Pr, re-link footage to CDNG sequence and do a final grade in SG. Just so bloody hard to get the look I am after in SG after so many years of ACR
About the disk issue, its worth noting that many high-end laptops have an available mPci slot that can hold an additional SSD making for a total of 3 drives (when replacing the optical drive with a caddy)
In this way, one could run 2x 512gb SSD + a 1TB 7200 (possibly a hybrid-drive) to keep the cost a bit lower.

*holds breath...
This is an interesting development to say the least. Are the issues limited to ml raw or are there reports of other raw files causing similar issues?

I would still love to see a comparison between VisionLog and CineLog before pulling the trigger. Anyone did such a clip?
Also, whats the status on the Lut-bank?
Website still says:

(The LUT Bank is coming soon. Est. online mid-April).

Anyone actually getting improvements with h264.ini now?

with good footage you can also use http://slowmovideo.granjow.net/

Pixelbending like Kronos and Twixtor?
How does it compare in terms of quality and processing speed to the two?

Nice

I tried searching for that what I spoke of, but it'd be quite a few years ago that I saw it.
However in the process of searching for it I found this:
http://pickandplace.wordpress.com/2011/10/05/canon-ef-s-protocol-and-electronic-follow-focus/

Interesting

+1
Inspiring

That sounds like a very worthy effort Marsu!
Are you looking into the use of modifier keys as well? (like the canon option of changing ISO by holding down SET while turning the index-finger dial on the 5D)

:edit: Should note that I'm converting the raw files with RawMagic, which lets you choose your cam model.

Thanks for the tip! This means that I can go back to using the raw module for that extra bit of performance until the mlv catches up. (main benefit of mlv for me was the inclusion of the exif that allowed the use of camera profiles)

Film Convert have just added Canon 5Dmk3 ML Raw Profile in their latest update .

Good news! I am sure this will land them a good few new costumers

Sounds exciting Thanks for taking your time to enlighten the masses