Aaron Star
Forum Replies Created
-
I would look at the “Media Info” (the application) on the ProRes files and make sure the Writing Library was Apply. If not they may have use FFmpeg to encode Prores and screwed it up.
Next try the Vegas 13 Trial and see if that plays the file in question.
-
Like Bob and John said. Also after rebooting, go to Start>settings> “update&security” and make sure any and all updates have been completed there. Verify that your GPU driver does not have Windows10 driver, or is up to the latest version. If there are any update installs make sure to reboot before attempting Vegas install again.
-
Normally with a default Vegas project open, you can just drag and drop on the timeline. Edit. Then “render as” video only track to MPEG2, and audio only to AC-3. Next bring those files into DVDA and make your menus.
-
To convert the mts to any format. Open a default vegas project, drop a clip on the timeline and render as to the XDCAM-EX.mxf that matches the footage size.
For batch rendering, there are plugins that convert vegas into a batch render tool, or there is this post from a while ago that explains how to use a modified Sony script in Vegas:
https://forums.creativecow.net/readpost/24/991739
I recommend testing how responsive your system is with MTS clips, MP4, and XDCAM both with GPU enabled and CPU only. Zoom in on the timeline and “scrub” back and forth quickly with the timeline cursor. You often times will see how much more responsive XDCAM, HDCAM-SR, and SR-lite.MXF is over editing from mp4 based file formats. If your machine struggles with editing .mp4 files, you will see “…” building after the frame counter vs smooth snappy visuals during the scrub test.
Try putting 3-4 layers of like video formats on a timeline, make the opacity 25% and see which format drops framerate the least.
For example on my modest system, here is run down on how the codecs stack up:
3 layers of HDCAM-SR&SR-Lite will not drop
3 layers of XDCAM no dropped frames
3 layers of XAVC-HD will achieve about 6FPS
3 layers of DNxHD.mov – 7FPS
3 layers of Nikon-AVC@54Mbs.mov – 11-15FPS
3 layers of SonyAVC.MP4 – 9FPSHDCAM SR and SR-lite are high bitrate HD equivalents to PRORES-HQ.
-
None of those photos are working, they are all link dead on my end. Can you post to GDrive or Gphoto and link from there?
-
You can Wiki VP9, but basically this is googles version of h265. Depends probably on region server you are being served from, or browser support, as to whether you will get VP9.
Google play a bunch in licensing fees to use .MP4 in their product. If google has its way, we only use VP9 for YouTube. VP9 eliminates the MPEG-LA fees.
One other thought on your capture. You might try to capture in .PNG or .tif. Set your game to limit frame rate to 60FPS, as this will keep the frame capture rate inline with the final render and save space. No need to render more than you have to. Limiting to 60FPS will also free up system resources.
If you can verify that your capture in png or tif is in 32bit RGBA, then rendering in 32-bit Video Level (not full range) to XAVC (project matching profile.) will improve color and banding issues. Upload the XAVC file directly, and verify that the media info says its in 10-bit mode.
-
// Edit 2: Just to let you know how the whole process goes. In the game, I set it to run at framerate of 300 (to make later editing easier while doing slow motion etc.) then I start capturing thousands of .tga pictures which I then connect in a program called VirtualDub to make an .avi file from all those pictures. This is a standard process of doing videos from this game at the highest possible quality.
You know that you can import still images as a video clip? Use the import function in the media manager, then select the 1st image, and then check the sequence duration of the last frame. Then set the media settings to what you want the play back to be. No need for VirtualDub or anything.
Also when capturing, no need for 300 frames per second, just capture 60FPS to still image. Your video will only show and render 60FPS, no need for overkill here. If you can capture to .PNG would be best, and or .TIF (tif will be large.)
-
The vegas settings you posted are not “project Settings.” What you posted is “render as” settings, there is a difference.
-
Posting “Media Info” on your source footage would help, also screen shot your project settings.
You might try the Match Media button in Project Settings, then render to an XDCAM-EX profile that “=” the project settings. Upload the XDCAM-EX clip directly to YouTube.
YouTube does scale everything down to 6-8Mbs HD at 30FPS, they double the bitrate for 60P. XDCAM at 29.97 will more than cover the bitrate issue, and allow YT a good master to encode the various MPEG-DASH streams. 60P is just more frames to render and gets into whether you are looking at the content or quality of what you are watching. If you need 60p, try an XAVC profile, or Sony AVC with the bitrate set to about 15-25Mbs. All this done in 8-bit project mode, as your source material is not likely more than 8-bit.
-
Proxy editing can be as easy as:
Vegas-file.veg
-Sub folder full res footage
-Sub folder Proxy res footageRender all the master footage to xdcam and place in proxy folder keeping the names the same. Changing back and forth is as easy as renaming the master folder name. Then open Vegas and point to proxy files. When ready to change back, rename the folders again, and re-point Vegas to full res files.
This is the way proxy is has worked forever. The proxy edit feature in Vegas is just an attempt to automate this old school process. They simply build the same files and then playback the proxy below Best/Good settings.
With footage as basic as RX100, you could just clip and convert all master media to XDCAM-EX and forget the .MTS media. Then just edit the resulting XDCAM footage. Vegas can batch render by region, which allows for CC and clipping the source footage to cut down on the batch render time.
On other thing to think about, the Lenovo y50 with i7-4700HQ, the processor computational comparison is less than a i7-Gen1 desktop. Getting a cheapo desktop with a i7-4790k, and using the intel graphics would probably give you a better editing experience. Assuming that is correct model number you posted.