Aaron Star
Forum Replies Created
-
Bob has a point if your GPU has not already not been tried. The k4000 has 10 compute units, the same as the older 5770, 6770. The 5770 was the minimum configuration for GPU under Vegas 11.
Compare that to:
20 compute units on the r9-270
32 on the 7970
44 on the 290x & W9100
64 on the 390 Fury Xk4000 = about 1240 Gflops Single Precision
hd5770= about 1340 Gflops Single Precision
Fury x= about 8600 Gflops Single PrecisionHD5770 in Luxmark “Room” OpenCL Benchmark = GPU-202
K4000 in Luxmark “Room” – from cgchannel.com test = GPU-137
Fury X = GPU-3565Not everything the GPU does is floating point math, but vegas does utilize both the CPU+GPU OpenCL virtual compute units.
-
Sounds like you need to clean up the Premier project before exporting to AAF.
You may need to save to a lower version of premier if possible, Vegas may not understand the very latest project files.
EDL is time honored, but has very strict requirements. EDL will get it done, but not have all the bells and whistles included, pretty much just cuts.
https://helpx.adobe.com/premiere-pro/using/exporting-projects-applications.html
-
If your final output is 720-30p. Use the scripting feature in Vegas to batch convert all your master footage to XDCAM-EX-720-29.97p. This will reduce the amount of information for multicam editing, as well as smart render, and render much faster to MP4 with either Sony AVC CBR or MainConcept VBR.
You can use the batch render stage to perform CC and other adjustments, so that editing is not bogged down with effect filters. Smart renders are almost instantaneous, if you can keep yourself from applying that one minor additional effect that defeats it.
Farm out your batch renders to another computer, or multiple PCs and write the results to a network drive.
Handbrake will also read the XDCAM final render output file for conversion to .mp4
Dump the k4000 for an AMD XT class chip like an R7-270x,7970/R9-280x, R9-290x/390x. Firepro w9000 or w9100 if you need the pro color monitoring equipment. X class cards have the most compute units and generally the best compute performance. MainConcept .mp4 encode is supposedly not supported on the newer R9 cards, however timeline effects like blurs and XDCAM encoding are accelerated. So you are looking for your GPU to speed up the computational speed of the PC, during effects where the CPU is slower at those functions. If you work in 32-bit modes, the GPU comes much more into play, as the GPU is faster at floating point math.
-
I know it may seem like a hassle, but converting all of your .MTS to XDCAM, then editing the xdcam will be a much better experience.
I believe the .MTS format is not that well optimized in Vegas, when compared to XDCAM. Also in the past I had issue with an old sound card editing MTS and AC3. Converting to XDCAM changes the audio from Dolby owned MP3 to uncompressed audio. Uncompressed PCM audio is more stable with most sound cards. I think editing MTS, you have two simultaneous decompressions going, then Vegas has to mux the result back to together on the fly. It is my believe this process has bugs in MS 11.
Have you tried the free trial of the latest release, to see if that is any better?
-
More than likely that was the instant the other side in the BG was pwning you with an exploit. 😉
You could also run some tests of converting your recorded footage to XDCAM-EX 1st, then edit the XDCAM footage. You may need to create a custom profile to match the 30p setting, vs 29.97. Media info will give you the correct stats on your recorded media. If your GPU is functional in Vegas the conversion to XDCAM should be faster than real-time.
-
One thing to keep in mind is file bitrate is overall, which includes your audio bit rate. Make sure to subtract your audio bit rate, then calculate your video bitrate.
From Vegas, I would render your finals to XDCAM-EX, then use Handbrake. Handbrake will use the best image scaler for sizes below your project setting, and a VBR codec which will minimize your storage needs.
-
Not all media players, like Windows Media player, will playback 4k codecs. VLC player is your best bet for consistent playback of a wide range of codecs.
Rendering is XAVC.MXF is pretty much your 4K codec with respects to Vegas. VLC will playback XAVC files just fine. YouTube will also accept XAVC uploads up to 128GB in size.
-
The best way to determine this is using windows Task Manager, or create performance monitor to run in the background while you edit.
Windows Key + R, then perfmon
Click the + icon, and add Logical Disk stats to the graph. Uncheck everything you do not want to see. You are most interested in %Read, %Write, Disk Queue. If you are seeing peaks of 100% on reads during editing, your disk could be holding you back. Disk Queue is another indicator that commands are stacking up and waiting on the disk to deliver.
In Task Manger some of these stats are shown as well, but perfmon allows you to record data of a large period of time.
Often times people are not held back by their disks, since most are editing AVCHD video that is generally only 4MB/s per stream. Most cheapo desktop drives from WD or Seagate can handle delivering a bunch of those streams at once.
Using a tool like Speccy, you can go into your SATA controller and verify that your drive is operating at its max interface speed, and if your SATA controller is operating in NCQ mode. If the drive is not operating at max interface speed, or NCQ, repair or upgrade this.
Normally most peoples complaints of bad editing performance in Vegas, comes from slow or not enough memory, slow CPU that does not support instructions that Vegas takes advantage of, or poor GPU compute abilities.
-
What capture card are you using?
Getting something like the Blackmagic Intensity shuttle, and then recording in MJEG to a couple of large fast drives in Raid 0 would be the way I would do this. That way you can edit the source material in high quality, then output to an .mp4 that slightly exceeds the upload recommendations.
If you can play that game on your PC, that 970 has shadowplay hardware, or using something like Mirillis action is how most do what you are trying to do.
-
Fades should go to background color, unless there is another color track below. Did you change the default background color?