Premiere CC 2014.2 crashes when rendering or (rendering effects) In and Out SEQUENCE for playback in a Nested Sequence

I have 4 internal HDD and an External. No matter where I assign Media Cache Files or Media Cache Database Premiere crashes within 100-300 frames in a Nested sequence. I am trying to move the caches around, deleting them, restarting a fresh nested sequence... nothing! I cannot get the short film done because of it. I have even formatted my hard drive and started fresh thinking that solves the problem, but it still remains. Anyone know what I can do?
Running Windows 7 64 on Bootcamp.
Quadro 4000
32GB Ram
dual xeon quad core

Hi,
I would suggest the following steps:
http://blogs.adobe.com/kevinmonahan/2014/09/10/premiere-pro-cc-freezing-on-startup-or-cras hing-while-working-mac-os-x-10-9-and-later/
Run a disk permission repair on your boot drive, and
Reset Home Folder permissions and ACLs Error | Apple Support Communities
Thanks,
Rameez

Similar Messages

Premiere CC 2014 crashes when exporting via the Queue

Having issues exporting from Premiere CC 2014 via the "Queue".
My system:
Dell Precision T5600 Workstation
Windows 7 Pro 64 bit
Xeon E5-2680 @ 2.7 GHz processor
Nvidia Quadro 4000 graphics card, driver ver 347.25
32 GB RAM
Creative Cloud 2014
Premiere Pro CC (2014) Up to date
Media Encoder CC (2014) Up to date
Exporting via the Queue has work just fine in the past. Had this issue awhile back and cleared some cashed files which fixed the problem but don't remember what I did. I have uninstalled and re-installed Premiere. This took care of the problem for awhile, but now the same issue has cropped up again.
Symptoms: When exporting a sequence from Premiere, clicking "Queue" launches Media Encoder but it doesn't completely hand off the sequence to Media Encoder. Premiere locks up, leaving a small blank window open named "Export Media (Not Responding)". It never completes the hand over to the Media Encoder queue. If I reverse the process by launching Media Encoder and import the same Premiere timeline directly into the Media Encoder queue, it loads and renders just fine. If I do an "Export" from Premiere, it works just fine. This seems to indicate something is going on with the exchange between Premiere and Media Encoder. I have this issues on multiple projects.
Any help would be greatly appreciated.
Thanks, Dave

I'm not clear why you couldn't run it in Administrator mode ... right-click the program icon, Properties -> Compatibility, near the bottom, run in administrator mode ...
Neil

Adobe Premiere CC 2014 CRASHES WHEN RUN AS A REGULAR DOMAIN USER

When I run the software as domain admin or local admin or any other user that has administrator priviledges on the domain the software starts just fine.
Faulting application name: Adobe Premiere Pro.exe, version: 8.2.0.65, time stamp: 0x5486db4a
Faulting module name: dvaui.dll, version: 8.2.0.65, time stamp: 0x5486b61b
Exception code: 0xc0000005
Fault offset: 0x00000000001871a8
Faulting process id: 0x1d2c
Faulting application start time: 0x01d04aecacb7353d
Faulting application path: C:\Program Files\Adobe\Adobe Premiere Pro CC 2014\Adobe Premiere Pro.exe
Faulting module path: C:\Program Files\Adobe\Adobe Premiere Pro CC 2014\dvaui.dll
Report Id: f1f36e19-b6df-11e4-a820-005056c00008
when i run as a regular domain user this is what happens.

I'm not clear why you couldn't run it in Administrator mode ... right-click the program icon, Properties -> Compatibility, near the bottom, run in administrator mode ...
Neil

Indesign CC 2014 crashes when printing to Fiery server

