It is indeed the Pro version. In fact I could not install the original version, but did not pursue it since I just assumed it was too old to work. I didn't do anything special to install the Pro version, and it has worked in both Logic and Cubase, so both AU and VST versions definitely installed correctly. My OS language is British if that helps.

I'm new to Macs, so I cannot offer any suggestions on what to try. Not much help I'm afraid, but I hope you manage to find what is causing the problem for you.

Ian

I'm sorry to see you are having problems Gunter, but I thought it might be worth me noting here that Vienna Suite Pro installed and seems to work fine on my M1 Macbook Air. I know that doesn't help you as such, but it does suggest the problem is more subtle that it just not working with the M1 chipset.

Best, Ian

I couldn't help but notice the following lines in the Mix Magazine article...

"Since October 2015, they have been test-driving Stage A, recording scores with Sands and sampling instruments for the library and the VSL Multi-Impulse Response convolution engine".

It's not definitive where this might lead, but it looks hopeful and exciting!

Ian

Hi,

I noticed on the Steinberg forums that they said the Server was down, and they were working to fix the problem.

HTH, Ian

Thanks for the reply, dissappointed as I am by the reality of the situation!

As far as I am aware, there currently isn't a VST3 version of the Vienna Instruments player, only Ensemble. I am struggling to see what the problem is for VSL since both Kontakt and Play both work with ASIO Guard turned on.

Thanks anyway, Ian

Hi,

I know there is an on-going thread about VEP and ASIO Guard, but I think this is probably a different issue so I have started a new thread. I hope I was right to do so! This relates directly to Vienna Instruments not VEP, and therefore relates to VST2.

- If I insert an instance of Kontakt as an instrument directly in Cubase 8, when in record mode I get a higher ASIO reading than when in playback. This is the benefit I understand I can get from ASIO Guard.

- If I insert an instance of VI directly in Cubase, when in record mode (Or 'live mode') it works fine. However, when I playback I get ASIO peaks, breakup and erratic sample playback. This is particularly bad with MIRx running in the instance. I don't know if this is just that the pops are more obvious with reverb, or another reason.

If I disable ASIO guard for the Vienna player, it works fine.

Can someone please confirm whether this is just my system, or a problem with the VSL player? Starting from a point of ignorance, I would have thought that Kontakt and the VI player would operate in a similar way.  It would be great if they did, since in my single PC rig, I could get many more instruments running in parallel.

Thanks for any assistance, Ian

Post deleted and a new thread started. I decided it was most likely a different issue to the one being discussed in this thread

Hi Cyril,

Perhaps I didn't expresss myself very well. What I meant was that I create my own matrices that all use C-1 to A0  as the keyswitches (or C-2 to A-1 depending on what you take to be middle C). I do not use any of the 'out-the-box' presets. For the instruments I use, I think the contra-bassoon is the lowest playable note which runs down to about B-1 (from memory), so anything below that avoids any clashes with my selected keyswitch range.

I experienced a similar issue to DG in the limit on accessing the extensive articulation choices in VSL. I therefore use a kind of two tier approach; also using Lemur, (but not a proper one, just the iCr*p  )

I have each matrix selected via the keyswitch. Like DG I always use the same mapping, eg Legato on C-1, Sus on C#-1, Stac on D, etc. I then control the X-axis with a CC. I put the main patch associated with the articulation in the first cell of the matrix, and then alternatives along the X-axis (different lengths, perf reps etc).

Assuming the x-axis CC is set to zero I can play live and use the second keyboard to switch articulations. I can then tweak the CC afterwards in Cubase to select alternative patches or use my Lemur template. That is set up to show all patches, and when I select a particular patch it sends out both the keyswitch and the CC value.

I hope that makes sense! For me, I have found it to be reasonably successful, so I just suggest it as an idea to consider.

Ian

Hello

It's rare that I post, but I saw your question, and for once I can offer some experience! I use a Novation Impulse 49 as my main keyboard for playing at my computer (a PC). I map all of my VI matrices starting at the lowest note (C-1), and over time, have tested two small format 25 key keyboards that I use for keyswitching only. Namely the Akai LPK25, and the Korg MicroKey25. Here are the pros and cons as I see them:

Akai LPK25 Pros:

• Very compact (Both in area and height)
• You can create four presets which can be accessed from the front panel buttons. Importantly for me, the preset can define the octave offset. I only use one preset, but when the unit powers, that reset is restored.

Cons:

• The octave Up/Down buttons are single colour. They are both off when there is no octave offset, but lit when there is. It is therefore not possible to see whether the offset is 1, 2, 3 etc. This is not a problem the way I use it though since I use the preset to control the octave offset.
• The buttons/LEDs are very bright when lit! In fact, I have taken mine apart and made a hardware modification to dim them.

Korg MicroKey25 Pros:

• Slightly more rugged construction than the Akai (but not significantly so though)
• The keys feel a bit nicer, they are not as springy as the Akai. For the purpose of key switching though I don't think this is an issue.
• Octave offset has tri-colour LEDs
• Has a decent (though small) joystick which can be useful at time (Not for keyswitching though obviously)

