Premiere CS3 crash

Hi all,
First I'm french, so excuse me for my poor english ; i hope you can help me solve my trouble anyway. :)
I'm running Adobe Production Premium on a Windows XP 64 based workstation. As XP 64 has a virtual 32 bits layer, I could install and run each software with no trouble, except Premiere Pro and Encore (which seems like connected to Premiere).
I know that CS3 products are not designed to run on 64bits systems, and that support is not provided by Adobe on 64bits systems, but they advised me to post on this forum by phone ; so y try :)
When I launch Premiere Pro, there is a window that asks if I want to create a new project or open an old one. As soon as I click on "New Project" and give details about it, Premiere Pro crashes. It seems like it crashes when loading the timeline or something like that.
Windows log files say that ntdll.dll crashed, but I couldn't find any link between these 2 troubles.
I really hope that someone will manage to help me.
Kind regards,
Raphael, France

>As soon as I click on "New Project" and give details about it, Premiere Pro crashes.
Try this:
Go to your "My Documents" folder and find the Adobe\Premiere Pro\3.0\Layouts folder. Move it to your Desktop. Be sure to move it, not copy it. Do the same thing for the Archived Layouts folder.
Launch Premiere Pro again. It will build new layouts for you.
If that fixes the crash, then delete the folders on your desktop. You will have to rebuild any custom workspaces that you had.
If it doesn't fix the crash, then put the folders on your back where they came from so you don't lose any of your custom workspaces.

Similar Messages

My Premiere CS3 crashes when I am exporting anything.

Premiere CS3 crashes on my HD project Most of the video i am working with is from the new 5D The files are as I recorded them on the camera there have been no conversion done to them. when ever I try to export anything out of premiere it crashes and windows Vista 64 crashes with it showing a blue screen and restarting the computer. I don't know whats the problem. I think it mite be my hard drives or something on the hardware end.
I am running
E8500 processor with 4 gb of ram DDR3 1600 Asus P5Q3 mob and Ati 4890 graphic card also I have 2 big hardrives and two 500gb drives on Raid.

BSOD can also point to heat, bad RAM, MoBo issue or power supply not adequate, along with Jeff's suggestions.
This ARTICLE might point you in the right direction.
I cannot recall if that article mentions Speedfan, but if it IS a heat issue, that will help you sort it out.
Good luck,
Hunt

MSVCR80.dll error - help!!! (Premiere cs3 crashes!)

Hi,
I searched all the internet regarding this problem, found alot of threads concerning it, but none really helped me...
Yesterday I installed TINDERBOX of Foundry co. effects. some plugin of after effects.
Since then, whenever I open my premiere cs3 on the project I was working on, it crashes immidiately! I can't do anything. ( if i open a blank one, it seems fine. but i didn't use the tinderbox effect on the project which is crashing...)
I have vista64, and it pops this window saying:
Problem signature:
Problem Event Name: BEX
Application Name: Adobe Premiere Pro.exe
Application Version: 3.2.0.0
Application Timestamp: 47fd3df6
Fault Module Name: MSVCR80.dll
Fault Module Version: 8.0.50727.1434
Fault Module Timestamp: 4757746d
Exception Offset: 00008aa0
Exception Code: c000000d
Exception Data: 00000000
OS Version: 6.0.6001.2.1.0.256.1
Locale ID: 1037
Additional Information 1: 8d16
Additional Information 2: d1b85fd63d9c87b5d7951cba718203fc
Additional Information 3: c80a
Additional Information 4: a2f07b4c887b117fbc63cc0679ff8128
Now, the funny thing is I searched all my MSVCR80.dll files and found many, all under adobe folders. neither had the version : 8.0.50727.1434. All had 8.0.50727.42!
I searched all my computer for the 8.0.50727.1434 version but nothing!
I unistalled the tinderbox effects - didn't help..
I remember that during my installation of tinderbox it poped up this window error about MS visual C++ library, and I read somewhere that this library may cause premiere to crash, so I uninstalled the library Tinderbox had installed, but nothing...
I tried to installed a new verion of C++ library for 64bit - nothing...
So now I can't open my project... it's a disaster!!!
What can I do?
Help!!!
Roy

>I tried to installed a new verion of C++ library for 64bit
PPro is a 32-bit application. I'm not sure how you expect it to use a 64-bit library.
Go back to a 32-bit operating system where you
know PPro will work properly.
Cheers
Eddie
PremiereProPedia (
RSS feed)
- Over 300 frequently answered questions
- Over 250 free tutorials
- Maintained by editors like
you
Forum FAQ

