Welcome Guest! To enable all features please Login or Register.

Notification

Icon
Error

Forum Jump  
VE Pro 5.2.12785 on Mac OS, VERY crashy
Last post Sun, Jan 05 2014 by Paul, 17 replies.
Options
Go to last post
Posted on Sun, Sep 29 2013 21:23
by MDesigner
Joined on Thu, Jul 24 2003, Chicago, Posts 124

I'm getting plenty of crashing when instances change (either deleting instances, or when the sequencer project changes and I tell VE Pro to load incoming data). I hope this is a known issue and it's being worked on! I can supply a crash log if needed.

Sam Hulick
Composer
http://www.samhulick.com/
Posted on Mon, Sep 30 2013 03:17
by Sami Boman
Joined on Wed, Mar 23 2005, Jyväskylä, Finland, Posts 207

I've got big problems here too. I just installed this latest version and it immediately stopped working. When first I open VE Pro it starts up fine. Then I open Logic Pro X and still everything is fine. But when I start to load a project in Logic, VE Pro starts to load it's first instance and it almost immediately crashes and I get an error message Vienna Enssemble Pro has unexpectedly quit (I'm not sure is the error message exactly this word for word because I get it in finnish). If I don't do anything for a while after this, Logic gives me the following error:

eLicenser Control - Error

Application '' has caused the following error:
 
An unknown interapplication communication error occured. In case the problem persists, please close all applications and restart your computer.

I've installed the latest elicenser version but it didn't change anything.

More information about my situation. When I opened another project in Logic VE Pro still behaved the same way but after it crashed Logic loaded the project otherwise ok and I didn't get the elicenser control error.

Posted on Mon, Sep 30 2013 07:42
by Paul
Joined on Sat, Aug 03 2002, Vienna, Posts 13475

HI Sam,

Please send the crash-log to

@Sami: I´d repair permissions on the system drive and check if there is another eLicenser protected plug-in loaded in your VE PRO, which could cause this error. 

Best,

Paul

Paul Kopf
Product Manager - Vienna Symphonic Library
Posted on Mon, Sep 30 2013 12:47
by winknotes_282
Joined on Mon, Dec 23 2002, Posts 221

I'm not sure the crashing is isolated to MAC OS either.  I'm running windows 7 and I'm getting crashes as well.  At first I thought it was with Finale but the same thing happens with Reaper. 

Does VSL dump some log or is it whatever the OS dumps that support wants to see?

Steve
Windows 10 Pro 64-bit
Finale 26
VSL SE/Synchron
Posted on Mon, Sep 30 2013 13:43
by Sami Boman
Joined on Wed, Mar 23 2005, Jyväskylä, Finland, Posts 207
Paul wrote:

HI Sam,

Please send the crash-log to

@Sami: I´d repair permissions on the system drive and check if there is another eLicenser protected plug-in loaded in your VE PRO, which could cause this error. 

Best,

Paul

I sent the crash-log to your support. For some reason MIR Pro has been giving me a hard time for a while now. It now and then fails to load and ingorms me that there is a problem with it's license.

Posted on Tue, Oct 01 2013 14:10
by rgmburia
Joined on Sat, Oct 01 2011, Posts 8
Hello,

PLEASE Help me!! I am using a mac OSX 10.6.8 I updated two programs PLAY 4 and VEPRO 5 to 5.2.12785 on saturday and now cubase 6 will not open it crashes before start up. It gets to ominfliter and crashes this is terrible.

I was going through help advice with PLAY 4 tech today but cubase 6 still does not open. I am starting to think VEPRO might have caused some errors now. Something has gone wrong can anyone help me.

It was working fine before any updates to any of the programs.

Cubase 4 opens and works why does that work and not cubase 6.

Who can help me fix this quickly.
Posted on Tue, Oct 01 2013 14:11
by rgmburia
Joined on Sat, Oct 01 2011, Posts 8
Here is part of the log

Process: Cubase 6 [1238]
Path: /Applications/Cubase 6.app/Contents/MacOS/Cubase 6
Identifier: com.steinberg.cubase
Version: 6.0.7.364 (6.0.7.364)
Code Type: X86-64 (Native)
Parent Process: launchd [143]

Date/Time: 2013-10-01 15:08:44.930 +0100
OS Version: Mac OS X 10.6.8 (10K549)
Report Version: 6

Interval Since Last Report: 45529 sec
Crashes Since Last Report: 13
Per-App Interval Since Last Report: 388334 sec
Per-App Crashes Since Last Report: 13
Anonymous UUID: 413C7087-D70A-479B-8B9C-39BB2C6507E3

Exception Type: EXC_BAD_ACCESS (SIGSEGV)
Exception Codes: KERN_INVALID_ADDRESS at 0x0000000124189d9f
Crashed Thread: 0 Dispatch queue: com.apple.main-thread

Thread 0 Crashed: Dispatch queue: com.apple.main-thread
0 ??? 0x0000000124189d9f 0 + 4900560287
1 dyld 0x00007fff5fc0c839 ImageLoader::link(ImageLoader::LinkContext const&, bool, bool, ImageLoader::RPathChain const&) + 201
2 dyld 0x00007fff5fc04d48 dyld::link(ImageLoader*, bool, ImageLoader::RPathChain const&) + 118
3 dyld 0x00007fff5fc08f68 dlopen + 490
4 libSystem.B.dylib 0x00007fff87a9be40 dlopen + 61
5 com.apple.CoreFoundation 0x00007fff8223eef7 _CFBundleDlfcnLoadBundle + 231
6 com.apple.CoreFoundation 0x00007fff8223de97 _CFBundleLoadExecutableAndReturnError + 1191
7 com.apple.CoreFoundation 0x00007fff822cb30e CFBundleLoadExecutableAndReturnError + 14
8 com.steinberg.cubase 0x00000001011e8e55 CSOLOISTExtendedAnalysis::~CSOLOISTExtendedAnalysis() + 69941
9 com.steinberg.cubase 0x00000001011e93f0 CSOLOISTExtendedAnalysis::~CSOLOISTExtendedAnalysis() + 71376
10 com.steinberg.cubase 0x0000000100402690 0x100000000 + 4204176
11 com.steinberg.cubase 0x00000001011d8e77 CSOLOISTExtendedAnalysis::~CSOLOISTExtendedAnalysis() + 4439
12 com.steinberg.cubase 0x00000001011e86b7 CSOLOISTExtendedAnalysis::~CSOLOISTExtendedAnalysis() + 67991
13 com.steinberg.cubase 0x00000001011e892e CSOLOISTExtendedAnalysis::~CSOLOISTExtendedAnalysis() + 68622
14 com.steinberg.cubase 0x00000001011e8a64 CSOLOISTExtendedAnalysis::~CSOLOISTExtendedAnalysis() + 68932
15 com.steinberg.cubase 0x00000001007c68ab 0x100000000 + 8153259
16 com.steinberg.cubase 0x0000000100d149c0 0x100000000 + 13715904
17 com.steinberg.cubase 0x0000000101277b99 CSOLOISTExtendedAnalysis::~CSOLOISTExtendedAnalysis() + 654969
18 com.steinberg.cubase 0x0000000100d16dbd 0x100000000 + 13725117
19 com.steinberg.cubase 0x000000010116b048 0x100000000 + 18264136
20 com.steinberg.cubase 0x00000001000d39c4 0x100000000 + 866756
Posted on Tue, Oct 01 2013 23:48
by studioj
Joined on Sun, Jun 13 2010, Posts 47
MDesigner wrote:
I'm getting plenty of crashing when instances change (either deleting instances, or when the sequencer project changes and I tell VE Pro to load incoming data). I hope this is a known issue and it's being worked on! I can supply a crash log if needed.

Also having a very crashy experience with VEP5...  AND i just updated to the latest version and my AAX64 VEP plugin is gone!  (and this was after touble shooting why it would not open my latest mframe).  How do I get it back?  reinstalling it is not adding it to the avid pro tools plugin folder and my sessions are not finding it.  Man this program used to be so stable....more stable than any of my other software.    What happened?  is it a mountain lion issue?  

Posted on Tue, Oct 01 2013 23:57
by studioj
Joined on Sun, Jun 13 2010, Posts 47
studioj wrote:
How do I get it back?  reinstalling it is not adding it to the avid pro tools plugin folder and my sessions are not finding it.

Ok third reinstall seems to have added the plugin back to the avid aax folder.  Weird!   PLEASE vsl, make stability a top priority on MAC....  It is currently my most unstable piece of software.  But so Vital!  I have do a little prayer everytime I do anything in an instance :)

