Premiere Elements 11 consuming obscene amounts of RAM

Swear, I've forgotten where the search bar is around here . . . I'd be surprised if there wasn't already a thread about this.
This has been sort of a problem since I started using PrEl 11 two summers ago, but for some odd reason it's been becoming more and more of a problem (same computer, decent machine, I'll post the specs if you want them but I doubt my specs are the problem). Project settings are 1920x1080@30, as they have been for . . . eh, a really long time.
Picture of my Task manager, about 4.5 GB of this is going to Premiere: http://i.imgur.com/BRVNtOJ.png
Picture of it going up and down for no apparent reason: http://i.imgur.com/PXJvXPw.png
Picture of my timeline, nothing too fancy: http://i.imgur.com/tdjiIrF.png The only resources in the project ***** bin are what's on the timeline and a few miscellaneous graphics and things.
On a typical day it'll do this every 5-10 minutes and lock my computer up so that I can't even move my mouse for another 5-10 minutes, meaning I have to go find something offline to do while I'm waiting for it to do . . . um, whatever it's doing. It's quite annoying. I know there has to be a solution because loads of other people still use PrEl 11, what's the best one?
Kogaan.

>video made up of still images
Photo Scaling for Video http://forums.adobe.com/thread/450798
-Too Large May = Crash http://forums.adobe.com/thread/879967
-And another crash report http://forums.adobe.com/thread/973935

