Participating Frequently

Question

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

Forum|Forum|17 years ago
September 8, 2008
64 replies
31719 views

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

Encore

This topic has been closed for replies.

Show previous replies

_

_marcel_wolfert_Author

Participating Frequently

Nvida Gforce 6100 nForce 405
driver version 9.1.3.6 date: 12-07-2006

I am downloading the newest driver now version 15.24 date 12-09-2008

Will check result

marcel

Stan Jones

Community Expert

On the PC: Intel P4 2.8, Nvidia GEforce4 MX440. I just checked the other day, and I am still using the latest drivers, but they are not "new."

On the laptop, a Pentium M 2.0, Nvidia GeForce Go 6600. I can't tell if the drivers are current; they only show the 8800 series as option under the Geforce Go type.

Stan

the_wine_snob

Inspiring

I have an nVidia FX4500-512 MB Quadro, latest drivers (as of late August) and no errors, but with EncoreDVD 2, not CS3.

Hunt

Jeff Bellune

Legend

Marcel makes a good point. How about video cards? I have an ATI Radeon X1600 upgraded from an ATI Radeon 9800.

Any chance you guys with the PGC errors have nVIDIA cards?

_

_marcel_wolfert_Author

Participating Frequently

Stanley,

What kind of processor have you got?

Bill, Neil and Jeff all have Pentium and no errors. I have an AMD and have an error. The computer I use with Encore 2.0, without errors, is also a Pentium.

Just a guess. I still believe it is more system related.

Marcel

Stan Jones

Community Expert

Thank you Bill and Jeff - and Neil! What is different about my test is that this specific avi clip, in a brand new encore project, creates a pgc error on my system. I am completely open to discovering I have done something wrong, but what can be wrong? System issues are likely, but how would they interact with a particular avi file. Note again that I completed a project last week (not with this avi file) that contained animated buttons, multiple timelines, correctly replaced assets, etc., burned without a hitch.

If someone who does get the pgc error would be willing to do my Test 1 in post 10, I would be interested in your results.

Jeff, just for the record, you added a couple extras to the type project I set up, by using a motion menu and animated button - both factors that result in the pgc error for some users. I used the same options as you did, and still got the pgc error.

But it got me thinking. You did not mention whether you set this up for an auto transcode with max rate 8, as I had. I changed my transcode setting for this avi (ie. my test 1) to cbr 4.5, and ... built with no problem. I do not have time to track this down just yet, but makes me wonder. A quick look at the transcoded file with mpeg bitrate parser shows a rate spike at the very end -max rate 27,000. I seem to remember discussion that this tool was showing an error. The 4.5cbr file has the same type of pattern, but peaks at 16,000. I don't see where to examine this down to the frame level (only seconds), but I wonder if the point at which this spike occurs is the same as the time of the pgc error. One of my files from the project finished last week (longer - 3 minutes) had a peak of 8,058 using this tool - i.e. correct.

Is there a better tool to examine this? Is there a comparable tool for avis?

Neil, I am able to demonstrate the pgc error/no pgc error by deleting the xmpses file before importing the same m2v a3c files into a new project. Any idea what may be at work?

I believe my tests eliminate the asset swapping issues, and I don't know what could cause these problems in terms of system issues.

_

_marcel_wolfert_Author

Participating Frequently

Neil,

I still do not agree with you. If you can't create an error yourself then you don't know what the error is related to.

You can read that tests are done by Bill who never gets an error (he uses CS2) and even after swapping around files still not got an error.

In CS3 I almost always get an error but after erasing the xmpses file it's gone but still I can't create animate buttons. Copying the files to CS2 with the xmpses file I also get the error. Without the xmpses file I won't get an error and I can even use animate buttons.

If you were right then swapping assets was allowed with CS2 but is not any more with CS3 ??

So please to confirm your statements by doing the following:
-make a project in Premiere CS3
-use media encoder to create a single M2V file and a single AC3 file
-swap those files around a few times, use blank spots in file names, save your project on a few different locations.
-Then create a project in Encore CS3 import the M2V file as a timeline. At the file location the xmpses file must be present.
-hopefully you then can create this error yourself.

If you can't get an error then I believe it is system related and not your work flow or planning. I'm almost sure about this while CS2 uses the same Sonic coding as CS3.

After multiple test for about a month now I am at the point to loose my interest in Encore CS3 and will switch back to CS2 forever without errors with animate buttons almost same layout and options as CS3 but now I ......can swap around as much as I like and use filenames as strange as I want.....My statements are: "never change a winning team" and "if it ain't broken don't try to fix it". So if CS2 works why change?

Marcel

neil wilkes

Legend

To follow up on Jeff's post above, I just did a set of 5 discs where every single menu was a library one with buttons that I deleted as they were un-necessary. Every button was an animated Video button.
Not a single problem anywhere.

This PGC error is related to either
A - Assets being repeatedly exchanged/edited/moved/swapped etc or
B - System.
The easiest way to avoid these type of errors is to plan your project first. Do not import a single asset into Encore until you know what you are importing is the final version. Sure - there are tools there to do basic editing, but if you planned this properly in the first place it should never arise. It all brings it back to the age-old point that just because you
i can
do something does not necessarily mean that you
i should
do it, or that it is in any way a good or desirable thing to do.

Plan your project.
To avoid Feature Creep, get your client to sign off on the final flowchart as well. Tell him/her that any changes they propose will add to the bill - believe me, they will then suddenly lose interest in adding ever more content. It protects you, and it protects your client.

Jeff Bellune

Legend

Stanley,

I put your .avi clip into a timeline in an empty Encore project on my machine. I added the Gears Submenu motion menu from the Library. I deleted 2 of the video thumbnail buttons and linked the third to the clip's timeline. I selected Animate Buttons. I set the menu as First Play and I set the End Action of the timeline to link back to the menu button.

I rendered the motion menu and previewed the project.

No errors on check project. I built a DVD image. The project transcoded and built without error.

Same result as for Rodger's project.

-Jeff

the_wine_snob

Inspiring

Well, I got off my lazy ___ and did some reading.

The majority of those with this/similar problem(s) are on CS3. Some reported that a roll-back to CS2 solved their issue.

One person had the error with CS2 and one with Encore 1.5 (if I read that reply correctly).

Seems that CS3 is the most common thread, though CS2 is not 100% immune. Nor is 1.5 (?), based on one reply.

Hunt

Show more replies

Sign up

To post, reply, or follow discussions, please sign in with your Adobe ID.

Sign in to Adobe Community

To post, reply, or follow discussions, please sign in with your Adobe ID.

Scanning file for viruses.

This file cannot be downloaded