Media Encoder/Premiere Export Crashing During long file exports

I'm running Premiere Pro CC 2014 on a windows 7 computer--a Livestream Studio HD500. I use the computer to capture live video, which is saved as large AVI motion-jpeg files. I need to edit and export these files as compressed h.264 videos for upload to the web.
I am able to import these files into premiere and work with them, but the program crashes to desktop during any long export. I am able to export very short (1 or 2 minute) videos just fine, but anything longer will crash to desktop after a few minutes of processing. Media encoder also crashes when attempting to compress the videos prior to processing.
I have been able to circumvent this problem by compressing the files I'm working with in advance using virtualdub, but it adds an annoying step to the workflow that I'd like to eliminate. Shouldn't premiere be able to import, edit, and export compressed versions of these files without crashing?
Note: I've tried turning off GPU rendering and clearing my cache several times.
Thoughts? Much appreciated.

Maybe this problem?
http://blogs.adobe.com/kevinmonahan/2014/01/13/computer-shuts-down-with-premiere-pro-or-af ter-effects/

Similar Messages

Premier Pro CC and Media Encoder crashing on long file export.

Please forgive the length of this inquiry. But it is complicated and has a lot of variables.
I have an hour long mixed format timeline both Red 3K footage and Black Magic ProRes 1080P footage that I want to make a DVD from and it takes forever and crashes half way through. I have tried doing it every way possible and the only way I was able to get even a partial export was using the "MPEG 2 DVD" export option in Premier CC. It goes fast at first telling me it will take about 2 hours but even though it starts quickly doing about 15 fps it slows down to less than 1 fps and finally just stops and crashes my Cuda Core enabled Macbook Pro Laptop.
I really don't know who to ask about this since there are so many different variables. I never had a problem like this on my MBP with PP6 on a 4K timeline exporting to DVD or Blue Ray or to H-264 or Even Prores. But I wasn't mixing formats either. But on this project the first 20-30 minutes of footage goes through fine in a couple of hours but something seems to be bogging down the system on longer projects. My work around was to break the project up into multiple exports and combining them on the DVD timeline but I can't do this on every project. I thought maybe it was a corrupted clip somewhere in the timeline but when I broke the timeline up into several parts I had no problems.
I did notice a dramatic variance in the time it took to export footage based on the sequence settings. A one minute timeline comprised Red 3K footage and ProRes 1080P footage Here are some sample export results:
From a Red raw 3K timeline 2880x1620 with 1080P Prores footage upscaled 150%)
to .m2v Mpeg 2 720x480 format    1:48 Minutes ***
to .mov Prores 422HQ 1080P                         22 Minutes
to .mov H.264 1080P                    22 Minutes
to .m2v Mpeg 2 1080P                                                22 Minutes
From a 1080P timeline Prores footage at 100% (Red footage downscaled to 67%)
to .m2v Mpeg 2 720x480 format                         13 Minutes
to .mov Prores 422HQ 1080P                             13 Minutes
to .mov H.264 1080P                                                             14 Minutes
to .m2v Mpeg 2 1080P                                                            14 Minutes
Since I am going to DVD, I chose the fastest option Red to m2v Mpeg 2 720x480 format which only took 1:48 per minute. Why? I have no idea. Maybe someone here knows the answer. But again these numbers are for a ONE MINUTE clip when I tried to convert the whole hour timeline to the 720x480.m2v DVD File the Red timeline froze my computer after several hours even though I had set sleep mode to “Never” and turned the display off manually and I had to convert it in multiple chunks. In 20-30 minute chunks it did go fast about 1:48 per minute like the test indicated. But I would like to be able to convert the whole hour and not to have to try to stitch the clips together in my DVD authoring program.
I don’t want to have to avoid using multiple formats on the same timeline or waste time transcoding everything to the same format.
Can anyone give me any suggestions as to why the computer is crashing or bogging down in long exports and what timeline settings I should be using?
I have plenty of room on my Scratch Disk and 8 Gig of RAM and according to my Activity Monitor during the export process have about 800 Meg of System Memory during export but the CPU Usage is 98% and in my Activity Monitor I see under “Process Name” ImporterRedServer flashing up at the top of the list about every second during export.
Why .720x480 mpeg DVD setting is so much faster than all the other export codecs?
And if there are any other settings I can use to get higher speed exports in HD? 14x1 seems a little slow especially since every time it crashes I have to start over.

Hi,
Since a long time I did not encounter the crash of Media encoder with
long file export.
But I take care of a lot of details before the export :
- clean up Media cache and Media Cache Files within PP CS6 and/or CC,
- delete all render files with Preview Files,
- rendering of sequences until the rendering is completed,
- PP CS6 and/or Pp CC opened during export to AME and/or Encore CS6,
I guessed to leave Adobe but this company remains the last with a
serious authoring software (Encore CS 6).
I tested :
- Avid Media Composer, Final Cut Pro X, both are very good software but
no really authoring software for these video editing softs.
Th only way is to "flood" Adobe with "bug reports" and "wish forms"
which are not very easy to use.
And also to call the Adobe support day by day until they send they
escalate the bug.
Le 16/05/2014 16:51, alainmaiki a écrit :
>
      Premier Pro CC and Media Encoder crashing on long file export.
