Edit-In-Place still caching media

FCSvr system, XSAN, Edit-In-Place set for all Devices. But when FCP projects are checked out by the editors, it still loads all the video files into their local Cache. Unable to duplicate the problem on my own system. The difference is that they have some Ethernet only clients, and some Fibre clients (FCP only on Fibre clients). Why would Edit-In-Place still download the video files to local cache?
FYI, I've set up FCSvr systems before, this is my first mixed (Fibre + Ethernet only) environment, and the first time I've seen this odd behavior.

OK, well, there were other problems they didn't tell me about. Some video assets could be drag-and-dropped from a Projects window in FCSvr to the Browser in FCP. Others could only be done from an Assets window in FCSvr. And this had been going on since the FCSvr 1.5 upgrade.
I attempted to change the URI, but FCSvr would simply revert back to the original every time I tried. I logged out, and the whole system seems to work fine now. Go figure.
Anyone see any quirks with the FCSvr 1.5 upgrade?
Now they want to upgrade everything to Snow Leopard. I'm not touching the Leopard Servers until I see a more stable SL Server!
Still, very odd problem. Wish I knew what it was exactly. Seems playing with URI's reset something. But it all works now.

Similar Messages

Edit-in-place but still prompt to cache

Hi,
I have my media stored on a SAN. The assets are there and media & Library devices, are set to edit-in-place URI's file://localhost/Volumes/Fibre 1/IDTV YV/Final Cut Server/Media resp. /Library. But on dragging an asset to Final Cut Pro I still get the "you need to cache" prompt.
What else do I have to do? Am I missing something?
regards,
Willard
Message was edited by: Willard Jansen

Problem solved. Turned out the specific asset was corrupt!

Assets are "Edit In Place" yet dragging to Final Cut Pro requests caching

This is an odd one. I have a large number of assets on our device that I can successfully drag from Final Cut Server directly to Final Cut Pro without issue. However I have what appears to be thousands of assets on the exact same device that I can not drag without the dialog box "You must add this asset to the cache before you can use it in a Final Cut Studio project."
This is very weird. If I right click on the asset in Final Cut Studio and select to view the Original Media I get the warning "The asset is an edit-in-place asset. Any changes..." so obviously it knows it is an edit in place asset, so why are they giving me grief when dragging to Final Cut Pro?
Specs: Final Cut Server 1.1, Final Cut Pro 6.0.4
Thanks!

Sorry that I keep replying to myself, but the bazaar behavior continues...
I took one of these odd assets and made a copy to my desktop. Then I deleted the asset and file within Final Cut Server. Next I moved the asset from my desktop back to the original location and waited for a Full Scan to pick up the asset.
After the Full Scan, the asset was draggable to Final Cut Pro! I can't possibly do this to every asset. Did the database get corrupt?
Ideas? Thanks!

FCPX Export issue. Item cannot be shared while it is still referencing media on the camera

I am having issues with exporting a project I just shot and I missed my delivery day and am now late. Need help ASAP. I'll try to keep this as brief as possible and stick to the pertinent information.
The Shoot: -2 Panasonic HVX-200's shooting on P2 Media shooting a live event -Dumped footage onto external hard drive via Macbook Pro on set into separate folders for organization using a Panasonic P2 Reader. -All dumps were confirmed completed and all footage accounted for.
The System: -Using Final Cut Pro X 10.1.2 -Mac Pro Tower 2009 quad core running OSX Mavericks 16gb Ram -Blackmagic Intensity Pro Card
The Edit: -2 Camera multicam edit -Imported footage using import media function -Imported from external drive -(important note: a camera has never been connected to the computer for this project) -Edit is finished, about a 2hr 20 min finished sequence (live event 2 cameras switched in post, all graphics and everything is done)
The Problem: -When I go to export via the "Share" function i get an error that says "This Item cannot be shared while it is still referencing media on the camera" -Imported footage has the camera logo in the corner meaning that it is referencing camera media; yet no camera has ever been connected.
Solutions I have tried: -Re-importing media with re-import function --Says that the camera is not connected yet I never had one connected in the first place. -Deleting preferences -Biting the bullet and starting from scratch to do a re-edit -- footage will not import without referencing "camera media" -Tried importing via dragging and dropping. Says it cannot importing the following files, lists all of the XML and MXF files -Started a new event, with a new project, with a fresh import; same results -Googled this to death, no solution seems to work, but I'll try whatever I have to; client needs this ASAP.
Questions: -The external drive is not showing up as a camera, so why is it importing as camera media? -Is there a way to salvage my edit and get it exported? I have a lot of hours into this and quite frankly, no time to redo the whole thing.
Please help!

