|
Post by obsessive24 on Nov 10, 2011 17:38:16 GMT -5
If you have a specific question about Vegas, ask it here.
To better enable our tech-savvy members to help, please give as much information as possible, including (where appropriate):
PC or Mac? What operating system are you using? What version of Vegas are you using? What file formats are you importing as source? What file format are you trying to export?
|
|
|
Post by gnattery on Nov 11, 2011 11:18:19 GMT -5
Okay so, I get this weird glitch all the time in Vegas. Sometimes in the preview window, it will start inserting these random frames from other parts of the source, or from right next to that frame, so that it looks like the video is flicking backwards for a frame. This is annoying, but it wouldn't bother me so much if it didn't also end up getting rendered sometimes too. Sometimes replacing the individual clip is enough, and sometimes I'll have to totally replace the entire source file and reclip everything, which is very annoying. Sometimes that doesn't even work. Does anyone know what is going on here, and if there's anything I can do?
Oh, and I'm using Sony Vegas Pro 9 on windows 7. Importing and rendering to .avi files.
|
|
|
Post by obsessive24 on Nov 11, 2011 11:22:43 GMT -5
I'm no expert on exactly why that happens, but it seems to be a common bug that I've heard people complain about. In particular it seems to happen to people who import AVI files? Have you tried converting the AVIs into something else first, and whether that would help?
I never edit with AVIs in Vegas just because the timeline preview becomes really laggy. I convert the AVIs to MPEG-2s before I import, and don't usually get this stray frame problem.
|
|
eunice
Pub Enthusiast
Posts: 116
|
Post by eunice on Nov 11, 2011 11:28:12 GMT -5
I think, but don't quote me on this, it has something to do with b-frames. Happens in Premiere too working with .avi files.
Manually removing the stray frames with a razor on the timeline works (I assume you can do that in Vegas too?) if you don't want to go and convert everything or start over.
|
|
|
Post by obsessive24 on Nov 11, 2011 11:53:20 GMT -5
This might not be overly important on the practical how-to side when you're just trying to patch a leak on the ceiling, but I'm curious now. What are b-frames?
|
|
|
Post by gnattery on Nov 11, 2011 12:03:33 GMT -5
Hmm, converting sounds like a feasible work-around. What do you use to convert? Obviously I'd prefer to do so with as little quality loss as possible.
|
|
|
Post by obsessive24 on Nov 11, 2011 12:07:00 GMT -5
After trying a few freeware and trials, I actually ended up paying US$35 to get Prism, just because that's the best one I found. I'm sure there's freeware out there that'll do a decent job, although I don't really know what's good, sorry. Prism does give you a free trial though, maybe first give it a try and see if converting does indeed solve the problem?
|
|
eunice
Pub Enthusiast
Posts: 116
|
Post by eunice on Nov 11, 2011 12:08:31 GMT -5
With the caveat that this shit confuses the hell out of me so I'm probably explaining it all wrong...
b-frames are a compression thing, saving space by creating frames that rely on info from other frames to decode so it doesn't have to store more data? Which for some reason either don't decode properly in Premiere or Vegas when imported and randomly grab other frames instead or something?
And I'm using a lot of question marks, because I'm not entirely certain I've got that right.
|
|
|
Post by obsessive24 on Nov 11, 2011 12:08:54 GMT -5
Also: converting from web download AVI to MPEG-2? Quality shouldn't be an issue. MPEG-2 will usually sample your video at around 4000 - 9000 bits per second, so there shouldn't be much quality loss, if any at all.
|
|
|
Post by gnattery on Nov 11, 2011 12:09:14 GMT -5
Sounds good, I'll definitely try it out, thanks! I'd love to get this bug fixed, it's one of the main reasons I get discouraged from vidding and just drop the whole hobby for months at a time. I just don't want to *deal* with it.
|
|
|
Post by obsessive24 on Nov 11, 2011 12:09:58 GMT -5
Eunice - that does make sense, at least from my completely lay perspective.
|
|
|
Post by obsessive24 on Nov 11, 2011 12:11:28 GMT -5
I'd love to get this bug fixed, it's one of the main reasons I get discouraged from vidding and just drop the whole hobby for months at a time. I just don't want to *deal* with it. I so know what you mean. Which I think is a large part why once we find something that works for us, we tend not to fiddle with it or look at it too hard... because it's so hard to get everything working in the first place. And if your vidding process isn't smooth, it just ends up taking all the joy out of it.
|
|
|
Post by gnattery on Nov 11, 2011 12:15:06 GMT -5
Yeah, which is exactly why I haven't installed Premiere yet, even though I've been meaning to try it out and see if I prefer it for... about a year now? I already have vegas, and know how it works, and when I get an idea and want to start working on it, I can just throw things in vegas and away we go. Learning is hard!
|
|
|
Post by obsessive24 on Nov 11, 2011 18:05:43 GMT -5
Personally I think Vegas is a lot more intuitive than Premiere, and I'm coming from the perspective of someone who used Premiere for years and only switched to Vegas this year. By all means try both and see which one's a better fit for you personally; I tend to think Premiere isn't terribly user-friendly and there's a bigger tech learning curve than Vegas.
|
|
|
Post by littleheaven on Nov 13, 2011 1:42:20 GMT -5
I've had that issue when using DVD source from a region other than the one my DVD drive is set to. I have AnyDVD that region-decrypts on the fly, and I think that is what was causing the problem. I also had it once using DivX encoded source.
The way I got around it was to convert the source to lossless avi using either Lagarith or Huffy UV codecs and VirtualDub. It made for ENORMOUS source files but it did cure the problem.
|
|