Dumb Proxy Question...

Lately I've been learning a thing or two about Proxy and how to create them for better playback and editing performance.

But I had an epiphany: I noticed that created Proxy media is stored in the Library bundle, at least the way I have it set up. In a project that has created Proxy, I get that you can switch from Proxy to Optimized/Original on the fly.

So here is my question, an apologies in advance if this has been covered a hundred times. Let's say I want to go off site to my Lakefront Villa and edit on a laptop. If I just copy the Library that has the Proxy to another drive/computer, do a bunch of editing, and then upon return to my workstation, re-copy that Library back, all my edits will re-link to my original media? On import of content, I always chose leave in place.

Does this question even make sense???

Thanks.

Jonathan

Whoa there partner! How do you get a Library that is "proxy only"? Not sure how that would work.

I tested this the other day, in fact. Made a Library, made media external. FCPX puts original, optimized and proxy all in the same location. Copied the Library to external drive. Copied external media folder, but only with proxy media folder, to external drive. Took it to work with me and launched it. Had to relink files to Proxy folder, but everything was off-line and unusable.

So if there is a way, I don't know it. Maybe there's a trick someone else here knows that I don't.

Please fill out the feedback form asking for a Proxy Only Library Version to edit on-the-road.

Jonathan Levin wrote: ....I noticed that created Proxy media is stored in the Library bundle....copy the Library that has the Proxy to another drive/computer, do a bunch of editing, and then upon return to my workstation, re-copy that Library back, all my edits will re-link to my original media? On import of content, I always chose leave in place....

I think this will work IF your drive name does not change. IOW you rename your portable or laptop drive the same volume name as the original. There are definitely problems with relinking in a proxy-only workflow if the drive name changes.

Additionally, there are two ways you can use proxy-only workflow with a "lean library", IOW use external proxies which are distributed once to remote editors, then email small library files back and forth to collaboratively edit. The first is described in this article from fcp.co:

www.fcp.co/final-cut-pro/tutorials/1828-...ant-by-using-aliases

The other way is a little too complex for me to describe from memory but it is covered in the Ripple Training 10.3 class on media management: www.rippletraining.com/products/final-cu...-final-cut-pro-10-3/

Other complications covered in the above Ripple training class include how to manage audio and graphic files (which don't have proxies) in a proxy-only workflow.

Both of the above cases work best if the disk volume name does not change. IOW you build the proxies on the portable drive you intend to distribute or you build them on your main drive, copy the proxies to a portable drive then rename that volume. If anything goes wrong on the remote machine and you need to relink to the proxies, this often will not work.

This entire area needs improvement in FCPX. We frequently discuss the ability to email a lean library back and forth for collaborative work. However you obviously can't do that with internal proxies, and there is no robust, fully-supported procedure for external proxies. With the widespread use of 4k, using proxies is more important than ever, likewise working collaboratively with lean libraries. However FCPX does not well support both of these important features when used together. The above procedures are workarounds.

Thanks Joema.

I had no idea that this was not as easy as it seemed. As a review: My workflow is to create a folder on my HD. In that folder I create other folders. Music, photos, graphics, Original video, and so on. All before I even launch FCP. Then In FC, I create a new Library and save that in the folder with all the other folders. Do my import, create and set up project(s).

Then create the proxy in FCP of imported video. I know I could do this on import too. Proxies created in Library bundle.

Now if I want to take this on the go to work on another machine, I would copy the entire folder WITHOUT THE ORIGINAL MEDIA over to the new drive. On new machine select Proxy and edit away. All photos, music, graphics still linked since I have those folders/files

Upon return, simply drag ONLY the library to first computer, replacing existing Library. Then all edits should convert to Optimized/Original media? Aren't proxies just little ProRes files and all edits/changes are metadata anyway?

Jonathan

Jonathan Levin wrote: ...Then create the proxy in FCP of imported video...Now if I want to take this on the go to work on another machine, I would copy the entire folder WITHOUT THE ORIGINAL MEDIA over to the new drive. On new machine select Proxy and edit away. All photos, music, graphics still linked since I have those folders/files...Upon return, simply drag ONLY the library to first computer, replacing existing Library. Then all edits should convert to Optimized/Original media? Aren't proxies just little ProRes files and all edits/changes are metadata anyway?...

You are using external media but your proxies are in the library. You can copy that library to a 2nd machine and edit -- but the music, audio, graphics and still photos will not be there since proxies are only for video not other media types. Assuming you don't need those other media types for your remote editing, it should work. You can edit on the road and copy your library back. However the library will potentially be pretty big since it contains not only edits but the proxies.

However instead of deleting your original library I would suggest renaming it or duplicating (assuming you have the space) until you're confident your edits are all present and accounted for and it will link to the original media.

Another problem is differing drive volume names. This is a potentially tricky area when dealing with FCPX proxies. In general the safest approach is just rename the drive volume on the remote machine.

The complete procedure for a proxy-only workflow, including music, audio and graphics is described in the Ripple Training FCPX 10.3 media management tutorial. This shows how to have external proxies outside the library and simply copy the small library bundle to the remote machine, then back again.

Before committing significant work to any workflow, it is best to thoroughly test this.

Just a note, if your Library storage settings in the Inspector specify that media be stored in an external folder, proxies are made in the external folder.

Thanks guys. I think its getting through my thick skull. So even though I can swith to proxy for the video, My other assets would go offline because you can't create proxy media of photos, music, graphics, etc.
I sssume I would get the bright red missing media warning in it's place. Sound about right? At this point I intend to view the Ripple training stuff.

But how great it would be to be able to work on something which included the assets and have some sort of simple re-link

Thanks so much!

Jonathan Levin wrote: ...you can't create proxy media of photos, music, graphics, etc.
I sssume I would get the bright red missing media warning in it's place. Sound about right? At this point I intend to view the Ripple training stuff....But how great it would be to be able to work on something which included the assets and have some sort of simple re-link...

Yes you get red missing media icons if you move the proxy-containing library to another computer and try to access the non-video media. There is a workaround (discussed in the Ripple 10.3 Media Management class), which is creating a scratch library, setting properties for that to an external location, drag/drop the graphic/audio media from main library to there, consolidate, then move the folder to the laptop containing the proxy library, open the library and relink the audio/graphic media only.

Yes FCPX badly needs a formal, UI-supported method of comprehensively dealing with external proxies (inc'l graphical & audio), including robust relinking for both original media and proxies. You can make this work today as documented in the above tutorial but it is very cumbersome, fragile and error-prone.

I often work with proxies without having with me the original media. It's easy and safe. Just "leave file in place" when you import and let the proxies inside the library bundle (I keep the original media in a storage drive and the library in some kind of portable drive). Then you can edit where you want just having with you the library. Obviously when you try to switch to "original media" you'll see everything offline, but, when relinking the originals or reconnecting your hard disk with those files there are no problems (and even after relinking you won't lose proxies).
One side note: since fcpx doesnt make proxies of audio and graphic files, remember to carry those files with you!