Aaron Star
Forum Replies Created
-
“dynamic ram max MB to 1000, with a maximum of 7128 available ” – Reduce this back to the default setting of 200. If you are using RAM preview during editing, then enable the 1024 (8-bit memory format) only during editing. Windows uses extra ram for caching operations, and dynamic preview frames are not used during render. You can slow your machine down by disabling D-Ram preview altogether setting it to 0, so use the default. Vegas uses some aspect of the default settings for frame buffering or something.
16GB is a good recommendation. The rule of thumb is 4-8GB per CPU core, and the more the better.
Your media does look suspect with the odd frame rate. You might try changing your project settings to 29.97 FPS. You can also try not rendeing in BEST FULL, and change your render profile to render in GOOD. If you are capturing game footage, use XSplit over OBS, as xsplit records constant frame rate video. If not, the suggestion of running it through handbrake is a good one.
Here is a way to get media info on your media details:
https://www.vegascreativesoftware.info/us/proxy/3aa8d068d6ee911c0a37/?link=https%253A%252F%252Fwww.vegascreativesoftware.info%252Fus%252Fforum%252Ffaq-how-to-post-mediainfo-and-file-properties–104561%252FYour GPU is not a terrible one, but AMD would be better suited for Vegas. You might try turning off all the CUDA settings in preferences, and render formats. Then enable the GPU under preferences Video Tab, then choose encode mode: AUTO in the render profile. Try a Sony AVC profile with bit rate set at 25Mbs, and audio at AAC 384, and enable progressive download.
An alternative would be to get a Blackmagic intensity shuttle, then record your game footage on that device. You basically use another HDMI cable from your PC and clone your display. Recording the 2nd display. Then take that footage and edit it on the timeline. This will look better and be recorded in a video standard format.
Knowing more about your actual system specs would be helpful too. Download a copy of “SPECCY,” then Save As .TEXT file, and post the resulting Summary section at the top to the forum.
-
No they won’t lose sharpness. The tapes might develop dropouts though which will in turn lead to video corruption.
-
I think you need to think in terms of workflow. Vegas is an “editor” that maxes out at 4096 x4096 resolution. 4K DCP is 4096×2160 as a display format. You can drop RED files on the timeline that are 6K, but vegas will scale that down to 4096×2160. For color and resolution shifts, you would do that in REDCINE or some other CC program with the color profiles you need. Then convert that footage to a format that Vegas edits well. If you want to use Vegas to edit that type of footage.
An EXR / proxy workflow is the best that vegas supports for RED level footage. EXR is pure floating point, and so most users machines are under powered to turn the media type. This is my belief as to why EXR has not caught on more.
-
I will be interesting to see what you choose to do.
If your Vegas version was newer, ProRes might be a good option. Since D2 is basically REC601 at 720×480 lines (in today’s terms) at 422 color (60Mbs.) I would look at Cineform in an AVI format, or HDCAM SR or SR-Lite422.mxf ( this is basically the HD prores for sony Vegas.) You want an intra frame format. If you go with something like HDCAM, you would be upscaling the image to HD.
Standard DV codec is the most supported at basically half that rate (25mbs,) by dropping the color down to color info down to 4:1:1. DVCPRO50 or HD was the digital file format that fit D2 the closest. Most people working with high end video sources back in the D2 days were converting to AVID AVR, so there was not really much need for high end “DV” codec.
The suggestions above are newer formats, but not prores new. Might be time to upgrade from V10.
-
You should head over to https://www.vegascreativesoftware.info/us/news-forum/ and read some of the FAQs. Then post info your media and system specs.
-
Sony AX100 has a fairly large sensor, UHD@100Mbs codec, and focus ring/multi ring.
Add a ECM-AW4 wireless mic, or XRL adapter.or
Samsung Galaxy 6S or newer, plus a mophie case for extended battery. (UHD @ 50Mbs codec)
Multi face focus tracking, tap to select track.
Turn off OIS, unless you like the look.
Add an AC3200 router for offloading images to laptop or other storage via network file copy, or just use the USB cable.
Selfie-stick a must. -
If you have properly setup workstation that is previewing 4K content (4k display in Best/Full) and your content looks sharp there, you need to determine where the media is being degraded.
https://www.google.com/search?q=youtube+bit+rates&oq=youtube+bit+rates&aqs=chrome..69i57j0l5.3247j0j7&sourceid=chrome&ie=UTF-8
Recommended upload encoding settings – YouTube Help
https://support.google.com/youtube/answer/1722171?hl=enThe poster is not showing his workflow from camera to posting file.
Basically you want to make sure you are not scaling in any manner with your project settings, make sure your effects, and track effects are not de-resing your footage in someway. Then render to a media format that is roughly 2x the bit rate that YouTube is steaming at. Sometimes this might need to be more for fast action or cuts. YouTube re-encodes your media to the basic bit rate shown above, so giving them more to throw away helps maximize youtube encoder.
Some of the sharpest HD and 4K content on Youtube mainly comes from an intra-frame workflow from beginning to end. Then they upload an intermediate codec level of information, like Prores, or XAVC-Intra in Vegas’s case.
-
Search on YouTube for a fan cleaning and your model number of laptop. Someone has posted a teardown video for this problem. Harbor Fright has all the tools you need to do the disassembly.
The posted picture is a good one showing how the lint builds up like a clothes dryer screen. You will be amazed how cool your laptop runs, and the battery will last longer since the fans will not be running as much. As far as rendering/editing goes, laptops are not great for this very reason. They gimp laptop HP to lower power consumption and reduce heat, basically tuning the hardware for intermittent load operation like browsing. When put under actual load they overheat, unless the cooling system is very clean.
Cooling pads and what not, generally in my experience do not do much.
-
You would be best off doing the composite in OBS, recording that footage, and then bringing that into Vegas. Recording the green screen output from OBS will create a lot of artifacting along the composite edge. Working in OBS, allows OBS to work with uncompressed information before encoding it to file / adding artifacts to the image.
-
From the AMD marketing materials on the RX480:
“The Radeon RX series features accelerated H.265 encoding and decoding, enabling …”
This means that media player would utilize onboard GPU playback through the video drivers.
Vegas’s software video engine does not work that way. Vegas decompresses the h.265 video to RGB in CPU/OpenCL, then attempts to work the video in 4096x2160x128x30-60fps in a Floating Point mode. This is what give you the quality of working at very high color levels. That works out to about 4.2- 8.5GB/s. Even though you have a nice system rig, it cannot keep up frame wise with the decode calculations, then the conversions to RGB, then send that back to the display driver, and do that faster than 30-60FPS. 30-60 FPS is 16-34ms. That means your system has to turn a frame in less than 16-34ms, with all the other system overheads, to maintain real time playback.
Windows media player uses the display driver directly, then the GPU offloads the h.265 calculations to an ASIC or register on the GPU specifically designed to handle that problem quickly. Then feeds the playback results to a window overlaid on the screen display, everything happens internally to the GPU at that 256GB/s available bandwidth.
Vegas’s mode of operation allows you to mix and effect the RGB information. GPU playback is just that, you cannot effect the info being shown to screen. Its a trade off.
All that is why they are telling you to work in proxy mode. Your system does not have what it takes to process the software engine in real-time. Convert your media to a format that has less calculation overhead/complexity. h.265 is really meant to be a playback format and not editing. This all echos back to the early days of h.264 and editing, before CPU/GPU power advancements. Even h.264 is a playback codec, and yet CPU/GPU performance is so high now its overcoming the end users slack in avoiding workflow steps.