created by alainmaiki <https://forums.adobe.com/people/alainmaiki> in
/Premiere Pro/ - View the full discussion
<https://forums.adobe.com/message/6384665#6384665>

Premiere CS4 crashes/freezes upon File Export Media click

My system:
CS4 master collection. I have some remnants of CS3 on my computer.
4 Gig RAM
Quad Core processor
Vista
My problem:
Problem started yesterday and I've tried a lot of things but can't figure this out. When I click File>Export>Media, premiere greys out most panels and nothing can be clicked. It gives a beep of death on every click. I need to use task manager to close premiere. The only thing I've found I am able to do is click escape, which returns me to my project as if nothing has happened.
I've tried a range of different projects, including a brand new one with nothing in it except a 10 second DV avi file. Same problem across the board.
I've reinstalled CS4 Master collection but didn't uninstall it first. No change. Would it help to uninstall everything and start from scratch?
Never had this problem before.
It also does the same thing on file>export>clipnotes but I CAN export an EDL.
The only change to my PC between this not happening and it happening was I installed the new music streaming software 'Spotify'. I have since uninstalled this but it hasn't fixed it.
If anyone has any ideas, I'd be hugely grateful.
Ed

Hey Ed, I had replied earlier in the other thread you posted in and just noticed you started a new topic here, so, copied from the other thread:
I had something similar happen to me a few times... if the escape key is taking you back to premiere and returning everything to normal, then your computer is not really hanging or crashing. What most likely is happening is that Premiere is opening a dialog box OFF SCREEN, so you just can't see it or click on it to attend to what it's asking. Hitting escape is like hitting cancel, which returns you to your project.
To fix: just mess around with your monitor setups in your display panel, ie.: if you have a dual monitor setup, temporarily disable one monitor - forcing everything to open on one screen. And/Or set your screen resolution to the maximum your video card allows so that you may uncover the off screen space the dialog opens on. OR... you're video card may have a control panel with the option of forcing all windows onto one screen or preventing off screen display. Basically do whatever it takes to get a view of off your screen.
Once you discover that missing window, make sure you move it onto your primary display, somewhere in the center, and the next time you try to encode it should be right where it should be.
Good luck.

Adobe Media Encoder CC constantly crashing during batch encodes

Hello!
We just made the big switch to Premiere Pro CC for our TV shows and now that it's time to finalize our first few episodes we are having some major problems batch exporting segments of the show. Sometimes it works, sometimes it works half way through the batch list then crashes, sometimes it crashes right away. There is no consistency, other than crashes are happening all the time. Here's what is happening:
• AME 7.2.0.43 (64-bit)
• Mac OS X 10.9.1 on 2x2.66 GHx 6-Core Intel Xeon, 40 GB 1333MHz DDR3 RAM
• Startup disk is SSD w/ 4GB free space (all footage is on external storage)
• Using Premiere Pro CC to export via AME.
• All recent updates insatlled as of 3/10/14.
The source footage is ProRes 422 720p 59.94 footage from AJA KiPros. Each project has 16 segments - these are individual sequences. There are 7 tracks of audio and 4-5 tracks of video in each. In addition to the video there are targa files that include the score bug, full screen graphics, etc (this is sports). There are also some Adoby Dynamic Link After Effects elements throughout.
Editing has been fairly crashless - however when I File > Export > Media and queue it up in AME, that's when the fun starts.
I can rarely get through an entire batch list - generally within a few files the preview window at the bottom shows that it has halted and nothing further will encode. There is no way to stop or close the program without force quitting. When I have tried to encode from Premiere Pro CC directly, it works, although it is much slower and will only do the one sequence at a time.
I have been trying to encode to two different formats from within AME:
1.) ProRes 422 720 59.94 (just like the source footage) with 4 channels of audio.
2.) ProRes 422 1080i29.97 with 4 channels of audio.
We have different broadcast partners so we need to deliver in these two difference specs. I get crashes regularly on both outputs.
Possibly unrelated but also weird - I've noticed that when AME starts this crashing cycle sometimes Premiere CC won't let me save anyome. The status bar comes up like it's going to save the project but it goes nowhere. I have to quit without saving. Weird.
Can anyone help me further troubleshoot? This is bordering near deal breaker to continue using this software if I have this much trouble when trying to get my project outputted. Thank you!

Agreed, I now have a project to GET OUT, and AME crashes consistently 1/3 into the render. It appears to halt all processing after (real time) 00:02:30
Am seriously considering uninstalling CC as I am beginning to find other issues in some apps, and going back to CS6/MC just so I can get work out. Durn it Adobe this is AWFUL!!
Alright, let's try to be constructive instead of throwing rocks... but the frustration level is high, and I have material on deadline. Let's get with this, guys...
What OS Win7, 64-bit
What version of AME/PPro (Please be specific by getting the full version number in the About Adobe Media Encoder screen) 8.2.0.54 Ppro: 8.2.0 (65)
When is it crashing (Again, the more detail here about where it was in the encoding process the better) roughly 1/3 into the sequence, always on exactly the same frame - tried replacing the clip with something different to see if it was a timeline error, and NO EFFECT.
What is your source (PPro project or media file (what kind?)) PPro
If the source if a PPro project, does it work when exporting directly from PPro? NO
What format are you exporting to? H.264, QT, WM, tried everything my client can play.
Do other formats work? MPEG2, QuickTime, etc? NO
Have you tried with GPU rendering on? How about turning it off by switching to Software-only mode? Mine doesn't have any choice, it's software-only.
Have you tried disabling Native Sequence Loading? (AME Preferences: General > Enable Native Sequence Loading) No effect
Other things I tried: uninstalling/reinstalling AME, setting cache to a fast local disk.

