[John Rofrano]

I like to use Nested Projects to work in sections on a long project. Then I can just render them from a master project or of that doesn’t work, render each nested project to Sony MXF and combine them into a long master project. As others have pointed out, this has the advantage of only having to render a smaller section of changes need to be made.

~jr

http://www.johnrofrano.com
http://www.vasstsoftware.com

[John Rofrano]

I’m not looking to blame anyone. I’m trying to advise my customers based on the topic of this thread which is about the is FASST Apps from VASST and right now NOTHING from MAGIX works with our plug-ins so my advice is to stick with the Sony builds until extensive work can be done to get this working with what MAGIX is putting out.

~jr

http://www.johnrofrano.com
http://www.vasstsoftware.com

[John Rofrano]

[Shawn Myers] “After rendering the 30p video to the MPEG2 Blu-Ray 60i template in Vegas. You say to just author in DVDA. But what Properties setting should be used in DVDA?”

60i is the same as 29.970 interlaced. Just use that.

~jr

http://www.johnrofrano.com
http://www.vasstsoftware.com

[John Rofrano]

[Simas Chomentauskas] “I can’t believe Vegas could be missing something THAT simple: basically moving selected events to cursor (with a shortcut).”

Yup. It doesn’t exist. 🙁

Luckily, you can add this capability with a script. Here is one that I just wrote for you that will work in Sony Vegas Pro 13 and earlier:

//****************************************************************************
//* Program: SnapToCursor.cs
//* Author: John Rofrano
//* Description: This script will snap all selected events to the cursor position
//* Created: August 28, 2016
//*
//* Copyright: (c) 2016 John Rofrano. All Rights Reserved
//****************************************************************************
using System;
using System.Windows.Forms;
using Sony.Vegas;

class EntryPoint
{
public void FromVegas(Vegas vegas)
{
try
{
foreach (Track track in vegas.Project.Tracks)
{
foreach (TrackEvent trackEvent in track.Events)
{
if (trackEvent.Selected)
{
trackEvent.Start = vegas.Transport.CursorPosition;
}
}
}
}
catch (Exception e)
{
MessageBox.Show(e.Message, "Unexpected Error", MessageBoxButtons.OK, MessageBoxIcon.Stop);
}
}
}
Just copy the contents into a file called:

SnapToCursor.cs

and place it in a folder called:

.\Documents\Vegas Script Menu

and then restart Vegas Pro and use the menu item Tools | Scripting | SnapToCursor to invoke it. You can even add it as an icon on your toolbar so that it’s only one click away.

Enjoy! 😉

~jr

http://www.johnrofrano.com
http://www.vasstsoftware.com

[John Rofrano]

You’re welcome. That will probably be more effective if you sit together anyway. I don’t believe there would be any way to send the project back to Premiere for him to see even if you did edit it.

~jr

http://www.johnrofrano.com
http://www.vasstsoftware.com

[John Rofrano]

[Scott Francis] “Does this also mean that BCC, NewBlueFX and Hitfilm plugins may also not work right away with Vegas 14?”

No, it has nothing to do with DirectX or OFX plug-ins. It only affects scripts and command extensions that are built on top of Sony’s Script SDK that has now changed with MAGIX. They basically broken every script ever written for Vegas Pro because of some legal mumbo jumbo that put lawyers before customers.

~jr

http://www.johnrofrano.com
http://www.vasstsoftware.com

[John Rofrano]

[Steve Rhoden] “Amanda, Vegas 13 will still be exactly the same. Nothing gonna stop you from continuing to use it if you choose.”

Actually that’s not the case. MAGIX broke the latest build of Vegas Pro 13 because they started changing things even after they said that they wouldn’t. I’ve reported this to MAGIX and they are working on a fix. I would NOT install the MAGIX version of Vegas Pro 13 because currently it WILL NOT work with script command extension plug-ins because MAGIX started renaming Sony folders where the scripts are kept and now it can’t find them!

So I will repeat: DO NOT install the MAGIX version of any Vegas Pro 13 or 14 if you want your script plug-ins to continue to work. Stick with the Sony version (which as far as I can tell you cannot download anymore because Sony’s web site redirects you to MAGIX that doesn’t have the installers). 🙁

I hope you all kept a copy of the Sony installers.

~jr

http://www.johnrofrano.com
http://www.vasstsoftware.com

[John Rofrano]

You bring up a good point that it was NVIDIA that broke CUDA support in Vegas Pro not Sony. OpenCL has continued to work. This is why I won’t support proprietary protocols like CUDA and favor Open Source standards like OpenCL. Sony made the right choice when they backed OpenCL.

~jr

http://www.johnrofrano.com
http://www.vasstsoftware.com

[John Rofrano]

No, it will not be automatic by any stretch of the imagination. My understanding from MAGIX is that we will need to make extensive changes to get our plug-ins to work with Vegas Pro 14 because MAGIX made a lot of changes to FX names and other things that impact us. We don’t even have a beta copy to asses the impact yet so it’s a huge unknown right now.

We aren’t sure if these changes will be ready with the launch of Vegas Pro 14. My guess is that they will not be and it may take us some time to catch up. If you need our plug-ins to work you should stick with Vegas Pro 13 until we can asses the damage and make the changes and test them and republish a Vegas Pro 14 version of our plug-ins.

BTW, thanks for the kind words. We’re glad you find our plug-ins useful. 😉

~jr

http://www.johnrofrano.com
http://www.vasstsoftware.com

[John Rofrano]

Your welcome. The only caveat is that it’s not “live” as Bret pointed out. If you go back and change a setting it is not reflected in the clips that are already on the Storyline. It only affects future clips created from that media. Just something to watch out for.

~jr

http://www.johnrofrano.com
http://www.vasstsoftware.com