Premiere (CS3) crashes everytime on RAM preview

hello all,
i am having a problem with a project i am working on in premiere pro CS3. Everytime i go to do a RAM preview, the dialog box comes up and says "Rendering 1 of 8 Audio Previews" and gets stuck there and eventually freezes up. I've noticed if I take the video clip i want to render into a new sequence and do it, it works fine. however whenever i go to export my clip as a qt, or wmv, using media encoder, i get the "serious error has ocurred" and then my project crashes for good.
any thoughts on how to rectify this? thanks

thanks, i'll try that, i should post a couple of things i have tried already that have not worked:
- i've started a new project, imported that one in, but still the same problem
- i created a new trimmed project, therefore creating new medial files based on what has been edited thus far, and still get the same problem.
i do believe it does have something to do with the audio, because when i bring just the video into a new sequence and render it, it works fine.

Adobe Premiere CS3 crash with Export Adobe Media Encoder

Hello,
I having a problem with Premiere. When I want to export my sequence with Adobe Media Encoder, Premiere crash. I tested the solution proposed by this link: http://kb2.adobe.com/cps/404/kb404804.html but no success ...
My computer configuration:
- XP 64
- Dual Xeon
Thank you,
Kevin

A link with many ideas about computer setup http://forums.adobe.com/thread/436215?tstart=0
Computer DETAILS are always good to provide
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 the DETAILS asked for in the questions at the end of the troubleshooting link

Premiere CS3 Stops when loading that 1 project !

Dear friends !
I have Vista 64
I use Premiere CS3
And recently upgraded my video card
I was working on a music video about 5 mins long , I added all effects , transition and etc, I have total of only 4 layers plus 1 audio.
Everything went smooth and I exported it to movie and got my final AVI, but suddenly I remembered that I had to add a 20 seconds clip
at the end, so I reopened the project and Premiere CS3 crashes !!
But if I open any other project, then it works fine.
So, I took my finished AVI (the one that I made earlier) to Encore CS3 and Encore Stopped as well ...WTH.
Then I Used my AVI to create a new project and added that 20 sec at the end of it, then "Export to Movie" again
result was fine , then I used the same project to "Export to Encore" Encore crashed ...WTH.
when I play that AVI file that I made earlier with Windown Media player, then it works fine.
Any Ideas !!

Glad that you got your Project finished.
As for what can freeze PrPro, well lots of things. These can be issues with the system, the Project, the Assets, and a few more.
Not sure what went wrong with your FLV to AVI conversion, but some converters play fast and loose with their export.
One thought for next time, or maybe to resurrect this Project is the Moyea FLV Importer plug-in for PrPro. It will work with PrPro 2.0, and I believe with CS3 too, though will not work with any flavor of CS4. For me, this plug-in works perfectly with FLV material, and all conversions are internal, and have yet to cause any issues. I use it with PrPro 2.0.
Good luck,
Hunt

PREMIERE PRO CS3 CRASHING on SNOWLEOPARD OS

Please Help!
I searched the forum - but I couldn't find anything that matched this exactly.
Adobe Premier Pro CS3 crashes every 5-10 minutes or so on my mac with no crash report!
I am running the fastest MAC available - with a solid state hard drive and 24G of RAM and ATI Radeon HD 5870 card.
After the first few crashes, one report came up - "Premier Pro Debug Event" - and I took a screen Grab for dear life.
It reads:
Premiere Pro has encountered an error.
[/Drusilla/pro/3.2.0/Libraries/UIFramework/Make/Mac/../../Src/
Document.cpp-53]
Kind Regards,
Ultan

