[Dave Smith]

I just installed Pro version 9e 32-bit and now I’m so sorry I didn’t read the forum here first. I can’t even get 9e to open. Now I have to waste my time and uninstall 9e, reinstall 9c or 9d, and most likely have to re-install all my plug-ins and probably re-activate them, a total pain in the rear end. Just to get back to a program that will HOPEFULLY open!

I work in IT and hate to be the cutting edge, so I usually sit back for a while, e.g. never even bothered looking at or trying Vista, just stayed with my XP.

Anyway, you seem to be blaming complexity of software. I work in the software market, and I can tell you two things that have been happening more and more over the past few years to many companies.

1- outsourcing to overseas shops- the quality is super low, the capabilities and processes are not understood, old code is not managed by the people that wrote it, pieces start to get corrupted, and things continue to go downhill from there. Executives are under pressure to show cost saving so they take the easy way out, at first just showing they have cut down the rates paid to the developers, but as time goes on more and more projects take longer and longer to get done due to the communication issues, the delays of not having constant work going on in the same time zones, etc. Just like everything else in life we start to outsource everything to people somewhere else and sure enough the quality suffers more and more. It’s not rocket science.

2- those programmers who do stick around and who get to work on the software here at home are less and less managed and rely less and less on formal methodologies. QA departments are mostly outsourced, otherwise the pay is dirt cheap and they get no support from management when they point out all the issues with the code. Management pushes things through to release anyway and overpowers QA, who often get code that has supposedly been unit-tested by developers who actually don’t have a clue how to test anything and no managers who will force them to do any formal testing.

I know, I see this every day. Development departments will argue all day long that they do unit testing and that QA is adequate, yet most of them truly don’t know what they are talking about. The proof is staring them in the face yet they deny it. I’ve seen this at most of the top software companies around, it’s epidemic. It’s evident in year-long issues with corporate websites like a particular hotel and airline website I use all the time. Functionality goes down all the time while serious issues and bugs continue to proliferate. The higher the version number of some IT-centric software the worse the quality. It’s getting worse across the board, not better.

Anyway, just thought I’d give a very likely reason behind all the issues we’ve been seeing with Sony Vegas in the past few releases. Sadly I do not expect it to get better. The only way it would (if my assumptions are correct) is to get back the original programmers, let them fix the code, even if they have to get rid of or redo recent features, and then build on top of a stable base. I doubt this will happen, and I expect it to get worse not better.

If Apple or Adobe are doing a better job perhaps they have a stronger methodology or have not been as quick to just outsource everything as a cheap and easy way to show some kind of savings.

[Dave Smith]

I’m actually using 9c, and I run malwarebytes all the time, it doesn’t find anything.

I think I was ok when I was running 9b (can’t remember when I switched to 9c) but I know that since I have been running 9c I did 1 project, but it was a month or two ago and I was having to render tons of short parts of the project as I went along and play it in an external player to see what I was doing since preview was slow. At the time I thought it was due to the large size of a couple of the clips I was using. However, now that I started a new project as soon as there’s a psd image on one track or any kind of transition on the main track things get “choppy” or stutter, so now I know it’s not the size of the clips files but something else.

Since I reset all the settings in 9c a couple of times I have to assume it’s not something I mistakenly hit. I tried some other settings previously like pre-rendering and a couple other hints I found somewhere else to change a couple settings within Vegas but to no avail, that’s when I just reset evertything back to factory defaults and reset Vegas with ctrl-shift during launch

So if anyone has any other suggestions or thinks it would be worth trying to go back to version b I could use your suggestions.

Other than that, maybe I will try to go all the way back to 8 and see what happens.

Please advise if you have any other suggestions of what I can try

[Dave Smith]

Ed

Thanks for looking into this and finding a solution (an update was provided and fixed the problem).

Tremendous support!

-Dave

[Dave Smith]

sorry, just a few more details (spending hours on this)… I removed the camera track and was able to render the whole work area or project successfully, then I carefully added a camera track (with no motion in it) and that worked too. As soon as I added a 2nd camera position and started using the tumble track and/or dolly it seemed that the rendering was again cut short for both project or work area. I’d successfully used these camera position changers before but it seems like all of a sudden I can’t render if they are being used.

I tried this on another computer and had the same result.

Any suggestions?

[Dave Smith]

and one more thing, when I said in the original post the projects “mostly rendered” I meant that most of my projects rendered completely.

[Dave Smith]

to add some more detail here, I’ve tried “reinstalling” ProAnimator (deleted old folder under program files, replace with unzipped folder from install zip file), and tried resetting preferences… and then tried re-rendering one of the projects over and over again. Each time it made it between 16 to 22 frames before stopping, regardless of the fps, resolution, render file location or name, and doing project or work area.

I hope there’s some way to figure out the issue since again, this is multiple different projects most of which rendered fine before.

I’ve looked for a location of temp files or some other way to “reset” the application but can’t find anything

[Dave Smith]

Hello

Thanks for your reply. I think some of it has to do with the alpha but I had tried both with and without alpha so some of it may not be related to alpha. I’ve tried rendering at different resolutions and frame per second settings and simplifying the edges to basic flat edges and that seems to make some difference.

I’ll continue to experiment but now I have a larger issue with crashes during rendering on multiple different projects, so I will post that one and hope for a resolution to it.

Thanks again

[Dave Smith]

hello

I really appreciate your help. This was not an imported graphic, just fonts I chose after I typed directly into the 3-d text of ProAnimator. Toying with the settings for that spike buster did help eliminate the spikes although as I moved the setting up and down it sometimes created more spikes. But I did find a setting that seemed to work for the fonts I was using. Now I just need to make them a bit sharper – some of the round letters look pretty jagged / bitmappy, e.g. the O.

-Dave

[Dave Smith]

By the way, I realize I made a mistake when suggesting you can’t see which animation is in use – I realize I forgot that it is displayed within the list at the top above all the choices. In any case, I am finding again and again that I get the spike below the letter, most of the time it’s on the O, and also it seems that trying different object animations causes this to happen, or even going to other programs in windows and then returning to this one (Pro Animator) at which time the spike can be seen. Sometimes the whole letter disappears, leaving the rest of the word without the O (even though going into edit text still shows the whole word with all the letters).

[Dave Smith]

anyone?