Error message in Premiere Pro CS3

When I try to export my project whith Media Encoder in MPEG2-DVD format, after more than 70%, I received "Application failed to return a video frame. Action has been canceled" error. I use Windows XP Pro SP2, Athlon 64 3000+ Proccesor, 1GB DDR memory, 2x150Gb harddisks in RAID 1. I succesfuly exported movie in DV format and this is the result:
Type: AVI Movie
File Size: 10,1 GB
Image Size: 720 x 576
Pixel Depth: 720
Frame Rate: 25,00
Source Audio Format: 48000 Hz - 16 bit - Stereo
Project Audio Format: 48000 Hz - 32 bit floating point - Stereo
Total Duration: 00:47:32:24
Average Data Rate: 3,6 MB / second
Pixel Aspect Ratio: 1,067
Created with: Adobe Premiere Pro 3.0
Project: C:\Documents and Settings\Black Dolphin\My Documents\Adobe\Premiere Pro\3.0\1.prproj
AVI File details:
Contains 1 video track(s) and 1 audio track(s).
Interleave: 1 : 25.00
Video track 1:
Size is 9.54G bytes (average frame = 147.80K bytes)
This movie appears to have DROPPED FRAMES
There are 71162 keyframes.
There are 162 empty frames.
Frame rate is 25.00 fps
Frame size is 720 x 576
Depth is 24 bits.
Audio track 1:
Size is 522.39M bytes

Try this.
Cheers
Eddie
PremiereProPedia (
RSS feed)
- Over 300 frequently answered questions
- Over 250 free tutorials
- Maintained by editors like
you
Forum FAQ

Similar Messages

Error message transferring premiere pro CS3 project ot Encore

I use an earlire version of Premiere pro with no problem. I cannot use CS3. I can create a project and try to export
it to Encore to burn it to a DVD, but I get the following message:
PGC "project name" has an error at 00;05;55;14 Internal software error %0, line "project name"-PGC info;name="project name", ref=Bpgc,time=00;05;55;14
One person suggested changing the Bitrate from variable to constant. I did that. Same error message.
I'm really frustrated. Can anyone help?

Ah, the dreaded PGC error. I would suggest that you head to the Encore Forum, and do a search for "PGC." There are probably 5 threads, and two are very, very long. Look closely, as some replies are tangents, and never proved to be useful, but some suggestions did - in certain circumstances.
Look closely at replies by Jeff Bellune and Stanley Jones, as they offer the most info.
Good luck,
Hunt
PS - welcome to the forum. I would also post to the Encore Forum with as much info as possible, as Stanley never makes it over here and has worked on this error for some years.

Help! I am getting this error message in Premiere Pro 4