hmmm,
that ssd stuff is over my head to be honest. I've heard that some systems with ssd work really fast but I have a feeling that the seek time and speed etc is not quite up to par in some cases... I've only read a little about this ...so all I know is that the ssd stuff hasn't been totally tested and proven, like normal hard drives have been...raid and so on
basically what you want is to spread the load over the most hard drives you can so the seek time and response time ( in accordance with your ram and demand on the graphics card ...front side bus, etc ) is the fastest you can make it...how that happens is mostly dependent ( IMO ) on the material you're working with ( source stuff and export demand -- or product ).... ssd just doesnt automatically say anything to me personally cause I have no clue how fast it is ....and this is a physical thing ( how close to the center of the drive disk is the pagefile, info you are dealing wtih etc )
most drives for editing are 7200rpm and average seek time is below 10ms... with raid and decent allocation of drives this gets sorta "as fast as it gets" ....and you have to just deal with it. Since I dont know exactly what you have and what you can do to make it faster there's not much I can say about this. You might have to put your os and programs on a fast hard drive and use some raid array for your source assets and exports and so on.. depending on tons of factors.... ( intermediate prores 422 and proxy editing ? )... I have no idea. As a rule I would say, get the biggest fastest hard drive you can for you os and programs and then get the biggest and fastest hard drives for your assets and exports....and if they are only 10% used, all the better....makes them faster seek time wise....and look at Harms info re: all the basic hardware configs to get the most out of that...and shut down everything that is running in "background" that you dont need for editing...

Large project in Premiere CS3 causes Windows XP64 to reboot

Ok...I have a rather sizeable project going in Premiere CS3. It contains a rather large number of animations created in Autodesk Maya (most between 10 seconds and 3 minutes long) and a large number of stills, as well as scrolling background (a .mov file I created using Photoshop and Premiere) and a soundtrack created by myself (in Cakewalk/Sonar). The total project is about 18 1/2 minutes in length....around 8 video tracks and 3 audio tracks at the moment. The main problem is that when I start working on it...either importing files and especially moving files around in the project or even just hitting the playback button, the system just reboots. I have seen the infamous Windows "blue screen of death" flash briefly once or twice, but it doesn't hang...just goes right to the system BIOS screen. The ONLY thing that seems to help is basically saving the project like every 30 seconds. Import a file, save, conform file to widescreen, save, bring file into project, save, move file around a bit, save, add crossfade, save....you get the idea.
Now before I go too much futher here, I suspect the problem isn't actually with Adobe/Premiere as I had this happen a few times while I was creating the sound track in Sonar 4 as well. The sound track is basically a pseudo-orchastral piece and is equally around 18 1/2 minutes long....currently with around 42 tracks of audio and 5 midi tracks. The audio has been sampled down to a standard stereo wav file for the import into Premiere. And yes, as the audio portion of this project got bigger and bigger, it caused a few reboots as well (not to mention drop-outs, studders and all the other fun stuff associated with audio production). With that, I was able to "compact" the Sonar file (basically a Sonar project defrag) and the reboot problem seems to have went away on that end.
The system itself SHOULD be able to handle this project...not top of the line, but pretty beefy. 2nd generation Intel i5 quad core, 16 gigs of Kingston DR-1600 RAM, Tascam US-428 for the audio and a good 2+ terabytes across 5 harddrives (3 internal 3 gig-per-second SATA's, 2 USB). Also has a 4 gig HIS vid card with ATI chipset (still can't afford a FirePro yet). While Premiere is installed on the (comparatively dinky) 160 gig C drive, I'm using the 500 gig E drive internal and a 500 gig USB drive as my work drives. Most of the Maya animations are on the internal E drive but the rest...the stills and Premiere files and such...are on the USB drive. I.e., the system itself should have plenty of rendering power for this. Also I have replaced the C drive with a nearly identical twin. After a recent crash, I finally broke down and got a backup C drive...in other words, I'm sure the drive(s) are a-ok...even put a brand new 500 watt power supply in just in case.
I have already re-installed XP64...a couple of times in fact, as just before I started this project one of those god-foresaken MS "critical updates" crashed the crap out of my computer. Then on the first reinstall, something hosed in .NET framework during the "night of a thousand updates" so I had to scrap it and start the reinstall all over again. Likewise, I reinstalled Premiere CS3 (along with everything else including Maya) once I finally had the computer running again.
A quick note here: I did create my own custom 1080 Hi Def widescreen settings for Premiere since CS3 didn't appear to have any such thing. For short projects they seem to work just fine...although admitedly, the render time is a serious b*tch. Likewise, all the Maya animations have been rendered out at 1080 widescreen, production quality (yea...the render time there was a killer too).
Another quick note: While I'm trying to use Premiere exclusively while I'm working, on occasion I have had to open either Photoshop or Maya to deal with a couple of stills...and when I open something else, I get a "windows virtual memory to low" (16 gigs of RAM and the virtual memory is too low??). Otherwise, except for Avira (virus scanner) I don't really have anything else running in memory...no screen savers, no desktop pictures, no Instant Messanger crap, etc.. Never cared for bells and whistles and such, so the system is pretty clean in that regard (and I do keep up on my degrags as well).
Finally, while I -am- grateful for any helpful suggestions regarding this, please do NOT simply tell me to upgrade something (Premiere, Windows, etc) as point blank; it ain't gonna happen. Aside from the fact that Adobe seems to have made Premiere CS4 and up much more difficult to use (I have -many- niggles about the newer interfaces there...using CS5.5 at the college and it's REALLY annoying) and aside from my wife being a MS programmer/developer and having to listen to her complain about Windows 7 and 8, we're in the process of buying a new house, so any and all "disposable income" is nill...and will be for quite some time. No money...zero...nadda...i.e. no upgrades. Further, while granted this is certainly the biggest project I've done to date, I've ran this setup/configuration for at least the past 3 years now without a hitch...this all seems to have started with that last MS critical update (at the risk of sounding paranoid, I'm really starting to think they slid a nasty in that last one to FORCE people to upgrade since they're discontinuing XP64 support soon).
Alrighty...I know that's a lot but I wanted to provide as many details as I could here in hopes that someone can help me get a handle on this reboot issue. Getting to be REALLY annoying having to save every 30 seconds or so. I have searched the help files, but got tired of randomly sorting thru all the blather and not finding anything helpful.
I'm grateful for any help here...thanks!
Jim