Similar Messages

  • HP 6100 printing problem: process pdftopdf consumes huge amounts of RAM

    I did some remote troubleshooting for my uncle's Mac yesterday who had a problem with his MacBookPro. It occured to him last week after trying to print a document with his HP 6100.
    When I tried to check the problem, the system UI took at least 15 seconds to register a user action. The Activity Monitor showed that the process pdftopdf consumed more than 2 gb of RAM and continued to do so after a restart. The system was practically unusable. As a temporary solution, I killed to process manually and deinstalled the printer drivers. I did not reinstall the drivers in order to avoid the same problem over and over again.
    It was a machine that came originally with Snow Leopard (so no upgraded system from Leopard), which was system-wide up-to date.
    Is there any "official" solution regarding this issue that seems to be known for a whole year (see e.g.: http://discussions.apple.com/thread.jspa?messageID=11004321)? In that thread someone suggested that the problem might be related to CUPS. So is it up to Apple or to HP to fix it?
    Please help, thx.

    Hello Scheepster, I have ProBook 4340s and I'm having trouble with suspend to ram. When my laptop wakes from suspend it fully hangs after some time. Sometime is 2-3 seconds later and sometime is 20-30 minutes later. I think this two models (4340s and 4540s) are not very different, so would you tell me do you experiencing SUSPEND problems.

  • Switching from Premiere Elements to FCE

    Greetings ...
    I'll very likely be switching over to an iMac soon. As I do a fair amount of video editing, I'm looking at FCE.
    I've been using Adobe's Premiere Elements (the consumer version of Premiere) for a number of years and was just wondering if anyone else had made the switch and could compare the two apps. Anything I should be aware of?
    Also, I'm assuming that FCE will run well on the 3.06 Ghz iMac (24-inch) with 4GB RAM and ATI Radeon 4850 ... correct?
    Thanks in advance!
    --Jason

    FCE 4 will run perfectly on your iMac.
    I moved from Premiere 6.5 to FCE four years ago without much difficulty but I don't know how similar or otherwise "Elements" is.
    In any case you should reckon on spending a week or so getting used to the program and +not starting straight off on an important project.+

  • Premiere Elements 10 slow GUI refresh

    Hi all,
    I am experiencing a very slow GUI refresh rate using Premiere Elements 10. It has been happening since I first started using the program, but I am using it a bit more now and it's starting to frustrate me.
    Basically, as soon as I open the program and create a new project, any action which changes the screen e.g. maximising, resizing the timeline, changing the timeline scale etc. occurs very slowly. For example, maximising the window takes approximately 4 seconds to complete, and resizing the timeline is very laggy.
    It is shown reasonably well in the following clip, although it is much more pronounced for me: http://www.youtube.com/watch?v=8C7GbqXir8o&feature=youtu.be
    This issue has been discussed in a few other questions, but none resolved the issue (that I have found) or have kind of gone off topic, so thought I would ask myself in an effort to resolve it.
    A couple of points to note:
    Occurs WITHOUT any video loaded i.e. with a completely empty project. (Loading video doesn't have any effect)
    It is not affected by the selected preset. They all have the same issue.
    Somewhat curiously, playback of video is fine.
    Disabling desktop composition as suggested in another post on this issue results in a slight improvement, but certainly does not make it go away.
    Computer specs:
    Windows 7 Pro x64 SP1 (I am using the 64 bit version of premiere elements)
    Core i5 2500
    8 Gb RAM
    EVGA GTX 460 1Gb
    Asus Z77 sabretooth motherboard
    Primary drive 2x 64Gb SSD's RAID 1 (OS and performance sensitive applications incl. Premier Elements)
    Secondary drive 2x 1Tb HDD's RAID 1 (Other applications & data storage)
    Note that the drive configuration and motherboard have been changed recently, and had no effect on this issue.
    Thanks in advance for any help.

    Thanks everyone for the responses, I really appreciate your assistance and thoughts.
    Here goes with how I have got on with your suggestions/answers to your questions:
    Steve:
    First of all let me just make it clear that this is occurring with nothing loaded - a completely blank project. Also, it would appear that it is a window refresh issue rather than program performance as such, as rendering/playback work just fine. This is just my initial impression though.
    Footage is  from a GoPro HD Hero 2, recorded in 720p at 60 fps (actually 59.94). I convert it to .avi using the GoPro Cineform software prior to editing. I use the DSLR 720p 60 preset. I have also tried the 720p60 AVCHD LITE preset which does not have any noticeable effect on the issue. I have tried using unconverted footage straight from the camera; again this has no noticeable effect on the issue. When I add video to the timeline, there is no red line above it  - although when I apply an effect e.g. brightness and contrast one does appear.
    I have never used still images so I don't know if they have any effect.
    I checked just now for OS updates and and a few (11 if I recall correctly) which I installed. They had no effect on the issue.
    I have also just updated to the latest graphics driver (320.49) and quicktime (7.7.4), again no effect on the issue.
    The RAID 1 setup is a data mirroring configuration - each drive is an exact mirror of the other. I have this  as I have had a few HDD's fail and having to get a new one, reinstall, etc. is just a nightmare - not worth it when the risk can be effectively eliminated for a bit extra $. I do not think this is the cause as I have had a few different configurations while using premiere elements (the SSD's are quite recent) and the issue stays the same.
    John:
    Thanks for the links, although I wasn't able to find anything that helped with the issue.
    I will have a look for what you mentioned re an older driver being potentially better, and will try it when if I find one that looks promising and I get some time. I am not overly hopeful though as I have used several different drivers, and I have not noticed any difference.
    Bill:
    I completely agree - I always go to the source for drivers rather than relying on driver update programs etc.
    ATR:
    Firstly I would just like to point out that the link was not my video - it is someone else's, who appears to be a somewhat similar issue. Apologies, I should have made that clear in the original post.
    What is really bugging me is adjusting the 'zoom' on the timeline (little bar on the right of the screen you drag left & right). When I move it, it will take a few seconds for everything on the screen to refresh. Not a massive issue, but really annoying!
    In response to your points though;
    I was not aware that the timeline scrollbar ghost trails are common to other versions. Is this a common issue or just some isolated instances of it? I have personally not noticed any bits of clips remaining on the timeline.
    I must confess I am a bit of a novice with this program, so would you be able to expand on what playback quality & playback settings I should be looking at? (Note that the playback itself is not an issue for me). Also, how might I go about checking for pile ups of preview/conformed audio/conformed video? If it helps I have all the scratch files in a dedicated folder on the SSD.
    I have just defragmented, but it had no noticeable effect.
    I would rather not use a registry cleaner (had some bad experiences in the past and not convinced they make a difference), and my computer is relatively clean. I do a complete fresh reinstall every 6 months or so and I am not in the habit of downloading all sorts of crap.

  • Premiere Elements 10 Bad/No performance on Win 8 64-bit Core i5-4440 16gig ram and GeForce GTX-650

    Since just over a year i'm the owner of Premiere Elements 10, however it has never pleased me due to bad and inconsistant performance. Just putting video's one after another without any transitions works so-so a few frames per second (which is rediculus). But when i start doing things like motion keyframes, i have no preview at all just a bit of choppy audio. First i thought it was my laptop (a win 7 64-bit core i7 3rd gen, with geforce 610m and 8gig of ram) not bad but i thought well it is a laptop so it might be a bit slower, i'll have to deal with it. However since a few months i own a new PC (specs above), and experience the very same issue. No performance! Every time i think about editing a video i start the program and within a few minutes i get so angry with it that i close it and leave the video's be.
    Pre-Rendering the workspace also has no effect at all. I have no red bar above the timeline (sometimes even green).
    And worst of all it keeps messing up the timing of the video while editing. If you change a clip in the timeline all clips following (the motion edits) are destroyed. Which is only visible after a few hours of rendering, since live preview is only audio.
    What in the world can be done to fix this problem. As you probably can read i'm pretty annoyed.
    The free video editing software that comes with the gopro moves rotates and scales smoothly in live playback, so it is not impossible on the machine. (too bad the functionality of this program is so limited, else i could finally throw Premiere Elements away!).
    Is there anybody who can help me in my despair?

    nVidia Driver Rollback PreElements-10 http://forums.adobe.com/thread/1317675 may help

  • Aspect ratio problem with consumer camera and Premiere Elements 11

    Hello everyone - I'm Steve. I'm new here. I do still photography on a pro level, digital and analog, but I am an absolute dummy with video...but then, I don't want to do much, just rudimentarily cut a few family videos, upload them, etc.
    However, I can't get Premiere Elements 11 to output my self-shot clips in a correct aspect ratio.
    My camera is a consumer-model Canon Legria FS200. I shoot video in a resolution the camera calls XP. The camera says they are 16:9, the camera monitor shows them as 16:9, and when I use the software (called Pixela Image Mixer) that came with the camera to import the clips to disk, I get mpg files that Windows (7) Explorer says are 720x576 pixel, and that VLC player correctly displays as wide-screen 16:9 without me having to tweak its display settings.
    However, the moment I import them into Premiere Elements, they appear horizontally squeezed, and I can't seem to output them any other way, with or even without editing them in Premiere. 
    I tried to use the recipe given here: https://forums.adobe.com/message/5987538#5987538 , (replacing only NTSC with PAL because I'm in Germany),  namely, setting the project preset set manually for PAL/Hard Disk etc/ Widescreen 48kHz and check force selected program settings. But no matter, Premiere displays the video in horizontally compressed form, with large black bars to the right and to the left.
    On the export side, setting the output to PAL DVD Widescreen and setting the Pixel Aspect Ratio in the output settings to Widescreen does not help, either. Neither can I force VLC player manually to display the correct aspect ratio. BTW, audio is perfect all along.
    This is about as far as I can see myself getting without help. Has anyone any idea?
    Thanks a lot in advance,
         Steve, from Germany

    Steve
    I see that you are now in the Adobe Premiere Elements Forum with your problem already solved.
    I did not see any Why for what you encountered, so I thought I would give you my take on this.
    Your Canon FS200 gives video with MPEG2 video compression with a .mod file extension. That .mod file extension can be found in use with some Canon as well as JVC cameras. The .mod file history with Premiere Elements (any version) is problematic. In some instances, the user needs to rename the file extension from .mod to .mpg before it can be imported, but not always. But, the .mod widescreen comes packaged with the aspect ratio dilemma, presenting as 4:3 rather than 16:9. The classical argument is whether Premiere Elements does not recognize a .mod file's 16:9 flag or whether the 16:9 flag got lost.
    There used to be a utility contributed by an user to handle the file extension and/or aspect ratio issues. Now, the general fix is to import the file into Premiere Elements (in your case 11) with Add Media/Files and Folder/Project Assets. And in Project Assets, you right click the file, select Interpret Footage, and go to the Pixel Aspect Ratio section of the Interpret Footage dialog where you
    (a) dot the Conform To:
    and
    (a) set the Contorm To: field to (in your case) D1/DV PAL Widescreen 16:9 (1.4587)
    Once you are in the program and have the file on the Timeline, if any black edges, you can click the monitor to bring up the image's bounding box. Then drag on a bounding box handle to scale the image just to the point where the black edges are gone.
    If you ever need the Adobe Premiere Elements Forum, maybe bookmark this link
    Premiere Elements
    You should expect to have this issue with any .mod widescreen file that you obtain from your Canon FS200 camera.
    ATR
    Add On...If you are depending on the program to set the correct project preset, you may want to check into what it is setting based on the properties the first file you drag to the Timeline. A manual setting of the project preset may be in order. Please see
    ATR Premiere Elements Troubleshooting: PE11: Accuracy of Automatic Project Preset (New Project Dialog) Setting

  • Premiere Elements 8 doesn't take advantage of all my RAM

    Hi, I'm running Premiere Elements 8 on a Windows 7 machine with 8 GB of RAM. Elements usually runs fine when editing standard-definition video, but slows down badly with HD. But when I check the system processes, I see that Elements never uses more than 1 GB of RAM--even when it's really working hard. It's like there's some setting that is keeping it from using any more than that. How can I force Elements to take advantage of the rest of my available memory?
    Thanks.

    That would be right, Gavin. Premiere Elements is a 32-bit app and will only use, at most, about 2 gig of RAM.

  • What do i do with a very slow Photoshop Elements and Premiere Elements on a PC?

    I seem to be getting mixed opinions as to why my Adobe software gets so slow, despite efforts to avoid that, but my computer seems to be working just fine, it is only when in Adobe that the problems arise, like freezing, taking longer and longer periods of time to open the screen to edit a photo, or to compare two photos side by side.  Any process seems to take such a long time, and the freezing can last for several minutes, and then continue on.    I have had a computer person come to my house and examine my computer and though his knowledge of Photoshop is limited, he feels that it is NOT the computer but something with Adobe Photoshop.  I would tend to agree with him.   
    Several theories have been explained to me, such as Elements and Premiere Elements are a low end of the scale of Photoshop programs, so it is just not going to be able to process high definition large photos well and quickly.  Stating comments like i can only use 2 GB of my memory even though i have 8 GB, so unless i can use 64 bit this is what i have to deal with, and it is just a way for Photoshop to say you need to upgrade to the fancier programs.  I do not need fancier programs.  I am working hard to master these, and have accomplished 4 great blu rays in high definition thanks to recommendations from the Forum here, especially Steve with the help of his books. 
    Others say i need a solid state hard drive to solve the problem.  Others say the only way i will ever solve the problem is to switch to a MAC.  Others state is a mal-ware problem, but i have never had my hard drive so clean and uncluttered.  I supposedly have as good of PC as i could have as far as QUAD-core, 8GB memory, presently a 1 TB hard drive less than 1/2 full.   All suggestions involve big outlays of money, with no guarantee that things will be any better.  I have tried to contact different computer companies and computer 'nerds', and these are some of the suggestions, but no one really has a lot of knowledge of the Photoshop software. 
    I am thinking of adding an additional internal hard drive, but not sure that is going to help either.  Could i put all my Photoshop of the second hard drive, and might that speed things up? 
    Adobe is rather worthless in trying to get help from them.  I have spent hours on the phone waiting and then talking to someone who says they understand English but they do NOT understand the question i am asking, which becomes very frustrating with repeat phone calls.  I gave up yesterday trying to do that challenging experience yesterday after i had spent 3 times the amount of time they said i would need to wait to get a reply, and i was at work, and my free time had come to an end.  So i am hoping you guys can give me some clues of the best thing to do.
    Is it true that Photoshop Elements and Premiere Elements are just such a lower end program that trying to do things in high definition, with 2000x1500 photos, making them into a blu ray disc is a major challenge with a PC?  I wish i had a greater computer knowledge, but i have struggled to achieve my goal, but the speed of it all gets very frustrating, though it is possible. 
    Another question asked which i don't think exists, is whether there is a program that could clean up Photoshop, or are there some clues that could accomplish that and thereby speed things up.
    Would appreciate any suggestions anyone has.  I am in the middle of another project so now is probably not the best time to consider any major changes.  But any comments would be appreciated.
    Ron

      Premiere Elements 10 is now 64 bit, but not PSE10.
    Take a look at your scratch disk set-up and if you have a spare volume, allocate that first before the C drive. Elements use scratch disks when it gets low on RAM.
    Click image to enlarge
    Turn off face recognition and the auto-analyzer to improve performance.
    When editing photos or videos check the task manager to see what background processes may be running and end them temporarily if not needed.

  • Adobe Premiere Elements 0.9 project crash, HELP!

    This is the first time I am using these forums, so I hope I posted this in the right sektions.
    I need help and solutions for a Project which constantly crashes on my Adobe Premiere Elements 0.9. This program has been awesome and helped me create some projects and videos successfully, up until.... well for about 3 days ago when my latest project crashed when I had just antered and checking the storyboard etc, triggering a "Serious Error" message and then it shuts down. I try again and again, but everytime I try to put something (any sound or video etc) on the storyboard and start working etc the same damn "Serious Error" message and then allways shuts down. It's allways this same and only project (which has worked fine before) that crashes like this...
    In an attempt to first solve the problem myself I went through the Premiere Elements 9 files and deleted finnished projects and automatic saved process on projects etc, but still won't work even better... The funny thing is that when I open another project (a finnished project I left saved just in case) and go through the storyboard there and messes around a little and such, it won't crash nor trigger the same message as my latest project. And that program even has some effects on every footageclip on it too, but still it works fine. Haven't touched the program or the program until and since yesterday night to give it some rest but it still won't work, the project just keeps crashing like when and since it first started a few days ago.
    I have also read through and tried some things from this Help/Troubleshoot page:
    http://helpx.adobe.com/premiere-elements/kb/troubleshoot-damaged-projects-premiere-element s.html
    I have so far been doing 1 and 2 of the "Beginning Troubleshooting", otherwise I have been reading it all and such. I am also kinda afraid to do the 3 of the first quests because I worked so hard on this project and even tough it just keeps crushing, I'm afraid to lose it. Other, I have deleted audios and such from my filegallery on my Adobe Premiere Eements, stuff I don't need anymore because its projects are already done. After I did that I also tried to create a new project just for testing. The amazing this about this is that this the new created project I created works just fine, I could do all kinds of the stuff, effects and advanced editing which I did on the same project before it started crushing. Tough I didn't save that test-project since I didn't find a reason to since it worked so good. And so the thing is that I can start and create a new project and start working and do usual stuff on it with no problem, same when I open up another project and do stuff, it all works just fine! It is just this one and only project that keeps crushing with this "Serious Error" message, all the time... Does anybody else have, or has had the same problem? What could the problem and error be and how to fix it?
    This crushing project do has some effects on every footageclip/videoclip on it, to set the right mood for the musicvideo I'm making. I am making a musicvideo, and I haven't even done the half of the project/video. The song I am making this musicvideo with is about 00:07:32 in length, and (tough this detail may have no influence or meaning) the music is Symphonic Metal. The actual file of the song is 6,96 MB in size. This is also not the first time I've done such projects with such long songs on this same program either, one of my last videos I managed to successfully make and create a musicvideo with a song which was about 13 minutes and 30 seconds in length, and I also used effects on pretty much every videoclip on that project too.
    The current filesize so far on the actual project.prel-file of my project that keeps crushing is 9.73 MB.
    I am also using Adobe Premiere Elements and doing this troubleing, crashing project on a PC, a Fujitsu Windows (I believe Windows 7, or even updated to a newer version?). It has a regular ATI-card. The computer also has 2 modems and there's still some pretty GB amount free on them. The PC's main system also has a RAM in 6.00 GB and the operative system is the 64-bites.
    In short, the PC should just fine be able to handle Adobe Premiere Elements 0.9 and all its projects, just as it has handled it all before plus all my PC games at that. So it must be something with my Adobe Premiere Elements and that specific project which is the problem, but what is the problem and the serious error and how to fix it?
    Could it help to save and create the actual video in this crashing project, delete that project then start a new project, upload and put in the videofile of the crashing project in that new project and then continue from there?
    In either cases, I need help with this. Please, help!

    Thanks so much for your reply, Steve!
    Even tough I trust you guys enough here on the official Adobe site/forums to answer those questions as best I can, I am at the same time not very fond of giving away too much information because of safety. I understand I have to If I'm to recieve the accurate answers and solution, but as this is the internet you can never know. But again, I trust you guys enough on here and thus I'll try to answer those questions as best I can, even tough I am not very good with such stuff about computers. The PC I am using is also not only mine, it is the family computer also which me and my whole family uses.
    The operating system on my computer (according to the computer propotions etc) is a 64-bites operating system and the computer/PC is also a Windows 7 Home Premium.
    The processor the computer/PC have is a Intel(R) Core(TM) i5 CPU and the RAM is 6.00 GB. However, (and I hope I make this understandable because the computer/PC is in swedish)the subscore of RAM in the computer's Performance-Classification/Ranking is 7,5. The processor subscore is 7,3 per second. And the free space? Well, we have two modems, let's say a modem A and a modem B. Adobe Premiere Elements 0.9 is set to save all its stuff etc on modem B, while modem A is the main modem and spaces all main stuff and other things of the computer/PC. Modem A has about 314 GB of free space, while modem B has 207 GB of free space. Modem A's capacity is a total of 489 GB in which 175 GB has been used, the modems filesystem is a NTFS. Modem B is also a NTFS filesystem and its capacity is a total of 439 GB in which 232 GB has been used. And the Disk Cleanup? I believe my that latest ran it for about a few weeks ago. We also have a CCleaner also. But about the Disk Defragmenter, I have no idea. What exactly does a Disk Defragmenter do?
    You mean, entering my project that keeps crushing and simply rename it by using "Save As"? If that is what you mean, I dunnow If that actually worked. When I still tried to do stuff and edit the crashing project (tough as said, it hardly took any changes and process before it triggered that message) and then crashed and shut down, and I opened up the program again (trying to open the same project that way), it asked me If I wanted to re-create the missing process from the last crash of the same project. I tried it and it automaticly was renamed to a for example Project.copy. But when I tried to work with that it was to no futher success, the project kept crashing. I haven't renamed the project by "Save As" tough, but I doubt it'll work, I even tried to rename the actual project file in the Adobe Premiere Elements files but nope... the project keeps crashing. But also about the same question, "Save As" under a new name but in its own folder? You mean the actual project folder or Adobe Premiere Elements preview folder of the projects?
    My camcorder is pretty old by now, have had it since I turned 15, it has worked pretty good since then. Its model is a Sony Handycam, Carl Zeiss Vario-Tessar OPTICAL 20x. Even tough the last thing maybe doesn't say anything, this is all I know about my camcorder, except that it is a model no. DCR-HC17E PAL. But in that Project  which keeps crashing, there are only a few actual camcorder clips used as I am making a Game-MusicVideo and most of the footage of the Video-game (actually a PC game) I'm making a musicvideo of is downloaded from Youtube mostly from a guy I asked permission for to download his recorded footage of the game. I used a Youtube downloader called ClipConverter. As I don't have a SD card I cannot make this footage myself. But some footage I recorded on my camcorder, but If I can find high quality clips and get them, I will. The other footages is actual official trailers of the PC games which also was downloaded from the net. But I can give you the stuffs filetypes and hoping that may help. The downloaded footage which was downloaded by this ClipConverter, are MP4 files. The other stuff (which were official trailers) and most of them are also MP4 files, the others are QuickTime-film files. Many of these downloaded footages and trailers are also in HD quality, at least some of them I think.
    The actual filetype ofthe footage I myself recorded with my camcorder are, well.... it says Videoclip in the file. Maybe it is AVI?
    The project settings? You mean the settings you set at first when starting as a new project? The general settings are, in editingsettings it is AVCHD 270p square pixel. This is kinda hard for me to tell since everything is in swedish in my program. But these settings has worked perfectly before, same with all files, footages and videoclips I have been using, also all the soundfiles etc. Even the actual crashing project worked perfectly before it started crashing... So why does it so suddenly start crashing now?
    The audio is a song I copied directly from its album and CD into the computer/PC and it seems to be in WMA format in filetype.
    And lastly, no I haven't rendered the timeline of the project ever, not even on my other projects. What does the rendering do and is useful for? I have very little knowledge of it. Other, I keep the Timeline mode open all the time because I can edit my videos much better with it, but perhaps that editing method make little influence of the actual problem.
    Other, yesterday when writing the post and topic, I forgot to mention that I restarded my computer right after I created a new project, that testing project. When finnished with the testing I restarted the computer. Since then I haven't touched the crashing project since now tonight, when checking its settings for this post. I am also right now trying to create and save the actual videofile of it, saving it on my computer. I'll soon see If it's successful without any crashing interruptions, plus that the video itself works and is smooth when I'll play it on Windows Media Player like all the rest of my other videos. I do this just in case I must create a new project to be able to continue with my musicvideo, as the first part of it I worked very hard on.
    Other and again, I am still puzzled about why this is even happening, that this project which worked perfectly fine before, just suddenly starts triggering that "Serious Error" message and crashes. And in this program which worked so perfect before. Has this happened to anyone else before? Has anyone else experienced the same issue I have? Is this a knowledgable issue which has solutions and ways to fix it?... :/

  • Adobe Premiere Elements 7.0 hangs while exporting and during peak file generation.

    I have Adobe Premiere Elements 7.0 (PRE7). I have a project which is using a single clip from a Mini-DV that was captured with Nero 8. Nero 8 was used because it was captured prior to installing PRE7. The file is 12GB and is on a USB disk drive because I don't have the space on my main hard drive (I have about 11GB free). My project doesn't do too much that's fancy. It merely uses about 20 minutes of the 60 minute Mini-DV captured AVI, and it uses simple transitions between each scene. I also have very simple titles at start and end. No themes or anything else.
    I've seen two problems. 1) While editing the project, seemingly (but I'm not positive it's related) while the peek file was being generated, PRE7 would get into a state of using about 40% to 50% CPU, and it would not let me do anything else. The other problem, 2) While using "Share" to export the video to WMA for playback on PC (about 180MB estimated file size according to Adobe), the file is exported to about the last remaining 5 seconds, but then PRE7 goes into that mode of hanging with 40% to 50% CPU usage.
    One time when it had this 50% CPU issue, I let it sit overnight, and the export was finished in the morning. The export that time was to a 90MB FLV for posting to the "web" according to the Share wizard. But when I was doing the above (issue #2), it went into the 50% CPU usage but didn't finish after waiting around 2 hours. Even if I were to let it sit that time, and it were to finish, it seems like something's wrong and that this is unacceptable.
    When this happens, and PRE7 goes into 50% CPU utilization, there is no pacifier or percentage bar advancing. It usually happens near 100% finished. Only one time did it complete successfully after leaving it unattended at 90% complete for an extraordinary amount of time.
    To recap:
    C:\ hard drive ---> PRE7, my project.
    E:\ USB drive ---> 12GB source AVI file and destination for export.
    I saw elsewhere on this forum that someone imported a mini-dv captured AVI into Window Movie Maker and then exported it to Mini-DV from that app. This solved that person's problem with hanging during peak file creation. I had the 50% hang issue during peak file generation but I'm not sure it was related to peak file generation. A peak file was generated in a project which, when exported with share as mentioned above, still did the hang 50% CPU issue. Regardless, I will try the import/export/movemaker thing and report back but I've been trying enough things that I wanted to take a second to ask for assistance.
    Does anyone have this issue, and is there a patch or fix?
    I might be able to provide a user mode dump of the 50% CPU adobe process. There is some call stack information and I'm wondering if developers would want this info if they don't already have a solution/fix to this bug.
    Thanks for any help.

    I have some more info on the hang which I've been experiencing during export/share of a project which uses an AVI as its one main clip. Adobe Premiere Elements 7 (PRE7) appears to be hanging because it's looping endlessly in ImporterAVI.prm. I'm wondering if this info can be passed onto Adobe developers and/or if I can submit this information elsewhere for such processing. I also have a process dump file which might be helpful, not to mention the original project files.
    I used Process Monitor to help analyze this situation, and prior to PRE7 getting into the endless loop, it appears to be reading from the AVI file little by little, and WMEncodingHelper.exe is writing out little by little to the destination file, both of which I would expect. When PRE7 gets to the end of the import/export, Process Monitor appears to show all the aforementioned disk activity ceasing. I see neither process reading or writing. This would be normal if the share/export procedure had completed. But PRE7 is not complete. It is hung and is operating at 50% CPU utilization.
    Far below in this post are technical details which may be helpful to an Adobe developer determine why the importer could get into this endless loop. In those details, there is a jump instruction, "jb ImporterAVI!xImportEntry+0xf32", which will always jump if a particular compare always turns out a certain way. But in my review of the counters being compared, it never will get to a point of exiting. When I modify a flag (the carry flag) to be 0, the loop exits. When I did this, my export/share of my project completed successfully. So it was done, but for some reason, PRE7 was looping and looping in its AVI importor instead of completing the export (aka "Share").
    I cannot say that this certainly indicates a bug with PRE7, but it seems to me that there's enough data for Adobe to be at least investigating this particular issue. I'm not the only person who has seen this as there was at least one other message describing the same problem which the user resolved by effectively re-creating the AVI file via a no-op import/export into and out of MovieMaker. My AVI also goes through MovieMaker, import/export, without a hitch.
    In a sense, I view PRE7's "share" as essentially an import, processing of imported information (i.e., effects and transitions), and an export. It's an import of all clips into the project at the right times, a processing of all effects, and finally an export to a destination. I realize this is simplistic, but the point I'm making is I have a simple project with a single AVI, and it appears that the "import" portion of PRE7's Share option is choking on the only clip used by this project. I also don't have much but simple transitions and a beginning/ending title on the project, so I'm not thinking this use of PRE7 is much more than what I'm doing with MovieMaker when importing/exporting this AVI.
    I fully agree that optimum hardware can be either required or critical for certain types of video editing, but PRE7 is a consumer program and I'm not using anything extensive about it and the symptoms are that PRE7 is looping on its import of a file other programs don't have a problem with. I already tried purchasing a 1TB external, which I'm glad I did, but I really think Adobe developers should look at this issue. There may be a problem with handling certain AVI clips used in a project when those clips come from certain sources. If there is an issue, perhaps it could warrant a fix that would make PRE7 more compatible with these other clips.
    Does Adobe have a procedure for people to upload (or mail) projects and files to it so that they can troubleshoot why the importer gets into this state? I also mentioned earlier that I have a full user-mode dump of the process which may be of value to a dev. Can I submit this information anywhere?
    Here are textual technical details:
    Plug-in which loops: C:\Program Files\Adobe\Adobe Premiere Elements 7.0\Plug-ins\en_US\ImporterAVI.prm
    The following are the instructions at the "bottom" of the loop which never ends. Below, I put "***" at the jump instruction I mentioned earler. If I force the carry flag to be 0 at that point, and the jump is skipped, the export completed successfully. Additionally, notice that [esp-0x1c] is 0x2000, and that both eax and edi are 0. When I see it loop, eax stays at 0 and never reaches 0x2000. I wonder if something about the AVI is causing values used by this importer to be such that it causes this endless loop, and if that's the case, and if such values are valid/good, I'm wondering if the importer can be fixed by being able to detect such values so as to not choke (if in fact it's an importer issue).
    1239dda2 50 push eax
    1239dda3 ffd1 call ecx
    1239dda5 8b442424 mov eax,dword ptr [esp+24h]
    1239dda9 015c2428 add dword ptr [esp+28h],ebx
    1239ddad 03c7 add eax,edi
    1239ddaf 83c410 add esp,10h
    1239ddb2 3b44241c cmp eax,dword ptr [esp+1Ch]
    1239ddb6 89442414 mov dword ptr [esp+14h],eax
    ; *** This is where it loops around and around.
    1239ddba 0f82f2feffff jb ImporterAVI!xImportEntry+0xf32 (1239dcb2)
    ImporterAVI!xImportEntry+0x1040:
    1239ddc0 8b542420 mov edx,dword ptr [esp+20h]
    1239ddc4 52 push edx
    1239ddc5 e810d40000 call ImporterAVI!xImportEntry+0xe45a (123ab1da)
    1239ddca 83c404 add esp,4
    ImporterAVI!xImportEntry+0x104d:
    1239ddcd 5f pop edi
    1239ddce 5e pop esi
    1239ddcf 5d pop ebp
    1239ddd0 33c0 xor eax,eax
    1239ddd2 5b pop ebx
    1239ddd3 83c428 add esp,28h
    1239ddd6 c3 ret
    ChildEBP RetAddr Args to Child
    WARNING: Stack unwind information not available. Following frames may be wrong.
    3195d9b8 12387545 10590f9c 27c53e00 06b35ff6 ImporterAVI!xImportEntry+0x103a
    3195d9ec 1239ea10 06b35ff6 00000000 27ad8a60 ImporterAVI+0x7545
    3195da1c 1238aa31 06b3554b 00000000 7fdf0000 ImporterAVI!xImportEntry+0x1c90
    00000000 00000000 00000000 00000000 00000000 ImporterAVI+0xaa31
    [esp-1Ch]: 3195d9a0 00002000
    eax=00000000 ebx=00000000 ecx=3195dbcc edx=00000000 esi=27ad8a60 edi=00000000
    eip=1239ddba esp=3195d984 ebp=3c7ba50b iopl=0 nv up ei ng nz na pe cy
    cs=001b ss=0023 ds=0023 es=0023 fs=003b gs=0000 efl=00000287
    ImporterAVI!xImportEntry+0x103a:
    1239ddba 0f82f2feffff jb ImporterAVI!xImportEntry+0xf32 (1239dcb2) [br=1]

  • Recording to laptop from Panasonic HVX through Premiere Elements 8

    I'm going to be using a Panasonic HVX200 and tethering it to my PC laptop  (It runs vista, has a 300 G hardrive and 3 Gig of RAM) via firewire.  I have Adobe Premiere Elements 8 and want to record using it so I can get HD footage (720p) rather than having to record to DV tapes for Standard Def quality. I also have a 1T external hardrive that will hold the recorded video (this is attached via USB, I can't recall the specs right now and don't have it with me, so I hope this is enough info).
    I have never done this before, so I have two questions:
    1) Will it work? I believe it will from what I've read (I know that Final Cut Pro on a Mac can do it, but I haven't seen anything specifically about Premiere Elements so any confirmation would be greatly appreciated).
    2) Are there any specifc settings I need to use to make sure Elements is capturing the video in the best format?
    If further specs are needed to answer these questions, please let me know.
    Thanks,
    Kelly

    You've got a number of challenges here, Kelly -- not the least of which is that you're trying to edit video from a $6000 professional camcorder on a $75 consumer video editor. You're much more likely to have success with a professional editor, like Premiere CS5, Vegas Pro or Final Cut.
    The other challenge is that this camcorder records at a number frame rate in a number of formats, many of which are not compatible with Premiere Elements.
    Still, if you're shooting in 1920x1080 30p HDV and you're connected to your computer via FireWire, you may be able to capture and edit the video if you've got your PRemiere Elements project set up for HDV. It's worth a try anyway.
    According to the specs online though, the only consumer format this camcorder is capable of shooting at 30i is 720x480 (standard definition) 30i miniDV. None of the hi-def modes are standard consumer modes.
    Still, this is predonimantly a DVPro camcorder. And the odds are much more in your favor if you edit its video with professional software.

  • Best laptop for Premiere Elements

    Can you recommend a laptop for Premiere Elements.
    I have PE9 and thinking about PE10.
    Preferably matte screen.
    UK based so Sager not really an option.
    Thanks

    Laptops are never best for video editing, since they're usually built for portability rather than power. They also cost about 50% more than desktops for the same amount of power.
    But what type of camcorder is your video coming from?
    If you are editign tape-based video, a dual-core processor and 4 gigs of RAM with a 500 gig hard drive should be adequate.
    If you are working with AVCHD video, you should go for a quad core or i7 processor running Windows 7 64-bit.

  • Premiere Element 12 when moving video clips. HELP me Rhonda!

    I am currently running Windows 7 (Professional) and I downloaded Premiere Element 12 off Tech Soup so I could make a short video for my company. I am working on a specific project and I have done a considerable amount of editing already. When I try to renegotiate  the positions of various clips- an "error" message appears and then the program shuts down. Is my computer incompatible??? HELP! I don't want to lose all the work I have done. Also, I am so desperate I would be willing to buy the software all over again and put it on my mac-laptop but that would be my last resort! Has anyone else encountered this problem?
    [Moved from Premiere PRO to Premiere Elements... Mod]

    Jordne716
    Thanks for the reply. Let us see what we can do with what you have.
    When I asked about computer resources, I was asking about how much installed and available RAM the computer has, how much free hard drive space, the processor and the clock speed. Most of that you can get by right clicking the word Computer and selecting Properties.
    About your alternative plans...
    Your Premiere Elements 12 Windows project is not going to work on Premiere Elements Mac (whatever version)
    If you export your Premiere Elements 12 project to a .mp4 file (Publish+Share/Computer/AVCHD with one of the .mp4 presets), you can import that into a Premiere Elements Mac project. However, that is a whole video which will need trimming to make significant further edits.
    No guarantees, but your Premiere Elements 12 Windows project file should open in Premiere Elements 13 Windows. But, work with a copy of the Premiere Elements 12 Windows project as a safety net.
    This is what I would like you to do.
    Can you open that Premiere Elements 12 Windows project that shutdown when you were moving clips around in the Edit area of the program? If so, open to the Expert workspace. Have you placed audio transitions in the Timeline content? If so, remove them and determine if the problem is gone, is the same, or gets worse.
    Also, what specific media were you moving around when the crash took place? If you can open the project, can you delete and re-import the file(s) in question? What Timeline tracks are you using and which were involved in this incident?
    I am particularly interested in the answer to the last question to use the answer as a point to start the troubleshooting.
    Please let me know if you need clarification on the above.
    We will be watching for further developments and will keep close track of your posts.
    ATR

  • Premiere Elements 8 Unresponsive & Unusable

    I have received Premiere Elements 8 for reviewing and installed the package with both Photoshop & Premiere Elements on a newly installed Windows Vista Premium system. The computer has Adobe CS4 running on it with no problems so I am pretty sure it can handle Premiere 8 but does have an NVIDIA graphics card, Zotac 8800GT. This system also has Intel Quad Core Q6600 @ 2.99 GHz, 4 GB Ram and Zotac 8800 GT.
    This should easily run Premiere 8 but when I start up the program after a succesful installation and updating it does the rendering in background where I cannot use the program at all. If I do anything in Premiere Elements it will go to an opaque white like the usual not responding in Windows Vista for awhile and I cannot do anything in the program. It has not crashed but just sits in the background rendering and i cannot really use the program at all.
    The videos I have imported and tried to use in a project are small two to four minute AVI clips that I want to work with but the program takes a long time with background rendering. Is Adobe seriously saying I need to do a bunch of driver uninstall and install older ones or other things to get a less expensive video editing program to work on a known good system that I can render video and audio in using other programs with no problems.
    I review products routinely and this system along with another, Windows Vista Business, AMD Dual Core @ 3.0 Ghz 2GB Ram, does not run Premiere Elements at all without the rendering in background that I could ever get through. Both systems are fully up to date and do not have any problems running other things like Flash, Dreamweaver and other CS4 programs as well as a host of other things like TV on PC using PCI cards.
    This is a Vista program that should run fine, is anyone else having problems like this?
    I also tried disabling the background rendering and turning off the analyzer in the organizer but it does not seem to have any affect to my problems.
    Is anyone else with a Windows Vista and NVIDIA graphics card having problems like the program is rendering in background and not being able to be used in this mode until it has finished?

    "If a person wants to edit video they need DO need to grasp what a CODEC is."
    This is utter hogwash, to use a nice term. No offense meant but I think you are wrong.
    Other than the double word "need," you are totally wrong. The CODEC is the building block of video, just as ISO is for still photographs. I feel that it your aversion to CODEC's, that is clouding your impressions. Also, maybe the word "need" does need to be repeated, just not as I had done.
    As has been belabored above, the CODEC is the keystone to AV files, and hence to editing. Whether one wishes to learn the rudiments of these, or wishes to sweep them under the carpet, is their own choice. Obviously one that you have made beforehand.
    Installing Premiere Elements and importing video and editing it does not require any knowledge of what a CODEC is or even that it exists. I remember editing video when I first got a Panasonic camcorder using a simple Arcsoft editing program that came with the camera and had no clue what a CODEC was at the time.
    Again, had you read, or understood, that was easy in an earlier time - back when DV-AVI from miniDV tape was the only real way to capture video footage, and then Capture it and edit it. Nowadays, there are many different CODEC's and how they work is very important. People want to do some form of capture of YouTube material and then edit it. People want to use programs like FRAPS, or Camtasia, and then edit the footage. People want to capture footage on various cell-phone cameras, or helmet cams and edit it. All of these are very different. They need to know what a CODEC is, how it impacts the prospects of editing the resultant footage, and what they can expect. To ignore this is foolishness, and will lead to problems, regardless of which NLE is chosen.
    An NLE can only contain certain capabilities, and adoption of newer technologies (read CODEC's here) takes some time and coding. In the case of Adobe, they must first decide if a new CODEC is likely to be a big enough part of their install-base to warrant the engineering efforts. All possibilities cannot be included. Some newer ones come out, after a program is released. Some need to be incorporated in an update. Two good examples of this are the RED CODEC's and the recent Panasonic Intra-Frame CODEC's. Both were included in the recent CS4 updates.
    Why you have such aversion to CODEC's is beyond me. Again, they are the building blocks of AV files and editing. They've been around for over a decade, and will be around for more. Maybe it's time that you learn what they are, how they impact video playback, editing and then Export. To ignore them is an injustice to anyone reading your reviews. Again, were I to ignore Megapixels in a camera review, or DOF in a review of a lens, or system, or to ignore CODEC's in my reviews of an editing system, it would be a disservice to my readers.
    Now, in a perfect world, every NLE would be able to natively edit all possible sources (read CODEC's here), and all that are likely to come about over the next decade. The world is not perfect. No NLE can possibly handle even the list of CODEC's that are available at this exact moment in time.
    I do not want to get off base with arguments about CODEC's, I'm simply stating what others here have said and it does seem like the wine snob is getting off track with CODEC's.
    Again, and in my defense, these are the building blocks of digital video. To think otherwise is shear folly. To ignore them is a disservice to the readers of any review. Now, many may wish that they did not exist, but they do. They are very important, whether some wish to acknowledge that, or not.
    What would you advise a user to do, should they have the TechSmith CODEC in a source file? What would you suggest, should someone hand you a RED CODEC file? What would you intimate would be a good workflow, should someone hand you a BlackMagic CODEC file? Same for Xvid, or DivX. Same for an Panasonic Intra-Frame CODEC. What would you suggest? Oh, I can guess that it would be, "ignore the CODEC, as they are meaningless." Is that correct?
    The other programs worked with the same video so obviously my computer has the right CODEC's otherwise they would not edit the video in the other programs.
    And this proves that those other NLE's support the particular CODEC's, and that they are installed properly on your system. It does not mean that CODEC's are immaterial, as you have repeatedly suggested. The Adobe NLE's are based on a DV-AVI workflow. They make use of other CODEC's, but that does not render CODEC's moot, regardless of what you might contend. As I stated up-thread, I use CyberLink's PowerDirector for some footage, that PrE and PrPro cannot edit natively. I use that tool (and many more) to handle the CODEC's, and then Export to DV-AVI for final editing in my Adobe programs. This does not mean that the particular CODEC is immaterial, but that some NLE's either handle one better than others, or include native support for some. Adobe programs are often a bit more limited. Does this mean that they are dreck? Not in my book. I use these various programs as tools. My art comes from my camera, and my skills as an editor. I might need to use several "tools" to get me to where I can create.
    Are the Adobe programs perfect? No. Do they do a good job with the proper footage and CODEC's? Yes, at least in my book. I've had the luxury of using many different NLE's, so I have a lot of experience with other NLE's. I also have extensive experience editing 16mm and 35mm film. Maybe that makes me so grateful for digital editing. That also allows me to open my mind to what it takes to do great work nowadays. I know how it was in the film-only days. One of my films was nominated for an Academy Award, and it was edited on a six-plate Moviola deck. I cannot imagine how much better that film would have been today, edited on an NLE with digital material. One will never know.
    I am not trying to say that I don't want to know or don't care about what a CODEC is, I shouldn't have to in order to use this program. I compare the box requirements to my system, I meet or exceed them so my system should be able to edit video from a compatible camera. Video from a camera that can work in less expensive and even free programs should easily work in Premiere Elements regardless of knowing what a CODEC is.
    But that is exactly what you have said, over and over again. What you are failing to grasp is that digital video cannot exist without CODEC's. Why you choose this platform is lost on me. I've stated many examples outside of video CODEC's, but they have been lost on you.
    Just to give you a bit of background, I have 393 CODEC's installed on my workstation, and 243  (266 now) on my laptop. Why? Most are to play various files with those CODEC's. Some are for just encoding, like the HuffYUV and Lagarith, so I can transport files in a lossless format between programs. Some are so that I can edit in various NLE's. Some of these, like RealMedia, Indeo and CinePak are for older AV material, that I still may have to use. I have 4 flavors of H.264, because all CODEC's are not created equally. I also only have CODEC's from the source, and no CODEC "packs," as I want the best that I can get for me, and for my clients. Amazing! If CODEC's were not important, why on Earth would I have 393 on my workstation and 266 on my laptop? Ignore them if you wish, but you are doing a great disservice to your readers. Still, that is you choice.
    Please do not confuse the issue of CODEC's with a program that does not work as advertised for many. It seems to me that high definition video is the problem and the program may be a resource hog when it gets its hands on HD content.
    Well, since most of the recent CODEC's are for HD material, I'm not sure how you propose to separate these.
    Now, what Adobe's marketing department might state, all depends on the CODEC's involved. Maybe they should state that that some HD material will work perfectly, and that some will not. Again, this will depend on that evil word, "CODEC."
    Going back up-thread, I was taken to task, after commenting on what the "average" consumer wanted. The following statement was on what those, who DID want to edit their footage would want. That is but a small subset of the "average consumer." I find that disingenuous, at the very least. What the "average consumer" wants is to display their footage on their TV for their friends and family. The next group up wants to also post it to YouTube, or similar. Then, the next group wants to edit it - a subset of the main group. Would you not agree, now that I have broken thing out? Now, it is quite possible that a majority of your readers DO want to edit the footage, but would you not agree that a great number could care less about that aspect?
    Good luck with your reviews. I hope that you are able to get PrE running on your system and can write about it. Only suggestion that I would make would be to use files that the majority of your readers are likely to use, and report on that.
    Hunt

  • Adobe Premiere Elements Won't Start A New Project?

    When I open up Premiere Elements and try to start a new project, all it shows is a black and purple line, then it just stops. I have already tried updating QuickTime, Windows 7, Nvidia Drivers, and Uninstalling and then Reinstalling Premiere elements. I am running it on a PC that has an AMD FX(tm)-6300 Six Core Proccessor, 8 GB of RAM, a Nvidia G-Force GTX 650, and i installed the program on a secondary hard drive with 761 GB of free space.

    xXFIRE
    What is this "secondary hard drive" on which you originally installed Premiere Elements 12? Internal or external and how formatted NTSC or FAT32?
    I do not see where anyone has asked about "Scratch Disks" as they relate to your issues?
    Please refer to Edit Menu/Preferences/Scratch Disks...
    a. Where are the scratch disks directed and how much free hard drive space is at that location?
    b. Do you have all the scratch disks categories directed to the same place? If not, do so and make sure there is lots of free hard drive space where you are pointing them to.
    Please look for pile ups of preview files in the Adobe Premiere Elements Preview Files Folder and pile ups of conformed audio in the Media Cache Folder. Both these folders by default are in Documents/Adobe/Premiere Elements/12.0.
    Please go to Edit Menu/Preferences/Media and hit the Clean button in the Media Cache Database in that area.
    As for the matter of where Premiere Elements program should be installed. Interesting question and some interesting answers. Back in a 2010 thread here on this type of subject, Akshat B (Adobe Staff) wrote
    Yes you can install Premiere Elements on any other drive. For that you need to follow these steps:
    1. Uninstall current copy of Premiere Elements.
    2. Start the installer of Premiere ELements.
    3. Choose a location on d:\ drive after choosing the default TV format.
    Please keep in mind, even if you select d: drive as the install location some amount of data will get copied to C: drive.
    -Akshat
    http://forums.adobe.com/message/3284673
    Is your Local Disc C, a SSD drive? Why is there so little free space on your Local Disc C?
    More later.
    Looking forward to your follow up?
    ATR

Maybe you are looking for