Jason Myres
Forum Replies Created
-
The biggest difference is that the 5D has a full-frame, 35mm equivalent sensor, and the 60D has an APS-C, or cropped (read: smaller) sensor. This allows the 5D to have better low-light capabilities, and it will produce less noise at equivalent ISOs than the 60D. That being said, the 60D is no slouch and has the same video capabilities as the 7D, which is also very popular, for quite a bit less, and includes a very good tilt LCD that can be very helpful when shooting.
Beyond that, going with a Full Frame or APS-C sensor may change your lens selection a bit. Lots of lenses out there, but you’ll need to make sure the ones you intend to use are compatible with the camera you ultimately decide to go with. Due to the nature of your question, I’d imagine it would be good for you to start with the 60D, and progress from there. The 5DII is due for a refresh fairly soon anyway, so it may be good to wait if you decide that’s the one you want.
JM
-
I have Resolve 7.1 on my MacBook Pro running 10.6.8 and everything is working well…
2008 MacBook Pro 17
2.6GHz/4GB/ 500GB
Nvidia 8600M GT 512MB
CUDA 4.0.17
GPU 1.6.36.10JM
-
Chris, Definitely need to buy you a beer some day.
Great post.
JM
-
From Apple Sales News:
“Effective June 21, 2011, Final Cut Studio, Final Cut Express, and Final Cut Server have reached end of life. Resellers may return any unsold inventory to Apple. If resellers opt to return unsold inventory, it will not count against the reseller return cap. See standard policies and procedures regarding returns for more information.”
JM
-
[Dave Barnard] ”
I have a feeling that the problem is caused by the Apple Fibre Channel card.
Although it will operate at full speed in a 4 lane PCIe slot, the board is physically 8 lane.
8 lanes would exceed the total bandwidth available on the PCIe bus, even though the extra bandwidth is not needed.”You’re fine. Your slot assignments are perfect. The Apple/ LSI fibre card works in 4x and 8x, but operates at full bandwidth in 4x.
JM
-
Wait, Andrew….you’re the one with the little birdies? lol.
JM
-
You’re making it more complex than it needs to be, and using software RAID on a production volume, not only adds a point of failure, but makes it more difficult to reliably move the array to another machine.
Reformat the array as one RAID5 volume, with a hot spare if you can afford the loss of space. Without it if you can’t. Use a 64Kb stripe size for mixed video, images, and graphics, or 128Kb stripe for pure video.
Connect it to your HBA with one fibre cable, and you should get over 300 MB/s read and write. A 16-bay Infortrend chassis gets about 375MB/s read/write when configured the same way. Also, your test results will vary dramatically depending on what frame size you use in AJA Stystem Test, so test for the format you’ll actually be using if you want a realistic estimate of how the array will perform in actual use.
JM
-
If you feel like you’re on the cusp and will need to move up to shared storage in the next year or so, I’d also be looking into sharing a fibre array with something like SAN MP:
https://www.studionetworksolutions.com/products/product_detail.php?pi=8
JM
-
SAN MP with 8Gb fibre arrays will be the easiest, most affordable route to scale that large and handle uncompressed HD. Later on, if you add several more bays, or need file-level locking, all of your arrays can be re-purposed for use with Xsan, StorNext, or ActiveSAN.
JM
-
[akshar bhosale] “on which device it is getting written?”
Short answer: all of them.
Long Answer: I took a quick look at an IBRIX white paper, and it seems to be a lot like other shared disk file systems, where the “Segment Servers” are equivalent to the Metadata Controllers used in a StorNext or Xsan environment.
Assuming that’s correct, then your arrays (MSAs) have been gathered into storage pools that are striped together to form your SAN volume. When files are copied to the volume, the individual blocks of data that make up those files are written across all of the arrays at once.
There are ways to control this using affinities, or by creating separate volumes for different types of data, but you would have to look into how your SAN is configured to see if anything like that has been set up. If you need to remove or re-purpose some of your arrays, many SAN filesystems have data migration features that allow you to re-assign blocks to the arrays you want to keep, so you can de-commission the arrays you need to remove.
JM