PGC error

I have been using the Master Collection CS4 without flaws for almost a year now, however, yesterday I suddenly received an unknown e
rror. PGC error. I take an HDV timeline (1080i) from PPro CS4 and export it via AME under the same settings I always have. I do n
ot make any menus or titles in Encore, I simply import the timeline, change the title and end actions to stop (like I always have) a
nd then burn. I then get the PGC error message about the aspect ratio not being for DVD. This is confusing since I've done this fo
r almost a year, but suddenly yesterday I started getting this message.
Operating System: Mac OS X (v10.6)

You might want to start by doing a Search of this forum for "PGC+error." IIRC, there are three different threads, one very, very long. This error-group (I say that, because there seem to be several circumstances that can cause them), while not common, seems to be tied to first Assets and Project and then possibly to system. SlideShows seem to play a role for some users.
My hope would be that some of the replies from people, such as Jeff Bellune and Stanley Jones, will point you to an immediate solution. You can even filter your Search on People, and use "Jeff Bellune," as he was very active in all of those threads.
Because of the vast number of variables that seemed to come into play, you can probably rule out some suggestions pretty quickly. Be sure to read down each thread, as some of the solutions did not come until much later on.
At the very least, you will see some of the things that appear to be contributors, and can either rule those out, or comment on how they figure into your issue.
Good luck, and please report back,
Hunt

Similar Messages

PGC error when burning in Encore CS3 ... help

I've looked and can not find any one else with exactly this problem. I recently upgraded to Adobe Creative Suite 3 and can not get a DVD to burn. The project checks fine, the files transcode without difficulty but during the burning process, I very quickly get a PGC "file name" error.
I have a Sony Pentium 4, 2 GHz, with 1.21 G of RAM, and plenty (30 G) free on my hard drive. I have a 16X Memorex DVD burner which is probably 6 months old, but up until now has worked great. I've tried several different brands of DVD-R media and same problem.
I'd describe myself as an advanced amateur at video making. I taught myself on Nova's Video Explosion and burned 100's of dvd's on the Sonic's My DVD program over the past 5 years. Actually that system worked well, but I'd outgrown it. I downloaded Encore 2.0 free 30 day trial and loved it. I'd import (uncompressed) avi files that I'd created in other programs (mostly Video Explosion, but also Movie Shaker, and Windows Movie Maker), create menus in PS CS2 and my DVD's burned quickly and without errors at all. When my 30 days expired, I found they no longer offered 2.0 and I decided to spend the big bucks at got Creative Suite 3 really solely for Encore.
I've now spent 3 days trying all kinds of different things, many different files from different sources and I always get the same error message of "PGC "file name" has an error at "time" internal software error %0, line "file name:, time 00:"time", ref= BPGC.
I did read some messages on here about uncompressed avi vs. compressed avi. I did find that I was using uncompressed avi, but when I used Adobe premiere and rendered as MPEG 2 ( I believe), I got the same error. The only success (?) I had was when I rendered a file as a .MOV. It did burn without the dreaded error message, but the quality was extremely poor and jumpy.
Any ideas? I've got a project due in a couple of days and at present I've got files that I can't get to DVD...

So, finally I've found the source of the problem and a workaround!
First the source:
when Encore has to transcode a video it must corrupt the file, because it's the transcoded file that causes the problem, I tried this by importing a transcoded file into Encore 1.5 there it came with the same error.
Now the workaround, ok maybe it isn't quite a workaround but it's a way to go:
What I did was: I built my project new in Encore 1.5, because Encore 2.0 has a problem importing the videos by me, but if you would just import the videos in 1.5 and let 1.5 transcode them so that all of them would fit on a DVD you should be able to import the transcoded files in CS3 and it should work, no guarantee.
Other possibility: try opening your project in encore 2.0 and re import your videos there and let 2.0 do all of the transcoding, that might work too!
But for certain: don't let encore CS3 do all the transcoding!
I'm working with PAL files I don't know if it will be the same by NTSC, but it's worth a try!
If anybody feels like reproducing the bug, here is the way to do it:
Make a project in Encore CS3 and import Videos encoded by premiere as MPG2-DVD (I think: .m2v .wav) and set the transcoding options to automatic, encore should have to transcode the files. Then let encore make the DVD, at some point you should get that nice PGC error!

The Dreaded PGC error in Encore CS4