This is to remind Adobe that issues printing to Fiery print servers from Indesign CC 2014 (10.0 or 10.1) on Mac have not been resolved.
A patch has been provided here: InDesign & Illustrator | Crash while printing to Fiery RIP | MacOS --- however, the problem persists after patching. I should note that the fix at that link only pertains to Indesign 10.0. If you download Indesign 2014 from Creative Cloud you would, at this time, receive 10.1. That script will break 10.1 completely. There is no fix for 10.1.
The original thread for this discussion is here: Indesign CC 2014 crashes when printing It's marked 'Answered' and methinks the ongoing conversation there has been over-looked.
I am bumping this topic to keep the conversation fresh. If anyone else has found solutions to printing to Fiery from Indesign 10.x either by updating Fiery directly or with additional scripts or workarounds, please share them here.
I could publish one of my 10.1 crash logs if I could be advised which pieces are most important, or how to post the unabridged without spamming the forum.
That's the constructive bit. Here's my rant...
After speaking to Adobe on the phone, they tell me this isn't resolved yet because it affects only a small subset of people. I called some peers at other agencies across my region and learned they all use Indesign with Fiery servers. We are not an isolated few! (those fortunate individuals I spoke to are still using CS6 -- and I received some jovial ribbing for having my on-going CC subscription.) I have a lot of printing to do on the Fiery now that these projects are finishing, but i'm held up while down-saving these projects to be used in CC (9.x). Its frustrating, its time-consuming, and its simply unacceptable to CC subscribers as we move in to 2015. I urge Adobe to work with EFI to solve this problem once and for all.

This is a user to user forum with "some" Adobe staff participation, report bugs at this link
https://www.adobe.com/cfusion/mmform/index.cfm?name=wishform for feature requests or bugs

Premiere Pro crashes when I open my project because the cursor is stuck on a time-lapse sequence

I have a Time-lapse sequence which I have just built and saved the project of, but my cursor has stopped on the time-lapse sequence. Premiere Pro does crashes when I open my project because the cursor is stuck on the time-lapse sequence.
My project was saved in Premiere Pro with the cursor stuck on my new time-lapse sequence. Now, Premiere Pro crashes when I try to open the project....Please help URGENTLY?

>It may be a corrupt font, but I have thousands installed. Is there any way to test for that?
Reply #8 was specifically to address this question.
>I basically wanted to know if this is a 3.2.0 issue or not.
That's not what you asked. Perhaps asking a specific question will get you closer to a specific answer?
The titler does not crash for me at any stage of the Adobe updates for Premiere Pro, including 3.2.
Cheers
Eddie
PremiereProPedia (
RSS feed)
- Over 300 frequently answered questions
- Over 250 free tutorials
- Maintained by editors like
you
Forum FAQ

Premiere Pro CC Crashing When Rendering Nested Sequences

When I try to render out my project which has a nested sequence (see below),
As you can see I have 2 sequences. My original cut is "IN CAR". I then have another sequence titles "TEST" in which I have laid out the entire sequence of "IN CAR". When going to render this project, I simply get an error saying "Error Compiling Movie".
I can render a single sequence without any trouble.. but as soon as there is a nested sequence, it crashes.
Is there something I'm doing wrong?
My specs:
iMac 27inch Late 2013
Quad Core
32GB RAM
GTX 780
3.5GHz Processor
Any help is greatly appreciated.

The Unknown Error is the bane of the PP editor, simply because the cause is unknown, and without that, there's no way to suggest a definitive fix.
You'll have to experiment with different things, see what works and what doesn't.

Premiere Pro CC Crashing when Scrolling Through Sequence in Timeline - Audio Waveform Goes Blank First

The description is in the title: Premiere Pro CC Crashing when Scrolling Through Sequence in Timeline - Audio Waveform Goes Blank First.
Just started today, won't stop crashing now after a minute or two, and always does it when I scroll through the timeline of a sequence. The audio waveform goes blank first.
What is going on?
Date/Time:
2014-10-22 12:16:16.078 -0400
OS Version:
Mac OS X 10.9.5 (13F34)
Report Version: 11
Anonymous UUID: E1BCDCD7-6284-3012-9151-FF85491060DA
Crashed Thread: 0 Dispatch queue: com.apple.main-thread
Exception Type: EXC_BAD_ACCESS (SIGBUS)
Exception Codes: KERN_PROTECTION_FAILURE at 0x000000011d74b000
VM Regions Near 0x11d74b000:
VM_ALLOCATE
000000011d748000-000000011d74b000 [   12K] rw-/rwx SM=PRV
--> STACK GUARD
000000011d74b000-000000011d74c000 [
4K] ---/rwx SM=NUL stack guard for thread 4
Stack
000000011d74c000-000000011d7ce000 [ 520K] rw-/rwx SM=COW thread 4
Thread 0 Crashed:: Dispatch queue: com.apple.main-thread

