Premiere Pro 5.5 - All Grown Up

I have been a Premiere user since version 5 going back to 1997 or 1998 I think. Through the years the one thing that frustrated me on more occasions than I can count is the countless crashes and instability. If I had a dollar every time Premiere crashed, choked, froze, threw an error, etc., I could have probably paid cash for my house. Through the years every new version was hyped as usual about the various new features and workflows but the instability and the fear of a crash always remained and I always said to myself "yeah ok, let’s see how many of the new features I can use before I am rebooting". The fear of crashes had me saving projects after ever other cut or tweak. If I has 5 or less crashes or freezes, etc in the course of a day it was a good "productive" day.
Like many of my fellow community members here I have been paying my mortgage and making 100% of my income with Adobe's tools with Premiere being the main staple of my workflow and income. I ran Premiere Pro 1.5 for a few years and didn’t bother upgrading until the CS4 release. And to what did my wondering eyes did appear? More instability! Shocked! No I wasn't really shocked, I expected it. It's Premiere "Pro" after all right? I would have been a fool to think that a new release of PP would be stable.
All playful sarcasm and kidding aside, through the years because of my true love and passion for Adobe and Premiere Pro I never abandoned Premiere. I never even tried FCP or Avid MC in hope that PP would one day get the love and affection from the PP development team and would one day be "all grown up" and be a "big boy" like it's big brothers AE and PS.
About a week ago I downloaded the 5.5 free trial and all I can say is WOW! As I stated above "I would have been a fool to think that a new release of PP would be stable". Well...I happily swallowed a big piece of humble pie...today I am a fool. I wouldn't have believed it unless I tried it. I have been editing about 6-10 hours a day for about a week and I am just speechless. PP has been rock solid and hasn't crashed, frozen, not a hiccup. I truly can't put into words how amazed I am about the stability. I haven't enjoyed editing this much in the last week as I have had in the last 10 years. When I upgrade to the Master Collection when my trial has expired I can only hope that Dynamic Link is as rock solid. I have faith that it will be.
About 3 years ago I met a friend of my brother n' laws and we got to talking and he said he worked out in CA doing audio editing for some TV show out there (can't remember the name but a cheesy show as I recall) and he said he did his audio on Pro Tools and the editors used Avid MC. He asked me what I did and I told him, he asked what I edited on. I said PP and SB and he kind of looked at me weird.
Today I hold my head up high and when someone asks what I cut on I can proudly say Premiere Pro and when they answer I can look weird at them (unless they're smart and are cutting on PP).
PP CS5 gave FCP a fat lip and now PP CS5.5 has FCP down for the count (with a little help from Apple stubbing it's arrogant toe as well !)
Adobe, THANK YOU! There's still one more "bully" left to go after...go knock 'em out!
Shane

@ Multimedia Lab,
I hear ya. I felt the urge to make the original posting because I was just that impressed, shocked, etc with my trial of PP 5.5. I was ready to burst with excitement and I needed to vent somewhere, lol. I tell my wife and just looks at me and says "that's great hon", she doesn't get it but she tries to humor me.
I am on day 14 or 15 of my trial and I literally have been editing several hours a day, every day, even on the weekends to squeeze every minute possible out of my trial and pound on PP as much as I can. As of this posting PP 5.5 has NOT frozen, threw an error or anything, literally NOT ONE HICCUP!!!!!!!!!! I still can't believe it. I understand that no software is perfect and I'm sure at some point there will be an error or a quirk or something, but if it's only going to have once every couple of weeks or once a month, etc., I can live with that. Like I said I know there is no such thing as perfect software but this PP 5.5 has me wondering...
I can't put it to words on this forum that would express my utter joy and excitement for PP 5.5 so I will stop trying haha. I don't want to start sounding like a weirdo or something.
I have had PP, AE and ME (all 5.5) open simultaneously, having ME encode in the background while I continued to edit in PP or mess around in AE...FLAWLESS!!! With CS4 when I would encode in the background and try switching back to PP or AE to edit or further composite 5 out of 10 times it ended badly. My system is adequate but by no means stellar. I'm sure a lot of my problems with CS4 was the fact it was 32 bit and I was asking CS4 to swallow too much in terms of ram for how much ram it could use.
I am running Win Vista 64 Home Premium, Intel Quad Core, 8 GB Ram. Like I said, adequate but certainly not stellar. I watched a recent video by Karl Soule in the Short and Suite series and I have been convinced that my next system upgrade will be an HP Worksation. I can only fantasize how fast PP, AE and ME would just be insane on a system like that.
IMO, I would definitely say give PP a shot. With the release of 5.5 Adobe has made a statement to the professional community. Like you said Apple seems to be moving away from its Pro line and focusing more on iPads, iPhones, iThis and iThat. In that respect Apple is fantastic and is the no.2 company in the world for that reason.
Anyone who is in our line of work uses Photoshop and I'm sure 99/100 use AE to some degree. So to me it only makes sense to use PP (now that is has been rebuilt and is ridiculously stable) because of the stellar integration between the apps. A few years ago I could see why a lot of editors said the heck with PP. With the rebirth of PP Adobe has one heck of an All Star team now. I know which team I'm staying on.
Whatever you decide I wish you the best. Keep us all posted on your decision.
Shane

Similar Messages

Adobe's move to a more "Final Cut" Premiere Pro is not all good.

Hi everyone. I don't post very often and I decided to do so because I want to hear people's comments on this subject. I have been a premiere pro user since Premiere Pro 2.0 and I've a good handle on Final Cut and Media Composer. To this day, I've always preferred Premiere for a number of reasons.
As of late, many Final Cut users have been migrating to other NLEs and in response to that the latest iteration of Premiere (Premiere CC) has included some decidedly FCP-ish features (And some Media Composer-ish stuff too). In my opinion, some are rather welcome additions and some are not.
What prompted me to write this is the feeling I got when I started using CC. It felt like in the rush to welcome the newcomers, some things were lost for those of us who has stuck by adobe for years.
Here's my list of good and bad:
Good stuff:
1) Auto Locate - Premiere is now smarter at finding your files. Awesome!
2) You can now select clips and move them up and down in tracks with keyboard shortcuts. Great!
3) You can move target and source tracks with keyboard shortcuts! In fact there are many new things you can do with keyboard shortcuts! (Can you tell I like keyboard shortcuts?) I'll leave the keyboard alone now. Yay! Ok now I'll leave it alone.
4) Audio Clip mixer. Now, I really don't see when I would use this, but sure. Why not? It's not invasive and they kept my track mixer as awesome as ever. I'm sure final cut users could shed some light as to it's utility. Specifically, what can you do now, that you couldn't without the Clip Mixer?
5) There are a few cool ways to expand tracks. (I've heard it works a lot like Media Composer).
6) You can now customize the buttons on your audio tracks. Sweet! (Also feels a bit Media Composerlike)
Bad stuff:
1) Symmetrical transitions - This is meant as a feature for Final Cut users but it's actually horrible to me. I don't want my start point to mess with my end point. I want to put them both exactly where I need them and have them stay. I know you can hold shift to get the old behavior back but I find I'm holding shift a lot these days.
2) Transition icon changed to a suspiciously fcp looking transition. It's smaller. I don't see the advantage of changing the look. I certainly don't see the advantage of making it smaller. Not a big deal, but not a fan.
3) The "fx" box replaced the name of the parameter whose keyframes you are currently seeing inside the clip. Now you can't tell which parameter you are looking at. Is this an attempt at removing clutter? Cause I think allow for the user to customize clip info is a better approach than simply removing stuff.
4) The clips now turn white when selected. Again I remember complaints of clips not being obviously selected but now you lose the label color when you select a clip. This means that if you select a bunch of clips, you can't use the color to see if you picked up something that should've stayed unselected.
5) Audio display now shows half of the wave instead of the doubled mirrored wave it always showed before. This sucks. Every DAW I've ever used (Pro Tools, Digital Performer and Audition to name a few) shows the mirrored wave. It's kinda standard. This new view is actually harder to look at. The negative view of the wave (the part of the wave that isn't the sound) looks like the bottom part of a wave. It's very distracting and annoying.
6) Work area bar is gone. This isn't such a big deal since the functionality has been added to the in and out marks, but since the work area bar is also a part of After Effects, this makes Premiere work differently than it's family of apps. I would think that having overlapping or similar tasks performed similarly throughout the Creative Cloud Apps would make a lot of sense to Adobe.
Again, Adobe Premiere Pro has been and still is my NLE of choice. This isn't an angry rant. I simply felt it was an update that removed some great functionallity and wondered if others felt the same. I'm sure my list is both incomplete and of course simply an opinion. I'd love to hear people's reaction to the new Premiere Pro CC. Do try and be nice though.