Hi Group,
Have used Encore for a couple of years now and encountered the PGC errors in previous versions all of which I eventually surmounted. Usually they were audio based and changing the saving settings in WAV files usually solved it.
However now in CS4 it has returned with a vengance, no amount of audio changes have solved it, even tried changing to different formats (wav to aif etc) to no avail. Tried changing the transcoding settings, no help.
What I'm doing is as follows: Using a PC, windows xp pro 64bit, 8gb ram. creating photofiles in Photoshop, into After Effects, making slideshow outputting as AVI, opening as asset in Encore and moving into a timeline, transcode and build to a disc and burn. NO PROBLEM there.
Now when I start adding audio and follow through as above, the assests transode and it starts to build I get:-
"PGC <timeline name> has an error at 48.7200s. The aspect ratio of this file is not supported by DVD. PGCinfo: name=<timeline name>, ref=epgc, time=48.7200s"
I have read some of the similar problems in the forum and have tried many of the suggestion without result.
Surely there must be some answer somewhere.
Please if you know a fix please let me know urgently.
Thanks in advance to all those that take the time to reply.
David

A couple things that may (or may not) help
Encore Roxio component problem http://forums.adobe.com/thread/400484?tstart=0
More on Encore and Roxio http://forums.adobe.com/thread/528582?tstart=0 or direct to
http://kb.roxio.com/search.aspx?URL=/content/kb/General%20Information/000070GN&PARAMS
Long File Names Cause Crashing http://forums.adobe.com/thread/588273

PGC Error, AMD system, and Possible Workaround

