Vienna Symphonic LibraryCompany Logo
  • Products
    Synchron
    • Synchron Series
    • Synchron Pianos
    • Big Bang Orchestra
    Starter
    • HELLO Free Instruments 🔥
    • Synchron Prime Edition
    • Smart Series
    Software
    • Vienna Ensemble Pro
    • Vienna MIR Pro
    • Vienna Suite Pro
    • more...
    VI Series & More
    • VI Series
    • Freebies
    • Vienna Voucher
  • News
  • Music
  • Forum
  • Academy
    Instrumentology
    • Strings
    • Brass
    • Woodwinds
    • Percussion
    • more...
    Discover Strings
    • Violin
    • Cello
    • Double Bass
    • Harp
    • more...
    Discover Brass
    • Trumpet in C
    • Horn in F
    • Tenor Trombone
    • Bass Tuba
    • more...
    Discover Woodwinds
    • Concert Flute
    • Oboe
    • Clarinet in Bb
    • Bassoon
    • more...
  • Support
    Software Manuals
    • Vienna Assistant
    • Vienna Ensemble Pro 7
    • Synchron Player
    • Synchron Piano Player
    • more...
    Instrument Manuals
    • Big Bang Orchestra
    • Synchron Collection
    • Special Editions
    • Changelogs
    • more...
    Tutorials & FAQs
    • Installation iLok
    • iLok Video Overview
    • Sibelius Integration
    • FAQs
    • more...
    Company
    • About Us
    • Team
    • Press Area
    • Contact
    • Send a Message...
  • en|de
  • Toggle Light/DarkMyVSLMyProfile
    Login
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.Feature request: "light" versions of Dimension Strings patches 7/30/2015 9:09:53 PM

Hi! :-)

I just want to bump this thread. I would like to request again that we could get "light" versions of the Dimension Strings patches. It would really help save resources when the full ensemble is needed.

Thanks!
MOH

 

**Oops I see this is in the wrong category. If possible please move the thread to the Libraries category. Thanks!

2.Solved: Vienna Ensemble Pro Adding MIDI Offset to Regions in Cubase 8 7/15/2015 3:37:05 PM

P.S. This issue is confirmed on another system as well. Both Mac and PC.

3.Solved: Vienna Ensemble Pro Adding MIDI Offset to Regions in Cubase 8 7/15/2015 3:05:39 PM

Solved: This is normal behavior of Cubase. This thread can be deleted.

Hi All

In Cubase 8, once I add Vienna Ensemble Pro to a session Cubase starts adding MIDI Offset to newly recorded regions (see photo). The value it enters seems to be random. Additionally, once I delete the Vienna Ensemble Pro plugin the problem persists even though VEPro is no longer there. Even weirder, once this happens and I start a blank new session the problem carries over to the newly created session.

Any ideas? This does not happen in Cubase 7.

 

Update... this seems to also happen with other plugins too. Not sure what's up here or if this is even something to be worried about. Will speak with Steinberg.

4.Bad timing problem with Orch. Violins Spiccato 3/16/2015 11:58:38 PM

FWIW I took DG's advice and turned off the first round-robin in VI-Pro. Indeed it fixed it.

5.Bad timing problem with Orch. Violins Spiccato 3/16/2015 11:52:41 PM

And here's Appasionata Violins perf-rep_spi, which is also fine

https://drive.google.com/file/d/0B-YeePfV2tlbb1RWT3hnMVotOHc/view?usp=sharing

So I really think that this is a problem with Orchestral Violins

6.Bad timing problem with Orch. Violins Spiccato 3/16/2015 11:47:30 PM

I should add that Dimension Strings is nowhere nearly this badly off, though:

https://drive.google.com/file/d/0B-YeePfV2tlbTDZPam5Sai1DYTg/view?usp=sharing

So I guess I'm just really questioning why this is a "feature" of the patch and not a bug...

7.Bad timing problem with Orch. Violins Spiccato 3/16/2015 11:41:28 PM

Wow I never realized how late it is.

OK. Well, I guess I'll consider this "resolved".... ... .. 

Thanks

8.Bad timing problem with Orch. Violins Spiccato 3/16/2015 11:18:34 PM

Hi All

