Premiere Elements 8 hang on exit - fixed

All,
As I posted earlier here: http://forums.adobe.com/message/2435573#2435573 The "hang-on-exit" bug is now fixed in our latest beta drivers version 195.81. You can find those drivers here:
http://www.nvidia.com/Download/Find.aspx?lang=en-us
As a bonus, these drivers also fix a few issues with GPU accelerated Flash rendering, and fully support the Flash 10.1 beta 2 release, in case you are interested.
Regards,
Barthold

Barthold,
Thank you for posting and nVidia for the work on these issues.
Appreciated,
Hunt

Similar Messages

Premiere elements 11 hangs on exit (OSX)

I have a brand new install of photoshop elements and premier elements (and organizer). Photoshop and organizer are working flawlessly. Premiere hangs on close almost every time. If I edit video then close and say "no" to save changes it hangs for sure. I can do a complete reinstall then it will open and possible close once or twice. Once it exhibits the hang behavior it seems that install is toast. The OS itself is a month install of fully updated mountain lion. Other apps I have on this computer are failrly straightforward but who knows. I'm hoping someone has seen something similiar. I really dont want to have to do a complete rebuild just because premiere wont work.
Thanks,
David

Thanks AT for the response. I am very new to PrE so bear with me. I figured it out and didnt find the exact culprit but maybe this will help someone. I knew something was wrong with something in the realm of Adobe so I removed everything I could....elements photoshop and premiere, reader, and flash. Also I did what I call a thorough removal...on a mac uninstalls are a bit more work I essentially did this:
(as root)
find / -xdev -iname "*<program name>*"
This finds anything on the local filesystem and ignores case for say premiere or organizer. After de-Adobe-ing my system completely I reinstalled reader, flash, photoshop elements, premeire elements and now all is well. It is important to note that the automated adobe uninstaller leaves a ton of stuff behind. I have a suspicion the fix was in the manual removal somewhere.

Premiere elements 12 hangs

Newly inmstalled Premiere elements 12 just hangs after 'new project' is selected. The start screen remains visible but no other window opens and nothing happens. 1 application and 3 processes are running:
Adobe Premiere Elements 12.exe
Adobe Premiere Elements.exe
Adobe QT32 Server.exe *32
Running Windows 7 pro upgraded from Vista 3 years ago. 64bit i7 procesor 8Gb mem.
No problems with any other applications.
Installation appeared to complete without problem. Uninstalled, reinstalled, same result.
Does Adobe have any support any more?

plinyEuropaea
Are you talking about "new project" in terms of Welcome Screen Video New Project or in terms of File Menu/New/Project?
I have found Premiere Elements 12 to be very problematic in getting "established". On two different operating system (Windows 7 64 bit and Windows 8.1 64 bit), I had an seemingly endless problem with
a. 1 to 2 minutes before opening via File Menu/New/Project
and
b. 1 to 3 minutes before closing of the project with or without saving it.
I would prefer to say that one thing resolved the problem. I tried "everything" and, when I was ready to retreat, it all worked as expected.
a. Besides running the program from a User Account with Administrative Privileges, right click the desktop icon for the program and select Run As Administrator.
b. Do a run through with ccleaner (regular cleaning and registry cleaning parts)
http://www.piriform.com/ccleaner
I experienced this project with no media imported. Is that the same in your case? If not, then we are going to need to get into the details of your project preset and the properties of what you are importing into the project. If you are saying that you cannot get into an opened project that is another matter.
Please review the above and then we can discuss all this and more in the morning.
Thank you.
ATR

Background Task on Adobe Photoshop Elements and Adobe Premiere Elements Organizer "hangs"

