3 Replies Latest reply: May 29, 2008 6:46 PM by (Carter_Reedy) RSS

    Why Does Encore 2.0 Transcode Twice?

    Averdahl Community Member
      Hi!

      I prefer to transcode my assets (DV-avi's) prior to burning and have noticed several times that even if the status of all assets says Transcoded, Encore 2.0 sometimes transcode one or more items once again when i burn the DVD eventhoug they already have been transcoded. I dont remember this behaviour when i was using Encore 1.5.

      A couple a minutes ago i had five motion menues transcoded prior to burning the disc, and when i pressed Build to build the DVD Encore 2.0 did transcode one of them once again.

      - Anybody know why?
      - Does this happen to you?

      /Roger
      Premiere Pro User Group Sweden - www.pproug.se
        • 1. Re: Why Does Encore 2.0 Transcode Twice?
          Ruud Blauw Community Member
          You didn't change anything (not even nudge a button into place) to that menu?
          • 2. Re: Why Does Encore 2.0 Transcode Twice?
            Averdahl Community Member
            The only button i used contained only a button highlight and highlights dont need to be rendered. So this button was not visable at all in the menues. This "re-encoding" has happened to movies as well, thats whats make it so strange.

            I did test some motion menues, thats why i only had highlights in them, so no "real" buttons was involved in any menu.

            /Roger
            Premiere Pro User Group Sweden - www.pproug.se
            • 3. Re: Why Does Encore 2.0 Transcode Twice?
              I'm building an SD DVD from a 90 minute HD quicktime output from FCP in DVCPro HD at 23.976 fps. I have a new Intel 8 core Mac with 8 Gb of RAM and 2 TB of internal drive space running CS3 production premium. The quality setting I used was a 2 Pass vbr 1.5 lowest, 4.9 average and 7.8 max data rate at 23.976 fps. The audio was stereo PCM at 48khz. The transcode step of the build ran for 5 hours and then the lower progress bar reset to the beginning and started over again! I let it run for another half hour to see if it was going faster than the first time but it wasn't so I stopped it and used a lower quality file from Compressor instead. What happened? Was it going to take 11 hours to encode a 90 minute film?