Mac OS 10.8.4

Mac Pro 12 core 3.33

64 gigs RAM

RME interface

Posted on Wed, Oct 02 2013 00:23
by studioj
Joined on Sun, Jun 13 2010, Posts 47

update...  it seems that the latest installer adds it but crashes on open and the one previous REMOVES it but will open and let me open my mframes.  hoping i can find someone to email me the file and it will work...   is the installer broken then?  I'm watching the folder as it installs and it literally just erases the AAX plugin and does not put anything back in its place.  PT users beware!

Posted on Wed, Oct 02 2013 10:03
by Paul
Joined on Sat, Aug 03 2002, Vienna, Posts 13475

UPDATE: 

VE PRO 5.2.12794 has just been uploaded, the crashes should be fixed. 

Best,

Paul

Paul Kopf
Product Manager - Vienna Symphonic Library
Posted on Wed, Oct 02 2013 19:00
by studioj
Joined on Sun, Jun 13 2010, Posts 47

it works!  THANK YOU THANK YOU

Posted on Thu, Oct 03 2013 00:33
by MDesigner
Joined on Thu, Jul 24 2003, Chicago, Posts 124

Nope, new version still crashes every time I select an instance from the list and click "delete" (from within the VE Pro Server window). But if I uncheck the "preserve" checkbox, it removes the instance without crashing. I'll do that for now as a workaround. I'm in touch with support.