I recently upgraded my software from Elements 10 to Elements 12 and had a bit of trouble. Apparently both 10 and 12 have a way of launching an executable in the background which tends to get "stuck" on my system. I believe the problem may be related to the network configuration and software mix I live with, but I need to confirm my suspecions and find a way to control the problem. Here is what I know... I have always experienced a lot of problems using Elements with my NAS device which is a 1TB usb 2.0 connected disk system attached to my Linksys E3000 Router. When I got the router, the BIOS software did not correctly support NTFS file systems, but subsequent updates eventually made this possible if you formatted the removable drive on a system in NTFS, you could then hang it on the router and "see" the contents, serve them via Windows Media Player, or iTunes, etc., etc. from a computer atteched to the network, or via wirless directly off the router. I archived all my photos out on this file system and have successfully indexed it for use with Adobe Photoshop Elements and Adobe Premiere Elements Organizer, but... When I went to install Elements 12 software I tried to install it without first removing Elements 10, and on a system which had run Elements 10 since the last full reoboot. During the install of 12 under "shared services install" the installation process "Hung" on a background task with a name like "AdobeElementsAnalyzer.exe" which only shows up in Windows 7 task manager as a running process, not as a full program, but because the file was locked by the system, the install hung. I eventually figured out that I needed to start the install of Elements 12 software immediately after having rebooted so that this program was not present in the background, and succeeded in completing an install of Elements 12 on my Windows 7 X64 system. This system required a "special" software download for Premiere Elements, but not for Photoshop Elements which is only apparently avaliable under 32bit emulation mode. I finally got the "shared components" portion of the X64 Premiere Elements to complete an install, and then set about verifying the onversion/upgrade of the indexes to my photos and video stored out on the NAS. The same rogue task which prevented me from doing the install showed up agian, taking all the system resources away from my dual processor Intel chip and refusing to let go. I was forced to terminate it from the task manager. I strongly suspect that my "issues" are in part due to the extrordinary network latency imposed by the drive connection I'm using to index my photos and videos, and I'm looking for a better approach to using the editors against my master catalog of files, as well as figruing out just what I need to do to insure that all the files I have stored on the drive are accessible by the organizer when I need to pull a copy to work on.
A complication is that I have two "legacy" Windows XP systems on my network, a reasonably fast Windows Vista Business desktop, and the Windows 7 X64 processor system which is the most powerful system I have. The Windows file security enhancements to NTFS changed from XP, to Vista, to Windows 7, so files which get saved to the NAS disk inherit a variety of different levels of security under windows. I have occasionally gone to one of my old XP boxes and "wiped" the security settings by resetting everything via Windows XP. Because the NAS is so slow, this process can take several hours and must not be interrupted by attempts to do anything affecting the NAS by any of my other networked computers. To avoid problems with my photo archive, it makes sense to me to do all my editing on copies which have been extracted from the NAS archive and stored on the C: drive (boot drive) of my Win X64 system.
What I seriously need to know is this: When/If I define a "watched" portion of my file system, rather than taking the time to manually import every little change to my photo archives, can I expect the Photoshop Elements Organizer to work properly as long as everything stored on the NAS is stored via the same system which runs Elements with the same active "user" in control so that all the windows 7 file security settings putting stuff on the mapped NAS drive remain properly secured under Win 7 X64? Frankly I don't care if the files appear "read only" to every other system and identity on my network, but I do need to be able to "see" them. I have been able to view slide shows and movies stored on the NAS via both my networked iPad, my Apple TV, and using Samsung's funky android and Windows compatible software. Frankly, I doubt that Microsoft or Apple has full understanding and control of the environment where there is no host "server" other than the eprom based stuff my Linksys E3000 loads to emulate early Windows Media Management architecture, but I mange to get it to work as long as I don't try anything sophisticated with the file permissions. As a fall back, can I expect individual "imported" bits out on the NAS to remain stable if indexed and used only by the Elements Organizer running on my Win 7 X64 system?
I am seriously considering converting an old WinXP desktop into a UNIX box which could be configured as a "Server" for everything stored on the NAS and be done with my problems in return for the power required to run the server all the time so stuff is there when I need it. Any recommendations?
Message was edited by: [email protected]

Adobe hasn't said whether it officially supports PSE 7 on Windows 7. But reports are starting to trickle in that PSE 7 works fine on Windows 7 for most people, though a couple people have reported crashes. My PSE 7 seems to work fine, though I primarily use PSE 8 now. This is all very preliminary, and we'll learn more as more people post here.

Adobe Premiere Elements 8 Hangs Crashes Errors - Vista 32

