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

the_wine_snob

Inspiring

Stanley,

I am going totally from memory here (just too lazy to re-read those two very long threads, I guess... ), but *believe* that some experienced it with CS2. If I get an extra second, I'll go poke around them. One started so very early, that it almost HAS to be a CS2 error. Also, most people reporting the error(s) were loathe to give any details, even after repeated urgings. Just a lot "me too's."

As for the folders, I think that one could easily build these. I may have committed an error, but could not find it on second look. I think my problem with your NCOR file was CS2 v CS3, as you pointed out. Still, I got the build, but just could not set the Title Remote, without another error. Project still built successfully, which, in light of the version differences and the direction that I was applying them, was my biggest surprise. Until my test, I'd have told anyone that a CS3 Project could NOT be opened and worked on in CS2. Look how wrong one can be. Damned near worked 100% and there might even be some workaround for the Title Remote error.

Good luck, and let me know if I can do anything else on this one.

Hunt

Stan Jones

Community Expert

Jeff, thanks for your response.

I remember that test well. It was significant in that it resulted in the pgc error occurring on a system (yours) that did not normally have such an error. Also, simply redoing the project resulted in a good burn. It was part of what helped me to conclude that these errors were not a simple bug or a workflow problem that could be reliably produced.

The hypothesis here is that the avi file I posted itself results in a pgc error using a very simple project and automatic transcoding in encore. There is little opportunity for encore workflow problems. And, while there certainly can be problems at the PPro level, a dv avi type 2 file exported by ppro should not have such a problem.

Hunt confirms that it did not have a problem on CS2. CS3 on my laptop showed a problem. I've forgotten: does the pgc error occur for anyone with CS2?

I am most interested in someone else using cs3 simply making any project with the avi file I posted. (In hindsight, I should not have even posted the project file - without the folders it is not meaningful.) The multiple project tests I described extend the notion into understanding what is going on with the deletion of the xmpses file.

Jeff Bellune

Legend

Stanley,

I participated in a similar test before, using someone else's project and assets on my system.

Loading and building the project that was sent to me resulted in the error (the first time I had ever seen the actual error!). But after rebuilding the project with the same assets, project elements and workflow, and then after that doing some naughty things with the assets that I wouldn't normally do, I could not reproduce the error. Zip. Nada.

I suspect that it would be the same with your project and assets.

-Jeff

Stan Jones

Community Expert

Yeh, maybe Jeff will get tired of playing with Dan and Jim and try my file.... lol.

Jeff, if you try this one, I really don't think the menu/buttons make a difference. I think it is something about that avi file or, more likely, that file on my system.

As soon as i wrote that, I realized that, duh, I have a laptop with cs3 on it! Ran my tests. As with the test using my pc, Tests 1 and 2 fail. Test 3 works.

the_wine_snob

Inspiring

@Stanley,

Dang, I had forgotten that your NCOR was CS3, even though I had typed that a half-dozen times in my reply, while I was testing. Yes, probably a good reason for CS2 to throw an error, or two. Just overlooked that possibility. Interesting that 99% of it worked fine and it Burned to folder perfectly from EncoreDVD2. There is more backward compatibility than I would have expected. I'll also re-check my directory recreation to make sure I didn't commit and error there.

Sorry that I did the Menu edit in PS. That is just my habit. I'll go back and see if deleting the Buttons in Encore makes any difference.

Wish I could help you test on CS3.

Good luck,

Hunt

jbowden

Community Manager

xmlns represents the namespace for an XML document.

_marcel_wolfert_Author

Participating Frequently

Still looking for the difference in the m2v.xmpses and the mpg.xmpses files. I figured out that you can both open the xmpses and xmp files in "windows Wordpad"

In the first lines of the xmpses file the toolkits and framwork creation dates are mentioned. After that the program used (encore, premiere cs3 etc.) Then for some strange reason there are mentioned a few webpages. For example:

xmlns:vindaloo='http://ns.adobe.com/1.0/vindaloo/'>

why???

Then there is some information on the bit rate, frame rate, field order, picture dimensions and more. Finally the picture data, duration, size, and headerdata are shown in a very very long list.

In the m2v.xmpses the file ends with a stream size and stream duration

The mpg.xmpses file shows before these data the audio data, while its about a muxed file and a m2v is not muxed so no audio data in the m2v.xmpses file.