I have had this issue too, and figured a work around. FYI, I rebooted, tried everything imaginable, and still no luck. I opened up iPhoto, and imported all the video clips into iPhoto. I then took the missing video from iPhoto, copied it to my desktop. Then I re-imported the video (same name) into Final Cut. I had to do some slight editing of the video, but everything worked fine, and allowed me to upload the video to YouTube.
Not certain it will work for others, but to recap, try to import the video into another program, then copy the missing video file to your desktop, and re-import to Final Cut.
Hope this helps.

Edit-in-place NOT working...

I've recently installed FCS at our small shop. I've read the Geller book, followed the Admin manual, and pretty much have gotten it to work.
However, I can't get "edit in place" to work. It did work when I initially installed the system and tested it. And now, after a complete re-install, it doesn't work.
I am using two local RAIDs. Each have a media directory that I set up as a device. For example:
One device is called "Mojo Project Media 02"
In the Device Pane (on the Admin / Client Java Interface) the Local Directory reads:
"/Volumes/RAID_02/Mojo Project Media 02"
So the Mac edit-in-place URI reads:
"file://localhost/Volumes/RAID_02/Mojo Project Media 02"
I can't get the edit in place URI to not ad "localhost" but I don't think this should matter.
Whenever I try to move media into a Browser Window from FCS, it tells me I must copy it to my local cache first. This didn't happen when I first installed/configured the system.
Can you not set up edit-in-place for a local directory (ie. a volume locally attached to the server with FCS installed)?
I know it worked before. Is there something I am missing?

Thanks A. Richards.
After much testing, I realized that on the FCSr machine that it indeed had edit-in-place status because of the storage directly attached to it. BUT the other client computers did not.
So basically, since we don't have the $1000 a seat for XSAN and we are only cutting DV and DVCPRO HD...
We could configure our Mac Pro Server to be an AFP share over the network; it's plenty fast over Ethernet since it's aggregated over 6 gigabit ports to a switch and has PCIe RAID storage attached. We could give this edit-in-place status IF...
We used another machine (server class) to install FCSr on.
This would work right?

Edit in place without Xsan

Hi
Is it possible to edit in place without xsan?.
I've tried adding a new device and entering the URI in administration but it still wants to cache
thanks in advance
regards
Lee

I had the same problem. here's what you do since apple isn't that clear in the help file.
from the FCS client app open the admin pannel
click on devices
double click Library (this is the default, same applies to other drives that are mounted)
on the "local directory" line click once in there and then scrub through to see your full path
copy this full path
on the "macintosh edit-in-place URL" line type file://localhost then paste the path from above
log out of the client and log back in
you should now be able to drag a fcp project to the FCP icon on the dock and start editing in place

Edit in place and versioning

Hi
Having built a very fast network to make use of 'Edit In Place' we are surprised to see that Edit in place does not appear to support versioning? i.e we want to drag out a project, work on it and then drag it back into FCserver, where a new version is created. Any thoughts?
There only seem to be hints in the manuals about using EIP, contradicted each time by the statement that 'Checking in and out' is the best way to use FCserver...
Thanks
Dan