Hi,
First I'll admit i'm no pro (obviously why im using elements), so if im doing something amatuerish it's because i'm not a professional.
I remember using adobe premiere elements 3 a while ago, and it ran fine.
I just bought Premiere Elements 8 and it's crashed more than any program i've ever used. Ive been to many forums to address the issues however there seems to be no solution in site (especially given that their support seems to be down at the moment).
The first "weird" issue is that I get a little red X that appears at the lower left portion of the screen and when I click on it it says that my preformance will be poor because my graphics card isn't working properly. This is not true as my Dual Nvidia 9800GT cards are working fine. (I have sli turned off for the record because of a conflict with Cubase). So I don't know what this means. But I did notice something odd in my windows video display options I have 1 montor enabled but I see 3 grayed out disabled monitors even thought I only have 1 plugged in. (I was using an additional one but it's unplugged currently)
My most common issue is with hanging that won't end. This usually happens when I apply a change to a file and trim it, or move it almost always in the timeline. The progrom just closes all together when I edit still images from time to time especially when I overlap it with a video.
When the hangs happen my Cpu is at 12%ish, and I have ram available. Although Premiere uses a truckload!
Here are my project specs:
The preset project mode that I chose was HD (hard drive) video, widescreen 48k because the files are from my hard drive so I didn't know what to choose
Working with .mov files which were improperly formated from the source with regards to aspect and given to me so i had to stretch them out (could this be an issue?)
Using the standard Premiere sound driver, although I do have a focurite interface but i only use that for Cubase.
Backround rendering is on (seems to speed things up with regards to workflow)
Autoanalyzer is off
Computer specs:
Dell XPS 630i
Intel Core2duo 3.16 Ghz
4 Gigs of ram (although only 2.8 showing because of partition issues anyone have a solution?)
Windows Vista 32 home premium
Dual SLI Nvidia 9800GT graphics cards - Both rated at 512 memory (latest drivers, physex, and 3D have been uninstalled threaded optimization turned off)
Mcaffe security system
If anyone can figure anything out from what I wrote please let me know! thanks

Here's some basics (some of which you've already covered). Definitely disable McAfee realtime scanning while using PRE.:
Install all Windows Updates.
Install latest version of Apple QuickTime (v7.6.8 at time of writing). Even if you don't use QuickTime, PRE relies heavily on it.
Install most recent graphics and sound drivers from the manufacturers web sites.
Run Disk Cleanup.
Run Defragmenter.
Temporarily disable any anti-virus realtime scanning.
Use the GSpot Codec Information Utility to analyse the file and post screen image.
Post back here with the necessary information described here: Got a Problem? How to Get Started
As you've JUST bought PRE8 contact Adobe and get the complimentary upgrade to PRE9. Upgrade eligibility after new product announcement
Cheers,
Neale
Insanity is hereditary, you get it from your children

Premiere Elements 11 hangs when opening projects

I have a 64 bit HP ProBook 4740s with Premiere Elements 11 installed. I use my laptop 2 days a week and work from a desktop machine 3 days a week.
The laptop installation of PE11 hangs when I try to open projects but when plugging external hard drive into desktop the project opens fine.
All files are on the hard drive so it's not from missing files.
If I create a new project PE11 runs fine I then create another new project and it hangs
Really frustrated, even reinstalled - still same issues.

Martin-Evans1
We were pleased to learn that your problem was resolved by a just the Premiere Elements uninstall/reinstall
as you wrote in your post 2 and repeated your result in post 4.
As SG pointed out, the details of these issues are important to get at the core of the issues (whys) and expedite
matters to get you moving forward with your projects.
If the problem reoccurs, please get back to SG in this thread with details necessary to help you. In this instance we will not know if the problem was really with the install or rather with corruption of Premiere Elements settings file which could have been handled by deleting the Adobe Premiere Elements Prefs file or the whole folder in which it exists on the hard drive.
Continued success.
Thanks.
ATR

Premiere Elements 10 Hangs at Loading Importerquicktim.prm then resets

I purchased the Premiere Elements 10, and uploaded it onto my 64 bit Windows 7 computer. It opens up the screen for "organizer, new project, open project" and when selecting New Project it opens a load screen, and then closes and goes back to the main screen after it gets to "loading importerquicktime.prm"
I just downloaded the newest quicktime, and still isn't working. I have AVG security software.
Can anyone help?

DougBairdComedy I would recommend posting your inquiry to the Premiere Elements forum. The users in that forum will be more familiar with the difficulties you have described.

Premiere Elements 10 Hangs at Loading Importerquicktime.prm then resets

I purchased the Premiere Elements 10, and installed all the discs onto my 64 bit Windows 7 computer. It opens up the screen for "organize, new project, open project" and when selecting New Project it opens a load screen, and then closes and goes back to the main screen after it gets to "loading importerquicktime.prm"
I just downloaded teh newest quicktime, and still isn't working
I have AVG security software.

This is what i found about my HP ProBook 6555b:
http://h20000.www2.hp.com/bizsupport/TechSupport/SoftwareIndex.jsp?lang=en&cc=id&prodNameI d=4174173&prodTypeId=321957&prodSeriesId=4174258&swLang=13&taskId=135&swEnvOID=4059#11360
ATI Video Driver and Control Panel
8.722.1-100408A-098374C
25 May 2010
121.3
56K: 4h
512K: 32m

