Hi mantrum, 

I have added this information to the post above, thanks for reminding me. 

Best, 
Paul

I'm running DP9 and my slave VEP6 machine crashes when opening a new project.  I even installed your patch from this morning and restarted both machines, but no love. 

Master machine MBP running 10.12.4, Slave machine MBP running 10.11.6.

@Paul said:

Hello everybody, 

Very sorry about the trouble, this is now fixed with a new update, available in your User Area. 

Alternatively, here is the direct download link for VE PRO 6.0.16012 for macOS, please restart the computer after applying the update!

Best,
Paul

Thanks Paul! I was hoping to find this when I woke up today, all my networks work again. 😊

Yes, I tried that patch and restarted both machines. Nothing improved. Still crashes as soon as instruments start to load under DP9

Thanks for the fix, but I feel like VSL didn't treat this issue seriously enough. Their update friggin broke the OS networking! That's a big deal. I lost a whole day to this, yesterday, and it never occurred to me that a minor bugfix update on some music software I did the night before would have broken networking. You guys should have emailed all your customers to hold off on the upgrade, once you knew about this issue. You should still email them, because many people won't think to check the VE Pro forums. And the update will never be picked up by the automatic update feature in VE Pro, because networking is broken.

I understand that bugs slip through (though I'm still angry about such a serious one), but you folks need to communicate with your customers when such a catastrophic one slips through. I still have received no emails from VSL about this. There is nothing on any of your social media.

@Paul said:

Hello everybody, 

Very sorry about the trouble, this is now fixed with a new update, available in your User Area. 

Alternatively, here is the direct download link for VE PRO 6.0.16012 for macOS, please restart the computer after applying the update!

Best,
Paul

 

Still crashes for me even after reset.  I've sent a crash log.

@ericgoetz said:

Thanks for the fix, but I feel like VSL didn't treat this issue seriously enough. Their update friggin broke the OS networking! That's a big deal. I lost a whole day to this, yesterday, and it never occurred to me that a minor bugfix update on some music software I did the night before would have broken networking. You guys should have emailed all your customers to hold off on the upgrade, once you knew about this issue. You should still email them, because many people won't think to check the VE Pro forums. And the update will never be picked up by the automatic update feature in VE Pro, because networking is broken.

I understand that bugs slip through (though I'm still angry about such a serious one), but you folks need to communicate with your customers when such a catastrophic one slips through. I still have received no emails from VSL about this. There is nothing on any of your social media.

Well said. I ended up missing the dealine for a project, and two days of reinstalling software because I needed to do a clean install of Sierra. I discovered that the VEPro 6 update was the issue because I happened to be on a forum and saw posting about it. A simple email would have saved me from all of this, as I could have downloaded the patch. VSL still hasn't communicated this info....I wonder how many composers around the globe are frustrated? Not good. On the other side of the coin, it's my own fault for jumping the gun and updating right away...should have known better.

Hi.

A fellow composer has just told me about this. I installed the faulty update last week.

A Mac repair man earlier today spent two hours at my studio trying to mend my computer. He had never come across a problem like it. The only way the internet could be accessed was through Chrome - Mail, Safari, iTunes, App Store, etc. wouldn't connect - and my main Mac Pro wasn't being seen as a shared computer by the other Macs on my network.

£210 his time cost me. He left without having fixed it and, on his advice, I am now in the process of a clean install.

I have to admit that I really am not very happy at all.

VSL, can I please ask: why didn't you email everyone to inform them that this update was buggy? If you had have done, I would have been aware that the fault lay with your update and I wouldn't have needed to get anyone out to try to fix my computer. If you'd like to reimburse me the £210, I'll happily forward you macman.co.uk's invoice.

Nick

Hello, 

We are very sorry that this bug slipped through, it resulted from an attempt to increase efficiency, along with other essential bug-fixes that we have worked on for quite some time. 

Our developer team reacted the minute we saw the first report, on sunday morning, and the download numbers of the OS X version for this fix were about the same as with the previous version within 24 hours. 

The bug affected OS X users exclusively, and only after a restart of the computer.

Luckily, very few OS X users restart their computer on a daily basis, which definitely helped in this situation. 

All in all, 6 days after release and 4 days after the quick update, we received 3 reports about this problem, and there is this very thread with 17 entries from 8 users.

So before alarming tens of thousands of users (which would have been too late for most affected users anyway), we decided to let our automatic update service help out in this situation, which, from our perspective today, turned out to be a good decision. 

I fully understand that this is not a comfortable situation for everybody affected by this unfortunate bug.

Thank you so much for your input and help resolving it!

Best, 

Paul

2 days it cost me trying to hunt this down. Even took it to Apple who coudn't find the culprit !

I ended up doing a clean system install , not happy really doesn't cover it.