Norman Black
Forum Replies Created
-
You never mentioned what you were encoding to. I’ll assume you were using the Main Concept AVC OpenCL encoder.
The Main Concept OpenCL encoder does not support the new graphics core next video cars. 7xxx. You can look inside the dll and see references to previous architectures but not the new one.
Who knows what the deal is with Sony and Main Concept. Do they have a snapshot from a certain date, do they have rights to new versions and such.
Also, I can understand MC tweaking thier algorithm for optimal use on individual architectures but why not have generic code that will work on anything. Vegas is this way with the rendering video stream. Vegas “proper” does work with the new AMD video cards.
Also Sony AVC does seem to use the new video card but the Sony AVC encoder does not use the GPU much. Only form motion estimation is seems.
I have had a support ticket with Sony on this subject for months. No respose of confirm or deny with regards to newer AMD cards and the MC AVC encoder.
-
Whatever your preview setting is full, 1/2, 1/4 determines the pixels that Vegas has to process during your editing. This is keyed from the project settings. So 1/2 means 1/2 of project settings. 1/2 is 1/4 the pixels to process.
If your project settings and source files are the same size, and you are not using full for preview then you have one interpolation of the source frames to the display size.
If you preview at 1/4 but your preview window is bigger than this and you have the scale option on then that adds another interpolation per frame.
Each interpolation adds a bit of overhead.
-
IMO, the next version of Vegas will run on Windows 7. I doubt there is anything in Win8 only that Vegas wants to use.
-
Quicktime is Quicktime. Independent of Vegas. If QT has support either out of the box or via codecs installed after the fact then Vegas may be able to use that format.
XDCAM is mpeg-2 for video at specific option settings for bitrate and such. You can see in the Quicktime render as dialog in Vegas what options are available in the QT installation on your machine.
Vegas does not install any codecs into the Quicktime system. Can’t say if Sony, or anyone else, offers those anywhere. With an mpeg-2 video option in QT you can mimic XDCAM settings.
I say mimic because XDCAM is a Sony thing and never exists in a QT file, so how are you getting XDCAM files in a QT file format.
-
When in doubt, right click is often your friend.
-
Right click the track fx icon for a given track and you should see a menu giving options to disable all and enable all fx for that track.
-
Vegas 12 credit roll can import text from a file.
The help file does not appear to have been updated to explain the usage.An easy way to figure this out yourself and get “help” is to open the credit roll and save the default text to a file. Then open the file to see what was saved.
You will notice the text file has comments describing the format. Voila.
-
If QT pro can handle the file, QT pro can probably convert the file to a QT codec that Vegas can handle. Otherwise some other program to convert will be necessary. AE is an option since you have it.
-
The Avid LE codec pack only support DNxHD in Quicktime MOV files since it is a Quicktime codec pack. Same for encoding.
-
I put in a suggestion to Sony with regards to CinemaDNG.
The big problem with Sony “support” for RAW camera files is that they use the Microsoft camera codec pack. No control over raw conversion parameters. You just get a raw with the MS conversion. At least Vegas gives no control when I try my Canon CR2 raw files.
Any raw support, photo and/or video, needs to give you some control over raw conversion params, like RED raw currently in Vegas.