The mpg.xmpses end at the video part (somewhere 3/4 of the file) also with a streamsize and duration.

Here is where I can see a small difference for a tipical file with an error:

m2v
streamduration 211838400
streamsize 2353756996

mpg (muxed file)
streamduration 211838400
streamsize 2353756992

If I look in the encore 2.0 version at the created animated menus, also a mpg.xmpses file but without audio, I see a streamsize witch ends with the numbers 6996.

I don't know if it is something but it is strange.

After that I looked at an Encore cs3 file with motion menus (movie background) and animate buttons.

All the MM_menus end with streamsize 6996 while all the menus with animate buttons end differently: 3214, 2626, 7329 etc.

Even more strange.

Stan Jones

Community Expert

Hunt, thanks for trying this out. So my "file that creates a pgc error for me every time" [in CS3] does not create a problem for you in CS2. I'm still curious about CS3 - anyone?

I think you followed my process in Encore right, except that I did not edit in PS, I just deleted the buttons in encore. but I have gotten the error in either condition in other projects.

I wonder if your odd results in my ncor project is the CS3 vs CS2. I don't get any of the errors you describe, but, as you note, I provided only the project file, and not the supporting directories. so it was not likely to work.

the_wine_snob

Inspiring

Joe,

Thank you for that clarification. I see that I was wrong with my assumption. Glad you got that correction out there.

Hunt

the_wine_snob

Inspiring

Stanley,

Unfortunately, I could only test this on EncoreDVD2, not CS3. I went through your first two tests, and each time Encore built to a folder (played fine on Cyberlink PowerDVD) with not a problem.

For Test 1, I created a new Project. Imported the AVI, as a Timeline. Imported Sunset and did Edit in Photoshop, to remove unused Buttons. Saved back to Encore. Linked Menu as Play First and its Play All Button to the Timeline. Set End Action on Timeline to Return to Last Menu. I tried this both from the drop-down and with the Pickwhip, just to make sure. EncoreDVD2 built to a folder perfectly, regardless of which End Action setting method I used.

For Test 2, I created a new Project in a new folder. Imported the m2v as a Timeline and the AC3 as an Asset, then added the AC3 to the Timeline. I then Imported Sunset and did the same Photoshop editing. Back in Encore, I linked the Menu as First Play and its one Button to the Timeline. I set the End Action of the Timeline, both with the drop-down and the Pickwhip once more. Again, EncoreDVD2 burned the Project to folder perfectly with both End Action methods.

Rather than trying your Test 3, since both 1 & 2 worked perfectly, I recreated the necessary structure to run your Clip1avi.ncor. As I didnt have your modified Sunset Menu in that structure, I got a placeholder Menu, but replaced it with the one from the Library. I did the same PS work, and Saved. I had to point Encore to the Clip1avi.avi, as my structure was obviously different, than yours. No problem, Encore accepted it. I linked everything as per tests 1 & 2. However, on Check Project, I got the Menu Remote Not Set error. Heres where it got odd. When I clicked on the Menu Remote setting in the Properties Panel, I got the dreaded Sorry, an abnormal condition has been detected. Before quitting, you have one chance to save your project (dont use the same name as the original). I did a few Save_As, and tried the Pickwhip for the Menu Remote - same error. I closed, and opened on of my Save_As Projects. Same error. I tried all variations of Saved Projects, but all yielded the same error. I went ahead and did a Burn to Folder, ignoring this error message. Though the Menu Remote was not set, the Project Burned perfectly.

I do not know if this additional little problem came from MY building the folder structure for your .ncor file, or if there is something amiss in your .ncor file. I would suspect that it is something in the way that I set up folders. Maybe I missed something necessary for Encore. I will assume responsibility for this one. Out of curiosity, did you get that error in your tests?

Im sorry that I did not get the PGC error in any of these. I also listed things in the exact order that I did them, in case that has any bearing on the problem.

Ill keep these files around on the workstation, just in case you need for me to try something else.

Computer:
3.5GHz Duo-core Intel
4 GB Corsair Pro (4x1GB) RAM (3GB switch)
4x 1TB SATA II HDDs
1x 1TB ATA-100 HDD
nVidia Quadro FX4500-512
Creative SB 5.1 SS
XP-Pro SP3 (latest patches)
Adobe CS2 (remember, Im on CS2) Production Studio

Good luck, and let me know if you want me to try anything else,

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