Vienna Symphonic Library Forum
Forum Statistics

180,772 users have contributed to 42,140 threads and 254,363 posts.

In the past 24 hours, we have 1 new thread(s), 13 new post(s) and 60 new user(s).

  • Keyswitching bug! Has it been mentioned?

    Well, from my observations (even after installing the latest VI version) all the keyswitching is an octave higher than it should be. When I set a keyswitch to C1, it only works at C0.

    By the way, I just became an official VSL user. I'm excited to show this community what I plan on doing with these lovely little chamber strings. *slowly takes out a knife*

    I own Chamber Standard. My next purchase will be Percussion Standard 


  • Double-check what your sequencer considers to be middle-C. It will be either C3 (Yamaha) or C4 (Roland). C4 is cool, just so you know. ;-)

  • I don't own a keyboard of any kind. When you say Sequencer, I own Cubase. Or is that considered a host and keyboard is considered a sequencer? I thought Keyboard = Remote and Cubase = Sequencer.

    Anyway, I hope you understand this is a BUG just like I said. The bug is in the standalone version on VI and in the plugin. For example, when I try to assign a key using the VI (not the sequencer, not a keyboard) I hit the lowest key on the VI virtual keyboard and it becomes C1, not C0 like it should.


  • I "understand" that you're not getting the octave you think you're getting...

  • last edited
    last edited

    No it's not a bug. Cubase thinks that Middle C is C3. In fact the International standard is C4. There are historical reasons why there are different views on this, but VSL is following the International standard. If you use a notation program like sibelius you will find the same thing. Middle C is C4. I'm afraid that until Steinberg implements a preference for changing their view of Middle C then you will just have to remember that your sequencer (Cubase) is an octave out.


  • Ah. Does that affect anything else such as the octave of notes on a given instrument? 


  • last edited
    last edited

    It affects everything. You will find that all the notes are an octave out from what Cubase tells you. I hope that Steinberg fixes this so that we can choose, as using a transposition causes problems with other things.

    DG


  • Hey everyone. New to the forum... I have a slightly different issue that seems like a keyswitching bug: When I use lower register instruments like Tuba or DB, the keyswitches don't work. Using Cubase, the keyswitches default to C0 for all instruments which work fine for most, but these two instruments won't respond to them even if the switches are assigned to a lower set of keys. Has anyone else run into this? Thank you! Cubase Artist 6 Mac OS 10.7 Vienna Instruments Special Edition

  • Welcome here in the family of VSL Bear1978!

    The time for bugs within the VI is far behind us - at any rate for common applications and uses. 

    So doupt first yourself in connection with the VI ;-)

    OK, your problem:

    Make sure that your keyswitches are not within the playing range of the instruments.

    If "C0" (C-1 within Cubase) is the lowest keyswitch you will also have those of C1, C#1D1 and probably C2 etc.

    This is too high for Contra- and Bass Instruments.

    Either you go down one more octave (C~) (C-2 in Cubase) or above the playing range.

    If you are using the new Vienna Instrument you can see the keyswitches on the built in keyboard.

    As I mentioned: The keyswitches should be outside the playing range of a certain instrument

    Best

    Beat


    - Tips & Tricks while using Samples of VSL.. see at: https://www.beat-kaufmann.com/vitutorials/ - Tutorial "Mixing an Orchestra": https://www.beat-kaufmann.com/mixing-an-orchestra/
  • Text deleted

    Sorry - the upper topic appeared twice...


    - Tips & Tricks while using Samples of VSL.. see at: https://www.beat-kaufmann.com/vitutorials/ - Tutorial "Mixing an Orchestra": https://www.beat-kaufmann.com/mixing-an-orchestra/
  • Well, here in 2012 this still drives me nuts.

    I had NO idea C4 was 'middle C' until I started using Cubase and VSL. One reason I like the new VI update is that it visually shows you which keys do what.

    I wish there was a way to be like with A440 v A442 and say 'This is -my- middle C'.

    ---JC


  • last edited
    last edited

    @Suntower said:

    I had NO idea C4 was 'middle C' until I started using Cubase and VSL. One reason I like the new VI update is that it visually shows you which keys do what.

    I wish there was a way to be like with A440 v A442 and say 'This is -my- middle C'.

    ---JC

     

     In some sequencers it is possible to make this choice. What sequencer are you using?

    DG


  • Cubase. Is there an option like this for Cubase?


  • last edited
    last edited

    @Suntower said:

    Cubase. Is there an option like this for Cubase?

    Nope, even though users have been asking for this for years.

    DG


  • By trial and error I learned that a C2 in Sonar triggers what is called a C1 in the Control panel of VSL. This has never been a problem once I learned how it is mapped. (And this confusion affects lots of software and keyboards. I had the same challenge with MusicLab products like RealGuitar and RealStrat. Funny, since almost everything else in MIDI is so well standardized.) By the way, one great feature of VSL is that every factory matrix uses the same keyswitch for the same articulation whenever possible and logical. This means if I decide to change from solo violin to chamber to orchestral, or move a second violin part to viola, I don't have to redo all the keyswitches. I don't need sticky notes all over my monitor to keep track of how to trigger legato v sustain v detache, etc. Contrast this to Hollywood Strings which has a very confusing hodge-podge of controls. (I am not being mean and Hollywood can sound good. I just think the VSL system is much more efficient for people and computers.)

  • At the risk of sounding even whinier than usual, this is why I want some sort of VST Expression.

    What -I- is some gizmo that sits next to my keyboard with some combination of levers/switches that I can set up for 'Stac', 'Sfz', etc... REGARDLESS of what VSTi I'm triggering. And -somehow-, using MIDI, usb, steam power or 'space magic!', the gizmo sends the proper 'command' to whatever MIDI track I have in focus in my DAW.

    I don't want to have to remember that C#1 is stac for violins... and C#6 for CB... when using VSL and then F#1 for EW flutes. I just want a UNIVERSAL STACCATO BUTTON. I take a day (and a fifth of gin) and program the device like a garage door opener, write labels on each button and then I'm -done-.

    In short, I think keyswitches should be disconnected from MIDI notes altogether so they can be 'transmitted' in some way that is universal and, above all, requires no memorisation of any kind. I thought Steinberg was -really- onto something with VST Expression and I'm sad that nobody else seems to have gotten on the bandwagon.

    And while I'm ranting... I'm partially disabled. I have crap eyesight and mousing is tough as well. It always annoys me that most software, that is designed for 'creatives' is so poorly set up for disabled people. I can't imagine even a genius like Stevie Wonder using -any- of this software.... or even a web browser... without an assistant. I'm constantly griping because things like taking my eyes off the screen or switching from the mouse back to the keyboard back to the mouse a billion times a day SUCKS. I would MUCH rather go back to MS-DOS or Unix where there was a key command for -everything-. See... a blind guy or even a lot of people with hand problems can do perfectly fine touch typing. It's the MOUSE... which seems so 'creative friendly' which blows.

    My point is that, music software, which should be one thing that disabled people can use to do really cool things, is -much- harder to use than say, BORING PRACTICAL programs like Word and Excel. Which seems kinda backwards to me.

    In America there are standards for GUIs (Section 508) which software devs are -supposed- to work towards... every key has an accelerator, every screen object can be used with a screen reader, etc... Ya know which company is 1,000 miles ahead in compliance on this leftie-progressive ideal? Apple? Nope. Google. Hell no. Microsoft. Boring, outdated Microsoft.

    I'm not sure disabled stuff is even on the radar for euro-software devs of -any- kind, which puzzles me considering how much more 'progressive' the EU is on so many issues. But I've groused at Steinberg (and now VSL) for -years- to make their products easier to use... at the very least to comply with the Windows UI guidelines (accelerators, default buttons for every window etc.) And that -really- puzzles me because, even before I was hurt, I worked MUCH faster when the UI had these kinds of refinements... I think everyone else would find it easier too.

    OK, I'm done. I promise not to rant on this for a -long- time. But this seemingly 'minor' stuff is -maddening- for some of us.

    ---JC


  • I think you're ranting at the wrong company. All of what you want is possible with VSL. It's just that the rest of the developers are still living in the dark ages. There are ways to do what you want, even without VST Expression, but it will take detailed preparation and every time you get a new, inflexible library, you will have to go through the process again.

    DG


  • That is the 'if everyone else would just do it my way, everything would be fine' argument all would be monopolists like to use. I agree that VSL has some pretty superior products, but standards -matter-. VSL has more and more taken the 'walled garden' approach. I understand their reasons but nevertheless...

    Since VEP is a stand-alone app, Vienna can do a lot more than other VSTi developers to address the usability issues I raised. They are not as hamstrung by VST. And like other devs, they also have the option to conform to the standards that Steinberg has put forward (like VST Expression).

    I'm not blaming anyone more or less than anyone else---and I'm certainly no Steinberg fanboy. But the whole DAW market has become so balkanized it drives me nuts. For what -I- do, even if I had all the $ in the world, I couldn't 'live' in a VSL world---they just don't have the product range.

    And I'll go one step further... I think that at least -one- reason music in general is getting so crappy is because you've got these super-sophisticated apps like VSL that are more and more living in their own little gated communities walled off from the general DAW hoipolloi.

    I roll my eyes at all these 'sound construction' libraries, with pre-recorded runs and stings or preset orchestral groupings, but when I think about how much sheer -work- it is to do an equivalent MIDI mock-up... because of all the importing and exporting and hand-editing between a proper notation program and a MIDI sequencer and then mixing and on and on... I start to understand why guys opt for the 'just add water' approach.

    MIDI mock-ups are just too frickin' hard to do given the current state of tech. End of story. And I've concluded that the lack of proper integration between the various components (DAW, sample libs, notators) is the big stumbling block. VSL can improve on VEP and MIR as much as they like, but until all the vendors do a -much- better job of working -together- on some sort of common integration, it's gonna remain much tougher than it should be. I -know- I'm in the minority, but I think the tools to write -text- are, after all these years, still about 1,000 miles ahead of the tools to write music.And everyone keeps focusing on polishing sound quality and making excuses instead of tackling that basic -speed- issue. By -speed- I mean the time it takes to convert my thought into a finished recording. -Way- too slow. It should take no longer to do a decent midi mock-up than it would to write out a score in pencil. Not parts. Just the score. That's the only way to counter all these stupid pre-fab libraries and other sonic wallpapers that pass for 'music' these days.


  • last edited
    last edited

    @Another User said:

    MIDI mock-ups are just too frickin' hard to do given the current state of tech. End of story. And I've concluded that the lack of proper integration between the various components (DAW, sample libs, notators) is the big stumbling block. VSL can improve on VEP and MIR as much as they like, but until all the vendors do a -much- better job of working -together- on some sort of common integration, it's gonna remain much tougher than it should be. I -know- I'm in the minority, but I think the tools to write -text- are, after all these years, still about 1,000 miles ahead of the tools to write music.And everyone keeps focusing on polishing sound quality and making excuses instead of tackling that basic -speed- issue. By -speed- I mean the time it takes to convert my thought into a finished recording. -Way- too slow. It should take no longer to do a decent midi mock-up than it would to write out a score in pencil. Not parts. Just the score. That's the only way to counter all these stupid pre-fab libraries and other sonic wallpapers that pass for 'music' these days.

     

     I certainly agree that i would like to be able to type a score and then it play back the way i want it. as long as I could over-ride the settings when I disagree with the default. However, I can't imagine how much time just working out the playback algorithms would take, and then you have to consider that even when sequencing by hand, some very simple things don't sound good.

    I don't think that writing text is remotely comparable though. What you're really asking for is that the text can sound as if it's spoken by the best actors in the world. I have yet to hear any text speaking program that doesn't make Stephen Hawking sound like a first rate Opera singer. [;)]

    DG


  • OK, here's someting else that you can try.

    http://www.bewaryprods.com/software/products/TransMIDIfier/

    DG