Aaron Star
Forum Replies Created
-
I agree with Ole’s recommendation.
Converting to Cineform, you can use Vegas and the batch render script. Vegas will keep the audio when converting to cineform.
Question #2 – Nope. The rule of thumb is “garbage in, garbage out.” You will never get better than your original format. In 10-bit color space, you will just be representing 8-bit colors in 10-bit numeric values. The gradient values in between light and dark are already lost in the low end capture format. There are exceptions to this when you apply composites or filters that effectively re-write the image, or numeric values of the image.
-
When vegas says the render format = the project settings, it’s just that. It says it’s matching the resolution and frame rate. This does not mean it’s matching the the bit rate of the original footage.
Media info will tell the specifics about your media. Then you will be able to match the bit rate of source material, using a custom profile that you create.
Disable resample on you footage that is on the timeline, and also use or learn about the “media match” button under project settings.
-
For HD only, I would just shoot in 60P AVCHD-FX (24mbs). The SD cards will be fast enough to record to.
-
If your laptop has more than 512MB of dedicated video ram(GPU ram) Vegas should see that device. Are your drivers up to date? What version of OS and Vegas are you running. GPU only started in Vegas 11, before that there is CPU only.
However, there may be more to the way Vegas selects a GPU to use than memory and OpenCL version support. Even if you were able to get the GPU working you may not see much improvement over CPU alone. Laptop/Mobile chipsets are given similar GPU numbers to the Desktop GPUs. The performance is generally way off in reality.
Radeon 7670M – 576.0 GFLOPS
Radeon 5770 Desktop – 1360 GFLOPS – Vegas 11 recommended minimum GPU for OpenCL timeline acceleration.
Radeon 7970 Desktop – 4300 GFLOPSWith a number like 7670M consumers are mislead to believe that performance will be in between or close to desktop units. Its all smoke and mirrors advertising.
-
You have no GPU or drivers installed that meet the requirements that Vegas demands. You list no info about your configuration or installed device. The vegas AMD minimums in order of performance are:
HD5770
HD6970
R9-270X
HD7970
RX480
R9-290X or 390X
R9-Fury X -
On the Dynamic Ram Topic – from the help file.
“Using dynamic RAM previews
When your project includes compositing and complex video effects, you may not be able to preview your project at its full frame rate.
If you prefer not to pre render your project, you can dedicate a portion of your RAM to cache video frames that cannot be rendered in real time.”
In other words, you can playback a few seconds of video at full speed, if you have a very complex composite, CG overlays, or motion graphics. It has nothing to do with rendering video to file, or timeline acceleration.
By maxing your ram to dynamic preview, you cut down on Windows available ram which it reduced your disk cache. That meant your system was IOing more to compensate, which lead to slower render times. It is best to leave this at the default setting, unless you are using the feature as it is intended to be used. Some believe that a 0 setting gives better stability, but I believe that is due to other system instabilities.
SHIFT+M – builds a temp file that can be used to view the difficult section at full frame rate.
SHIFT+ B – builds to RAM the number of seconds that can fit into the allocated ram setting to view the difficult section at full frame rate.
CNTL+M – is probably the least used, but could be useful if you are shooting/editing in say XDCAM. Then you can build a difficult section to a new track, then during render you would get a smart render over that section and the rest.
As far as the rendering tests go:
test the trial of Pro vs MS. I believe MS is gimped hence the lower price tag.
Source codecs matter and you say that your source is coming off your phone, and not an actual video device. There could be issues with that workflow that is slowing things down.
Not sure about MS, but all versions of Vegas have supported AVI, so the statement about MS not supporting AVI is odd.
Straight timeline encoding to MP4 will not be helped with GPU, since there is very little math there that OpenCL will help with. Another way to look at it is, the GPU is completing the math it is tasked with so fast, you are still waiting on the CPU to complete. Frame by frame, slow math kid vs fast math kid then combining the results. The fast math kid will be sitting waiting for the next problem, which looks like 0 GPU usage on an average meter system like most monitors are.
If you want to see how much GPU helps rendering to MP4, try 2 video layers, cookie cutter the top, and defocus the bottom track. Now try the same test in 32bit Floating Point mode. You should see a large improvement over CPU only. GPU acceleration is application specific. The uneducated marketing people have screwed most consumers here due to the complexity of the subject.
Rendering 60P means 2x the amount of frames to render, which means a longer render. The question have to ask yourself, is your material really worth or require 60P video?
GPU MP4 rendering was abandoned for a reason by most NLE and encoders. Instead favoring things like ASIC, or processor extensions like Quicksync. NLEs have not picked this up much, because of the dev time involved with coding for specific hardware. “Laying Up” a software only NLE is much easier, cheaper, and will run on all hardware. Just maybe not optimized. I have always found most low end NLE software to be a bit of a con job, you get what you pay for.
-
No. That’s not what he is asking. Switch Media Info to Text view and list the format parameters.
This is probably a another issue with OBS creating non standard video format, with a variable frame rate mode.
Also why are you capturing at 120fps? Is it to slow stuff down when needed or what? Most streaming services only support 60P, which in fact is actually 59.94. There is a difference between Video standards and PC monitor (gaming) frame rates.
Filmmakers and NLEs like Vegas want constant frame rate video codecs that are very rigid in timing. Mainly for audio drift problems. Does that sound familiar? I would convert that media with FFMPEG, and get it to a constant frame rate, intra frame codec.
You might also test X-Split broadcaster and see if you have the same problems. Last time I recorded something with XSplit, it produced constant frame rate media that edited well in Vegas.
Another question. Are you seeing a rock solid playback counter of 120fps at the bottom of the preview window?
-
UI is hard. Sounds like the Magix programmers need to take some UI classes, or at least their designer. Dropping color for certain key functions is not good idea. It’s like not painting the working end of the nail gun red, just because it doesn’t look cool.
Please do not screw up Vegas like the Nimwits over at Blackmagic. Those people for some reason think Resolve should take over the OS and not function like standard windows program. I mean what the heck is that? It has to be a just serious case of narcissism over at Blackmagic, AVID, and the others. Ego tends to step forward with idiots that think they have a winning solution. Some of these media apps are coming at UI design from attitude they are the only thing that will be done with the PC it’s running on. What about edit notes in another application? Do not give “Windows Users” a Unix UI. If you want to go Linux UI, then just go 100% Linux, and do not make a Windows version.
There is a very thick book on Windows UI design. If you read it, you will understand just how many man hours of product testing has gone into the UI that exists with Windows. You can also watch Video, if you tune into the BUILD conferences when they make UI changes. Because a large portion of the Keynote will be about findings of product testing and why the UI is changing. Why go you own way when you have thousands to work with, and the other guy has spent tens of millions on testing his UI.
One of the best things Vegas had going for it was that is was written for windows following the standards, such that it functioned just like Word or Excel. You could have multiple windows open to different projects and flip, or cut and paste between them. You could render another project in the background at low process priority and keep editing. Try any of that in the competitions UI. Resolve has gone so far as to just avoid even placing the minimize buttons on the panes. I mean wtf? There is a clear windows standard for the File, Edit, View across the top, or Settings Drawers if you are into the Universal App Touch standards. Just like there are standards for all the things under the hood as well.
What would be nice is some way to get the 2nd or 3rd windows of vegas to share the GPU with the other applications. Right now the 2nd window of vegas is CPU only. The 1st Vegas window launched is the GPU enabled window. So rendering in the background means you have to close the edit window project and open it into the background render window.
Stepping down off the stump.
-
You can also download FFMPEG and use FFProbe if you understand the output. If FFPlay will playback the media, then FFMPEG will allow you to convert the media to a Vegas friendly format.
I agree with John. Figuring out some way to convert you media to XAVC-Intra, or Cineform will be about the only way to make h.265 work in Vegas 13. There was a way to hack h.265 into VP13 but it caused other issues.
-
I mean “media info,” there are links all over the place in other threads to the application. Here is another:
https://mediaarea.net/en/MediaInfo