Jim.
Agreed. You can't please everyone every time. Though user customization goes a long way I think. And I definitely feel like this release was not really targeting me.
shooternz - Too bad. I did know this. It's not such an imposition but it does change the way I work without gaining anything I wanted. Seems like a lot of people actually like the symmetrical transitions though. Me, I think it is only useful when you don't care about being very precise. Maybe not. Maybe there's a good use for it. I haven't found it. I just wish there was a way to make the default behavior what it used to be and the symmetrical transitions work with shift. I'm already getting used to holding shift all the time so I'm not worried. I just don't see much advantage.

How to get Premiere Pro to access all of the professional codecs?

Hello,
Premiere Pro CC does not open projects that use any of the professional codecs, such as R3D or ProRes. It also has no presets available to create projects based on R3D, DSLR, etc. just presets for DV and a minimum number of older presets.
I have read that the problem could be due to an activation issue. Since the software was installed from a package created by CCP, there are no options to deactivate and then activate again.
I have two lab images. The first is just the Adobe video bundle. The second is the web/design bundle AND the video bundle. Premiere Pro is fine with the computers with just the video bundle. The one lab with both bundles is giving us the problem. I created the two installer packages based on the two serial numbers I have (one for each bundle).
I tried creating one installer for that lab using the serial number for the web/design bundle, but included all applications available to us. I uninstalled both bundles from a computer, restarted, ran the Adobe cleaner, and then installed all of the apps again. The Premiere Pro issue remains.
I assume the two bundles are still in conflict, but I don't know how to resolve it. OR, is there something else out there that can make Premiere use all of its codecs and settings?
All machines are running MacOS 10.8.4
Thanks!
Scott Meador / Mike Gunter
University of Central Arkansas

