[Norman Black]

I believe they call this a swish or whip pan.
Try a Google for “whip OR swish pan transition Vegas” or
“whip OR swish pan Vegas”

Here is one link from the results
Thread link

Boris has a plugin to do this. With a bit of work you can get an effect you might be happy with straight from Vegas.

[Norman Black]

This is the only link I have to some free stuff, effect wise, here

They seem to be building block type stuff.

[Norman Black]

Your “full hd mxf” file were probably mpeg-2 encodings.
AVCHD is AVC (H.264, mpeg-4 part 10) encodings.

AVC is a more complex specification capable of greater compression and it requires more work(compute effort) to decode than mpeg-2.

That is my guess as to why you had difficulties with the AVCHD files.

Vegas 12 has a smart proxy feature which may be of help. The smart proxy is mpeg-2 encoded and is used when is display mode of preview or less, otherwise the source is used.

I need to smart proxy my GoPro 1080p60 files (AVC). I smoothly can edit 1080p30 but the 60fps files are too much for my machine.

[Norman Black]

Yes, it is a given that if you use things like youtube/vimeo/smugmug to deliver your video you give up all control over what format and bitrate is delivered.

For the other options the OP talked about one should consider format, bitrate and such.

Never so much about upload, but customer download or streaming depending on what you do.

[Norman Black]

For internet delivery I think you want to keep the file size as small as you can, which means you want the best compression you can get and keep the quality to your standard. AVC (H.264) is probably the best compressing widely available encoding you can use.

The x264 encoder would give the the best quality at lower bitrates. People commonly use Handbrake as a front end interface for x264 and use the free DNxHD MOV codec as an intermediate file to Handbrake.

Use High profile encoding for best quality. In x264 speak, use Medium preset or slower for best quality.

Also note that WMV with the VC-1 codec should be pretty good as well.

[Norman Black]

Since you are recording PC video you should use the Sony Levels Computer to Studio RGB video effect to keep from crushing the blacks. This is needed when encoding to AVC (H.264) MP4 files. I don;t know about WMV. I have never used it.

Youtube re-encodes anything you send them into AVC video streams.

You get pixelation most likely because internet video streaming site are all pretty low bitrate. This works okay with most video sources and AVC can compress really well. However for a source that does not compress well quality really does suffer and there is nothing we can really do about it.

I don’t know about gameplay sources, but I do know about what I have done. Mountain bike videos with the camera mounted to the bike or helmet. This video stream do not compress well at all. The camera is constantly in motion as the bike is rolling and also bouncing around due to the bumpy trail surface. Contrast this with a stationary handheld camera filming someone riding by and I get very good quality with a source like that.

[Norman Black]

Simple. The Main Concept encoder is just plain slower than the Microsoft encoder for WMV because itd algorithms are not very fast.

In Vegas the Sony AVC encoder is faster than the Main Concept AVC encoder. Taking into account the external world the x264 AVC encoder is much faster than both Main Concept AVC and Sony AVC with higher quality as well. These are all examples targeting the same encoding format, AVC.

[Norman Black]

Probably because your source video has a range of 0-255 for color components and commonly for playback the studio RGB range 16-235 is required.

You can use the Sony Levels effect, Computer to Studio RGB preset. You can put his effect on output, track or media as required for you project and source material.

[Norman Black]

Edit Menu, Insert Time

Select the area you want to delete. Press delete. If auto ripple is off then use the appropriate post edit ripple option (edit menu).

[Norman Black]

…and they still have not fixed the problem with OpenType with postscript outlines fonts problem in Titles and Text. I reported and they said it was a known problem a couple of builds ago.

Legacy, protype and NewBlue are all okay.