Problems with Premiere

Hi,
I've been having problems since the last Premiere Pro CC update.
1) After rendering with Adobe Media Encoder Premiere crashes. If I try to render more then one format also Encoder crashes (it actually crashed my whole system and I had to reboot with power button). Reboot sometimes works.
2) Sometimes the clips cant be selected or moved on the timeline. I have to scroll the timeline so that the clip disappears and scroll back in, then it works again.
Sami
iMac 27"
OS X 10.8.5
Graphics NVIDIA GeForce GTX 680MX 2048 MB
Memory 32 GB 1600 MHz DDR3
3,4 GHz Intel Core i7
Premiere Pro CC 7.2.1 (4)

No one? I've tried contacting chat and no one is available before monday...

Similar Messages

Problem with Premiere always conforming Audio again & again

I've got a problem with premiere CC which is always conforming audios time & again & again. Although this problem is not new in Premiere and I did face it in previous versions. But I've never found a good way to avoid it, especially when I work with much heavier clips or with some formats like mpeg or mov....
What should I do? Is that a network issue?
Thanks, Jim.

No Antivirus.
Audio is 5.1 audio from the video AVCHD, and music tracks are mp3 files.
Hardware: Intel i7 970 hex core processor, system drive (C:) 600GB 7500rpm, data drive (F:) where audio and video files are stored 10000rpm 500GB velociraptor, NVidia GTX 470 video card.

Problem with premiere elements 4.0

i am having
problem
with premiere elements 4.0. it keeps on crashing and when i put pictures on the timeline it comes up black. when i try to preview it either it shows black or sometimes the picture but i cant see it to delete if i wanted to. also it gave me a message something like that adbe is running low on memory and i should be caution

This is aimed at Premiere Pro, but may help
Work through all of the steps (ideas) listed at http://ppro.wikia.com/wiki/Troubleshooting
If your problem isn't fixed after you follow all of the steps, report back with ALL OF THE DETAILS asked for in the FINALLY section, the questions at the end of the troubleshooting link... most especially the codec used... see Question 1

I have 64 bit windows 7 and CS4 Production Premium. I have a problem with Premiere Pro CS4, it keeps

I have 64 bit windows 7 and CS4 Production Premium. I have a problem with Premiere Pro CS4, it keeps freezing and Crashing. A simple thing like leaving the project idle for about 15 minutes, you come back and find that it has frozen. Also if you drag out a clip on the timeline you will find that the whole application freezes. Any possible solutions would be much appreciated.

Could be several factors at play here. This ARTICLE might give you some tips on getting your computer ready for an editing session. Note that there are some added tips on Win7, thanks to Black Viper, near the end.
If nothing is helping, then the tips in this ARTICLE might help you find some clues amongst the breadcrumbs left behind with a hang, or crash.
The link in this ARTICLE will give you some general troubleshooting tips.
If nothing improves, then please post back with more details. This ARTICLE will give you tips on what would be helpful.
Good luck,
Hunt

Problems with premiere Cs5.5

I am having more and more problems with premiere CS5.5... I am running it on a windows base system. It freezes all the time and now I am not able to render... can someone, please, enlight me why? I am not using creative cloud, just the old set up... thank

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
•What is your exact brand/model graphics adapter (ATI or nVidia or ???)
•What is your exact graphics adapter driver version?
•Have you gone to the vendor web site to check for a newer driver?
•For Windows, do NOT rely on Windows Update to have current driver information
•-you need to go direct to the vendor web site and check updates for yourself
•nVidia Driver Downloads http://www.nvidia.com/Download/index.aspx?lang=en-us
•ATI Driver Autodetect http://support.amd.com/en-us/download/auto-detect-tool
Exactly what is INSIDE the video you are editing?
Codec & Format information, with 2 links inside for you to read http://forums.adobe.com/thread/1270588
Report back with the codec details of your file, use the programs below... A screen shot works well to SHOW people what you are doing
https://forums.adobe.com/thread/1070933 for screen shot instructions
Free programs to get file information for PC/Mac http://mediaarea.net/en/MediaInfo/Download

Problems with Premiere Elements 8 after updating to Nvidia driver 195.81 or later?