same problem of mine, as posted here:
Crash when scrolling the timeline
please find attached the crash report log, as requested.
Process:         Adobe Premiere Pro CC 2014 [3770]
Path:            /Applications/Adobe Premiere Pro CC 2014/Adobe Premiere Pro CC 2014.app/Contents/MacOS/Adobe Premiere Pro CC 2014
Identifier:      com.adobe.AdobePremierePro
Version:         8.2.0 (8.2.0)
Code Type:       X86-64 (Native)
Parent Process: launchd [225]
Responsible:     Adobe Premiere Pro CC 2014 [3770]
User ID:         501
Date/Time:       2014-12-22 16:33:25.725 +0100
OS Version:      Mac OS X 10.9.5 (13F34)
Report Version: 11
Anonymous UUID: DC744912-A135-A02B-C2D3-75C4CA421CDD
Crashed Thread: 0 Dispatch queue: com.apple.main-thread
Exception Type: EXC_BAD_ACCESS (SIGSEGV)
Exception Codes: KERN_INVALID_ADDRESS at 0x000000011a46a000
VM Regions Near 0x11a46a000:
    VM_ALLOCATE            000000011a461000-000000011a46a000 [   36K] rw-/rwx SM=PRV
-->
    VM_ALLOCATE            000000011a46d000-000000011a46e000 [    4K] rw-/rwx SM=PRV
