Vienna Symphonic Library
  • LOG-IN
  • LANGUAGE
  • BASKET
  • English
  • German
Your Basket contains the following items:
Your Basket is empty.
MY BASKET
  • PRODUCTS
  • NEWS
  • MUSIC
  • COMMUNITY
  • ACADEMY
  • COMPANY
  • MANUALS
  • MyVSL
  • FORUMS
  • SEARCH
  • LATEST POSTS
Welcome Guest! To enable all features please Login or Register.
  • Forum
  • Active Threads
  • Search
  • Help
  • Login
  • Register

Notification

Icon
Error

OK


> FORUMS > Search
Search
Search for
Posted by
Forum
4 Pages123>»
Go to Page...
1.Strange dropout behavior in synchron player. (Synchron strings, syn Dimension strings etc..) 7/26/2020 3:37:13 PM

Here’s a hint at what this problem might be.  This discussion requires that the plugin is VST3 and is created using JUCE tool set. My understanding is that VSL uses JUCE.  If that is no longer true, then please disregard this post.  The VST3 assumption applies to VE Pro or individual plugins.  Using the VST2 version of VE Pro or the individual plugin instead of the VST3 version will eliminate the problem I am describing.

 

My mental model of the problem is that there is a protocol mismatch in the interface between the host (e.g., Cubase, Dorico, etc.) and the plugin (e.g., VST3 version of VE Pro, Synchron Player, VI Pro, Pianoteq etc.).  The host assumes a single-stream serial MIDI protocol, and the plugin assumes a multi-stream timestamped MIDI protocol.  If two or more MIDI events occur with the same timestamp then (depending on what those events are) they might get reordered in the plugin.  I’ve seen this issue using Dorico and Pianoteq and using Dorico and VE Pro.

 

In one example, an All Notes Off event occurred at the same timestamp as a Note On event.  They were ordered serially from the host as All Notes Off followed by the Note On.  But the plugin reordered these as Note On, followed by All Notes Off.  So notes were cut short.  This sounds exactly like what is occurring for some users in this thread.

 

In another example, before Dorico introduced the notion of negative time in its MIDI stream, a condition occurred if you specified an articulation different from the default on the first note of a score and the plugin was using the VST3 version of VE Pro.  In this case, a Key-switch Articulation event occurred at the same timestamp as the Note On event.  Sometimes the correct articulation was respected.  But not always.  In every case, the subsequent notes respected the articulation event.  So the plugin was causing those events to be re-ordered some of the time.  It was repeatable that it occurred, but not repeatable every time.  So it was as if a race condition determined which event happened first.  Once negative time was introduced then the articulation events moved forward enough in time to ensure the correct ordering.     

 

Both examples above did not fail in a consistent way.  They only failed some of the time, but often enough to be noticeable.

 

I am sure there are other examples where the ordering can cause issues.  Particularly because the Synchron Player requires events to be in the correct order for articulation selection in the tree structure.  So if your tree structure is using key-switches for some branch and CCs for another, for example, then I suspect this will cause issues.  I don’t currently use this plugin for anything, so I haven’t experienced this first hand, but suspect this is possibly a problem.

2.Help With Dorico and VSL Jazz Drums 5/7/2020 7:28:38 PM

There is an old thread on this issue that might still be useful.  I haven't used these in a long time, so I don't know if it still applies.

 

https://www.steinberg.net/forums/viewtopic.php?f=246&t=134006&p=736655

3.YAY: SYNCHRON-ized Plucked Instruments! 2/15/2020 9:12:26 PM

upright bass IR

4.YAY: SYNCHRON-ized Plucked Instruments! 2/15/2020 5:00:31 PM

Why is the impulse response for the Upright Bass called "Organ"?

5.NEW: VE Pro 7.0.921 Catalina Update with great improvements! 10/28/2019 3:38:04 PM

Thanks for these updates.

One issue... the plugins in Vienna Suite 1.5 still has sym links to the executable.  The installer is installing files from July 2018.

The others seem to be fine.

6.Logic can't see an existing VEPRO instance 8/31/2019 11:38:47 PM
See this thread:

https://www.vsl.co.at/co...3-templates-from-scratch
7.Building LogicPro AU3 templates from scratch 7/12/2019 5:09:40 PM

Here are the steps:

  1. In the software instruments dialog, create an AU3 multitimbral track with 1 part
  2. Track>Other>New track with next MIDI channel (ctrl-return)
  3. Repeat step 2 until you have as many channels as you want for that port up to 16 channels (stop when you get to 127 channels)
  4. Select the last track, Change to port n+1, channel 1 in the track inspector
  5. Select there second to last track and do step 2 (this back fills the previous port)
  6. Select the last track and repeat steps 2 through 6 (stop at 127 channels)
8.Building LogicPro AU3 templates from scratch 7/12/2019 4:35:40 PM

It's even easier...

After creating port1, channel 16...

6a Rename port 1, channel 16 to port 2, channel 1

6b backfill port1, channel 16 by selecting port1 channepo 15 and create new track with increementing channel.

9.Building LogicPro AU3 templates from scratch 7/12/2019 3:21:19 PM

I found a way to make this work.

Using the old instructions, after step 6 (where you rename channel 17 to be port 2, channel 1), do this:

6a. Select and delete either one of the tracks that are port 2 channel 1.

6b.  Select the second to  last channel again (e.g., port 1, channel 15) and then select Track>other>new track with next midi channel as before.  

These two steps break the link between what was port 1 channel 16 and what wants to be port 2 chanel 1.

10.Building LogicPro AU3 templates from scratch 7/10/2019 5:01:56 PM

yeah, you have to do that in the environment. 