Hello PRE8 users,
If you have an Nvidia-based graphics chipset, and you've updated to Nvidia driver version 195.81 or later and you're still experiencing frequent crashes and freezes in Premiere Elements 8, then we'd like to hear from you in this thread. As mentioned in the announcement at the top of this forum, we believe most of these issues are caused by a problem with an Nvidia driver that was released after PRE8 was developed, and that the issues should be resolved by updating to Nvidia driver version 195.81 or later. Notes from the announcement I mentioned above are copied below for your reference.
Best regards,
Chad
For Nvidia users, there is a driver update that will fix both of the following issues:
Premiere Elements 8 does not restart after closing on Windows
Frequent and inexplicable crashes with Premiere Elements 8
To resolve these issues, you should update your GPU (graphics card) driver to version 195.81 or higher, by following the steps below.
1.      Identify which GPU driver you have by right clicking on the Desktop > Properties > Settings and in the Display field it will be displayed.
2.      Go to http://www.nvidia.com/Download/index.aspx?lang=en-us and download driver for your GPU card. Its size varies from 80 to 120MB depending upon the GPU card model.
3.      After the download is complete, run the driver install Installation. This should take less than 2 minutes.
There are no known issues that the latest driver update will cause.
This is an announcement. There is a separate discussion topic located here.
***If the update steps shown above do not upgrade your system to version 195.81 or higher, then you may need to download the driver directly. Use the link below only if the steps above do not update your driver to 195.81 or higher. The download page for Vista and Windows 7 is located here:
http://www.nvidia.com/object/win7_winvista_32bit_195.81_beta.html
http://www.nvidia.com/object/win7_winvista_64bit_195.81_beta.html

Processor
AMD Athlon(tm) II X4 620 Processor
7.1
4.9
Determined by lowest subscore
Memory (RAM)
4.00 GB
7.1
Graphics
NVIDIA GeForce 9500 GT
4.9
Gaming graphics
2431 MB Total available graphics memory
6.3
Primary hard disk
231GB Free (466GB Total)
5.9
Up here I copied and posted my PC's spec's. Since upgrading to the new driver, my problems increased. I seem to experience more crashes than before. Happens randomly and I can not see a pattern.   (I have noticed dragging clips from one area to another on the time line is no-no)
JPR

Problems with Premiere Elements 9.0.1 on Mac OS X Lion

Hi,
I recently upgraded to Mac OS X Lion and I am having several stability issues with Premiere Elements 9.0.1 now. None of these issues occurred on Snow Leopard. I experienced these issues on a machine that was upgraded from Snow Leopard to Lion after Premier Elements 9.0.1 was installed and I also had problems with a Premiere Elements installation on a clean install of OS X Lion.
I noticed the following issues:
1) System hangs when trying to save a project. The "save" window stays open at 100% completion.
2) Nothing happens when dragging footage to sceneline. The clips do show up on the timeline, though
3) System crashed when trying to upload a video to YouTube
Could you please get these issues fixed and provide a patch for Premiere Elements?
Thanks.
Ralph

This is not Adobe technical support, this is a user to user forum with the space provided by Adobe
To talk to adobe go to https://www.adobe.com/cfusion/mmform/index.cfm?name=wishform
And, be prepared to provide a LOT more detail about your computer and project

Problem with Premiere Pro CS5 project files bloating

Has anyone had the same problem that we're experiencing? - we have Production Premium CS5 installed on a machine with Win 7 Pro x64. We have three separate edits all of which are experiencing bloating of the .prproj project file. Often this bloating seems to occur when no importing of assets has occured, just changes in the edits. A project which started at 5mb has bloated to 1.5GB and we can no longer save it. Another project has bloated to 200mb and continues to grow in size. We have not brought in any weird assets, although we are using hi-def footage.
We upgrade from CS3 and never had this problem using Premiere CS3.
We can't fix the problem by 'remove unused footage' as this doesn't reduce the project size, although it does remove the unused footage.
We can't fix it by importing the project into a new clean project as the problem and huge file size just comes with
We can't fix it by using the project manager to collect up the project as it requires to save before collecting and the problem files can't be saved.
A couple of points to note - these projects were originally on Premiere CS3 and were upgraded to CS5. The footage is either Sony EX3 or Canon 5D - both HD.
The machine it's running on has 8gb of RAM.
Currently the projects I'm working on are gradually grinding to a hold with no way to make the files usable again.
Any suggestions are greatfully recieved as I'm at a loss. I've reported this to Adobe, and will report back if I get anything useful.
thanks.

natswilson wrote:
TClark,
I'm shocked that you are having the same problem on a mac. This seems to suggest a problem that could be really widespread. You've also beaten my 1.5GB file bloat size.
What the hell is going on with Premiere Pro? I'm surprised to have heard nothing from Adobe either via my support request or on this forum, save for Jeremys useful work around, considering how serious an issue this is.
I've had to break all the projects I'm working on which have multiple timelines in each project into a new seperate project per timeline in order to reduce the file bloat problem and reduce the risk of me loosing all my work in one go on a bloated file.
Adobe - we could do with some help here. It's frustrating to have spent so much money on licences for this software only to have virtually non-existant help when a serious flaw in the software manifests itself.
Nat
Yeah...it's really a bummer that no one is acknowledging it. It's pretty serious!
I hope Dennis jumps in soon!

