Vienna Symphonic Library Forum
Forum Statistics

199,402 users have contributed to 43,164 threads and 258,953 posts.

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

  • Vepro reading Note0 vel 9 as 8?!?!

    Hi,

    I'm struggling why vepro is reading my note 0 (c-2) value velocity 9 as veloctiy 8? As seen in the gif below it reads the 20 as 20 but the input 9 comes out as 8. I've tried this identically inside cubase without using vepro and it reads normal so vepro is misinterpreting it somehow.

    I'm using cubase with expression maps. Also if you noticed the other script in kontakt Flexrouter that is bypassed during the gif I shot. I also even tried removing it completely but still the same. Anyone help me why it is misreading this?

    https://i.gyazo.com/d54c52e866b8af9c82585e2ea02302db.gif


  • This is still happening. Can anyone else test this for me? Note0 Veloctiy 9 is coming out as 8 in vepro. This is quite ridiculous. 

    I've tested this in a blank vepro and a blank cubase session without expression maps and no instrument just a blank kontakt session. Simply inputting a note from a midi channel to the vepro konatk instance, any note c-2 - g8 velocity 9 outputs as veloctiy 8. This does not happen if you open kontakt in Cubase only if it talks to kontakt within vepro.


  • I've started asking some users on vi-control.net forum to confirm if anyone else was experiencing this. And it seems that they can reproduce the problem I am having with Cubase (latest version) and Vepro (latest version). However, a user reported trying this on Logic Pro X and could not reproduce the problem. 

    I can't speak for the remainder of the daws but the problem seems to either be Cubase translating the message out to Vepro wrong or Vepro reading the message wrong from cubase. 

    *Updated*

    If I'm doing/reading this right. I inserted a mini monitor onto the midi track from cubase sending the singal. It seems that it is sending out the correct value of velocity 9 to vepro however vepro is misinterpreting it as velocity 8.

    https://i.gyazo.com/005845fbbf1a60e016542ef4b2e15d16.png


  • *more Updates*

    Another user responded and investigate it even further that there are actually more than just one velocity doing this.

    9 (out as 8)

    13 (out as 12)

    18 (out as 17)

    26 (out as 25)

    36 (out as 35)

    72 (out as 71)

    104 (out as 103)


  • Hello Dillon, 

    Thanks for reporting, we will look into this as soon as possible. 

    Best,
    Paul


    Paul Kopf Head of Product Marketing, Social Media and Support