Help! I am getting this error message in Premiere Pro 4
[/belding/mediaCore/MediaLayer/AudioSupport/Make/Mac.../.../src/Mac/CoreAudioHost.ccp-1623
Does anyone know what this means?
I am using a very new IMac and running the latest apple os
Thank you

answer probably here
http://forums.adobe.com/message/1826019

Error message "Adobe premiere pro ne parvient à charger aucun pilote audio"

Error message at installation

Bonjour,
As Claudio points out, this forum is for discussing the Adobe Forums, themselves.
There is a very active Premiere Pro Forum, and I will Move your post to that forum. Your link, and any e-mail subscriptions will follow.
Good luck,
Hunt
[Moved to the Premiere Pro Forum]

Error message Adobe Premiere Pro CC has stopped working

I am working from a PC with Windows 7 and an i7 intel CPU. Premiere was working just fine and then one day it decided to throw errors at me when I try to place a clip on the timeline. The program will start up fine and import video clips, but won't allow me to add the clips to the timeline without presenting the error message. I have tried updating the drivers through Intel (some other form suggested this) but no luck. I also tried updating Premiere with hope that would fix it. I then uninstalled and reinstalled the program and still no change.
Anyone else had this problem?
Any answers would be great!

I have just had the same thing happen to me too. Everything has been working fine but today, Premiere has crashed/stopped working twice. I have managed to get back into it now, but it won't playback either the Source or Program Monitors, saying there is a 'Low-level exception in Adobe Player (Player)'.

Error in Premiere Pro CS3.

Whenever I had a problem and i posted it here, i always got helped by you guys, so first of all, i want to thank those who helped me out there, and wanted you to know that i really appreciate that help.
Here is probably my last issue with Premiere Pro CS3.
The problem:
From time to time, i get an error. A message saying: " sorry a serious error has occurred that requires adobe premiere pro to shut down"
It saves the current project, and when i start premiere over, it loads it from there. It usually happens when:
I ' activate ' an effect, example: I change the opacity to 0 ( typing it with the keyboard as a percentage ) and press enter. Right when i press enter, it pops up. ( it happens with any kind of effect, just from time to time, when i ' activate ' it)
When i minimize an audio file by dragging it to the left or the right, it happens when i release the right mouse button. These are just examples. The issue is that when i make a change, this error repeats.
I'd love to hear what the issue may be.
Appreciate any kind of help.

Can you give us the specs. of one of the typical Projects, and their Assets, where you see this happening?
Next, can you give us the specs. of your computer, in as much detail, as is possible?
Can you also list the programs/processes, that load at boot up? A screen-cap, or report from Process Explorer will tell us a lot.
Also, before beginning an editing session, you might want to look into this ARTICLE. If you have Win7, be sure to look down-thread for the link to Black Viper's Web site for tuning that OS.
This ARTICLE might be useful for telling you what is happening with your system and your programs, when you get the error and crash.
Good luck,
Hunt

Adobe premiere pro cs3 installation error

hi all
im downlaod adobe premiere pro cs3 trial version and setup it on my pc but at the first step i take this error message
i have sata hard disk 250 GB and i have more 200 GB free space and i give privillage for the setup folder but i have the same error plz help me why
note:
i have windows vista ultimate version 6.0 ( build 6000)

Create a new administrator account and login using it. Try the installation again. If it fails with the same error the download may be corrupt as Phil mentions.
Cheers
Eddie
Forum FAQ
Premiere Pro Wiki
- Over 250 frequently answered questions
- Over 100 free tutorials
- Maintained by editors like
you

Capture error premiere pro cs3

I've got an ongoing capture error in premiere pro cs3 (on Mac OSX).
At around the 9 minute mark of capturing, it stops and says 'Unknown recorder error'. The footage is still captured if I stop it straight away but lost if I leave it for a while. I'm using canon hv30 camera to capture dv footage (not hdv) and can't seem to solve it. Any suggestions?

Try a different capture utility. VideoHelp.com will list plenty of free alternatives. If they stumble as well, there ie likely something wrong with the tape at that spot.

Premiere Pro CS3 capture error after Aug 09 vista update

im using premiere pro cs3 on two PC's running vista. after the last vista update last week, i can no longer import HDV or DV from my HV30. both PC's detect the camera and ask to import into windows movie maker or other programs, but when i open premiere pro cs3 and click on capture, both PC's refuse to acknowledge that a camerat attached. is anyone else having this error? if so, have anyone found a soultion to this error?

Strange as it might sound, I'd also install the latest audio and video drivers. OS updates can kill these in a heartbeat. Test afterwards.
It sounds like Vista is seeing the camera OK, but I'd check just a bit deeper. Go to Control Panel>System>Hardware>Device Manager (or whatever Vista might call it?), and with your camera attached and turned on, navigate to it. Open up the window for that device and check every panel. Any warnings, or errors anywhere?
In PrPro, check all of the Capture Preferences. Anything amiss there? Anything changed, since the update?
As a test, create a current Restore Point (do not trust that Vista has done this for you - do it manually to be sure), and then choose a Restore Point from before the Update (I'd actually go back several, if possilbe). Use that and test again. Does PrPro now see the camera and does it Capture as before? If the earlier examinations do not point up something, and this test shows that PrPro CAN Capture, you have at least narrowed it down to the Vista update.
Good luck,
Hunt

Premiere Pro CS3 Encoding Error

I'm supporting an end user who has been using Premiere Pro CS3 for years to develop and encode videos on their computer.
Recently, they have been experiencing an issue with one particular project they're been attempting to encode. The project is nothing out of the ordinary, various video and audio files, a little bit of text. They're trying to encode the project down to an MPEG2 format for burning to a DVD.
The problem occurs about 20%-30% through the second pass of rendering. Premiere Pro will give an application error, stating that memory referenced cannot be "written". The program then shuts down and the attached Event Viewer log is written. I've done research, but haven't found any items relating to these errors.
The only major change that I know of on his computer was that Adobe After Effects was installed recently. I don't know the version level of After Effects installed.
Premiere is up-to-date. The user demonstrated the ability to encode other projects, both larger and smaller, without issue. All of the files been used as part of the problem project have been used in the past without issue. I'm having the user deconstruct their project to try to identify any layers or files that may be causing the problem. Rather than go through that tedious tasks, I'm hoping someone has an idea of what's going on.

If the project have captured video, this problem can be caused by defective capture. Frames of captured video can have compression problems even not having any apparent defect when they are showed. Since some compressions are inter frames, the compression can have defects during the capture. the funny is, the appearance of those frames can look like normal (since human eye cant see and scan those thousands/millions of pixels one-by-one and detect which one is defective).When you are about to encoding it, or "trancode" it, the change from a defective compressions to a mpg2 DVD for example make the program crash.
If thats the case, u can check in which frame Prem crashes, get the clip to AE and re-export it to a completely diferent format and compression, them replace the Premiere clip by the new one.
o/

Audio balance greatly different in Encore CS3 after encoding 5.1 master track in Premiere Pro CS3

Hello! I'm wondering if anyone can offer some advice for my DVD audio problem.
I have a Premiere Pro CS3 project with a 5.1 master track that appears to behave correctly judging by the meters when I play it in PP. It also sounds reasonable (in a mixed-down fashion, I guess) on my PC system's speakers (L,R,LFE), and all rebalancing and panning seems to work well. However, once I export the master track to Encore using PP's SurCode Dolby Digital codec, the resulting audio mix is totally off. Here's what I get: both front channels play mainly out of the right front and center speakers, and the rear channels play mainly out of the left front speaker. I've tried all different settings, but I can't seem to change this. Well I've read that Encore just sends the audio mix straight through (the DVD trancode status is "Don't transcode"), but when I build the DVD and play it on both of my 5.1 surround systems, the results are just as bad as what my desktop PC speakers were hinting at. [Actually all DVDs that Encore builds are UNSUPPORTED on one of my set-top DVD players and they're both Panasonic! So first, I first have to copy the DVD using Nero and then the copy is accepted by all. That seems to have no bearing on my audio dilemma but I thought I'd mention it. I would love to know what Nero is doing right that Encore is doing wrong!)
Anyway, here's some background: I began to notice this problem with the audio balancing whenever a .wav music source is imported into PP as a stereo source. [A side issue here - I don't seem to be able to explain - or control - how one .wav file gets imported as stereo while another is imported as 5.1!] Anyway, as one would expect, since my master track is 5.1, the stereo track is automatically set up with a rebalancing tray with the puck set in the middle. The meters show that the source is stereo and the sound has been rebalanced across the master track. If I drag the puck around, the master meters behave accordingly. Then I import my video (.avi video clip) and that sound is imported as a stereo track. For that track, I drag the puck to the rear. Again, the master meters respond correctly. So far so good. But when I export to Encore, the resulting audio mix so completely wrong it can't even be explained as a 5.1-to-stereo downmix situation. The sounds that were supposed to come out of the rear channels are in front left and center (and deafening), overpowering the music that is only coming out of front right. And the rear speakers are silent unless I turn on Pro-Logic on my amplifier, which just confuses the issue. I didn't bother to check LFE as things were bad enough.
Where I DO NOT have the problem is when the audio file is imported as a 5.1 source (although it is just a stereo CD track ripped using Sony CD Architect). In that case, there is no rebalancing tray and the track meter shows only the L and R channels active, as expected. Ditto for the master track. Now if I go ahead and send the music to a stereo submix track and let that rebalance to the master, I see all channels active. But that results in the problem above after exporting to Adobe Media Encoder using SurCode and then importing the audio into Encore. If I don't remix to 5.1, the audio on the DVD is OK. But I would like to have the music come out of all speakers when there isn't a video soundtrack as there are many still pictures in the presentation.
So the question is, if I can rebalance and pan channels in PP CS3, why are the results coming out all wrong in Encore using SurCode? And how can I hear my project on DVD the same way I mixed in PP?
Any help would be greatly appreciated!
Doug Herbst
Holmdel NJ

Problem solved everyone!!!
Rebecca of Adobe support helped me identify the root cause: project was originally set up as standard (2-channel) and although it had evolved to a 5.1 project over time, it could never grow up to be anything other than a standard audio project. After you set up the new project, the setting that controls your audio is buried in the project somewhere. Changing your project settings to set up new 5.1 audio tracks for new timelines does NOT make the project 5.1! The real audio identity attribute set at birth is not alterable OR EVEN VISIBLE (even as a grayed-out project setting) although PP will allow you to set up and mix 5.1 audio tracks at will. So you may think you're working on a 5.1 project now, but you're only fooling yourself and PP goes right along with it. Even the .ac3 files you create via export are 5.1! But dare to build your DVD in Encore and all of your timelines are transcoded back to 2.0 instantly. Resistance is futile.
A new feature in PP CS4 will allow you to view, and even CHANGE, your project's audio identify from standard to 5.1. How sweet!
Well, I've devised a way to dig out myself out of this deep hole in CS3 and it worked, but I can't promise that it will work for everyone. (This assumes you own the Dolby Digital 5.1 codec from Minnetonka.)
1. Create a new Premiere Pro project as 5.1 audio from the get-go.
2. Import your suspected 2.0 project into this new 5.1 project and click each sequence to flesh out the timeline.
3. Re-export all audio as elemental streams using Adobe Media Encoder. Make sure you export the audio component of each timeline as Dolby Digital 5.1 and exactly - and I mean EXACTLY - the same way. To deviate the audio settings for each timeline is to ask for trouble, so I recommend setting up an audio pre-set that you can just click when you need it.
4. Create a new Encore project and import all original video assets and your new replaced and, hopefully, 5.1 audio assets into it.
5. In Encore, create a separate timeline for each pair of assets (.m2v and .ac3 for example). DO NOT ATTEMPT TO PLACE MULTIPLE PAIRS OF ASSETS ON THE SAME TIMELINE! For some unexplained reason, the build process will transcode the audio back to 2.0, and if you continue pack new 5.1 audio assets on the same timeline, you will get an error message "an input contract violation has occurred" because you now have 2.0 and 5.1 assets on the same timeline, even though you really don't know that and didn't ask for that to happen anyway. (Thanks to Bill Hunt who mentioned his habit of keeping the asset pairs on separate timelines in another thread - that suggestion was absolutely essential to the solution here.)
6. In Encore, check to make sure that all of your original video sychs up correctly with the new, true 5.1 audio. Link the end actions of each timeline with the next timeline to play in the correct sequence. Check your project for orphan timelines and other errors. Then, before you start building menus and start getting fancy, build a DVD and make sure it plays as 5.1 on your system.
Tip #1: while you're re-exporting and replacing the audio files, don't have Encore running. I've seen it gracefully and automatically re-import the replaced file once the export is done, but I have also seen it choke with the terribly descriptive "Encore has encountered a problem" message upon discovered the asset is not available while it is being replaced. Encore then continues to mark the asset as offline.
Tip #2: when re-exporting and replacing files, always select audio and video separately. For some reason, Encore will allow you to replace an .ac3 file when you perform an elemental audio export, but when you try to combine video and audio and both files exist, Encore will prompt you to replace the video, but immediately abort with an error that it cannot replace the .ac3 file, thus forcing you to delete the .ac3 component manually before trying again.
Doug

Adobe Premiere Pro CS3 3.2.0 update

Thought I'd share a bit of information on the 3.2.0 update that will be coming out via AUM this morning. The update will come out first via AUM, then will be available on the updates page shortly after at http://www.adobe.com/downloads/updates/?ogn=EN_US-gntray_dl_updates.
The readme will also be hosted at http://www.adobe.com/support/documentation/en/premierepro/releasenotes.html.
Dave Helmly has posted about the update on his blog, as well: http://blogs.adobe.com/davtechtable/2008/04/xdcam_and_premiere_32.html#more
New in this release:
- This update adds compatibility with the Sony XDCAM range of cameras. This includes disc-based XDCAM and XDCAM HD cameras., and the newer SxS-based XDCAM EX cameras. Content from XDCAM cameras can be imported and edited natively without transcoding or conversion. This makes possible similar workflows to Panasonic P2, including the ability to edit content directly from XDCAM EX cameras.
- Note: Adobe Premiere Pro CS3 3.2.0 does not support IMX editing or XDCAM HD50 editing at this time. Export to XDCAM is also not possible.
- Adobe Premiere Pro now has presets for HDV 24p. Note: Adobe Premiere Pro does NOT support print to tape in 24p mode.
- Improved handling of MPEG streams (e.g.: HDV video), along with error detection. MPEG stream errors can occur during recording due to tape dropouts, record start/stop glitches, timecode breaks, etc. Bad frames caused by these MPEG stream errors are identified during import/indexing or playback. These frames will play back as full red frames to alert the user that there is a problem in the encoded video at that location. Adobe Premiere Pro will also log error messages to the Events panel, indicating where the error(s) were encountered in the stream. Users can open the Events panel, determine the location of the MPEG stream error, navigate to that location in the clip and take corrective action, such as trimming out the video glitch or covering up the red frames with duplicated good frames copied from before or after the glitch. Note: MPEG files will need to be re-indexed to take advantage of the improvements in Adobe
Premiere Pro CS3 3.2.0. For more information, please see Working with MPEG Files.
Notable fixes:
- Titles/Footage no longer show up as offline when reloading saved projects.
- Rendered preview files no longer missing when reloading saved projects.
- Certain filters and/or transitions are now applied correctly when reloading saved projects, until the timeline is forcibly refreshed.
- When exporting via the Adobe Media Encoder, there is no longer a long delay before the progress dialog shows and rendering resums (Mac OS 10.5.x only).
- 24p HDV clips shot on a Canon XH A1 no longer come in incorrectly as 30 fps clips.
- Creating an offline clip in the project window then attempting to link it to media on disk no longer results in the application crashing.
- QT PAL movies rendered out of Adobe After Effects® software are no longer incorrectly identified as requiring rendering in a Adobe Premiere Pro PAL project.
- DV Clips of certain specific durations are no longer incorrectly identified on the timeline as requiring rendering.
- For P2 DVCPro clips, the right-most pixel column no longer contains video garbage.
- Fixed a memory fragmentation problem that would occur with projects with many custom bin columns.
- Fixed a bug where exporting to a QuickTime movie (with QT 7.4) would crash the application.
- Selecting "display only exact name matches" when relinking clip no longer crashes on Leopard.
- Fixed an issue where 30p and 30f HDV clips would incorrectly be identified as requiring rendering in a 29.97 progressive project.

Harm,
I don't use HDV, so I'm not sure if this is the case or not, but in the top post, there is mention of having to re-index the MPEG files "to take advantage of the improvements in Adobe Premiere Pro CS3 3.2.0." While it seems this should be an automatic process, maybe wiping out the previously-created index files (I seem to remember them being in the Media Cache folder when importing MPG files from DVD rips and such) would let the project open. Or, maybe the old trick of importing an existing project into a new one? Just a couple thoughts...
To the other poster: surely, I don't jest. At least, not when it comes to anything in the video production industry and my operation in it. Long ago, I gave up expecting perfection from any particular piece of hardware or software, and just focused on being creative. That's why I got into this. I refuse to let any piece of equipment dictate what I can or can't do--I just find another way around. Funny how we managed to make it as a species and a civilization as long as we have, and now that computers are here to make our lives easier (*snort*), we're quick to raise our ire about everything that's wrong with them. That's why I will always marvel at things built long ago prior to the advent of all the technology we take for granted today.
Anyway, we're all entitled to our opinions, and I've taken this thread completely off-topic. My apologies, so...

Big problems exporting from Premiere Pro CS3

Hey all.
Would be massively grateful if anyone here could help me out. I'm in the process of trying to export a 23 and a half minute project from Premiere Pro CS3. I've tried exporting to different formats, (Quicktime, MPEG2, etc..) but keep arriving at the same conclusion. The process will freeze midway through, and I'm greeted by the following error messages:
"premiere pro debug event
premiere pro has encountered an error
[..\..\Src\PPixHandleUtilities.cpp-114]"
When I close that, another window pops up saying;
"export error
application failed to return a video frame.
cancelling the operation."
I'm not really sure where to go from here. Previously during the process of editing this project, I would occasionally get a message telling me that premiere pro was "running low on system memory". Fearing this to be the problem I was having while exporting, I attempted to export an extremely low quality version of the project, but arrived at the same conclusion. I also wondered if there was a corrupt frame or clip somewhere that was causing the issue, so I overlayed one whole transparent clip over the whole sequence and tried to export, but again, the same result.
I now have to put all my faith in you Adobe Wizards! Please ask me any questions that might help you to arrive at what may be causing the problem, I'll answer them the best I can
Many thanks!
Andy

>13.4GB free
FAR too small !!!
The program itself uses more than that for temporary working files
Also, unless you already have a 2nd hard drive or eSata external, you are below specification
Trying to use only ONE Hard Drive for Video Editing
You are a music conductor, with a baton that you use to point to various parts of the orchestra... this is like Windows pointing to various parts of the hard drive to do Windows housekeeping or to load program segments for various functions
Now, at the same time and with the same hand... while still using the baton to conduct the orchestra... pick up a bow and play a fiddle... this would be doing something with your video file at the same time as all the other work
You as a person cannot do both at the same time with the same hand
A computer is a LITTLE better, in that it can switch from one kind of task to another very quickly... but not quickly enough for EASY video editing
You need AT LEAST two hard drives (separate drives, never a partition http://forums.adobe.com/thread/650708 for more) with Windows (or Mac OS) and software on your boot drive, and video files on a 2nd drive so the boot drive is not slowed down by trying to do everything
Partition = Crash http://forums.adobe.com/thread/957286
I find that the three drives I use work very well for me, for editing AVCHD video... some people use a 4th drive, so video INPUT files are on drive three and all OUTPUT files are on drive four... I only bought a mid-tower case instead of a full tower case (my bad... but had to fit in the space available on my office desk!) so I use the three drives that will fit
Depending on your exact hardware (motherboard brand & model AND USB2 enclosure brand & model AND external hard drive brand & model) AND the type of video file, you may... or may NOT... be able to use an external USB2 hard drive for SD (Standard Definition) video editing
Steve Grisetti in the Premiere Elements forum http://forums.adobe.com/thread/856208 and Jim Simon in the Premiere Pro forum http://forums.adobe.com/thread/856433 use USB externals for editing
A USB3 hard drive connected to a motherboard with USB3 is supposed to be fast enough for video editing (I don't have such, so don't know) but eSata DOES have a fast enough data transfer for video editing... I have not used the eSata Dock below... for reference only, YMMV and all the usual disclaimers
http://www.amazon.com/Thermaltake-BlacX-eSATA-Docking-Station/dp/B001A4HAFS/ref=cm_cmu_pg_ t

Can't install Premiere Pro CS3 in vista x64!

Hi
I'm trying to install Adobe Premiere Pro CS3 trial version on my system Vista Ultimate X64, every time I run setup.exe that extracted on my desktop it load for few seconds, loading and then it close with no reason.
There's no error code or any message after it close. and I'm also pretty sure that my system met recommended requirements. I'll upload dxdiag anyway.
I just were on my way to buy this product but I said ill try it as long as there a trial version, thanks to "trial versions" idea that adobe presents to us.
Anyway, what is my problem, what's wrong?

I have to agree with Aanarav but I haven't suffered the same USB audio problem. My Rode mic works fine.
I've loaded CS3 Production Premium on Vista x64 and suffered no ill effects at all. My projects are longform (documentary) and the greatest benefit so far is the drastically reduced rendering times (mind you that's a quad core with 8Gb of memory.) Apart from the Adobe suite I can run GPU based programs like ProDad's Vitascene and many others concurrently without affecting processing speed all that much. For the first time I can actually run Prem Pro and Avid liquid at the same time (not too well mind you) and that's a feat.
As to all the "questions" Vista may ask the solution is simple - turn them off.
There's a lot of rumours about "lack" of drivers but this is changing daily and I don't have one piece of hardware/software from XP that can't run on Vista x64 including my 14 year old HP Laserjet 6p printer. The only hardware I needed to replace was my Lide30 Canon scanner (2 years old).
Oh! the nVidia x64 bit video drivers are a treat.
Vista x64 - faster than a speeding bullet (if you have a half decent machine)

PSD lassen sich in Adobe Premiere Pro CS3 nicht mehr importieren

Wir haben seit Montag das Problem, dass sich in Adobe Premiere Pro CS3 keine PSD mehr importieren lassen. Als Fehlermeldung erscheint, dass es ein nicht unterstütztes Format sei. Am Betriebssystem liegt es wohl nicht, da das Problem auf Rechner sowohl mit WinXP als auch mit Win7 besteht. Bis Freitag lief alles wunderbar, nur am Mo. ging es nicht mehr. Weiß jemand, woran das liegen könnte?

[Entschuldigen Sie alle. Ich habe dieses Post geschrieben bevor ich bemerkte dass es gibt hier ein Deutsches Forum. Ich habe es jetzt in einem Englischen Forum auch geschrieben.]
Not a reply, but a "me too". Like Bjoern I use PPro CS3. Mine is on WinXP with all updates. I import PSD files as keying masks. I've never had a problem until this evening (27 Aug 2014). I tried to import a mask I've used many times before. And it has always worked before. Tonight PPro refused to recognize .psd as a supported file type, so it didn't show in the import folder file list. When I told PPro to show "all files *.*", it showed the file. When I selected it, PPro even showed the "import file" window, then displayed the "File Import Failure" window with Error Message: File format not supported. See the picture below.
This is a file I've imported into many previous projects with no problem whatever. In fact, I started with a project file from last year which showed the mask file in the project assets but offline! Even though the file had not been moved.
If PPro CS3 is as obsolete as Adobe claims it is, then who's been messing with it? And how can we get it "unmessed"?

Error message in Premiere Pro CS3

Similar Messages

Maybe you are looking for