Problem with Premiere Pro and Creative Cloud.

Hello, I have 2 big problems, when I lauching Premiere Pro, the software closes automatically after 5 seconds. It's the same thing with Photoshop. The second is about the software of Creative cloud, there isn't any information in the software, just a white page.. Please help me !

Neoriser are you referring to the Creative Cloud Desktop application being blank?
If you are facing crashing issues with Premiere Pro CC I would recommend posting a separate discussion in the Premiere Pro forum at http://forums.adobe.com/community/premiere.

Having Problems with Premiere Pro crashing

Greetings all,
We have been having problems with Premier crashing and we have tried everything to fix, I was reaching out to this community to see if anyone has seen this before.
Exception code: 0xe06d7363
Fault offset: 0x000000000000940d
Faulting process id: 0x1894
Faulting application start time: 0x01ced6f8a66eee8c
Faulting application path: C:\Program Files\Adobe\Adobe Premiere Pro CS6\Adobe Premiere Pro.exe
Faulting module path: C:\Windows\system32\KERNELBASE.dll
Report Id: 06533511-442c-11e3-94ca-d067e551f5b6
Faulting application name: Adobe Premiere Pro.exe, version: 6.0.3.0, time stamp: 0x505748bf
Faulting module name: MSVCR100.dll, version: 10.0.40219.1, time stamp: 0x4d5f034a
Exception code: 0x40000015
Fault offset: 0x00000000000761c9
Faulting process id: 0x350
Faulting application start time: 0x01cee4cd89040e74
Faulting application path: C:\Program Files\Adobe\Adobe Premiere Pro CS6\Adobe Premiere Pro.exe
Faulting module path: C:\Windows\system32\MSVCR100.dll
Report Id: 9209dc6a-50c1-11e3-b267-6480996eb95c
It just seems to crash all the time.

https://encrypted.google.com/search?q=0x40000015

Major problems with Premiere CS4

Hello there!
I'm having major problems with CS4. I recently bought a new computer - essentials are as follows:
Intel Core i7 920 2.66GHz
2 x Kingston 3x2GB, DDR3 1333MHz (=12 GB RAM)
Ati Radeon HD 5770 v2
Asus P6T SE, LGA1366, X58, DDR3, ATX
2 x 500GB, Barracuda 7200.12 (RAID1), system disk
2 x 1TB Barracuda 7200.12, media disks
Windows 7 Pro 64 bit
Adobe CS4 Production Premium + latest updates
The problem I have has mostly to do with Premiere although I think the rest of Production Premium softwares should be running better on this computer as well.
For starters, I was highly disappointed when I couldn't view a single HD clip from the Premiere timeline (it was an .m2ts rip from a previously self-burned Bluray disc) at all. Rendering is very slow and even after that the video doesn't run normally, showing just a few individual frames per second. When I point the timeline at a certain spot, it takes many seconds until even that very frame is shown in the monitor window.
And this is not all - I decided to try with a basic DV AVI clip, previously captured with my PPro 1.5 on my earlier computer (3.2ghz Pentium from 2005). It's a native file so it doesn't even need rendering and still the same problem occurs. With normal playback only about 6-10 frames are shown per second. It's absolutely ridiculous - even my 2004 laptop runs DV AVIs more smoothly with PPro 1.5.
While I'm running the Premiere, the level of used RAM comes only up to around 24 percents. The processor, then again, comes close to a hundred when play is pressed on the timeline.
I haven't had such immense problems with other Production Premium softwares (though as I said, I think they should be running faster as well). Otherwise the computer is running smoothly.
A friend of mine pointed out that the graphics card I'm using isn't on the Adobe website's list of supported ones with Premiere, but afaik it shouldn't even be a graphics card problem with this high-end machinery.
So - I sure could use some help and ideas about how to get the Premiere working. My main intention for buying a new computer and Adobe CS4 Production Premium was to start HD editing after all! Thanks beforehand!