Crashed Thread: 0 Dispatch queue: com.apple.main-thread
Exception Type: EXC_BAD_ACCESS (SIGSEGV)
Exception Codes: KERN_INVALID_ADDRESS at 0x000000011a46a000
VM Regions Near 0x11a46a000:
VM_ALLOCATE 000000011a461000-000000011a46a000 [   36K] rw-/rwx SM=PRV
-->
VM_ALLOCATE 000000011a46d000-000000011a46e000 [    4K] rw-/rwx SM=PRV
Thread 0 Crashed:: Dispatch queue: com.apple.main-thread
0   com.adobe.HandlerTimeline.framework 0x000000010c2b31f4 HandlerTimeline::TimelineMediaIconManager::DrawAudioWaveform(UIF::DC&, ASL::ParamRect<int> const&, ASL::ParamColor<RGBColor>, unsigned int, unsigned int, ASL::InterfaceRef<ASL::ASLUnknown, ASL::ASLUnknown>, bool, std::vector<bool, std::allocator<bool> > const&) + 1620
1   com.adobe.HandlerTimeline.framework 0x000000010c1dc4f5 HandlerTimeline::AudioTrackContentView::DrawWaveform(UIF::DC&, ASL::ParamRect<int> const&, ASL::ParamRect<int> const&, ASL::InterfaceRef<BE::ITrackItem, BE::ITrackItem>, unsigned int, ASL::InterfaceRef<ASL::ASLUnknown, ASL::ASLUnknown>) + 2661
2   com.adobe.HandlerTimeline.framework 0x000000010c1dafb3 HandlerTimeline::AudioTrackContentView::DrawTrackItemWaveform(ASL::InterfaceRef<BE::ITrac kItem, BE::ITrackItem>, dvamediatypes::TickTime const&, int, ASL::InterfaceRef<ASL::ASLUnknown, ASL::ASLUnknown>) + 2131
3   com.adobe.HandlerTimeline.framework 0x000000010c2b447d HandlerTimeline::TimelineMediaIconManager::HandleWaveformNotification(int) + 429
4   com.adobe.HandlerTimeline.framework 0x000000010c2b53b0 HandlerTimeline::AsyncRequestNotifier::ListenToMessage(ASL::Message const&) + 176
5   com.adobe.ASLMessaging.framework 0x0000000100e1fb97 ASL::Broadcaster::BroadcastMessageInner(ASL::Broadcaster::ListenerRecord const&, ASL::Message const&) + 39
6   com.adobe.Frontend.framework   0x000000010006b039 FE::ApplicationErrorManager::ExecuteFunctionWithTopLevelExceptionHandler(boost::function0 <int>) + 41
7   com.adobe.ASLMessaging.framework 0x0000000100e1f71f ASL::Broadcaster::BroadcastMessage(ASL::Message const&) + 1695
8   com.adobe.ASLMessaging.framework 0x0000000100e25e9a ASL::StationUtils::BroadcastMessage(dvacore::utility::ImmutableString const&, ASL::Message const&) + 42
9   com.adobe.dvacore.framework   0x00000001003c763c boost::function0<void>::operator()() const + 28
10 com.adobe.dvacore.framework   0x00000001003c8f4c dvacore::threads::(anonymous namespace)::FunctionQueue::ExecuteOneFunction(boost::shared_ptr<dvacore::threads::(anonym ous namespace)::FunctionQueue>, bool) + 124
11 com.adobe.dvacore.framework   0x00000001003c9a4c boost::detail::function::void_function_obj_invoker0<boost::_bi::bind_t<bool, bool (*)(boost::shared_ptr<dvacore::threads::(anonymous namespace)::FunctionQueue>, bool), boost::_bi::list2<boost::_bi::value<boost::shared_ptr<dvacore::threads::(anonymous namespace)::FunctionQueue> >, boost::_bi::value<bool> > >, void>::invoke(boost::detail::function::function_buffer&) + 60
12 com.adobe.dvacore.framework   0x00000001003c763c boost::function0<void>::operator()() const + 28
13 com.adobe.dvacore.framework   0x00000001003c9b02 dvacore::threads::(anonymous namespace)::RunLoopAdaptor::Execute(__CFRunLoopTimer*, void*) + 18
14 com.apple.CoreFoundation 0x00007fff8b7ae3e4 __CFRUNLOOP_IS_CALLING_OUT_TO_A_TIMER_CALLBACK_FUNCTION__ + 20
15 com.apple.CoreFoundation 0x00007fff8b7adf1f __CFRunLoopDoTimer + 1151
16 com.apple.CoreFoundation 0x00007fff8b81f5aa __CFRunLoopDoTimers + 298
17 com.apple.CoreFoundation 0x00007fff8b7696a5 __CFRunLoopRun + 1525
18 com.apple.CoreFoundation 0x00007fff8b768e75 CFRunLoopRunSpecific + 309
19 com.apple.HIToolbox 0x00007fff93049a0d RunCurrentEventLoopInMode + 226
20 com.apple.HIToolbox 0x00007fff93049685 ReceiveNextEventCommon + 173
21 com.apple.HIToolbox 0x00007fff930495bc _BlockUntilNextEventMatchingListInModeWithFilter + 65
22 com.apple.AppKit 0x00007fff8e47924e _DPSNextEvent + 1434
23 com.apple.AppKit 0x00007fff8e47889b -[NSApplication nextEventMatchingMask:untilDate:inMode:dequeue:] + 122
24 com.apple.AppKit 0x00007fff8e46c99c -[NSApplication run] + 553
25 com.adobe.Frontend.framework   0x00000001000d302d FE::MacApplication::RunSelf() + 45
26 com.adobe.Frontend.framework   0x0000000100047e98 FE::Application::Run(std::basic_string<unsigned short, std::char_traits<unsigned short>, dvacore::utility::SmallBlockAllocator::STLAllocator<unsigned short> > const&) + 4328
27 com.adobe.Frontend.framework   0x00000001000d4944 FE::AppMain(ASL::ObjectPtr<ASL::Module, ASL::AtomicValue> const&, std::basic_string<unsigned short, std::char_traits<unsigned short>, dvacore::utility::SmallBlockAllocator::STLAllocator<unsigned short> > const&, int, void*) + 276
28 com.adobe.Frontend.framework   0x00000001000dbbe5 FE::Run(ASL::ObjectPtr<ASL::Module, ASL::AtomicValue> const&, std::basic_string<unsigned short, std::char_traits<unsigned short>, dvacore::utility::SmallBlockAllocator::STLAllocator<unsigned short> > const&, int) + 581
29 com.adobe.AdobePremierePro     0x00000001000018ac main + 508
30 com.adobe.AdobePremierePro     0x00000001000016a4 start + 52