11.Building LogicPro AU3 templates from scratch 7/10/2019 4:58:31 PM

This doesn't quite work.  When I try to change the track 17 to port 2 channel 1 in step 6, it also changes the track 16 to port 2 channel 1.  So those two tracks aren't unique.

12.Build your own AU3 custom templates in LPX 10.4.5 6/15/2019 8:46:18 PM

I was referring to getting it to work at all.  The plugin doesn't load unless you have allocated enough audio outputs in your server preferences.

I agree about the midi channel limitation of 127.

13.Build your own AU3 custom templates in LPX 10.4.5 6/15/2019 8:23:43 PM

This worked for me.  Thanks for the insight.

Dewdman, you need to increase your audio outputs per instance preference in VE Pro Server to 50 for the multi output version of the plugin to work.

14.Sul Tasto Dimension 4/13/2019 6:04:52 PM

Originally Posted by: Dewdman42 Go to Quoted Post

But I'm also quite overwhelmed about how best to dig into it.  

If you look in the Music section, the demos with the red buttons have tutorial files you can download.  I'd recommend you look at some of these to see how others use the library.  VI Pro allows you to see which articulations are used even if you don't yet own that library.  Caution is advised in that this will only make you want to buy more libraries when you see you don't yet own a specific articulation that makes you go "oh, wow.  I need that one".

15.Dimension Strings I 03.2019 Update 4/4/2019 10:15:08 AM
Is your license key plugged in? I had the same problem until I plugged it in.
16.Close mics on Steinway D 3/6/2019 9:41:48 PM

deleted

17.Mojave - VEP5 Server "Synsopos.app" Error 2/26/2019 3:59:44 PM

Here are couple of things to try.  I've seen these work on other apps that are not designed for Mojave.

Make sure your elicenser app is up to date first.

Also, before doing any of the following, make sure synsopos is not running (force quir it if you have to using activity monitor).

 

1.  Try disabling and re-enabling the security and privacy checkbox in the automation panel.  

 

2.  If that doesn't work, you can reset the TCC database using the following command in a terminal window:

tccutil reset AppleEvents

This will remove all occurances odf the Sysnsopos.app items in the automation tab.  You can see this happen if you have that window open at the time.  This will require you to authorise each app once again as you did initially.  

If one of these works you probably need to do it each time you update the elicenser app,

 

3. As a last resort, you can launch elicenser and leave it running while using VEP 5. Then VEP 5 won't need to control synsopos since it will already be running.

18.Help with VST3 performance 12/26/2018 8:32:52 PM

My general rule is leave two for the DAW, and divide the rest evenly between VE Pro instances.  You have 24 total.

19.Help with VST3 performance 12/26/2018 8:19:31 PM

Originally Posted by: Dewdman42 Go to Quoted Post

Thanks for the idea.  Seems to help a lot...  what is a good rule of thumb on the thread counts, on a 12 core system?

 

I would allocate 22 to VE Pro leaving 2 for Cubase.

20.Help with VST3 performance 12/26/2018 8:16:54 PM

Are you using VE Pro Server or are you instantiating VE Pro directly in the sequencer?  If the latter, there may be some preferences to set in the sequencer for thread allocation but I am not familiar with Cubase.  If you are using VE Pro Server, then the thread count should have made a difference.  Also, if you are using Server, then there is a buffer number in the server window that you can adjust.  Are these the same in both cases?

21.Help with VST3 performance 12/26/2018 7:43:50 PM

Check your instances preferences and be sure to allocate more threads per instance since you only have one instance. 

See page 22 of the manual for guidance.

22.Yamaha CFX -- sustain pedal chopping samples? 5/17/2018 9:57:01 PM

I have two computers (both Macbook Pros, 2.7GHz, 16GB, quad processor).  One is 2012 vintage and the other is 2016 vintage.  The newer one has a very fast SSD, the older one has an SSD that is significantly slower but still pretty good.  On both machines I am streaming from the internal SSD.

I have a midi file that stresses the SSD pretty hard (over 400-500 voices in some parts depending on the mic preset).  The older machine has problems in the more stressful parts of the playback.  The newer machine has no problem ever with this file.  When looking at ther CPU monitor, the older machine hits 100% in several places and it is here that I hear samples cutting out.  The newer machine never gets over 75% even with the lowest preload setting.  The old machine hits 100% often even with the highest preload settings.  But the preload setting does make a difference.

The SSD speed is the only significant difference between these machines.  I suspect the SSD speed is why some people are having problems and others aren't.

Anyway, the logic pro project and midi file are at the link below so you can test on your machines and monitor the CPU to see if it gets to 100%.  I think that is when the samples are cutting out.

https://www.icloud.com/#iclouddrive/0cns36_RgsPKidH8NUCcurESA

23.Synchron Piano won't load into ProTools or Logic 5/3/2018 11:22:22 PM

Try rebooting.  I needed to do that before it shows up in Logic Pro.

24.macOS High Sierra (10.13) compatibility 9/28/2017 2:56:44 PM

OK, thanks.  I also found the script and looked at that. 

25.macOS High Sierra (10.13) compatibility 9/28/2017 2:42:09 PM

I see that this has been released and it seems to allow the Vienna Suite Pro AUs to work once again.  So what exactly did this do?  What files got installed and where are theyt located?

4 Pages123>»
Go to Page...

Loading...

Icon
Loading Search Results...

VIENNA SYMPHONIC LIBRARY
  • © 2002 - 2021 Vienna Symphonic Library GmbH. All Rights Reserved.
  • Terms of Service
  • Terms of License
  • Privacy Policy
This website uses cookies to enable you to place orders and to give you the best browsing experience possible.
By continuing to browse you are agreeing to our use of cookies. Full details can be found here.