Matt Carlson
Forum Replies Created
-
Sorry I mispoke when I said send it back to the Tascam input. If the vocalists headphones are attached to the Tascam unit I do not see a possibility of feeding back an affected signal without it going directly back in to the recording.
-
There is one more piece of information that is necessary. How are you actually listening to your computer’s output? A generic sound card will have problems with the Vegas side of things which is to have “Input Monitoring On” checked in the Record Input button on the audio track. This will allow effects to be applied at the track level to be heard but the input source is unaffected. This, however, only works well if the sound card being used has ASIO drivers and the effects are not overly ambitious (simple reverb should be fine, and it can be changed after recording to any effects chain you want.) The problem you will have is whether your computer output (depending on sound card and cpu) has latency. On a good computer recording card (I use m-audio 1010 and 1010lt) you could just send the affected voice back to the Tascam’s second input and all should be fine. If you try doing that with a motherboard generic sound device the latency may be unbearable (then again you could get lucky and the “delay” could pass for reverb… but none of us are ever that lucky are we?)
-
The clickable portions of video on YouTube are done through the Annotations section of the video manager on YouTube itself (you can find the information there.) I do not know of any plugins or any developers taking an interest in somehow adding an export in Vegas for this type of information right now. Now that Vegas exports directly to YouTube it is quite possible this will come in the future, though.
-
In order to get what you want two things must be done.
1) The pan/crop size on all your events (hopefully this is not a highly split and edited video already) has to be 640×360.
2) When you get to the render dialog you must choose custom frame size in the frame size drop down and enter 640×360.
If you do #2 without doing #1 all the video information will be squished in to the new aspect ratio. If you do #1 without doing #2 it will look fine but you will not get what you want: a actual frame size of x360. It will be a 640×480 video with borders baked in.
-
I just did a test to see if an image sequence is a valid replacement option and it is. You can edit your Quicktime version of your animation and have the smooth playback you want then right before you render replace it with the better looking image sequence version.
-
Yes Steve is not engaging in hyperbole. Neat Video is x@#*}^# Amazing. BCC Noise reduction ends up blurring the pixels much more than Neat Video does. The only advantage that BCC has is the built in pixel chooser that most of the BCC plugins have… but considering the final output it is not enough to consider using over Neat.
-
The sequenced PNG version on the timeline is not actually a codec implementation. Vegas just strings together the images by itself. In theory this should not be a bottleneck but the way the program works the editor prefers to get its data from the API through a codec (and preferably a codec that it is optimized for like certain Quicktime ones.) When it has to do resizing of PNG images instead of video to fit on a timeline things start to slow down a bit. There is not a real solution to this except possibly a proxy… but I am not exactly sure if the media bin “replace” function can actually replace a clip with an image sequence. If it can you can edit the Quicktime animation and later replace it in the media bin with the sequence and all of your changes will remain in the timeline.
-
I am sure there is a preset somewhere in the Vegas text media that can come close to this and someone will probably direct you to it. However if you want total control and development time is not an issue here is how you would go about it.
Create each single word as a different text media on a NEW track (yes this will get cumbersome to look at.) At the point you want the word to appear you drag the text media event to that point, fade it in quickly to your liking, and have that word event exist until you want the next “page” of text to start appearing or the end of your project depending how much text you will be going through. Placing the text visually quickly where you want can be done by using the Pan and Crop window on each word’s event. Locking the window to drag in one particular direction is great help for aligning the text properly (or you can pay attention to the window’s coordinates to maintain a linear alignment.)
Doing it this nuts and bolts way will allow you to have each word exactly the way you want it as opposed to fiddling with timings in a preset in one of the media generators. It will allow you to have each word the color, font, and size you wish as well without having to puzzle out where to make key frames in a preset solution. The downside is that you have to manually space and place everything yourself instead of just typing in your text somewhere. In the end it may take the exact amount of time doing it by hand than it would to find and wrangle a preset to your liking. On the other hand someone may have done this a hundred times already in one of Sony’s media generators and point you a preset that you need.
-
Copy the event of the state you want (in this case “un-normalized”) then select any and all of the events you wish to change and right click/paste event attributes. Unfortunately this will also copy over any effects of your first event as well so ideally the only thing you have done so far is change normalization.
-
The SSD can help a bit with speed in video editing if you put the source files on them. The sweet spot for data transfer is between a standard 7200rpm and an SSD. Somewhere in between CPU decoding and calculations become the bottleneck and all the disk speed in the world will not help… and an SSD will certainly take you to the point of this bottleneck easily (so will a Raid setup of your standard drives.) If your terabyte drives are in a Raid setup you will not see a significant advantage in using the SSD as a scratch pad. I am also a musician so I use SSD’s for virtual instrument sampling which works better with higher disk data transfer but most video editor’s don’t have this need.
With Vegas the most significant increase in having everything SSD is the program start (which you already have with, I assume, the program being on your OS drive.) Having the project files on SSD (and slightly better because it is a completely different physical drive) your projects will load much faster as well. That will be about it.