Norman Black
Forum Replies Created
-
Main Concept AVC and Sony AVC are both H.264. AVC = H.264
As for the other formats. If someone provides a Quicktime (MOV) or Video for Windows (AVI) codec then you could use those codecs for those file formats.
Other file formats Vegas uses it’s own code to import/encode directly, so unless Sony provides it there is no way to install something third party for support.
-
If your paragraph consists of 8 lines of text, you do exactly as I said. Set fade in to apply on a line by line basis. Fade in can operate on a letter, word, line or paragraph basis.
Example steps;
Enter your paragraph. 8 lines in your case.
Go to transistions, select the fade in transition, click and drag the fade letters preset to your paragraph.
Now change “apply to” to “line”At this point you will/may want to adjust the overlap and smoothness settings to taste.
If you have multiple columns, you have to use a paragraph for each and stagger the start point of the second paragraph fade in.
-
If you are talking about having a line at a time fade in, then use the Fade in transisition. Set apply to Line. Then maybe set overlap to 0, or just play with the params to get what you want.
The Titler transisitions can apply per letter, per word, per line or per paragraph.
-
“Sony” uses OpenCL fine, as that is what the Vegas video engine uses and only uses. No CUDA. Even Version 11 works with my new card and version 11 was before the new AMD cards came out.
The Main Concept AVC encoder is not written by Sony. Main Concept OpenCL/CUDA are pure encoders running on GPU written via software in the OpenCL/CUDA language respectively.
Sony AVC with GPU support is OpenCL for AMD and CUDA for Nvidia, and it works fine with OpenCL. However Sony AVC is not a pure OpenCL/CUDA encoder. Meaning only some items are GPU accelerated and does not get much speed boost. I believe only motion searching is accelerated. This is similar to what someone is doing in the x264 project.
Encoders in general are poor matches for GPU as increased parallelism compromises quality.
-
The Main Concept OpenCL encoder does not support the AMD 7xxx series cards so you will not see any performance difference. The encoder falls back to the CPU only encoder. I pooled others in another forum and got another reporting the same situation.
I had an AMD 5850 and the OpenCL encoder was almost 3x faster. My 7950 card gets the same results as you see.
I reported this to Sony, but for a Month now I get the runaround and no response, which is typical of their “support” from my very brief experience.
Seems like a trivial thing for QA duplicate.
-
Either leave GPU off permanently, or turn it off as needed when you have an issue.
Vegas is not 100% bad with GPU, nor is it 100% good. It is somewhere in the middle. Unfortunately that leaves people in limbo with your question. What do I do? No perfect answer.
-
I wish there was a way to use x264 in Vegas. There exists an old, no longer developed, Video for Windows codec using x264. This would give you an AVI file.
x264 is a Open source program under GPL license. This means a comercial program like Vegas cannot include x264 in its product unless Vegas itself is open source and GPL.
I am no legal expert, but I believe if Sony published the interface to the codecs in Vegas, then they should be able to provide the x264 codec so long as the source to that is released.
If that is not possible, just having the interface would allow someone write the Vegas x264 codec. I would do it if I knew what the interface to Vegas is.
If Sony could interface to a codec via a piped console program, then all we would need is to download the x264 executable and point Vegas to that. This may too complicated as it might not fit the data flow of how Vegas does things. Just throwing out possibilities.
x264 is as fast as the hardware encoders in its superfast mode at similar quality, and nothing best it in qualty when working in those modes, and we are stuck with a two step workflow to use it in Vegas. Actually other NLE’s are in the same boat as Vegas.
-
Mediacoder is using the x264 encoder which is the best encoder available for H.264 encoding at low bitrates. 2Mbps is pretty low for 720 video.
To use x264 you can generate an intermediate format, or very high bitrate some else, and use Handbrake or mediacoder to get the final low bitrate result. I use DNxHD as my intermediate and Handbrake for the output. Handbrake uses the x264 encoder also.
-
Are The fonts you are having trouble with, OpenType fonts with postscript outlines. You can tell this by looking at the font in \Windows\fonts. Double click the font to preview it and at the top of the window you will have some detail information.
Titles and Text has issues with these types of fonts. The other 3 text generators in Vegas 12 seem to work fine with these fonts.
Sony support has told me this is known and will be fixed in some future release. We shall see…
-
I looked at my system. I looked at Video for Windows and DirectShow and DirectX installs. I have installed things like Photoshop, K-lite “standard” 32-bit, Sony Movie Studio and Vegas pro.
I have K-lite installed only for movie playback of any file type out there using Media Player Classic Home Cinema which is included with K-lite.
My Sony stuff is only installed 64-bit.
Sony installs nothing into Video for Windows.
Sony installs nothing into DirectShow.
Sony installs various audio plugins into DirectX.To look for installs I first used tools that show you and let you poke around Vfw and DiectShow. I also searched the registry in the appropriate locations and generically for anything pointing to the Sony installation. Also, items copied to Windows folders (SYSTEM32, drivers, etc) were known Windows items and one VMware item.
One note. Even if an application uses VfW or DreictShow there is nothing forcing them to use some other installed codec. If the app wants to use its own is certain can ignore the system codec search. It appears Sony is doing just this for the Sony YUV type codecs listed in the Video for Windows render as dialog. They are not installed generically and other apps do not see them.
David Alfredo did some good work looking up the Sony codec DLL file loads. Thanks! Saved me the effort of starting up Vegas in my debugger.
Sony codecs are all in File IO plug-ins folder and they all appear to be using proprietary API interfaces (aka, no Vfw or DirectShow) and this jibes with the rest of what I see.
It would be nice if Sony supported DirectShow for input on unknown file types, or codecs. Then you could put an MKV on your timeline for example. As it is, unless it is AVI (VfW) or Quicktime (MOV) if Sony does not support it, it wont work…period.
Why the heck can’t VfW just die and go away. It was replaced 15 years ago with better systems.