-
Jeff Schroeder
June 15, 2012 at 4:56 pmI set up a test project using extremes to verify what would happen. With project settings at 4k and I used a 4k test pattern png with text generator over-layed. I zoomed to 1920, 1280, and 720. Then I set the project setting to 1280 and zoomed my 4k bitmap to 720. The results were best when my zoom did not exceed my project setting.
I recommend everyone who is interested, try it and see for yourselves.
Jeff
2-Xeon X5680 @ 3.33, EVGA SR-2 Mobo, 48GB DDR3, GTX 580 3072MB, 16TB Attached Storage, Win7, Vegas 11 x64
-
James Houghtaling
June 15, 2012 at 5:56 pmJeff your experiment would appear to support my thought that one should keep their project setting = the largest raw footage resolution and then only zoom/crop so as not to go below your expected render resolution – else live with a lesser quality for those clips where you did exceed render settings. Except for preview speeds, I do not hear any argument that says it’s better to set the project to the (lower) desired render setting.
—————
My Hardware:
Core i7 2.67GHz; Nvidia GTX580, 12 gig RAM Win7 64bit.My Software:
Vegas Pro V11 with Boris Continuum Complete 8, VASST Ultimate S; Bluff Titler; AE5; PhotoPaint and other stuff. -
Jeff Schroeder
June 15, 2012 at 6:25 pmJames,
That’s not what my results found. In fact it’s the opposite. You came a little late to the post, so you should read the whole thing. I have been saying all along that your project settings should be set at your delivery size, allowing you to crop in post to zoomed in sizes up to your delivery size without loss of quality. To set them at the highest resolution forces interpolated pixels when cropped.
Jeff
2-Xeon X5680 @ 3.33, EVGA SR-2 Mobo, 48GB DDR3, GTX 580 3072MB, 16TB Attached Storage, Win7, Vegas 11 x64
-
James Houghtaling
June 15, 2012 at 8:21 pmyeah I have read the entire thread I just didn’t go back and read your original comments again. Sounds like what you’re saying is that for some reason when you set your project to match the footage (say 1080p) vegas throws out all the 1080p data once you crop using the pan/crop tool? I think that may be the case when using track motion, but I never experience said loss using pan/crop.
I’ll have to try your experiment and post some screen shots.
—————
My Hardware:
Core i7 2.67GHz; Nvidia GTX580, 12 gig RAM Win7 64bit.My Software:
Vegas Pro V11 with Boris Continuum Complete 8, VASST Ultimate S; Bluff Titler; AE5; PhotoPaint and other stuff. -
Gilles Gagnon
June 18, 2012 at 1:47 pmThanks everyone for your input.
I’ll stick to keeping my proj props to 1080 and pan/zoom while maintaining quality… and render out to 720.
G
Gilles
-
Gilles Gagnon
June 18, 2012 at 1:57 pmOopps! Just reread some of the later posts.
Quite confusing as there is conflicting advice in the thread.
Can someone PLEASE tell me for once and for all if the following approach is the correct one?
“Set my project properties to 720 (original footage is 1080), pan/crop and render out at 720”
Cheers,
GillesGilles
-
John Rofrano
June 18, 2012 at 3:10 pm[Gilles Gagnon] “Can someone PLEASE tell me for once and for all if the following approach is the correct one?
“Set my project properties to 720 (original footage is 1080), pan/crop and render out at 720″”
Yes, that is correct. If you want to pan/scan and crop, you want to set your project to a lower resolution than your source so that you can use a subset of the full resolution of the source and still have good quality without scaling (unless you crop smaller than you project resolution).
~jr
http://www.johnrofrano.com
http://www.vasst.com -
Gilles Gagnon
July 6, 2012 at 7:55 pmGood afternoon fellows,
Regarding wanting to provide the best quality to a client for a video for which I need to crop (zoom in)….
Well I just did some tests using the two project properties and the resulting video’s quality looks identical. no difference at all!
It would appear that setting the property size doesn’t effect the outcome at all.Here’s what I did:
1. use source footage at 1080i
2. set proj properties to 1080/60i
3. crop clip to width of 1000
4. render using 720p internet template – gives video A5. set the proj properties to HDV 720/30p
6. once again render clip using 720p internet template – gives video BVideo A = Video B… they look identical quality wise.
Can someone shed some light and confirm this please?
GillesGilles
-
James Houghtaling
July 6, 2012 at 8:38 pmThat’s been my thought from the git go. So long as your don’t crop below your desired render resolution of 720 it shouldn’t matter if you start with a 1080 project or a 720. Advantage to starting with a 1080 project is that any generated media you create will be at 1080 and therefore giving you a better result if you change your mind and want to render at 1080 – of course any cropped events will suffer loss of information consistent with how cropped they are below the render setting of 1080.
But some smart people who chimed in on this thread say otherwise and I’m no smarter because I still have not run my own test. LOL… but I’m glad to hear your results Gilles.
—————
My Hardware:
Core i7 2.67GHz; Nvidia GTX580, 12 gig RAM Win7 64bit.My Software:
Vegas Pro V11 with Boris Continuum Complete 8, VASST Ultimate S; Bluff Titler; AE5; PhotoPaint and other stuff. -
John Rofrano
July 6, 2012 at 8:46 pm[Gilles Gagnon] “Can someone shed some light and confirm this please?”
Yes, your project property resolution has no bearing on the final render quality. My recommendation to work in the final output resolution is to help you know when you’re zooming too far (i.e. don’t zoom past the project resolution because it matches your output resolution) Vegas will use the full resolution of the media when rendering regardless of the project resolution.
~jr
http://www.johnrofrano.com
http://www.vasst.com
Reply to this Discussion! Login or Sign Up