Peak files crashing Premeire

I am still having problems with the computer crashing when I import certain files from external drives. As the peak file is created it freezes and the computer has to be powered down manually. I have not found any way to fix this. After multiple trys and many restarts it will work but I wasted over two hours today trying to get this to work. What can cause this crashing problem.
Windows 7 Pro
2820 processor
16 gig RAM
NVIDIA 3000m cuda card

Here's what I recommend as a good starting point for an edit system:
C: System (OS and Programs only)
D: Projects
E: Scratch/Cache/Previews
F: Media
G: Exports
Here's what I recommend as a bare minimum:
C: System (OS and Programs only)
D: Projects/Scratch/Cache/Previews
E: Media/Exports
All internal drives.
You might start by getting up to at least that minimum and seeing if you still have an issue.

Similar Messages

Crashing When "Generating Peak Files"

Experts...
I new in town, and to CS3.
Premier CS3 is working just fine on my system with one major exception...
Ecah time I import media I get a small progress bar in the bottom right corner of the status bar that reports "Generating Peak File for 123.avi" where 123.avi is the name of the file I have just imported.
As this progress bar reaches completion Premier hangs. No error message, just becomes unresponsive.
This is consistent for all imported media and very predictable, easy to replicate.
Any ideas?

Welcome! You will also find links to many free tutorials in the
Premiere Pro Wiki that will quickly
show you how things are done in PPro.
Cheers
Eddie
Forum FAQ
Premiere Pro Wiki
- Over 250 frequently answered questions
- Over 100 free tutorials
- Maintained by editors like
you

Photoshop Elements 7 Crashes When Peak Files Are Generated

Have a PC with 80g HD, Pentium 4, 2g (400hz) RAM running Windows XP. PSE7 generates peak files each time project is opened. When blue bar at bottom right of screen reaches 100%, Elements 7 freezes and must be shut down using Windows task manager.
I have copied the file from 340g ext. HD back to C drive (the location of Adobe Photoshop Elements 7 program) and this has not resolved the problem.
I note that this appears to have been a common problem since 2006 (earlier versions of Photoshop) with Adobe.
Can anyone help.
Regards
Ozyjohn

Elements User
Have taken screen shot but Forum site will not allow upload of 1.8mb image even though the initial message states "Image will be scaled to fit 2mb limit". Have edited shot to show bottom right of screen only (700kb) and scanned to PDF (895kb) but still will not accept images!!!
In the PRE 7 application the message beside the blue progression bar is "Generating Peak Files For ......" . When the progression bar reaches 100%, the program freezes.
Any suggestions
Regards
Ozyjohn

Confirming, indexing, creating peak file. What's this all about?

Althought I'm new to PrPro (see my very first post, it was the that I just started using this app), premiere already ate me that anywhere I go, when it comes to video editing, I am in its belly. But still I want an explanation regarding (again) about this message that's appearing in the status bar: 'conforming ?????.mpg". I don't really understand what's this all about. A little explanation is a lot to me. But what I am concerning about this thing is, it seems to be endless. PrPro had done already on all of my assets, conforming, creating peak files, indexing, but it still keeps on doing it again and again. Is there a problem with my audio/video files?
During the first time of my use, I didn't mind. I didn't even notice it. But now I started to be concerned with it since I my pc really slows down when PrPro starts this seemingly perpetual activity. If there's a problem somewhere else please help me.

Did you notice that you make the same mistake as one of our regulars here, the_wine_snob, otherwise known as Bill Hunt, in leaving out one 'a' in my last name? I'm not offended but wonder if that is a human trait to not overdo it and two 'a'-s may be too much?
I resemble that comment! Harm, you have to realize that I am from Mississippi, and everyone is known as Billy Bob, Joe Bob, or Bubba. We had no Harm Millaards - too many double vowels and consonants for us. At least this helped, when I signed up for a bunch of X-rated sites, as Harm Millard...
OK, where were we? LameTiger (check that spelling, as I think I got it wrong again and apologize profusely), when one has non-standard footage, three thing need to happen: the files need to be indexed, the Audio must be Conformed (CFA files) and the Waveform Display (PEK) files must be created. Depending on the number of files, their Duration and one's computer's speed this can take from moments, to maybe 20 mins.
If you have not just loaded up this Project, then gone for a cup of coffee, or tea, I urge you to do so. There is a tiny progress bar in the very lower-right of the GUI, that traces this. Let it happen, and be patient. I know that this sounds like a scene from the Karate Kid, but it's important. Many systems will crash, if one tried to do anything, before this process completes. I can work (albeit slowly), during the process. Many cannot.
Now, if you HAVE patiently waited this process out, and it has completed, AND the next session yields the exact same thing, then something is not quite right. Could be files getting moved, deleted, or otherwise not available to PrPro, or some setting in one's Scratch Disks, or some other problem.
Hope that a bit of patience, and a cup of Darjelling helps. Please let us know.
Good luck,
Hunt

