Creative Communities of the World Forums

The peer to peer support community for media production professionals.

Activity Forums Apple Final Cut Pro Legacy Random Access Memory_am I wrong?

  • Random Access Memory_am I wrong?

    Posted by Sherwood Ball on September 28, 2006 at 8:24 am

    Why is it when we spend hours upon hours tweak out cuts, save them
    and then open up the file the next day to find anamolies.
    Is it just the nature of the beast, random access memory?

    Spent months on my documentary feature, put the movie into eleven nests,
    calling them chapters and exported to compressor.

    The long nights of handholding the cpu, praying and hoping the computer
    wouldn’t crash or Compressor wouldn’t send a failure message.
    Making me want to throw the computer out the window.

    Funny thing is sometimes it would just work perfectly.
    No reason or rhyme. But having to stay up all night, several nights in a
    row at deadline time, ain’t happenin’.
    Couldn’t we just set it to export, go to sleep and then wake up
    with a “successful” message. Ideal world?

    Not worth the wearying, exhausting aggravation.

    One of the moderators mentioned exporting to QT then putting the QT’s
    in a new sequence, then exporting to Compressor.
    Makes sense, but shouldn’t Compressor work properly exporting from the
    timeline?

    Anyone been a beta pig for the new update of Compressor yet?

    and anyone have any OTHER workarounds?

    Thnx.
    Sherwood

    G5 Dual 2.5 GHz
    4G Ram OSX4.6
    Sata drives
    Final Cut Pro 4.5HD, Logic Audio 7.1
    PS CS2, AE CS2

    Sherwood Ball replied 19 years, 7 months ago 4 Members · 6 Replies
  • 6 Replies
  • Gunleik Groven

    September 28, 2006 at 8:34 am

    The advantage of _first_ exporting (dependent) quicktime movies is that you can batch process files while still working in FCP. As far as you go from a dependent quicktime, you won’t get any extra generation loss.

    Funny you mention compressor woes. Haven’t had any for a while, but I’m using bitvice for mpeg-2.

    Gunleik

    https://www.vuture.no/testvid

  • Gunleik Groven

    September 28, 2006 at 8:43 am

    btw

    Nested sequences can be a pain if you go back and edit.

    Gunleik

    https://www.vuture.no/testvid

  • Shane Ross

    September 28, 2006 at 3:21 pm

    [S.E. Ball] “Spent months on my documentary feature, put the movie into eleven nests,
    calling them chapters and exported to compressor.”

    FCP slows down a lot when dealing with nests. Eleven of them will REALLY slow it down.

    Don’t nest if you can help it.

    Shane

    Littlefrog Post
    http://www.lfhd.net

  • Sherwood Ball

    September 28, 2006 at 7:59 pm

    Nesting is a freakin’ joke.
    It shouldn’t be an option.
    When I play back the nest, audio is clipped, yet when
    I open up the nest and play, it’s not clipped.
    Unbelieveable.

    G5 Dual 2.5 GHz
    4G Ram OSX4.6
    Sata drives
    Final Cut Pro 4.5HD, Logic Audio 7.1
    PS CS2, AE CS2

  • Gary Adcock

    September 28, 2006 at 8:07 pm

    [S.E. Ball] “When I play back the nest, audio is clipped, yet when I open up the nest and play, it’s not clipped. Unbelieveable.”

    how many tracks of audio do you have?
    if you are over the default setting 8 TOTAL tracks of audio YES it does clip.
    if you have enough hardware and RAM try upping the number of Audio tracks in the Prefs.

    What about the mixdown function or item level render options for audio renders.

    gary adcock
    Studio37
    HD & Film Consultation
    Post and Production Workflows

  • Sherwood Ball

    September 28, 2006 at 8:25 pm

    Only one or two audio tracks of an interviewee being clipped.

    Pref’s are at 8 audio trks.

    WHat’s to mixdown with only one or two tracks?
    But a good policy, thank you, for anything over that amount.

    G5 Dual 2.5 GHz
    4G Ram OSX4.6
    Sata drives
    Final Cut Pro 4.5HD, Logic Audio 7.1
    PS CS2, AE CS2

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