Sam Hulick
Composer
http://www.samhulick.com/
Posted on Thu, Oct 03 2013 02:46
by studioj
Joined on Sun, Jun 13 2010, Posts 47
MDesigner wrote:
Nope, new version still crashes every time I select an instance from the list and click "delete" (from within the VE Pro Server window). But if I uncheck the "preserve" checkbox, it removes the instance without crashing. I'll do that for now as a workaround. I'm in touch with support.

Bummer, hopefully they get that sorted soon.  i had a few crashes today also...  they all seem GUI related... clicking around doing something in the interface seems to trigger the crash.  BUT it was a huge step up from NOT opening my mframes at ALL.  So thanks VSL for getting the update out quickly.  

Posted on Sun, Oct 06 2013 00:17
by MDesigner
Joined on Thu, Jul 24 2003, Chicago, Posts 124

I haven't heard back from support. This thing is still very unstable when updating VE Pro with sequencer project changes. Paul, do you know anything about bugs still existing in this latest version?

Sam Hulick
Composer
http://www.samhulick.com/
Posted on Sat, Jan 04 2014 23:22
by arturek
Joined on Sat, Apr 30 2011, Posts 4
still crashes
can i downgrade to ve pro 4 ?
this is rediculous :(
Posted on Sun, Jan 05 2014 10:57
by Paul
Joined on Sat, Aug 03 2002, Vienna, Posts 13475

Hi arturek, 

I have already answered your mail to

We´d be happy to receive crash reports and more details about your system. I couldn´t find any previous reports from you, so maybe that´s something our developers can fix quickly. 

And as a user of VE PRO 4 who upgraded to VE PRO 5, you can install VE PRO 4 anytime. 

Only catch: You cannot open VE PRO 5 projects in VE PRO 4 (it only works the other way around). 

Best, 

Paul

Paul Kopf
Product Manager - Vienna Symphonic Library
You cannot post new threads in this forum.
You cannot reply to threads in this forum.
You cannot delete your posts in this forum.
You cannot edit your posts in this forum.
You cannot create polls in this forum.
You cannot vote in polls in this forum.