Well, I'm about 98% sure it isn't a hardware problem. I had already pulled the RAM and tried some backup RAM I have sitting in the box (8 gigs of Corsair), went thru the harddrives weeks ago with Chkdsk and everything was a-ok there (a couple of bad clusters on the old C drive, but that has since been replaced and is on the shelf as a backup), motherboard seems to be fine, re-seated all cards and cables, etc.. Again I even slapped a new 500 watt PS in just in case (the old one was a 400 watt and with all the crap I have on this system, thought it might have been a voltage drop off issue...nadda). I did have a bit of a heat problem a while back...one of the case cooling fans was going bad and the CPU was getting just hot enough to trip the system (about 5 degrees over). That said, that also shows up in the BIOS monitor as well and was easy enough to track down. Either way, the bad cooling fan has been replaced and I even added a "squirrel cage" style fan as well...system is running nice and cool now.
BTW...I used to be A+ certified on both PC's and Macs when I was a hardware tech (not to mention HP, IBM and Lexmark certified, Cat 5 installer, etc), so I like to think I know my hardware fairly well. Not just a weekend warrior on that front...used to do it for a living.
I had also already tried manually resizing the paging file as well...tried different sizes, tried spreading it out across the drives, etc.. Didn't really make a difference either way and again the only time the virtual memory low comes up is if I try to open Photoshop or Maya while this big project is open in Premiere. That said, Photoshop and Maya both tend to be pigs when it comes to memory/RAM (Photoshop especially). Doesn't seem to happen with Illustrator or any other program....just PS and Maya if this project is open in Premiere.
One other oddity I have noticed recently is actually with Maya. Before all of this started...in other words, before that last MS critical update and 3 days of reinstalling software...I used to be able to do a background render with Maya and still be able to keep working on stuff. I'd fire off batch render and then I could move on to other things...editing images in Photoshop (CS 5 there if it matters), surfing the web and even doing some light stuff in Premiere. Since this problem has been occuring however, I have noticed that the Maya batch renders are REALLY slowing down the system big time. Difficult to even check my email while a batch is running. Likewise, I have noticed that since I upgraded the Maya from 2011 to 2013, Maya has a nasty tendency to freeze during a batch render. If I have a long batch render, I'll set it up to run over night...when I get up the next moring, the render itself will still be running (you can see Mayabatch.exe still going in processes under Task Manager) but Maya is totally frozen up. Now I did that update at the same time as the rest of this mess happened so I don't know if these problems are due to the Maya upgrade or the (apparent) Windows problem...I'm inclined to believe the latter.
BTW...after having a project file get corrupted yesterday during one of these shut downs, I've been double saving the files (so as to have a backup) and that too seems to have made things a bit better. Hasn't actually shut down on me when I've been doing this. That said, it's also a serious pain in the butt having to save that way too.
With that, looking thru the rest of Hunt's article there, I did kill indexing services...at least on the work drives. it's about the only thing there that I haven't tried, so we'll see what happens this afternoon. I seriously doubt that would be the problem though as usually that would give an error or a lockup and not an instant shut down, but we'll see.

