Aviator459
Forum Replies Created
-
Well, I downloaded and installed the patch to v. 3.0.1 and I still have the same issues. The write-up for the patch said something about fixing compatibiilty for BlueRay. I was hoping they fixed this bug as well.
So, tell me. Can you right-click in the flowchart panel and select preview more than once without incurring the general error? If you can, then maybe this is something more specific to my computer rather than a code issue.
-Aviator
-
Ah, Thank you for informing me about the patch. I will look for that. I’m not sure why I missed seeing it. I’m using version 3.0 at this time. So that sounds very promissing.
-Aviator
-
Just had another thought. You get one chance at this per reboot. Compose your project and then preview to make sure it is what you want. Once you’ve done that, you will not be able to build or preview again until the compter is rebooted. I know, it blows. Save your project and reboot. Then bring it back up again and do a build. What I like to do is creat a DVD image so I can just burn the image to disc later.
It’s a long work around, but it gets the project done. Any luck with Adobe Tech support?
-Aviator
-
I have the same issues, but for me it seems to happen after I preview the menu or do a build. In any event, I believe a video file is created for the menu and stored in the Sources\Video folder of your project folder. I believe the name of the file is determined by your video settings. My file is called mp24x3NTSC720x480.mpg.
The strange thing here is once it is created it cannot be deleted. Even after Encore is closed. There is a stuck process that is keeping it tied up and therefore, when Encore tries to recreate it in a new build or preview, it generates a general error. I am unable to identify the process in Task Manager, so I doubt that it is listed there. Could be a memory leak/error within the program. Something is not being closed in memory.
After rebooting the computer, the file is freed and able to be deleted. Encore then responds normally until it has to recreate that file which is again stuck summoning the general error.
No solution here, just an observation. Check it out on your system and see if you are getting similar results. Maybe Adobe can issue a fix to this seemingly notorious bug in their code.