Vienna Symphonic Library Forum
Forum Statistics

197,145 users have contributed to 43,056 threads and 258,543 posts.

In the past 24 hours, we have 3 new thread(s), 12 new post(s) and 57 new user(s).

  1. Home
  2. General & Hardware
  3. Automatic sample detection - why is it not possible?

  • Automatic sample detection - why is it not possible?

    DominiqueD
    DominiqueD

    Hey everybody. Can anybody explain why automatic sample detection isn't currently possible to implement? I mean that when you play a short, somewhat accentuated note, the Vienna Instrument automatically would make a guess about which sample would be most appropriate and in this case - hopefully - would choose a staccato sample. Accordingly it could switch to legato if the notes played are somewhat overlapping etc. If it was even more sophisticated it might even take the notelength in proportion to the tempo into consideration.

    Now I know that this probably might not be possible in a live situation, but could it be done similarly to the 'learn' function to optimize ram? This could be a huge timesaver. Of course there might be several limits to that but that could be easily dealt with by for example overruling such automatic decisions with keyswitches. I guess the speed detection feature is something on that line of thought.

    Or is there just no demand for such a thing? Don't get me wrong, I'm not criticising, just interested in how far this concept could go
  • D
    D

    The length of a MIDI note is determined by the time before note off command. As this is not send until you take your hand off the keyboard, how would VI know when you were going to do it?

    DG
  • DominiqueD
    DominiqueD

    I guess that's why it cannot work in realtime. But couldn't it be done similar to the 'learn' function, where VI detects which samples are used and unloads the rest afterwards? Is it impossible to detect notelength etc. in such a 'learn'-pass?
  • J
    J

    Actually, the "speed matrix" works pretty well for "guessing" what the player is doing.  It's simply based on how fast a player is playing a passage.  It should only be used for simple passages though as it's only comprised of, at the most, four patches but when used in conjunction with more complicated matrixes it works quite well IMO and saves a little time too.
  • D
    D

    Hmmmmm. I always find the attack of the first fast note too slow and the last one too fast because of the inability of VI to read my mind. therefore I always KS as it is quicker and gets better results for me.

    DG
  • J
    J

    Yeah, you have a good point there.  I guess I should have clarified that I use it for sequenced passages.  As the DAW plays the passage I manually adjust the attack and expression faders to suit my needs and record it in real time.  Works for me anyway.  
  • Cyril BlancC
    Cyril BlancC

    The speed matrix has funny behaviours :

    If after a few short notes you end with a long note it plays a short note !

    ............
  • DominiqueD
    DominiqueD

    Though by all means a great feature, I understand that these limits of the speed matrix stem from it being a real time controller. I was asking if it's possible to make a sophisticated guess which sample could be meant after the notes have been played in. So you play in a part, choosing say a legato patch. All you hear while playing is the legato patch (you don't use keyswitches while playing). Now, after the part is played in, you could then click a learn-button. The engine runs through the part, detecting e.g. notelength, attack, overlap etc. After that, it makes a guess which sample could be meant for each note and automatically sets the according keyswitches.

    After that you can start tweaking the part to your likings, change keyswitches where you find the guess inappropriate etc. It's a bit like automated keyswitches. Instead of hitting a keyswitch while playing to switch between staccato and legato, you just play legato and the engine detects it afterwards.