Has anyone noticed this about the orchestral violins spiccatos (perf-rep_spi)? This passage should just sound like straight 16th/32nd notes, but the spiccato patch is making it swing:

https://drive.google.com/file/d/0B-YeePfV2tlbVnlzcW5tWVlqVVk/view?usp=sharing

Here is the same passage, as it should sound, but with staccato_short:

https://drive.google.com/file/d/0B-YeePfV2tlbb2xwWG1rWFlkWTQ/view?usp=sharing

 

Please advise.

Thanks!

MOH

9.MIDI confusion. 1/30/2015 6:57:21 PM

VSL goes into the studio and records a flute playing every possible note. All these note recordings are then saved into a single file.

When you press a key on your piano, VSL's software looks up what note you've pressed and plays black the recording of that note. When you release the key, VSL's software stops playback of that note.

MIDI, or Musical Instruments Digital Interface, is simply a standardized set of commands (a "protocol") that tells the software how and when to do this, i.e. start playing A#; stop playing A#; make A# louder etc. Thus, MIDI is not audio, it is a simply a set of instructions about how to play existing audio. The MIDI protocol therefore must encompass a variety of different actions which correspond to different aspects of sound making , such as:

- note on: start playing a note

- note off: stop playing a note

- velocity: how hard a note was played

Your keyboard speaks "MIDI-ese" and so does VSL's software too speak "MIDI-ese", and it's because they both speak this same language that they are able to work together to produce the coordinated dance of instructions that equates to a musical performance.

Now to your question:

Your sequencer -- whether Cubase, Garageband, Logic, etc. -- is simply is a recorder of this MIDI data. It sits in between your keyboard and VSL's software. When you play your keyboard, you generate MIDI data and your sequencer remembers this data which then passes it along to VSL's software. Us humans need some way to look at this data so that it makes sense to us. Sequencers typically displays it as "blocks", but there's no real reason that it has to look like blocks, except that it happens to be easy for humans to look at. So, yes, your sequencer generates these blocks. The start of a block corresponds to "note-on" and the end of a block corresponds to "note-off" and by looking at the length of the block we can get an idea of how long the note is.

When you think about it, traditional musical notation is no different than MIDI blocks. Traditional notation is just MIDI blocks represented in a different way. An eighth note is simply a "note-on" message that lasts one-eighth of a beat. In your sequencer, however, this eighth note looks like a short little MIDI block.

Both musical notation and MIDI blocks contain no audio, they are simply a set of instructions which indicate a musical performance for a receiving device. In the case of notation, the receiving device is a human being. In the case of a sequencer, the receiving device is VSL's software. Thus, your sequencer (being the recording device), is akin to what a blank sheet of paper is to music notation: a canvas on which to record and display data.

This is a gross over-simplfication but I hope it communicates the basic idea.

Best
MOH

10.Please Fix - Playback Problem 1/29/2015 4:07:04 PM

Hi Andi!

Sorry for the late reply. Thanks for your response. I am curious, was the solution offered in the Optimizing Sib Playback Doc pre-VIPro 2? Because the solution I suggested above (using Sequence Map) works 100% of the time without any further editing. Please forgive me for this criticism, but having to edit every single pre-legato note using the inspector is just far too difficult and time consuming to be practical, and changing the interval threshold just doesn't really work. I understand that this really is Sibelius's fault for making such a clunky note editing system. It's too bad because as a notation program Sibelius is pretty awesome. Perhaps VI (non-pro) can also include Sequence Map as a feature, and the definitons can be reworked so that everyone can do this. I can't imagine the hell you went through trying to work with Sibelius's incredibly complex playback dictionary.

Thanks again for your time, and best for 2015.

MOH

11.Please Fix - Playback Problem 1/26/2015 4:25:30 PM

Actually, not next topic, and you are both correct.

This user is in Sibelius. As someone who does a fair bit of score prep, I can commiserate. Switching to sustain first then to legato is a small step for a sequencer, but a giant leap for notation. 

Rangi, you are literally going to have to create your own Sibelius matrix where the legato patch has a sustain in the first slot, and then legato in the next, and then use "Sequence Map" as your axis control (in VIPro 2) so that the first note is always sustain and then subsequent notes are legato.

Have fun with this.