Premiere Elements 2 hangs on Vista

I have recently purchased a Dell Inspiron PC with an Intel Quad Q8200 CPU, running Vista Home Premium SP1. I installed Premiere Elements 2.0 and have had nothing but trouble. I keep getting messages about not finding ad2mpegin.dll, although these are not coming from PE2. When I start PE2 and try to create a new project, I get the initial screen in no time. Then, however, I try to hit the Capture icon and my system freezes up till I reboot. I have waited half an hour but it stays frozen. HELP ...

Premiere Elements 2 is not certified for Vista.
The first version of Premiere Elements that will run on Vista is version 3.02. Sorry.

Adobe premiere elements 13 - im getting choppy video and audio in premiere elements 13, how can i fix this...

what settings in preference and project settings can i set to fix this. i have a windows desktop
asus m11
windows 8
64 bit
intel core i5
2.8 ghz
8gb ram
i hav the software on my c drive and in scratch disks preferences i have the rest on my 2tb external drive same as project. thanx in advance...........

FNGTF84
Thanks for the follow up. Sorry that the news was not better.
As for project settings (project preset)....that should be set to match the properties of the media that you import. Only one project preset per project, so, if you have more than one format, you need to set priorities for the project, and then work everything else around that prime choice. But, for now, assuming all the project content have the same format.
The program is set up to have the project select the project preset based on its analysis of the properties of the first source you drag to the Timeline. If it cannot do that for some reason, it does not give you the closest project preset for what you need, instead it gives you its default NTSC/AVCHD/Full HD 1080i30 or its PAL counterpart if you are working in a PAL setup. You can always check to see what the project set. See Edit Menu/Project Settings/General and the readings for Editing Mode, Timebase, Frame Size, and Pixel Aspect Ratio (even if they look grayed out). You can view project settings there, but you cannot make significant changes in what has been set. So, you start a new project if the settings are not right.
The manual way for you to set the project preset....
File Menu/New/Project and Change Settings
In Change Settings, change the project preset to match the properties of your source file. OK out of there.
In the New Project dialog that you see next, change the name of the project, and make sure to have a check mark next to Force Selected Project Settings On This Project. OK out of there.
Back in the Expert workspace, import your source media using the project's Add Media/Files and Folders.
If you setup according to my suggestions in post 3 and are still have previewing issues, then I think we should look deeper into the video card/graphics card. See Device Manager/Display Adapters to verify what your computer is using. And, then go to the web site of the manufacturer of that card to determine if you have the latest driver for that card.
Please consider.
Thank you.
ATR

Premiere Elements 10 hangs up/crashes

I have downloaded the trial version of PrE 10 and it won't start up. I'm using it on Windows 7 and have gone through a lot of computer clean up tips in other support messages on the forum and it still won't start.
Downloaded Photoshop Elements 10 at the same time and have no problems but I can't get PrE to work.
Any ideas? Can't say it's exactly a great endorsement of the product right now.
Thanks in advance.

When you attempt to launch PrE, what happens?
First, I would take a look at this ARTICLE.
Now, if the program is not launching, perhaps this ARTICLE will be of use?
Good luck, and welcome to the forum.
Hunt

Premiere Elements 10 freezes when exiting clip edit

I'm running PRE 10 on a Dell 1725 with Windows 7 premium, 4 Gb of RAM, 2 GHz Core 2 Duo processor. After I've edited a clip ie set the in amd out points, exiting the clip PRE 10 freezes and closes. Even without setting the in and out points this occurs. What's up? Appreciate any advice.

My apologies I thought I had answered all of the questions. I see the format issue was unanswered. The format is HDDV which I assume is MP4. The start up tests were done using a Pentax W90 camera. I simply chose to let the software determine the format and correct it but I did choose the right one in the options.
My comment about "not ready for shrink wrap" might be a little unfair but the software seems volitile and not very robust or forgiving. There is no message to inform you of a wrong format or any problems. It simply shuts down after transfering the last clip. It doesn't even seem to matter how many you put on the timeline.
In other words it sound like the same problem. Unfortunatly I'm working with an onboard Intel chip set which I believe is the same the Dell in the original post. I would gladly buy a new computer if the chip set is the problem.

Premiere Elements 8 won't open

