[László Kovács]

I tried, and I don’t seem to have this bug.

Windows 7 x64 Home premium / Vegas pro13 build (453)

Regards

[László Kovács]

[Nigel O'Neill] “Your recent performance hit could be due to a Windows update, but working out which one is going to be next to impossible and uninstalling/reinstalling is a trial and error exercise.”

It’s not that hard, if you find a good way to do it.
Here’s how I did:
In elevated command prompt type “wmic qfe list brief /format:csv >>d:\temp\updatelist.txt”
That puts a comma delimited txt into d:\temp\updatelist.txt with the list of installed updates.
Of course you can have this list in any txt file you like.
Then you can import this csv file into a spreadsheet (Excel or anything similar/compatible, I have Softmaker Planmaker, but Libreoffice should work as well).
In the spreadsheet you can sort the list by the date the update is installed (so that the newest comes first), and add to another column, one before the “KBxxx”, and one after it, with a special text, which is not contained by the list elsewhere. You can use “command” before, and “parameter” after. Then delete unnecessary columns, only “command” “KBxxx” and “parameter” is neededd.
Could look like this:

Then export it to antother csv, and then open this csv with a txt editor.
I like notepad++, but simple notepad will do as well.
Search and replace for “command,KB” (note, that the delimiter and KB is in the search criteria).
Replace with “wusa.exe /norestart /uninstall /kb:”.
Do another search/replace for “,parameter,,,” –> ” /quiet”.

If everything went well, now you have a txt similar to this:
wusa.exe /norestart /uninstall /kb:3138910 /quiet
wusa.exe /norestart /uninstall /kb:3135988 /quiet
wusa.exe /norestart /uninstall /kb:3139914 /quiet
wusa.exe /norestart /uninstall /kb:3135983 /quiet
wusa.exe /norestart /uninstall /kb:3134214 /quiet
wusa.exe /norestart /uninstall /kb:3127220 /quiet
wusa.exe /norestart /uninstall /kb:3126593 /quiet

(This is just an example, you’ll have much more lines.)

Save this file to any cmd, say “removeallupdates.cmd”
Now, if you start enelevated command prompt, and execute “removeallupdates.cmd”, all the installed updates will be uninstalled.
This is not what you want 🙂
Instead, break it up into smaller chunks. Cut-paste into other cmds, which you can number. 01.cmd could remove the first 10 updates (the newest), 02.cmd other 10 updates and so on.
After running a script restart windows, and see if your problem is solved.
And temporarily disable autoupdate, so you won’t get back those updates unintetionally 😉

With this method you can quickly find the group (10 updates) which contains the culprit.
Then reinstall those updates one-by one, and when your problem appears again, you know which update to remove again and hide fo forever.
Then you can reinstall the rest of the updates (reeanble autoupdate).

It’s not that hard so, at least way much easyer then uninstalling updates via control panel/remove one by one.

Kind regards

[László Kovács]

I would blame windows update.
If you have the time, try uninstalling recent updates in small groups, until the problem disappears.
I bet you’ll find the culprit somewhere in 2016 updates.
(I mysels also had problems with some of the updates)
If I’m wrong, you can still reinstall the updates.
Regards

[László Kovács]

Just as a sidenote:
In Vegas builtin creditroll it is possible adjust space between lines on the “styles” tab.

However, doing the way Steve suggested has another big advantage: it is possible to add to the credits pictures, logos, other graphical decorations, etc. which is impossible with creditroll in Vegas.
The way I did it once I needed a creditroll:
I made the whole thing with my word processor, then exported to pdf. Imported the pdf to Photoshop, added some effects and saved as transparent png.
This way it was much easyer for me to enter that lots of text, than input them right in Photoshop.

Regards

[László Kovács]

The above example nicely shows, in Vegas there’s no ultimate way to do something.
There’s always another way 🙂

[László Kovács]

Yes, I think so.
Source is progressive, so no deinterlace will be done.

[László Kovács]

You need to save your render template, if you want to reuse it later 😉

Regards

[László Kovács]

Yes, exactly.
I see, your project framerate matches the source.
Try to create a render template with a matching framerate.
And then do the render with that.
That will eliminate the ghosting effect.

Regards

[László Kovács]

Hi,
Instead of pan/crop move and scale it with track motion!
That gives you the possibility to resize to even 0 width/height.
Best regards

[László Kovács]

Hi,
Therare more ways to get this info.
1. Right click the media on your timeline, and select properties. On the “general” tab you’ll find the info.
2. In the poroject media select the file, then status bar will change to show the info about the file.

I would set up the project to match the source (or the majority of sources if there are different ones) framerate, and would render to a file with the same framerate.
If you do this, there’s no need to resample.

Regards