Aaron Star
Forum Replies Created
-
What version of Vegas Pro 11.0 are you on, are you running the last build?
Have you run all the windows updates including any optional ones having to do with .net?
Is GPU enabled or disabled under preferences?
Verify your GPU driver is up to date from NV or AMD.
Verify your Audio device driver is the latest from the manufacturer.
Right click on Start > Device Manager – make sure you have no ! devices listed.
Right click on Start > Admin Command Prompt – “sfc /scannow” will verify your windows core files for problems.
There really is very little difference between Win8 and 10, so Vegas should work well in either version. Upgrading will not install the latest device drivers for hardware, it will only load compatible drivers.
-
I would make sure you are on the latest builds of Vegas and DVDA.
Then maybe try some different media like Verbatim, even try burning a DVD-RW disc, or DVD-R or DVD+R. My experience with LG drives has not been that great. I have had 2 LG drives stop burning +R media correctly but burn the others fine.
Memorex is some of the worst media out there, with high error rates beyond 3.8GB. There are utilities out there that you can test your media surface quality from beginning to end.
-
Get a utility app like Speccy, and post a screenshot of the summary page running on your system.
Fraps is not a very good application. In my experience the files it creates are not that compliant or something. I would try to Mirillis Action for screen capture. Action uses hardware on the your CPU and GPU to offload the recording. The speccy screenshot helps understand the hardware installed on your system, to know if Action is a good fit.
An alternative to the files you have already created is to try FFPLAY and see if that displays the videos. If FFPLAY will show the video, you can use FFMPEG to convert the media to an editable format in Vegas like .MP4/h.264.
Microsoft has given away Encoder 4 now as a free download. This tool has really good screen capture utility built in, but records in a proprietary file that works well in Encoder. So getting the file into Vegas can be tricky.
Xsplit has a good screen capture tool and offers a free version with limited abilities.
Your best screen recording solution with lowest system impact, would be to clone you monitor output to another computer running a recorder. Something like a Blackmagic shuttle that records to MJPEG.AVI, that footage will drop on the Vegas timeline and edit well.
-
Update to the latest versions of Vegas(B453) and to the latest version of Quicktime (7.7.9). Make sure all the Windows updates, and updates for .NET have been installed. Reboot. If the problem is still there, post the “mediainfo” on the quicktime footage. Black frame means Vegas cannot understand the codec properly to display the image. This could be due to any number of reasons, but start with the simple stuff 1st.
https://mediaarea.net/en/MediaInfo
-
You would have to look at what info is actually in the camera master clip. The posted JPG is clipped, so there is only so much reducing levels is going to do. You may have a better results on the master file. If you want to share the master clip to dropbox, people would most likely help you.
-
Buy a new machine, as it looks like there is an issue with that device.
https://forum.toshiba.eu/showthread.php?63586-Qosmio-X770-GPU-CPU-temperatures
Read the Verdict section:
https://www.notebookcheck.net/Review-Toshiba-Qosmio-X70-A-11R-Notebook.102010.0.htmlWhen was the last time you cleaned the fins on the CPU cooler. The CPU cooler on that device is like a dryer lint trap, and needs to be clean about every 6 months.
I read another thread on that machine, that you need to make sure the BIOS is the very latest to enable the disabling of the Intel Speed stepping.
Posting video of Speecy showing CPU Thermals and freq, along with temps for the other devices on the system would help the forum help you better.
Use something like GPU-Z from “Techpowerup” and monitor GPU utilization and temps during renderings to verify there is no thermal throttling on the GPU, which in turn is causing the CPU to step down. A render test like Luxmark will spike the CPU+GPU to max for extended periods of time.
Verify that that you do not have a DPC latency issue on the device might help too. A bad driver could be causing system interrupts that the system is seeing as idle time and causing the CPU to step down.
Verify with a multimeter that the external power supply is maintaining the 19V under burn in load, or under a stress test like Luxmark CPU+GPU.
Vegas is not like other encoder apps like Handbrake, there is a lot more going on than Handbrake. Making sure you have fastest memory and plenty of it (16-32GB) for the motherboard, is something I would check. Next make sure you have a good SSD, with low latency, no errors, and high throughput. Power supply is providing correct voltage, and heat sinks are clear.
-
Fraps is junk and has been for a while.
Try Merillis Action – https://www.mirillis.com/en/products/action.html ,Xsplit, or Shadowplay (NV card needed).
Apps like Mirillis action will use hardward functions like Intel® Quick Sync Video, NVIDIA NVENC, and AMD APP to off load recording during gameplay.
-
People tend to think Windows Media Player is just a simple application, but in fact its pretty advanced. At one time in the late 90ies it was the most advanced player on the market, that had feature other products would integrate years down the road. Support for multiple streaming formats 5-7 years before the likes of YouTube is mainly what I am referring to here.
WMP is likely buffering your source video and determining the error in the bit stream, and then dropping the information in a way that is not perceivable to give the best viewing experience.
Vegas on the other hand is showing exactly the status of the clip information. This is what you want in a video editing application. A captain needs to know the status of the ship no matter how bad the news.
You may want to check the chip that media was copied from an verify it for errors. Reformat it with a tool like:
https://www.sdcard.org/downloads/formatter_4/
or
https://rufus.akeo.ie/ – which has a built in bad block checker option.
Then verify your system Memory with Memtest86 v4+ and your Storage with chkdsk /R
These steps will make sure the info is not being lost during storage and copying.
-
For the type of content you are producing and the codec you are rendering to, there is no reason for you to be operating in 32-bit Full mode. Switch your project settings to 8-bit and you will massively reduce your compute cycles.
Here is a workflow to try:
1. Game capture file
2. Vegas new project, drag and drop on to timeline. This should make the project settings match your source file. You can alternatively use the “Match Media” button on the project settings window to do the same thing. “MediaInfo” installed on your machine also allows you to see the media format that your capture system is outputting in detail.
3. Edit project on timeline.
4. Render to Sony AVC 1080-60P profile, or a profile that exactly matches your project settings. If your project settings do not match 1080-60p, then correct your game capture to cap at 1080-59.94P, as 59.94 is the actual stream format that YouTube and others operate at. An FPS setting of 60 even can cause frame rate conversion issues that appear as picture artifacts in high motion events.
Your bit rate on the render template is excessive. If you are uploading to YouTube or a similar service, those services only stream at 8Mbs@30P and 12Mbs@60P. Selecting a Sony AVC profile and changing the FPS to 59.94 and the bite rate to 16Mbs will yield enough picture quality to toss out the extra info at the encoding service. You videos are re-encoded once upload. There is no reason or quality benefits to upload more info than needed.
https://support.google.com/youtube/answer/1722171?hl=en
For YouTube, I render 1080-30p material in XDCAM-EX which is 35Mbs, is standardized and optimized in Vegas, and yields great results. An XAVC-I 1080-60P profile would also be a good choice for what you are doing, as that codec is highly optimized in Vegas. No need to re-invent the wheel on MC encoder profile settings.
A long time ago, I used to create WoW BC raid videos for my guild, and uploaded all the raid stats and video within 12 hours of the event. Those were some long hours. Today things are so easy, what with sites like Twitch and live posting of stats.
Rendering an 8-bit project, to and 8-bit encoder, to a 16Mbs profile will greatly reduce the render times and get your videos uploaded faster.
-
“XD-HD in the 50Mb, 1080i/ 59.94”
The TV station is probably operating on Sony XDCAM422 equipment. You can shoot pretty much whatever you want, but just need to deliver in 1080i(29.97 interlaced or 59.94 fields/s) rendered to Sony XDCAM422, which is a 50Mbs MPEG2 format in an .MXF wrapper.
https://en.wikipedia.org/wiki/XDCAM
Shooting in 422 color will help with this, but is not necessary, as the TV station is likely buying your content an not the production color qualities. Shooting your DSRL in 1080i mode, editing in 1080i, and then rendering to XDCAM422.MXF will more than likely be accepted by the station. The station will likely have the equipment to accept the .MXF file and play it directly, or convert it to tape if they are really old school. The main thing to watch are your black levels when you do the conversion from 4:2:0 to 4:2:2. Verify with your video scopes the conversion is staying the same.
XDCAM422 can be rendered from Sony Vegas Pro Edit, and the recent Sony Catalyst series of products. Sony also makes a downloadable plugin for AVID and Final Cut, with some of the most recent versions support exporting it native.
You may also want to see if the Station is working with
as that may also be an alternative delivery solution.