Comments

zdogg wrote on 8/13/2018, 3:09 AM

Let me say that you may know a lot more than I do, as an old IT guy, so, good to know that. I don't want to insult anyone's intelligence or good efforts.

The reality, at least mine, after also building a lot of machines and trial and error, is that things have a way of sneaking into your system, be it viruses or screwed up registry or what have you, and really the ONLY way to get going again is to reinstall, and this might have ZERO to do with Vegas, as I and others similarly situated aren't having these problems, we might have problems, other problems, but not this one.

Third party, well, yes, you'd think that they would need to be engaged, is your Vegas default to open last project or some default template? Or just a blank slate new project? I don't really know your settup.

OK, if you have 'thrown in the towel' (what we say for 'quit') or given up, that's fine, let's see the next version. Sorry you are having this trouble.

BTW, reinstall of windows, for me, is just a must do (I don't like it either) every couple of years it seems, just like going to the dentist, you don't want to go, but you don't want your teeth to fall out either, just the "nature of the beast" we say. Cheers!!

 

JJKizak wrote on 8/13/2018, 8:18 AM

Let me say that you may know a lot more than I do, as an old IT guy, so, good to know that. I don't want to insult anyone's intelligence or good efforts.

The reality, at least mine, after also building a lot of machines and trial and error, is that things have a way of sneaking into your system, be it viruses or screwed up registry or what have you, and really the ONLY way to get going again is to reinstall, and this might have ZERO to do with Vegas, as I and others similarly situated aren't having these problems, we might have problems, other problems, but not this one.

Third party, well, yes, you'd think that they would need to be engaged, is your Vegas default to open last project or some default template? Or just a blank slate new project? I don't really know your settup.

OK, if you have 'thrown in the towel' (what we say for 'quit') or given up, that's fine, let's see the next version. Sorry you are having this trouble.

BTW, reinstall of windows, for me, is just a must do (I don't like it either) every couple of years it seems, just like going to the dentist, you don't want to go, but you don't want your teeth to fall out either, just the "nature of the beast" we say. Cheers!!

 


And if you re-install Windows and you don't like what it's doing (you must watch it continuously) re-install it again after double zeroing your hard drive. Windows leaves small control files on a special section of the hard drive that must be removed but not sure if they do this anymore.

JJK

 

OldSmoke wrote on 8/13/2018, 9:33 AM

I will not talk about or do anything more for V15 - not one second

@ritsmer I am confused, are you an VP14 or 15?

Proud owner of Sony Vegas Pro 7, 8, 9, 10, 11, 12 & 13 and now Magix VP15&16.

System Spec.:
Motherboard: Intel DX79SR
Ram: G.Skill 8x4GB DDR3 2133 (running at 1600 and lower latency)
CPU: 3930K @ 4.3GHz (custom water cooling system)
GPU: 1x ASUS Fury-X
Hard drives: 4x 2GB WD Red in RAID 5 (with Hot Spare), 2x Crucial 256GB SSD in RAID 0 (mulitcam project drive), 1x Samsung 850 Pro 256GB SSD (System), 1x Crucial 64GB SSD (temp files and swap file), 1x 3.5" Hotswap Bay, 1x LG BluRay Burner
PSU: Corsair 1200W
Monitor: 2x Dell Ultrasharp U2713HM, 1x Sony HDTV 32" preview monitor

ritsmer wrote on 8/13/2018, 10:02 AM

I'm on V15 b384.

As I like to support the Vegas development - and also am curious what improvements are made from version to version - I always buy every version. How could one want that Vegas continues without supporting it?

Therefore I know that everything was fine in V13 and that the issue showed up - not immediately in V14 - but just after the first update of V14 - and has continued through the V15 versions. I could have left V14 and 15 unused on my machine and continued using V13 - but at that time I had started making DJI drone videos and therefore I needed 14 (the DJI videos did not behave well on 13).

But never mind - let us put this behind us and look forward to V16 which I will buy as soon as the e-mail arrives here 🙂

OldSmoke wrote on 8/13/2018, 12:28 PM

But never mind - let us put this behind us and look forward to V16 which I will buy as soon as the e-mail arrives here 🙂

Well, there is no guarantee that it will be better with VP16 if we can't establish what is wrong with your setup and VP15.

Proud owner of Sony Vegas Pro 7, 8, 9, 10, 11, 12 & 13 and now Magix VP15&16.

System Spec.:
Motherboard: Intel DX79SR
Ram: G.Skill 8x4GB DDR3 2133 (running at 1600 and lower latency)
CPU: 3930K @ 4.3GHz (custom water cooling system)
GPU: 1x ASUS Fury-X
Hard drives: 4x 2GB WD Red in RAID 5 (with Hot Spare), 2x Crucial 256GB SSD in RAID 0 (mulitcam project drive), 1x Samsung 850 Pro 256GB SSD (System), 1x Crucial 64GB SSD (temp files and swap file), 1x 3.5" Hotswap Bay, 1x LG BluRay Burner
PSU: Corsair 1200W
Monitor: 2x Dell Ultrasharp U2713HM, 1x Sony HDTV 32" preview monitor

Kinvermark wrote on 8/13/2018, 12:34 PM

+1. Clearly this is an esoteric problem, and if it gets fixed without proper diagnosis it will only be "by accident."

ritsmer wrote on 8/13/2018, 3:29 PM

A good point - but - I have been fighting this problem since 1. update of V14 - used extremely much time trying to track down the issue and also some good money for 2 new GPU cards - have started quite a few posts about it like "Vegas has stopped working all by itself" - and - this is probably the worst: unfortunately I have faithfully filled in hundreds of "error reports" - all not received by support, I learned yesterday - and so just making a huge fool out of myself. Customer care - anyone ?

There have been other "Vegas stopped working all by itself"-like posts from other users - IMO some of them trustworthy - so even if the issue is rare it is not only in my HW/SW setup.

I also filed a "real" ticket linking to my- and one or two of the other users- posts in the forum - with deep silence as the only answer. EDIT: It would have been so easy to send me a Vegas with tracing facility which probably would have revealed the issue in hours - but no.

So - after all this - I throw in the towel for good - and with a good conscience.

Please accept that I can and will not participate further in this issue.

Kinvermark wrote on 8/13/2018, 3:52 PM

1) Error reports: I agree, this "feature" should have been fixed or removed by now. It has been like this for a LONG time. Experienced forum members are aware of it, and cynical users don't expect any help anyway, but... just looks bad.

2)Also agree: sometimes it is more practical to walk away and try something else. If you ever reconsider, perhaps find a local friend who has a reliable working setup just to build confidence that it can be done. It is one thing for some of us here online to claim our systems work fine (mine does), but it's better to see it in person, and have a chance to interact with the program in a satisfying way instead of the frustration of unexplained crashes.

 

 

 

