John Rofrano
3
COW Coins
Forum Replies Created
-
The key here is “Document Size”. In video there is no “document”. What that screen is telling you is that if you were to print that image at 72 dots per inch it would be 53 inches across, but if instead, you packed 150 dots per inch, it would only be 25 inches wide. Smaller dot… smaller printed picture. The “image” has exactly the same quality (amount of information) in both cases. It is just being printed with smaller or larger dots.
The “dot” on your computer monitor can’t get smaller. You can’t pack more to the inch. So DPI has no effect. If you want a comparative size, your normal computer monitor is 96 DPI. So setting the DPI to 96 will give you “information” about how big the image might appear on your display. Of course, it will really depend on how many “pixels” per inch your computer monitor actually has which is dependent on the physical size of the monitor.
Note in both cases the Pixel Dimensions did not change. Since your computer monitor is based on pixels, the picture quality did not change regardless of the DPI setting (which is primarily a “printer” setting)
Does that make sense? (if not, ask more questions)
~jr
http://www.johnrofrano.com
http://www.vasst.com -
You can also try using the Track EQ that’s already on all of the audio tracks. The first point is set for Low Shelf, which is what you want. Set the Frequency (Hz) to 300 and the Gain (dB) to –Inf (all the way to the left). Now listen to a loop of your audio and adjust the frequency to filter more or less of the wind rumble.
Wind is broadband noise across all frequencies so to really get rid of it you will need a plug-in as Steve suggested. BIAS SoundSoap 2 is inexpensive, easy to use, and does a pretty decent job of noise reduction in general. A killer tool is iZotope RX but that is probably more than you want to spend.
~jr
http://www.johnrofrano.com
http://www.vasst.com -
I didn’t want to say anything but I wouldn’t recommend a Dell to my worst enemy. Nothing but trouble and inferior parts by design. I was burned once, but never again. Sorry to hear you’re having trouble with yours.
~jr
http://www.johnrofrano.com
http://www.vasst.com -
> So essentially M2T is higher quality, even with the same specs?
It’s not really the same specs but yes it is higher quality. There are different profiles that are applied to the MPEG video and SD and HD use different ones. Also, as I pointed out, your standard MPG files are stored as program steams and M2T is a transport stream. So there are several differences in how the video is stored and encoded between SD and HD.
~jr
http://www.johnrofrano.com
http://www.vasst.com -
> scripting can’t handle this?
Nope. None of the generated media parameters are available to the script API. It’s just a “black box”. All scripts can do is select presets. Unfortunately, presets include the text. 🙁
~jr
http://www.johnrofrano.com
http://www.vasst.com -
I assume you are talking about rendering. It doesn’t matter what format the source is, you should use a template that conform to the format you are delivering in. For an SD DVD use a standard DVD template.
~jr
http://www.johnrofrano.com
http://www.vasst.com -
It sounds like you want to manipulate the objects themselves in Vegas which you cannot do because Vegas does not support the import of 3D objects. You would have to use Boris BLUE or the combination of After Effects CS4 with PhotoShop CS4.
The next best thing is to do as Mike said and animate the objects in Maya or Cool 3D and export with an alpha channel. If you want to match camera movements you will need a match moving program like SynthEyes, MatchMover Pro, etc.
~jr
http://www.johnrofrano.com
http://www.vasst.com -
No it is not the same thing. M2T uses a different profile and is a transport stream. If your other applications don’t support M2T files I would highly recommend that you use the CineForm AVI codec instead. You will need to at least purchase Neo Scene in order to use CineForm files in other programs but it is well worth the money if you are working with multiple applications in HD.
~jr
http://www.johnrofrano.com
http://www.vasst.com -
Hi Andre,
In your original post you said:
> I shoot in HD, edit in Sony Vegas Pro 8 with NTSC Widescreen project settings, then output in NTSC Widescreen.
Just now you said:
> when I “save snapshot to file”, it’s saving a JPEG and the attributes of that JPEG are 655 X 480 and not 720 X 480;
That should not be happening. If your project is NTSC Widescreen and you set your preview to Best (Full) and use Snapshot to File, you should get a 873×480 PAR 1.0000 JPG file. If your snaps are 655×480 this is your problem. It’s too thin and getting stretched back out to widescreen.
One thing to be clear about is that Snapshot to File uses the resolution of your video preview. If it is not set to Full, you will get less resolution. It sounds like your project was set to NTSC DV and not NTSC DV Widescreen when you did the snaps. That’s the only way they would be 655×480. You need to redo them at the full project resolution to fix the problem.
~jr
http://www.johnrofrano.com
http://www.vasst.com -
If you press the image icon when you create your post (second icon from the right above the area that you type in) it will give you instructions on how to upload those jpg files and embed them in your post.
~jr
http://www.johnrofrano.com
http://www.vasst.com