Premiere Elements 9 crashes when I try to open a project

Premiere Elements 9 was installed on my laptop when I bought it. I have only just tried to use it for the first time this week. When I choose 'create a new project' it opens but there's only a blank screen - no way to start editing, drag video in, etc. When I try to re-open a project, it crashes - saying there has been an error and it has to close.
I have uninstalled and re-installed from the discs that came with the laptop but this problem continues to happen.
Any ideas what I can do to fix this?
Thanks.

Thanks for your suggestions. I'm working on a Windows 7 laptop.
When I try to download the 9.0.1 update I get an error message: "There was an error downloading this update. Please quit and try again later". It doesn't say what the problem is.
1. Yes
2. I've tried this and got the same blank grey screen as before (no work area) - tried to open a project/ create new and I got the error message: "Sorry, a serious error has occurred that requires Adobe Premiere Elements to shut down." But then it doesn't shut down.
3. I'm not sure what kind of video card - how do I find this out?
Unless you have other suggestions, given my replies above, I'll try deleting the folder you suggest next.
Thanks
Emily
Premiere Elements 9 crashes when I try to open a project
created by A.T. Romano in Premiere Elements - View the full discussion
emilyw76
What computer operating system is your Premiere Elements 9 running on? For now I will assume Windows 7, 8, or 8.1 64 bit.
Have you installed the 9.0.1 Update and are trying to work from it? I suspect not. To do that, you can use Help Menu/Update within the project or, if that is not possible, you can do the update with the program closed. Use the download link
Adobe - Premiere Elements : For Windows : Premiere Elements 9.0.1 update
Then the usual
1. Do you have the latest version of QuickTime installed on your computer?
2. Are you running the program from a User Account with Administrative Privileges and have you applied Run As Administrator to the desktop icon of the program?
3. What video card/graphics card does your computer use? How many cards, 1 or 2? And, is the card driver version up to date according to the web site of the manufacturer of the card or the web site of the manufacturer of the computer?
An important troubleshooting scheme is to delete the Adobe Premiere Elements Prefs file and, if necessary, the whole 9.0 Folder in which the Adobe Premiere Elements Prefs file exists.
Local Disk C
Users
Owner
AppData
Roaming
Adobe
Premiere Elements
9.0
and in the 9.0 Folder is the Adobe Premiere Elements Prefs file that you delete. If that does not work, then you delete the whole 9.0 Folder in which the Adobe Premiere Elements Prefs file exists. Be sure to be working with Folder Option Show Hidden Files, Folders, and Drives active so that you can see the complete path cited.
After you determine that the video card/graphics card is up to date and the problems persist, the delete the BadDrivers.txt file.
Local Disk C
Program Data
Adobe
Premiere Elements
9.0
and in the 9.0 Folder is the BadDrivers.txt file that you delete. (After you close out of there and open a project, a new BadDrivers.txt file will be generated but the problem should be gone hopefully.)
Please review and consider the above and then we will decide what next as indicated.
Thank you.
ATR

Photoshop CC 2014 crash when opening or creating new files when running with Cintiq 13HD.

