Forum Replies Created

Page 8 of 23
  • Kim Rowley

    June 8, 2009 at 3:52 pm in reply to: MXF EXPORT

    I am familiar with this. Just wondered if there were other choices.

    Dual 2.7 GHz G5, 4GB RAM, ATI Radeon 9650, Xserve RAID, AJA IO, 2 20″ Cinema Display, FCP Studio 2 (6.02), OS X10.4.11

  • Kim Rowley

    February 2, 2009 at 4:07 pm in reply to: P2 and FCP Log and Transfer

    Great Paulo! Eureka 🙂 Now I got it. Thanks, that makes things easier on the eyes.
    All the best, kim

    Dual 2.7 GHz G5, 4GB RAM, ATI Radeon 9650, Xserve RAID, AJA IO, 2 20″ Cinema Display, FCP Studio 2 (6.02), OS X10.4.11

  • Kim Rowley

    February 2, 2009 at 6:49 am in reply to: P2 and FCP Log and Transfer

    In the Log and transfer mode unless I am missing somthing, I don’t think you can see your video on an external monitor.

    Dual 2.7 GHz G5, 4GB RAM, ATI Radeon 9650, Xserve RAID, AJA IO, 2 20″ Cinema Display, FCP Studio 2 (6.02), OS X10.4.11

  • Kim Rowley

    January 30, 2009 at 10:09 pm in reply to: P2 quicktime file names

    I DID notice one thing today in L&T that could at least make such a task a little easier. I discovered that if I name a clip for example “capture” and send it to FCP, then load the next clip, as soon as I hit the “c” key, the rest of the word comes up automatically. If I send that over to FCP without adding a number after “capture”, FCP adds it automatically, and continues to do so sequentially. So in a sense the OS and FCP at least give you a hand. The only thing to check is what name is assigned to the actual new quicktime file. I’m not at my mac so I can’t check. Hope this helps.

    Dual 2.7 GHz G5, 4GB RAM, ATI Radeon 9650, Xserve RAID, AJA IO, 2 20″ Cinema Display, FCP Studio 2 (6.02), OS X10.4.11

  • Kim Rowley

    January 30, 2009 at 9:58 pm in reply to: P2 and FCP Log and Transfer

    No problem Paulo. Actually I did try that but it really doesn’t make a huge difference. I was not referring to the thumbnails but rather the actual viewing window.

    Dual 2.7 GHz G5, 4GB RAM, ATI Radeon 9650, Xserve RAID, AJA IO, 2 20″ Cinema Display, FCP Studio 2 (6.02), OS X10.4.11

  • Kim Rowley

    January 30, 2009 at 4:57 pm in reply to: P2 and FCP Log and Transfer

    Thanks Noah. That’s what I was afraid of… I have too much material to ingest everything. I’ll write Apple and ask for a bigger window for Christmas.

    Dual 2.7 GHz G5, 4GB RAM, ATI Radeon 9650, Xserve RAID, AJA IO, 2 20″ Cinema Display, FCP Studio 2 (6.02), OS X10.4.11

  • Kim Rowley

    January 28, 2009 at 11:33 am in reply to: Log and transfer window size

    That is the case with log and capture but I tried and with Log and transfer and the canvas size has no affect on the L&T image window size.
    Good guess though.

    Dual 2.7 GHz G5, 4GB RAM, ATI Radeon 9650, Xserve RAID, AJA IO, 2 20″ Cinema Display, FCP Studio 2 (6.02), OS X10.4.11

  • Kim Rowley

    January 27, 2009 at 2:19 pm in reply to: third party logging software? anyone?

    Hi Edo,
    We have been using TepX forever and at the beginning of January purchased TepHD to run on a Macbook pro. We used it during a recent trip to Africa and had no problems. We have a custom template for logging and used it also to offload our P2 cards. What problems are you experiencing? Our only “gripe” so far has been the price… This is our first experience with the OSX version, but so far so good.
    Hope you get your logging problem sorted out. Dan Montgomery of Imagine has always been helpful to us.

    Cheers, Kim

    Dual 2.7 GHz G5, 4GB RAM, ATI Radeon 9650, Xserve RAID, AJA IO, 2 20″ Cinema Display, FCP Studio 2 (6.02), OS X10.4.11

  • Kim Rowley

    January 26, 2009 at 6:37 pm in reply to: Native MXF question

    Thanks Jeremy. The jump from Digibeta to P2 is a continuous learning experience.
    I was in Cameroun for almost 3 weeks. First in Douala and then in a small village called Fontem in the forest about a 6 hour drive from there. A fantastic experience.
    Our 3 HVX171’s stood up to the dust and heat and humidity perfectly – much better than we did 🙂 I opted for offloading with HDLog on a MacbookPro using Western Digital 2 TB drives set to RAID1. Miraculously everything performed well and it went very smoothly. I’m now trying to sort out the rest of the workflow since the material will be edited on 3 different workstations. As I said…a never ending learning experience 🙂

    I have to say that I’m beginning to think again about the QT re-wrap process and it may not be all that bad after all. Wouldn’t it give more peace of mind to just use HD log to select shots and export them as a QT file to use for editing (metadata included Imagine assures me). My MXF files are safe on a separate drive and I can edit without worry and just delete the QT’s upon job completion after laying off to tape (DigiBeta master). Just considerations after today’s pondering!

    Then comes the LTO back-up process. But… one step at a time!

    Dual 2.7 GHz G5, 4GB RAM, ATI Radeon 9650, Xserve RAID, AJA IO, 2 20″ Cinema Display, FCP Studio 2 (6.02), OS X10.4.11

  • Kim Rowley

    January 26, 2009 at 5:08 pm in reply to: sequence settings DVCPro50

    OK…I follow your thinking. I am in PAL land actually (Italy). So… I set up my sequence with the ProRes HQ PAL setting, the first time I bring a clip into the sequence FCP asks me the famous question if I want my sequence settings to match the video format. I of course answer “no” since I know what I am doing! 🙂 I do though get the green “need render” line in my timeline over each clip. Have I understood correctly?

    That would give me the highest quality output of my mterial?

    If so couldn’t I just leave the sequence settings at DVCPro50 during editing and then change my sequence settings to Prores at the END of the job, then render only once and Output to Digibeta?

    Thanks for time Rafael. I see you are in Laos. Incredible!

    Dual 2.7 GHz G5, 4GB RAM, ATI Radeon 9650, Xserve RAID, AJA IO, 2 20″ Cinema Display, FCP Studio 2 (6.02), OS X10.4.11

Page 8 of 23

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