Hector Silva
Forum Replies Created
-
[Shane Ross] “If you want to Raid them and have some protection, I suggest getting the CalDigit Raid card…it can RAID 5 those 3 drives.”
Although this is a very useful solution, it will not work with current Mac Pros. The CalDigit RAID Card only has the ability to talk to the motherboard of 2008 and earlier Mac Pros. In a 2009 model it can only talk to HDElements connected externally.
A 3 drive internal RAID 0 is the fastest, cheapest option, but David is right to recommend a firewire backup drive for your data. A three drive stripe means that you are three times more likely to lose your data.
Want speed and protection? Get an external RAID 5 option.
H
-
Hector Silva
September 4, 2009 at 4:39 pm in reply to: One of disk damage into RAID cannot capture???Not an option in my opinion. With a drive down in a RAID 5 it is only usable in a degraded state which means it’s incredibly slow since the RAID controller is building the missing info on the fly. In that state I don’t think you could trust it to capture without dropping frames.
-
Are you using any plug-ins with the software you mentioned?
The stock video card has only 256MB of VRAM, while the 8800 has twice that. I do know of some effects and transitions that do not want to run at full precision on a video card with only 256MB.
For Final Cut try going into your sequence settings and lower your precision to 8-bit in the Video Processing tab. That may help, but it will lower the quality a little.
-
The reason why it’s roughly the same speed of RT as ProRes is because it is ProRes.
Final Cut now knows how to play back the clips in the timeline, but any changes will be rendered out in ProRes since there is no way for Final Cut to write new AVC-I video, it’s just too intensive. So Apple’s claims of native AVC-Intra editing is kind of a half-truth. The footage is native, but transitions and other new elements are not.
-
It sounds like it’s too late to sway you, but maybe others will read this thread.
Go AJA Kona. Unless there is a very special feature that they do not have available (like the MacBook Pro connectivity the MXO2 has). It is true that you can work quite well with Decklinks, but the difference lies in how quickly you can recover when things stop working well.
AJA’s support is unparalleled and they are quite responsive with replacement units if it is necessary. When you are up against a deadline every day saved may mean the difference as to whether or not you get paid.
The other part that I like is that you don’t have to buy all the cables for a Kona card. Most of them are included in lengths that are usable. Buying up a whole whack of cables can make up the difference in price between AJA and BM quite quickly.
-
Get a DVI to HDMI cable. Go into display preferences and choose mirroring and the highest resolution that is common to both displays.
Done.
-
Hector Silva
August 25, 2009 at 2:29 pm in reply to: The effect cannot be rendered with current graphics cardIf switching to 8 bit rendering didn’t help solve your issue, probably the only other option is running it on a computer with a 512MB (minimum) graphics card.
iMacs are terribad for FCP work.
-
Hector Silva
August 24, 2009 at 9:06 pm in reply to: What is the best consumer camera to edit with in FCP that is under $1000?On a simple level, I still recommend the HV series of Canon cameras. I know most don’t find HDV to be that sexy, but it has two nice advantages: it can be cut natively without transcoding, and you have a tape backup of what you shot. I think the only negative is that capture is done at realtime rather than faster than realtime.
-
Excited, but slightly fearful. I’m really interested to see the benefits that Grand Central brings to render times and the speed of applications (in time). But, I’m worried about Quicktime X destroying programs for the next six months.
I mean, most have had problems when Quicktime is upgraded as a point release, let alone an entirely new build of this framework.
Any comments from those running Adobe, old Final Cut Studio, or Avid who were brave enough to try it on the beta? I’m sure Apple built the current FCS with this OS in mind, so there should be less potential problems.
-
Hector Silva
July 30, 2009 at 6:35 pm in reply to: Normal? Can’t Play ProRes HQ on MacbookPro 2.66 wo rendering[Wayne Carey] “This is because ProRes422 HQ is running at an average bit rate of 220 Mb/s and your drives are running at an average of 150 Mb/s.
This means your drives aren’t fast enough for ProRes422 HQ.”
Whoa Wayne, watch your ‘B’s! The HQ codec at 1080 runs at 220 Megabits per second (Mb), where his RAIDed drive has 154 MegaBytes (MB) of throughput. There are 8 bits in every byte, so 220Mb/s would equal 27.5MB/s. His storage is definitely fast enough to keep up with the throughput required (assuming everything is working properly), even if his array was 80% full he should still be able to get at least 60-70MB/s.
Try capturing some footage in the regular ProRes422 and see if your computer has the ability to play it back realtime. I would say your system should be able to play back a single layer no problem, maybe the HQ footage is just a bit too much.