Update
I installed the design/web bundle on a computer where Premiere was working properly and after installing, Premiere continued to work properly. I am sure that is how I made the master for that lab (video bundle first > image for film program computers > add web/design for shared lab image), but it seems to work.
For now I will make a new master and re-image the lab, which sucks because we are in our third week of classes, but our film students can't do their work in our best lab with Premiere broken.
Scott Meador / Mike Gunter

Is Premiere Pro compatible with "all" Canon XA20's native recording formats (MPEG4-AVC / H.264)?

NTSC:
AVCHD - 1080: 59.94P / 59.94i / PF29.97 / 23.98P
MP4 - 1080: 59.94P / 29.97P / 23.98P; 720 and 360: 29.97P / 23.98P

Yes. There should be no issues handling these files in Premiere Pro CC.
Best,
Peter Garaway
Adobe
Premiere Pro

Premiere Pro CC Capturing All Files as MP3

I have Premiere Pro CC My capture files are being imported as mp3 files. I have a macbook pro which I am having problems with and I have access to an IMac and the IMac with the same Premiere Pro CC software gives me zero problems. I'm not sure what else to change because simply changing the file name to mpeg or I saw online about an m2ts (I copied it right when I did it) file but that didn't work either. Any suggestions??

Please see this link for possible solutions:
http://helpx.adobe.com/premiere-pro/kb/cant-capture-dv-hdv-video.html
Also, others have found success changing the mp3 files extension from .mp3 to .mpeg or m2ts.
Peter Garaway
Adobe
Premiere Pro

Premiere Pro not capturing all material

We are capturing live video from a Vaddio system mixer through a Matrox MX02 mini into Premiere on a Macbook Pro. Probably 4 of the last 12 video sessions we recorded came up short in Pr. Most of our sessions end up around 70-80 minutes and we might end up capturing 40-45 minutes of it. The time signature is still running when we finish and we are seeing the live image in the capture window. So, we know it is getting to the computer. After stopping the live capture and naming the file it proceeds to build audio peaks. Why is it dropping the last 20-30 minutes of our live capture?
Changed the title to be more clear. Message was edited by: Kevin Monahan

Kevin,
Thanks for your assistance. The HDD on my Macbook Pro is formatted as Mac OS Extended (Journaled) with 188 GB of available space.
We record live mainly because that is how our system was designed and set up. We use a pair of Vaddio PTZ robotic cameras permanently mounted and run through a Vaddio mixer. Those cameras don't have hard drives on them.
The nature of the sessions we record (Bible teachings) don't require much editing since it is done live. We pretty much have a finished product when we finish the session instead of having hours of editing to do when it is over.
It is just puzzling to me that we watch the whole session as it is being recorded through the capture window in Premiere Pro (since we use that as our record monitor) yet it only saves a portion of it. I certainly hope you have some ideas that could help. Thanks,
Brent

