Forum Replies Created
-
I think that you are looking at two different issues. Fix them one at a time.
FileIOSurrigate is installed by Vegas, so try reinstalling Vegas. Also, just for grins, try plugging the computer into the net and try again.Are there any unused media in your Project Media window? Remove them from the project. Also check any nested projects for the same unused media. Vegas will try to find all media in the Project Media regardless if it’s not used on the timeline.
Steve Mann
MannMade Digital Video
http://www.mmdv.com -
“Steve, do you have a special version of Vegas 12? I don’t see an “internal” tab under my preferences. It’s the only one that’s missing. ”
Hold the shift key when you click on Preferences.WARNING – Changing entries in the Internals tab can truly screw up Vegas.
Steve Mann
MannMade Digital Video
http://www.mmdv.com -
You can ignore .sfk and .sfl files. They are created by Vegas for internal use.
From my personal Wiki:
File types used or created by VegasSteve Mann
MannMade Digital Video
http://www.mmdv.com -
Stephen Mann
November 5, 2013 at 5:20 pm in reply to: Catastrophic Failure errors when using TimeWarpThere is something wrong with the Sony email notification system. I only occasionally see the monthly Sony emails where these sales are announced.
Steve Mann
MannMade Digital Video
http://www.mmdv.com -
I am not familiar with either Rode mic. As I said, I am using an inexpensive MXL 661 Dynamic microphone and an MXL Mike Mate USB adapter. I do voiceovers with it and my daughter uses if to record voices for animation.
The golden key to good audio is absurdly simple and cheap – get the microphone close to the subject. A $50 wired lav will sound so much better than any on-camera microphone that you will wonder why there is even a microphone on the camera. Except for what Dave said, I do use the on-camera microphones only to synch multiple cameras by matching the sound tracks. (OK, it saved my ass once when a wireless failed during an interview).
Shotgun microphones are only marginally better than on-camera microphones. I don’t like the term “Shotgun”, but we’re stuck with it. All a shotgun microphone offers is a more focused response curve, but you’re still at the same distance from the subject and the sound level reaching the shotgun is the same as what your on-camera microphone hears. The shotgun just minimizes sounds from the sides. They are best used on a boom pole.
Steve Mann
MannMade Digital Video
http://www.mmdv.com -
-
I am still inclined toward the Video Device Drivers.
I’ll try to address various issues in your list.
Network activity: Just because you are unplugged from the net, it won’t stop Vegas or some plug-ins from checking for a new version.Just for grins – What file paths does Vegas use?
In the Options tab hold the shift key and click on Options.
WARNING – Changing anything on the Internal tab can truly screw up Vegas
At the bottom there is an option to filter your preferences. Enter “Path” here. In the “Value” column, you want to make sure that all of the paths listed are accessible and have plenty of free space. If you have an SSD for your system drive, space could be getting tight. Also, due to the nature of some SSD drives, you could be getting into a racetrack condition where one process could be dependent on the data that another hasn’t moved from the SSD RAM buffer to the SSD storage yet. You can safely change these to a folder on your hard disk with two warnings. First, never use an external drive for Vegas paths. If the external drive is not present, or assigned a different drive letter by Windows, then Vegas will crash. Second, you must create the folder on the HDD before you change the path in the Internal Preferences tab. Vegas will not create them for you.” average 60% memory use, lots of disc activity. ” – As I said before, CPU % use and Drive % use are extremely poor metrics for system performance. Besides, they are only useful when 0% or 100%. 100% only means you hardware isn’t fast enough.
” Resmon showed one 100% hard memory error” – Could be a problem, but if the error didn’t abort the program, it probably worked on retry by the program. Still, did you run MEMTEST86?
“Render stopped at 99%, but the file was written and could be played as well. ” The disk activity at the end of a render is where Vegas is cleaning up the temporary files and finalizing the output file.
“Sound and image were however not always correct, sometimes repeated, sometimes left out.” This one is a head scratcher. What render template are you using? Have you tried a different one?
“FileIOSurrogate.exe”
See: https://www.custcenter.com/app/answers/detail/a_id/5121/~/fileiosurrogate-error“Most memory then seemed to be used by explorer.exe” This is normal when nothing else is active.
“At startup Vegas doesn’t just flash anymore with the bigger projects, the screen gets all white for several seconds. After that there seem to be several interruptions before I can work again. With very small projects it is still just a flash.” – This is screaming Driver Error. Those white flashes could be the driver trying to load a function then giving up.
“At computer shut down often the message is displayed that a process is going on in the background.” – What process is still running? Cancel the shutdown and open the task manager to see what is still running.
Steve Mann
MannMade Digital Video
http://www.mmdv.com -
You will get a lot more responses if you start a new thread.
Steve Mann
MannMade Digital Video
http://www.mmdv.com -
Whatd’ya know – there it is. I had never seen it before.
Steve Mann
MannMade Digital Video
http://www.mmdv.com -
I don’t know what’s happening on the forums today, so this may be a double post.
CPU activity dropping to zero only means that the CPU is waiting for a process to finish.
You can use the Windows Resource Monitor to try to determine what process has caused the problem.
Go to Start, Run, and enter “resmon”.
In the Overview tab, look for Vegas in the image column.
Right-click on the program image name and select “Analyze Wait Chain”
If a hung process is the problem, you can try to simply end the process. More often than not (in my experience) this usually fixes the immediate problem and the program can continue running. Back up your work and Google the offending process to see if there may be a fix. (It’s a long shot, though.)Steve Mann
MannMade Digital Video
http://www.mmdv.com