I have a problem where Photoshop CC 2014 crashes when trying to open or create a new file while the Photoshop window is being displayed on my Cintiq 13HD.
When Photoshop is being displayed on my main monitor it doesn't crash.
I'm running Windows 7 (64 bit) and have updated my graphics and wacom drivers to their latest versions and Photoshop is completely up to date. (I'm running the 30-day free trial)
Here's the event log of the crash:
Faulting application name: Photoshop.exe, version: 15.2.1.257, time stamp: 0x543dbc5e
Faulting module name: atig6txx.dll, version: 8.14.1.6398, time stamp: 0x54176130
Exception code: 0xc0000005
Fault offset: 0x00000000000122b7
Faulting process id: 0x23dc
Faulting application start time: 0x01d0030b1092334e
Faulting application path: D:\Program Files (x86)\Adobe\Adobe Photoshop CC 2014\Photoshop.exe
Faulting module path: C:\Windows\system32\atig6txx.dll
Report Id: 61680f48-6efe-11e4-aeeb-bc5ff45851ea

As you can already see, your ATI/AMD video card drriver is crashing.
Update the driver from AMD's website to pick up all the bug fixes you are missing.

PS CC 2014 crashes when I select print

PS CC 2014 crashes when I select print. I have updated all printer drivers as well as the graphics card. Any help is greatly appreciated.

Faulting application name: Photoshop.exe, version: 15.1.0.148, time stamp: 0x53d97a8f
Faulting module name: ntdll.dll, version: 6.3.9600.17114, time stamp: 0x53649e73
Exception code: 0xc0000374
Fault offset: 0x00000000000f87a8
Faulting process id: 0x1528
Faulting application start time: 0x01cfd5c2a647fe43
Faulting application path: C:\Program Files\Adobe\Adobe Photoshop CC 2014\Photoshop.exe
Faulting module path: C:\Windows\SYSTEM32\ntdll.dll
Report Id: ceaf0daf-41b6-11e4-8343-bcee7be34650
Faulting package full name:
Faulting package-relative application ID:

Premiere CC keeps crashing when moving or deleting a group of clips