GB crashing during large file export

GB 09 is crashing during an export of a project that is 2 hours and 20 min. I've tried diff export settings but the program still quits when it reaches about 3/4 of the project length.
No crashes in the past. Been exporting the project to rough cuts at various lengths from1 hour to 1 1/2, but upon finalizing the project, which happen to total over 2 hours, it can't make it through an export.
It's an audio book - talking only -no effects, other instruments, very straight forward.
I've tried exporting from the master .book file and a version with all the clips joined, tracks locked, and extra stuff deleted for project.
Here is some of the crash report (just pasting the first page of the crash report).
Process: GarageBand [2716]
Path: /Applications/GarageBand.app/Contents/MacOS/GarageBand
Identifier: com.apple.garageband
Version: 5.1 (398)
Build Info: GarageBand_App-3980000~2
Code Type: X86 (Native)
Parent Process: launchd [138]
Date/Time: 2010-03-29 11:14:16.969 -0400
OS Version: Mac OS X 10.6.2 (10C540)
Report Version: 6
Interval Since Last Report: 1758706 sec
Crashes Since Last Report: 39
Per-App Interval Since Last Report: 219501 sec
Per-App Crashes Since Last Report: 6
Exception Type: EXC_BREAKPOINT (SIGTRAP)
Exception Codes: 0x0000000000000002, 0x0000000000000000
Crashed Thread: 0 Dispatch queue: com.apple.main-thread
Thread 0 Crashed: Dispatch queue: com.apple.main-thread
0 com.apple.CoreFoundation 0x94dd0554 CFRelease + 196
1 com.apple.AppKit 0x9468967a -[NSBitmapImageRep initWithFocusedViewRect:] + 2257
2 com.apple.garageband 0x001f5fea 0x1000 + 2052074
3 com.apple.garageband 0x00205650 0x1000 + 2115152
4 com.apple.garageband 0x0014f7c2 0x1000 + 1370050
5 com.apple.garageband 0x0015a58a 0x1000 + 1414538
6 com.apple.AppKit 0x945edb6c -[NSView _drawRect:clip:] + 3721
7 com.apple.AppKit 0x945eb238 -[NSView _recursiveDisplayRectIfNeededIgnoringOpacity:isVisibleRect:rectIsVisibleRectFor View:topView:] + 2217
8 com.apple.AppKit 0x945ebbcb -[NSView _recursiveDisplayRectIfNeededIgnoringOpacity:isVisibleRect:rectIsVisibleRectFor View:topView:] + 4668
9 com.apple.AppKit 0x945ebbcb -[NSView _recursiveDisplayRectIfNeededIgnoringOpacity:isVisibleRect:rectIsVisibleRectFor View:topView:] + 4668
10 com.apple.AppKit 0x945ebbcb -[NSView _recursiveDisplayRectIfNeededIgnoringOpacity:isVisibleRect:rectIsVisibleRectFor View:topView:] + 4668
11 com.apple.AppKit 0x945ebbcb -[NSView _recursiveDisplayRectIfNeededIgnoringOpacity:isVisibleRect:rectIsVisibleRectFor View:topView:] + 4668
12 com.apple.AppKit 0x945ebbcb -[NSView _recursiveDisplayRectIfNeededIgnoringOpacity:isVisibleRect:rectIsVisibleRectFor View:topView:] + 4668
13 com.apple.AppKit 0x945ebbcb -[NSView _recursiveDisplayRectIfNeededIgnoringOpacity:isVisibleRect:rectIsVisibleRectFor View:topView:] + 4668
14 com.apple.AppKit 0x945ebbcb -[NSView _recursiveDisplayRectIfNeededIgnoringOpacity:isVisibleRect:rectIsVisibleRectFor View:topView:] + 4668
15 com.apple.AppKit 0x945ebbcb -[NSView _recursiveDisplayRectIfNeededIgnoringOpacity:isVisibleRect:rectIsVisibleRectFor View:topView:] + 4668
16 com.apple.AppKit 0x945ebbcb -[NSView _recursiveDisplayRectIfNeededIgnoringOpacity:isVisibleRect:rectIsVisibleRectFor View:topView:] + 4668
17 com.apple.AppKit 0x945ebbcb -[NSView _recursiveDisplayRectIfNeededIgnoringOpacity:isVisibleRect:rectIsVisibleRectFor View:topView:] + 4668
18 com.apple.AppKit 0x945ebbcb -[NSView _recursiveDisplayRectIfNeededIgnoringOpacity:isVisibleRect:rectIsVisibleRectFor View:topView:] + 4668
19 com.apple.AppKit 0x945ebbcb -[NSView _recursiveDisplayRectIfNeededIgnoringOpacity:isVisibleRect:rectIsVisibleRectFor View:topView:] + 4668
20 com.apple.AppKit 0x94689b5f -[NSNextStepFrame _recursiveDisplayRectIfNeededIgnoringOpacity:isVisibleRect:rectIsVisibleRectFor View:topView:] + 311
21 com.apple.AppKit 0x945e7111 -[NSView _displayRectIgnoringOpacity:isVisibleRect:rectIsVisibleRectForView:] + 3309
22 com.apple.AppKit 0x94547d6e -[NSView displayIfNeeded] + 818
23 com.apple.AppKit 0x944fb9c5 -[NSNextStepFrame displayIfNeeded] + 98
24 com.apple.AppKit 0x94511094 -[NSWindow displayIfNeeded] + 204
25 com.apple.AppKit 0x945425aa _handleWindowNeedsDisplay + 696
26 com.apple.CoreFoundation 0x94e43892 __CFRunLoopDoObservers + 1186
27 com.apple.CoreFoundation 0x94e0018d __CFRunLoopRun + 557
28 com.apple.CoreFoundation 0x94dff864 CFRunLoopRunSpecific + 452
29 com.apple.CoreFoundation 0x94dff691 CFRunLoopRunInMode + 97