I too am experiencing the PGC error in Encore CS3. I have found what seems to be a work-around (although it isn't convenient at all). I'm thinking that it has to do with either:
1. Codec Issues in the transcoding (it appears that Encore and Premiere are using the same codec, too). Perhaps I have some weird codecs installed.
2. Some incompatibility between the AMD processor or NVIDIA chipset and the transcoding codecs.
Here's the error I was getting when I was trying to build a DVD image:
PGC "Main Menu" has error at 00;00;20;21.internal software error: %0, line Main Menu - PGC Info: name = Main Menu, ref=gpgc, time = 00:00:20:21
So, I removed the motion background from the Main Menu, then got the same PGC error referencing one of my timelines. That timeline had been exported from Premiere as an MPEG2 file (separate .m2v and .wav files were created).
I was doing all this on an AMD Athlon 64 3000+ system with NVIDIA chipset and graphics card. So I loaded the project (over a firewire network) on my Intel Core Duo / Intel Graphics based Dell laptop. Once I got everything relinked properly, I tried to Build the DVD image again, but got the same error. It was still using the same transcoded files.
Next, still on the laptop, I reverted all the transcoded files back to their original, and imported AVI files instead of transcoded files into my timelines. I then saved the project and closed Encore, and manually deleted any files that had been generated in the transcodes and cache folders. Then I re-opened the project and re-rendered my one motion menu. I tried building the DVD image again, and after a few hours transcoding it actually worked!
I've now used a similar procedure twice and it has worked both times. I haven't tried using "Transcode Now" instead of having it transcode before building, but I imagine it would work too.
Also, on the AMD system I was having several problems with Encore freezing up during transcoding. The Intel-based laptop seems to run it more stable. So my plan for now is to use Encore on my laptop instead. Besides, the laptop is faster anyway!

I think this install all packages as "explicitly installed" which you may not want (remove a package and it's dependecies remain, because they are not installed as deps anymore).
you may want to break it up into
#first dependencies:
for p in `pacman -Qd | cut -f1 -d" "`; do pacman --noconfirm --asdeps -S$p; echo "y
y" | pacman -Scc; done
#then explicitly installed packages:
for p in `pacman -Qe | cut -f1 -d" "`; do pacman --noconfirm --asexplicit -S$p; echo "y
y" | pacman -Scc; done

PGC error in EN CS6

On a new Win8 system with CS6 freshly installed and updated with the latest updates, I consistently get a PGC error at the same location everytime I try to build a DVD.
The Encore project is very simple: 1 timeline (the video) and 1 asset (the audio). No subtitles.
The timeline was encoded in PR and consists of a single nested seuence, HDV material, scaled down to 54% to fit the SD sequence settings, On track 2 there are some SD MPEG2 scenes and on track 3 are some titles.
This was encoded to MPEG2-DVD, PAL Widescreen High Quality, CBR 8 Mbps with MRQ on and audio to Dolby stereo at 192 Kbps.
The video file was imported as timeline and the audio as asset. Of course no transcoding required.
So far, so good. Previewing gives no problems. But on the build of a DVD, I get a PGC error everytime and the build stops.
I located the problem as the start of the first title on track 3 in the PR project. I removed the title and created a new (identical) title and exported again. Still the same problem. I moved the title a few frames, exported again and yes, the PGC error now shows the new timecode of this title.
Haven't tried yet to completely remove the title in the PR project, but this is weird that a simple title can cause this problem.
Any workarounds?

Disabling the title track in PR and re-exporting does not help. Here are the export settings:

PGC error caused by subtitles

I went to build a project and got the "PGC has an error at" error. After re-encoding all the assets on the timeline and re-importing into Encore it built fine UNTIL i added the subtitles back into the mix. I went to the time it said it had an error and just deleted the subtitle there and tried to output again, same error but different timecode. If I delete the subtitle that occurs at each error it progresses BUT this isn't really a solution. I could deal with a couple deletions, not this many.
Is there any actual fix to this issue? Or suggestions (rebuild from scratch?)? Very frustrating.
The timeline has 3 audio tracks (DD 2.0 192k), not sure if that is a contributing factor.
I'm using Encore 5.1 (CS5.5).
thanks
Ryan

For what it's worth, here's what solved the problem for me.
I have a DVD project, one timeline with one video track and one audio track, both rendered to .m2v and .ac3 in Compressor on Mac.
I'm working on PC on Encore CS 5.1.
A couple of months after releasing my DVD I had to come back and redo another edition with minor changes, so I just replace the assets on my timeline expecting it will work. Then I get the dreaded PGC error....
After messing up with any possible part of the project I could think of and eventually redoing a whole timeline, I realize the problem is coming from my subtitles (I have 10 subtitle tracks), and finally find out that the problem is coming from one of the subtitle tracks in particular.
And more specifically from these lines :
00:52:50:01 00:52:52:07 No fue lo primero que elegimos.
Cuando nos decidimos por el mulch,
00:52:52:07 00:52:54:15 hay muchas otras maneras
de crear una capa de mulch
The first line here ends at the same time at the second line starts. I changed the start of the second line to 00:52:52:08 and it compiled fine.
Now, keep in mind that this is a project that I had successfully compiled in the past, just reopened after a couple of months without changing anything to it, and it didn't work anymore.
I can't imagine anyone from Adobe is paying much attention to these threads, but it would be nice if errors were a tad more descriptive... I spent a week working on this one. How about "subtitles overlap at hh:mm:ss on track n"?
Anyway, I hope this helps someone.

Encore CS6 - PGC error

i am using Encore CS6
I have rebuild the timelines as well as the entire project which no results.
I tried removing the last video clip in the timeline, trimmed the last few seconds off at the end. Th error is usually about 1-2 seconds from the end of the last clip on the timeline.
PGC "<timeline name>" has an error at 00;26;51;28. internal software error: %0, line <timeline name> - PGC Info: name = <timeline name>, ref Bpgc, time 00:26:51:28
Thank You

hello Stan
thanks for the reply.
i Have tried every idea I could find online.
rebuilding, reexporting, deleting xmpses, build dvd folder and image, even just for luck tried from another system but still cannot seem to fix the issue.
it is strange that after rebuilding the project that i still get the same problem.
are you working with Adobe because I cannot get access to Adobe Encore support directly. Just get the forums.
thanks for the help

PGC Error - Again

I have Googled away, trying to get a solution, but with poor results.
I am using CS6 Production Premium. I exported a Premiere timeline (footage is 1440x1080) using the PAL Widescreen Mpeg-2-DVD preset. Over in Encore, I created a single menu project. "Check project" shows all is OK but, then, when I hit the "Build" option to burn a DVD, I get -
PGC "File" has an error at 00:16:32:02, internal software error, %0, line "file" - PGC info: name = "File", ref = Fpgc, time = 00:16:32:02
The stated "time" location is in the middle of a clip. There are no gaps in the video in the Premiere timeline and no audio tracks extend beyond the video, which totals 17mins.
I then took the original sequence and nested it into a new PAL WS sequence and exported from there, but I still get the same error message, albeit the timecode has shifted from the one generated in the original error message.
I have never had this problem with Encore before,
Please HELP me out of this one...

Hi John
We learn something new every day. I didn't know about the Roxio connection and your explanation helps my understanding of the issues...but then, I look at this from the point of view that, if I buy something from any supplier, my "contract" is with them - irrespective of where they got it from? My car air bag, for example, is almost certainly not manufactured by Ford, but if it goes wrong, then they are responsible. I assume Ford engage in rigorous testing to ensure quality and they are then accountable to me, as their customer. If their airbag supplier causes them a ton of customer complaints, I think Ford would "sort" them out, one way or another?
Maybe (er, make that, definitely) Adobe needs to get a quality audit imposed on Roxio? For me the DVD authoring and burn should really be the easy bit of the process. Yet Encore conspires to drive me nuts, after I've done all the "hard" stuff elsewhere. Having spent a lot of time making sure the production looks 'the canines cajones', trying 'what ifs', with the last bit, is a mega pain.
Sorry if I appear to be having a dig here, it is assuredly not aimed at you John, but at Adobe...

Recurring problem with encore CS3 for windows - pgc error

Hi,
I've been looking through the solutions to pcg errors and not finding what i need.
A couple of years ago I was getting these messages and looked them up here, found a workaround that I've been using since then. All of the sudden the problem is back and none of the workarounds work.
My workflow is as follows:
Create a timeline in Premiere and export as m2v (for dvd) import into encore add menu and burn. This has worked many many times. When it first started happening i employed the workaround of moving the m2v and wav files to a different folder (without the other files). Like I said this has worked for a couple of years. Now I keep getting error message referencing the last few frames of the timeline.
When I bring the m2v file into encore there is an extra approx. 9 minutes of black at the end of the timeline (there should only be 30 seconds of black). When I look at the file in a media player the extra black isn't there.
Does anybody know what to do here? Currently I am reexporting all timelines from premiere as .avi files and will try transcoding them in Encore (this worked the other day), but I have 6 hours worth of footage to retranscode now - so much wasted time.
Please help.
Thanks,
Michelle

Ask your question in the Encore forum.
Mylenium

Internal Software error PGC for encore CS3 !!! solved !!!

Almost everybody here knows the next error:
PGC "timeline name" has an error at xx:xx:xx:xy internal software error : %0, line timeline name - PGCINFO: name= timeline name, ref=BPGC, time=xx:xx:xx:xy
Where the y in time stands for the length of the timeline minus 2 frames. The BPGC error can also be FPGC or DPGC dependant on how many menu's there are in the project.
It kept me awake for weeks and after reading this forum several times and comparing encore CS3 with encore 2.0 filenames I found the solution.
This Error is a bug in encore witch has nothing to do with blank filename spots and sonic coding or codecs or planning your workflow with a pencil but pure with the combination Adobe Premiere Pro CS3 and Encore CS3.
This is what generates the problem:
In Adobe Premiere Pro CS3 you build project with video, sound and chapters. Then you export the project via the Media Encoder not Multplexed.
Premiere CS3 then creates the following files:
filename.M2V (video file mpg)
filename.AC3 (audio file ac3)
filename.M2V.XMPSES (an adobe file with preview info and chapter pointers)
filname.XMP (??)
It is the .M2V.XMPSES file witch creates the PGC error. If you use the MULTIPLEX DVD option then ADOBE will not create the .M2V.XMPSES file so there will not be an error. This trick mentioned by ADOBE and many others is just to go around the bug instead of solving it. Also with multiplex you have just one sound track. I use two sound tracks like 5.1 and a 2.0 track witch you can choose in a menu.
Some people say it is the blank spots. Also not true. They have probably just erased the blank spots of the M2V file and forgot the .M2V.XMPSES file.
When you just delete the .M2V.XMPSES file and then open the M2V and AC3 file in Encore as a new asset, make a timeline and menu's and the project will built and burn. Only if you delete this .M2V.XMPSES file Encore takes a longer time to import the M2V file and will be without the chapter points.
Almost everything else will work like menu with sound and even a movie background (use M2V files). Only the motion buttons in a menu still wont work unless you use a black background !?!. Haven't figured this out yet. Only solution for this is use Encore 2.0. In this older version also the motion buttons will work without error's (everything else also so why buy CS3??)
Here is what you must do create a DVD without errors:
-Create a project in Premiere Pro, even with chapters.
-Write down all chapter points (minutes:seconds:frames)
-Create two new unique maps in explorer for example D:DVD1 and D:DVD2
-Export in Premiere with Media Encoder without the Multiplex:DVD but with NON to the D:DVD1 map
-Copy from D:DVD1 only the M2V and AC3 files to D:DVD2
-Start up Encore DVD CS3 or 2.0
-Create a new unique project in Encore for example "DVD" and save this in the map D:DVD2\
-Then use Save-as (under file) and pinpoint to D:DVD2\dvd to be sure that all Encore's files are placed in this folder.
-Select M2V file and make new timeline.
-Make chapter points (you wrote down the points, did you?)
-Create menu's, even with sound (AC3) and movie background (M2V)
-Then render project if you have used a video for menu background
-Finally Built and burnnnnnn!!
-If you like to use motion buttons in a menu then use Encore 2.0
I have double checked my work flow and it really works. I have built a project and burned with success Then I deleted the timeline and the M2V file. Copied the .M2V.XMPSES file in the used folder. Re loaded the M2V file in encore (this time much faster! and with chapter points). Tried to built and burn and back was the error. Also this happened in in Encore 2.0!!
Hope that this will solve the PGC error once and for all !!!
Marcel W
system:
acer aspire AMD 64 3800+
2 GB
250 GB hard drive for system
750 GB hard drive for movie
software Adobe Encore 3.0.1.008, Premiere PRO 3.2.0, Photoshop CS3 10.0, All upgraded
NERO 7
No Internet

> Where the y in time stands for the length of the timeline minus 2 frames.
This can actually vary, and so far at least, I don't think we've seen a pattern as to type of pgc error based on how many frames from the end it reports.
> The BPGC error can also be FPGC or DPGC dependant on how many menu's there are in the project.
Number of menus is not relevant; the iteration of the first letter is more related to subsequent occurrences of the error. In my current tests it did not always update; they may have been too similar.
> This is what generates the problem...
Well, the problem does not occur every time you do what you describe, any more than it occurs every time spaces are left in the file names. What you have is, as some other suggestions, a workaround. Thats not bad, and I wonder if you are onto something as to what is contributing to the problem.
So, on to the interesting part whether the xmpses file, or at least what Encore is doing with it, is contributing something. I took an old test project that throws the PGC error and did some experiments.
Background. I am a user who does get the pgc errors regularly, but not always. Creative Suite Production Premium, with PPro CS3 3.2.0 (374) and Encore 3.0.1.008. Pentium 4 2.8GHz 2G RAM, XP SP3, Multiple drives, Nvidia GEforce4 MX440 i.e. an older system. I have lots of stuff loaded and running, including virus protection and firewall, so there are any number of potential conflicts. But I get no crashes, and only one problem other than the pgc. (PPro and Encore monitor windows do this diagonal thing I suspect the display card, but the drivers are up to date. Maxing and then back to fit fixes it.)
If you want to attempt to replicate my studies, here is a link to my problem clip and the first Encore project I describe.
http://www.videoandcomputer.com/test/pgc_test.htm
This project involves a very short AVI export from PPro CS3 - just over 8 seconds - called pgcbad_clip1.avi. Just to answer any question, the source is dv camera capture, and the source and avi export I use are dv avi type 2. There were no effects added on the timeline.
Test 1: Create a project in Encore CS3. Use the sunset menu and delete all the buttons except "play all." Import the avi as a timeline. Set the timeline end action as "return to last menu" and set the button link to the timeline. Auto transcode. (Project settings are 8mbps max and a3c.) Check project shows okay; there is never a problem with that. Build to a DVD folder in a new folder. This project throws the pgc error.
Test 2: Now create a new Encore project in a new folder. Use the same process, except import as timeline the m2v and a3c files from the first run. (I.e. if the clip is pgcbad_clip1.avi, in the test1 project folders, there is a folder called pgcbad_clip1.avi that has 6 files.) Note that in the folder they are imported from is an xmpses file from the first project's encore transcode. The build again fails with the pgc error - same frame, etc, but I really think the frame number doesn't matter.
Test 3: Now create another new Encore project in a new folder. Use same process, but before importing the m2v and a3c as timeline, delete the xmpses file. Drumroll...... Build succeeds!
Go figure.
This is not the repeatable bug option weve been looking for, but based on a clip that always fails, it does demonstrate the odd event of deleting the xmpses file as a workaround. I wonder if that will give adobe something to work with.
Can anyone else get my clip to work/not work in a straight project?
Test 4: Just to answer the question since the avi file fails here, will the elemental option succeed? I exported elemental m2v and wav from PPro, used the same project process, and transcoded the wav. That build also works! I have seen this work both ways. I have had projects where the elemental failed, and an avi export worked. I do believe the elemental options work more consistently. But my project that I completed yesterday used all avi exports, animated buttons in the submenu, - no pgc error.

PGC Internal Software Error During DVD Build

After weeks of editing my 77-minute feature and days of DVD authoring effort, it's more than a bummer to see this appear during the final DVD build process:
PGC "Analysis" has an error at 47:21:29 internal software error %0 line . . . PGC Info; name=Analysis, ref FPGE time 47:21:29.
I verified the project before the build and there were no errors/warnings. I tried several times and get the same error at the same spot; I tried creating an image and the same error takes place at the same spot. I previewed the entire thing in Encore and everything plays/sounds great. All the footage/sound was imported as two large, uncompressed DVI files exported from PPro 2.0. The video is 16:9, 24p. Most of the sound came straight from the source video feed, except for two WAV files containing theme music.
What can I do to get this production finished-- of course, I am behind schedule...

So, finally I've found the source of the problem and a workaround!
First the source:
when Encore has to transcode a video it must corrupt the file, because it's the transcoded file that causes the problem, I tried this by importing a transcoded file into Encore 1.5 there it came with the same error.
Now the workaround, ok maybe it isn't quite a workaround but it's a way to go:
What I did was: I built my project new in Encore 1.5, because Encore 2.0 has a problem importing the videos by me, but if you would just import the videos in 1.5 and let 1.5 transcode them so that all of them would fit on a DVD you should be able to import the transcoded files in CS3 and it should work, no guarantee.
Other possibility: try opening your project in encore 2.0 and re import your videos there and let 2.0 do all of the transcoding, that might work too!
But for certain: don't let encore CS3 do all the transcoding!
I'm working with PAL files I don't know if it will be the same by NTSC, but it's worth a try!
If anybody feels like reproducing the bug, here is the way to do it:
Make a project in Encore CS3 and import Videos encoded by premiere as MPG2-DVD (I think: .m2v .wav) and set the transcoding options to automatic, encore should have to transcode the files. Then let encore make the DVD, at some point you should get that nice PGC error!

PGC has an error--data rate of this file is too high for DVD

Getting one of those seemingly elusive PGC errors, though mine seems to be different from many of the ones listed here. Mine is telling me that the data rate of my file is too high for DVD. Only problem is, the file it's telling me has a datarate that is too high, is a slideshow which Encore has built using imported jpg files. I got the message, tried going into the slideshow and deleting the photo at the particular spot in the timeline where it said it had the problem, now getting the same message again with a different timecode spot in the same slideshow. The pictures are fairly big, but I assumed that Encore would automatically resize them to fit an NTSC DVD timeline. Do I need to open all the pictures in Photoshop and scale them down to 720x480 before I begin with the slideshows?

With those efforts, regarding the RAM, it would *seem* that physical memory was not the problem.
I'd look to how Windows is managing both the RAM addresses and also its Virtual Memory. To the former, I've seen programs/Processes that lock certain memory addresses upon launch (may be in startup), and do not report this to Windows accurately. Along those lines, you might want to use Task Manager to see what Processes are running from startup on your machine. I'll bet that you've got some that are not necessary, even if IT is doing a good job with the system setup. One can use MSCONFIG to do a trial of the system, without some of these.
I also use a little program, EndItAll2 for eliminating all non-necessary programs and Processes, when doing editing. It's freeware, has a tiny footprint and usually does a perfect job of surveying your running programs and Processes, to shut them down. You can also modify its list, incase it wants to shut down something that IS necessary. I always Exit from my AV, spyware, popup-blocker, etc., as these progams will lie to EndItAll2 and say that they ARE necessary, as part of their job. Just close 'em out in the Tasktray, then run EndItAll2. Obviously, you'll need to do this with the approval of IT, but NLE machines need all available resources.
Now, to the Virtual Memory. It is possible that Windows is not doing a good job of managing a dynamic Page File. Usually, it does, but many find there is greater stability with a fixed size at about 1.5 to 2.5x the physical RAM. I use the upper end with great results. A static Page File also makes defragmenting the HDD a bit easier too. I also have my Page File split over two physical HDD's. Some find locating to, say D:\ works best. For whatever reason, my XP-Pro SP3 demanded that I have it on C:\, or split between C:\ and D:\. Same OS on my 3 HDD laptop was cool having it on D:\ only. Go figure.
These are just some thoughts.
Glad that you got part of it solved and good luck with the next part. Since this seems to affect both PrPro and En, sounds system related.
Hunt
PS some IT techs love to add all sorts of monitors to the computers, especially if networkded. These are not usually bad, but are usually out of the mainstream, in that most users will never have most of these. You might want to ask about any monitors. Also, are you the only person with an NLE computer under the IT department? In major business offices, this often happens. Most IT folk do not have much, if any, experience with graphics, or NLE workstations. They spend their days servicing database, word processing and spreadsheet boxes.

Adobe Premiere Elements 7 With Worthless Error Messages.

I have been a programmer since 1984, and if I saw a programmer in my team wrote these worthless error messages, I would go into my office and kill myself.
I Googled them, and I found them discussed; but the responses were of no use to me, mostly.
1. The error message I got that brought me to the edge of a cliff is: "Sorry, a serious error has occurred that require Adobe Premiere Elements to shutdown. We will attempt to save your current project."
Then it crashed.
When I was taking Operating Systems in my computer science class, a crash means you will get no more than 60 (out of 100). At IBM, a crash is always a SEVerity 1 issue. There is no way around it. Crash means the program is worthless.
I Googled it, and Adobe suggested it could be some drivers using virtual audio. I uninstalled everything I could find, and this problem is not going away. I looked at the sound device configuration, and it's using physical audio, not virtual audio.
I uninstalled Premiere Elements 7 five times and reinstalled them. They still failed. Finally, I reinstalled it at a different location, and it managed to "Found default catalog. Trying to open the default catalog." Then crashed.
If I wanted to use the default catalog, I would have said so. If I knew where they are, I would have set them on fire.
Anyway, I have a project due this afternoon, and I am stuck with these worthless Adobe Premiere Elements 7 error messages. No wonder Steve Jobs banned Adobe Flash. They are pretty worthless.
Sorry I am so upset, because none of you need to read my frustration; but I am up to my neck with Adobe. Once I get my project done, and I am switching to SONY Vegas.
But, for now, would someone tell me how to get rid of these problems so I can get the video edited? Thank you.

I noticed these errors were reported years ago, and Adobe has done NOTHING to improve it.
Go back to my little list of how problems, crashes and errors sort out. That was how it was way back with Premiere programs, and how it still sorts out.
Even the patch for PrE 8 was mainly to get it functioning with nVidia and ATI graphics cards. Yes, those "fixes" probably straddle the line between Bugs and system, with a nod towards Bugs. I know that Adobe takes their Bugs very seriously, and work overtime trying to find fixes for those, that do exist. Though it took a bit of time, as they gathered info, still Adobe had a patch, and that is rare for PrElements, due to the normal lifespan of that program.
I provide some of the same answers today, that I did years ago, to fix the problems. In nearly every case, things sort out per that list. As "system" is both #1 and is also by far the largest segment of causes, that is where I begin looking. With PC's, there are myriad configurations, and most are not suited for video editing. Too many load up their e-machine and expect to edit HD material. Obviously, that is not the case here, but there could still be equipment incompatibilities, or just some tweaking needed. I see similar in the PrPro forum, as the Mac-users put the program on their MacBook Pros, with one tiny HDD, and a very weak CPU, and things go horribly wrong. If PrE was ported for the Mac, we'd have the same issues here. Usually, my first question will be about the I/O sub-system, i.e. the HDD's, their size, speed, free space, controller type and how they are allocated. Video editing is highly I/O intensive, and most computers are not even close to being able to efficiently handle it. I recommend a minimum of 3x SATA, physical HDD's, and suggest that they be setup to spread the I/O workload over all three. Some manage with a 2x I/O, but that is below MY minimum, and is the real minimum from Adobe. A single HDD I/O is just going to cause bottlenecks, and there is no way around that.
Once, it was more the domain of the PC, that one had system issues, as Mac's were so limited and controlled. Now, as they have gained the ability to expand beyond the absolute control of Apple, those users are finding out that systems DO matter.
Notice #2 - Assets. Not all AV material is meant to be edited. Some, like AVCHD (a consumer format) will require a pro-level computer, just to get smooth playback! The second most common issue is trying to edit material that has something like the Xvid, or DivX CODEC.
Number 3 - Project, is very important too. One must match their Project Preset to their source footage. If not, then there will be problems. The failure to do this match is one of the biggest causes of issues, though usually not crashes, or hangs.
Number 4 - OE, is when a user decides to push a button, and expects something else to happen, and often because that's how it worked in another program. Many argue with me that #2 and #3 are OE too, but I am much more lenient, than they are.
Then, there ARE the Bugs. PrPro CS4 had a bunch. CS4.1 fixed a few, but broke some other things. It was not until CS4.2, that things got corrected, mostly, with that version. Then, CS5 hit, and seems quite good, but has a few Bugs too. Some were left over from CS4. A new update for CS5 is coming, and soon. Will it also fix those lingering Bugs? Only time will tell. Will it be a perfect program? Doubtful, but I'll bet that it'll be a "better" program.
Think back to when you started programming. You were writing apps. for the majority of the install-base. However, what happened if the user had Extended Memory? What happened if they had Expanded Memory? What happened if they had both, and a software manager to handle those? Most still had 640KB. By that time, I had 2GB, though my MoBo could only handle 1GB with the managers. How could you write for me? I was 1:1000000, or maybe even less. I had to do my programming on the fly, and often had boot discs for different programs. It's not that much different now, except that I would not be such a rarity any more, but hardly mainstream.
I'll bet that we can sort much out, by tackling the "Big 3," and then working down, if necessary.
I like doing test Projects, keeping things simple, and testing as we make them more complex. That helps isolate the issues in most cases. In another thread, the poor user says that all Project Presets, all formats and all Export setting yield issues. My first thought is to isolate on one Project Preset, one set of Assets, and see if it's a system issue.
Sometimes it's easy, and that is good, 'cause the user gets to editing and not fritzing so much. Just nailed one in Encore, but the poster gave me all the data necessary, and my memory did not fail me (maybe it was not "wine-thirty yet?). One post, and one correct answer. Life is good. Sometimes, it takes days, and many posts, to narrow things down. In but a few, there is an answer. In those (like the PGC error in Encore) one never does really solve the issue, and the only hope is to get the OP to start over, do everything by the book, and hope for the best, this time around.
Good luck, and be assured - I do feel your pain. If I have not had one of THOSE error messages, believe me, I have read of them too many times.
Hunt

PPro6 to Encore "internal software" error

I encoded in PPro6 and then imported an mpeg2 project as a timeline from PPro6 into Encore. When I try to burn a DVD, I get an error message: PGC "" has an error at 00;00;00;00. Internal software error: 50, line "" Info: name = "", ref= Bpgc, time = 00;00;00;00;00.
The project was fully rendered in PPro. I've re-exported 3 times, and it happens every time.
I did a search on the Forum, and found one other person who had this problem, but their problem turned out to be with their audio. My project has no audio at all. Just video.
Thank you for any help/ideas/suggestions you may have! I'm totally flummoxed.

Stan Jones wrote:
The .xmpses file is an xml (type) file.
Rename the file .xmpses.old and the .xmp renamed as .xmp.old (I don't recall for sure whether there was ever any benefit to renaming the .xmp file. We want to maximize the chances that it works, so rename both.)
Can I just say Stan I am so so grateful for this post. So easy to do and solved my problem!!! I was beyond fed up with the whole thing. After having such problems with Dynamic Link causing slight flickering in my videos I have tried to go back to Exporting with my own settings for Encore in CS6 but found it caused so many more problems than it ever did in previous versions of the programmes. I tried exporting the sequences in so many different ways, different bit rates, including Encore chaptering before Encore and even nesting. Had so many different errors like 52102, line 332 and this PGC error was the final one and my biggest problem. Cannot believe how simple it was. I normally chapter within Encore anyway so changing a little file name of the other 2 connected files of my sequence really was no bother at all.
I honestly think this is the answer to many of the problems that I have had in Encore as the errors although in different forms, more often than not, seem to be chapter related.
it is now 1.45am and because of you I can now go to bed to get up and film another event in the morning. CHEERS! (don't worry I'm a girl lol)

Internal Software Error: %0

I get the following error message after Encore 2.0 prepares the slideshows and goes to the next step. All of the video material is prepared and, the progress window is in the middle of "Planning Audio for movie". Any suggestions for a fix?
Adobe Encore DVD
PGC "Yosemite Valley" has an error at 00;00;20;04.
internal software error: %0, line Yosemite Valley - PGC Info: name = Yosemite Valley, ref = Ipgc, time = 00:00:20:04
OK
Thanks.

So, finally I've found the source of the problem and a workaround!
First the source:
when Encore has to transcode a video it must corrupt the file, because it's the transcoded file that causes the problem, I tried this by importing a transcoded file into Encore 1.5 there it came with the same error.
Now the workaround, ok maybe it isn't quite a workaround but it's a way to go:
What I did was: I built my project new in Encore 1.5, because Encore 2.0 has a problem importing the videos by me, but if you would just import the videos in 1.5 and let 1.5 transcode them so that all of them would fit on a DVD you should be able to import the transcoded files in CS3 and it should work, no guarantee.
Other possibility: try opening your project in encore 2.0 and re import your videos there and let 2.0 do all of the transcoding, that might work too!
But for certain: don't let encore CS3 do all the transcoding!
I'm working with PAL files I don't know if it will be the same by NTSC, but it's worth a try!
If anybody feels like reproducing the bug, here is the way to do it:
Make a project in Encore CS3 and import Videos encoded by premiere as MPG2-DVD (I think: .m2v .wav) and set the transcoding options to automatic, encore should have to transcode the files. Then let encore make the DVD, at some point you should get that nice PGC error!

PGC error

Similar Messages

Maybe you are looking for