"Premier on cloud is looking cheaper and cheaper."

Except that you end up having to use Premiere. :)

So, from what I'm seeing so far, VP13 doesn't load if you've got a cineform problem, or if you've got an ffdshow problem, or if you've not updated a stale version of a NewBlue product.

I personally had a startup error on a machine that I hadn't yet updated Vegasaur on, although the Vegasaur folks had sent out a notice and an update at least a week before Vegas 13 was released. Once I updated Vegasaur the error went away.

So far all of this is problems with third party products. The Vegasaur example shows that a vendor could be on the ball and proactive, but I doubt that either Cineform nor whoever develops FFDShow are going to tweak their code for Vegas' sake. Maybe it's more a matter of installation order with these, but I don't know.

Rob

Rob:

With the exception of Cineform, most of the 'conflicting' 3rd party software as suggested is stuff Sony is,or has, bundled with their software. Most are just VST plug-in's which Sony touts in its sales literature as for VP13 as having a latest VST plugin standards built into the software.

Uninstalling and reinstalling multiple software to try to figure-out the issue is not the answer. There are even people on this forum that have Cineform and VP13 is working...So it's hit and miss.

Every time the program crashes, Sony gets a crash report. So they know the score. Let's see what happens from here.

Between my tests this past week on VP12 and reading all the issues arising with VP13, I'm sticking with Adobe's CS6 apps - no monthly subscription costs and it just works.

Time to remove it completely as I dont' see any reason to give it a go any longer.

It's broken software IMO as much as I hate to admit it

Cliff

Vidmus:

When I send Sony a 'support' question, I can assure you I stick to the problem at hand and the troubleshooting performed. Here at the 'forum' a little more of my frustration comes out. Where were the 'beta' testers? Is Sony testing their software on optimized machines? And what about all the bug reports piling in? This crash on start began with Movie Studio 13 6-weeks ago.

This is a major release and not being able to start the program is an embarrassment to their brand. Again, we have a release with new features and the old problems still remain.

P.Films

Are you using Vegas Pro 13 or Movie Studio 13? They are I believe different products and handled on their respective forums.

WE are the beta testers.

I hate it when software companies get away with this. Aren't there LEMON LAWS in place for software??

Haven't used Vegas 13 Pro demo for anything more then a "Hey, it works, how awesome, and they still default to that hideous color!" but no install/startup errors for me.

I installed Vegas Pro 13.0 on Windows 8.1 without any issues at all. Everything works as it should. I don't have any GoPro software on this machine. No software manufacturer can shield themselves from what havoc other software manufactures can create. It's working fine for me.

BTW, CineForm has never played nice with Vegas Pro ever since Sony stopped shipping it with the product so I'm not surprised. Not sure how much GoPro has made this worse.

~jr

Working fine here. No GoPro materials.

Grazie

FWIW, the Cineform stuff that comes with GoProStudio *seems* to work just fine for me, but I installed it after installing VP13 just to see if I could break VP13 with it.

Rob

diverG:

I have Sony Movie Studio 13 installed on an 11.6" ASUS Laptop with Windows 8.1, and the trial of Sony Vegas Pro 13 on a 17" high-performance Windows 8.1 laptop. In other posts I was just trying to point out that SMS13 crashed on the ASUS computer 6-weeks ago and was reported to Sony. Same start-up crash errors. The programs share some core software, so my point was that Sony has not acted to fix the problem before VP13 was released.

Working fine here, as long as I turn off all acceleration stuff. SCS still can't do nVidia.

Nope, not working for me. I keep getting an error that says something like "document short file name is not valid." I've tried downloading, saving and downloading, changing file locations, etc, etc, - nothing! I talked with tech support and they were ZERO help as it was 10-minutes before closing time. I paid $150 bucks for this and want to use my new software, very disappointing Sony! I agree, not off to a good start.

SCS still can't do nVidia.

I guess that's not that was Vegas is meant to be played. 8)

welp, tried that hideous cloud purchase based NLE who shall remain nameless, and it is not bad at all. very smooth, NO hiccups, uses GPU, everything plays back smooth..... 10 minutes of tutorial videos and was able to transfer most of my vegas editing knowledge over to it and accomplish teh same thing... just in a different dress. Since Sony orphans broken software (my Pro12) and pushes NEW broken software, I'll probably leave vegas. Sadly.

> " The programs share some core software, so my point was that Sony has not acted to fix the problem before VP13 was released."

