I know, that´s why I suggested a reinstallation of the Vienna ensemble, just as a wild guess....

Phew, glad it worked [:)]

We will look into it!

Time to go to bed for me....

You can expect a lot of improvements, thanks everybody for contributing!

Best,

Paul 

I am having some major crashing problems! Every time I start VE, the main VE window appears and after a few seconds I get an error message, "We're sorry, viennaensemble.exe has encountered a problem..." blah blah, we all know this message very well.

I've tried reinstalling, I've tried rebooting... I must say it is very disappointing!

I am using Creative Audigy 2 sound card... maybe it has something to do with the sampling rate? By default this soundcard has a sampling rate of 48khz instead of 41khz...

I'm just not sure how to fix this!

Hey folks - where are you downloading VE?  When I log in to the user section, no product registrations show up.  Is that why I can't find the download?

Do I need to do something since the changeover to the new website?  Do I need to re-register all of my libraries?

Thanks,

rgames

@sonicether_29951 said:

I am having some major crashing problems! Every time I start VE, the main VE window appears and after a few seconds I get an error message, "We're sorry, viennaensemble.exe has encountered a problem..." blah blah, we all know this message very well.

I've tried reinstalling, I've tried rebooting... I must say it is very disappointing!

I am using Creative Audigy 2 sound card... maybe it has something to do with the sampling rate? By default this soundcard has a sampling rate of 48khz instead of 41khz...

I'm just not sure how to fix this!

I have the same problems. Whenever I start VE as standalone or as a VST in Reaper or Sonar, the VE crashes

In Sonar the VE is loaded without error, when I choose not to connect it automatically to an audio channel. As I manual insert an audio channel in Sonar and connect them with one of VE's outputs, then the error occur again and VE crashes.

I've tried different Audio cards. I have three, an onboard Nvidia Soundsystem, a Creamware DSP Audio and a Digidesign MBox2-Mini.

The error occur independent which audio card and which driver system (ASIO oder DirectSound) I choose.

I have no clue anymore how to fix this. I tried several things, like reinstalling VE, reinstalling all my audio drivers, reinstalling chipset drivers and some more.

I have no more ideas and btw, Vienna Instruments works fine in standalone and vst.

The VE ist the only audio software on my PC that don't work.

If VSL is interested to solve this problem, don't hesitate to contact me (I'm speaking german too) [:)].

I'm an experienced PC user with some knowledge of software development.

If any other have some more ideas to help, then post please.

Thanks

Markus

@ETM Dude said:

IT doesnt surprise me with Nvidia or Creative, both have this error alot with pro-audio aps... but the Mbox should have pretty decent ASIO drivers, do you have it set to be your default sound device in control panel prior to opening VE?

Yes. I have set die Digidesign-ASIO and the very well working Creamware Scope-ASIO as default audio device, but always the error occur.

Using VE as VST-Plugin I can't not set any sound-device, becauses it uses the sound device of the host software, and the error occur too.

So I don't think the error is specific audio driver dependent.

If it would be a problem with audio drivers, then it should be occur in some other applications, like the VI, Sonar, Reaper, Kontakt2, ProTools etc. too. But all this applications do work fine.

I mostly do work in ProTools and maybe VE could help me alot, because of no current RTAS versions of VI. So it would be nice to bring VE on the run on my machine. [:)]

greetings

Markus 

These problems that you guys are describing sound exactly like my problems. No, it doesn't seem to be related to the soundcard... This just totally has me stumped!

I'm using Windows XP with all of the latest updates. How about you guys?

I've tested this as a vst plugin in FL Studio (don't laugh, it's actually pretty awesome) and in a vst host that I have... I've also tried this stand-alone, and I'm getting no luck. The thing that I find most peculiar though about the crashes is that if I ignore the error message, I can keep tweaking volume sliders and the like... The interface does not lock up, like you'd normally see in crashes.

I hate not being able to find a solution to a problem!

So, really no Ensemble for mac today? [:'(]

Oh well, I guess we always have tomorrow.

Colin Thomson 

Dpcon, take a look at the first page of this thread. I also downloaded the mac ensemble that was up earlier, but was then told that it was not the right one, and had to uninstall it. So I guess you don't want to install what you have, and we're just stuck waiting a little longer.

Colin Thomson 

@ColinThomson said:

Dpcon, take a look at the first page of this thread. I also downloaded the mac ensemble that was up earlier, but was then told that it was not the right one, and had to uninstall it. So I guess you don't want to install what you have, and we're just stuck waiting a little longer.

 

 

Colin Thomson 

Hi !

I don't have enough time to test Vienna Ensemble right now, but I've one question :

If you use a x64 os with a 32 bits vst host, does the client/server allow us to use the x64 VE ?

I don't think so, but... 

Hmm, sorry, another (technical) question :

Why do we need to manually set the latency compensation ?