Norman Black
Forum Replies Created
-
Vegas 13 does not come with NewBlue Titler Pro.
Titler Pro is always using GPU. There is no option.
The other starter pack effects included with Titler Pro have an option to use GPU or not. You find that option in the “about” button in the Video Event Effects window/pane/tab. Where the effect controls are.
It should be defaulting to use GPU, but I thought I would have you check to make sure.
Also, one thing to remember. Some effects are just slow to compute. I have no experience with the NewBlue effect you mention. I do have experience with a lot of others.
-
NewBlue does not use the OpenCL GPU interface. They use OpenGL GPU API.
Make sure the NewBlue plug-in has GPU support turned on.As for questions about NewBlue upgrades, current version and such, I suggest you contact NewBlue support. They know better than anyone here.
-
[Rene van den Bosch] “I registered specifically to answer you (and because I like the forum in general, “
This thread is over 5 years old…an answer not so topical and some might not even monitor the forum anymore.
-
[Ron Whitaker] “So, even if a media file were corrupt, and I created a subclip referencing that media file, it shouldn’t make a difference, should it?”
Vegas may try to verify a subclip on project open.
By that I mean
It opens the media file.
It seeks to the subclip start position to verify.
It seeks to the subclip end position to verify.With this Vegas can tell you about some possible errors on project open. If Vegas simply accepted a subclip specification “as is”, then you would not get an error until use.
Either way is valid. It is just a choice of implementation.
A verification process at project open could make project files with a ton of subclips take a very long time to open. Possibly making the application seem like it is stalled/hung. All this activity would have little CPU use (task manager) but heavy disk activity. If the user interface thread was the one doing the project open, then Windows can give the unresponsive message as well. Then again, Vegas could be simply hung.
-
If there is some bug/problem in Vegas then only SCS can address that.
The only thing we can do is work around any bugs and limitations the software has.
With 500+ subclips Vegas might just be taking a very long time to load. Those subclips might be something like is commonly called an N-squared operation. Double N, and the compute time goes up by a factor of 4. One can investigate that by trying 50,100,200 subclip projects and test and compare load times.
Assuming your VEG file is not corrupt; All I think of right now is to not do such a tremendously large number of subclips as it may be causing Vegas fits. Either exposing a bug or exposing a performance issue.
If the VEG file is corrupt then I am not sure there is anything you can do.
-
“not responding” means that the user interface thread in the application is waiting on some “object/handle” to become available. Windows detects that the application UI thread is not available to handle new messages and gives the not responding message to us the users.
The object/handle can be many things to technical to go into. You will likely see that Vegas is idle with no CPU use. Vegas might have some background, non user interface, threads doing something but who knows.
My guess is that something is wrong/corrupted with your file(s) and this causes Vegas to wait on some object. That object will likely never become available, due to something being amiss, but Vegas has a timeout value on the “wait”. This timeout might be a long time. When the timeout expires Vegas notices that the wait failed, and then takes appropriate actions to handle or cleanup from the problem.
-
Is your quality problem in the file rendered from Vegas or in the Youtube result. If your Vegas render is fine but the Youtube result is not as you would like then you are really out of luck. There is nothing you can do about the Youtube re-encode of what you upload.
You can upload a “perfect” video and their result will only be as good as their encoding settings are capable of.
-
[Simon Weaver] “So I have created a new project with 30FPS (actually 29.97 I think was the figure) and will render in 30FPS and will capture in 30FPS :)”
If you capture 60p and want to render 30p then pay close attention to the exact source frame rate. If the source is 59.94 then 29.97 would be the proper half rate. If the source is exactly 60, then 30 is the proper half rate. I say this since video captured from a computer screen may be 60.0 and not the NTSC 59.94.
For computer playback you don’t really care much about the precise frame rate (29.97 or 30.0). For TV playback then one needs to output NTSC or PAL whichever is appropriate.
-
[Simon Weaver] “So of course I want people to watch the videos…. YouTube offered 60FPS last year, so I was simply making them in the best format possible.”
One can say 60p is more than 30p, but more does not directly equate to best.
As for 30p vs 60p, I would render in each and watch them. If the 30p looks good at normal playback then I would use that since it put less stress on the delivery.
-
[John Rofrano] “It’s probably also important to note that the video you are trying to emulate has the person’s face large and well lit while your face is in the shadows which tend to get blurry due to lack of definition. So you might want to shine a light on your face to get better video.”
+1
Many times, the little things really can matter when one is trying to push bitrate down to internet delivery levels.