Sorry about listing too much data from the GB crash report.
Anyone have trouble shooing tips for crashing during large mix downs/exports?
The file that crashes during export is over 2 hours long, but only 1 voice track with no effects!

Premiere CC 7.2.2 crashes when trying to export via Media Encoder and Encore crashes while DVD build

Hello,
My computer is a:
2x Intel Xeon Processor E5-2650 (2000 MHz, 20MB);
16x Kingston DIMM 8 GB PC3-8500 ECC Reg.;
PNY Quadro 4000 with 2048 MB GDDR5-RAM;
PNY Tesla C 2075
2x 2000 GB Western Digital RE4 (7200 UPM/S-ATA II) as a RAID I
1x 120 GB OCZ Vertex 3 SSD
1x 240 GB OCZ Vertex 3 SSD (system disk)
Tyan S7050GM4NR motherboard
Windows 7
I freshly installed Windows 7 and the CC-Apps PremierePro, After Effects, Media Encoder, Photoshop and Speedgrade.
When I try to export any video from premiere to the media encoder premiere crashes without any error message. The problem is not the project: I created several new projects and even if I only have one Graphic-File/Bars/h264-video in the timeline that I try to export: premiere crashes. When I export directly from premiere it works, but there is no chance to go via media encoder. The strange thing is that I can export from after effects to the media encoder without any problem...
Second Problem: Encore crashes also. Everytime I try to build a DVD => Encore crashes
Does anybody have an idea?
Here is what I already tried:
Yesterday it worked fine today it crashes when I export from premiere via media encoder.
1. Bars+Tone => export => crash
2. Video Project with 2 short h264-files => export => crash
3. I used Software only renderer => crash
This is the Windows log that I found:
Ereignis-ID 1000
EventXML
param1
WmiApRpl
param2
WmiApRpl
binaryDataSize
16
binaryData
38270000DE27000039270000DF270000
So it would be great if you have any idea what to do...
System
Provider
[ Name]
Microsoft-Windows-LoadPerf
[ Guid]
{122EE297-BB47-41AE-B265-1CA8D1886D40}
EventID
1000
Version
0
Level
4
Task
0
Opcode
0
Keywords
0x8000000000000000
TimeCreated
[ SystemTime]
2014-04-16T08:25:51.922502600Z
EventRecordID
3402
Correlation
Execution
[ ProcessID]
19984
[ ThreadID]
24964
Channel
Application
Computer
Schnittplatz
Security
[ UserID]
S-1-5-18
UserData
Die Leistungsindikatoren für den Dienst WmiApRpl (WmiApRpl) wurden erfolgreich geladen. Die Eintragsdaten im Datenbereich enthalten die neuen Indexwerte, die diesem Dienst zugeordnet sind.

The Error is back!!!
Yesterday it worked today it crashes when I export from premiere via media encoder. I tried it with all the things you told me:
1. Bars+Tone => export => crash
2. Video Project with 2 short h264-files => export => crash
3. Software only renderer => crash
These are the two logs that I found:
Ereignis-ID 1000
Die Leistungsindikatoren für den Dienst WmiApRpl (WmiApRpl) wurden erfolgreich geladen. Die Eintragsdaten im Datenbereich enthalten die neuen Indexwerte, die diesem Dienst zugeordnet sind.
System
Provider
[ Name]
Microsoft-Windows-LoadPerf
[ Guid]
{122EE297-BB47-41AE-B265-1CA8D1886D40}
EventID
1000
Version
0
Level
4
Task
0
Opcode
0
Keywords
0x8000000000000000
TimeCreated
[ SystemTime]
2014-04-16T08:25:51.922502600Z
EventRecordID
3402
Correlation
Execution
[ ProcessID]
19984
[ ThreadID]
24964
Channel
Application
Computer
Schnittplatz
Security
[ UserID]
S-1-5-18
UserData
EventXML
param1
WmiApRpl
param2
WmiApRpl
binaryDataSize
16
binaryData
38270000DE27000039270000DF270000
So it would be great if you have any idea what to do...