Premiere Pro headless gobbling all my RAM

Running CS5 here. I'm doing an Export from PP using the "queue" function, so Adobe Media Encoder is launching.
But after a few minutes, my machine grinds to a halt as Premiere gobbles up all my RAM, my OS X creates a whopping 38GB virtual memory swap file and my startup SSD is completely filled (this Mac has 32GB of physical RAM installed). Everything pinwheels and I have to do a hard power down of my workstation.
Any idea why it's not respecting the 20GB limit I set on the apps? Is this a Premiere problem or an AME problem?

Hi Todd,
I am busy transcoding in Encore (3 time Lines +- 75min each) it is using 23 gig of my 24 gig ram and it is set to only use 20 Gig. when I started it was going quick until the ram hit +-18 gig then it started going slower and slower. It has been going now for 4 hours.
System Spec:
Asus P6X58D-E
980X OC to 4.1
24 Gig Corsair Gt Dominator Ram at 1600
GTX 480
600 gig Veloci Rapter OS (windows 7 64 bit ultimate)
4 x 1tb Samsung raid 0 Media
3 x 1tb Samsung raid 0 Render and output
both of the above run off a Intel raid controller (RS2BL080)
Black Magic Ultrastudio Pro USB 3
Production Premium CS5 and CS5.5
If I open windows task manager it shows that Pr is using 21 473 440K and Encore is using 446 644K of memory. the funny thing is if I close Pr then En hangs and shuts down and if I start En by it's self and try and import the Pr sequences it says something about not been able read the format. Do you think this could have something to do with the blackmagic settings?
regards
Darren

Premiere Pro CS4 Crashes all the time

CS3 worked well for me, but I updated my system to CS4 and no matter what I do, the program crashes and gives me the error screen. I updated the program and still have this error happening. Is there any fix for this? Any help would be greatly appreciated.

>Make sure you update all your hardware drivers.
Which is what the link I provided recommends among many other things. ;)
We still need a lot of details to try to help the OP.
Cheers
Eddie
PremiereProPedia (
RSS feed)
- Over 300 frequently answered questions
- Over 250 free tutorials
- Maintained by editors like
you
Forum FAQ

I'm trying to install Premiere Pro CC 2014 and it keeps failing. I'm at this all day!

I've been trying to install Premiere Pro CC 2014 all day. It will begin the installation then progress. Suddenly it will decrease the %complete. Once it went all the way to 84% then failed. Can anyone tell me why this has happened. I have never had any trouble installing any other apps from my CC Membership.

Please read, and reply back here with information https://forums.adobe.com/thread/1499014
-try some steps such as changing browsers and turning off your firewall
-also flush your browser cache so you are starting with a fresh browser
http://myleniumerrors.com/installation-and-licensing-problems/creative-cloud-error-codes-w ip/
http://helpx.adobe.com/creative-cloud/kb/failed-install-creative-cloud-desktop.html
or
A chat session where an agent may remotely look inside your computer may help
Creative Cloud chat support (all Creative Cloud customer service issues)
http://helpx.adobe.com/x-productkb/global/service-ccm.html

"Adobe Premiere Pro 6 Quit Unexpectedly" - after deleting Cache files. All other Adobe programs working.

I went in and deleted Cached files after repeatedly getting the 'scratch disks are full' message. I have done this before and have had no issues. However, this time it comes up with a crash message whenever I open Premiere Pro 6. All other Adobe programs are working fine.
Does anyone know what could be wrong? Have I accidentally deleted something crucial? How can I fix this?

If you have a 64bit Windows adding more ram will allow Windows to use that ram, and provide more to CS4
Otherwise... here are some links I've saved that discuss crashes... may, or may NOT, help in your case... but free to read
Firewall = Crash http://kb2.adobe.com/cps/857/cpsid_85711.html
Win7 64bit Crashing and "a" fix http://forums.adobe.com/thread/580435
Photo Scaling for Video http://forums.adobe.com/thread/450798
-Too Large May = Crash http://forums.adobe.com/thread/879967
-And another crash report http://forums.adobe.com/thread/973935
Partition = Crash http://forums.adobe.com/thread/957286

