-
how do I prevent this video corruption?
Gilles Gagnon replied 12 years, 11 months ago 5 Members · 22 Replies
-
Gilles Gagnon
August 20, 2013 at 2:04 pmlol… heaven and stress free ! Love it!
Thanks. I really liked the GPU for the significantly faster render times. Again, a feature I may have to forego.
Which card do you have? I purchased an NVIDIA specifically to reduce render / preview issues. no such luck.
Gilles
-
Stephen Mann
August 20, 2013 at 3:02 pm“Bug” is a touchy subject for me because many, many people use Vegas 12 with no problems at all. I just finished encoding six MPEG files for DVD’s and my biggest problem was keepng from mixing up the discs as I moved to the labeling workstation. Those white discs all look alike….
If you have to restart Vegas to get a clean encode, then something in your PC is corrupting the data in memory that Vegas is using. But it’s not Vegas. You can run resmon.exe to view the memory usage of all process that your PC is running. The one that increases the commit amount over time is your culprit.
I have Vegas on two workstations – on one the GPU never worked right, and on the other there’s no problem at all. But with a sufficiently fast processor, the GPU doesn’t really add anything anyway.
Steve Mann
MannMade Digital Video
http://www.mmdv.com -
Steve Rhoden
August 20, 2013 at 4:20 pmI dont use a GPU Card anymore. as i mentioned earlier, i go strictly
on Processing power alone.Steve Rhoden
(Cow Leader)
Film Editor & Compositor.
Filmex Creative Media.
https://www.facebook.com/FilmexCreativeMedia
1-876-461-9019 -
Gilles Gagnon
August 20, 2013 at 4:34 pmThe card you use is not GPU enabled? I thought most of them were nowadays. or… is it an older card?
Gilles
-
Norman Black
August 20, 2013 at 4:48 pm[Stephen Mann] “If you have to restart Vegas to get a clean encode, then something in your PC is corrupting the data in memory that Vegas is using. But it’s not Vegas.”
I’ll disagree with that. Bugs easily, and most commonly, exist where 99 of 100 or 999 of 1000 circumstances work but that one very specific situation fails. This is also why you have to be very careful fixing bugs.
Only processes running in kernel address space can possibly corrupt some other process memory without it’s consent.
Vegas is a very threaded, lookahead system and this makes reproducing an exact situation difficult if the issue is memory organization and corruption related.
-
Gilles Gagnon
August 20, 2013 at 5:06 pmIn respect to memory over-writing, I think Norman has a good point. Only kernel mode processes can stampede over other processes’ ram and… if this were the case, from badly written kernel modes application(s), the entire system would tend to crash and misbehave randomly, not just in Vegas.
very interesting topic.
my 2 cents.Gilles
-
Steve Rhoden
August 21, 2013 at 3:56 amYou are correct Norman, it is a deeply entrenched issue
with Vegas and one thats hard to reproduce, which makes
some users experience it and others dont.
It is a Sony Vegas issue, but Vegas is still the best…lol
(Show me the perfect software)Steve Rhoden
(Cow Leader)
Film Editor & Compositor.
Filmex Creative Media.
https://www.facebook.com/FilmexCreativeMedia
1-876-461-9019 -
Steve Rhoden
August 24, 2013 at 8:43 pmWhat GPU Card?….lol
Steve Rhoden
(Cow Leader)
Film Editor & Compositor.
Filmex Creative Media.
https://www.facebook.com/FilmexCreativeMedia
1-876-461-9019 -
Gilles Gagnon
August 26, 2013 at 7:35 pmIs there a method of turning off GPU globally for renders or must it be done for each render template?
Gilles
-
Gilles Gagnon
August 28, 2013 at 11:33 amUPDATE:
For what it’s worth, I’ve observed that this “corruption” appears much more frequently when I have 2 or more Vegas instances simultaneously opened or… when I’ve opened (and closed) more than one simultaneous session in an edit session.
I do this regularly. It’s Vegas’ not-so-charming method of providing us editors with a variety of edit timelines, found in other NLEs. The actual name for this missing feature escapes me.
Gilles
Reply to this Discussion! Login or Sign Up