Hi
Yeah, I hope he solves problem and knows how it got solved and tells us all...it's like being a detective ! " Mr Plum did it in the "svchost" room ! "
I got a little lost on this....
You are welcome and I'm glad that it paid off so nicely for you. One more suggestion, if I may: I'm a big fan of a fixed pagefile size. When making a fresh install of Windows, one of my first actions is to set a fixed pagefile on a different disk (min=max) before installing anything else on that different disk and removing the pagefile on the C drive. This will ensure that the pagefile in on the fastest part of the drive and will never be fragmented.
I think it used to be that I made swapfiles, or swapdisks which now seems to be called pagefile. That in itself is a little confusing semantic wise, because of the use of mempage stuff. It used to be that base memory was 640k, with the upper memory (to make up 1024 kb) was mostly for drivers and stuff. If more memory was needed than 640k (an event the inventor never thought possible... "who could want more than the enormous amount of 640K ?", he said..)..the extended and expanded memory got invented to swap memory pages from that 640k as needed with the rest of RAM. That's basically correct right ? Sooooo, I don't know if that still goes on, but I suspect it does, unless someone totally changes the architecture of the computer and cpu and fsb and everything... but I don't know what is going on nowadays. Anyway, there were other ways besides windows OS to create virtual memory on the hard drive, and Photoshop was one of the programs that could do that, I think.
Why MS would want to call the swapdisk virtual memory "pagefile" is beyond me.
Anyway, be that as it may, I understand that making the pagefile first on a drive so it's close to the center of the drive (heads don't have to travel far to access). But I haven't added a lot of drives to a system before, and I suspect I will be pretty soon...and this is the part I don't get...
You add drives and put OS on them? So they are bootable ? I've added a drive or two but just formatted and used as more storage but didn't put OS on them. So that part is confusing...
Then you take the pagefile off the C: drive ? Are you then using the new drive as your boot drive and the C: drive is too full to use accept to run the programs already installed ?
Thanks again !
Rod

Problems with Premiere Elements

1. My biggest problem with Adobe Premiere Elements 10 is it closes out on me all the time. I have a windows 7 computer. When I open it up it will stay up for about a min. then it pops up Adobe premiere elements has stopped working and shuts down on me.
2. The videos are jerky. When I go to play them they won't play smoothly. They are AVI files.
have the inspiration browser updated, I have installed quick time player, the computer is all updated, the videos are rendered. I don't know what is going on with it. It should be working.

It sounds as though these AVI files are not from a digital video camcorder.
What model of camcorder are these videos from and what resolution are they?
If they are from a still camera or smart phone that shoots in MP4/AVIs, they're not going to work in that format in Premiere Elements.
If you see a lot of red lines above your clips when you add them to your timeline, that's a pretty good indication of problems.
Is that the case in your project?
BTW, please don't start a new thread if you're continuing to discuss the same performance problems. It makes it very difficult to follow a discussion because we're not sure what you've already discussed and tried and what the history of your problem is.

Problems with Premiere Pro 2.0: sound lost after clip pasting

To integrate small projects to one bigger Project, it used to work well with Premiere Pro 1.5 in the following way: import small projects into the main sequence of the new project and, in parallel, copy the clips from the timeline of the small projects and past them into the timeline of the new project. However, I am encountering the following problems while trying to do the same thing with Premiere Pro 2.0:
·        Video and sound of every pasted clip becomes unlinked.
·        Although the sound was there (also shows in the wave view) right after the pasting and it can be rendered, but the audio Information gets lost as soon as I exit the new project (saved beforehand). If I re-open this new project, although the timeline shows all the pasted sound clips, but there is information in them - no sound (the wave views show only straight lines).
·        As well, some of the video and audio effect settings get lost (e.g. cross fading), but the effects such as brightness and contrast settings always remain.
·        At least one thing seems to be sure: the imported files themselves are ok. Newly created clips in the timeline from those imported files (dragged into the timeline) are fine - no information lost.
All tips are great helps. Thanks in advance.

I got it!
Though not described in the English HELP, but in the German HELP: I have to press the Shift and T Keys. It works in my case with the following steps:
1.     Mark the corresponding audio and video tracks
2.     Put CTI over the clip
3.     Press shift + T
4.     Double click the clip
5.     Eventually I have to repeat and press the keys shift +T again.
Thanks a lot once more for all of the hints and the detailed explanations. It is indeed a great help. I really appreciate it very much.
tryerlu

Problem with premiere pro and encore with win7 enterprise 64-bit.

We are a college with approx 500 pc's running win7 enterprise 64-bit. Premiere pro and Encore will only open with admin login, not user login. All other packages ok. Any suggestions as to why this is?

Our lab has just had CS6 installed on it, running Win 7 enterprise. A user account will open a Premiere Pro project. I've done it. That was only to check that everything worked ok. I edited a couple of clips and stuck them on a sequence (16:9 PAL DV) and it played them ok and the project was saved back to the USB hard drive OK.
I have also opened up encore, made a new project and saved it to the USB HDD. No assets were added to it, just checking that the preference files had copied from the central server to the machine, so that users have certain options already pre-selected.
What exactly are the problems with Win 7 enterprise?
Andrew