fifonik wrote on 8/13/2018, 3:56 PM

I understand and honour your decision, however I'd say it is strange.

You've already spent so much time trying to find the source of the issue and do not want to spend another 30-45 minutes for checking two the most important steps (disabling GPU completely and re-installing OS).

I'm NOT suggesting to re-install your normal OS (that is pain and I would not do this myself). Just connect a single drive and install fresh W10 + chipset drivers + graphic drivers (you will delete OS folders after testing). You can also try to download Win 10 PE (as Hiren's BootCD PE for example), put it on flash drive, load from it and try to install GPU driver + Vegas (I'm not sure if Vegas can be installed on Win PE as some programs refuse to do so).

P.S. If you do not find/report the issue you cannot be sure that it is fixed in the following Vegas version (report would not guarantee this as well, but usually chances are better).

ritsmer wrote on 8/13/2018, 4:31 PM

@fifonik being a MSc in IT and electrical engineering I have, of course, not only disabled the GPU. I have tried many driver versions too - and after this I bought an AMD card and started from square 1 trying different drivers, disabling enabling etc - still crashing I bought a new Nvidia card and started from square 1 enabling, disabling, dynamic RAM etc etc. etc and etc.

As to Windows: I do really take much care that I only install the very most needed programs - and do not install, try and uninstall anything on that machine. Of course I know Win PE but having Vegas + PE installed is not my everyday environment etc

And sometimes enough is enough and the issue with my hundreds of error reportings in vain did hit the nail on the head for me and it has reduced me from being a devoted Vegas FAN since V3 to an anonymous user.

Please do not ask me to I use more time than these nearly 2 years - and please accept that this was the last post.

OldSmoke wrote on 8/13/2018, 5:25 PM

Please do not ask me to I use more time than these nearly 2 years - and please accept that this was the last post.

Sad but understandable. Would have been nice if we could have isolated the problem; still a lot of open questions.

I was “out there” for a while too, used Resolve for projects where I didn’t need scripting but I must say it’s a pain too. Extremely clunky when it comes to importing media and working with an external monitor; node based editing is also not my cup of tea. I was glad to see VCE was added and so far I am happy with Vegas 15. I actually managed to crash Resolve a couple of times, may have been my fault though. Anyways, good luck “out there”.

Proud owner of Sony Vegas Pro 7, 8, 9, 10, 11, 12 & 13 and now Magix VP15&16.

System Spec.:
Motherboard: Intel DX79SR
Ram: G.Skill 8x4GB DDR3 2133 (running at 1600 and lower latency)
CPU: 3930K @ 4.3GHz (custom water cooling system)
GPU: 1x ASUS Fury-X
Hard drives: 4x 2GB WD Red in RAID 5 (with Hot Spare), 2x Crucial 256GB SSD in RAID 0 (mulitcam project drive), 1x Samsung 850 Pro 256GB SSD (System), 1x Crucial 64GB SSD (temp files and swap file), 1x 3.5" Hotswap Bay, 1x LG BluRay Burner
PSU: Corsair 1200W
Monitor: 2x Dell Ultrasharp U2713HM, 1x Sony HDTV 32" preview monitor

Deva-Bida wrote on 8/14/2018, 12:34 AM

I'm running VP15 on this off the shelf gaming PC. (No longer for sale, but you can click to read the specs.)

iBuyPower

No crashing, except if I have a project primarily of AVDHD cam files and with a few prores files, one of the prores files my lose connection with the app isn't active, and on occasion in those circumstances, hang.

All in all, very stable for this new user so far.

(Aside:I really like the mixing console for managing multi-cam cutting where I may need to mix in bits from several cameras.)

I wish luck to those struggling with issues. I just wanted to offer my experience.

Turd wrote on 8/14/2018, 11:01 AM

At the risk of sounding like a complete Vegas fan boy, which I am, I very much like and appreciate the whole Vegas experience. I've worked with every version since Sonic Foundry's Vegas Video 3.0. For reason(s) I can't explain, I rarely run into a crash. Not saying -- at all -- that I'm better than everyone else -- just stating one of the reasons I've stuck with Vegas for so long. Is Vegas perfect? Well, yes and no. I think it's perfect for the price, but EVERY editing software has annoyances. The trick is to find the right balance between what fits your needs for the price.

I think pointing out issues is a wonderful thing -- when it's done constructively. But "bashing" something really isn't necessary. Here's something I don't like about Vegas' latest versions: Gal-dang, I wish "View transform" in "Project Video Properties" is turned off by default or at least is a property setting that remembers how I set it last when I start a new Vegas project. It's a setting that keeps catching me off-guard and I have to remember to change it with every new project I start! That's constructive -- and I'm not calling anyone an idiot. For all I know there's a reason Vegas works that way and I'm the idiot for not understanding why!

I can't wait to see V16! I hope it's not rushed, I hope it has HDR built-in (at least HLG, but Dolby Vision sure would be nice!), and I hope ALL the CHOICES on how to pay for Vegas never go away. Will 16 be perfect for everyone in every circumstance? Everyone knows that answer. Given Vegas' track record, I, for one, will most likely not be disappointed.

 

Note to self (everyone else please look away -- the note that follows is a reminder for mine eyes only): Figure out a clever, kick-booty signature that suggests I'm completely aware of how to properly and exhaustively party on and that I, in fact, engage in said act on a frequent and spontaneous basis.

fr0sty wrote on 8/15/2018, 1:51 AM

HDR is indeed in 16, Magix has already announced that... I couldn't say if Dolby Vision will be supported, though I personally wouldn't think it would be considering it is proprietary tech that would have to be licensed, whereas standards like HDR10 and HLG are open source. HDR10 seems to be the most popular as far as adoption goes currently, but if other standards don't make it in at launch, it is possible they can be added in updates afterwards.

Turd wrote on 8/15/2018, 9:32 AM

HDR is indeed in 16, Magix has already announced that... I couldn't say if Dolby Vision will be supported, though I personally wouldn't think it would be considering it is proprietary tech that would have to be licensed, whereas standards like HDR10 and HLG are open source. HDR10 seems to be the most popular as far as adoption goes currently, but if other standards don't make it in at launch, it is possible they can be added in updates afterwards.

Oh, cool! I somehow missed that HDR announcement. Thanks for the info, fr0sty!

I'd certainly be quite happy with HDR10, HDR10+ and HLG support on 16. Dolby Vision would be icing on the gluten-ladened confectionery pastry. However, mp3 also requires a license, and that's built-in to the Vegas soup, so perhaps my hope for Dolby Vision in 16 is not for naught.

Note to self (everyone else please look away -- the note that follows is a reminder for mine eyes only): Figure out a clever, kick-booty signature that suggests I'm completely aware of how to properly and exhaustively party on and that I, in fact, engage in said act on a frequent and spontaneous basis.

Wolfgang S. wrote on 8/15/2018, 2:48 PM

Do not think that most of us would like to pay Dolby Vision. That is not even included in Resolve. I will be happy with HDR10 what is the most important one, and maybe HLG.

Turd wrote on 8/15/2018, 3:37 PM

Do not think that most of us would like to pay Dolby Vision. That is not even included in Resolve. I will be happy with HDR10 what is the most important one, and maybe HLG.

Amen, bro. I don't know if HDR10+ will ever really catch on, but HLG is certainly proving to be a rising rock star. I just wish HLG would extend black level detail like the other HDR flavors do : (

But I'm talkin' 'bout Dolby Vision being built into the normal cost -- not at extra cost!

Dare to dream...

Note to self (everyone else please look away -- the note that follows is a reminder for mine eyes only): Figure out a clever, kick-booty signature that suggests I'm completely aware of how to properly and exhaustively party on and that I, in fact, engage in said act on a frequent and spontaneous basis.

fr0sty wrote on 8/15/2018, 6:36 PM

As much as Dolby is notorious for charging for just about everything, and due to the fact that Magix apparently isn't willing to pay what Dolby wants to license the dolby 5.1 ac3 codec, so all we can export is stereo, I wouldn't count on it. I don't see Dolby Vision winning the format war anyway... due to its proprietary nature. HLG, with its backwards compatibility with Rec709 displays, is a likely candidate, especially for broadcast. For film and internet, HDR10+ may win out.

Turd wrote on 8/16/2018, 10:20 AM

As much as Dolby is notorious for charging for just about everything, and due to the fact that Magix apparently isn't willing to pay what Dolby wants to license the dolby 5.1 ac3 codec, so all we can export is stereo, I wouldn't count on it. I don't see Dolby Vision winning the format war anyway... due to its proprietary nature. HLG, with its backwards compatibility with Rec709 displays, is a likely candidate, especially for broadcast. For film and internet, HDR10+ may win out.

Almost all my work is in broadcast, so HLG support is quite important to me because of how little impact it has on the current broadcast workflow and equipment. The other HDRs would be a nightmare to implement, but I still like choices -- especially for non-broadcast projects. I sure hope HLG shows up in 16!

About your stereo comment, I assume you're talking about being able to render ac3 stereo specifically. I'm sure you're well aware that several-channel audio rendering is, indeed, possible, just not in ac3. I regularly edit 8-channel audio in a rendered .mxf file for broadcast. Yes -- the fact that we can't render 5.1 ac3 audio guides a thinking person's prediction to no Dolby Vision in 16. Wouldn't it be a pleasant surprise if we get 5.1 ac3 AND Dolby Vision? Wow!!!

Note to self (everyone else please look away -- the note that follows is a reminder for mine eyes only): Figure out a clever, kick-booty signature that suggests I'm completely aware of how to properly and exhaustively party on and that I, in fact, engage in said act on a frequent and spontaneous basis.

zdogg wrote on 8/16/2018, 1:01 PM

Apparently there are some workarounds, if you have the dolby ac3 plug for DVD Architect or older vegas, something about copying from one folder to another...look that up here on these boards.Also, someone did mention Sonic Foundry's inclusion of ac3 encoding.

fr0sty wrote on 8/16/2018, 1:34 PM

"I  sure hope HLG shows up in 16!"

If I had to guess, they are going to focus on HDR10 at first, and then work on adding HLG later once they know HDR10 is working well.

As for Dolby, I think a lot more than just Vegas are going to skip it. Dolby wants you to use their tools to do Dolby Vision, I don't see them licensing the tech out to many people, especially not in an affordable NLE. Not to mention, cost aside, the tech requires that you be able to set individual metadata parameters per scene, which would require a retooling of how Vegas does things. HDR10 and HLG are far easier to implement.

Turd wrote on 8/16/2018, 2:41 PM

"I  sure hope HLG shows up in 16!"

If I had to guess, they are going to focus on HDR10 at first, and then work on adding HLG later once they know HDR10 is working well.

As for Dolby, I think a lot more than just Vegas are going to skip it. Dolby wants you to use their tools to do Dolby Vision, I don't see them licensing the tech out to many people, especially not in an affordable NLE. Not to mention, cost aside, the tech requires that you be able to set individual metadata parameters per scene, which would require a retooling of how Vegas does things. HDR10 and HLG are far easier to implement.

That makes sense. I guess we'll just have to agree to agree!

Oh -- and thanks zdogg for your 5.1 ac3 suggestion!

Note to self (everyone else please look away -- the note that follows is a reminder for mine eyes only): Figure out a clever, kick-booty signature that suggests I'm completely aware of how to properly and exhaustively party on and that I, in fact, engage in said act on a frequent and spontaneous basis.

JJKizak wrote on 8/16/2018, 6:34 PM

I just hope all of these new versions will work in Windows 7 Pro 64 bit.

JJK

fr0sty wrote on 8/16/2018, 10:27 PM

I don't see why not.. Vegas 15 doesn't rely on any features that are exclusive to Windows 10, nor should the new features, except for HDR, but even then there are workarounds (using 10 bit capable output device).