I recently purchased APE 8 and am new to video editing. The Organizer program opens fine and I was able to put my videos into different albums. However, when I tried to open Elements to actually edit the videos, I was unsuccessful. I clicked on Edit, Edit with Premiere Elements; right clicked on a video and videos, and then clicked on Edit with Premiere Elements; and, finally, clicked on Fix, then Edit. In each case, the software went through a multi-sceond loading process but then nothing opened and I remained in Organizer.
When this first happened, I was told that I didn't have enough RAM. I've now installed 2.5 gigs of RAM. My system runs Windows XP and I have plenty of memory.
What am I doing wrong?
Thanks.

aschiffr67
Although a dual core processor would be nice, so would be 4.0 GB installed RAM instead of 2.5 GB. Even with that 4.0 GB installed RAM in a 32 bit system, typically only 3.5 to 3.0 GB RAM would be available, but it is more than what you probably have now. But, there is always the possible perk of the 3 GB Switch. If you have Windows XP, I believe that you do that through the boot.ini file.
http://dwf.blogs.com/beyond_the_paper/2009/04/enabling-3gb-switch-on-windows-vista.html (this has to do with virtual memory, not RAM)
Have you optimized your virtual memory setup and defragmented and cleaned up the computer a lot.
There is AVCHD and AVCHD-Lite. AVCHD has the video codec (compression) = MPEG-4 AVC/H.264 and is characterized by final images of 1920 x 1080 (either via AVCHD Full HD1080i with 1920 x 1080 frame size and square pixels OR AVCHD HD 1080i with 1440 x 1080 frame size and HD anamorphic so that you end up with your 1920 x 1080. These days you will usually see a video with the MPEG-4 AVC/H.264 codec with a resolution less than 1920 x 1080, namely 1280 x 720, referred to as AVCHD-Lite. Flip Mino HD appear to be recording 1280 x 720 30 frames per second video with mp4 file extension. In addition, I have seen the codec for some referred to as H.264. Do you know for a fact that this "H.264" represents MPEG-4 AVC/H.264 compression which would be representative of the AVCHD family??? MPEG-4 by itself does not mean AVCHD, at least not in my mind. Have you taken your video into the free utility named gspot to see what it says about the codecs for your video? Or, called the camera manufactuer to asked if the video codec in your camera is AVCHD-Lite or in the AVCHD family?
http://www.headbands.com/gspot/v26x/quick_start.html
If you really do have AVCHD-Lite, have you looked at the Steve Grisetti popular FAQ about editing AVCHD-Lite? If not, please do so.
http://forums.adobe.com/thread/454585?tstart=0
Lots to think about.
ATR

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]

Adobe Premiere Elements 10 on Mac OS 10.7.2 - Hanging and Freezing

Hello there,
While I'm not very knowlegable about video editing software, I do use Premiere Elements 10 to edit videos for YouTube. I recently have been able to record using a device which records in 1080i, 29.97fps and saves as an mp4 file format. I've been trying to edit these files (which can be up to an hour long) in Premiere Elements; however, as soon as a video file from this recorder is imported and dragged into the project, it hangs and freezes. Sometimes, the hang happens when "conforming" the video file; other times it happens when trying to preview the video.
My theory is that it is due to the file format, or because of the sheer size of the file. The files can be several GBs.
I have tried to reinstall the program, but this hasn't worked.
Is there any advice you could give me?
Thanks,
LiamWatson28.

Hey Bill, thanks for the quick response.
It does use the H.264 CODEC. The project preset I'm using is NTSC-AVCHD-Full HD 1080i 30, although when I import the video to the project, I sometimes get a dialog box telling me that the project settings can be matched to the imported video, which I allow it to do. I have around 250GB of free space on my HDD. I allow the video and audio to conform and such on importing, I do not try to edit the video/audio while it is conforming. I'd also like to add that all files are transferred onto the HDD before the edit.
My specs:
MacBook Pro 13" (Late 2011) running Mac OS 10.7.4 (Lion) I apologise, I had this wrong in the title and the original post.
Intel Core i5 2.4GHz Dual-Core
8GB RAM
500GB SATA HDD
Intel HD3000 Integrated Graphics (if that's any help)
If there's anything else I need to provide, please let me know.
EDIT: I just tested editing a 10 minute video with the same file format and project preset, and, while it was hanging as frequently, it would only be for up to 5 seconds. Compared to the 50 minute video I was trying to edit, the hangs were much longer, sometimes becoming freezes. I know that if there aren't any immediate fixes and using the same video settings, I'll have to reduce the file size by reducing the length of the video, so cutting more frequently rather than recording long stretches.
Thanks,
LiamWatson28.

Premiere Elements 8 hang on exit - fixed

Similar Messages

Maybe you are looking for