-
VideoYesterday
External Monitor Overlap
Is there a file in Vegas 14 that I can transfer to Vegas 12? No.
-
ScriptingYesterday
C# plugins stopped working in latest Vegas Pro 20 build
I'd try removing the files you copied, uninstall VEGAS, and then reinstall VEGAS. There's definitely something odd with your VEGAS installation at this point.
-
ScriptingYesterday
C# plugins stopped working in latest Vegas Pro 20 build
I've had every build of VEGAS Pro 20 and this has not been an issue.
-
ScriptingYesterday
C# plugins stopped working in latest Vegas Pro 20 build
I didn't see any "Using" statements in your script. You do NOT need to copy those other files to the script menu folder. All scripts and custom commands are working just fine in all versions of VEGAS here without copying any of those files.
-
VideoYesterday
⭐Flow for VEGAS Pro (Extension for animations based on bezier curves)⭐
@Mindmatter please show some screenshots of what you've placed where. If you put the DLL files into the [My Documents]\Vegas Application Extensions then it should load fine. Having said that, I haven't tried that specific custom command - just going by the ones I've written.
-
VideoYesterday
⭐Flow for VEGAS Pro (Extension for animations based on bezier curves)⭐
Pan/crop tool is the most confusing tool (for beginners) in Vegas, I hardly use it anymore. I think it will become a deprecated feature one day. I certainly hope not! I use it on MOST of the videos I do. Not confusing at all. It allows you to CROP just the portion of the video you want to use and also PAN across the video. Hence the name Pan/Crop! I think people are more confused with Track Motion than Pan/Crop. The new PIP effect is really more of a replacement for Track Motion than Pan/Crop. And, yes, Pan/Crop uses the full resolution of the image/video where Track Motion does not. I'm not totally sure where effects fall on using the resolution. It could be that if placed before Pan/Crop they use the full resolution but if placed after they do not...
-
ScriptingYesterday
📝⚙️(Script) Add Picture-in-Picture to the event.
@relaxvideo I did not test the code - only reworking what you had already written. The number in the parentheses tells you which line the error is on. So your first error is on line 28. It appears line 28 is: OFXEffect ofx = effect.OFXEffect; So the big question is: Is the effect you're adding an OFX Effect? It appears that answer is yes for "Stereoscopic 3D Adjust". This: OFXEffect ofx = effect.OFXEffect; foreach (OFXParameter parm in ofx.OFXParameters) { if (parm.ParameterType.ToString() == "PushButton") { parm.ParameterChanged(); } } should really be (As you should really be verifying it is an OFX Effect before trying to get the OFXEffect variable): if (effect.PlugIn.IsOFX) { OFXEffect ofx = effect.OFXEffect; foreach (OFXParameter parm in ofx.Parameters) { if (parm.ParameterType.ToString() == "PushButton") { parm.ParameterChanged(); } } } Now, all my code is written in C# and you're doing .JS so some other changes are needed to make sure everything works. Then, on line 29, .JS does not like the "For Each" loop. Changing to this will eliminate the above errors: import Sony.Vegas; import System.Windows.Forms; import Microsoft.Win32; var plugInName = "Stereoscopic 3D Adjust"; var presetName = ""; try { for (var track in Vegas.Project.Tracks) { for (var evnt in track.Events) { if (!evnt.Selected || evnt.MediaType != MediaType.Video) continue; var fx = Vegas.VideoFX; var plugIn = fx.GetChildByName(plugInName); if (null == plugIn) { throw "could not find a plug-in named: '" + plugInName + "'"; } var effect = new Effect(plugIn); evnt.Effects.Add(effect); if (null != presetName) { effect.Preset = presetName; } var ofx = effect.OFXEffect; for (var parm in ofx.Parameters) { if (parm.ParameterType.ToString() == "PushButton") { parm.ParameterChanged(); } } } } } catch (errorMsg) { MessageBox.Show(errorMsg, "Error", MessageBoxButtons.OK, MessageBoxIcon.Exclamation); }
-
Scriptingon 3/24/2023
📝⚙️(Script) Add Picture-in-Picture to the event.
@relaxvideo Well... you don't need to go through the list of effects because you just added the effect you want to look at. Turns out that var effect = new Effect(plugIn); and foreach (Effect effect were both creating the "effect" variable. Therefore, you were getting an error because the same variable was being defined twice in the same scope. But you don't need it anyway - just use the initial "effect" variable and get rid of the foreach loop looking at the effects list. import Sony.Vegas; import System.Windows.Forms; import Microsoft.Win32; var plugInName = "Stereoscopic 3D Adjust"; var presetName = ""; try { for (var track in Vegas.Project.Tracks) { for (var evnt in track.Events) { if (!evnt.Selected || evnt.MediaType != MediaType.Video) continue; var fx = Vegas.VideoFX; var plugIn = fx.GetChildByName(plugInName); if (null == plugIn) { throw "could not find a plug-in named: '" + plugInName + "'"; } var effect = new Effect(plugIn); evnt.Effects.Add(effect); if (null != presetName) { effect.Preset = presetName; } OFXEffect ofx = effect.OFXEffect; foreach (OFXParameter parm in ofx.OFXParameters) { if (parm.ParameterType.ToString() == "PushButton") { parm.ParameterChanged(); } } } } } catch (errorMsg) { MessageBox.Show(errorMsg, "Error", MessageBoxButtons.OK, MessageBoxIcon.Exclamation); }
-
Scriptingon 3/24/2023
📝⚙️(Script) Add Picture-in-Picture to the event.
@relaxvideo I just realized, you have incorrect code there! foreach (Effect effect in evnt.Effects) { OFXEffect ofx = effect.OFXEffect; foreach (OFXParameter parm in ofx.OFXParameters) { if (parm.ParameterType.ToString() == "PushButton") { parm.ParameterChanged(); } } } You have to be looking at the OFXEffect and the OFXParameters.
-
Scriptingon 3/24/2023
📝⚙️(Script) Add Picture-in-Picture to the event.
OFX was added in Vegas 10 so, it might work in Vegas 11. However, I don't know exactly when all of the API calls were added. I do know that the ".ParameterChanged();" call was available at that time. I cannot say whether or not it worked for the "push button" parameter.
-
Videoon 3/24/2023
⭐Flow for VEGAS Pro (Extension for animations based on bezier curves)⭐
@Reyfox I don't either. But in Windows 11, that's where the "true" [My Documents] folder is located - even though there's still a folder with the same name listed under [user name]. So that's actually an error in his installation documentation. That used to be correct - until "one drive" happened. Now you have to literally specify: [My Documents]\Vegas Application Extensions
-
Videoon 3/24/2023
⭐Flow for VEGAS Pro (Extension for animations based on bezier curves)⭐
To confirm, you're adding the folder into "My Documents" - wherever that happens to be. If you're on Windows 11, there's a differences between [user name]\Documents (which won't be seen by VEGAS) and [user name]\OneDrive\Documents (which will be seen by VEGAS) That's why I always say to put custom commands in: [My Documents]\Vegas Application Extensions and regular scripts in: [My Documents]\Vegas Script Menu
-
Videoon 3/24/2023
⭐Flow for VEGAS Pro (Extension for animations based on bezier curves)⭐
I had wondered if he had built that based off of my tutorials. If he did - GREAT! The functionality looks very similar. The interface is cleaner but my purpose was to show the process, not make a perfect interface.
-
Videoon 3/23/2023
Vegas Pro with Newblue Pro Titler?
I'm sure this would be "Titler Pro 7 Basic" and not "Titler Pro 7 Ultimate" so it would have fewer templates.
-
Videoon 3/23/2023
Vegas Pro with Newblue Pro Titler?
Currently listed in the HUB.
-
Videoon 3/23/2023
GL Transitions always crash program (Solved)
@Bill-Maries, are you going to try the OLDER video driver? Version 522.3?
-
Videoon 3/23/2023
Request: Shift+B should work everytime
It appears Shift+B is under every category EXCEPT "Explorer" and "Global" in Options - Customize Keyboard. I suppose you could add it to "Global" and it would then work as you desired.
-
Videoon 3/23/2023
GL Transitions always crash program (Solved)
You probably DON'T want the "latest" driver. Try driver 522.3.
-
Videoon 3/23/2023
Having major trouble with NewBlue Titler 7 Pro
Here's the difference between the Media Generator and VideoFX and Standalone: The Media Generator version gets added as a new event on the timeline allowing you to easily adjust the length of the event and place it over one or more media events. The VideoFX version gets added as an EFFECT. This will limit it to the scope of the effect. If you add it on an event on the timeline, it is limited to that event. It DOES have the advantage of being able to show the underlying video in the Titler Pro timelilne. However, if you were to drag the VideoFX to a track like you would the generated media, it will apply as an EFFECT to that TRACK - probably not what you want. Both Media Generator and VideoFX will automatically open the Titler Pro 7 interface. This is NOT the "standalone" version although the interface will look the same as the standalone version. Once the changes to the title are made, you simply need to close the Titler Pro interface and confirm you want to keep the changes. To open the "standalone version", you simply need to run Titler Pro outside of your NLE. You can do that by using the Titler Pro 7 icon or open the App Manager and clicking on Titler Pro or TotalFX there. When Titler Pro is open in standalone mode, you can still create titles but will need to save them as a .nbtitle file. Once back in your NLE, add Titler Pro to the timeline and you can then open that .nbtitle file to add it to your timeline. You cannot open a .nbtitle file direct on the timeline.
-
Videoon 3/23/2023
Having major trouble with NewBlue Titler 7 Pro
@Ardat, it all depends on what's "inside" the MOV file. MOV is like a paper sack, you can put many different things in it. But what it contains determines what is needed read the file. In the case of PNG Sequence files, Quicktime is required and, to use Quicktime, it must be turned on in the deprecated features. To read a ProRes MOV file, VEGAS will read that natively so nothing else needs to be turned on. The stock footage you are using must be using a format that VEGAS can read natively without needing Quicktime. The same is true with other file formats. AVI, MP4, etc... can contain many different formats of files. That's why if someone says a file can't be read, the next question is - what's in the file? And if they answer "It's an MP4 file", that doesn't answer the question.
-
Audioon 3/23/2023
Multitrack Audio Mp4
Import stereo as dual mono
-
Videoon 3/23/2023
GL Transitions always crash program (Solved)
You haven't said what video driver you have installed. OpenGL is a Windows component.
-
Videoon 3/22/2023
Having major trouble with NewBlue Titler 7 Pro
You should be able to open VEGAS, drop the Titler Pro 7 Generated Media, on the timeline, and then do full title creation there and it play on the timeline. There's no need to render out. If you do render from Titler Pro, it creates a PNG Sequence MOV file. To get VEGAS to read that, you have to install QuickTime and turn Quicktime back on in the deprecated features. It's really recommended that you use it directly on the VEGAS timeline.
-
Audioon 3/22/2023
Multitrack Audio Mp4
That's the standard way 5.1 audio is imported: Channels 1 & 2 as a stereo track Channel 3 as a mono track Channel 4 as a mono track Channels 5 & 6 as a stereo track And that's what I had to replicate in my current tutorial:
jetdv
Offline, Last login 3/26/2023, Member since 8/23/2016