Aaron Star
Forum Replies Created
-
Select the 1080-24p profile, customize it to be 30P, and save it as 30p profile.
You do not want xdcam.MP4, you want to use a profile under Sony MXF > xdcam-ex. Change the 24P profile to be 30p (29.97)
Can’t help much with the Mac side of things, if that post looks complex. You could just edit everything on one or the other.
-
I think your workflow is backward.
Trim the bad stuff, and color correct in a separate VEG file.
Render all source media to XDCAM422 or EX.
Edit the converted media in a new VEG file.
smart render to XDCAM and upload to YT, or render to Sony AVC.
Working with a bunch of non optimized media sources will slow you down, and be much more unstable doing it.
Your system config could use some improvements.
Add more RAM and get it up to 32GB a processor or at least 16GB a processor. Verify your RAM is optimal for your chipset, and that there is a dimm for each of the 6 memory channels. Use “winsat mem” to gauge improvements after changes.
Lose the 560 card and replace it with a 7970-ghz, 290x or 390x. The 560 is around 1200 GFLOPs, while the 7970 is around 4300 GFLOPs. Even the R9-270x at 2600 GFLOPs would be a better performing card than the 560. The AMD cards are also more stable in Vegas over Nvidia.
-
The forum would need to know more specifics about the new and old systems to help.
-
lol. There needs to be some type of bold “this is an old ass post.” 🙂 I missed the dates.
-
I failed to see that your system was a laptop with a HD6770M, that GPU ois only capable of about 700.0 GFLOPS. The Vegas 11 recommended spec was 1300 GFLOPs. That means the 6770m does not have enough compute units to work reliably in GPU acceleration. CPU only would be my recommendation for that system.
-
The work flow I would use with that camera is just take your clips, and render them to a 1080-30p-XDCAM-EX.MFX profile. Then edit the xdcam clips, and keep the .mts around if you need them for some reason. Render your media to the same XDCAM profile. YouTube supports uploading that file directly, MP4 conversion is not needed.
So basically you would have a 3 step vegas project process.
1 – Convert to xdcam-ex, add FX and color correct if needed.
2 – Vegas edit project that matches the XDCAM format settings (match media button.)
3 – Render Edit project to Sony AVC.mp4 or XDCAM-EX.mxf, and upload directly to YouTube. XDCAM.MXF will smart render segments of edit timeline, so you gain back conversion time here.
Render profiles can be created to suit your needs, so if a format profile does not exist, create it. 1080-60P is one that is contemporary, but needs to be created under render settings. There is a customize template button in the render window.
Stay away from rendering to QuickTime formats in windows. Apple makes sure to keep their software gimped on the PC, for obvious reasons.
There is a utility available from Sony that allows FCP on the Mac the ability to edit XDCAM footage. So it is a good format for both. Of course like any religious conversation, there will be several passionate pleas for the their way of doing things. Sony AVC.MP4 @ 22-26MBS would work as well, xdcam is just more pro. DNxHD, or HDCAM-SR-Lite formats would be good as well if they are using AVID or Resolve.
-
The way OpenCL operates in Vegas and other apps, is the GPU is added to existing OpenCL compute units that are virtual on the CPU. Your CPU is only capable of hundreds of GFLOPs, while the GPU is capable of thousands. Think of the GPU as a device that can do certain math functions much faster than CPU. A good test of GPU benefit is drop a Sony Gaussian Blur on top of Sony Min and Max FX. Then do some time line playback and render tests. Straight up rendering from one MP4 to another is not going to show you much.
People have a misconception of what the GPU should be doing for them. There was another .mp4 encoder that attempted to do more with the GPU years ago, and it “loaded” up the GPU. That does not mean it is the best way to do it.
Vegas uses OpenCL (CPU+GPU) to perform tasks it can do best on the appropriate device. That might be only CPU in certain circumstances. The CPU+GPU combo can decode video, compute timeline composites and FX, then also help out with complex math in the encoder. That’s what GPU acceleration means in Vegas, not just one format to another. When you “load up” your timeline with clips and effects, you start to see how much the GPU is helping you.
The current release of Vegas best supports AMD cards. AMD does a better job of providing OpenCL performance and stability. NVidia has their own competing CUDA architecture that they would rather have app developers use.
Anandtech.com publishes Vegas performance results under the compute sections of their GPU reviews. The Luxmark test is another good benchmark test, since it utilizes the CPU and GPU combined in the same way Vegas does.
The 290X or 390X would be your best “vegas” card for a new system like yours. Vegas only supports adding one GPU to the OpenCL group, and hopefully in the future we will get multi GPU abilities. So adding a GPU with the highest Compute units you can afford is the best thing for Vegas.
The ADM Fury X has 64 compute units, while the 390x and 290x have 44 compute units. You can roughly arrive at the compute units number by dividing the stream processors by 64.
-
The system configuration looks goods. Here are a few things I would try:
Make sure Windows updates are fully installed, make sure the latest NVidia drivers are installed, and the latest audio drivers. Make sure to reboot after updating any of those components.
Make sure Vegas is fully updated to the latest version 453.
Under Vegas Options -> Preferences -> Video Tab -> hit the “default all” button, then apply and exit. Now try your render again and see if it fails.
You try rendering to another format besides .WMV, Try a test render to a Sony AVC Internet profile that matches the your video setting. Sony MXF > XDCAM-EX or XAVC-L would be good formats to try and see if they fail with the memory problem.
Pull the 560 from the computer, unless you absolutely need the extra monitor ports. The 560 is below the 1300 GFLOPs of the Vegas requirement. Vegas 11 noted the AMD 5770 as the minimum requirements, and the 5770 is around 1300 GFLOPs. The 560 is beneath that at about 1000 GLOPs, while the 760 is close to around 2500.
Pulling the second video card will also allow your 760 to run at optimal interface speed. You can check this before pulling the card with GPU-z, and hovering your mouse over the GPU interface field. There should be a popup that tells you what the interface is capable of, and what the card is operating at.
-
YouTube’s approved formats page changes like the wind. It is very likely John’s question comes from a previous posting of that same page. Page posted is not that up to date, as it has no mention support of 8K support that is active as of this post.
Try not to post rude comments to people that are just trying to help.
Your simplest YouTube upload formats to use from Vegas would be XAVC-Long.MFX or XDCAM-EX.mxf. These formats are variable and will use only the amount of bit rate needed, as well as maintain what ever quality the low bitrate AVCHD source footage has. If you are shooting with high end source material, these formats will be optimized, which YouTube will simply downgrade again to the display format.
Applying a sony levels FX, with Computer to SRGB to your render will keep YouTube from expanding your contrast.
-
Steve’s suggestion is good.
Have you tried the Media Match button on the project settings tab?
What is your source media? You can determine this with “MediaInfo” utility. You can also see a lite version by right clicking and going t to properties on some of your media in Vegas.
I noticed your project settings are at 24FPS Film, and you are rendering to a 24FPS XDCAM profile. It is unlikely you are shooting your source footage at true 24FPS, it is likely this footage is actually 23.97. Cameras like the RED, and ARRI are able to shoot at true 24FPS. Lower end cameras tend to shoot in video frame rates. Small misalignments in FPS like this can create odd video issues, as Vegas attempts to adapt footage to what you asking for.
Inexpensive cameras from Canon and others will actually shoot in something called 24PF. 24PF is 24 frames buffered in camera, then run through the AVCHD hardware codec, and written to file in 29.97 interlaced format. Since your project settings seem to be in French, the frame rate written by the codec is probably in European frame rate native to the camera. If you are confused by this, so are most that attempt to work with this footage. The 24PF mode is more marketing than actual 24P mode of operation. The media match button can help to align the project settings to the correct media format.
If you have a camera that is shooting in 24PF mode, it is best to shoot in the native interlaced mode and avoid the 24 or 30PF modes.