Cons:

• Although the octave buttons are tri-colour, when set to start at the bottom note I use, the LED flashed red since three colours are not enough. I find this very annoying.
• There is one stored configuration which can be set from the editor, but this does not include the octave offset. I found myself always forgetting to set the correct octave every time I turned it on.
• More expensive than the Akai
• Takes up more desk space than the Akai

So I prefer the Akai for this function. I just feed it into a USB hub and leave it connected all the time. I have been happy working that way and not experienced any down sides when using it with Cubase.

I hope that helps

Ian

Hi

I can confirm your experience with the Hybrid Reverb, also running Cubase 6, W7 64-bit on PC.

In addition, I have also found the following GUI quirk on my system with the Convolution Reverb:

- Open an instance of CR and load a factory preset

- Click on the IMPULSE button to load a different impulse

- When the Windows file selection window opens, hit cancel

- Now click on the Factory Presets button, and the Windows file selection window keeps opening.

I also think the HR is great product - congratulations to VSL!

Cheers, Ian

I have only just had chance to follow this up, but I am happy to report that ticking the 'Don't use extensible format' in Cubase 4 solved the problem for me. So my thanks to you all !

I would like to give my vote of support for the idea of implementing the option to load two stereo files instead of having to load a 4 channel one every time.

Ian

I'm glad to see it is not just me! Stereo wav files load without any problems, but like you, I have tried creating an assortment of four channel files, none of which will load into the VS reverb.

I hope someone can point us in the right direction!

Ian

Hi,

Although I lurk alot on this forum, I don't usually post. I thought it might be worth saying though that I also have this problem on my PC running WinXP Pro, but with Cubase 4.1.3. If the VSLdaemon is running before I launch Cubase, then Cubase will crash out, even before a I open a project. Killing the process before running Cubase means that it works fine. I forgot to say that I am running the latest version of VI. It has not always been like this, but unfortunately I cannot say whether the problem started with an update to Cubase or a particular update of the VI.

I hope that hasn't muddied the water! 

Ian 

I thought I should just clarify something from my post...

In the situation under consideration, I only use the freeze function as a method of supplying the information to the VI what articulations and notes are needed so that the VI learn function can operate correctly. As Jay pointed out, the operation can be done faster than real time. The reason therefore for unticking 'Unload VI after freezing' is that in this particular case it is a redundant and time consuming operation. If I were to use the freeze function as designed then I too would usually unload the VI to save system resources.

I'm not sure if this point was clear, but if not I hope it is now.

Thanks

Ian

Jay,

I too have found that technique to be very useful. What I find slightly less hassle (Using Cubase that is), is to freeze the VI after setting it to learn mode. It is important to make sure that the 'Unload VI after freezing' option is NOT ticked when prompted. After freezing is complete, immediately unfreeze and optimize in the VI.

I know it is effectively the same thing as you are doing, but track is automatically deleted by the unfreeze command.

Of course this suggestion maybe of no use if you do not use Cubase!

Cheers

Ian

Thanks for info Herb. Hope you enjoyed your vacation, you deserved it! I cannot really imagine how much work was involved in getting all of the SC released.

Best regards

Ian

A friendly bump!

Ian

Ron

I do not have a Resources folder in my Brass installation (Unlike the WW and strings). Perhaps VSL have forgotten to enable it in the Level I install (?). If so, this is almost certainly the source of the problem.

Thanks for your assistance.

Ian

I have just purchased and installed the Brass I VI. It seems to me there is a problem across a number of the instruments for the Perf_Legato_Speed matrix. It certainly occurs for the Trumpet, Trombone and Trumpets - I have not tested the others.

The problem is that the first cell in the matrix references a patch that does not seem to exist. e.g. For the trumpet this is TrC-perf_leg_slow.

Can someone at VSL please investigate this.

Thanks

Ian

Thanks Herb,

It's not a problem in the short term, as you say the perf-legato is fine for the moment.

Ian

Hi,

I am running the Woodwind VI with just the basic license. I note that all of the solo woodwinds have four patches in the 'SHORT + LONG NOTE' folder except the bassoon which only contains BA_Staccato and BA_Portato+Short. This corresponds with the WW patch document, but seems somewhat inconsistent.

I note that the LEVEL1 matrix Atriculation Combi contains BA_Sus_Vib in cell 1:2, and when this cell is accessed there is no sound.

Can someone please confirm whether I have something strange in my install, an error in the preset, or an error in the license handling.

Thanks

Ian

Thanks David, it was worth just checking.

Ian

Hi,

I have just bought the Orchestral Strings Vol 1 VI basic version. According to the website, I believe I should have the following articulations:
Con Sord - Stacc, Sus, Trem
Octave Gliss Up & Down.

However they do not appear to be in the patch list. Could someone please confirm whether I should indeed have them, and if so what I may have done wrong with the installation (All other patches seem to be correct)

Thanks

Ian