Vienna Symphonic Library Forum
Forum Statistics

185,110 users have contributed to 42,379 threads and 255,422 posts.

In the past 24 hours, we have 4 new thread(s), 12 new post(s) and 61 new user(s).

  • Vienna Ensemble 6 - So many years in the making and still the incarnation of unreliability

    Brand new iMac Pro - Brand new OS cleanly installed. Logic Pro Installed.

    Then one wanders off to the most dreaded task in the histroy of macOS -> Download and install VLS Stuff.

    This went quite well. Until I clicked the application icon. It crashes itself on launch. And it freezes Logic Pro.

    I think someone oght to give you a prize for actually achiving to provide unrelaible software for 6 versions in a row. Some record you got there ! It is 2018, people arent back in 2002 when it was normal to sit and debug audio software for days for it to work. Artist arent earning moeny with music anymore - they release it for "free" on spotify and have much less time for debugging badly written software. I have in all the years of using VSL never had ONE single day where your software did not get on my nerves. 

    Here is the crash thread...


    Thread 4 Crashed:: Dispatch queue:

    0      0x938df6e2 CFStringCreateCopy + 18

    1      0x939345c1 CFStringCreateByCombiningStrings + 209

    2           0x92d8784f _merge_array_string(void const*, void const*, void*) + 84

    3      0x9390a9d8 __CFDictionaryApplyFunction_block_invoke + 24

    4      0x9390a99e CFBasicHashApply + 110

    5      0x9390a8e1 CFDictionaryApplyFunction + 145

    6           0x92d8767b HTTPHeaderDict::copyAsOrdinaryDict(__CFAllocator const*) const + 91

    7           0x92cc08f9 HTTPMessage::copyAllHeaderFields() + 63

    8           0x92cc0d4e HTTPMessage::copyHeadersWithShadowedArrayValues() + 26

    9           0x92bb834a URLRequest::createArchiveList(__CFAllocator const*, long*, void const***, long*, __CFDictionary const**) const + 1270

    10           0x92bb7e36 _CFURLRequestCreateArchiveList + 56

    11           0x92bd189f URLRequest::copyPropertyList(__CFAllocator const*, __CFDictionary const**) const + 95

    12           0x92bd1835 _CFURLRequestCopyPropertyList(__CFAllocator const*, _CFURLRequest const*, __CFDictionary const**) + 42

    13           0x92c940bb invocation function for block in __CFURLCache::CreateAndStoreCacheNode(__CFURLCacheNode*, _CFCachedURLResponse const*, __CFString const*, _CFURLRequest const*, void const*, bool, bool&) + 1306

    14  libdispatch.dylib             0xa757ad89 _dispatch_call_block_and_release + 15

    15  libdispatch.dylib             0xa75735a9 _dispatch_client_callout + 50

    16  libdispatch.dylib             0xa758828d _dispatch_queue_serial_drain + 601

    17  libdispatch.dylib             0xa757a8e1 _dispatch_queue_invoke + 307

    18  libdispatch.dylib             0xa7589085 _dispatch_root_queue_drain_deferred_wlh + 347

    19  libdispatch.dylib             0xa758cfd6 _dispatch_workloop_worker_thread + 742

    20  libsystem_pthread.dylib       0xa7831e4c _pthread_wqthread + 956

    21  libsystem_pthread.dylib       0xa7831a6a start_wqthread + 34

  • It is indeed extremely buggy. Wish there was an alternative out there.

  • yeah only game in town as it were and they really don't seem to give a crap. or get more programmers to fix things... they just care about their new baby sycron.. meanwhile what i want to know is.. how they don't get blasted by the high end film guys like zimmer ...they wouln't put up with this crap for a second... its insulting... 

  • Apparently you believe your individual issues are universal.  I'll just say, without getting shirty, that I doubt this is the case. :)

    Were I your tech person, the extent of your troubles would signal a real problem that's local., to me. Years of downloading/installation problems is surprising. Are you contacting support with these crash logs? 

    "it freezes Logic Pro." Ok, let's troubleshoot now; I guess you have Logic Pro open and then you launch VEP. Does the other way around work? I'm not using Logic. I can go either way in the order of things, and this never happens. Cubase since v 5 thru 9.8 and Nuendo 8.

    Can the actual problem here have anything to do with Logic? 

    At my end, there are crashes occasionally. Kontakt 5.8.1 crashed during a save here. Since this behavior is new to 5.8.1 I consider maybe this is something to do with this version vis a vis VE Pro. I would do more saving in other libraries to maybe isolate this vendor (Spitfire) before I'm very conclusive. Hmmm... this SonicCouture one did not crash VEP. 

    I rely on VE Pro and a number of VSL libraries. It isn't less or more stable than anything else I've used in my 12 yrs doing software-reliant/DAW-rendered music. 

  • last edited
    last edited


    Same pretty good experience for me considering the complexity of software and my peronnal settings.


    @civilization 3 said:


    I rely on VE Pro and a number of VSL libraries. It isn't less or more stable than anything else I've used in my 12 yrs doing software-reliant/DAW-rendered music. 


    I also had from time to time little issues and crashes or freeze, but on average, during years of intense use, it's one of the most reliable and stable software package I ever used (on both Mac and PC).

    Actually things were getting a bit worse with last Windows 10 and Mac OS updates, and some combinations of plug-ins and DAWs can create serious trouble, but I always interpreted and trouble-shooted it as a "combination" where VE wasn't really the main guilty or the key source of problems.

  • This entire thread is the result of some people who have unstable systems overall, and conflicting software issues they don't understand, and then instantly blame VI Pro for. It is NOT buggy but is extremely stable and reliable.  On my system which is currently a 12 core i7 slave with 64 GB of RAM and Windows 10 running the entire Symphonic Cube there are no issues, and extremely reliable power.

  • Hello, 

    I couldn't find a support case for the initial post, but here is some quick feedback regarding that crash: Some network thread is crashing, perhaps a hosted plugin checking for updates or something similar. 

    There is always room for improvement, and we're happy to see that our products are used with passion and dedication. 


    Paul Kopf Product Manager VSL
  • Speaking for myself, unreliability should be the very last word I would use to qualify VEpro... I'm working on PC so maybe something different here and there but I consider VEpro as an extremely reliable app.

  • The frustration must clearly stem from spending that much money on the iMac pro. Clearly, one would except such a computer to work very well ... but it is simply not the case. Use a Mac, if you want to use final cut and logic. For most other software products a Windows 10 computer works way better and costs much less. For any system for professional use, you cannot expect to work everything without proper research, installation and safety measures (backup!). You also should not do updates at any given time, but lock the system with planned update periods in between projects. That is just the nature of professional computer systems. Apple is trying to persuade people, they can guarantee you an experience where everything just magically works - out of the box and reliably so! You just fell for their marketing. That is never the case, for no amount of money and it is not even the case using Apple software exclusively (or how else would you explain even the most basic iOS features not working reliably?)! If you want things to work by spending money, pay a system administrator to work out a proper system an maintain it. That would be the only way to solve the problem with money! Just by spending more for Apple computers, your experience won't be any better. By blaming software developers for that, you are addressing the wrong people.

  • That is perfectly put.  I guess this sort of misinformation is what software developers have to deal with all the time.