I have made a slideshow with pictures that is ONLY 3 minutes long. It has one song added to it. In Adobe Photoshop elements I can save it with no problem. However, in Premiere I have tried saving it to Youtube, saving it as a windows media file, saving it as mpeg and basically every option on there. It runs for several minutes and looks like it is going to be okay and then at the end it hangs up and says something to the fact of ''unable to return frame, aborting process''. Then when I click okay it doesn't send me out of the program it just stops trying to export the file. When I go to ''my videos'' you can see the file I have attempted to export or when you go to youtube as well. But, nothing is in there! I have a dell latitude d820 with high speed internet. anything else runs find on here. I have had my computer all cleaned up and everything else runs extremely fast on this computer. This programs is pretty slow, but other than exporting it so far I have been able to use it fairly well. It is rather frustrating though to create a slideshow and then not be able to do anything with it. A waste of my money if you ask me. I am running Microsoft Windowns XP Pro Service Pack 3. I have 2.00 GHz, 1.0 GB Ram. I don't know what else anyone will need to know to help me, but I can look for it if you show me.
Should I be having problems with this? I have even tried shutting ALL other programs down while doing this so that Premiere is the only thing running to save memory, etc.
Can someone please help me? I got this program to replace Nero because I heard it was much better and so far I am not having any luck.
Error everytime I export in Premiere...
You should have no problems doing this if you have optimized your photo sizes to 1000x750 pixels, per the FAQs at the top of this forum.
http://www.adobeforums.com/webx/.3bb8822c
If you do this the whole process should take about 5 minutes tops.
(Assuming that you keep your computer up to date and well maintained:
http://www.adobeforums.com/webx/.3bc43f9a )
Error everytime I export in Premiere...
Very good suggestion and I didn't resize my photos. These photos all came from a Nikon D40 so I imagine they are huge files. Once the video is already in Premiere can I resize them then? Or do I have to do it the way you mentioned in Photoshop?
Thanks so much for your help!!!!
Just thought I'd mention that Faststone's Photo Resizer is an option for resizing photos, too.
You can resize one file or entire directories, save your image to the same or new directory in various formats, and also save your settings to a file (e.g. ''Premiere Resizing'') for later use.
Somewhat non-intuitively, you need to use ''Advanced Options'' to resize, but you can specify any standard size, ''longest side'', etc.
It's a free product (www.faststone.org - note the .org suffix, not .com) and a quick 1.4MB download.
Marcy,
When you do re-size the photos, I'd also check closely to make sure that you do not have any gaps in your Timeline. If you are editing in Scenline, switch over to Timeline and Zoom in so you can see single frames. Step through your slideshow, looking for any gaps. Usually, ''Failed to return frame'' will happen if there is so little as a one-frame gap.
Also, the Rendering of your Project is completely dependent on your CPU. with a 2.0GHz CPU it will take some time. Also, the CODEC to compress the files, say WMV 9, will require even more time, as will any Effects that might have been added. This is pretty much life with any NLE. Even my dual quad-core workstation takes some time to Render.
One last suggestion, when you go to Export and Render, you might want to make sure that your AV, pop-up and spyware programs are shut down. They take quite a few CPU cycles and can bog down the process.
I'll bet that one, or both, of Steve's links will address this, plus more.
Good luck,
Hunt
[Edit] Just reread your post and it appears that you constructed your slideshow in PSE. That should NOT leave any gaps, so my warning about them might well be moot. Still, it never hurts to check the Timeline in PE, just to make sure, since that is a main cause of the error that you got.
Subscribe to:
Post Comments
(Atom)
No comments:
Post a Comment