Opening a movie in another app MODIFIES IT?

Question

hi,
final cut pro X 10.1.
I have FCP set to leave footage where it is, and make aliases in the event.
with FCP NOT LAUNCHED, i imported some files (that are referenced in FCPx) into After effects, interpretted the footage to a lower FPS, then I exported NEW VERSIONS of those files under different names.
I launched FCPx, and it says the original files have been modified.
I have 3 issues with this:
1. No they weren't.
2. WHY DOES IT MATTER? the footage is the same length, same content, same everything...
3. I can't find anything that lets me tell FCPx to shut up and import the file, and use it. 
can anyone help shed light on this? why it happens, and then maybe (i know I'm reaching here) provide a FIX, that doesn't involve.... maybe two hours of labor, replacing the unchanged movies that are riddled throguhout my project?
thnx
-t

Answer 1

and just for fun, some excerpts right from Apple's current Human Interface guidelines (google it)
Allow the user, not the computer, to initiate and control actions. Some applications attempt to assist the user by offering only those alternatives deemed good for the user or by protecting the user from having to make detailed decisions. Because this approach puts the computer, not the user, in control, it is best confined to parts of the user interface aimed at novice users. Provide the level of user control that is appropriate for your audience.
The key is to provide users with the capabilities they need while helping them avoid dangerous, irreversible actions. For example, in situations where the user might destroy data accidentally, you should always provide a warning, but allow the user to proceed if they choose.
Consistency in the interface allows users to transfer their knowledge and skills from one application to another. Use the standard elements of the Aqua interface to ensure consistency within your application and to benefit from consistency across applications. Ask yourself the following questions when thinking about consistency in your product:
Is it consistent with Mac OS X standards? For example, does the application use the reserved and recommended keyboard equivalents (see “Keyboard Shortcuts”) for their correct purposes? Is it Aqua-compliant? Does it use the solutions to standard tasks Mac OS X provides? (For more information on these solutions, see “Mac OS X Technology Usage Guidelines.”)
Is it consistent within itself? Does it use consistent terminology for labels and features? Do icons mean the same thing every time they are used? Are concepts presented in similar ways across all modules? Are similar controls and other user interface elements located in similar places in windows and dialogs?
Is it consistent with earlier versions of the product? Have the terms and meanings remained the same between releases? Are the fundamental concepts essentially unchanged?
Is it consistent with people’s expectations? Does it meet the needs of the user without extraneous features? Does it conform to the user’s mental model? (For more information on this concept, see “Mental Model.”)
Meeting everyone’s expectations is the most difficult kind of consistency to achieve, especially if your product is likely to be used by an audience with a wide range of expertise. You can address this problem by carefully weighing the consistency issues in the context of your target audience and their needs.
Encourage people to explore your application by building in forgiveness—that is, making most actions easily reversible. People need to feel that they can try things without damaging the system or jeopardizing their data. Create safety nets, such as the Undo and Revert to Saved commands, so that people will feel comfortable learning and using your product.
Warn users when they initiate a task that will cause irreversible loss of data. If alerts appear frequently, however, it may mean that the product has some design flaws. When options are presented clearly and feedback is timely, using an application should be relatively error-free.
Anticipate common problems and alert users to potential side effects. Provide extensive feedback and communication at every stage so users feel that they have enough information to make the right choices. For an overview of different types of feedback you can provide, see “Feedback and Communication.”
A reliable, stable app behaves in predictable ways and maintains the integrity of the user’s data, while doing everything possible to prevent data loss or corruption. It also has a certain amount of maturity to it and can handle complex situations without crashing.
An interoperable app communicates seamlessly with other apps and services so that users can open their content in different apps and exchange information with other users. Users appreciate interoperability because it means that they can focus on their content, without having to pay attention to details such as file formats and data-exchange protocols.
needless to say, everything I have copied are areas where FCPx needs work. I love the timeline editor, I think the app has great promise, but I am so frustrated with the stupid crashes, the blatant and rampant render errors, and the lack of planning in the media system. None of this should be my problem, ever.