-
Vienna crashes for new instrument
I have set up a simple symphony orchestra with the following instruments (two instances of Vienna Ensemble VSL in Sibelius): Flute Oboe English Horn Clarinet 1 Clarinet 2 Bass Clarinet Bassoon Horn 1 Horn 2 Trumpet 1 Trumpet 2 Trombone Tuba Violin 1 Violin 2 Viola Cello Bass Timpani Now I need to add a Solo Violin. So, I created a new instrument. But Vienna crashes as soon as I try to assign the matrix for Solo Violin. I thought it might be a memory problem. But I have had a greater number of instruments before, without any problems. After this, Vienna seems to have become shaky, it crashes without a reason even when I use configurations with less instruments. I use Sibelius 5 and Vienna Special Edition Plus. I have a Mac Pro 2 x 2,8 GHz Quad-Core Intel Xeon, 6 GB RAM. I'm very satisfied with Vienna, hope there's a solution to this problem. Pekay
-
Yesterday, the same thing happened to me. I had 2 instances of Vienna Ensemble running under Sibelius. After I wanted to add a solo cello to colorize my score (which was almost doen) the entire application crashed.
I started up Sibelius again after the crash (Sibelius did not crash but Vienna Ensemble did) and immediatly Vienna Ensemble crashed again.
I restarted my computer, fired up Sibelius once more and one instance of Vienna Ensemble crashed but the other one loaded. And it keep like that since yesterday.
The latest build of Vienna Ensemble is used. It seems to be a common bug, or is there a work around?
[edit] in the meantime I try to solve multiple issues but without success. But what I came accros is the same old bug I saw earlier. A screencast remains on the screen like if there's still an instance of Vienna Ensemble running. Although I force quit the application it remains there and when I hover my mouse over it I get this twirled cursor.
The last time this happened somebody pointed out that I had to install the latset versions. I did, and I apparently still have the latest version. But I'll try to reinstall the application and get back to report the results.
-
Hello Arnold!
I can't read crash reports, but could it be that you are overloading your RAM? Please keep in mind that Vienna Ensemble is a 32 bit application and can't take more than about 3 GB. You won't get more just by opening more instances of VE.
Vienna Ensemble Pro is a 64 bit application. You can use all the RAM that you have with it. For a complete feature list, take a look at this link:
http://vsl.co.at/en/211/497/1685/1693/1342.htmI hope this was helpful.
Best regards,
Andi
Vienna Symphonic Library -
Hi Andi,
I'm a bit at a loss again... I can't figure out wheter I overload my system's RAM. Simply because I can't get Sibelius back working anymore. I am in the middle of orchestrating a musical.
I tried restarting my computer, installing the latest versions and did all the troubleshooting and Inow feel like the Viennese plug-ugly... who tries to keep his wits ;-)
These things never come at the right moments... but I'll have a look to the 64 bits version. Why is it that there is a 64 bits version for windows but not for the mac btw?
Best regards, the Viennese plug-ugly :-)
-
Hello Arnold.
Sorry, but I can't really help if Sibelius is not working anymore. I guess you have already tried uninstalling and reinstalling it.
I am not a programmer, but as far as I know it was not possible to make a 64 bit version of VE on Mac while it was developed. VE Pro has a new technology behind and also Mac OS developed since then.
By the way. The amount of RAM an application takes can be seen in the Activity Monitor.
Best,
Andi
Vienna Symphonic Library -
Hey Andi,
Yes, I know you can not help me with Sibelius issues. But the problem is addressed to Vienna Ensemble, which crashes and due to that - Sibelius freezes.
The developments yet reached is that
- I intentionally let Sibelius/VE crash.
- Start up Sibelius again with a blank file.
- Shut down Sibelius properly
- Restart Sibelius
- Fill en reinitiate the playback devices and creating all (both) template VE's again
I hope that will work, (I'll keep you updated as I normally do) but I guess you'll agree that this is not the most elegant way to fix problems?
Cheers, The Viennese Plug Ugly
- I intentionally let Sibelius/VE crash.
-
OK, now I know it for 100% sure. I found a bug!!! (crashing without any warning)
Do as follows on a Mac OSX 10.6.4
- Set up 2 instances of Vienna Ensemble.
- load the first instance with: fl/ob/cl/bs/hn/trp/trb/tmp/vib/mar (that makes at most 1gb)
- load the second instance with the Vienna Ensemble Strings Plus : vln (1)/vln (2)/vla/vcl/cb (makes approx. 1,25 gb)
- now comes the bug - load a solo cello from the Vienna Ensemble Strings Plus! (around 260 mb?)
- BOOM, it crashes!!!
There you have it, step by step. I've done this for 3 times now, including the steps above (the intentionally crash part)
Of course there is a change that it is about my hardware configuration, or something else but I really don't recognize anything wrong with my computer. Maybe I must try and load another instance for the solo cello?I don't see why it just crashes, instead of giving me a warning, concerning a RAM overload. If there is any, because a little math gives me around 2,5 gb of RAM used. So it comes close, but I really thought this would be managable.
Crashing makes it really hard to recover things...
Best wishes,
The Viennese Plug Ugly
-
Hello Arnold!
Sorry, but now I know it for 99% sure, that you didn't find a bug, but just overloaded your RAM. ;-)
The 3 GB were only an approximate value. This varies from machine to machine depending on various things.
Adding up the amount of RAM of the samples doesn't give you the amount of RAM Vienna Ensemble takes. Vienna Ensemble and every opened Vienna Instrument inside also need some RAM.I recommend using the Learn/Optimize function of the Vienna Instruments before adding the solo cello.
Best wishes,
Andi
Vienna Symphonic Library -
Hi Andi,
Maybe not, but I find it highly interesting that the application just crashes instead of warn me first.
Normally an application (like the Protools app I use) gives me an error message. Sometimes with a hint about in or decreasing the amount of latency, RAM or whatsoever. Not very charming either, but at least slightly more professional because it gives you a bit more information on what is happening, and why.A crashing application without any apparent reason gives me this conclusion: bug... I mean, what would you think when you, for instance, record a group of Viola da Gamba's (I wish you guys did [;)]) for your latest sample set and the recording application would suddenly crash because there's not enough memory, without you knowing it? Especially when after that your entire computer will be frozen and you have to restart the session all over again. And then, as a bonus because you don't know yet where exactly the crash came from, you start to build up your session again and again until you figure out what happened? Sort of... Just imagine, what would you think? That's very cost inefficient! [:D]
Sorry, but I assume there's a fix needed for this. It might be not a big bug, but my extensive Activity Monitor reads out 1.84 gb (along with 22% cpu ussage and 26 threads) Which is by far the maximum amount of RAM. But I'll keep it in mind, that's what you're after, hehehe
Refraining,
the Viennese Plug-Ugly
Forum Statistics
196,053 users have contributed to 43,014 threads and 258,388 posts.
In the past 24 hours, we have 2 new thread(s), 18 new post(s) and 144 new user(s).