-
Hi and welcome to the Studio One User Forum!
Please note that this is an independent, user-driven forum and is not endorsed by, affiliated with, or maintained by PreSonus. Learn more in the Welcome thread!
Pro Studio 8 killed Vegas ?
- Thread starter John Vere
- Start date
Vocalpoint
Well-known member
Yes - these libraries are used by EVERYTHING on a typical Windows install. Keeping them tight should be standard maintenance.
VP
AAV
Active member
Thanks for posting this. This worked for me with Vegas Pro 22.
Craig Anderton
Well-known member
Dean Winter is now on my official list of guardian angels
I had a hard deadline for getting a promo video for MusicPro 26 done today. Don't know what I would have done without this fabulous forum!
Craig Anderton
Well-known member
Today's second reason for thinking this is the most useful forum in the known universe. Thanks VP!!
Vocalpoint
Well-known member
That one is a tad obscure - but updating this VC++ stuff is not well documented (at all) and even less is known about what to do, where to go to get these installers and the best way to "update" if a library is already present.
I stumbled across this script several years ago - but man - it is a lifesaver.
Brings a workstation right up to current in less than a minute.
If I had a nickel for every time I shared this with users of Native Instruments (Native Access) to get users squared up - it would be like winning PowerBall.
VP
TimC340
Active member
I just installed V8 on my studio computer and it included the C++ v14.50 install automatically.
Vocalpoint
Well-known member
To be expected - the 14.50 C++ came out back in November I believe.
Most (larger) new app installs usually do a VC++ check prior to a new install - and snags the latest if not already detected.
VP
But that’s what trashed Vegas.
I had been using Vegas. I closed it. Later I had some time and thought I would check out the Pro 8 deal. As I was installing it I found it strange that it asked me to install the C++?
Why? Is this version different than S1 7?
Anyway I installed it and got the new version up and running got bored and decided to get back to work on the Video.
Vegas would not open. Crashed every time.
I had a big hunch about the C++ and that’s why I posted this here and it looks like my hunch was right. I was also hoping that there would be other Vegas users here which thank goodness for that!
Otherwise I would be still trying to figure out how to use another Video editor.
Maybe the developers fixed it already.! It was obviously some bad code.
Last edited:
AAV
Active member
If you follow Dean Winter's link as posted previously, it looks like the Vegas issue has been going on a long time. Way before Fender came out with FSP8. My own experience with Vegas has been brutal. Nothing is as big a crashfest (speaking strictly from my own experience) as Vegas. I generally prefer to use the free Capcut if my own needs aren't too stringent. Fender has been taking a lot of heat, but saying it "trashed Vegas" is a bit of a stretch, IMO.
Craig Anderton
Well-known member
The first thing I did when I couldn’t resolve the problem was I already had Resolve installed.I agree. Sometimes I think Vegas is an advertising campaign for DaVinci Resolve
I attempted to take my clips and dump them in there. It seemed that I couldn’t drag and drop? So I import them and they were totally backwards on the time line even though they are sequentially numbered?
10 minutes later I started my normal routine of dragging the clips so they cross fade and the audio is smooth and flowing. Nope? 20 minutes later still can’t get that worked out so now I try and add transitions? 30 minutes later I give up and moved on to try Filmora. Much more intuitive and all is great and in no time at all I finally finished and go to export and it says that it will have a watermark? They said it was free!!
I finally find an editor called Lightworks that seems like it was promising. But once again. Can’t transition or slip edit or nothing!
Right then this thread netted me the solution with the link to the C++ installer. Problem solved and now Im back to work in Vegas and in 20 minutes finished the stupid video.
I actually have not had crashes since I figured out that I needed to have auto save turned on.
Don’t know why but it seems to work.
I also avoid DX plugins.
What appeals to me is Vegas works like a Daw. And the ability to open the audio in Wave lab is pretty critical to my workflow. WaveLab instantly makes the audio bang on -1.5 db at -16 LUFS. Takes 10 seconds.!
Ya it’s very outdated at all the glamorous stuff but I’m not making movies.
Filmora looks like you could create something modern and spiffy but im not paying for a subscription.
Resolve reminded me of Ardour. Free but totally weird and not intuitive.
SoxialAxxidense
New member
As a professional software developer I just can tell you that it's very unusual that a new installed C++ redistribution library will kill older software which relies on older versions of the lib. Normally it's like that the older software still uses the "old" version of the lib, since they are installed parallel on your system.
As I can read, the solution for you seemed to be to install the newest version of the libs for a piece of software that relies on an older version?
I really would like to test this on my sandbox system. Can you give me more information about all the versions of software you used?
BTW: I AM NOT THE DEVELOPER OF THE MENTIONED SOFTWARE
dean.winter
New member
Sure - for me it was just Vegas 23 and S1 8, followed by installing the latest VC++
Hmmm...sounds like what a Sony Vegas dev would say.....
Dean