What are /r/SonyVegas' favorite Products & Services?

From 3.5 billion Reddit comments

Color space problems. It's 4:2:2 (10 bit) vs 4:4:4 (12 bit) color. I'm guessing your're recording in full range (there's a button in Fraps called 'lossless RGB' and a Full Range button in OBS) and losing some color info along the way. Or the opposite. I can't remember exactly the problem, but I know how we solved it here. We fixed the encoding with some ffmpeg re-encodes, then moved that step into encoding with some libx264 params in OBS.

Take a look at this overly technical thread on color space, then pick one and do everything in it. I like 4:4:4, but eh, I'm picky. Here's another link that gets in to it in a tangent about ffmpeg image sequences.

It should have an autosave and load it when you launch again vegas, but ONLY the first time you load vegas again.

One thing you can do if you haven't force closed vegas yet, is to install Everyhting search engine and search for *.veg files, if should detect several veg files from your projects, or presets, but one (or more, maybe it saves several autosaves) will be a 00000XXX.autosave.veg located in %appdata/local/sony/vegas or something like that. Copy it to another location and then try to force close and load again vegas, if it fails to load the autosave try to open your recent copy.

You've missed my point. The shutter speed is not actual. Shutter speed is not manually adjustable on GoPros. It's a simulated motion blur. At 120 frames per second, there is no actual motion blur to really speak of in the raw footage. The blur you're seeing is because 120fps are stacked onto one another when you speed it up in Vegas using their Resampling function. The 1/48th of second was just a reference, meaning that since it is a 24fps clip, creating a 180º shutter effect would mean to EFFECTIVELY have a 1/48th of a second shutter speed to create the specifically-desired amount of motion blur, but only if I had actually been traveling at the impossibly high speed the timelapse portrays (as I said originally).

Here...https://vimeo.com/96693933

...go to 1:15. It's the same timelapse, but a side-by-side comparison of it with and without resampling. Notice how the left side has motion blur and the right side does not, making the right side look like stop motion. The right side portrays what most people do - take a photo once every few seconds or so. I'm not doing that. I'm recording 120 frames per second so that the frames, when stacked, create a faux motion blur. The more frames you can shoot, the cleaner and more accurate this blur effect is.

Basically what I'm pointing out is that if you have a camera that is incapable of manual shutter speed settings or incapable of shooting long enough shutter speeds to create this effect, but that does give you the ability to shoot high frame rates, then this method will allow you to achieve the ever-popular 180º shutter motion blur effect. This isn't just about getting motion blur. If that were the case, my explanation would have been way shorter. It's about getting that SPECIFIC motion blur. If 180º shutter motion blur is not a concern for you, then this entire thread is probably moot.

I tried rendering in 320p just to check if it would render, but it stops at arounds 25%. Here are my specs 1 and 2

You're sure there is a video portion? MP4 can be just audio. I've had trouble with that when using certain freeware screen capture software, it will only record audio and all kinds of other errors. If it was a screen capture I recommend changing capture programs and using Open Broadcaster Software. That fixed my issues.

I've got the same thing. I'm running Windows 8. I found that it is some kind of an issues with the .NET Framework. I found that out by going to Control Panel -> Administrative Tools -> Event Viewer -> Windows Logs -> Application. In the list I found a few rows that said Error in the Level column. If you do this just after the Vegas crash it should be near the top. Here's the error I got:

Faulting application name: vegas130.exe, version: 13.0.0.453, time stamp: 0x55720ce9 Faulting module name: clr.dll, version: 4.5.27.0, time stamp: 0x545ca861 Exception code: 0xc0000005 Fault offset: 0x000000000006c854 Faulting process id: 0x2410 Faulting application start time: 0x01d0b18690883e08 Faulting application path: C:\Program Files\Sony\Vegas Pro 13.0\vegas130.exe Faulting module path: C:\Windows\Microsoft.NET\Framework64\v4.0.30319\clr.dll Report Id: e2261bcb-1d79-11e5-bed1-bcaec51e926c Faulting package full name: Faulting package-relative application ID:

You can see it's Sony Vegas Pro 130 from Faulting application path line and that .NET Framework is the problem from then next line. If the latter says something different try googling it.

~~Unfortunately I haven't been able to fix my problem yet. I've tried uninstalling .NET Frameworks, cleaning them, running the repair tool, but nothing helps.

Not a fix, but wanted to share a way to narrow down the possible cause.~~

EDIT: Found a fix here. As a developer that uses .NET I've always had my frameworks (almost) up to date, but apparently 2 months ago an update to 4.6 Preview, called 4.6 RC, came out. Apparently this version fixed whatever made Sony Vegas crash.

I had no frame of ref to how slow that video was.... my apologies. I do remember someone here asking about SUPER slow motion and it wasn't possible to vegas natively, either it was a plug in, https://handbrake.fr/ or some other app. ...that is, if I remember correctly

Uninstall and reinstall QuickTime using the installer found here: https://www.apple.com/quicktime/download/

If that doesn't help, try uninstalling QuickTime again and use version 7.6 instead: http://support.apple.com/kb/DL762

If both of those don't resolve the issue, I'd be curious to see if the camera came with its own app for handling the videos which can process them to an alternate format/file type. Also, if another app can open the media files.

Yes there is:

https://gyazo.com/6796bbe700845793660c5dba5bfe9618

Thats a movie of 1 hour and 50 minutes. Using the Ctrl down method shorten the video to 27 min, and then after applying the velocity envelope, you can increase the speed 300% more. In this case, it shorts the 27 min to 9 minutes.

The only thing is, the velocity envelope, only affect the video event, not the audio.

Look for the stabilization plugin.

Alternatively you could try hyperlapse outside of Vegas and then import the resultant footage.

On my previous system, less powerful than yours and I could deal with HD footage with no issue. My current system which I have no problem dealing with 4k footage.

So this is going to be something that can be fixed. It's not you.

Upgrade to 12:

http://www.amazon.com/dp/B008MIMHDU/ref=twister_B00HFDXM2S?_encoding=UTF8&psc=1

or 13:

http://www.amazon.com/Sony-Movie-Studio-13-Download/dp/B00I3MTI9Q/ref=sr_1_3?ie=UTF8&qid=1445094484&sr=8-3&keywords=sony+movie+studio

Not terribly expensive, and should have a bunch of new stuff and better interface over 9. Plus most/all of your stuff should be forward portable.