Forum Replies Created

Page 2 of 3
  • David Butterfield

    August 19, 2011 at 4:31 pm in reply to: Render Manager/Finder discrepancy

    Thanks Dave, a path is becoming clear. I still wonder why the manual warns against using Finder to delete render files, but clearly this is the only way around the mis-reporting in Render Manager of the number/size of files.

  • David Butterfield

    August 19, 2011 at 1:07 am in reply to: Render Manager/Finder discrepancy

    Thanks for your help, friends. Still not sure what to try here. Does the “Compress” action get rid of redundant files? The magic bullet here would be to get rid of everything not pertinent to my current saved project…they go back for months…very much appreciate the suggestions.

  • David Butterfield

    August 18, 2011 at 11:53 pm in reply to: Render Manager/Finder discrepancy

    Yes, I think they are. Except for some audio and constant frames in different folders.

  • David Butterfield

    January 27, 2011 at 5:06 pm in reply to: Capture problems/Audio synch etc.

    Thanks for your reply. Unfortunately the MX0@ Mini only supports two capture settings for an uprez: 720p @ 59.94 and 10801 @ 59.94. According to Matrox, both of these are overwhelming my Mac Book Pro and WD Studio Book (set at Raid 1) and therefore dropping frames. I can get a clip in at 480i then render and render and render in FCP as the project evolves. The point is I’d like to be able to do the uprez with the I/O box as its captured. So, wonder just what system and external HD one would need for that??? One would think this is quantifiable and the answer would point towards hardware that could do the job, but it’s beyond my depth to make that calculation. Is anyone able to uprez through a Matrox or Kona without a huge ‘puter and massive/expensive array? What lap top version, which external HD will do the trick?

  • David Butterfield

    September 19, 2010 at 5:04 am in reply to: FCP log and transfer crashes

    Happy ending. We got both a flat movie and a project out of FCP and into a working editing system–special thanks to Duck. Show back on schedule and many relieved campers here. For sure the best possible information available was here on The Cow. Regret time and money invested in Apple and will be looking at other systems, but am a Cow fan for life.

  • David Butterfield

    September 18, 2010 at 3:54 pm in reply to: FCP log and transfer crashes

    Thanks for taking the time to reply (glib though it may be). I did watch the tutorial from Richard Harrington (didn’t I see him at NAB a couple of years ago?) and we tried everything again. Sometimes systems and software don’t work and we are in that mode. We are using the animation codec to take the project to Avid and will continue work with that until we have time to address the Apple cluster F. Interesting/ironic though that you mention the Hokey Pokey as pre WW II footage of that dance is in the show. Thanks again and cheers.

  • David Butterfield

    August 3, 2010 at 3:00 pm in reply to: Historical project mixing formats

    Thanks Walter. If I knew there would be more demand for this kind of up-vert, I might go with a Kona 3, but 3 as in $3 grand might still be too pricey for this one project. Hmmmm. Going to go ahead with Compressor tests and also fish around for a facility that has a Terranex or K3s and see how much farming it out might be. (I’m in the mountain West and might want to be there so travel is a factor.) Very stoked about the way COW is helping me with this strategy. This is just a great site. Thanks again and good luck with the new BCM facility and docs.

  • David Butterfield

    August 2, 2010 at 11:45 pm in reply to: Historical project mixing formats

    Thanks John, appreciate the reply. I’ll do some tests with Compressor and see how that works out. New hardware may have to wait for now.

  • David Butterfield

    April 11, 2010 at 8:38 pm in reply to: Log and Transfer double dipping

    Thanks for your reply.

    I’ll remember to hit the Start Queue button only once. In retrying transfers I noticed I was not apt to do that but I’ll keep it in mind.

    I tried transferring a single clip, and then two clips, and both went through normally, just once. I find the double copies are happening when there are 20 to 50 clips on a card. I haven’t escalated a few clips at a time to see where this kicks in but it does seem to be in transfers with quite a few clips.

    I fussed a bit with Prefs and Permissions. The former seems pretty straight forward, the latter I may not completely understand as regards FCP as an application. I’m more used to Permissions being applied to files being shared or released.

    Tried transferring the whole card and again got doubles with FCP adding higher numbers if there was a numeral at the end of a clip and a numeral beginning with “1” if the clip name ended in text.

    EXAMPLE: Tracking With Carl 1 gets doubled as Tracking With Carl 2
    and Carl Slo Mo gets doubled with Carl Slo Mo1 Instead of two files transferred I get four.

    ?????

  • David Butterfield

    December 24, 2009 at 2:12 am in reply to: FCP 6.06 export HD to SD

    Hi Mark,

    Tried your settings (except for the source) and again came up with a pillared and pinched image. Tried putting the 720P material into a larger HD sequence (1280 x 1080) and then tried exporting that with Conversion, and still came up with a pillar/pinch. I remember being able to export any HD material on V 5.4.1 and get a letterbox with Conversion, but it’s not working on 6.0.6 with 720p material.

    Meanwhile, back on Compressor, I had my windows laid out too large and was missing that toggle in the upper right. Out of sight out of mind. I was using the slider and toggle on the left, top side. If you use the one on the right it does give you an accurate export preview. So, being careful with the toggles and slider, Preview does work as advertised.

    It looks like Compressor is going to be the key to this job.

    THANKS TO ALL!

Page 2 of 3

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