Both After Effects & Adobe Media Encode CC giving are not letting me export.

Dear All,
Both After Effects & Adobe Media Encode CC giving are not letting me export movies.
Some times they will, but after one file both programs give me the following error messages.
After effects:
“[file path and name].mov. An output module failed. The file may be damaged or corrupted. (-1610153464)"
AME:
"Can't read from source."
I've went through the forum and found threads & pages discussing the problem.
E.g.
http://blogs.adobe.com/aftereffects/2013/08/solutions-for-problems-with-quicktime-files-in -after-effects-cc-12-0-because-of-conflict-with-dvcprohdvideoout-quicktime-component.html
http://forums.adobe.com/thread/1252092
After following all the tips and suggestions (from deinstalling quicktime components & audio components to completely reinstalling CC) I'm still experiencing the problems.
Which leaves me in a bit of a squeeze. I need to export over 144 movies in the coming 2 days and the only way to do this is to quit and open media encoder (or AE) after each single export.
Not really an option.
Both problems have the process Adobe QT sever in common, I took this from the console:
9/26/13 1:02:44.517 PM com.apple.launchd.peruser.501[171]: ([0x0-0x42042].com.adobe.Adobe QT32 Server.application[331]) Job appears to have crashed: Segmentation fault: 11
9/26/13 1:02:44.672 PM ReportCrash[354]: Saved crash report for Adobe QT32 Server[331] version 7.0.1 (7.0.1.0) to /Users/martijn/Library/Logs/DiagnosticReports/Adobe QT32 Server_2013-09-26-130244_martijns-MacBook-Pro-2.crash
System information:
Retina MacBook Pro (Mid 2012) (16gb ram)
Mac OS X 10.8.5 (12F37)
Running Adobe CC (for teams), all apps are up-to-date.
I don't no why Adobe puts out such a buggy piece of software (I know it has to with Apple's poor 32bit quicktime implimentation, but hey, this was known information no?).
Upgrading to CC has given our office nothing but problems.
Hope someone can help to find a work around until Adobe realeases a proper update and solves this problem once and for all.
All help is much appreciated.
Kind regards,
Martijn

Hello Tim,
Thanks for the really quick response!
Regarding the crash log: it doesn't reference com.apple.audio.CoreAudio (though it did before, so I followed all the steps in your blog post before I posted to this forum).
I've uploaded the crashlog to:
http://martijnlambada.com/TMP/AdobeQT32servercrash.zip
If you want to inspect it. It mentions the DXV codec (which I also uninstalled), but the crash keeps occuring. Also I need to export to DXV since it's the only codec the d3 media
server accepts (http://d3technologies.com).
I followed all the steps in the troubleshooting steps.
Codecs used: I've tried everything from animation to Apple ProRes (including: h264/motion jpeg/uncompressed). With all codecs the Adobe QT32 server keeps crashing (though I can't always reproduce).
Export destination: Internal SSD (same as where the OS is installed on) + External raid (via firewire & thunderbolt) + external HD via usb 3.0 (tried everything).
When does the problem start: Really hard to specify, sometimes a day without crashes, sometimes every export for days on end. Sometime after restarting (tried logging out, restarting, switching off and on the computer). With other programs running and with out. Now checking every process active when exporting, and comparing log files.
Can you export to other formats: See question 1, sometimes I can, sometimes not.
When you launch AE and/or AME, is QT32 Server running? At what point does it stop running? Still runing when I open the program. It crashes when exporting (ofter after finishing the first export).
What component files are in your Library/QuickTime folder?: Currently the folowing:
AppleAVCIntraCodec
AppleHDVCodec.component
AppleIntermediateCodec.component
AppleMPEG2Codec.component
AppleProResCodec.component
DesktopVideoOut.component
DVCPROHDCodec.component
DVCPROHDMuxer.component
DVCPROHDVideoDigitizer.component
DVCPROHDVideoOutput.component
DVCPROHDVideoOutputClock.component
FCP Uncompressed 422.component
iChatTheaterPreview.component
IMXCodec.component
LiveType.component
Hope this helps.
Cheers,
Martijn

Urgent : Plantage constant de Media encoder, premiere pro CC et CC2014.

