-
Random Access Memory_am I wrong?
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.
SherwoodG5 Dual 2.5 GHz
4G Ram OSX4.6
Sata drives
Final Cut Pro 4.5HD, Logic Audio 7.1
PS CS2, AE CS2