Stutter, jitter, whatever.

May 23, 2012 10:41 AM

• 

  Currently Being Moderated

  15. Jim Simon,

  

  May 23, 2012 5:02 PM   in reply to abekutter

  Report

  The clip format per FCP is:

   

  Take FCP entirely out of the loop.  Do not start it at all for any of this.  Do not use any media that has ever been touched by FCP.  Use Premiere Pro only.

    Submit

  |

  Mark as:
• 

  Currently Being Moderated

  16. Jim Simon,

  

  May 23, 2012 5:04 PM   in reply to abekutter

  Report

  The timeline, getting properties off the project window:

   

  1920 x 1080

  00;00;30;00, 29.97 fps

  48000 Hz - Mono

   

  That part confuses me.

    Submit

  |

  Mark as:
• 

  Currently Being Moderated

  17. abekutter,

  

  May 24, 2012 6:17 AM   in reply to Jim Simon

  Report

  yes, absolutely, keeping FCP and PP media and workflows completely segregated.

  Though at one point I did experiment with exporting my entire FCP project into PP and...

  surprisingly painless! Still shittered, so I trashed it.

   

  Jim, RE your #16, you can get settings off the timeline itself, or you can get them off the timeline icon in the project window. #16 is the latter. Sorry. New to Adobe, very unclear on jargon.

    Submit

  |

  Mark as:
• 

  Currently Being Moderated

  18. Jim Simon,

  

  May 24, 2012 8:38 AM   in reply to abekutter

  Report

  OK.

   

  Your sequence and your media are different.  That suggests you did not perform step 4 from post 5.  Back up and do it that way.

    Submit

  |

  Mark as:
• 

  Currently Being Moderated

  19. abekutter,

  

  May 24, 2012 2:56 PM   in reply to Jim Simon

  Report

  You mean the FCP sequence, right? Yes, I noticed that. Pretty sure I did it exactly right, but happy to try it again.

   

  Made a discovery by sticking the CF card back in the camera. As I mentioned,  the footage, as unmessed-with as possible, plays fine in both FCP and PP 'Player' sides. Only once it hits a timeline does it go bad. Well, when you try to review the clip in camera, the clip I showed you and about four subsequent clips on that card, cause the camera to display a still thumbnail of the video, and the words "cannot play back image".

   

  Hmmmmmmm.......Bad CF card? Cosmic rays? Freakin' sharks wearin' freakin' lasers?

   

  But is this even relevant?

   

  Remember, the clips play in the NLE'S.

   

  They play with a small amount of horizontal tearing, especially in full screen, but I've seen that artifact a hundred times and never have been able to associate it with any downsides.

   

  So I've been messing with this for three days now, and in desperation I thought to go back way back, to the issues I had with

  FCP3 and 4 and the hardware I had back then, the same issue that prompted me to get a Sonnet F2, which solved it.

   

  Dropped frames.

   

  Sure enough. It definitely is a problem in playback of the timeline. There definitely seems to be a problem exporting.

  The question is why the export problem. I had understood that FCP (dont know enough about PP), upon export, performed

  substantial error correction of this very thing. IE it recognizes when dropped frames occur on export, backs up, and stitches up the gap. Right? Wrong?

   

  Now, if I'm right, I need to figure out where the bottleneck lies. Is it the F2? A couple years old, but few hours.

  Or the Mac, a couple years old, boatloads of hard use. Ideas how to troubleshoot?

   

  Oh and I got curious about my RAM utilization and discovered that I am in a serious deficit for whatever reason.

  Apple says to do what I'm doing all you need is 4gigs. They also state that if you see a number of page outs in Activity Monitor

  that is greater than zero...you need more RAM for what you're doing. I'm hitting 6.

    Submit

  |

  Mark as:
• 

  Currently Being Moderated

  20. Jim Simon,

  

  May 24, 2012 3:07 PM   in reply to abekutter

  Report

  You mean the FCP sequence, right?

   

  No.  Again, leave that closed.  Forget about it.  Uninstall it even.  From now on, FCP does not exist.

   

  I meant the Premiere Pro sequence.  It doesn't exactly match your media.  So go back to post 5 and make sure you're performing step 4.

   

   

  it recognizes when dropped frames occur on export, backs up, and stitches up the gap. Right? Wrong?

   

  Wrong.  There is no such thing as a "dropped frame" during an export from Premiere Pro or AME.  A print to tape maybe, which runs in real time.  But that's not what you're doing here.  Exporting takes all the time it needs, processing every frame in turn, never skipping any.

    Submit

  |

  Mark as:
• 

  Currently Being Moderated

  21. abekutter,

  

  May 30, 2012 4:33 PM   in reply to Jim Simon

  Report

  Sorry to bail on this. Bottom line is that the saga continues. Been busy, as you'll see.

   

  Just as an aside, why is it an acceptable state of affairs that these pricey products are so damn touchy touchy touchy,

  so damn buggy buggy buggy? Why are we, all of us, not continuously harassing the publishers to make them more robust, more

  transparent, and to do more to help us when their dodgy products go badeep?

   

  Enough.

   

  Here's where I am today, and let this be a lesson to all:

   

  I was getting nowhere. I followed the (generously given) instructions I received here, to the letter. Repeatedly.

  Nothing changed.

   

  I cleaned up the laptop, bigtime. Nothing.

  So I delved deeper into the vitality of my drives and RAM, and discovered that there were a whole lot of processes going on in the background

  that I could not turn off even after deleting the app. Yes, you, Verizon. Among others.

   

  Here's where I really went wrong: I listened to Apple, in the person of the manager at my local Apple store.

   

  He recommended I start over. Backup, reinstall the OS, reinstall the NLE's (PP, FCP, MC).

   

  Desperate times...

   

  Did it. As a result, I am in worse shape than ever. NOTHING WORKS.

   

  Lame #1:

  PP (5) couldn't compile media owing to an unknown error. That's helpful, Adobe, thank you. ....And then suddenly it could.

  Then it couldn't play video for more than a few and varying number of frames. Repaired permissions,

  and now it plays. Working it. No doubt there are other probs, but as of today it is NOT stuttering. Yay.

   

  Lame #2:

  Composer won't let me in because it thinks I'm trying to run two machines when I only own one license. 

  That should be easy to resolve if Avid ever responds.

  Then we'll see what else is broken.

   

  Lame #3:

  FCP won't open at all. I get a crazy error message telling me to check with the developer because the app may not be compatible with the OS.

  Oh, Apple, please. There's just one little line of something or other missing or corrupt, on a fresh install, and this is what happens?

   

  Lame.

  Lame.

  Lame.

   

  So if anyone out there feels my pain, please do share your wisdom on any or all of these issues.

  If I sound pissed off, well, where would your head be after pounding it against this wall for over a week?

   

  May the throughput be with you.

   

  [Edited for content]

    Submit

  |

  Mark as:
• 

  Currently Being Moderated

  22. Jim Simon,

  

  May 30, 2012 4:34 PM   in reply to abekutter

  Report

  Apple, please.

   

  I couldn't agree more.

   

  [Edited for content]

    Submit

  |

  Mark as: