Aaron Star
Forum Replies Created
-
Most of the time when people are posting render times on the web, they are commenting on 24-30fps. When you rendering 60FPS, you are having to render 2x the amount of frames. Hardware encoding can speed up render times but this depends on your GPU type, and whether or not your system is setup to utilize QuickSync on your CPU. You should look into the results you are comparing to and determine if your results are a direct comparison. 5mins to render 30p would be 10-15 to render 60p.
Laptop hardware is not as fast as desktop hardware, so your laptop results will be slower than Desktop render demos.
There are other factors as well like the source codec. Decoding can be much faster and lighter weight with the right source material, and in turn allowing more processing time for encoding.
YouTube 720-60p bitrate is 7.5 or rounded up is 8Mb/s. I would render your upload file to about 10-12Mb/s using Sony AVC. Using a custom Internet profile that matches your project settings, and has QuickSync enabled. Assuming your laptop only has the integrated Intel GPU and no other discrete GPU.
Another option if you have good upload bandwidth (5-20Mb/s) would be to use a Sony.MXF>HD EX 1280-720-60p profile. Render to that format and upload the resulting file directly to YouTube. The variable bitrate nature of XDCAM will scale well with the amount of motion in your material, and minimize bandwidth for the static sections. XDCAM is GPU accelerated but not QuickSync capable.
What laptop model are you using?
-
What is your system configuration?
Do you have the latest Quicktime installed, if it is installed?
Have you scanned your system for bugs with something like Malaware bytes?
Latest win10 compatible GPU drivers, sound drivers, network?
Any other devices we are not aware of like old sound cards, BM boards, or other add in boards?
I had an issue a long time ago with MS11 and a similar error where it turned out to be an old unsupported ASIO sound card. Pulled the old card, switched to the built in sound card and problem subsided. Not saying that is what the problem is, its just an example.
-
Pretty sure if you made an image of your Win7 install, then broke the RAID, and did a clean install of Win10 with the ICH10 in SATA mode, it would more than likely work just fine. Would be a good time to upgrade to an SSD for boot anyways.
-
Hmm. Is your Quicktime up to 7.7.6 and the Avid codec pack up to 2.6.0? Those are the versions I have that are working on my end.
Are the include Video and Audio track check boxes marked in the QuickTime profile settings?
-
“render loop region only” – is what I was referring to without having Vegas open for the correct term. This will just render your 30 seconds selected on the timeline.
“A professional Color Corrector company is charging the film 8 grand to Color Correct.”This makes sense. Yeah DNxHD is probably your most compatible format with a professional Resolve setup, or depending on what they are using. Choosing one of the following profiles:
Avid DNxHD 350x 1920 x 1080 4:4:4 10-bit 23.976 352Mb/s 0.407 Mins/GB
Avid DNxHD 175x 1920 x 1080 4:2:2 10-bit 23.976 176Mb/s 0.814 Mins/GBSince you have footage from DSLR and GoPro the 175x profile should be good enough. Rendering your project in 32-bit Video Levels is recommended to push through the Redcode color, while the 8-bit DSLR/GoPro formats will just be expanded. If the Redcode was not in the picture, you could pretty much just follow John’s tutorial. So your quality level depends on which format dominates the timeline. This is assuming that the R3D footage was dropped on the timeline and not transferred to some other format before editing.
The post house should give you the exact format specs they prefer.
.MXF HDCAM-SR 444, SR 422 or HDCAM-SR-Lite would be your Vegas optimized formats at that level and 1080-24p. Resolve supports this, but there again it depends on what the post house is running and willing to accept.
“There is not a whole lot of info on your planned workflow from Source media, to Vegas project settings, to CC application requirements, to display format conversion(DCP for example.)”
I guess in hind sight, for 8 grand they are delivering you a DCP and graded DNxHD file.
“If you have a format that keeps my quality and gets this out the door, I am all ears!!!”
The DNxHD 175x profile would be a good middle road, 350x if you really want to maintain your REDCODE footage.
On the Sony side – HDCAM SR 444 if you want to optimize for the REDCODE material, SR 422 or 422-lite if the majority of footage is DSLR and GoPro.
-
Unless Sony is dumping Vegas all together or selling it off, there will most likely be a Vegas 14. If Sony hangs on to Vegas, then they will most likely merge Vegas into a catalyst product sometime down the road when the catalyst products reach version 3 or 4.
-
You could do this in Vegas, but it might not be the best tool in the box to use. This is probably created in After Effects or some 3D app, and then rendered out to a .PNG sequence to act as the transition. To do this in Vegas would require some heavy compositing of tracks and key framing. Although there only seems like 3-4 layers depending on how you do it.
1 – White background
2 – Lanyard layer
3 – Badage with logo layer.
4 – Additional animated title text layer
Then key frame 2-4 to wipe white backdrop to reveal an alpha background.Render to .png sequence.
After Effects most likely has a template or the motions already built, which is why people like After Effects.
-
Do you have render selected timeline area enabled, and are you selecting the entire project you want rendered?
What rendering as settings and DNxHD profile are you using right now, and how does that compare to your project settings and source material.
Do you need to render to dnxhd.mov? Is all your source media in DNxHD already?
There is not a whole lot of info on your planned workflow from Source media, to Vegas project settings, to CC application requirements, to display format conversion(DCP for example.)
Highest quality is really determined by your source material, and carrying that level through to your display format.
-
Could you provide a few other bits of info?
“Media Info” – most post the “text results” which can be selected in the application. Use this tool on your source media, and report the results.
https://mediaarea.net/en/MediaInfo/Download/WindowsInside Vegas timeline or media window, right click and select properties on your source media. Goto the general tab and post the media info here, specifically looking for the Plug-in information.
Since you installed the K-LITE pack, I would:
Uninstall KLITE
Uninstall Vegas
Use CCleaner Reg cleaner to clear any bad entries
Use Malware Bytes to scan/clean any remaining crapware, and reboot.
Install all MS updates under windows update, and reboot if upgraded.
Verify your GPU driver is the most recent, reboot if upgraded.
Reinstall Vegas and test your output again.
Use something like GPU-Z to verify that your GPU is in use while rendering to MC Encoder with Cuda.I would do all that after you post your info on your source media.
Also Under the MC Encoder, choosing VBR and using 18Mbs Peak, and 12Mbs Average, 4 slices, and enable progressive download.
Rendering Sony AVC is a good idea too, your profile would be the same as your project settings with about 10Mbs, 16Mbs, or 22Mbs bitrate. YouTube HD is only 8Mbs, but uploading more and allowing YT to toss the rest is preferred.
You could also try rendering to XDCAM-EX and uploading that file to YT.
Hardware wise, I would not think you HDD is holding you back, unless you are attempting to work with uncompressed video sources. You could use something like Speccy, under storage and verify that your HDD MAX transfer mode and Used Transfer Modes are the same. Then under Windows Device Manager, under IDE ATA/ATAPI controllers, verify that the SATA controller is listed as a AHCI controller. With out AHCI your system will not take advantage of certain drive performance enhancements like NCQ.
-
So have you tried pulling the GPU and running only on your embedded GPU as a test?
Is your system clean and heat fins clean of dust build up?
Have you run something like Malware Bytes to check for crapware?
CCleaner to rid your registry of false entries?
Performed all MS updates, then rebooted?
While the GPU is out, and again installed with latest drivers, run a “winsat formal” from an Admin Command line. Verify this test completes under both configurations. If this test completes fine, I would look at your Vegas install and what is hanging there.
Something in your post seems odd to me. It says you have an NVidia card with onboard Intel graphics, but then you talk about updates to AMD catalyst center? I do not understand this.
System halting or freezing is often times hardware or something that ties up the system into a wait state for something to complete. In the worse case a kernel crash. It is really hard for a forum to understand where you are at in the troubleshooting of the problem.