Mark Barton
Forum Replies Created
-
The assertion error looks to be file I/O related, so I tried changing the Sony Vegas Pro Option/Preferences/General and unchecked “Close media files when not the active application”. I restarted Sony Vegas after making that change and completed working on my project without getting that error again. See if that makes a difference for you too.
-
Update. I chose ignore a few times and the clips ended up on the timeline and other than that assertion message, it appears it worked fine. I tried a new project and dragged one clip and then two clips, etc to the timeline to see if it was the number of clips at one time that caused the error. I did not get an error with that test. I have not noticed any issues yet once they are on the timeline with editing them and playback.
-
I just happened to get the same error after my last post. I just dragged onto the timeline about a dozen clips that I had rendered using cineform. Not sure if it was the Windows update I applied just before or just the way I brought those clips to the timeline. I will share if I find out more tonight.
-
That is an error from the Go Pro Studio software. Try updating it or reinstalling. It is the one that installs that Cineform dll.
-
Would Sony Levels plug-in and automate “Output End” to get the same curves dialog meet your needs for the fade?
-
How do your project settings compare between Vegas 11 and 13? Did Vegas 13 set the properties to the lower resolution, usually it offers to set the project to the media you first drag to the timeline. Do you really need 1080P delivery for this school project? I have done some of these, only to end up showing it on a lower resolution projector or people wanting DVDs rather than BluRays. No software is going to add detail to the source, so I would choose not to scale the lowres media and make it more of a picture in picture format than trying to scale to full screen.
-
Are the jagged lines in the preview window? If so, double check you are using Best and Full for the quality to compare. When rendering, you need to set it from Good to Best in the Project properties for “full-resolution rendering quality” setting, since you are re-sizing content on the timeline.
-
How did you stabilize the video? Did you bypass the plugins in the preview window by mistake?
-
I’m not sure, if it is when you compare it to v2. I had v3 SAL (stand alone version), so the CMOS fixer was one of the reasons I upgraded. You should be able to download the trial to try with your footage and see if it helps.
-
Make sure to follow the tutorial video, because their recommendation was not as straight forward. You add the CMOS Fixer plug-in first in the chain and then turn off Rolling Shutter Compensation in the stablilizer plugin options.
I normally use the standalone version to batch convert my son’s soccer video and I upgrade from v3 to v4. I was able to get the SVP suite in the upgrade, so I have the plug-in version too.