4 Replies Latest reply: Nov 3, 2010 2:01 PM by Stan Jones RSS

    Why can't project property changes affect file size in existing projects in Encore CS5?

    zorrocbr Community Member

      I had 5:30 minutes of MPEG4 Video that I brought into Premiere Pro CS5, did my editing and transitions and then dynamic linked to Encore.  I built my menus, and then set the options to Blue Ray and DVD transcoding as automatic to fit on a 25 GB blu-ray disk.  This worked.  For my next project I decided to transcode in Premiere Pro rather than in Encore with basically the same input assets (5:30 MPEG 4).  I set the project for Blu-ray and DVD custom options with 720 X 480 resolution, custom settings for the bitrate with a max of 8MHZ, target bitrate of 6 and low of 4, quality setting 5.  This resulted in a transcoded file size of 19995 GB.  So that I didn't have to rebuild all my menu structures etc., I opened the previous Encore file I had done, deleted all the assets, then imported the Premiere Pro asset and did all my chapter links etc.  The project shows as Blu-ray with Dvd at 720 X 480 (which is what I wanted) but the file size is 97GB!!!

      I went to project settings thinking that maybe there was something there to change but it was already set to Blu-ray format with resolution at 720 X 480 and a max bitrate of 15MBs which is what I wanted it to be.  Then I closed Encore and started a new project and defined the project settings as Blu-ray with 720 X 480 Resolution.  Then I imported the SAME asset that had already been transcoded in Premiere, brought in some simple menu to test and now the project size was a little over 20 GB!!!!  Why would I have to start a whole new project to get the file size correct?  Both Blu-ray and DVD showed as "Don't Transcode" so I am not sure where all the additional file size came from and why it only did it on the pre-existing project but not the new project???

        • 1. Re: Why can't project property changes affect file size in existing projects in Encore CS5?
          zorrocbr Community Member

          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 CommunityMVP

            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 Community Member

              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 CommunityMVP

                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.