[Wayne Waag]

[Simon Graham]

Really?

No, I’m just making it up. Lol. Despite what they say on their website, it does work–at least for me. Here is a screen shot showing both the media properties and project properties to be 4K, along with the Mercalli Fx window.

I don’t blame you for questioning the veracity of postings on this or any other forum. If you’re interested, suggest you download a trial and evaluate it for yourself. That’s really the best way. It may or may not work on your system. It does work on mine though, for 2.7K as well as 4K. In any case, good luck.

wwaag

[Wayne Waag]

[Steve]

You have or use a batch script Wayne?

Yes. Here is the YT tutorial.

https://www.youtube.com/watch?v=FLJ-r4jxZro

All necessary scripts are available on Dropbox.

wwaag

Some contents or functionalities here are not available due to your cookie preferences!

This happens because the functionality/content marked as “Google Youtube” uses cookies that you choosed to keep disabled. In order to view this content or use this functionality, please enable cookies: click here to open your cookie preferences.

[Wayne Waag]

[Simon Graham]

I much prefer plugins myself, however Mercalli V2 lacks 2.7k and 4k support which is kind of a deal breaker for me.

Wrong. It works just fine for both 2.7K and 4K–just tried it. The plug-in is so much easier to work with than the SAL version. In most instances, you waste a lot of time and space applying stabilization to the entire raw file. Usually, you want to stabilize only the parts on your edited timeline. You can batch render events to a lossless format from the Vegas timeline and then import into Mercalli, being careful you’re using a codec Mercalli likes. However, you’re pretty limited in what Mercalli exports, especially in V3.0. Moreover, if you’re a stickler for color accuracy, you’ll find that the colors coming out of Mercalli are slightly different from those going in. If color accuracy is important, stick with V2.1 SAL which also provides a lot more export options. OTOH if your footage has a lot of movement and CMOS distortion, the V4.0 SAL works extremely well, although its pretty slow.

IMHO, stick with the V2 plug-in unless your footage has a lot of CMOS distortion and then use V4.0 only for those problem clips. For anyone interested, there is also a way to apply the V2 plug-in in a batch fashion.

wwaag

[Wayne Waag]

I agree with Steve. Have you rendered this source video and the audio still came up out of sync? It sounds as if you’re basing this on preview performance. I don’t think it’s valid to compare Vegas “preview” with VLC “playing” performance. If your rendered video is indeed 4 frame off, then you can do what Danny suggests.

wwaag

[Wayne Waag]

It is still pretty clear offline and looks very good quality aside from the colouring issue however, after uploading to YouTube it is becoming blurred.

If your rendered file looks OK, but your YT is blurred, then it’s most likely a YT encoding issue that you have no control over.

They recommend avc h264 which I’m not sure how to get in Sony Vegas.

If you render to an MP4 using either the Mainconcept or Sony templates, that is avc h264.

So, it sounds like its mostly a YT problem. I notice that your YT file is 60P. You might try rendering to 30P (make sure you disable smart resampling) and trying another upload. (you could render just a loop region around one of the problem areas).

wwaag

[Wayne Waag]

[Edward]

The screen shots are really good. Too bad that others often don’t give such detailed info. I looked at the YT video and can see where it really becomes pixelated. I gather that the original footage has no such blurring?

Here are a couple of things I noticed. First, in your project properties, you have rendering quality set to Good. That should be changed to Best. Hopefully, that’s the problem. Second, in your two photos (Original/MP4), the differences are most likely due to a levels problem. Suggest you bring up the histogram display to determine the levels of your original avi footage. If its 0-255 or full-scale, you should apply a Computer RGB to Studio RGB conversion. I usually apply this on the output bus.

I can’t really comment on your MP4 render settings since I usually use Handbrake for encoding or Sony AVC directly from Vegas. Same for your WMV settings.

wwaag

[Wayne Waag]

Edward. You need to provide a lot more information. First, your avi files (frame size/frame rate, codec, interlaced/progressive, etc.). Second, your project setting (frame size/frame rate, etc.). There is no reason that you cannot get a reasonable MP4 render. If your rendered files are pixelated, it’s most likely due to your settings. An avi file is not considered a delivery format. Screen shots of file and project information as well as a screen shot of your timeline would be most helpful.

wwaag

[Wayne Waag]

Mike, Steve

Thanks a lot for your replies. Since I use Vegasaur, that seems the easiest. Quite frankly, this doesn’t happen very often. In fact, I can’t remember the last time. Sadly, the next time it does occur, I probably will have forgotten how to do it. There’s not much to be said for getting older.

wwaag

[Wayne Waag]

[John] You said, (do not use 2.6 use 2.5)

Just curious. What’s wrong with 2.6?

wwaag

[Wayne Waag]

Mike, Steve. Glad I was wrong when I said “Don’t think so”. That’s a very useful tip. Let me ask another question. If you have an edited clip on the timeline that you’ve added without the audio, can you later add the audio track, keeping it in sync with the video track that’s already been sliced up?

wwaag