While I am a big fan of VSL, and slow to criticize unless I really feel like something is a major problem, it quickly became clear to me that no one over there actually tried their Sibelius mapping in context or this would have stuck out like a sore thumb.  

HTH

MOH

 

EDIT: Addressed my reply to the wrong person. Apologies.

12.swapping Dimension players 1/25/2015 8:25:57 PM

VIPro?

13.swapping Dimension players 1/25/2015 5:25:24 PM

In Vienna Instrument Pro Standalone only: ctl + alt + w

 

Not sure about Vienna Instruments (non-pro).

14.Performance questions about Dimension Strings 1/20/2015 3:55:23 PM

Oops! My bad. Back to high school math for me, eh?

Thanks. I will persevere and hopefully I can fix the problem.

As long as I know that someone else out there is running it without any voice limits that gives me hope, though it does seem that at some point almost everyone experiences a voice limit ceiling making certains types of writing precarious. 

FWIW I have indeed experimented with this setting.

Thanks again!

MOH

15.Performance questions about Dimension Strings 1/19/2015 2:14:19 AM

Well that's a good news at least! :-)

But you did have drop outs on runs.

When I get a chance I will see exactly how much polyphony my system can handle. On the last project I did (orchestrated a musical) the score got very dense at times, and Dimension Strings was always the choke point.

Thanks for your input!

16.Performance questions about Dimension Strings 1/18/2015 4:48:46 PM

Hi Stephane!

I've experienced the same thing, however, if I leave that section of music for a while, when I return to it I again experience drops. For me, this fix is quite unreliable because sometimes it will play OK but then begin to drop again on the 3rd, 4th, or 5th play. Furthermore, what if the whole piece struggles to play because of the density? It's too easy to get voice counts above 2500 with DS. Having to play through a piece multiple times is an incredibly frustraing experience, because "quick fixes" now turn into 10 minute slogs while I put my DAW in loop playback and leave the room for 10 minutes while it attempts to load everything. 

It's curious that doing anything in Cubase or MIR has any effect, because isn't the issue hitting the voice limit and not CPU spikes? I think the high latency values that you are describing are quite unwieldy for doing any sort of composing since there is just too much lag in order to play naturally. Maybe it's OK for mixing. 

My template could load in less than 2 minutes if it wasn't for Dimension Strings, but because I have to increase the DS preload buffer to >8192, loading is quite a painful experience. 

Since no one yet has chimed in to say that they can run full DS without any problems, again I'll reiterate my stance that DS absolutely needs some lighter patches-- please: no reduced velocity layers, just save the enembles as single patches. The solo players are already well balanced with each other, and each ensemble size (div2, div 3, etc.) already has its own slot in MIR. Not to mention that it would make customizing the patches in VIPro much easier, since instead of making changes to 8 slots we'd only have to make changes to one slot. Not to mention that VSL could benefit from being able to drop the system requirements on this great library. I can't see the drawback to doing this, except for the poor guys at VSL who actually have to do it :-P 

Thanks for the input.

MOH

17.Performance questions about Dimension Strings 1/17/2015 5:21:54 PM

Hi Goran

But what about using also Dimension Violas, Dimension Cellos, and Dimension Basses? Just Dimension Violins is fine--- the problem is using Dimension Strings as a full ensemble: when 2 x Dimension Violins, Dimension Violas, Dimension Cellos, and Dimension Basses are all playing together.

I'm using VEPro.

My CPU level is fine, it's voice stealing/streaming that is the problem. 

Thanks

MOH

18.Performance questions about Dimension Strings 1/16/2015 5:46:13 PM

Sorry I should mention too that there is usually other stuff going on as well (ww, brass, perc). But that's not the point, really, because I can do whatever I want with orchestral strings + chamber strings + appassionata + solo all playing together. It's DS incredibly high voice count that is in question.

 

If I'm doing the math correctly:

8 x violins x 4 velocity layers = 32 voices for one note x 2 sections = 64 voices for violins

6 violas x 6 celli x 4 basses x 4 velocity layers = 576 voices for violas/celli/basses

Total for 5 notes: 640 voices

So if two voices overlap for even a second (which happens all the time) that will double that number to 1280 voices.

