[Seamus Callagy]

Thanks to Peter for encouraging me to post here –

We encountered a similar problem with students losing L+T files, having files appear offline anytime they closed the project or moved to another computer in spite of having their footage on an external hard drive.

it seems that at the core was a skipped step pre-ingest. Because of time and computer disk space issues some people used the Log and Transfer straight from the memory cards.

What confused us at first was the issue seemed to only affect certain groups, even though several had adopted this procedure- however on inspection this seemingly random slice of luck for some students was down to their being no other AVCHD files on the system when they entered into the L+T window.

And so, sorry if it seems like stating the obvious but –

with our machines on FCP 6.0.8, their is no option to use ProRes HQ, and therefore, it seems, no timecode for FCP or mere humans to confirm that a clip is really the intended/named clip

coming straight from the cards the Volume is NONAME which becomes the Reel Name in FCP, which Reel Name would be shared by all other straight from card transfers -as would the title ‘Clip #1’ ‘Clip #2’ etc and so while the FCP project might work with those files in the beginning, as soon as the project is closed and re-opened it can look for a ‘Clip #1’ etc that is not the one that was Log+Transferred into the project, but one that was L+T’d by someone else-
as someone mentioned in a previous post, FCP/L+T will see that there are already clips from NONAME in the L+T cache and so will increment from the end of those clips, thereby making what we see as supposed ‘Clip #1’ into what the computer sees as Clip #Seemingly Random Number

having scratch disks set incorrectly or having these conflicting ‘Clip #Names’ all going into the same scratch disk seems to compound the issue as does continual reconnecting and project copying

Without saying there is a simple fix – creating a new project and copying the cut sequence in as either a straight Cut + Paste or by using an XML import – and then reconnecting manually seems to have resolved the issue for those affected. And when the correct clips are back online – changing the Reel Number manually and also using the Rename File to Match Clip function after changing clip names in FCP – this seems to keep it all together thereafter.

Hope it helps someone

[Seamus Callagy]

Thanks to Peter Sengstock for encouraging me to post here – from a similar thread.

We encountered a similar problem with students losing L+T files, having files appear offline anytime they closed the project or moved to another computer in spite of having their footage on an external hard drive.

it seems that at the core was a skipped step pre-ingest. Because of time and computer disk space issues some people used the Log and Transfer straight from the memory cards.

What confused us at first was the issue seemed to only affect certain groups, even though several had adopted this procedure- however on inspection this seemingly random slice of luck for some students was down to their being no other AVCHD files on the system when they entered into the L+T window.

And so, sorry if it seems like stating the obvious but –

with our machines on FCP 6.0.8, their is no option to use ProRes HQ, and therefore, it seems, no timecode for FCP or mere humans to confirm that a clip is really the intended/named clip

coming straight from the cards the Volume is NONAME which becomes the Reel Name in FCP, which Reel Name would be shared by all other straight from card transfers -as would the title ‘Clip #1’ ‘Clip #2’ etc and so while the FCP project might work with those files in the beginning, as soon as the project is closed and re-opened it can look for a ‘Clip #1’ etc that is not the one that was Log+Transferred into the project, but one that was L+T’d by someone else-

as someone mentioned in a previous post, FCP/L+T will see that there are already clips from NONAME in the L+T cache and so will increment from the end of those clips, thereby making what we see as supposed ‘Clip #1’ into what the computer sees as Clip #Seemingly Random Number

having scratch disks set incorrectly or having these conflicting ‘Clip #Names’ all going into the same scratch disk seems to compound the issue as does continual reconnecting and project copying

Without saying there is a simple fix – creating a new project and copying the cut sequence in as either a straight Cut + Paste or by using an XML import – and then reconnecting manually seems to have resolved the issue for those affected. And when the clips are back online, we then get them to manually change the Reel Number in FCP and also to change the clip and use the Rename – File to Match Clip – function in FCP – this resolves the issue.

Sorry if its old ground – hope it helps someone.

We all skip steps sometime and sometimes we get caught badly, sometimes not so badly, but this is how we learn!