We will add some updates further down the road to see how we are getting on with ClipExporter. But even if you save a small amount of space on each project pretty soon at all adds up. Obviously, our case is a fairly extreme one in terms of the amount of space that we can save by using this software. But from the space saving results that we are seeing so far it is well worth this extra effort. And so far we have only been testing it on our more ‘simple’ editing projects where we don’t have a lot of video and audio layers or too many visual effects.
#CLIPEXPORTER FOR FCPX SOFTWARE#
We have had to change our editing workflow a little to incorporate the new software which now takes a little more time. We have been testing out ClipExporter for the past few weeks here at CEDE and we have been impressed with the results. We can then delete the clips that are not used from our server and voila! From bloated, overweight rushes to space saving, efficient clips in no time at all.
But what we do is then make a “light” version timeline of the same project and reconstruct the time using these clips. The idea is that then you can take these clips and go into Aftereffects or Nuke to do further post production work.
#CLIPEXPORTER FOR FCPX FULL#
So you end up with a folder full of short clips that you are going to use in your video. Then the program will make copies of the each individual clips used in the timeline referencing your original rushes.
#CLIPEXPORTER FOR FCPX PRO#
The idea behind ClipExporter is to be able to quickly export clips from your Final Cut Pro X timeline. But we can’t afford to work this way anymore and now we have started to take action to fix the errors of our ways.Īfter many discussions in the office our studio technician, Gilles Raimond, found a lovely little program that seemed to be the answer to all our problems. Obviously, this takes up loads of space on both our working server and archiving server. Our rushes policy up until now has been the classic “keep everything” approach. At the end of their sessions we have three large video files (we record three video streams with audio simultaneously), often 25+ GB each, with lots of mistakes and pauses that we will never use within those files. When they record we tell them to start the recording at the beginning of their session and just let the video record continuously, capturing mistakes pauses and all. So we have a studio assistant set them up in the studio and do a short test recording to make sure everything is working properly, then after that they are on their own in the studio for their recording session. The concept behind these studies was to allow the professor, presenter or speaker to be as autonomous as possible. Here at the EPFL we have three studios specifically designed for recording MOOCs. To help you understand our problem let me first explain briefly our setup here and how we work with our rushes. We have known for a while now that our method of storing our rushes isn’t the most efficient.
Right now at the Centre for Digital Education (CEDE) at the EPFL we are starting to feel the pinch with our server space. Ahhh, the age old problem of storing digital rushes on servers or hard drives is the bane of every production company and freelancer alike.
0 kommentar(er)