19.Performance questions about Dimension Strings 1/16/2015 5:36:18 PM

5 instances of VIPro in VEPro with MIR Pro = 2 x DS violins, Violas, Celli, Basses.

Everybody playing together in legato with Velocity XF turned on. Depending on the passage of music, sometimes I can get away with it. But as soon as I start having lots of motion in the voices I get red lines, especially if there is a fast run somewhere.

The problem isn't CPU spikes but voice stealing (red lines on voice count). DS strings preload size at 8192. 

Thanks Goran

20.Performance questions about Dimension Strings 1/16/2015 5:18:05 PM

Well, you could always render the midi to audio. For me, this is something that I never want to do until it's time to bounce or archive the project.

P.S. It's not uncommon for sample developers to offer "light cpu" patches. All of my other VSL libs run fantastically well and I couldn't be happier. But in the case of DS with its high voice counts, I think it's warranted.

Best
MOH

21.Performance questions about Dimension Strings 1/16/2015 3:29:44 PM

I believe I have wrote about this before, here and elsewhere. I have 2 monster machines--- master/slave, both 6 core i7-4960x turboed to 4.0Ghz, 64 GB of RAM, SATA 3 SSDs. I've been working with this library for a while now, and I have to concurr with the OP. There's just no way to run a full ensemble of DS without voice dropouts. I've tried every conceivable setting and every conceivable file distribution. Sometimes I can get away with turning off Vel XF, but this is an unacceptable kludge of a workaround. If someone out there is doing it successfully I would love to hear how. 

 

My wish is that VSL would re-save the enembles as single patches, because streaming 8 patches at once to get a single note is just killing the performance of this otherwise great library. Lord knows how people with lesser machines are making out with it. I realize that the power of DS is its ability to vary each solo instrument, but realistically most of the time I'm using either the full ensemble or divisi a2. Just having these two options would be fantastic. 

 

Thanks for your great products!!!

 

MOH

22.Andy Griffith Theme song (The Fishin' Hole) Whistler demo 1/10/2015 9:58:25 PM

lol!

23.Looing for new DAW - what do you prefer? 1/7/2015 7:58:45 AM

Cubase. I started on ProTools, then went to DP for many years, then switched to Cubase about 3 years ago and never looked back. For orchestral writing, it's hard to beat. Though lately I've been checking out Logic and I must say the Environment is pretty awesome...especially if you like to highly customize your template. 

24.Feature Request VI Pro - Controller Speed Ratio Setting 12/16/2014 4:46:02 PM

I really thought you would be able to do this in Cubase with a simple input transformer, but argh, when I tried it I see that once you change modulation to expression you can't send through modulation any more. They should add a "copy" command to the input transformer. I love Cubase but I wish they would create something like Logic's Environment.

In any case, the best way to control expression and modulation at the same time is to use a multiball in Lemur. It gives you total control over the dynamic envelope. Or, with a little knowledge in Lemur scripting you can have several faders that output as a ratio of each other.

 

HTH
MOH

25.Composer Tools for Liine Lemur 12/8/2014 6:01:17 AM

Hey All! 

I wanted to give you a heads up about a Lemur controller I've just released on my website, midimockup.com.

It's called Composer Tools and it is a comprehensive suite of tools designed specifically for composers. With it you can create 126 presets for your virtual instruments collection, and recall them instantly--- directly from your D.AW.! Composer Tools also has a sophisticated divisi script which allows you to assign any note, to any channel, in any order. No knowledge of Lemur scripting rquired. 

Since I primarily use VSL instruments,  I of course use a lot of VSL instruments (and MIR) in the demo video. I think VSL users in particular will find it useful as a way to create presets for their instruments, since there are so many articulations to choose from. In the demo, I use VSL Woodwinds to show you how to use Composer Tools to play with different voicings. You could also use it to voice all your Dimension Brass instruments from a single track. The possibilities are endless.

Hope you enjoy it!

Best,

MOH

4 Pages123>»
Go to Page...

Loading...

Icon
Loading Search Results...

  • Forums
  • Search
  • Latest Posts
  • Terms of Service
  • Terms of License
  • Privacy Policy
© 2002 - 2022 Vienna Symphonic Library GmbH. All Rights Reserved.
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.