Sean Oneil
Forum Replies Created
-
[Christopher S. Johnson] “The AJA and Blackmagic SD and HD Uncompressed codecs are transferable between systems, right? They are both Apple UC, right”
There are Blackmagic and Kona legacy codecs from before Apple had UC natively. But you’re right. Nowadays in Final Cut, both of them just use the Apple UC codecs.
The other guy doesn’t need to load any Blackmagic software unless it was captured w/ the BM codec – which most likely it was not.
The only exception is 4:4:4 RGB. I believe AJA and BM still have to use their own codecs for that.
Sean
-
Multilane SATA just crams four SATA links down a single cable. The connector used for Infiniband happens to have the same amount of pins as four SATA cables do. So that is why SATA card makers are “stealing” Infiniband connectors and cables. An Infiniband cable can be used as a multilane SATA cable, since they’re both just point-to-point copper connections. But it’s still just four SATA linkl, not an Infiniband link.
Actual Infiniband is different. It’s a completely different protocol that has nothing to do with SATA or SAS. Infiniband has it’s own controller cards and switches. It’s more like ethernet, in the sense that it’s designed to network computers together. Not to connect computers directly to hard drives like SATA.
Wikipedia:
https://en.wikipedia.org/wiki/InfinibandSean
-
[JeremyG] “The Sonnet drives are connected through infiniband at the back of the drive itself, then they connect to SAS at the ATTO card.”
That’s actually just an Infiniband connector, commonly used for multilane SATA. Actual Infiniband is different.
-
Remove attributes.
Sean
-
[Jeff Bernstein] “Someone mentioned that Fibre Channel was the only fiber-based solution out there. O’ contrar monfrar! Check out Infiniband. It’s very fast, 20Gbit, for starters, and components are half the cost of Fibre Channel. The current missing ingredient is Infiniband storage. Though, I think CalDigit’s new stuff is Infiniband, yet they don’t mention it by name.”
I have checked out Infiniband 🙂
I would LOVE to have an Infiniband SAN. You can find DUAL 10gb adapters on ebay for a few hundred bucks. But an IB SAN is not possible, at least not with Mac clients.
There is not a single Mac driver for an Infiniband HBA. Small Tree made one to show off some cluster thing Apple did. One of those supercomputer university projects. But they don’t sell the driver, it only works with a revision of a certain card, and it only works on PowerPC Macs. Not Intel.
Also, IB requires special software in addition to a driver. You need something called a subnet manager (whatever that means). Without it, you have to use an IB switch. And those are very, very, very expensive.
But as far as available storage, there are options. Open-E iSCSI target software support a few IB cards. You’d have to build it yourself though.
-
I think Fiber Channel is absolutely dying. But it’s been a very slow death. If you already have it, I think you’ll be using it for a long time.
Not so sure comparing fiber to SATA/SAS is relavent. Comparing local disk solutions to SAN solutions is apples and oranges.
Back to fiber dying. It’s pretty obvious that everything is going toward IP-SAN. And iSCSI is clearly the most used now. The problem w/ iSCSI that most people don’t realize is what an incredible hog it can be on your CPU. Some 10gbe ethernet adapters have what’s called TCP Offload Engines which free your CPU from the tasks (none available w/ Mac drivers yet unfortunately). But right now these adapers cost a lot more than FC adapters.
I’m using an iSCSI SAN right now with 1gb adapters. I have two different ones. Both with their own problems. But when (and if) everything works right, I have 2gb for each client using dual gb connection. Not too shabby.
I know people using regular file sharing or a NAS server that supports Apple File Protocol (AFP). They use jumbo frames over gigabit ethernet and have no trouble working with anything that isn’t Uncompressed. With ProRes, this becomres even more attractive. On paper this is supposed to be a bad idea. The block-level access that iSCSI and Fiber provide are supposed to be all but necessary for this kind of work. But I’m not so sure anymore. Gigabit filesharing can be so fast it may not even matter. And a huge advantage is you don’t need an expensive cluster sharing program like Xsan/Metasan/SanMP.
-
[Peter Wiggins] “Remember, iscsi is built into leopard so expect to be able to build cheap shared storage at GigE speeds soon.”
That may or may not be true.
In one of the older developer builds, the Disk Utility showed “Connect to iSCSI Disk” in the file menu. Since that build, it hasn’t been there AFAIK. It may end up being part of it. It may not. Or, maybe it will only be in OSX Leopard Server.
Apple also had ZFS filesystem in one of the Leopard builds, and that’s dissapeared as well.
SNS’s iSCSI initiator is now free, but it doesn’t always play nice with non-SNS targets.
-
Forget the audio place. Just fix it yourself. It will take 2 seconds to do.
Your video is 24.00. Your audio was output for 23.98/29.97. SLOW THE AUDIO DOWN to 99.9%. Or speed it up to 100.1% (I can clearly think as to which direction you go). Point is, the speed must be altered by .1% in order to match. That’s it. You said earlier you tried this and it worked fine. So what’s the problem?
This is not some workaround hack with imprecise results. It is a perfectly legitimate method with a perfectly good technical explanation as to why it works this way.
Audio doesn’t have frame rates. It has a sample rate, usually 48000 samples per second. You audio engineer sent you a 48khz audio. Quicktime is assuming that it should play this back at video speedin order to sync up with video that has a framerate of either 29.97 or 23.98. But your video is .1% slower (or faster) because it’s 24.00.
Just change the audio speed settings in Final Cut, like you successfully did before.
I don’t know any other way to explain this. Sorry for the tone, but I feel I could not have explained any more clearly. If you don’t trust our advice, then I suggest reading the Cinema Tools manual.
Sean
-
I don’t know much about PAL. But in NTSC-land, The Kona’s SDI can output 23.98psf (which is a 48i signal) or, the Kona can output 29.97 by adding 3:2 pulldown in real-time.
Sean
-
That will get you no [Tippytink] “I think I need to call Apple.”
If they’re any help at all, they’ll tell you exactly what we just did.
Look at your source video in Quicktime and hit Apple-I. What framerate does it say?
Sean