Generating Peak File for...

Wow, this has been going on for 3-4 hours already.
Unacceptable, and I can't find any reference to this process in the Adobe Docs for PP. I have no idea where it is in the process. Is it almost done? Does it have another 12 hours to go? What is the deal with this? I have not touched my computer in hours.
I have a PP Project with about 10 bins with about 1 hour of video in each.
Should I break my project down so I have 10 PP files with 1 hour of video per project?
I was hoping to keep everything in one PP file, but that is looking like a really bad idea right now. I don't remember having to suffer through anything like with when working with Final Cut Pro.
Will these stupid Peak Files be saved? Is there a chance they will get corrupt and have to regenerate? This took a whole half day, and more, since it's still ongoing. This is on my MBP 2.4GHz. If I want to move the files back and forth between my laptop and my Windows Core i7 920 desktop (I have Production Premium on both platforms), will I have to suffer the Peak File Generation everytime?
All video was captured in OnLocation, straight from the camera. That part of the process seemed really cool. This part with the Peak File is really lame.
Any tips on getting to a workable workflow with PP, or should I just bag it, and buy another editor (Final Cut Express would even probably do the simple cut edits I want to do) ? I do most everything in After Effects.

count_schemula wrote:
The solution? I'm going to edit on my windows desktop.
OMG, what have I gotten myself into?
Same problem on my PC. Premiere Pro 4.2 on Windows 7 64 bit. Freshly installed. All legit software.
I made a new project, import all the video, and let it generate all peak files.
It finishes. Close Premeire. Open Premiere... Generating Peak File for...
My heart sinks so low.
I delete the .pek files and the database files and in the preferences, I set it to save cache and database files to a folder within my project folder.
It dutifully generates all new .pek file and database files. I watch it write them one by one. It does not write anything in the original Adobe shared cache folders. It completes. I quickly edit up one segment, just so I have some work to show for my 4 days of messing around with this.
Close Premiere. Open Premiere.
Generating Peak File for...
I'm speechless.
Footage was captured to disc using OnLocation on a Mac from a Panasonic AG-HVX200a via fireware.
If you want to call me an idiot, point out where I'm not doing something right.
If you want to blame my rig(s) just know that I push these systems hard daily with ZERO issues in other apps.
I'm blaming Premiere at this point. Something about how this program works is just not right. In both cases it writes over already existing .pek files. I have 4 channels per clip, so 4 .pek files for every clip I have. It's towards 1000. pek files.

Premiere freezes when generating peak file

Hi,
Anyone know who to solve this?
I started a project in FCP 7 on a mac, exported an XML and imported it into a Win 7 64bit machine running PPro 5.03 to finish the edit.
All media loads (about 500 files) but while generating the peak files eventually the program locks up and crashes. This occurs on one of the video files (but a different video file each time). Furthermore, the peak files regenerate every time I open the project.
I have write xmp on import unchecked.
All the files are located on a single external drive (esata), which I use on both machines. I'm using Mac drive so it can be read on the Win 7 machine.
I also have my scratch disc set to the same drive (maybe this is an issue?), although I have not had an issue with it before.
The footage - 1080p Pro Res 422 HQ
CPU specs
Quad Core 2.4
4gb DDR2 Ram
GT240
Thanks

Is that eSATA external formatted as FAT-32? If so, that is likely part of the issue. There is a ~ 4GB limit on file size on FAT-32, and while the PEK files will not likely exceed that limit, the CFA files likely will, depending on Duration.
Good luck,
Hunt

Premiere CS4 Pro Hangs - Generating peak file