Bonjour à tous !
Je rencontre de grosses difficultés avec Premier Pro et média encoder CC et CC2014.
Lorsque je veux mettre en fil d’attente mes projets que je passe par Fichier>Importer (composition After ou même Première) ou que je fasse simplement un glisser/déplacer dans Media Encoder....Une fois sur deux ça plante, ne chargeant pas Dynamique link, ou plantage de première pro..... Avec les versions CC comme 2014....Je n'ai pas de message d'erreur particulier. En revanche je suis obligé de killer les processus Dynamique link, adobe (en général : Qt32 server, Adobe ipCbrocker, PProHeadless.exe) via le gestionnaire de tache Windows. Sinon impossible de réouvrir les logiciels.
J'ai d'ailleurs remarqué que même lorsque les logiciels ne plantent pas, que je ferme premiere ou afx ou autre, les logiciels ne s’enlèvent pas des Processus, il reste ad vitam aeternam, dans les processus actif.
Lorsque j'arrive quand même à importer mes séquences dans MediaEncoder, celui-ci plante certains encodages mais pas tous....sans raison particulière et ne me disant pas pourquoi il les a planté. S’il ne les plante pas, il tourne en boucle sur la même image et je suis obligé d’arrêter moi-même l'encodage, qui ne se finira jamais. Sachant que tous mes fichiers font parties d'une série, qu'il y a donc exactement la même choses dedans en terme de montage, effet etc. Ce qui en passant n'est que du fondu....
Mes Rush sont des fichiers MXF. Et j'utilise le dynamique Link pour mes imports de séquences entre première et afx. Bien que ça me fasse exactement le même problème que j'importe directement mon première ou que je passe par dynamique Link.
Aussi, autre problème lorsqu'il accepte d'exporter (Media encoder j'entend). Il ne m'exporte pas forcement tous le son, il va m'exporter la première séquence par exemple l'intro, puis tous le reste de la vidéo qui est dans une autre séquence et compo, il ne l'exporte pas........
Je ne sais plus quoi faire la. Au prix ou est vendu cette suite franchement !
Je suis donc sur :
Windos Seven PRo 64Bits.
J'ai un i7 X980 3.33GHZ
Une Nvidia GTX480 driver 337.88 (les derniers quoi)
ET 16 Go de RAm
Mon cache n'est pas plein, je le vide régulièrement. Il est sur un disque au regard des projets, et ne bouge jamais.
Voilà, si jamais quelqu'un a le même problème, ou connait une solution, je suis preneur.
Ça tombe au plus mauvais moment, j'ai 200 vidéos à encoder pour dans 1 Mois.
Merci d'avance.
A.H
Message was edited by: aurel motiond

Il ne sert pas à grand chose ce forum, sans vouloir être offensant....

Cannot export to reporting schema (File - Export - To Reporting Schema )

I just installed SQL Data Modeler version 2.0.0 Build 584
Export to reporting schema (File -> Export -> To Reporting Schema ) is not working.
I created a report schema and tried to export the Sql Data Modeler (SDM) repository to the Oracle schema.
I received the following error from SDM: "Error occured while exporting to Reporting Schema. See the log for details".
I checked the log ( View -> Log ) and all the log contained was "2010-01-18 11:10:23 - Exporting to Reports Schema"
The reports schema contained 44 tables. None of the tables contain any data.
I can create a test table and add data to it in the reporting schema. There is lots of quota available to the reports schema.
I have tried the report export to Oracle several times with the former version with mixed results.
Any suggestion? Does the "export to reporting schema" work for anyone else?
The following script from TOAD describes the reports schema.
CREATE USER SDM_REPORT
IDENTIFIED BY <password>
DEFAULT TABLESPACE USERS
TEMPORARY TABLESPACE TEMP
PROFILE DEFAULT
ACCOUNT UNLOCK;
-- 2 Roles for SDM_REPORT
GRANT CONNECT TO SDM_REPORT;
GRANT RESOURCE TO SDM_REPORT;
ALTER USER SDM_REPORT DEFAULT ROLE ALL;
-- 15 System Privileges for SDM_REPORT
GRANT CREATE TRIGGER TO SDM_REPORT;
GRANT CREATE PROCEDURE TO SDM_REPORT;
GRANT DROP PUBLIC SYNONYM TO SDM_REPORT;
GRANT DEBUG CONNECT SESSION TO SDM_REPORT;
GRANT CREATE MATERIALIZED VIEW TO SDM_REPORT;
GRANT CREATE TABLE TO SDM_REPORT;
GRANT CREATE SESSION TO SDM_REPORT;
GRANT SELECT ANY DICTIONARY TO SDM_REPORT;
GRANT CREATE ROLE TO SDM_REPORT;
GRANT CREATE VIEW TO SDM_REPORT;
GRANT CREATE TYPE TO SDM_REPORT;
GRANT CREATE SEQUENCE TO SDM_REPORT;
GRANT CREATE PUBLIC SYNONYM TO SDM_REPORT;
GRANT CREATE ANY SYNONYM TO SDM_REPORT;
GRANT UNLIMITED TABLESPACE TO SDM_REPORT;
-- 1 Tablespace Quota for SDM_REPORT
ALTER USER SDM_REPORT QUOTA UNLIMITED ON USERS;

Problem solved: Data Modeler would export other designs to an Oracle schema but not the one I was working on (Babylon). I saved a copy of Babylon, BabylonReports and deleted everything except the relational model. Then I could export it to the repository. I assume that either the logical model or dataflow model had a problem which prevented Data Modeler from saving the export. Next time I'll run Design Rules to see if there is an error I can eliminate that will allow me to save an export.

GoPro Cineform files cause Premiere to crash during Media Export

I first noticed this problem when using a project that had been copied and transcoded with GoPro codec as demonstrated in Dave Henly's helpful video. The codec is indeed beautiful.
However, 50% to 80% of the time when trying to export a project where there are GoPro files on the timeline, it'll get about halfway through the export before Premiere (or Media Encoder) simply freezes up.
I didn't know what was causing this problem until I was using one large GoPro-exported video as the new base layer for a project that had otherwise been working perfectly prior to that (using Canon 60D-created .mov files). Now it was crashing during every export. On a hunch, I re-exported that base layer as an h264 file and replaced the GoPro video on the timeline, and now the project exports out just fine.
Is this happening to anyone else? I'm using just the standard 8bit GoPro preset whenever I export out or transcode clips.
I'm using Premiere Pro CC, whatever the up-to-date version number is right now.
Windows 8.
24 gb RAM.
GeForce Titan Black
Intel Core i7

Similar problem.
The new feature rendering a ae comp inside premiere timeline is perfect, but using gopro cineform codec crashes premiere on export.

Premiere Pro crashes when sending files to media encoder

Premiere Pro CC keeps crashing when sending files to Media Encoder. This is a new problem. I cleaned the cache, typed purge into terminal, checked the sharing in the preferences library and verified/repaired disk permissions. What else can I try? Help, I have urgent deadlines this week!

I am using the most updated version of PPro CC with OS 10.8.5. It seems to have issues with certain sequences and not others. It also may be the files themselves. They play fine in the program viewer and I have sent them to Media Encoder before, but if I create a new sequence with the same settings and copy the files into it, the same thing happens. I have a lot of 29.97 720x480 (1.21 pixels) and 1440x1080 (PAR 1.333) footage to edit together and create dvds out of (not my idea - it's a job) and I am in the middle of trying various ways of encoding to make it as clear as possible.
Currently I am using 1440x1080i HD anamorphic sequence settings encoding into 1440x1080 p HD anamorphic with frame blending, maximum render quality, Target bit rate of 30 VBR 2 pass. Then combining those files with other sequences into a longer 1440x1080 p HD anamorphic sequence and encoding MPEG 2-DVD NTSC widescreen progressive 100% quality, VBR 2 pass and the output is much better. This has been working, and today suddenly it stopped and started crashing. Any ideas?

Premiere Pro CC 2014 and Media Encoder CC 2014 Crashing constantly

Running out of options and ideas...
Symptom: Every time I work on any project in Premiere Pro CC 2014 or try to render out in Premiere Pro CC 2014 or Media Encoder CC 2014, the software crashes after 2-3 minutes of use/rendering when the GPU is enabled in Premiere/Media Encoder, or after 5-10 minutes of use/rendering in software only mode. The crash is a software crash, Windows continues to run fine.
I have tried all the standard list of steps that adobe reps post on threads like these - clearing media cache, software only on render, new project, etc. https://helpx.adobe.com/x-productkb/global/troubleshoot-system-errors-freezes-windows.html
Windows event is not that helpful to me:
Faulting application name: Adobe Premiere Pro.exe, version: 8.2.0.65, time stamp: 0x5486db4a
Faulting module name: unknown, version: 0.0.0.0, time stamp: 0x00000000
Exception code: 0xc0000005
Fault offset: 0x00007ff5ecb4de40
Faulting process id: 0x1dc8
Faulting application start time: 0x01d04a503cd82df2
Faulting application path: C:\Program Files\Adobe\Adobe Premiere Pro CC 2014\Adobe Premiere Pro.exe
Faulting module path: unknown
Report Id: cacdfbab-b717-11e4-826d-8863dfc268bc
Faulting package full name:
Faulting package-relative application ID:
I have wiped adobe off the machine and reinstalled - same problem. I have tried projects that crash the machine on other machines and it works fine.
The machine is new, clean install and runs everything else great - 3ds max, high res games, scientific computing - max memory use, etc.
Spec:
5K iMac running bootcamp and Windows 8.1
Intel Core i7-4790K @ 4.0 GHz
32 GB ram
1TB SSD
AMD Radeon R9 M295X 4GB GDDR5
I have used this bootcamp/imac configuration for 5+ years on 3-4 machines and everything has always just worked great. Guess it was my time for a problem, but I'm open to new ideas to try...
Finally - I hope someone from Adobe reads this. I have spent 2 nights on the phone with support. The first night I got an over confident answer that it's a gpu driver issue, just go with software only (no luck - same crashes and different drivers aren't solving the problem). Tonight I was hung up on "by accident" as the agent looked up my video card after waiting 15 minutes to talk to someone, only to be hung up on a second time while on hold after calling back and waiting 20 minutes (because I assume the Adobe call center closed). No message to say so, just hung up on. An overall very disappointing experience.
Thanks in advance to anyone with ideas on things to try,
Cheers!

I am having a similar problem.
Premiere Pro CC 2014 suddenly decided to crash every time I export to either Adobe Media Encoder or within Premiere itself.
The encode will usually go for 5-10 minutes before the programs either spits out a "serious error has occurred" window, or it just sits there frozen until I force quit.
I did find a work-around for the moment. If I open AME and FILE > OPEN, select my project and then the sequence I want, AND put it in Software render mode, it will work.
My timeline is 2K, 58 minutes in 23.976
Only effects applied are Lumetri LUTs - no third party.
I've exported as recently as a week ago without issue.
Running OSX 9.5 on an X99 board
3.75 GHz 8-core
64GB 2400 MHz RAM
EVGA Titan Black 6GB
Because I can get my renders out, I am not too concerned. Either there is something wonky with my timeline that screws with any graphics enabled rendering, or there is a bug that is have the same effect. I will try rendering on another of my edit bays that utilizes a GTX 580 that I KNOW works. The Titan is pretty new to my workflow.
Thanks Adobe, for checking this out.

Media Encoder CC2014.2 crash on windows when trying to export when quicktime is installed

Hi,
I'm trying to export .mov files (created on random Mac computers in very hi-res) to reduce file size, and have the same output format. (possibly 1080p H.264-> .mp4)
I installed Media Encoder cc2014.2 on my pc (win7, 64bits, french).
When I first tested, Only the audio was being exported. But I soon realized I didn't had the proper codec installed on my PC.
(I wasn't able to play the original video file, only the audio was playing).
So, like a good boy I installed Apple Quicktime (7.76.80.95)
With quicktime on my PC I was able to play the original video file. (with quicktime player)
So I opened Media Encoder again, and on the preview this time I can see the video with the sound. But as soon as I start the coding (the little green arrow) Adobe Media Encoder crash.
I have tried multiple output format, it always crash right when I start exporting the file.
I uninstalled Quicktime, and media encoder is working again ... but my original files (.mov) can't be exported with video, only the sound.
I have tried a third party codec (K-Lite), I can see the video+sound on my pc, but Media Encoder is still blind, no video, only the sound.
Is there a way to add codec to Media encoder without having to install Quicktime?
Or a way to make Media Encoder work on my PC when Quicktime is installed?
btw I'm sorry if my text is a bit confusing, I'm french speaking
Thank's in advance!

The Error is back!!!
Yesterday it worked today it crashes when I export from premiere via media encoder. I tried it with all the things you told me:
1. Bars+Tone => export => crash
2. Video Project with 2 short h264-files => export => crash
3. Software only renderer => crash
These are the two logs that I found:
Ereignis-ID 1000
Die Leistungsindikatoren für den Dienst WmiApRpl (WmiApRpl) wurden erfolgreich geladen. Die Eintragsdaten im Datenbereich enthalten die neuen Indexwerte, die diesem Dienst zugeordnet sind.
System
Provider
[ Name]
Microsoft-Windows-LoadPerf
[ Guid]
{122EE297-BB47-41AE-B265-1CA8D1886D40}
EventID
1000
Version
0
Level
4
Task
0
Opcode
0
Keywords
0x8000000000000000
TimeCreated
[ SystemTime]
2014-04-16T08:25:51.922502600Z
EventRecordID
3402
Correlation
Execution
[ ProcessID]
19984
[ ThreadID]
24964
Channel
Application
Computer
Schnittplatz
Security
[ UserID]
S-1-5-18
UserData
EventXML
param1
WmiApRpl
param2
WmiApRpl
binaryDataSize
16
binaryData
38270000DE27000039270000DF270000
So it would be great if you have any idea what to do...

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]

Urgent: constant Crash Media encoder, premiere pro CC and CC2014.

(Sorry by advance, its an Google trad)
Hello everyone!
I meet great difficulties with Premier Pro and Media encode CC and CC2014.
When I want to wire my pending projects that I go through File> Import (or even composition After Premier) or I simply do a drag / drop in Media Encoder .... Half the time it crashes, not charging Dynamic link not or crash Premier pro ..... with CC versions like 2014 .... I have no particular error message. However I have to process the killer Dynamic link, adobe (in general: QT32 server, Adobe ipCbrocker, PProHeadless.exe) via the Windows task manager. If not impossible to reopen the software.
I also noticed that even when the software does not crash, I close the first or afx or other software will not come out of the process, there is ad infinitum in the active process.
When I still manage to import my sequences in MediaEncoder, this plant some encodings but not all .... no particular reason and not telling me why he crashed. If it does not crash, it runs in a loop on the same image and I have to stop myself encoding, which never end. Knowing that all my files are part of a series, there has exactly the same things in it in terms of editing, effects etc.. Which by the way is only melted ....
Rush are my MXF files. And I use the Dynamic Link to import my sequences between Premier Pro and afx. Although it makes me exactly the same problem that I import directly my first or I go through Dynamic Link.
I'm on:
Windos Seven PRo 64bit.
I have a 3.33GHz i7 X980
Nvidia GTX480 driver 337.88 (the latest what)
AND 16GB RAm
My cache is not full, I empty it regularly. It is a hard look at projects and never moves.
So, if anyone has the same problem or knows a solution, I'm interested.
It falls at the wrong time, I have 200 to encode videos in one month.
Thank you in advance.
A.H
Message was edited by: aurel motiond

Il ne sert pas à grand chose ce forum, sans vouloir être offensant....

Media Encoder/Premiere Export Crashing During long file exports

Similar Messages

Maybe you are looking for