4 Replies Latest reply on Apr 2, 2011 11:14 AM by joe bloe premiere

    RED / .R3D proxy editing in CS5

    joe bloe premiere Level 5

      In CS4, using the REDCODE CS4 Win 1.3.msi add-on,
      the Source Settings menu has the option of setting a proxy editing
      resolution (Full, Half HQ, Half quick, Quarter, Eighth, Sixteenth).
      You can edit at a proxy res, then reset the resolution to "Full"
      prior to final encoding / export.

       

      This was a great feature for CS4.  No need to encode low res
      versions of RED media prior to editing then swapping out files,
      the proxy is accessed directly from within the .r3d file.

       

      CS4 R3D Source Settings:

      RED_SOURCE_CS4.png

       

      In CS5, the Source Settings menu does not seem to have
      an option for setting any proxy resolutions for editing.

       

      CS5 R3D Source Settings:

      RED_SOURCE_CS5.png

       

      Was this capability to independently set low res proxy
      resolutions for 2K, 3K and 4K media a function of the
      REDCODE plugin that is now lost with native .r3d support?

       

      Say it ain't so!

        • 1. Re: RED / .R3D proxy editing in CS5
          Colin Brougham Level 6

          Say it ain't so!

           

          It ain't so. You just use fractional playback in the Source/Program Monitor to set your playback resolution to 1/2, 1/4, or whatever is necessary to get smooth playback. With RED 4K, for example, at 1/4 Resolution you're operating functionally with a 1K resolution; you'll barely notice the "downshifting" when you play back the footage. With my workstation, I set the Paused Resolution at 1/2 and Playback at 1/4, and it works great.

          • 2. Re: RED / .R3D proxy editing in CS5
            joe bloe premiere Level 5

            Altering playback resolution just does not look as good

            as a CS4 proxy of the same resolution.

             

            I can flip files for proxy editing that look much better than running

            the display res at 1/4, and it does not take long.

            Just an extra step added to the workflow.

             

            Was this capability to independently set low res proxy
            resolutions for 2K, 3K and 4K media a function of the
            REDCODE plugin that is now lost with native .r3d support?

            • 3. Re: RED / .R3D proxy editing in CS5
              Colin Brougham Level 6
              Altering playback resolution just does not look as good

              as a CS4 proxy of the same resolution.

               

              I honestly can't see how it would be any different, but not having used RED in CS4, I'll have to take you at your word on that one. The "proxy" resolution from CS4 would have fundamentally been the same process as changing the playback resolution in CS5. If the quality isn't the same, I suppose that would be a difference between whatever scaling the non-native plugin was doing and what the native plugin is doing.

              1 person found this helpful
              • 4. Re: RED / .R3D proxy editing in CS5
                joe bloe premiere Level 5


                I wish you had a copy of CS4 running to see the workflow difference... it is considerable.

                 

                Flipping .r3d files to 1920x1080 MPEG-II I-frame is a fairly quick and simple process
                to run in AME.  The files are 1/4 the size of the original media and they play back
                in a 4096x2304 timeline without any yellow or red line even if they are "Scaled to Size",
                and it looks better than if I reduce playback resolution.

                 

                Creating my proxies is easy to do, I just miss the feature that was available in CS4
                while using the REDCODE CS4 Win 1.3.msi add-on,

                 

                Was this capability to independently set low res proxy resolutions for
                2K, 3K and 4K media directly from within the .r3d file a function of the
                REDCODE plugin that is now lost with native .r3d support?