Windows Vista Ultimate. Dell M1730 Intel X7900 2.8 GHz 4.0 gigs of memory Dual NVIDIA GeForce 8700M GT with SLI off 175 Gigs available on raid for speed drive
I basically opened 10.4 G 52 minute AVI file imported via MovieMaker. I wanted to cut two segments about 3 or four minutes.
I can progress a bit at time before I get a not responding lockup. Once a blue screen of death.
On the not responding I noticed the "generating peak file in lower right corner with a gold filled progress bar.
I am doing dragging a marked clip to the sequence, two and crashed each time. Also crashed in process of finding my start and end points a few times. Then I added a transition and crashed there as well.
Any suggestions to do this without crashing?

For BSOD, or program crashes and hangs, this ARTICLE might help you track down "clues," as to what is going wrong, when it goes wrong.
Good luck,
Hunt

Premiere project opened - closed sequences and generating new peak files

Hey guys,
I'm working on a big project, which resides on our Drobo. I have been sorting clips and working in sequences for the last couple days now. All media was loaded fine, and peak files were generated.
When I went to open the project this morning, all of the sequences I had been working on (accept for one) had been closed, instead of opening up like how I left them. Further, Premiere is now generating new audio peak files for the project, which is taking forever. Finally, it took 25 minutes to load all of the clips (about 800 or so). They finally finished loading, but I can't start working until the peak files are finished. All in all, i've been at work for 1 hour and still can't work.
Basically, why didn't Premiere open the project as I left it last night? Closed sequences, slow load time, generating new peak files?
I'm working with footage from RED, Sony FS700, GH4, and GoPro.
My system:
Creative Cloud
Premiere Pro 8.0.1
Windows 7 (64 bit)
Intel 3770k
Quadro k4000
16 gb ram
256 gb SSD (System)
256 gb SSD (Render files)
5.39 TB Drobo via USB 3.0
Thanks,
Dan

>Drobo via USB 3.0
Did you by any chance unplug/replug your USB drive?
Have you gone into Windows and "locked" the drive letter?

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]

Why does PS CC file crash every time i try to print?

PS CC file crashes every time i try to print. Ran a virus scan on file, saved as a JPEg and also tried saving to another location.......program crashes and closes every time i go to print file.

These questions below may be for a different product... but the KIND of information you need to supply is the same, for the products you use
More information needed for someone to help... please click below and provide the requested information
-Premiere Pro Video Editing Information FAQ http://forums.adobe.com/message/4200840

Rasterization of complex postscript-file crashes in 64-bit Photoshop CS5

Rasterization of complex PS-file crashes in 64-bit Photoshop CS5
I have a variety of complex postscript files that were created in Adobe InDesign CS3 and CS5 through "print to postscript file". I try to rasterize these files in Photoshop CS5 (64 bit on Macintosh) and it crashes Photoshop even before the dialog box comes where one has to specify the dpi for rasterizing. If I use Photoshop CS3 or Photoshop CS5 with 32 Bit opening, it does not crash; and in this case I can rasterize a 100cm x 160cm format with 300 dpi.
If I reduce the complexity to near triviality it works with the 64 bit version.
A major reason why I bought CS5 was because I thought that with the 64 bit version I can handle rasterization of large files better: there are a few minor artifacts created by rasterization in Photoshop 32 bit version which are presumably due to some memory problems; I thought the 64 bit version can solve it. But now it turns out that the 64 bit version cannot handle complex files at all.
If I use Distiller to convert the postscript-File into a pdf file, then the 64-bit version does the rasterization, but there are some reasons why I prefer the rasterization directly from the postscript file.
Is that a bug of the 64 version?
V.S.

