Aaron Star
Forum Replies Created
-
[lucas pelus] “Here is what I could buy : Asus – W10 GL752VW-T4004T (1300€) 17,3″, i7-6700HQ, HDD 1To 7200tpm + SSD 128 go, GTX 960M, 8 go DDR4”
- Sticking to Roy’s rule of thumb which I agree with, you would want 16GB-32GB of RAM. I would prefer 32GB, but 16GB should be enough for application + disk cache needs.
[lucas pelus] “I tell you i see, HDD 1 To + SSD 128 go. It’s what it’s wrotte on the web site but i don’t know what that’s mean.”
- This is probably a Western Digital drive. WD makes SSD drive + 1TB Spinning HDD in a 2.5 form factor. The drive appears on windows as 2 individual drives C & D. Of course it could be an M2 for the SSD too, but I think they would market that.
.
A Dell XPS 8900 with i7-6700, Samsung 850 M.2, 32GB RAM, and a AMD 390X would be a much higher performing machine in Vegas than that laptop.
-
The m275x is just shy of an HD5770 so make sure to have you GPU selected in Vegas Preferences, and in your codecs that allow GPU set them to automatic. With only 2 cores, you will want as much help as your GPU will give you.
I would try XDCAM-EX.MXF at 720P if you really need 60P, or 30P if you need 1080. You will need to create a custom 1280×720-60P profile. XDCAM will upload directly to YouTube, it is GPU assisted and much less taxing on a weaker system.
Here are some comparable time on my system for a 1 minute AVC-1080-60P clip rendered to:
WMV 1080-60P-16Mbs-VBR – 5m 38s
Sony AVCHD 1080-60P-16Mbs – 2m 59s
Cineform.AVI 1080-60p-40Mbs – 1m 29s
XDCAM-ex.MXF – 1080-30p – 32s
XDCAM-ex.MXF – 720-60p – 24sYou can multiply the times by your project duration.
You may also want to test Quicksync exports and see if that works on your newer system. Most have said that QS does not do more than 720p, but your processor does support the latest version of QS. That way your CPU+GPU would be rendering the timeline, and Quicksync would be assisting on the encoder to MP4. QS would be rendering to Sony AVC codec, and there are other posts on the topic in the forum.
-
You can do that too.
I always try and figure out why a system file like that would go corrupt, disappear, or not be found before just re-installing. Bad memory blocks in ram can sometimes look like disk failure, disk errors from a failing drive can start making windows files like that not accessible. Malware and virus do their own things. Reinstalling may only temporarily repair a bad situation.
I keep my .NET packages up to date for development and security reasons, that’s why I advocate doing updates on .NET from MS. Consider how many security patches there have been since the 453 installer was released in June.
-
MSVCR110.dll is a Microsoft C runtime Dll. Vegas is written in .NET which is a form of C. I would make sure your system drive or memory is operating well before blaming the vegas application. You system RAM or Storage could be in error, or something that was uninstalled recently has screwed with the operation of that dll.
I would verify your .NET versions are still loaded and installed versions do not need an update in Windows Update.
If that does not work, verify the file exists in C:\Windows\SysWOW64\MSVCR110.dll
If the file exists, you have executed all the updates and restarted, run SFC /scannow from an admin command prompt. Repair any of the file issues noted in the CBS.log, windows will give a message that it did not find problems if all is well.
Make sure you have a clean system by running Malware bytes and window defender scans.
Run MemTest86 through one pass of 10 tests to verify your memory is good.
Run chkdsk /R from an admin command prompt and set for reboot check, then reboot. Then check event log for issues found from the chkdsk scan.
Then if the app still does not operate, reinstall Vegas 13 B453.
-
Drop some MP3 material on the timeline and then check the properties of the file. What dll is vegas using for mp3?
Have you installed any other software that may have insall mp3 encoding changes to your system?
Have tried AAC,that is mp4 based and bit more updated vs mp3. Do you get the same slowness converting to AAC?
-
Aaron Star
January 2, 2016 at 3:07 am in reply to: Vimeo does not recognize color profile from Vegas .mp4 renders anymore ?What encoder are you using? What is your work flow?
Mp4 is pretty much just studio RGB, so maybe try sony AVC?
-
Aaron Star
January 1, 2016 at 10:03 pm in reply to: Vegas plug in for particle effects – light saber?I would say no off the top of my head. I would look into Blender or some other type of similar app to produce that effect.
Once you realize how much time is spend on individual frames in an effect sequence, you garner great respect for the visuals you see in films.
-
Verify Hardware temps are ok during playback and rendering with something like Speccy or another program like it. Repair cooling issues if high temps are present. A utility like Speccy will show you temps on internal devices.
Anything over 40C idle, and CPU/GPU under load exceeding 70C+ should be looked into.
Make sure to not overclock memory, CPU, or GPU during troubleshooting.
When I have seen this error in the past, it was driver related on a laptop that had a bad Wifi adapter that was not compatible with Win10, as well as a bad trackpad driver that was not compatible with the OS. So I would make sure to have the latest drivers from NV, and RealTek loaded. Also verify that your Bios from ASUS is the latest, and if there are any chipset driver updates for your OS.
From there I would try the following:
Check Event log for system errors.
Check system RAM with Memtest86 from a Boot DVD or Boot USB drive. Run memory through all 10 tests. There should be no errors, if there are errors replace bad sticks until you get no errors on the 10 tests.
“chkdsk /f” from a command prompt, choose yes on next reboot. Reboot
Apply all windows updates, including any .NET updates.
Make sure GPU driver is latest.
Uninstall any old applications or utilities no longer used.
Run CCleaner Registry cleaner and repair issues. Reboot.
Run a Windows defender scan, and Malware Bytes scan, and repair issues found, reboot if issues found and re-run scans.
“dism /Online /Cleanup-Image /RestoreHealth” from an admin command line. You should get:
[==========================100.0%==========================]
The restore operation completed successfully.
The operation completed successfully.sfc /scannow from an admin command prompt. Verify you get:
“Windows Resource Protection did not find any integrity violations.”
repair any issues here. Reboot and re-run if issues repaired until you get the message above.
Make sure Vegas is running the latest version (build 453), reboot if upgrade is needed.
-
If you have a laptop and it has that interface it will work. I used to have a similar device for an old laptop to record DV in uncut segments longer than tapes. The interface worked really well. DV is pretty low system requirements by today’s computer standards.
-
Aaron Star
December 31, 2015 at 6:10 am in reply to: Magewell XL 100 D HDMI Capture to Sony Vegas 12 ??Well I was off one letter on the product number. When I looked it up, I came up with the DE which is a PCIe. My bad.
I believe the Sony App will capture whatever is presented correctly to Windows, as the app is very rudimentary. But like I said, the lack compression and better alternatives provided generally by manufacturers, I do not see the point to using the capture utility these days. When I need to capture a video signal, I generally use Blackmagic’s included app, or go to an encoder app for live or direct mp4 capture.