Videomansf
Forum Replies Created
-
Render out from Motion, and not FCP. Also if you have a slow mac with a low quality graphics card you’ll not get great motion performance.
VM
HD and SD On-lines
FCP 5, OS 10.4.2
G5 dual 2.7, 8GB ram, x800xt
Kona 2, aja io full
Medea SCSI 320 5TB Raids -
Um… yeah…
If your going to monitor on a consumer HDTV connected to the mac Via a dvi cable, your color is going to be way off (at lease 50% off). Unless if you use a Pantone Spyder Pro on the HDTV and set the calibration to NTSC. I do not recommend this. And for storage, with HD you need speed much more than space but at 130MB/s for 720p your going to need a lot of space too. HDCAM is NOT like DVCPROHD. The mac can not decode the digital information of HDCAM. You must recapture at uncompressed or some other compression system. If your really thinking of doing HD on anything less than SCSI 320 or FC raids, you’ll have nightmares.
A much better solution is to dub everything to a deck format that you have in your possession, like DV (d25), with timecode. Edit the DV, and then go do an online on a purpose built system that has the drive speed and storage that you need.
This is about baseline for me:
https://www.macworld.com/2005/01/news/highdefmacpart2/index.phpVM
HD and SD On-lines
FCP 5, OS 10.4.2
G5 dual 2.7, 8GB ram, x800xt
Kona 2, aja io full
Medea SCSI 320 5TB Raids -
It’s a good idea to use a “media” drive for just that; video media. Text and photos and work files should be on the boot drive. You can put a back up of your FCP sequence files on the media drive as well. Also, you can move the Live Type and Sound track files to the media drive. They are located in the library -> application support. Also make sure to set your media drive as your capture scratch disk as well. Oh, and I would buy a Fire Wire drive of the capacity of your media drive as a backup to that one as well.
VM
-
Videomansf
August 9, 2005 at 6:06 pm in reply to: omtimizing an Xserve RAID for uncompressed HD questionThe main thing is wiring. Go FC from the dual port card to the xraid with two individual cables. Avoid FC patch and hubs. Also a fresh format and new soft raid is a good idea to avoid fragmentation. Each bank of 7 drives should be in a raid 5 and then stripe them. also make sure that your FC card is in the pci-x slot or 133mhz slot. The 133 slot will give you about 250MB/s so don’t go over that. No dual steams now. If your going to need to run faster than that, you’ll need another xraid, and FC dual card, and use the two 100Mhz slots. That’ll get you up to about 400MB/s. What HD card are you running? I have a kona 2, and do onlines all day long. Also 4GB of ram is about as little as you can get away with, as the system will need about 2GB, and FCP will take 2GB too.
Vm
-
If I am not mistaken, this deck can be set up to run in 232c as well. I would check the menu settings on the deck, and make sure that your set to 422. Or you might want to make a 232c sony control preset, and give that a try. Also, in trying to track down the problem, use capt now with tc to capture a segment, and then try a reconnect. If that works, then it is not a black burst generator problem. You are sending Black to the card, and deck and a 75 ohm terminator on the ref loop through?
VM
-
I have done this to transcoder all of my BetaSP to Dbeta to embed audio to SDI, but I used my old G4 500MHz laptop to control the io. I do not think that you’d have to remove the io’s drivers though. Also you could do this the easy way:
configure the io via the control panel how you would like it, say Svideo and analog 1-2 to SDI embedded. Then disconnect the firewire cable from the io. the io will stay set to the last settings until you power it off and on. Then capture using the io as a non controlled converter box. I have been doing this for about 18 months now, and have had no problems, long before the control panel app. The same works from FCP, just set up the io with the preset you need and then open log and captuer, and unplug the firewire from the io.
Presto, no need to run the control panel at the same time.
VM
-
How are you controlling the deck? Via RS422 or Firewire? I would recommend RS422, and if your BM dose not have it, you can use a USB to 9pin adapter. Also try just LTC or VLTC and not both (under device control settings). Lastly dose capture now work, and if so dose it move TC with the clip? Oh and have you configured the frame offset to the beck with a timecode window burn? And lastly, are your hard drives up to running at 60-72MB/s? I have always had problems with firewire drives and UC10bit/8bit.
VM
-
FCP5 can address up to 2GB of ram per application. IE get Motion 2, Compressor, and FCP5 rocking and you could be looking at 6GB of ram utilization. OS 10.4 can only address 512MB of real ram, and another 3GB of Virtual Ram, or HD Cache. If your running just FCP, look at 3GB as the best compromise. But, in your case, I fear a poor instal is more to blame than Ram problems. I recommend doing a clean install of 10.4 -> upgrade to 10.4.2 -> and then install FCP5 and upgrade to 5.02 via software update. I have a Dual 2.7 with 8GB ram and fast 10K boot drive with a 5.6TB xserve and Kona 2/io card box combo. I was crashing with the original shipping version of 10.4 and when I reinstalled, and upgraded, everything has been great. As I type this I am at 238 Hours uptime running an HD 720P online.
VM
-