Premiere cc 2014 crash with message "Adobe Premiere Pro could not find any capable video play modules. Please update your video display drivers and start again."

I updated to Premiere Pro CC 2014, all the other Adobe CC 2014 software works great, but Premiere doesnt even load. The starting page (frame) comes up - my whole computer slows down and after a minute or two it crashes completely and comes up with the message : "Adobe Premiere Pro could not find any capable video play modules. Please update your video display drivers and start again."
I'm running a macbook Pro 15" (2014) with 16GB RAM and 760GB SSD.
PLEASE HELP!

Hi Delarey,
Please go to the following location and rename the folder to old_folder name
User/user library/Application Support and rename Adobe folder
User/user library/Preferences and rename the Adobe folder
Then go to Documents folder and Go to Adobe/Premiere pro/8.0 and rename 8.0 folder
Make sure that you are in user library if you are not sure check the link below.
Access hidden user library files | Mac OS 10.7 and later
Regards,
Vinay

Need help with 24fps in Premiere Pro CS4

I am having issues working with 24fps imported video. My computer hardware is an AMD dual core processor running at 2.6GHz. It has 2GB of Kingston Hyper-X memory, 2x 300GB hard drives (not RAID), and an Nvidia 7900GS video card with 256MB video ram. My operating system is Windows Vista Ultimate with SP1. I am running Premiere Pro CS4 with all the current updates.
So here is the issue I am having. I captured video on a Canon XL2 in 24fps, 16:9 widescreen, and 2:3:3:2 pulldown. My CS4 project settings were set up as DV-24P Widescreen 48KHz. I did not try changing other settings on the other tabs. I captured the video directly from the XL2 with no dropped frames. The resulting AVI plays back in Windows Media Player 11 correctly. What I mean by that is the is no jerky video, I get no raster lines, and the video quality is very clear. When I load the video into the time line and play it back in the program monitor the video jerks like it is dropping frames, I get raster lines and it looks like video clarity fades in and out.
At first I thought nothing about it. I used Adobe Media Encoder, and burned a DVD. Playback on my widescreen TV looked jerky, rastered, and the video was only clear in static scenes. So I made some test projects with different settings. Still had no success. The original capture looks good, but whatever I do in Premiere the video jerks and looks like old VHS video.
I did another test. I set the XL2 to 30P and 4:3, and captured the video. Again the captured AVI looks good. Put it on the Premiere timeline and played it in the program monitor. It plays fine - good video quality, no rastering, and no jerking. Made a DVD with no problems in the video. So my question is what setting in Premiere do I need to capture, edit, and export 24fps 16:9 widescreen video so that it plays back with with the same video quality as it was captured? Do you think it is an encoder problem? The captured AVI is what ever encoder came with Windows/Premiere as I have not added any other encoders.
Any help would be apperciated. If I have not supplied enough information, please just ask.

If the video is playing back badly in Premiere Pro from the timeline, then the things I would check would be the program monitor quality - is it set to highest...if you don't know where that it is, click on the 4 horizontal lines in the top corner of the program monitor - make sure highest quality is selected. It also may be a video card issue - are your drivers up to date? If the clips are only playing back badly on the PPro timeline (and anything exported from it), but fine in Windows Media Player - something is up.
As for the frame rate - no, you don't have to work at 24P...as mentioned before, the camera actually records at 29.97 fps, but is able to be played back and edited at 23.976 fps (or 24P)...it's a complicated explanation on how it all works...
If you're going to finish to a regular DVD, then working at 29.97 is the way to go. As for the interpret footage command, highlight the clips in your bin, then right click on them - in the menu, you'll see interpret footage - click on that and a new window should open...you should see a box with a check next to it that says remove 24P pulldown - click it (removing the check) and the footage frame rate should change to 29.97 - then click OK...create a 29.97 sequence (DV NTSC Widescreen 48Khz), and edit away.

What is the best way to handle .mod files in premiere pro cs4?

I recently got a JVC Everio GZ-MG130u and as I'm sure many of you are aware, it saves footage in the .mod format.
I have googled this and found quite a few different solutions, but I'm just wondering if anything has changed since some of these solutions were posted, or in other words, what is the best way at this current point in time to handle .mod files in premiere pro cs4?
As far as I know, the best thing to do is convert the .mod to .avi and then import it into premiere so it can be edited.. Is there a better way to do it than this? Also, by doing it this way, will I have separate audio and video tracks?
Thanks.

