Robert Headrick
Forum Replies Created
-
That works if all I need is to get the file into .SWF format, but defeats the purpose of creating a .SWF in the first place since the file size ends up being enormous. I’m working on a 12-second animation that needs to be cut down to under 200K in the final deliverable, and that can only happen if all of the vector art stays vector.
I ended up having success with saving the project as a CS5.5 file and opening it in that version, which apparently doesn’t suffer from the same bug that CS6 does. It’s annoying, but it works.
-
Looks like it’s due to the CS6 bug you mentioned. I back-saved the file to CS5.5, opened it up, and exported with zero problems at all. Redid all my tests just to make sure, and nothing tripped it up! Seems like a pretty glaring error; I googled around a bit and found a thread with people talking about it way back in August when Adobe had already acknowledged the bug and were supposedly working on a fix. I’m fine just using 5.5 for this particular project, but that’s only because I have both versions. The average user just working off of CS6 would be completely out of luck.
-
Another thing you can do is just set the render up to run overnight or some other time when you’re not going to be using the computer. Just start it sometime in the evening, and it’s ready for you in the morning when you get up.
-
I imagine its the 7 CC Particle explosions that are racking up the render times. If your particle systems have even a little bit of complexity to them, and there are seven of them, and they’re emitting particles for 5 minutes, then I wouldn’t be too surprised to see a 10 hour ETA on an average system. Unless you’re working on a high-end workstation machine with a lot of processing power, that sounds pretty normal.
-
I am having this same issue and also found that threat from Red Giant recommending the Render & Replace workaround. I tried it though, and I still get the error from PluralEyes saying that the files are not supported. Did I miss a step?
-
Found the solution… it has nothing to do with the script, which was written correctly. I was operating with the ExtendScript Toolkit rather than the After Effects CS6 library, so it just didn’t have the correct set of functions and methods available to pull from. As I suspected, stupid mistake.
-
One thing that might help you would be to use multiple viewer windows. You can have your main window be the nested composition that you’re currently working in, then go to View –> New Viewer. Choose one of the viewers and set it to your master comp that includes background, other characters, scenery, etc, and toggle the viewer lock so that that particular window stays locked on that comp. Then just make sure that your other viewer is left unlocked, and you can now switch between various precomped layers and edit them in one viewer, while your other viewer will always show you your finished, master comp.
-
Have you ruled out the possibility of it being specific to the footage you’re using? Here’s what I would try next:
1. Create a new project with the same settings that are being used on your current project.
2. Import a portion of the clips you’re using in your current project into the new project.
3. In your current project, attempt to send a specific set of clips to an AE composition and confirm the problem still exists.
4. In your new project, create a sequence with the same settings and create an identical section on that timeline.
5. Attempt to send the exact same set of clips to an AE composition using your new project and new sequence and see if the same thing happens. -
Glad you got the problem solved, if not completely figured out! Now I’ll probably be stuck poking around the settings for the next couple of days trying to find where it was changed. If you do happen to stumble across the setting, you should post the information back here for other people who might come across the issue.
-
Very strange. I still can’t duplicate the issue. You’re on a PC, and I’m using the Mac version. It’s possible there’s a difference in the way the PC version handles dynamic link, but I’m not sure. Someone else who uses Premiere Pro and AE on a PC would need to chime in and confirm that. I just can’t get it to do the same thing that you’re describing.