Vienna Symphonic Library Forum
Forum Statistics

182,268 users have contributed to 42,216 threads and 254,739 posts.

In the past 24 hours, we have 3 new thread(s), 22 new post(s) and 40 new user(s).

  • Ongoing VE and DP5.13 crashing issue - have reached crisis point!

    I've been having issues with VE crashing DP5.13 for several months now. The problems seem to come and go and so just when it starts to get really frustrating (ie continual crashing for several hours) it suddenly dissappears and DP / VE work fine again for another couple of weeks without a hitch....

    BTW I use VE as an AU plug in DP just to manage my VI instances, and it is invaluable just for that! I only have 4GB on my G5 and so there is no reason to use it standalone.

    I'm now in the middle of another 'bad patch' and any project with VE already saved in it crashes when the project loads this has been happening now without exception for 24 hours!!!! I have projects I needed to finish that I can't open because they have VE saved in them - and this evening I've had to cancel time in another studio because of this! The project starts to load, syncro liscenses are scanned, the VE main GUI appears ..... and then right at the moment when samples would have started loading (when it should be saying 'loading samples, please wait') DP crashes (spinning ball, not responding) ...

    .... meanwhile VE itself becomes operational but with none of the saved VI's loaded - instead just the master channel and one empty channel, as if I were loading a new VE standalone project ..??? (but it is loading from inside a DP project!)

    So I have to force quit DP .....but after DP ihas dissappeared the empty VE GUI stays open and 'alive' (even though it was opened as part of the DP project I just quit ..!!??).

    So I try to then quit VE and I get the 'save project y/n' dialog - I hit 'no' that does cause the VE GUI to dissappear ... but VE still stays active as an app (it is like the Terminator!) and I have to 'exit' the VE service to make it go away which always gives me the message:

    'one or more connections are present. Do you want to forcibly close these connections and terminate the server app.? (this may cause host app to crash or freeze).'

    All the above has been the behaviour without exception for 24 hours now. I've tried repairing permissions countless times/ rebooting etc

    Typically this problem would have gone away after a couple of hours of battling and I would have another week or two of trouble free operation - annoying but bearble ... but now I have already lost an entire day's worth of wrok and I can't access 90% of my projects from the last 6 months or so (as they contain a VE)

    In short - HELP!

    OK more info...

    If I create a fresh new DP project and then try and load a VE the same exact same thing happens every time.

    BUT if I open VE as standalone it is fine

    (obviously DP is working fine in all ways and is rock solid with numerous other plugs and VI's) 

    If I open instances of VSL VI (not using VE) in DP they load into the project fine too.

    All VSL software is up to date - I just checked my user area.

    It seems to me the DP crash always occurs when VE is starting to load samples into RAM ... OR with a new (empty) VE into a new DP project it is the moment when samples would have been loaded.

    I cannot go on with this any more!

    Any help appreciated!

    G5 d1.8

    4GB 

    10.4.11

    DP5.13

    VI/VE latest as per my user area

    Syncro latest 5.2.24.1 - it is plugged into front USB port on G5 (works fine with VI)

    Samples are fine - I rescanned my directory and verified the drive itself (a dedicated SATA internal)


  • FInally ... after a reinstall of (the same version of) VI and VE and another 100 reboots for good luck I am back in business again!

    TIme to stay up all night and play catch up ...

    See you in a coulpe of weeks !

    (I still love VSL) 


  • last edited
    last edited

    @orchestralalala said:

    FInally ... after a reinstall of (the same version of) VI and VE and another 100 reboots for good luck I am back in business again!

    TIme to stay up all night and play catch up ...

    See you in a coulpe of weeks !

    (I still love VSL) 

    OK .. more like 10 days then..... another 24 hours of no projects opening exactly the same issues as described above... still trying to sort it out.

     Any comments/ advice from anyone welcome.

    Starting to feel very weary. Will lose 3 weeks of work every year of work at this rate - not acceptable. I know it's my system, not universal problem, but any help would be really appreciated! [:)] 


  • Have you gone here? You will get a lot of good DP info as to how to solve the problem. 4 gigs of ram is not enough I would say in any case. Have you ckecked how much you're loading and using? http://www.unicornation.com/

  • last edited
    last edited

    @dpcon said:

    Have you gone here? You will get a lot of good DP info as to how to solve the problem. 4 gigs of ram is not enough I would say in any case. Have you ckecked how much you're loading and using? http://www.unicornation.com/
     

    Thanks DPcon - yes I am aware of Unicornation - 'tis a great forum for all things DP and beyond ....  !

    I am sure it this has nothing to do with RAM, when VE is running OK I can still run a very decent amount of VI's no problem at all.

    I am also pretty sure it's me and my mac and not VSL ... however it is still an 'issue' whatever the cause is. Apart from this ongoing problem everything works like a dream on my system. I've had another bad episode since my last post. In all cases it seems I need reistall VI and VE and perform multiple permissions repairs and reboots to get it working again.

    It is becoming a serious drag and time/ money down the drain.

    Again, any suggestions generally on how to fix this issue (see my posts higher up)gratefully received! 😊


  • Have you tried opening the VE as standalone so syncrosoft will see it and then closing and then opening DP? Just a guess but syncrosoft will stop the show if it it isn't happy and so this would be a way of finding that out.

  • last edited
    last edited

    @dpcon said:

    Have you tried opening the VE as standalone so syncrosoft will see it and then closing and then opening DP? Just a guess but syncrosoft will stop the show if it it isn't happy and so this would be a way of finding that out.
     

    Yes. VE has always worked OK standalone, even when it's having one of its crashing DP phases ... in fact, when it is playing up it usually opens OK in DP too  - except that it loads empty when it should have VI's loaded into it (ie the state it was in when DP was last saved) and it always crashes DP as it launchs.... so although it opens (sort of) it is useless. What happens is that the DP project starts to open, then as VE (as a plug inside the DP project) launches it scans the license OK, the VE GUI appears and just at the very moment when it should start loading data it doesn't and instead it crashes DP (spinning BBOD) and then just sits there empty but still responsive. DP never recovers and I have to force quit it and VE then just continues to sit there like a lemon.

    When it is playing up like this it will never work ...... until it's sorted out (by reinstalling/permissions/rebooting) - when it at last decides to work again it will work every time no problems for another couple of weeks until the next bad patch ... and so on). So it's not like sporadic crashing of an unstable plug, it comes in distinct phases. Also when it's playing up it will crashes DP (in exactly the same way) even when I try and open an instance of VE into a new DP project (or any project with no VE already in it). 

    VI works fine on it's own regardless.

    It's quite bizarre! 


  • To be honest I am having exactly the same problem with DP 5.13 only it is being caused by spectrasonics atmosphere plugin!! DP crashed evry time I hit rewind!!! It even crashes sometimes if I move a midi note in the midi editor. Nightmare!!!

    Roll on DP 6!!!

  • I started having the problem last night.   I'm locked out of 2 weeks of work on a project.  Do I need to uninstall VE to gain access to my projects?  I guess I will try a re-install first when I am back at my machine.  Frustrating to say the least.  I am running DP 5.12 on a G5 Dual 2.7 with a Duet audio interface, and VE version 2.0.3059


  • I had a similar problem a couple of weeks ago. In the middle of my work, I got a kernel panic, and from then on every DP project containing a VE instance puts DP 5.13 into endless spinning-beachball mode. (I have 2.0 2779 installed.) VE standalone still works fine. To open a project containing VE, I must remove ViennaEnsemble.component from Library/Audio/Plug-Ins/components and recreate all the instruments with VI. Since then I only work with VI instead of VE. Of course lots of VI instances are much more complicated to handle than one VE instance (and I miss the power panning), but at least it's reliable...

  • Thanks so much Pierre.  That is the answer I was looking for to solve my short-term project access issues.  I am surprised that the use of VE within DP continues to be somewhat unstable. 

    VSL Team, are you aware of the cause of this problem, or is everything running fine on most DP setups?


  • I've had exactly the same problem, and it's taken up so much time. The lovely people at VSL sent me a beat version of VE which has so far helped a bit, but it's still really unpredictable/unstable for exactly the reasons you've stated with DP5.13. As a standalone it's been fine.

  • I'll add my experience to the list as well. Virtually identical issues. The only success I have had this morning, after the force quitting everything, is to re-boot, re-scan with the VE Directory Manager, and so far it appears DP opens as it should. I have to try a couple of other permutations before I feel like it is the solution,but thought I'd pass it on. FWIW I've never had the Atmosphere issue. Andrew

  • last edited
    last edited

    Hi!

    @ orchestralalala: which version of VE are you using?

    so far, we couldn´t reproduce the problems you encountered with VE 2 and DP 5.13. I´d suggest to try the following:

    1) close DP and delete the following file:

    "Mac HD"/Users/<username>/Library/Preferences/DigitalPerformer/Audio Unit Info Cache

    Restart and launch DP again. DP will now "rescan" its Audio Unit plug-in´s. In case that the problem persists please send a DP project and a problem description to <support@vsl.co.at>

    Best regards,

    Maya