-
1. Re: Why can't project property changes affect file size in existing projects in Encore CS5?
zorrocbr Nov 1, 2010 6:54 AM (in response to zorrocbr)Quad core 2.4GHZ processor
100 GB on C drive and 100GB on external hard drive
6 GB RAM.
Windows 7 64 BIT
As info.
-
2. Re: Why can't project property changes affect file size in existing projects in Encore CS5?
Stan Jones Nov 1, 2010 10:20 AM (in response to zorrocbr)Answer 1: Encore is funny like that.
Answer 2: You may not have fully or correctly deleted the previous assets, particularly if they were already transcoded in Encore. You didin't have any named the same as the deleted ones did you?
Answer 3: The transcoded from PR assets were actually bigger than you believed, or you did not read the transcode status correctly. (Unlikely.)
Answer 4 (same as Answer 1 mostly): As appealing as it is, That is just not a good workflow with Encore. I have found that you can import the same menus, but delete assets and bringing new ones in brings grief. You might experiment with using revert to original and replace asset, but there are too often problems.
-
3. Re: Why can't project property changes affect file size in existing projects in Encore CS5?
zorrocbr Nov 3, 2010 1:37 PM (in response to Stan Jones)2) The assets were deleted. The new assets may in fact have had a similar name as deleted assets, Premiere Pro named them "Sequence 1" etc.
3) I brought in the same new assets to a "New" Encore project and burned successfully to a 25 GB disk. Encore did not tray to re-encode and the file size was about 21.5 GB.
4) It seems a bit odd that this wouldn't have been fixed in Encore, intuitively you should be able to just delete and replace assets without causing grief. The work around was a bit of a pain, but I created a template with no assets in it other than menus and for new projects I bring in the assets and save it as a different name so I always have a blank template to work with.
Thanks for the help. :-)
-
4. Re: Why can't project property changes affect file size in existing projects in Encore CS5?
Stan Jones Nov 3, 2010 2:01 PM (in response to zorrocbr)4) It seems a bit odd that this wouldn't have been fixed in Encore, intuitively you should be able to just delete and replace assets without causing grief.
Some of us suspect that the fact that Encore is based on the sonic authorcore may limit adobe's ability to fix/tailor as they wish.The work around was a bit of a pain, but I created a template with no assets in it other than menus and for new projects I bring in the assets and save it as a different name so I always have a blank template to work with.
This is the more common workflow, and it works more consistently.