Error compiling movie: out of memory !!! Premiere CS3

Hey every1 --- desperate need of some guidance here. I've been all over the internet and these boards --- have seen this come up with a lot of people but no real solid answers that I'd seen or that have helped.
First off, my comp is an imac 3.06 Ghz Core 2 Duo, 4GB memory. (just bought the computer last year)
I'm shooting with a canon 7d in HD (1920 x 1080p) and I'm editing using Premiere CS3. I've noticed that editing has become very difficult since I started using HD; playback is very choppy and the 'quality settings' in the preview monitor are a joke and do absolutely nothing whether it's on draft or automatic.
Anyway, despite the choppiness and slow editing, I was able to get a 3 min clip completed. These are my export settings:
Export > Movie
H.264
960 x 540
23.976 fps
Square pixels,
100% quality,
recompress: unchecked.
Once exported (I was able to export smaller timelines previously--- say, 50 secs of footage or so) the files look AMAZING and from there I use them for online video via vimeo -- stuff looks really awesome.
Anyway, recently I'm getting: 'Error compiling movie. Out of Memory. Change optimization preferences to memory', etc. etc. Well, I did as it asked and that did absolutely nothing.
So, I decided to open up my activity monitor and watch what's going on with my memory while premiere is exporting. I also closed ALL unused applications. System runs at about 2.16gb free memory before I start exporting. Memory seems stable during export UNTIL around the 50% exporting mark, and then its starts climbing like crazy and my memory just gets eaten up --- finally resulting in a crash at about 70% render.
I really don't know what else to do. Does my computer not have the power to export 3 min of HD footage??? This seems surprising to me ... I don't know what else to try.
Thanks for any help !!!
-Mark

