Aaron Star
Forum Replies Created
-
https://www.custcenter.com/app/answers/detail/a_id/918/~/what-is-wave64%3F
It was just the way they address the container, so that you can have a very large file size. The recording format you put inside it is what matters. When you can record 192Khz@24bits, the file sizes climb fast.
AC3 is a delivery format specializing in compression, multi-track delivery, and tops out at 48Khz sample rate. Basically just another audio format that specifically licensed by Dolby Labs, mainly marketing designed to ride on THX and theater sound format PR.
Unless you are referring to 32FP or 64FP(double precision) audio. With Floating Point Audio in .w64, you get 32 channels, and the audio is written in a format that does not have the range limits that 16-24bit audio does.
https://en.wikipedia.org/wiki/Audio_bit_depth
-
Here is a clue: https://www.anandtech.com/show/7764/the-nvidia-geforce-gtx-750-ti-and-gtx-750-review-maxwell/21
Sony listed the HD5770 as minimum back in on Vegas 11. Your card is well below that card with OpenCL performance, and latest cards like the r9 290x are so far past the 5770 its not even funny.
Your CPU with intel quick sync enabled would be a faster render than the GPU. That GPU is just not that great. Just edit CPU with that configuration.
Also what is your source media? There is no 60FPS, there is 59.94. So unless your source material is actually recorded true 60fps, you will be doing some conversion which will be slowing your renders down.
Not exactly sure how NVidia gets away with advertising OpenCL support when its all so bad. I think they must have a qualification driver set, then gimp the production driver to steer people at CUDA. AMD and NVidia play a mean shell game.
-
-
Vegas will work. I have windows 10 running in a VM and an old laptop. In the current build there is not that much different under the hood from Windows 8.1 that I can see. Most of what I see in Windows 10 is playing with how the UI looks and how cloud apps integrate into the UI. Windows prides itself on supporting legacy apps, especially apps as new as windows 8.1, and Sony will not let Vegas sit long with out supporting the latest OS.
-
Right click on the “A video” and “select in project media, then right click the project media and select replace. Choose the video you the “A video” to be.
-
You could try https://code.google.com/p/ffmbc/ and convert to prores. Using the audio codec copy/passthrough might get your audio channels thru. I dont really know enough about prores and whether it supports 8 audio channels, or if you will need to separate out the audio tracks. XDCAM422 has either 4 or 8 channels by spec, but they may only be using 1 and 2.
-
I think you need to decide on your final output and display. From my perspective, EX1 if you do not need 4K display at the end, or AX100 if any of your screenings are 4k capable. I think you will get better color from the 3CMOS ex1, than the single chip ax100 in the same 4:2:0 colorspace. The AX100 does include the ability to shoot slow-mo at 120fps over the EX1. The Z100 would be a 4k camera more like the ex1, with the ability to shoot at true 4K@10bit 4:2:2 intra-frame XAVC. I do not like DSLR for run and gun due to poor focus assist, unless you have full time 1st AC.
-
That is banding, generally due to not having enough steps in 8-bit video to represent the gradient transitions.
Is the source footage 60P?
Try rendering in 32-bit FP (video levels) and seeing if that helps. Unless the banding is present in the source footage.
Could also try playing back in VLC just to compare.
Could try a different codec with a default profile that matches (=) the project.
Could try rendering to XDCAM-EX or 422, use VLC to check output, then use Handbreak to render to .mp4.
-
You can have multiple versions of Vegas installed. Have you tried the trial of Vegas 13, to see if your issues still arise? Also are you using 3rd party effects, or only the Sony plugins? There is no system specs in your post, so its hard to see problem areas that you might try.
You might try the following:
Convert edit media to XDCAM-EX, XDCAM422, HDCAM-SR-LITE(only if you need the 10-bit support), or XAVC-i (list progresses in degree of difficulty for your machine.) Then try and render to SonyAVC.mp4 and MC.mp4 and compare speed differences, making sure GPU is enabled or set to auto in render profile.
Make sure all audio is PCM-uncompressed and not AC3(some camcorders record AVCHD with AC3, converting to xdcam-ex will convert audio to PCM uncompressed.)
Make sure windows is fully updated, and GPU has latest NVidia drivers.
Depending on motherboard manufacture, verify that MB has latest chipset drivers including Storage device controllers.
Use GPU-z to verify that your GPU is interfacing the motherboard at x16 and not something lower.
Use Luxmark v2 benchmark to verify that OpenCL is functioning on your configuration properly. You should be able to select rendering on CPU and GPU or individually.
Try using only Sony GPU capable plugins as a test.
Disable taskbar startup items as many has a possible during testing, including Anti-virus, re-enabling one at a time during testing.
If you are using a really old creative sound card, try removing it and using the motherboard sound card (with latest drivers) as a stability test.
For timelines with >4 video tracks where events all include 3-6 plugins, render CPU only. There are just to many variables to try and troubleshoot.
GPU does work in Vegas, but often times end users DIY hardware configs based on gaming, adobe marketing reasons, or really low end hardware configs from DELL and HP, can lead to problems. I have a theory that Vegas runs best on AMD XT GPU chips like HD5770, 7970, 290x, FPv5800, FPw9000, FPw9100. AMD has the best OpenCL performance which Vegas is using for timeline playback and rendering.
-
I would batch render all your media to xdcam-ex with a profile that matches the input media. You definitely want to get out of the .M2T wrapper. This can done by importing media with the device explorer windows, or making sure the segments are aligned with no gaps on the timeline.
Try a test project with this workflow and compare the timeline playback difference.
I made a post on batch rendering large amounts of timeline clips, where the region name gets use as the output filename. It is a pretty simple process of copying the original filename to region name in the edit details window. Then batch rendering your camera media to .mxf/xdcam-ex
https://www.sonycreativesoftware.com/forums/ShowMessage.asp?MessageID=862462