I did a lot of testing in the meantime since we have often the task to printout large charts with complex content on plotters of medium size printing companies who need tiffs since they cannot handle pdfs with complex contents.
It turns out that for large charts with complex content the method to export from Indesign to pdf with PDF/X-1a profile and subsequent rasterization in photoshop to create the tiffs sometimes produces a few minor artifacts; mainly very thin white lines that you see in the printout. Also it is not good if your file contains graphics for which PDF/X-1a profile sometimes does not yield the desired high quality. (In addition the pdf file has a lot of display artifacts visible on screen but not manifesting in the rasterized photoshop file.)
The use of the "High Quality Print" profile (instead of PDF/X-1a profile) makes it worse since sometimes semi-transparent objects are printed as 100 percent solid. The solution in this case is to change the Acrobat 5 compatibility of the "High Quality Print" profile to Acrobat 4 compatibility, this solves the semi-transparent problem, I don't understand why, but it does.
On Macintosh one can print to pdf (instead of export to pdf), this solves all problems with artifacts as far as I can judge; however "print to pdf" has PDF/X-1a profile and I don't see any direct way how to change it to "High Quality Print" profile. Presumably I would have to locate somewhere in the Library > Adobe Application Support > Adobe (on Mac) the presets for "print to pdf" and change it if possible.
The easiest way on Macintosh that gives no artifacts is for large charts with complex content to "print to postscript" (with Adobe PDF 9.0 PPD), then use distiller with any suitable profile, like "PDF/X-1a-2001" profile or "High Quality Print" profile, to produce a pdf. This pdf looks fine on screen and simultaneously when rasterized with Photoshop (for example the 64 bit version of CS5) gives you a good photoshop file.
You may be right that the workflow
Indesign > print to postscript > pdf via distiller > rasterize to photoshop file
is outdated for simple and medium complex projects, but for those really complex large charts this is the only viable way to my knowledge; I also know that some of my colleagues use this sometimes for complex projects when export to pdf creates artifacts.
V.S.

I can't do anything when "generating peak file for..." ends.

After the reinstallation, I have a problem with "genarating peak file for.." , when it ends (when progress bar is full) the program stops and I can't do anything.
After the program is disabled, a message appears:
PhotoshopServer.exe - Błąd aplikacji
W aplikacji wystąpił wyjątek unknown software exception (0xc000000d) pod adresem 0x78138aa0
In English it may be:
PhotoshopServer.exe - Application Error
In application exception occurred unknown software exception (0xc000000d) at adress 0x78138aa0
What I should do?
I hope you understand what I mean.
Grettings Angelika.

Can you provide more information about your system, and the Assets that you are Importing?
This ARTICLE will give you some tips on the types of info that would be so useful.
Good luck, and welcome to the forum,
Hunt

Premiere CS3 Freezes when 'Generating Peak File' for Video Clips

Well the title explains it all really.
I'm importing a large 7.5 gb video file (.avi) and in the bottom corner it says 'Generating Peak File for xxxx'.
Which is fine until the bar is right at the end, and Premiere freezes on me and I have to end the process..
Thanks for your time!
George

Temporary storage.
You will also find links to many
free tutorials in the PremiereProPedia that will quickly show you how things are done in Premiere Pro.
Cheers
Eddie
PremiereProPedia (
RSS feed)
- Over 300 frequently answered questions
- Over 250 free tutorials
- Maintained by editors like
you
Forum FAQ

Playing wmv files crashes windows 7

playing wmv files crashes windows 7. same happens when online streaming video

Hi,
I recommend asking your question in the Windows forums here:
http://answers.microsoft.com/en-us/windows
This forum is meant for reporting issues with the MSDN/TechNet forums, not product support.
Good luck.
Don't retire TechNet! -
(Don't give up yet - 12,830+ strong and growing)

Scanned jpeg file crashes computer

I have a Canon 8800F printer. It's worked fine using Mavericks, but I just bought a new iMac that's running Yosemite (10.10.3) and it's been a nightmare.
At first the 8800F wasn't showing up at all, but I found directions about resetting the printing system and reinstalling the scanner. Now it shows up and I seemed to be able to scan using the Printers & Scanners system preference.
What's strange/awful is that when I click on the jpeg file that's created by the scanner it crashes the computer. I tried producing a tiff file instead, which opens up ok, but when I covert the tiff to jpeg the resulting jpeg file crashes the computer.
The other thing that I don't see an option for scanning transparencies. Under Mavericks I was using photoshop CS3, but that doesn't seem to be compatible with Yosemite.
Help!

I think that I discovered that this only happens when scanning at the highest resolution (9200). It's not a RAM issue, as I have no problem opening the TIFF, which is much bigger than the jpeg. Kind of a drag as I scan a lot of negatives and some single frames from proof sheets, and I've never had this problem before the new iMac/Yosemite.

Peak files crashing Premeire

Similar Messages

Maybe you are looking for