Hi Mark,
Hope you are having a wonderful day.
Sorry to hear that you are having such a hard time. Although I did not specifically get the out of memory error, I can only be convinced that that is the problem.
Although I am not a computer whiz, I have learned my share of things. I have been troubleshooting a video all this week (really, a couple of months), but I had to put it aside and come back to it.
I tend to be talkative; so I will get back on topic or at least try to stay on topic, so bare with me. Smile....
Here is what I have learned and maybe it will help you with yours if you have not found a solution already.
Based on your hard drive specs and ram, I was thinking the same thing e.g. hard to believe that you are not able to render 3 minutes of video in HD. I primarily work in HD/1080p.
The place where we are similar is that I eventually could get the video to render by reducing the workspace that is rendered piece by piece until I was able to render the entire file. When I tried to encode the video, I kept getting error compiling messages. I tried different codecs, deleting xmpses, not rendering xmpses, etc. I could not figure out the keyframe trick so I just put in a black video from after effects. By the way, all of my videos intro the same and no problems with the other videos fading from black to a still photo.
Here is the problem from what I could gather.
Simply, out of memory. I was rendering and trying to encode a 45 minute video with after effects compositions and the dynamic linking kept timing out once the file reached a certain size. There were no other true fancy effects. I do alot on the green screen and just use after effects to make a white background. Smaller videos, rendering has been slow, but doable. This massive video would never compile. I won't bore you with my system specs, but know that similar to your situation, the system in theory should have been adequate.
Work around...
I ended up exporting the video as 3 separate 15 minute video clips. I could not get them to encode as .wmv files so I encoded them as .mp4 files. By the way, I still encoded in HD.
Here is the kool stuff.
After what seems like forever, I found a converter that could convert .mp4 to .wmv and rejoin the files to play as one large file with the same quality as my source file and no audio synching issues. By the way, I do not work for this company. I just found this encoder at 4 o'clock this morning after trying all of these other converters that were straight garbage or were free to try and not really free if you wanted quality. By the way, the conversion tool is not only user friendly, but free which is awesome.
The name of the software is Media Cope. Just visit www.mediacope.com.... Be sure to send the owner an e-mail to thank him and let him know that Mark sent you. I just sent him an e-mail earlier to let him know that I was going to post on Adobe what a wonderful software he created. I just needed something free, quick, easy, and user-friendly.
Whoops... got off topic....
I'll do a summary at the end for my recommendation to you.
Here are some other tidbits that I learned as well that may save you some time.
When editing this is what I do now...
1) I use CCleaner from www.piriform.com to quickly clean my system especially temporary files before I start editing and if I am switching from project to project.
2) In all of my troubleshooting this week, I found a kool little software call Smart Close. (Just google to find this one.) It closes all of your non-critical background files in order to maximize system resources. (When I am done editing, I just reboot and all of my background programs start up again. You do not have to do it that way, that's just how I do it. The nice thing is that it is a wizard interface; so you do not have to try to figure out if a process in the background is critical or non-critical.)
3) Depending on my mood and if I did not forget, smile.... I change the priority to high for the adobe products in the task manager.
More things that I learned...
1) We are not able to change the temp file for how Adobe encodes. My logic was if I could change the encoding to a hard drive that was simply empty so Adobe can render there, then I would be good. Wrong.... Adobe does not allow you to change the temp location. (Note: This is what I discovered in the different forums; so encoding to an external hard drive is not the best move. Read more to se why.)
2) It is best to have your scratch disks as your internal disk. If you have multiple internal disks, then you shoud check some other forums for the best way to set up your scratch disks. When I was just starting out, I bought an external hard drive enclosure with the thought that I would work primarily off of those external drives with the option of doing some RAID work. Bad idea... Even the simplest of tasks took forever. It was best to work off of the internal drive. By the way, I still use the enclosure hard drives for backups in order to allow me to free up some space on the primary hard drive. When rendering, it is truely a use of the RAM and the hard drive space in the editing process.
I'll leave you with this...
I take back what I said earlier, you do need a new computer with more RAM. If you can get 16 GB, great. The primary reason is that if you are editing in Premiere and if you do anything with dynamic linking into your after effects, it will cause your ram to climb as the file gets larger. Of course, be sure to get the largest hard drive possible as an internal drive, the maximum on processor speed, 64 bit operating system, etc.
I know you are like by now, Mark, what is the point of all of your gibberish... Really, it was to share with you and others on some really kool work arounds.
My recommendation for you are as follows.
1) You have already proven that you can render and encode 50 second clips and you are very happy with those clips, so create separate smaller clips for this particular project.
2) Once you have the final clips outputted, then use Media Cope to rejoin the files as one large file and you are done.
(Note: The one thing that I did notice is that there is a small break right between where the files are merged. The nice thing is that as a video editor/film maker, you will be the only person likely to notice it because you know where the breaks are. The other nice thing is that the untrained eye will not notice it and if you had to submit your work to a television station especially on DVD, the video system should recognize the file as one large file and play all the way through. Note: For the last sentence, I said 'should play all the way through' as I have not had a chance to check this one yet as I just finished this project today and still have to turn in all of my videos. I still have some more videos to merge.)
By the way, the only specs that I will share are that I work on a PC and it has 8 GB of ram.
The summary of the summary is that sometimes an error compiling message could simply be that your system does not have resources to render and the encode that large of a file. At least that is what I learned this week or at least my specific situation. The confirmation is that I just finished shooting a documentary which was one hour and some change and was able to render and encode to .wmv with no problems. Of course, I was not using after effects for this particular project.
In either case, hope all the information helps you with your project.
Have a wonderful day and happy holidays everyone.
Mark

Adobe After Effects CS3 crashes with Codecs such as Motion JPEG and Avid DnxHD

Hey guys, I'm new here
I'm having a problem with After Effects CS3 crashing with .mov files (exported from Adobe Premiere) with codecs such as Motion Jpeg A and Avid's DnxHD. Its driving me crazy.
If I import a Motion Jpeg A file, AE crashes immediately. If I import a DnxHD file that works fine with Premiere, it seems to import ok. However, when I try to play it in AE it comes up as a plain white... thing. If I move the slider across it previews one or two frames before AE crashes. Its driving me crazy.
AE works ok with H.164 and animation files.
I'm reinstalled quicktime and Avids codecs, uninstalled ffdshow, disabled Open GL and multiprocessing, changed between 10bit and 8bit (whatever that is all about) with the dnxhd and I'm really stumped. If I can get Dnxhd working I'm fine with that. I thought I'd mention the Motion Jpeg A codec to see if they're a result of the same problem.
I've also tried Avid's RGB packed Codec with the same results.
I'm running Windows Xp 32 bit with 3gbs of ram, a GeForce 8600 gt with a Intel Pentium Duo Core Processor 2.00 GHZ.
Can anyone help me please?

