Forum Replies Created

Page 3 of 3
  • Steven Nichols

    September 8, 2010 at 3:35 pm in reply to: New Mac Pro advice

    I have another question regarding the card. Do you think I should get a better card than the ATI for After Effects, and if yes what would you pick ? Thanks again.

  • Steven Nichols

    August 12, 2010 at 7:18 pm in reply to: New Mac Pro advice

    Do you mean if you have like 4 GB of RAM on a 4-core machine, that means AE only has 1 GB/core during rendering ? Does that also affects RAM preview ?

  • Steven Nichols

    August 12, 2010 at 5:00 pm in reply to: New Mac Pro advice

    I think my workflow is pretty decent right now… but I can always use a little speed boost Jerry 😉
    I remember 15 years ago when doing promos for a network in SD, I would always plan a complex After Effects rendering on Friday night so I could get it on Monday morning. And now I have a real-time HD editing workstation… Not that I am complaining but you always find yourself pushing the envelope, especially when doing motion graphics.
    Having that said it’s always amazing the gap between Apple’s software and hardware. They are selling 12-core processors but it would be great if FCP could actually benefit from that. So I think I’ll wait for the 1rst non-Apple benchmarks.

  • Steven Nichols

    August 12, 2010 at 3:55 pm in reply to: New Mac Pro advice

    My typical workflow is with XDCAM EX footage, but I always render the final sequence chancing the codec to ProRes before exporting. All of my After Effects work is done with ProRes too.
    I currently have a 2007 4-core @ 3 Ghz (2xIntel Core Duo ) and I am wondering which configuration might give me the best speed improvement. For instance I am not sure with FCP if the 8-core (2.4 GHz) will perform better than my current 4-core (4 GHz).

  • Steven Nichols

    May 12, 2008 at 12:53 pm in reply to: RAID: SATA vs Fiberchannel

    Sure I don’t need 600 MB/s but I think RAID 5 protection is better than RAID 0-which is none ! I switched to XDCAM EX last year so even though the workflow is great, I bear in mind that one day some drive will fail me, and that I’ll have to explain that to a client.
    Besides, when I scrub in the timeline it’s not as reactive as I would like. And last but not least, my internal RAID 0 has “only” 1 TB capacity, and the more you have the more you need 🙂

  • Steven Nichols

    May 12, 2008 at 8:30 am in reply to: RAID: SATA vs Fiberchannel

    I already stripped 2 drives (RAID 0) in my Mac Pro, but the datarate I get is around 110 MB/s. I heard good things about Dulce’s Pro DQ since it can reach 500-600 MB/s and I was wondering how well it worked with FCP/AJA.

  • Steven Nichols

    May 11, 2008 at 8:29 pm in reply to: RAID: SATA vs Fiberchannel

    I shoot XDCAM EX and edit in ProRes.

  • Steven Nichols

    January 15, 2008 at 5:43 pm in reply to: Rendering with XDCAM EX codec

    Thanks Dave, but I think you’re answering 2 questions in one 🙂

    Regarding the issue I am having, I don’t think it’s related to the long-GOP aspect of the XDCAM EX codec. I have tried to render to QuickTime files (codec XDCAM EX) in other apps (Motion…) and it plays just fine in FCP. Besides as I said, the file rendered in AE plays just fine in QT player. I checked the specs of the rendered file and compared it with an original shot from the EX1 and I can’t see any difference so far. To answer your question, I am on a Mac 4x3GHz with 5GB or RAM and a Kona LHe card, under Mac OS 10.5.1, but I don’t think this is hardware related since I am having the same problem on my Mac Book pro.

    Now I agree that the XDCAM EX may not be ideal for post. But once you know how fast a transfer is using Sony’s XDCAM codec (about x7) it’s hard to get back to real-time ! I know I could use the SDI output of the camera, but I don’t think Apple’s ProRes422 works really well in post too, and I don’t want to go uncompressed since this means investing in an expensive RAID. So what workflow would you suggest ? Thanks for your input.

Page 3 of 3

We use anonymous cookies to give you the best experience we can.
Our Privacy policy | GDPR Policy