Hilights Clipping Problem with Premiere CS3 Media Encoder

I've just discovered a pretty serious problem with the way Premiere CS3 processes video to the Media Encoder.
Many of you are familiar with the term "super whites", the ability of modern cameras to capture and record levels above 100 IRE. With HDV and newer technology, recording to 109 IRE is quite common.
I was aware for some time that importing this footage into Premiere results in a hard truncation of whites above 100 IRE. However, I discovered last month that the Fast Color Corrector has a Output Levels adjustment that can rescale all the levels to fit down in the 0-100 IRE range. I verified this using the scopes in Premiere and by observing recovered details in my footage. I was even able to export frames to TIFF files and show the recovered highlights in the exported TIFFs. The difference is substantial and not subtle--it's the difference between a sky completely blown to white and one where you can see the sky is blue with clouds in it.
Last night, I discovered that the Unsharp Mask filter doesn't handle footage above 100 IRE, either. Even if I use Levels to set 0-235 RGB range, somehow, Unsharp Mask is processing the un-level-adjusted signal, regardless of stacking order of the filters.
I rendered two Blu-ray discs, one with Unsharp and the other without. To my astonishment, BOTH discs lacked any detail in the highlights--the whites were clipped at 100 IRE!
Now I turned attention to the Media Encoder. Pausing on a frame where I can see the difference between 100 IRE and 109 IRE and shades in between, I fire up the Media Encoder and note that even in ME's previews screens, the whites are already clipped. There is more highlight detail in the program monitor, whereas it's all gone in the Media Encoder's display.
It is obvious that highlight information, even scaled back to 0-235, is being treated as if it were 0-255 and clipped at 235 before passing to the encoder. This is a real disappointment, because there is another half f-stop of detail up there that I was trying to pull into the useable range of 100 IRE for the Blu-ray disc. Since it is very difficult to shoot footage and limit the peak whites in-camera to no more than 100 IRE, nearly all of us are losing valuable picture information.
Even if you can recover the highlights on the timeline through a Levels filter, it gets thrown away again on the way to the Media Encoder. Short of exporting a few hundred thousand frames as .TGA files and then loading those back in and rendering out to whatever motion CODEC, I am at a loss as to how to get Premiere to leave the whites intact.
I haven't seen this issue discussed in any detail here. Has anyone found a way around it, besides reshooting all your footage of one-time events to sub 100 IRE levels?

I'd rather the camera added that extra lattitide within the appropriate 0 to 100 IRE range.
That's a lot like saying you want 10 gallons of water in an 9-gallon jug.
As it is, it looks like such adjustments will need to be done on a clip by clip basis.
Or, you can do it the "Dan" way in AviSynth. I wrote a script function called SoftLimiter: It applies photoshop-style curves on the Y + U + V channels to bring the maximums within legal range… using a sort-of "soft-knee" approach to reducing extreme highlights and/or oversaturated areas.
It causes a tiny bit of posterization in the highlights, just like all 8-bit per channel color adjustments do… but it is hardly noticeable on a computer screen and even less on TVs.
SoftLimiter for AviSynth 2.5
Create a folder C:\SoftLimiterCurves\ and place the .amp curves files in that folder.
Place the other files in your AviSynth 2.5 / plugins folder.
The example below assumes DV avi files and requires a DV codec (such as Cecocida DV, MainConcept, Canopus) that can read / write in YUV formats.
Create a script like this:
AviSource("dv.avi", pixel_type="YUY2")
SoftLimiter()
Open the script in VirtualDub, use Video / Fast Recompress, Select Cedocida DV codec. File / Save as .avi
Before:
After:
And, Jim… you can place your dv2film() command at the end of this script if that's what you're trying to accomplish.

Audition problems with Premiere CS5

Has anyone had problems with Audition 5.5 not functioning with Premiere CS5. I have both programs (but not a part of the Suite). So, Audition CS5 is installed and so is Premiere CS5. After separating a sound channel, I want to pick the Edit with Audition from the drop down but the Edit with Audition is muted; interesting however is the Edit with Soundbooth is highlighted and it works. But I would like to work with Audition instead. Anyone have those sorts of problems?

This built-in functionality works only with Premiere CS5.5, I believe. There may be some registry hacks or something to make it work a little with Premiere CS5.0, but I have a feeling the only way to successfully fly stuff back and forth as intended is to get the upgrade.
Now, if that's actually what you have, and this is happening, then that's a different problem altogether.

Problems with Premiere

Similar Messages

Maybe you are looking for