Hello,
I am getting this weird bug where Premiere CC keeps crashing when I am trying to delete or move (either by using drag'n drop or cut-and-paste*) a selected group of clips on the timeline.
The sequence is set to QT ProResHQ for video previews to match the codec of the video files, so this couldn't explain this issue.
Here is the error message I am getting everytime:
Premiere Pro has encountered an error.
[/ppro721/releases/2013.10/shared/adobe/MediaCore/Backend/Make/Mac/../../Src/Sequence/Pers istentGroupContainer.cpp-279]
* Copy-paste does work though, that's my workaround for the moment: I copy the selected group of clips, then delete the "originals" one by one, because Premiere crashes only when I am trying to delete or move more than one clip at a time...
Even though I have found a temporary workaround for this weird problem, it's really frustrating as it keeps happening randomly throughout the sequence (not all clips on the same timeline are affected by this), and it complicates the execution of such basic operations as deleting or moving clips around on a timeline.
Any help is welcome, as I keep wasting a lot of precious editing time with this issue.
Thank you.

KT7373
What computer operating system is your Premiere Elements 9 running on and are you running the 9.0.1 Update version of the program. Just background information.
To each of the three groups, have you first applied the Group option under the Clip Menu? If so, you do not use Alt or Ctrl. You click and drag the selected/highlighted Group to where you want it. Doing that, to the extreme, I can move the Groups including dragging Group 2 over Group 3 to place Group 2 after Group 3 and no disturbances.
But you must wait the the Group to be selected/highlighted completely before you move it.
However, could it be that you have lost control of your project for resource reasons. Besides the 24 tracks high and the body of the tracks in three Groups, what is the duration of this project? Premiere Elements 9.0/9.0.1 is a 32 bit application whether it is run on a 32 bit or 64 bit computer, and the limitations include max supported installed RAM = 4 GB of which 3.2 to 3.0 or less of that are available.
Please review and consider.
Thank you.
ATR

Premiere elements 10 crashes when saving as DVD or DVD folder, etc.

Hi [me again!]
While awaiting resolution for PRE7 and PE7 'registered' licence 'not accepted' problems, my other Premiere elements 10 crashes when saving a Project as DVD 4.7Gb folder or direct to DVD or 'any other DVD way'.
The repeated windows error report I get is this:
Problem signature:
Problem Event Name:    APPCRASH
Application Name:    Adobe Premiere Elements.exe
Application Version:    10.0.0.0
Application Timestamp:    4e791009
Fault Module Name:    wdmaud.drv
Fault Module Version:    6.1.7601.17514
Fault Module Timestamp:    4ce7c9f8
Exception Code:    c0000005
Exception Offset:    000000000000f827
OS Version:    6.1.7601.2.1.0.768.3
Locale ID:    2057
Additional Information 1:    c1eb
Additional Information 2:    c1eb94943c7b4efb7ee314d92a94924b
Additional Information 3:    7d3f
Additional Information 4:    7d3fe30533dcbba28d68d00b60422c7b
In the meantime I am evaluating the 'cheaper' and without installing / working / DVD problems and possibly send Adobe discs back for full refund.
My Laptop is fast enough and well kept - not other 'larger' programmes have any problems running or installing [Stenberg Cubase Pro, Flight Simulator X and so on] only Adobe programmes!
I am really getting tired now.
Regards
Mobon

Hello
All problems are carefully separated - not all together, since I am a tidy person by default.
It is very simple and not confusing.
I actually have one main issue with PE7 and PPE7 [which I hope they will care of] and a series of small teething problems as many in these forums have on Premiere 10 since installation because Adobe programmes have 'basic' problems even loading / reading/ converting its own created files.
I looked up for Premiere Elements problems on-line [on external forums] and I can see so many problems and people opting for alternative programmes or getting 2 or 3 different programmes to do the job faster and better - that confirms my thoughts.
I am not here to stir things up [if by any chance you are thinking that], but I am merely trying to use a PAID and SUPPOSED to be GREAT program and it is clearly not my friend.
But if I get pushed up around and treated like a non-in-the-computer-field-person, then I might 'need to' stir things up with 'proves'!
I have been working with computers Hardware and Software since 1975 with the Sir Sinclair Spectrum .
So, I do know one thing or two by working 'manually' and without the 'easy' mouse clicking [!] and my main job these days is to actually fix People's messed up computers, recover data, erase data, etc. and often I find either Apple's or Adobe's programmes not working properly [being the main problem on slower computers] and users tried to fix them and messed things up!
Mainly is Apple programmes [ iTunes is one!] on Windows environment - just pure mess.
In fact I do not keep ANY Apple Programs on ANY my computers any-more and by adding the blooming QuickTime - it actually adds 3 'mostly not needed' applications that must be run in the background only slowing down 'most standard' computers and 'mostly' for no apparent reason but needed by Premiere Elements 10.
Adobe Acrobat Reader too is a kind of an offender in that sense, which I do not use any-more in favour of an alternative and very light program that does not invade your computer.
I could be talking about the above for days ...
The fact I do not know Premiere 10 very well and I am having some teething problems with 'Adobe Premiere Elements 10' does not make me a lower being or anything to the like or even put me aside the forums for being realistic and a human being most of all.
I simply am an Intermediate / Advanced / Professional Computer User / Repairer [depending on which subject] trying to fix this non-working-properly Adobe's program and get on with his life.
You as an employee perfectly know what I am talking about, the Adobe numerous problems with Elements and pro and the clever Marketing and money making tool Adobe has created around it and I do understand you must keep Adobe's side - of course and that is not a problem at all.
BACK TO THE ONLY PROBLEM THIS THREAD IS OPEN FOR:
Having said that, in the meantime I seem to have solved it myself [as I do most of the time], at least for now.
I am sure many other problems will arise.
My Solution that worked:
I simply clicked on the time-line [bottom] and then clicked on top menu TIME-LINE [if I am not wrong, it was late night and I might be wrong - do not crucify me please!] and MERGE CLIP and then I let the program do the job I purchased for.
Days ago using the Trial Version [before I purchased Premiere 10] I already read that Premiere does not like either large gaps [I did not have] or even simple clip cuts not merged and it did have 'loads' of problems, but most of them were solved by 'users' mostly.
Anyway, that seems to have done the trick, even thou it did take around 4/5 ours to do 3Gb ! Why?
My computer is fast.
But I have not checked or burned the files yet - so, I do not know100% - just yet, I will check later on today.
I believe Adobe must prepare a Service Pack with 'Loads' of fixing, there is no place to hide and that may convince users to even 'spend' and buy the PRO version - the ball is in your court now.
I cannot believe Premiere is having so many small teething problems and I am only doing a BASIC test and I can see the vast majority of users of Elements Programs going literally insane and only us, the more Techy ones coping.
Regards
M
PS the fact you see an avalanche of problems with my installation is actually normal.
That is because I am a 'fast' and organised Computer Technician which gets on with things and I usually do this with all new programmes to get rid of the possible initial several small hiccups, that other Companies usually fix with Patches - not Adobe, it seems - at least with Premiere elements.
In the last few years are mainly with Adobe Programmes. It is the only way to get the 'basic' program problems fixed straight away, so I do know the next time I run it actually works!
ADDITION:
IT WORKS!
Message was edited by: mobon

Premiere Elements 8 crashes when selecting the edit option

Hi to you all,
I just installed Premiere Elements 8 on my new system.
It is a Intel i5 + 4 GB mem, GTS250 and 400 GB of free disk space.
OS is WIndows 7 64 bits. The system is completely up-to-date with patches, fixes and so on.
BIOS, Drivers etc. All to the latest.
Starting PE8, no problem
Getting the film from my sony DV on to the disk, no problem.
Disc menu: no problem
Then when I want to add transitions or titles via the edit menu, Premiere elements 8 crashes. It is not responding anymore and windows is looking for a solution.
I followed the hints and tips on this forum on crashing Elements 8. No help. Quicktime to the latest. ended processes. All no help.
I also started PE8 in WIndows XP SP3 mode. Same problem.
Could it be the 64 bits?
Any help would be appriciated.
Richard
The Netherlands

Thank you all for the quick replies.
I installed the latest Nvidia GTS250 driver (from the Nvidia site) and guess. No crash anymore when selecting the edit menu.
My graphical card is a Asus GTS250 DK/DI/1GB and I was using the latest drivers retrieved from the asus site. Those drivers are old.
I can now continue to evaluate Premiere Elements 8.0
Thanks all.
Richard

InDesign CC 2014 crashes when creating alternative layouts

InDesign CC 2014 crashes when creating alternative layouts. I successfully created alternative layouts in 3 documents, now I cannot create any at all, it just crashes the program.

I just taught a class using Alternative Layouts in InDesign CC 2014 without crashing.
Start by telling us what kind of computer and operating system you're running. Are you having any other problems in InDesign CC 2014? Have you try restoring your preferences?
Trash, Replace, Reset, or Restore the application Preferences

Premiere Pro CC crashes when importing media.

Premiere Pro CC crashes when importing media. Every time. Driving me crazy.
It crashes as soon as the Windows dialogue box comes up.
Does it in new projects and in a project I created and imported into just fine 2 days ago.
Have rebooted.
Running Windows 8.1 on Samsung Series 5 ultrabook Intel i5 - not too sure what else to say about other settings:
I did have a problem the other day when Windows was crashing when browing a large folder of largish images and video clips but it went away when I put images and videos in separate folders.

Thanks for reply.
Point taken but I've been using it for over a year for simple edits (5 min films) in PPCC just fine. Can't even do what I could do the other night now.
Simple folder with a few jpegs and movies in it. In fact it just crashes before I even got to another folder.

Premiere CC 2014.2 crashes when rendering or (rendering effects) In and Out SEQUENCE for playback in a Nested Sequence

Similar Messages

Maybe you are looking for