Thanks John - I think you made a vital link in my understanding!
I've been messing about this morning and all my problems (touch wood) seem to be resolved after your last comment.
You may remember replying to my thread a while back about metadata... Even that seems to be fixed now!
I think I should outline my workflow - it may help anyone reading!
Firstly, I have changed my compressor cluster to a custom one. I was having problems using 'this computer' cluster; freezing transcodes and i think it was screwing with my Log and Transfer metadata too. Anyway, it tells you how to change it to a custom cluster in the setup guide - takes two minutes. I recommend it, even if you only ever use the admin user to use FCServer like we do.
Ok, the workflow:
-Create a new (filesystem) device with an Edit In Place path using the java client app (not the server pref pane). call it XXX_JOB for example. remember to create a folder in your storage/raid/san first!
Local Directory:
/Volumes/Data/FCSvrDevices/XXXJOB
Macintosh edit-in-place:
file://localhost/Volumes/FCSvrDevices/XXXJOB
(nb: our server has a RAID called 'data', it's share is a mounted as a volume on the local machine called 'FCSvr_Devices')
-Create a production scan for the device - set it off - make sure it is setup to read the correct directory levels for its production name and metadata name. in my experience this takes some fiddling! the workflow example book regarding this setting features a few misprints too!
-In this order; open FCP on the local machine, set the capture scratch to the XXX_JOB device you just made (our devices are on a server volume mounted locally - v.important for EIP to work). Save the project with the exact name you want the production to be - XXX_JOB.fcp. Open log and transfer, add your metadata and set it off. when it is done save your project and close FCP.
Check locally in finder that as a result of changing your scratch you have something like:
FCSvrDevices/XXXJOB/capture scratch/XXXjob/mvixxx.mov
(Where FCSvr_Devices is your storage device/raid/san, XXX_JOB is the new device and mvi_xxx.mov is a file from L&T.)
-If all is well you should soon after have a new production folder called 'XXX_JOB' in FCServer. If you double click this you should see all the files you ingested using L&T. You may now upload your local FCP project to this production. If your Edit In Place has worked properly then you will not duplicate your original media. We do this because we don't want to have any extraneous copies or have to take any unnecessary steps in deleting them.
-When you check this project out you will get a pop up asking you if you want to use original or proxy media. since we are editing in place it doesn't matter. hit 'check out' and only the FCP project will come down. you can now edit away, adding more media as you go from any EIP enabled device - we've found it even works using finder (allowing the use of finder's cool spacebar preview that FCServer doesn't have!). When you check back in FCServer doesnt duplicate any media. you just get a nice new version of your project and no uploading or caching! you can view the assets used in the project by double clicking to 'enter' the project.
This seems to work perfectly now. If anyone has any thoughts as to if this is the best way of doing it i would be interested to know.
Thanks again John
Best
Dan

Edit-in-place isn't working

Hi
I've a problem with the edit-in-place config. I have mapped the device with "afp://..." and put the path into the field "Macintosh edit-in-place URI":
file://localhost/Volumes/Data/FCS/...
The file path shouldn't be the problem in order of the finding items when I test it in Safari.
But I still need to cache the asset when I drag'n drop the file into a final cut project. And I don't get a grey dot in the list view in front of the asset.
Any ideas to fix the problem?
thanks!

I am having similar symptoms using Lightroom 1.2 and CS2. I just updated to Lightroom 1.2 this week.
The first time I select edit in CS2 Photoshop launches fine and the image is transferred. If I attempt to edit a second image Lightroom hangs indefinitely on "Preparing the file for edit". Lightroom is dead at this point. Any attempted operation, including canceling the edit, just adds to the hanging stack. The only out I have found so far is to exit Lightroom, tell it to abandon all uncompleted tasks, and then restart it. At that point it will again work correctly to edit one image. It is the editing that causes the hanging, other functions performed after an edit do not (e.g. working in the develop module on a second image).
Lightroom 1.1 did not have this problem. The images I was working on were imported into Lightroom after I updated to 1.2. I am working under XP Pro and off of an internal (vs external) hard drive.

Setup Edit in place

I need to setup edit in place on our main array. I have plenty of bandwidth so that's not an issue.
how do you make your main library an edit in place device? I've tried adding file:///volumes/volumenamehere in the mac edit in place url field
what's wrong?

I got it working. I will post this just in case it helps someone else.
this is the setup:
dedicated macpro running FCS with a locally attached SATA RAID called FCS_RAID
It is a server, both public, dhcp, and some other stuff not relevant. I am directly connected via 2 gigabit ethernet cables (trunked) and use a locally assigned IP e.g. 168.254.xxx.xxx
the volume is mounted and is accessible as file://localhost/Volumes/FCS_RAID/
I am wanted to use the Library (default created by FCS) as an edit in place device since that is where the media lives
to get EIP to work I copied the path from the "Local Directory" field. So basically file://localhost/whatever it says in the local directory field
What is not working properly now is the location in which the project thinks the files are located.
This is our simplified workflow:
P2 dumped to external drive during shoot
archived raw etc
footage is logged and transfered in FCP and media managed to a DROBO
from there is is uploaded to FCS and our main RAID.
If I were to check out the project I'm sure the file locations would be updated to the local cache but since I'm doing an edit in place I want to use the media on the RAID. But, when I "reveal in finder" I see that the media is linked to the DROBO instead of the RAID. Now the media is also located on the RAID in the standard "library" location.
Why didn't FCS update the FCP project to the new location of the media?
I can work around this by unmounting the DROBO and relinking the media to my RAID but I don't want to.
Thanks for your help guys.

Edit In Place but use Edit Proxies possible?

Hi all,
Trying to figure out if the above is possible.
Reason being Orig media is either uncompressed or prores 444 or Red.
Over Gig-E the Prores edit proxies are fine to be edit in place so no need to cache every time.
Is this possible?
Cheers
Si
Message was edited by: simonblackledge

Yes. You'll want to reshare the edit proxy device read only, via AFP or NFS.
There are caveats - editing over ethernet cannot guarantee bandwidth and latency in the same way as fibre or direct of disk, so there might be occasional dropped frames. But for the purposes of editing with the proxies, this is not so much of a big deal - you'll be conforming with the hi-res media at a later point.
Depending on how many clients and streams per client would be using this, you'd need to have a think about the backend infrastructure. I've got a setup where I have the edit proxies device on an XSan and a dedicated XServe resharing the device as AFP (read only). That keeps the AFP I/O off the final cut server machine.
You can also do things like get a 4 port ethernet card and bond the network interfaces to give you more bandwidth from the xserve to the switch.

Getting my head around editing in h.264, Proxy Media, or Optimized Media for Canon DSLR

I'm trying to understand these different workflows, how they work, plusses and minues of each, with a focus on how it relates to file size. Please help me fill in the gaps
Here's what I think I know now.
Optmize meda to ProRes 422
Better for performance, but creates HUGE files. On 30 GB worth of h.264 footage, the optimzed files were over 100 GB, not including any render files, etc. I'm running off a laptop and only use external drives for storage, so I'd like to find a better way that uses less disk space and requires less time to convert (took all night for those 100 GB)
Proxy Media
Creates an easy to edit file that is very poor resolution and quality. You can use this for editing, then before final export, switch back to original/optimized media and it will re-render and reconnect with the good media.
QUESTION: If I ONLY do the Proxy optimization, do I need to also Optimize to ProRes 422 at some point also, or can I just have it refer to the h.264 .mov files and get equivalent results? If I can, this seems like a good compromize.
Editing directly with the h.264 footage
I have read that some people are dropping the footage directly into the timeline and editing without any real problems. Others say it will cause performance issues and to always optimize. Ideally I'd like to do this way as it is the quickest (no conversion) and has the smallest file sizes of all of them.
It would also be useful to start out this way and optimize later if I need to on the smaller sub-set of the footage. But I have found no good way to do a rough cut with little editing and then select only those clips used in the timeline for optimization in case I start experiencing slowdowns. Yes, you can clip-by-clip select them and "show in event browser," but you can't do this with multiple clips as far as I can tell.
So what are your workflow tips for keeping file size down? What am I missing in my understanding of these options?
I'm on a 2010 MBP i7 (dual core) with a 7200 RPM drive for what it's worth since I know the h.264 one largely depends on the hardware.

Proxy Media
If I ONLY do the Proxy optimization, do I need to also Optimize to ProRes 422 at some point also ...
Nope. You don't need to do the "Optimze Media" at all, you can use with the Proxy media for your working edit, then switch the references back to the Original media for mastering/export.
... or can I just have it refer to the h.264 .mov files and get equivalent results? If I can, this seems like a good compromize.
Exactly. And yes it is, an excellent compromise. Start working with the original media right away, but have FCPX create proxies in the background (which it switches to using as soon as each one becomes ready); if at any point you need to check a clip in place in the timeline in full resolution then you can just quickly toggle your general playback preference to "Use original", otherwise just edit away with the proxies and then switch that preference back to "Use original" when you are ready to output.
Editing directly with the h.264 footage
I have read that some people are dropping the footage directly into the timeline and editing without any real problems. Others say it will cause performance issues and to always optimize.
Yep, you can edit just with the original media if you choose but your source footage is H264, a dreadful edit codec by any measure, and certainly you will get much better timeline performance if you work with transcoded Optimized or Proxy media instead.

HOW TO: EDIT IN PLACE ON WINDOWS CLIENT

Hi everybody,
I work in TIBA (broadcaster company), we use FCS so much and I have a problem, actually i have running edit in place on XSAN for MAC clients, but i cant work of the same way on windows.
We have XSAN and fiber channels working.
I configure the device but it doesn´t work.
Somebody, help me please. My email is [email protected]
Kind regards
Emiliano

Hi,
No iam not using stornext for the windows clients.
The mac and windows clients running on ethernet. The the mac clients have mapped the xsan volumes using AFP or SMB protocol and the edit in place works ok.
The windows clients have mapped the xsan volumes through SMB but the edit un place doesnt work, the files are cached and doesn´t run as edit in place.
Note: sorry by my english.
kind regard.
Emiliano
Are you using StorNext FX to add the Windows clients to your Xsan? If so, then all you have to do is add the Windows Edit-in-place URI to each EIP device in the Devices section of the Java client Admin GUI (not the System Preferences pane). Once you've done that, EIP will work for the Windows clients as well. Here are the instructions for entering the correct URI syntax.
If you are not using StorNext FX for your Windows clients, please give us more detail on how your system is set up.

'Edit in Place' for XLSM-files (Excel Macro-Enabled)

Hi,
is it possible to activate 'Edit in Place' for xlsm-files (Excel Macro-Enabled Workbook file)?
For xls(x)-files there is the link 'Edit This File', but not for files of type 'xlsm' allthough they could be dealt the same way with Excel.
I know I can edit this files using the 'Add-in for MS Office' and via the 'Vibe Desktop', but it would be nice to deal them like other Excel-files.
thx
Martin

Originally Posted by mschuhmann
RTFM helps I admit:
Novell Vibe 3.3 Administration Guide > Site Setup > Setting Up Site-Wide Customizations > Configuring File Associations for Edit in Place Applications
Novell Doc: Novell Vibe 3.3 Administration Guide - Configuring File Associations for Edit in Place Applications
Append ".xlsm" for the variable edit.in.place.file.applet.extensions, edit.in.place.file.webdav.extensions
Hi Martin,
Yeah, the Vibe docs can help on occasion
Still, thanks for feeding it back to the forums as it can be quicker finding a hit in the forums than having to go through the docs!
Cheers,
Willem

What is the error message "This item cannot be shared while it is still referencing media on the camera" mean?

When I tried to create a movie, I got this message: "This item cannot be shared while it is still referencing media on the camera". What does it mean?
How do I resolve it?

eDude.com wrote: ... What does it mean? ....
It means that you cannot share something unless it resides on your computer.
eDude.com wrote:... How do I resolve it?
Import all clips that you plan to use in your finished project to your Mac before you edit and share your finished work.
For help see iMovie '11: Overview: Importing video and iMovie ’11: Import Video.

Edit in Place on test setup

Obviously, I'm doing something wrong?
My test system in my Macbook Pro. I have a folder at the root of my boot drive named STORAGE. I have set it up as a device, and in the Administration/Devices window, I have defined the URI as file://localhost/STORAGE. When I look at the Devices list in the Final Cut Server Preference Pane, next to the device STORAGE it says XSAN, so FC Server certainly thinks it is an edit in place device. However, when I check out a Final Cut Pro Project, I can see that server is moving all the associated clips from STORAGE to my cache. In the Show All Jobs window, I see 34 events where it says Downloading <name of file> from Device Storage to Device Export. So for some reason, I'm not able to actually edit in place.
What am I missing?

Oh, nevermind. I figured it out. I needed to have the Volumes/Macintosh HD in the URI even though it is technically the "root" drive.

Edit-In-Place still caching media

Similar Messages

Maybe you are looking for