I'm mistaken, Animation files don't work either!
I tried that with no luck. I even tried a few more Quicktime codecs with the same results.
Only H.164 and some png compressed .mov files seem to work. Very frustrating.
I'm surprised thats the case - I am defintley due for an upgrade. Even though this system seems to work ok, struggling a little bit with HD .mov files but yeah, I've been planning a new system for a while.

No audio in Premiere CS3

Hi
I have just installed CS3 onto a brand new machine, and no audio of any type is playing from with Premiere CS3 - I have tried all the usual video formats, MP3, WMA etc which all worked on my last computer. (audio in other windows programs works fine). I do get a message when I start up CS 3 which says "The currently installed soundcard driver does not support DirectSound Input, Recording audio is not possible" This obviously doesn't mention anything about playing back audio.....
Anybody have any ideas?

John, Thanks for your reply. In fact, the audio is built in to the motherboard on my Dell. I'm a little confused by the error message though... It says that, with my present sound card, recording will not be possible. Hmmm... Does that mean that I can not record narration by plugging a mic into the sound card, but that audio from my source tape(s) will still be recorded? I'm just getting started with CS3 after I have experienced a 2 month nightmare of crashes and a multitude of problems with Premier Elements 4. (The Adobe techs finally admitted to me that Premier Elements 4 really isn't cut out for HD processing/editing). Anyway, back to the sound issue.. It appears as though the sound from my source tape is being recorded as is sound from a CD or a file. If it's just the mic input that won't work on my sound card, it's no big deal as I do no narration. If you know the answer to that, I'd appreciate hearing it. Thanks so much for your input! Kent

How to get HD presets in Premiere CS3?

Hi,
I use Adobe Premiere CS3 under W7 and I would like to import, process and export movie clips in HD resolution (1920 X 1080).
The files to import are video files having a format .wmv or .mp4 with the above mentioned resolution and located on the hard disk.
When opening a new project I have the presets folders for DV-24P, DV-PAL, DV-NTSC and folder HDV which is unfortunately empty.
Looking In the Adobe Premiere Pro CS3 Program File I found a folder called Settings which contains a folder HDV with all the HD presets such as HDV 1080i30.prpreset or HDV 1080p25.prpreset.
How can I "move" these presets into the empty presets folder HDV in the program in order to access them?
Many thanks in advance for any help you can provide.
N.B. So far I can import the 1929 x 1080 clips , but then they are processed and exported as 720 x 576 files hence loosing the original HD resolution.

Do you have a USB hard drive handy?
If yes, you need to make a full boot drive backup to that USB hard drive before changing anything
Hardware crashes or virus infections or simple software problems happen, so you should buy AND USE software to make a full backup of your hard drive to an external USB hard drive... plus, making step-by-step backups during a new install or major program addition makes it easy to go back a step if something doesn't work
This backup and then restore is, of course, only to the same computer with a new drive (or the same drive as long as you don't mind writing over everything) since doing a restore to a new computer won't work due to Windows and many programs having activation information that is keyed to your hardware (which is why Windows will force you to RE-Activate if you change very much hardware)
The product I use is at http://www.terabyteunlimited.com/image-for-linux.htm
Image runs off of a bootable CD via Linux (the Zip you download includes a program to make the bootable CD) and it reads EVERYTHING on the drive, even the hidden registration information, so everything is restored when needed... and you may restore the image to a brand new drive in case of a crash, and not have to re-install anything
Please note that I own no part of Image, and I don't get a referral fee (that is just a plain web link) but I use the program and it has saved me a LOT of trouble when I had a hard drive die... and I was able to restore everything and not have to re-install or re-activate a single program, from Windows on up

Prepro CS3- crash when export to flash

In Premiere CS3, every time I try to use the Adobe Media Encoder to export to Adobe Flash Video, it crashes as soon as it starts to render; an error message pops up for 1/2 second before the whole program quits:
OMP abort: Initializing libguide.lib, but found libguide40.dll already initialized.
This can cause performance degradation.
Set environment variable KMP_DUPLICATE_LIB_OK=TRUE if you want your program to continue in this case.
Is this the solution? How do I set an environment variable?
Thanks in advance!
Production Premium CS3), fully updated
Windows 7 64bit
EVGA nForce 750i
4gb ram
GeForce 9800GT
Creative X-Fi
scads of hdd space

nevermind, here's the solution:
http://kb2.adobe.com/cps/403/kb403633.html

Impossible open project Premiere CS3

Hello, sory for my english, I´m from Czech republic.
I have got a big problem. I can´t open project in Adobe Premiere CS3(update 3.2.0). I worked on this project more than 5 mounts. During loading the project Premiere show message "p:\drusilla\pro\3.2.0\mediacore\mediafoundation\ap i\inc\Keyframe/Keyfrarr.. and than crash.
I tryed everithing I know: Autosaves not work, import to new project, reinstal program and windows, open offline....
Project is very big - 97 Gb.
I have Windows XP Pro SP2 with CZ lokalizacion. Smaller projects work fine, without any problem.
Please help me, Johny A.

Johnny A,
Lets do a review:
You had a Project that has been worked on for five months and all worked fine. The Project opened in PP perfectly over that time. You then recorded a WAV into PP, edited some more, and now your Project will not open, and you get the error message. Did the Project function properly, after you recorded the WAV, before you Saved and shut down? If not, what seemed to be happening then?
You have attempted the following:
1.) Open Project in PP - result does not Open and gives error message, followed by crash
2.) Open all AutoSaves - result does not Open and gives error message, followed by crash
3.) Started a new Project with the same specs. as your old and tried to Import the original Project into it - result does not Import and gives error message, followed by crash
[Good things to try, BTW]
Does the info in this link help:
Eddie Lotter, "import failure - error message 1231" #1, 11 Jan 2009 1:19 pm
Has anything changed on your P:\ drive? What are the specs of your P:\? How is it connected, internal, external FireWire, USB, etc.?
One thing that you might try would be to Move all of your Assets to a new location, especially the WAV file(s). Try to Open your Project again. As you have hidden the Assets from PP, it should ask you to locate them again. If you kept the same folder structure, but just hid the structure, you should be able to help PP locate the files and let it load them up again. Id make sure that I hid the WAV file(s) even further away in the folder structure, so you can *possibly* get the rest of your Project loaded, and just Offline the WAV file(s) for now. Then, do a Save_As, or Save_As_a_Copy (without the WAV file(s). If you get the Project back to that state and Open, then try to re-Link the WAV file(s). Have a look at:
http://www.adobeforums.com/webx/.59b78a80/7 if you have any questions about Save, Save_As etc., and why/when you might choose one, over the others.
Last, there is a freeware program, XML Wrench. It can do a lot of detective work on your .PRPROJ file. Ive only used it sparingly, but others here can step you through its operation. First, however, I would download and install it. Run your PRPROJ though it and report back with what it says. Usually, a corrupt file will have bad header info. If this is the case, others can possibly direct you with way to repair that header info. There could also be some other problem, that folk here will recognize and help you cure.
Good luck,
Hunt

Premiere CS3- HDV problems¡¡ Help¡¡¡

Hi
I have been working in a movie since 2009, in Premiere Pro CS3. Project settings: HDV 1080i. I have been having a lot of problems with the render process, new timelines, and saving the project. Sometimes when i make renders, save the project, close and open again, It doesnt save the render, so I have to start from the begginning. But that´s not the big problem. 2 weeks ago, I capture 4 hours of hd video and aded to the project. Since then, all my other sequences have dissapear. I only have the main sequence with the movie, and the rest of the sequences are still ther, but only as video clips, not as sequences. So, I´m just working in one sequence, one timeline. The size of this only sequence is about 7 hours in full hd. Since then, Premiere have been crashing every 5 or 6 minutes. Sometimes when I´m working and I want to save, it pops up a message and say that it cant save the project becouse of an unknown problem, so I try to save it in a different location, but it doesnt work, so simply, I cant save my project.
This is the machine Im working on:
PC Microsoft xp Profesional, Version 2002, AMD ATHLON 64x2 Dual Core Processor 5200+, 2.61GHz, 3 gigs RAM..
Hard disk memory: I have like 130 gygabites available. The size of the project with all the captured videos, autosaves etc is about 200 gygabites.
I really cant understand the problem, I have uninstall and install two times Adobe Premiere cs3 and every time I have the same problems. Somebody tell me that Premiere only works fine with less than 4 hours of video in the timeline so, is this my problem? Is it the computer? I really cant undersatand.
I really need some help.
Thanx

First, read Harm on drive setup http://forums.adobe.com/thread/662972?tstart=0
Then, 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

Premiere CS3 crash

Similar Messages

Maybe you are looking for