Do you have any third-party effect plug-ins used in the project that aren't installed on that machine? I've seen this problem in two cases before, and in both cases it was because there was a missing third-party plug-in used in the project that was not installed on the current machine.
Also, please give much more information when asking questions. At the bare minimum, tell us exactly which version of After Effects and which operating system you're using.
Hi, I've had a similar issue. I literally just updated to 10.0.1 on my Mac Pro and the message has come up ever since.
I'm also suffering from a separate issue where neither of my two Mac Pro computers running Leopard will render more then 2GB of a file. I was hoping the latest update would fix it. But I can't test that due to this new issue.
Any help on either issue would be great.
Please answer the questions that I asked the original poster.
Regarding the inability to render and export a file greater than 2GB: Are you creating a QuickTime movie? Over a network? Please give more details.
Hi, sorry I'll give a few more details. I'm not sure her Jersmi is though.
In regards to the "unexpected data type" issue:
Yes there is a 3rd Party plugin not installed on the Mac Pro in the project I'm using. But the plugin is not used on the comp I want to render and also I wasn't getting this message before I upgraded to 10.0.1.
I'm in AE CS5 on a Quad Core Mac Pro running 10.6.4 (Sorry I thought I was Leopard before).
In regards to the 2GB render issue:
Yes, I'm rendering over a network.
I'm rendering a Quicktime file with the Animation codec.
Project file is HD in size, but I've tried rendering at smaller screen widths and everything will be fine unless the comp I render breaks the 2GB barrier.
Not sure what other information to give you on this one. But I can tell you defnitely that the 2GB issue occurs across two machines (1 Leopard, 1 Snow Leopard. I haven't updated the Leopard computer to 10.0.1 yet, as if I lose the ability to render from both computers I'm totally screwed.).
Hope this helps.
> I'm not sure her Jersmi is though.
Oops. That's what happens when I'm answering several questions in a row. Sorry.
Regarding the 2GB issue: This is a known problem with After Effects CS5. Actually, it's a known problem with the QuickTime Compression Session API that Apple asked us to use for this version. We found out (too late) that this API has a limitation when rendering over a network. The workarounds are a) render and export using a different format---anything but QuickTime--- or b) render and export locally, not over the network. We have a bug report in to Apple about this and are looking into what we can do on our side. Sorry for the inconvenience.
Regarding the "Unexpected data type" issue:
Would you mind sending the project (or a reduced version that exhibits the problem) to aebugs -at- adobe -dot- com ? (I'm the human on the other end of that email address.) We've seen two cases of this issue so far, and they were both caused by a poorly behaved third-party plug-in that was missing on the machine on which the project was opened. Granted, After Effects shouldn't freak out like this even if there's a problem with the plug-in.
Thanks for the info. I had no idea about the 2GB limit.
Rendering directly to the desktop has done the trick. My 7GB file rendered fine. I'm glad I asked. Thanks a lot for the solve.
In terms of the unexpected data issue I'll see how I go. I don't have time to send a project file over currently. But I will definitely need to sort it. So I'll try and send you something next week some time.
Sorry for the delay and lack of info.
No third party plug-ins used on any of the machines. All are on CS5 7.0.2. Mac in question is running 10.6.4. 8 core 2.93Ghz. 8GB of ram.
Hope that helps,
> All are on CS5 7.0.2.
That number doesn't make any sense to me. If it's After Effects CS5, it's either 10.0.0 or 10.0.1.
Please send a project that demonstrates the problem to aebugs -at- adobe -dot- com.
The "Unexpected data type" error is occurring because you are opening a project that contains a third-party plug-in on a computer on which that plug-in isn't installed. To get past this error, install the plug-ins used in this project. If you don't have the plug-ins, you can get past this error by doing the following:
1) Press Caps Lock before starting After Effects (to prevent After Effects from trying to render anything).
2) Search for missing effects in each composition. (Paul Tuersley provides a script on the AE Enhancers forum with which you can search compositions for effects and turn them on or off.)
3) Reset or remove _each_ instance of the missing effect.
4) Save a version of the project.
5) Quit After Effects.
6) Open the newly saved version.
This should get you past the "Unexpected data type" error.
never had this problem but nice work Todd
As I mentioned previously, there are no third party plug-ins installed. I have 3 identical machines, and only this one gives the "unexpected data type error" from the same set of files. One day it worked fine, the next I got the error that I can't get past. As there are no missing effects to replace or remove, the caps lock trick is of no use in this case. I've reinstalled Aftereffects, Permission checked the system and tried unlinking and re-linking all the itmes in the library. All with no effect.
> As I mentioned previously, there are no third party plug-ins installed.
The issue isn't that third-party effects are installed. The issue is that some third-party effects used in the project are _not_ installed. The problem that we have seen is that a project that should open with no problems other than some of the effects being "missing" instead opens with these error messages.
If you're 100% certain that the project that you're opening doesn't use any third-party effects, but you're still getting this error, then we'd really like to see that project so that we can use it to isolate and fix this bug. The email address for sending bug reports with attachments is aebugs -at- adobe -dot- com.
Sorry, maybe I was unclear. I'am 100% sure that there are no third-party extensions _used_. This is not a project that we've gotten externally and then had problems with. I created this project myself, on this same machine. It's then been passed around internally to 2 other machines for small changes along the way. Suddenly within the last week, though I can open and work on it fine on 2 of the 3 machines, the machine that I created and worked on the project originally has started giving me this error. All 3 of the machines are setup identically to avoid issues like this.
There are definitely no third party plugins installed and/or used on any of the other machines, and as I setup the original project myself I can be certain that I used no 3rd party plugins in the creation of it. Also, i've gone through the timeline and library quite thoroughly on a machine that I can open the file on and it's clean.
Thanks for your effort on this, I appreciate your suggestions. In terms of sending a test file your way, it's probably not possible as the job is of a corporate nature and has NDA's involved.
Since I can open the project on other machines, it's not a game-stopper, just a frustrating experience when I can't seem to find the issue and resolve it so I can avoid future similar situations.
Just an FYI, I was having this problem with a project this morning. The two "machines" in question are two partitions of Leopard and Snow Leopard on the same machine. I have to boot into Leopard from time to time to use Director MX2004. The problem occurred when opening the project in Snow Leopard after having opened it in Leopard. I do have 3rd party plugins installed, but I don't think any are used in this project. I actually have more of them installed on the Snow Leopard partition than the leopard one. I tried Todd's suggestion of starting AE with Caps Lock on, and that opened the file for me. Just in case I checked for use of plugins but couldn't find any. I saved it as a new project. Quit, opened it again, no problems. The file that was causing the crash is unchanged, but once I got it to open using Caps Lock, it no longer gives the error. Things seem ok, but it was a scare. My time machine isn't backing up while I'm in leopard, and I thought I had lost a couple days of work.
Thanks, Matt. I've given a link to this thread to the software engineers and testers who are working on a fix for this issue.
Paul Tuersley provides a script on the AE Enhancers forum with which you can search compositions for effects and turn them on or off.
For anyone encountering this error and using the workaround that I described above, this script might be useful.
"Unexpected data type" is a major issue that should be repaired. CS4 doesn't have this, it's a unique CS5 feature.
It is almost impossible to remove missing plugins due to the pesky error message.
Turning of missing effects does not help.
If anyone else is hitting this issue, please respond to this forum thread and let us know whether the workaround is working for you.
I've also run into this problem. The work arounds have not yet actually worked around this problem. The project will not launch if cap lock is engaged. If I launch in the usual manner I can't get beyond the error.
This is a project I've inherited from unknown source. I'm sure there may be some third parties involved, but as previously mentioned, can't get in to turn them off.
This does not work.
You must use the older AE version to remove the reference to any missing third party plugin.
Caps Lock does not prevent the error message from appearing all the time.
Just have the useless error message removed in the next update; that will help.
The error message prevents the user from operating the user interface.
The very nice script unfortunately can't delete plugin references; if it could, it would be great.
Turning of the missing effects does not help a bit; the project remains unstable in AE CS5.
I came across your post via Google. Registered on the forum and all.
I switched jobs and now that I'm trying to finish off a freelance project, the AE file
won't open on this new mac Machine. Running AE CS5 still.
But my old machine had Video CoPilots optical flares, while this one doesn't.
Is there a way to over ride that... and still open the file.
many thanks if you can help with this.
I'd hate to have to build the project from scratch
Did you ever figure out a work around for this.
I'm in the same boat... and would hate to have to rebuild from scratch
Is the workaround that I described in post #10 on this thread not working for you?
Like the other posts mentioned, that script is not useful for this.
You can only access that script if the project is already opened, and it
never opens. In fact you have to force quit After Effects... As it's locked
On this Unexpected Data Type window pane... No matter how many clicks, it
won't go away.
I'm on AE cs5, mac osx 10.6.5
Thanks if you can....
I'm really hoping there is a patch or update I can apply.
Stefan, I held the return button for several minutes, as that means OK or Yes in the PC world. It made the error go away just long enough to start deleting EVERY instance of the non existing plugin. Like I said, turning the plugin off, does nothing; full removal is needed. I did manage to get the script running and I used it to track down the whereabouts of every instance of the evil plugin.
If only Adobe would read the forum and just remove the stupid error message, but no. I used to file bug reports but I NEVER found a bug fixed I reported within a year, so I'm done with that. How hard can it be to remove a line of code and issue an update? Yech...
I'll give it a shot.. On a Mac here.. Fingers crossed.
Yeah - that one ae_script is nice, but only if you can open the project first!
> How hard can it be to remove a line of code and issue an update?
Making changes in code is easy.
Testing the application thoroughly before releasing the change---to ensure that we're not introducing yet another bug---is much, much harder.
If you're interested in helping to test the prerelease version of the fix, send me your contact information. My email address is kopriva -at- adobe -dot- com.
> If only Adobe would read the forum...
I don't understand this statement.
I think that it's pretty clear that we do read the forum.
I'm into it...
Sign me up!
Because this bug was introduced in the After Effects CS5 (10.0.1) update, you could do this:
1. Uninstall After Effects CS5.
2. Reinstall After Effects CS5. Don't install the update.
3. Open the project and remove the instances of the effect that relies on the plug-in that you don't have installed.
4. Save the project.
5. Close After Effects.
6. Install the update.
7. Open the project.
The update has a huge number of bug fixes and major improvements. And it has this ghastly bug. I do recommend installing the update, but temporarily going back to 10.0.0 to rescue a specific project may be the best solution in some cases.
Now you're talking. Read problems, try a fix at once and have us test it a.s.a.p.
You can play with fixes in the lab but you'll never find the next real problem real work invokes.
I've been working with Adobe products since PS V3. To me that is the only application that works flawless these days.
All other aps have severe quircks. Those have caused a negative energy build up over the decades, yes.
Try losing work due to crashes, try losing time due to quircks, try reading in the manual that functions you need do exist but it doesn't tell you where they are at exactly and then have Adobe tell you to go take some lessons because of that, try help files that open internet and display outdated non help, try interfaces that suddenly are less handy after an update, learn to love the removal of functions after an upgrade, live with hardware which you can't do without but which also messes up Adobe apps (see several companies blaming eachother), try buying $30.000 worth of machinery and tell your boss the stuff can't print to tape or batch capture anymore because apparently that's old school. I am so glad Matrox, Nvidia and Adobe do not build or repair airplanes together. There is nothing besides Adobe if you have to do desktop publishing, editing, compositing, audio mixing and internet coding in one office. So sometimes I really need to try and wake up some people. Sorry if that seems a tad aggressive and I appologise in thousandfold. Just don't forget to get them coders to fix things faster.
Sorry. Restarting AE did the trick.
I'm seeing this error for the first time today.
I'm not using any third-party plug-ins in the project. It is a very simple 10 second animation and all I use is "Scale" and "Opacity" and perhaps the crossfades are scripted. I can't recall for certain.
The project file fails to open. I just get the "Unexpected data type" error popup and when I click OK AE just closes the project.
The Project library loads right before I get the error.
When we upgraded to CS5 , several plug-ins were dropped for the sake
of economy and thus 'orphaned".
AE will not open tried using CAPS LOCK...no joy.
MAC OS 10.6.2
2X2.8 GHZ Quad-Core Intel Xeon
12 GB 800M MHz
Todd, is there anything new on this subject?
If the Caps Lock trick isn't working for you:
If you open the project using a computer running After Effects CS5 10.0.0 (not 10.0.1) and then remove all references to the missing effect plug-ins, then resave the project (or save a copy), then you can open that in After Effects CS5 10.0.1.
We are very actively working on getting a fix for this out. That requires rebuilding and retesting everything, so it's not fast. But we are going as fast as we can. Stay tuned.
The caps lock workaround did work for me. I was able to open my project and save it as a copy. However, I am still experiencing multiple crashes with this project. I do have the 3rd party plug in installed in CS5. So for me, I think the workaround definitely got me out of a tough situation, but I don't think the problem is fixed. Thanks for looking into this for us.
Caps Lock a no go for me either. Received a project from a client. It says on open the project uses Reel Smart Motion blur and VideoCopilot Optical flares, Colorista (“RSMB”, “Optical Flares”, “RSMB Pro Vectors”, “Colorista”). I don't have any of these plug-ins.
Running latest everything...
MacOS X 10.6.6
AE CS5 10.0.1
HOWEVER - I DID FIND SUCCESS GETTING THE PROJECT OPEN!
I imported the project into an empty Untitled Project and it all came in. I had Caps Lock enabled if that mattered, no Comp was loaded as open with this method. Poking around a bit, looks like I can open all comps with Caps Lock. Not sure if deleting all filters will solve the "Unexpected data type" issue but I would bet it would. Looks like Optical Flares seems to be the plug-in killing my project. It is sure a pretty plugin. If I open a Comp in the project that has the filter without caps lock, I have to hit OK only 1-time for each filter instance, not 100+!
The real work around is to use the script above to remove 3rd party plugins then save and shut down AE. When you re-open the project, it should work like it did for me. I had a bunch of plug-in references to delete.
Thanks for the update on what worked for you, Brian.
We're currently testing a fix for this issue. We need to be certain that any fix doesn't introduce other problems, so this takes some time, but we're going as fast as we can.
Thanks to everyone for your patience and your feedback.