[Wayne Waag]

Because one doesn’t do the editing in Handbrake that you do in Vegas guys!!

Not every video is straight from raw footage to MP4 finished edit.

Surprised you guys didn’t realize that!

I think its YOU that has a very basic misunderstanding. You DO the editing in Vegas as always, but RENDER in Handbrake rather than using either Mainconcept or Sony AVC–simple as that.

wwaag

[Wayne Waag]

If I run them through Handbrake, they work fine.

If Handbrake works, why not use it? It’s a much better encoder than MC, especially at low bit rates. You can do 2 pass encoding as well. There is even a script that permits one-click rendering from Vegas. https://www.vegasvideo.de/vegas-2-handbrake-en

wwaag

[Wayne Waag]

Easiest thing is to make sure in your preferences that the entry “Double click on media file loads into Trimmer instead of tracks” is unchecked. If you set Auto-ripple to “on”, then the file will be placed on the timeline at the cursor whenever the file is double-clicked. But as Mark warned, be very careful of keeping auto-ripple on past your initial cuts editing. I know from sad experience that it can really mess things up.

wwaag

[Wayne Waag]

I can tell you for a fact that Mercalli does not work with Vegas12.

Could you spell out exactly what you mean by “does not work”? Does that mean the effect doesn’t show up and you can’t even try it? or does it mean, that the results are terrible?

wwaag

[Wayne Waag]

but should I change that to 25Mb or something in the middle or closer to my a7s’ 50Mb?

The higher the bit rate the better, although you have to weigh that against the time to upload and the time YT takes to process. Many of us are stuck with relatively low upload speed (mine is 6 Mbps), so I try to minimize bit rate. For lower bit rate renders, there are better encoders, notably Handbrake. Here is a link to an excellent tutorial on using Handbrake for Youtube. https://www.youtube.com/watch?v=rWMX5lSvEgY There is also a script available that permits Handbrake renders directly from Vegas without an intermediate. https://www.vegasvideo.de/vegas-2-handbrake-en It takes some time to set up, but is well worth the effort. The consensus seems to be that Handbrake is much better for lower bit rate renders. However, at higher bit rates it really doesn’t make that much of a difference.

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]

Wondering if Wayne has Vegas 12 and 13 installed together why it works in Vegas 12 for him.

Maybe yes. Maybe no. I do have both installed, but can’t imagine how one would effect the other. I’ve just done test renders in V12, but it seemed as responsive as V13. If there is really concern, perhaps someone should send an e-mail to ProDAD with that question. When Mercalli 4 was released, I sent an email complaining about the lack of a batch process. I promptly received a fix, which I presume has been incorporated in later releases. On the other hand, as I suggested before–just try it.

wwaag

[Wayne Waag]

Perhaps I don’t understand what you are trying to do, but I think it is “keep frame one, remove the next six, move remaining frames left, keep next frame, remove the next six, etc.” If that is correct, then the two methods suggested do exactly that.

In any case, Vegas pro does support scripting. You can download the Vegas Pro SDK here https://www.sonycreativesoftware.com/download/devkits There is also a scripting forum here that can provide assistance. https://www.sonycreativesoftware.com/forums/showtopics.asp?forumid=21 If you get it to work, please share. Good luck.

wwaag

[Wayne Waag]

Because of file size?

Exactly. You want to have the best quality in the smallest file size. Unless you are fortunate to have a “super-fast” upload capability, this becomes a necessity.

wwaag

[Wayne Waag]

Is there a specific reason you are editing lossless, vs using xavc-intra, hdcam, or cineform?

The problem is that he using Virtualdub to render so the Sony codecs won’t work. Cineform does work, although I’ve had problems maintaining color accuracy when going from Vegas to Virtualdub and back. Plus, for me at least, Cineform seems to be more prone to the “black clip” problem and more importantly, it does NOT smart render, unlike other codecs such as MagicYUV or UTVideo.

wwaag

[Wayne Waag]

If you’re happy with the workflow you described, then do it that way–that’s really all that matters. However, you asked the question “will there be a loss in quality” and the answer is still yes. You start with camera footage recorded at 50 mbps, stabilize, do color correction, and then render at 12 mbps. While there is no problem with doing a project in stages (I do it all the time), I suspect that most editors would agree that the initial render should be to a digital intermediate format and not a final delivery format. I like using XAVC S as an intermediate since it maintains a relatively high bit rate (60 mbps) and doesn’t create large file sizes so its suitable for archiving as well. Others prefer using a lossless codec. While you certainly CAN use a 12 mbps delivery format as your intermediate, once you do further color correction and effects processing, there WILL be additional loss of quality. Whether you can “see” that loss or it’s meaningful is a question only you can answer. If it seems OK to you, then you’ve answered your own question.

wwaag