Aaron Star
Forum Replies Created
-
Aaron Star
August 15, 2015 at 10:54 pm in reply to: Does Vegas 13 fix the GPU acceleration failed rendering?There is no reason why you cannot run both versions on the same machine. Why not run the trail version of VP13 and see for yourself if the stability is better? Then report back the results.
The R9 270x is only about 150.00 which will support the GPU features in Vegas, and is comparable in hardware specs to the 770. Which also gives a certain view into where the 770 sits, the AMD 6970 had similar specs to the 770 back in 2010. The NV700 series was released in 2013. Nvidia just has a better sales and marketing graphic departments working for them.
-
Aaron Star
August 13, 2015 at 7:08 pm in reply to: A few questions re: proxy editing, large video/project, and a weird blac preview screen problem (Windows PC – Vegas Pro 12)You know there is almost no difference between all these manufacturer codecs in the end. Each proprietary codec is based on the same codecs the others are using, each with their own MPEG-LA licensing. Most differences people see in using the various codecs is generated from converting signals inside a workflow of their own insanity. It takes high end Pro tools that look at the signal differences, and artifacts to make comparisons. The artifacts people see themselves are generally created by their own work on the signal converting.
If you work in Vegas as a primary tool, converting all your master footage to .MXF is your best bet. Then convert your .MXF output to whatever you want via FFMPEG, or use the integrated Sony AVC encoder at 10Mbs+.
Handbrake is pretty much just a FFMPEG front end tool that focuses on one task. This is evident based on the terminology used in quality settings inside handbrake.
I guess I feel like getting the smallest file was more of an 1997-2005 issue, these days file size is not that big of a concern to me. The streaming services all convert your footage to something below 10Mbs-HD. If you stream your own stuff you are going to render multiple stream sizes down to postage stamp sizes. If you are going to DCP, then your file sizes are going to be appropriate for that format.
-
I would play around with how CC works in vegas, read the help file and what not. CC can be toggled off and on, but the player that is embedded into the powerpoint, how the video is embedded in powerpoint will determine how this works.
CC can be embedded into come codecs (generally broadcast codecs)then all you need is the right player that understands that codec.
YouTube embeddeding will allow toggleing the CC, but YouTube does this different. YouTube shows you the mp4/VP8 video on screen, then has a player that pulls the CC when needed from a separate source and syncs it on top of the video playback. YouTube’s implementation of CC creation is very good, and you download the CC you create as a file when done for use in other applications like DVDA. YouTube videos can be set to unlisted or private, so as not to be publicly available.
So all this really depends on how you plan on showing the presentation. Embedding YouTube into PowerPoint is something I would try, and see if that allows you to do what you want.
-
There is a triangle that needs to be optimized on any given system. This is the triangle of CPU, Memory/RAM, and GPU.
CPU should be the fastest for your Chipset. AMD and Intel make different chipsets, and lately Intel has pretty much released a new chipset with each processor that can not be interchanged. Intel chipset/CPU holds the speed title as far as rendering goes.
GPU should be interface compatible with the motherboard. That means you could be holding back a motherboard that supports PCIe3.0 with a PCIe2.0 card. You could also be holding back a new FURY X with some old motherboard that cannot keep up. Keep the generation of hardware roughly the same. PCIe3.0 has a much improved communication ability, which equates to lower latency, which means more operations per second.
Memory/RAM – should be the max stable Profile that you chipset supports. You can google intel chipset block diagram that will show the memory speed the motherboard was designed for. Overclocking memory can be done, but you run the risk of not knowing how many errors the memory channel is compensating for. Running the max memory profile the chipset is designed for is the best. Memory also comes in different speed timings, this should be optimized as well, but I prefer more slower memory over the fastest timing. 32-64Gb is a good size for todays video editing, as windows will use the remaining memory for disk cache. Information is always faster from cache memory than pulling from HDD or SSD.
Harddisk speeds factor, but not as great when it comes to rendering. Years ago hard drives might not have been able to keep up, but todays HHD are much faster.
AnandTech.com has a Compute section of their review of Video Cards. This Review of the r9 Fury is an example of one of the latest cards released.
https://www.anandtech.com/show/9421/the-amd-radeon-r9-fury-review-feat-sapphire-asus/16
The problem with this result is that the Vegas Test File used does not “Load Up” the system with the true compute power a card like the R9-390 Fury is capable of. Running the same test in 32-bit Full Levels would be a better test of these cards.
Luxmark V2 or V3 is a good benchmark of OpenCL performance, and if you look at the results comparison, you will see that this benchmark has a similar result standing to the Vegas test file. Vegas uses OpenCL devices from the virtual CPU device + the GPU device. Compute cores or “Stream Processors” are like the “cores” on a CPU. The more Compute cores a GPU device has the better at OpenCL calculations generally the card is.
AMD cards at the moment perform the best at OpenCL calculations. The Luxmark site has a ranking board that can be sorted by Single CPU+GPU. While Luxmark will use multiple GPUs, Vegas will only use 2 devices, one of which is the virtual device on your CPU. That leaves choosing the best performing OpenCL card you can afford.
Nvidia states OpenCL compatibility, but the test results tend to indicate some sort of bias towards their Propritary OpenCL standard called CUDA. It is hard to tell if NVidia is gimping drivers to lean people toward CUDA, or if their hardware is just less than AMD at OpenCL standard.
-
Aaron Star
August 12, 2015 at 8:53 am in reply to: Want to put butterfly coming out of broke guys wallet.Find a butterfly in PNG with Alpha like this one:

Cut the image into slices with Photoshop, then animate the layers with Pan/crop key framing in vegas. If the image is to large to scale properly in Vegas, reduce the size before importing into Vegas.
-
Yeah. You want to keep that RAM preview at the default, unless you are using crtl+B in your editing workflow.
From what I can tell from a far, the fact that you are close to 1:1 rendering speed and doing so at with 60P material is pretty good. Most people at that are claiming faster than real-time renders are doing that on 29.97 material. With 60P you are rendering 2x the frames and doing that in almost 1:1 time.
Your hardware choice is geared more for Premier, so maybe that is the better choice for you.
-
There is not enough information on the details of what you are trying to do. Source Media info, project size settings, render codecs tried.
-
I posted this on the Sony forum awhile ago:
Here is a modified version of the default Sony Batch script. This script uses the Region Name as the output file name. Copy the script below to a new text file, change the extension to .cs, and move to your programs/sony/vegas13/script folder. Use what ever name you want to describe it.
I use this script to convert camera .mts and .mov to XDCAM or other editing intermediate files. I like to keep the camera original files around incase there is a need to re-render from individual files. You can also use this to create proxies of your footage in any format you choose. Here is how I use the script:
1 – insert all the files you want to batch on the the timeline
2 – execute the default Sony script that inserts regions around the timeline events.
3 – using the “edit details” windows in vegas, copy and paste the “active take name” column into the Region “name” column.
4 – execute the script below, the GUI will popup, set for Regions, select output template, and use the default base name. the script will ignore the default base name, and use the region name for the output file name. The output template you select will determine the .xyz extension. You can select multiple formats that have different extensions.
Basically you just cut and paste the following into a .txt file, rename the extension .cs, and place the file into your script folder. Start vegas and you will see the new script under Tools> Scripting. This will turn Vegas into a large batch render tool.
Here is a link to a zip file with the 2 scripts, drop them into your vegas script folder.
https://www.astardp.com/techtips/Vegas-Region-Batch.zip
Code Block:
/**
* Sample script that performs batch renders with GUI for selecting
* render templates.
*
* This script has been modified to batch render the region names to the new file, and not the default render template.
*
* Revision Date: 8-27-14.
**/
using System;
using System.IO;
using System.Text;
using System.Drawing;
using System.Collections;
using System.Collections.Generic;
using System.Diagnostics;
using System.Windows.Forms;using Sony.Vegas;
public class EntryPoint {
// set this to true if you want to allow files to be overwritten
bool OverwriteExistingFiles = false;String defaultBasePath = "Untitled_";
const int QUICKTIME_MAX_FILE_NAME_LENGTH = 55;Sony.Vegas.Vegas myVegas = null;
enum RenderMode
{
Project = 0,
Selection,
Regions,
}ArrayList SelectedTemplates = new ArrayList();
public void FromVegas(Vegas vegas)
{
myVegas = vegas;String projectPath = myVegas.Project.FilePath;
if (String.IsNullOrEmpty(projectPath))
{
String dir = System.Environment.GetFolderPath(System.Environment.SpecialFolder.MyDocuments);
defaultBasePath = Path.Combine(dir, defaultBasePath);
}
else
{
String dir = Path.GetDirectoryName(projectPath);
String fileName = Path.GetFileNameWithoutExtension(projectPath);
defaultBasePath = Path.Combine(dir, fileName + "_");
}DialogResult result = ShowBatchRenderDialog();
myVegas.UpdateUI();
if (DialogResult.OK == result)
{
// inform the user of some special failure cases
String outputFilePath = FileNameBox.Text;
RenderMode renderMode = RenderMode.Project;
if (RenderRegionsButton.Checked)
{
renderMode = RenderMode.Regions;
}
else if (RenderSelectionButton.Checked)
{
renderMode = RenderMode.Selection;
}
DoBatchRender(SelectedTemplates, outputFilePath, renderMode);
}
}void DoBatchRender(ArrayList selectedTemplates, String basePath, RenderMode renderMode)
{
String outputDirectory = Path.GetDirectoryName(basePath);
String baseFileName = Path.GetFileName(basePath);// make sure templates are selected
if ((null == selectedTemplates) || (0 == selectedTemplates.Count))
throw new ApplicationException("No render templates selected.");// make sure the output directory exists
if (!Directory.Exists(outputDirectory))
throw new ApplicationException("The output directory does not exist.");List
-
The eye dropper seems to work close enough for the girls I go with.
-
Can you post a 5 sec stop start of this capture you are doing? Maybe post a media info display on your source media?
One more thing to try is to put Vegas into CPU only mode, change your project settings to 29.97 progressive, then use Sony AVC and set the encoder type to Intel Quicksync speed. Then Test QS quality. Then may be try enabling the GPU in preferences again, and try renders again with Quick Sync in Sony AVC. I would just like to know the stats on this, as the Gen4 I7 supports this function. You need to restart Vegas each time you change the preferences GPU setting, not the render as settings.
This guy does a good job of explaining it:
https://www.youtube.com/watch?v=0BTx4qfBpdASome contents or functionalities here are not available due to your cookie preferences!This happens because the functionality/content marked as “Google Youtube” uses cookies that you choosed to keep disabled. In order to view this content or use this functionality, please enable cookies: click here to open your cookie preferences.