I have just done a bit of reading, here. All of the quotes that follow are from users who have posted in that thread.
It seems that there isn't one solid answer on this subject. The thread that I linked to was started 2 years ago, and replied to just 4 ago, so it's relatively current.
I noticed a couple different interesting statements:
posted by mmontgomery:
In the case of .MOD, you are actually getting a MPEG-2 file. The way
video files work is that there is a codec (COmpressor/DECompressor)
algorithm and a file wrapper (or extension). A JVC .MOD file is a
MPEG-2 encoded file, with a .MOD extension.
You're faced with two
challenges, first the .MOD file type is only recognized and support by a
few applications. I think we covered some of those already. The
interesting thing about wrappers and extensions is that they can be
dealt with in a variety of ways. Sometimes all you need to do to convert
the video file to a compatible video file is to change the extension.
In the case of .MOD files that's not enough. The .MOD wrapper apparently
does a few more things than just bare a unique extension name. It
requires a slightly more complicated method to convert that file. That
is why there is supplied software and that certain third party
applications have .MOD support.
(posted 2 years ago)
This seems to indicate that Ann's solution of simply re-naming the extension is not good enough, unless I am mis-interpreting what she meant.
However, another user said:
posted by futball8:
I edit with Adobe Premiere Pro CS3. All I have to do is simply rename
the .MOD files as .MPG and then import into PP CS3. It takes a small
amount of time to conform the audio, but no file conversion is
necessary. It's a pretty slick workflow and I've never encountered any
problems editing them this way.
(posted 5 months ago)
One can only assume that simply re-naming the extension from .mod to .mpg works in some circumstances, and doesn't work in others. I assume it depends largely on the editing software being used. Perhaps there are still issues that futball8 was simply unaware of or never encountered.
That said, there seems to be a couple of different real solutions to this problem that I have found:
1. Simply use an editing program that supports .mod file format. While pe7 and pe8 supposedly support the .mod format, the following should be noted:
posted by macksgarage:
While Elements 'supports' these files, it is markedly unstable and frequently crashes while using the files, though the application is otherwise reliable. The solution I have arrived at is to repair the container using ffmpeg. (see #3)
(posted 5 months ago)
2. Use a file conversion utility of your choice that will covert .mod to .avi, or another desired format. Import the resulting .avi file into premiere pro cs4.
3. Use FFmpeg. This seems to be the best solution as it does not convert any audio or video:
posted by macksgarae:
If you are not familiar with ffmpeg, it may be a bit of a bear to
learn, but it's not only useful for this, but functions as a video swiss
army knife useful for splicing, muxing/demuxing, and rendering just
about any format into just about any other format.
ffmpeg is an open source project from the linux world, but it has
been ported and is supported on windows. Fetch it here and place it somewhere handy
on your system.
To rewrite the container into a nice, standards compliant .mpg file
that doesn't make applications die, WITHOUT rerendering video or audio
itself, I use this command.
ffmpeg -i INFILE.MOD -acodec copy - vcodec copy OUTFILE.mpg
This not only renames the file, but actually rebuilds the container
around unmodified video and audio data, yielding a file which works much
more stably with Adobe applications, and presumably others as well, as
ffmpeg's open source development goals result in very standards
compliant files.
(posted 5 months ago)
Now, this seems to properly address the issues that can arise from simply renaming .mod to .mpg, as suggested by Ann. So from this point, I assume you can simply import the .mpg into Premiere Pro cs4 (or any other .mpg compliant program) and edit without issue, but it seems like I remember hearing something about Premiere not liking mpegs or something like that, so in that case, maybe it'd be better to skip this and go with option #2. But, it's been awhile since I've touched any NLE, much less premiere pro cs4, so I could be completely wrong and it may have no problems handling mpegs.
All of the things that I've quoted here came from the same thread, so I don't know how accurate any of this is, but the people that have posted these things seem fairly knowledgeable. If someone reads all of this and can confirm or deny any of it, it would be much appreciated.
Option 1 is not really an option for me, because I am sticking with premiere pro cs4 -- I'm not going to get another editor just because it has .mod support. That leaves me with options 2 and 3: Convert to avi, or change the file wrapper/extension properly with FFmpeg and then simply import the resulting .mpg file... Which is better? Or is there yet another solution that I am unaware of that would be even better?

Premiere Pro CS5.5 closes, but process in taskmanager doesn't

Windows 7, CS5.5.2
I had this happening to me a few times times, I click the x in the top right corner to close Premiere, it asks me to save my project, I click no and the program seems to close, nothing on the taskbar left either, but it's still there in the taskmanager as a 290MB process.
I discovered this when Premiere refused to start. Now I'm forced to close the process before I can start Premiere.
What's causing this?
It seems that more people had this problem:
http://forums.adobe.com/message/2920945
http://forums.adobe.com/message/3248472
Some had it solved by updating the video driver, but since I already have the latest one (NVidia) I don't see how that's going to solve it. I also have the latest chipset and audio dirvers as of yesterday.

In one case I waited almost 15 min.
While I was away I have done some rigorous testing with Microsoft's driver verifier tool, the same tool they use to certify drivers. I have found two issues that I solved by removing two conflicting programs. The last diagnostics run of driver verifier was 100% successful. I also did a rigorous memory test and that didn't show any problems either. As a matter of fact I'm been amazed how stable my system is running for almost 2 years now and trust me, I stress it a lot by running applications like Photoshop, Illustrator, Cinema 4D, games and even Vmware. It's also not a system that is cluttered with all kind of junk, since I restore an image of the system partition every 3 months or so. The backup only contains the complete installation of my OS and software BEFORE use. A restore of this image before I posted my problem in this forum also didn't solve the issue
Anyway, after using driver verifier, I tried Premiere Pro again, closed it 3 times after fiddling with some videos and now after the 4th time I close the program I have the same issue as before: the program seems to close, the taskbar is empty, but again the task manager is showing the adobe premiere pro.exe process. That process is now still visible in task manager after about 10 minutes.
The only thing I could try now is cancelling all non-Microsoft processes and services and see if the problem still returns. I'm open for any other suggestions.
Mind you, I could solve this issue by writing a script that kills the process after I leave the program, but:
a - I don't know if it will do any harm (maybe the process is still saving or updating files)
b - It just camouflages the issue and I never feel good about that
EDIT: I closed all non-Windows processes (as an IT professional I know what I'm looking at), stopped all non-Windows processes and killed the adobe premiere pro.exe process that was still running, I started Premiere Pro fiddled with some videos, closed the program and again....the adobe premiere pro.exe process continues to run....for several minutes now.
To sum it up: I have the latest bios and drivers for graphics card, audio and chipset. I ran Microsoft driver verifier and managed to run a full final diagnostics without any conflicts, I ran a memory test that didn't show any error, I restored a clean backup of my system partition, I have all the latest updates for both Windows and Adobe software, I even tried running Premiere Pro without running all non- Windows processes and services and the Premiere Pro process still doesn't want to close. I don't run any brand new model video card either, I'm using a 9800GT that has very mature drivers and the card itself was bought brand new only 6 months ago and has not crashed any game so far ( the best test for any video card) or any application that makes use of GPU acceleration, like Photoshop for example, which always runs at OpenGL/normal.

Adding metadata in Prelude but Premiere Pro not retaining it after closing

While in Prelude in CC, I'm adding metadata in the Dynamic Media list; i.e., Scene, Shot Name, Shot Number.... I save the clips after each update and send it over to Premiere Pro by highlighting all the clips. It arrives in Premiere Pro with the info attached and visible on the clip and in the metadata. I save Premiere Pro and Prelude and when i reopen Premiere Pro there's no information there anymore; it's there in Prelude when I reopen that. Not sure what's happening. I did save the metadata separately also.
Message was edited by: Layne Batt

Hi Jenny,
thank you for taking the time to reply.
The media is from a Canon 7D ( MVI_####.mov ) shot in full HD in
1920x1080p at 30fr
as I'm answering this email i'm checking that project... and now it's there
again in full. I was missing metadata in the first 3 rows of data
information.... Scene, Shot Name & Shot Number. I used those three columns
because that was the order in the metadata check list.
This is on my Win 7 computer w an Nvidia quadro fx 3800 card and 8 gigs of
ram.... I am still having some of the same issues as well on my Mac OS
X.... 12 core... I'll need to check that again too.
I'm not sure if this problem will be persisting... right now it's
inconsistent. will continue testing on both computers... not ready to put
it into my workflow yet.
thanks,
Layne

Premiere Pro 5.5 - All Grown Up

Similar Messages

Maybe you are looking for