[Jonathan Lakser]

I am already in touch with QNAP about this.
I am curious why you think the QNAP would be a better solution than Small Tree though.

Thanks for responding.

[Jonathan Lakser]

ok thanks for the response

[Jonathan Lakser]

Thanks for all the responses guys.

Just so you guys know where I am coming from here is the situation.

We are a post house with both Avid and FInal Cut Systems. A lot of the times editors will have the option of choosing which system they are comfortable working with based on the job they are doing. More often we have been using Final Cut over Avid, simply because our Final Cut systems are running the latest software While we still run an older Avid version.

One of are editors who primarily works in Avid but is also able to work in Final Cut (just not as fast) is forced to use Final Cut because it makes the most sense for the workflow. (camera type, file formats, etc… I am not going to get into the details)
This Editor feels he would be able to speed things up and also be a little more comfortable if he had similar matte tools to Avid on his FCP system. I agree it makes sense to just send to motion but the way we handle our workflow; comps and motion effects are generally handled by assistants in third party software such as Motion but mainly After Effects.
Since we are offline for the editor to make a quick change to a comp or motion effect by using the native matte or masking tools makes a lot of sense and helps things move quickly.
When it has to go to a separate program it is usually the case that someone else will handle the change while the editor continues to work with the client.
Since all these comps and motion effects will essentially be redone during the online (most likely in the flame) I think it makes sense to have more masking options natively in Final Cut.

Thanks for all the suggestions though. I think we need experiment with motion a little bit more.

If any one has any more suggestions though I am still open to them.

[Jonathan Lakser]

Ideally we would like to be able to not leave FCP. But I suppose sending to motion is really one of the only options right?

[Jonathan Lakser]

u need a leopard install disc from a mac pro with nehalem processor.

[Jonathan Lakser]

i have just revived an email from edit share report regarding this issue as i have pointed them to this thread. here is what they wrote:

I have done some checking here. This doesn’t seem to be an issue with a
32-character filename limit. I am able to create files with
40-character names on EditShare Media Spaces and not have any issue. In
fact, 44-characters including a “.mov” at the end. I didn’t try longer.

What could be an issue is the total number of characters in the PATH.
That is, the combination of “Media Space Name” + “Capture Scratch” +
“Project Name” + “File Name”. In fact, you probably have to add the “IP
Address” to that as well, i.e.,

\\192.168.1.3\Media Space Name_1\Capture Scratch\Project Name\File Name

I think if the total exceeds 255 characters (the limit for POSIX and
Windows filesystems) you can get into some trouble. When you first WRITE
the file, Samba and OS X might be able to agree on what spot on the
storage system you are pointing to. But then you might get some weird
filename truncation later after disconnecting and re-connecting.

However, that all said… in your case, it looks as if you have
something like:

\\192.168.1.3\UTW201G_1\Capture
Scratch\U2W_201_0916\U2W201_p49_clip08_sit down interview

That’s only 89 characters (I don’t know your IP Address), so I don’t
think the 255 character limit for PATH is coming into play here.

Question: Can you reproduce this problem reliably? If so, can you tell
us how you reproduce it? If you can, then we can up the level of Samba
logging to see what’s actually going on.

I don’t know if THIS is relevant — a post about QuickTime failing to
deal with filenames > 60 characters:

https://lists.apple.com/archives/QuickTime-API/2006/May/msg00113.html

i will update when i have more information on what this means for the issue we are experencing but figured I would throw this up here.

[Jonathan Lakser]

we are using Dave SMB to connect to the editshare. During the time when media was ingested on to the edit share they were mos certainly connected via Dave smb.

this however is a good line of thought and i will most certainly check it out to be sure.

[Jonathan Lakser]

kona 3 will only do analog audio monitoring if you buy the kbox

[Jonathan Lakser]

Thanks for your responses guys. That last suggestion seems like it might be on the right track. Edit-Share is a linux based server so the fact that an issue very similar to this has existed on a linux based san leads me to think we are headed in the right direction.

Edit-Share has a great Tech Support, and they are very helpful. However I was unsure if this was a storage issue or just a general Final Cut Pro issue.

i am going to suggest they keep there file names under 32 characters and see if we can avoid any issues in the future… thanks for the help and any more suggestions are appreciated.

[Jonathan Lakser]

sorry for the repost but i had the wrong email address listed before

we are editing standard dv footage. it is stored on an isilon system which is similar to a san.
it is very fast and the same footage looks perfect on the same computer that is right next to it.

when we open the same project on another computer there are no play back issues. it isn’t really affecting anything besides the playback in fcp…