Trip Gould
Forum Replies Created
-
In that case, am I shooting myself in the foot by investing in smaller SATA drives like the G-SATA instead of just ponying up for one of the GSPEEDes arrays? Twice the price, so tough to swallow, but a bit more future-proof and I can always expand the capacity by swapping out drives in the future. Still, I’ve always been of the philosophy that you get what you need for a given project, nothing less and nothing more (or maybe a little bit more), and for this project, I’m doing SD only and 1TB is more than enough storage for what I need and the speed of the G-SATA is more than enough for the job. But, again, I don’t want to shoot myself in the foot, or pay more in the end by investing incrementally in inferior technology. Does that make sense? It’s late…so I’m not entirely sure if it does. At any rate, thanks to all who chimed in.
Trip Gould
Editor – Composer – Professor -
Trip Gould
November 4, 2007 at 6:00 am in reply to: Going back and forth from office to home…need advice.Thanks for the tips, I will be sure to put them to good use.
-
I will be working in MXF, so it sounds like it should be a non-issue, then. You are saying, though, that even if I go with two 500GB drives striped together, I should partition them as four 250GB partitions? Is this correct even if I’m working with MXF?
-
Trip Gould
November 3, 2007 at 5:43 pm in reply to: Going back and forth from office to home…need advice.But what would be the best way to consolidate all of the media I need to be able to transfer it onto that FW drive? I work on a series that is shared by other editors, along with quite a lot of footage that is shared, so bits and pieces of the media are in so many different places on the Unity. I figured exporting from the project itself to brand new reference clips would help ease the workload, even though it requires the extra step of exporting and waiting for that process to complete. Is there an effective way to consolidate all of the media that I am using in a project (not just what’s in the sequence, but all of my general B-roll bins and stock footage)?
Thanks.
-
It was my understanding that, to get the best performance out of the FW800, I would need to buy an additional FW800 bus card, as I will inevitably have other FW800 devices hooked up to my computer at one time or another and don’t want them to have to share a data stream with the media storage. Is this not correct? If it is, wouldn’t that basically be the same as having to buy a PCIe adapter?
-
I do understand the point about more drives being faster, which would definitely point me in the direction of two or more 500GB drives striped together. But how about the difference between the G-RAID2 and G-SATA? They seem to be almost identical performance-wise, with the only real difference being FW800 vs. PCIe SATA. Is there something I’m not realizing?
Thanks for responding, by the way.
-
I would need the complete Automatic Duck FCP bundle, though, to be able to import and export the OMFs…correct?
-
Would another option be to use Sebsky Tools to export from the Avid MC at the office and just work in FCP at home? All the true media would remain housed on the Avid Unity at the office and I would use Automatic Duck to export OMFIs from FCP that I would then bring back into to the Avid for finishing work. I would, of course, save all of the graphics heavy work for when I am actually at the office and do it directly on the MC. A viable option?
-
What would be the best way of dealing with the Unity mediafile structure? What exactly should I be watching out for? Thanks.
-
Speaking of compressor, and other people have mentioned this on these forums but I’m not sure why it is so, when I use compressor with the exact same settings I use with QT conversion, the compressor created movie doesn’t look as nice as the QT converted one. Is there a reason behind this? Also, I have gotten great results exporting the FCP movie, opening it up in QT outside of FCP, and then doing the exporting and conversion from that. It allows me to continue cutting while a batch of QTs export, and it looks better and is even a little smaller than what I get when I try to use Compressor. But, again, if I really knew how to use Compressor, I’m sure I could get much better results that way.