It may be that Sony can't fix the problem. It may be that GoPro needs to fix their problem of backward compatibility!

I can confirm the problem. Being a software developer, I have lots of test systems. I just created a new Windows 8.1 Pro 64-bit machine, I put GoPro Studio 2.0.1.319 on it and then installed Vegas Pro 13.0 Build 290 and when I started Vegas Pro 13.0 is crashed immediately. :(

If you rename C:\Windows\system32\CFHD.DLL to something else, Vegas Pro 13.0 starts up fine so it's definitely the CFHD.DLL file that is shipped with GoPro Studio. It's hard to say who's fault it is.

~jr

wwjd:

Don't be so quick to jump. I Produce several 1 hour national sports shows in the cloud based un-named software you speak of. and believe you me, there are plenty of problems on that side of the fence. Like, randomly making the .mxf format corrupt in every encode they put out in a cloud update that you can't undo that you only installed because it promised to fix a different problem that was irritating you day in and day out. The workflow is not as fast by a long shot ( though they're copying more and more of Vegas every day ). Every time an update with new features is released that will actively save you time and frustration in your edit, it's like playing Russian Roulette with your editing machine because you may or may not be hosed from some other random bug they've introduced making a serious glitch in your show. One time they changed it so that all the GoPro footage interpretted differently than the previous update, and I went back to make a change to a previous project, rendered it out, and everywhere the gopro footage was, it was completely random and out of sync but nothing had been moved or changed.

Pick your battles is all I'm saying, because you're not finding anything that's problem free...

Oh, and we only use it because the company is all apple based, and we still go through Vegas for the captioning with VASST Caption Assistant because captioning in Adobe is a joke as far as workflows are concerned compared to caption assistant in Vegas Pro.

Dave H.

To add to any confusion, I have GoPro studio 2.0.1 (free version) installed and Vegas 13 and it does not crash on me. I can playback and encode Cineform files. I installed the current GoPro Studio version on March 17th.

I am on Windows 7 so maybe that is something.

I have read other reports on this forum of problems with Cineform and all/most of those were with the Premium version of GoPro studio. I use the free version.

Thanks for the experienced feedback, FRIGIDNDEDIT! It really helps. I do think Vegas is faster and better in many ways.... just tired of developing a tick where I HAVE TO hit CTRL-S every 5 seconds or after EACH edit.

Do you feel you have to do that with that cooky cloud thing?

Since Sony orphans broken software (my Pro12) and pushes NEW broken software, I'll probably leave vegas. Sadly.

1) What makes you think Adobe is different? Which brings up point...

2) Then don't upgrade. Use 10, 11, 12, but not 13, whichever you want. Something you can't do with Adobe. You go their way or no way, so when you find broken stuff with their software (and you will, it exists in all software), no using the previous version.

"Do you feel you have to do that with that cooky cloud thing?"

Vegas auto saves, and so does Adobe. Although adobe's autosave feature requires you to stop doing anything before it saves, and it inhibits you from working in the application while the save occurs (on large projects this can take upwards of 15-30 seconds) right in the middle of your editing workflow. Not to mention that I've had it set to auto save every 10 minutes and then had a crash and it hadn't saved for the last 3 hrs for some reason, and I lost a lot of work. Everything has it's flaws, and if I hit Save every 5 seconds in Adobe I'd be waiting more than I'd be working. OH! and don't even get me started on audio conforms. I have 1TB of AVCHD Content from any given event. Audio conversions are going constantly in the bg w/o a way to stop them and then they corrupt half way though because you're supposed to be able to work while conforming happens in the background, then you dig in and find the .cfa conformed audio file, and remove it, and then it re-conforms and does it right, but then you load it on another machine and it says oh... let's conform all the audio again, and it starts eating up tons of space on the drive with conformed audio files that it's already conformed before.

- Vegas autosaves to a folder in a hidden folder on the pc and I shortcut to that on my explorer so if it ever crashes - there's a crash I was getting with the looksdx.dll (or something like that) in vegas whenever I create a folder while trying to save and I didn't know what was causing it for the longest time). All you have to do is sort by date modified and find the latest one (some random name unfortunately) and open it up and recover most of your work if Vegas doesn't ask you to restore the crash when it opens again.

That said, there are strengths to that cloud software as well, and we successfully create shows in it, but believe me when I tell you, sometimes it seems like adobe has their head up somewhere a lot darker and smellier than they do in the clouds...

Dave H.