Skip navigation
Currently Being Moderated

Workflow question starting big, then small, then big, it goes on

Sep 10, 2010 9:37 AM

Hi,

 

I have a project. I have several comps, let's call one of them Comp A.

 

Comp A is 1920x1080 pixels in size. I am hoping my company will make the switch to blu-ray sooner or later, but it hasn't happend yet, so I was working large.

 

I need to output to standard DVD size, 864x486

 

So I place Comp A inside of a new comp, let's call it SizerComp. SizerComp is 864x486 pixels in size, and this is the comp that gets rendered, and finally, authored to DVD.

 

I notice that the DVD that results from this output, the text is somewhat blurry. Is this because of the workflow I have used? Or maybe I need to scale my text up larger? It's not small text, but definitely on the smaller side.

 

 

Ok onward.

So I am also rendering videos from 3DS Max. I don't want to render at 1920x1080 because it takes FOREVER. Am I safe to render at the final size my DVD will be? So can I render 864x486, place this file into Comp A, and then scale it up to fill the comp? It would pretty much double the size of the 3D frames that were outputted, but then upon final render, the whole Comp A would get sized back down to 864x486 again, the original size of the 3D frames.

 

So for the second scenario, am I looking at a quality loss on my 3D output?

 
Replies
  • Currently Being Moderated
    Sep 10, 2010 10:02 AM   in reply to garek007

    If the point of working large is that you think that there may be a need for a large version later, then I would suggest doing your 3D renders at the large size, even if it takes a long time. Scaling of raster images is always going to cause a quality loss.

     
    |
    Mark as:
  • Currently Being Moderated
    Sep 10, 2010 10:25 AM   in reply to garek007

    The quality loss when scaling down is typically less than the quality loss when scaling up, but it does occur.

     

    Yes, I would recommend working at your output size in most cases.

     

    You had a good thought, which is to work large if you think that you will be required to output at a large size later---but there are tradeoffs. And, if you're really not likely to have to output large later, then you've made those tradeoffs of quality and time for nothing.

     

    I made similar points here.

     
    |
    Mark as:
  • Currently Being Moderated
    Sep 10, 2010 12:14 PM   in reply to garek007
     
    |
    Mark as:
  • Currently Being Moderated
    Sep 10, 2010 1:28 PM   in reply to garek007

    Sorry, but I'm not going to be able to respond much more on this thread today. Very busy.

     

    Regarding text, though, see this.

     
    |
    Mark as:

More Like This

  • Retrieving data ...

Bookmarked By (0)

Answers + Points = Status

  • 10 points awarded for Correct Answers
  • 5 points awarded for Helpful Answers
  • 10,000+ points
  • 1,001-10,000 points
  • 501-1,000 points
  • 5-500 points