Acousticsamples

woocaash · Post by **woocaash** » Sat Feb 11, 2017 5:17 am

I am hammond organ player. Own A100 and Leslie 122.
While playing this VST from time to time (every couple minute) one random note gets sustained.
Nothing can stop this and the note just sounding.
I have to reset all MIDI in my DAW.
This makes it impossible to use.

Contacted customer support and received an answer that it is my hardware fault.

I have hundreds of VST instruments, effects and other plugins. Playing on this particular setup for a long time and never had or have a single issue. VB3 also works properly.

This plugin unfortunately not.

Every time customer support tried to screw me up.
They said is impossible and asked me for recording.
Unfortunately you can not record this in DAW.
I had to record a video and then they made up a story that it is my keyboard.

So very simple how can that be that B-5 is the only plugin that doesn't work properly.
Software must have some kind of bug with my settings/setup because I know people are using it.
I am just not sure if everyone is playing on 3 different midi controllers at the same time.

Please help.

As of now it is useless for me and not playable.

My setup is:

Panorama P6 midi controller for: upper manual
KAWAI MP11 stage piano for: lower manual
Roland PK-5A midi controller for: bass pedal
Cubase Pro 9
RME FireFace UFX+
Windows 10 LTSB

Thank you

PEACE

Teksonik · Post by **Teksonik** » Sat Feb 11, 2017 6:36 am

Sounds like the plugin is just not seeing a Note Off message once in awhile. If this doesn't ever happen with any of your other plugins it almost has to be the B5 at fault. It uses the UVI Workstation plugin so maybe contact UVI directly and see what they say ?

https://www.uvi.net/

ErikH · Post by **ErikH** » Sat Feb 11, 2017 8:49 am

Does it happen on all keyboards you use? It it's only the P6 it may perhaps be linked to the aftertouch, or better: to th interaction between the aftertouch (if still on) and the coding of the B-5 inside of UVI workstation.

I'm having the opposite problem and am trying to find out what and how: my QuNexus mini keyboard ( I use it for the aftertouch) sometimes refuses to produce any sound anymore, and this whilst there is still indication that midi info is being being sent through.

In Cubase - I also use 9.1 - instead of an Instrument track, you can use a Midi Track and add Midi monitoring. This should show you the Note Off, or not.

What I also do is never use All Midi Inputs but only the specific input I want to link to.

Not much help perhaps...

Turello · Post by **Turello** » Sat Feb 11, 2017 10:11 am

Try the free ORGANized trio...

otristan · Post by **otristan** » Sat Feb 11, 2017 12:39 pm

Some info from UVI
UVIWorkstation requires note on / note off pairing as allowed per MIDI specification requirement:

Assignment of Note On/Off Commands

If an instrument receives two or more Note On messages with the same key number and MIDI channel, it must make a determination of how to handle the additional Note Ons. It is up to the receiver as to whether the same voice or another voice will be sounded, or if the messages will be ignored. The transmitter, however, must send a corresponding Note Off message for every Note On sent. If the transmitter were to send only one Note Off message, and if the receiver in fact assigned the two Note On messages to different voices, then one note would linger. Since there is no harm or negative side effect in sending redundant Note Off messages this is the recommended practice.

Most Synth do not care about this and if they receive two note on on the same key and one note off will happily kill the two voices which UVIWorkstation don't in order to support retriggered note on which some DAW allows (like in DP)

If you use 3 keyboards there might be some bug in your MIDI interface that skip some note off

Hope this clarify things.

waltercruz · Post by **waltercruz** » Sat Feb 11, 2017 2:28 pm

Not affiliated with AcousticSamples or UVI, but I have B-5 practically since the day it was released, and never had any troubles like this.

thysm00 · Post by **thysm00** » Sat Feb 11, 2017 3:36 pm

Just so everyone know this thread is just about an angry customer that insulted us by email, let us explain a little bit our side of the story.
First, we answered that ticket 12 times between January 30th and February 2nd... How is that for bad customer service...

Now a little information about the problem:
He reported this "bug" to us but would not and could not send us a way to reproduce it... As i'm sure everyone can understand, if you can't reproduce a bug, then maybe it is not one, especially when noone esle has the same problem.
We asked for a MIDI file that reproduces it, and oddly enough, when playing back the MIDI file, even on his end, there was no problem anymore.
When a double MIDI even occurs and recording MIDI, most sequencers will remove one as they consider it a mistake, we then concluded that his keyboard was emitting double strikes and since UVI (and our scripting) just as otristan explain earlier, follow the MIDI norm to the letter, every note on should have a corresponding note off. So, yes, in that case, there is a "stuck" note and this is not a bug, this is simply following the guidelines of the MIDI norm as a "note off" event is missing.

That's where he simply told us to go f*** ourselves... and we stopped answering/helping.

Here is also a quick link to the "nice" video he sent us to help us fix the bug...

Funkybot's Evil Twin · Sat Feb 11, 2017 5:06 pm

To the OP I'd say:

1. As frustrated as you may get, don't be rude when people are actively trying to help you. Reserve telling people to f*ck off until after they stop helping you. I can tell you, having seen the video, that it's far from polite. If I was tech support, was trying to help you, and got that, I'd stop helping you too.

2. I'd try to figure out why you're getting double MIDI messages. Disconnect all MIDI keyboards except the top keyboard, and see if the double notes occur. Disconnect all except the bottom and see if double notes occur. Same for the bass pedals. Do the double notes occur with the expression pedal? Etc. I suspect you'll find that individually the issue doesn't occur, but there may be something in your setup driving the issue.

3. Did you politely ask for a refund? Considering this is an iLok plugin, I'm pretty sure your license can be surrendered without questions about whether or not you're still using the product.

To Acoustic Samples, I'd say:

1. I actually started experiencing stuck notes too, but only after I bought the old Native Instruments B4D drawbar controller. The setup is Yamaha P90 MIDI Out into B4D's MIDI IN and the B4D MIDI Out to my RME Fireface. Also, seems to happen when I use the sustain pedal. Note: the B4D is new (to me), and the Yamaha never did this by itself (old setup; Yamaha directly into RME), so it's clearly the MIDI brain in the B4D not sending enough note off messages, probably when a sustain pedal is being used. My solution: don't use the sustain pedal. Alternate solution: buy a MIDI interface with multiple ins and connect the units separately rather than daisy chaining them. Third possible solution? See next response...

2. I don't know if the issue is with UVI or you guys, but there would be no harm in deviating from the MIDI spec to kill any C2 notes upon receipt of a C2 MIDI Off message just to prevent issues stuck notes entirely. I doubt you'd be the first company to have to work around this and it would get to the root of any stuck notes other users may be experiencing (like me) and just not reporting.

3. Did you offer a refund? Soemtimes, it's the best way to make situations like this go away without anyone's feelings getting too hurt. I'm pretty sure you'd be able to deactivate his license through iLok.

llTheSystemll · Post by **llTheSystemll** » Sat Feb 11, 2017 5:53 pm

seems like it would be pretty easy to install a MIDI monitor type program to log what is coming in on from the keyboard to verify what is actually being received.

i use MidiMonitorFX as an aid to help me map Jamstix to SSD4 and BFD3.

just insert MidiMonitorFX or whatever before B5. once the issues occurs, right click and copy that MIDI data. i personally would weed through it before sending it off but that is just me.

just my opnion.

brian

rifftrax · Post by **rifftrax** » Sat Feb 11, 2017 6:06 pm

woocaash wrote:Unfortunately you can not record this in DAW.

...

My setup is:

...

Cubase Pro 9

Uhhh.... what? Of course you can.

ErikH · Post by **ErikH** » Sat Feb 11, 2017 8:01 pm

I prefer to stay out of a part of this discussion as I understand both sides.
Insulting is never a good idea but I admit my QuNexus' velocity problems brought me very close to it.
Otoh: SA RME FireFace UFX+ - about 2700Euro here - and a KAWAI MP11 show this is way above my level of music making.

This said:
When using Cubase, whether you have a Midi track or an Instrument track, you can open Midi Inserts from the Inspector panel and add Midi Monitor.

thysm00 · Post by **thysm00** » Sat Feb 11, 2017 10:55 pm

1. I actually started experiencing stuck notes too, but only after I bought the old Native Instruments B4D drawbar controller. The setup is Yamaha P90 MIDI Out into B4D's MIDI IN and the B4D MIDI Out to my RME Fireface. Also, seems to happen when I use the sustain pedal. Note: the B4D is new (to me), and the Yamaha never did this by itself (old setup; Yamaha directly into RME), so it's clearly the MIDI brain in the B4D not sending enough note off messages, probably when a sustain pedal is being used. My solution: don't use the sustain pedal. Alternate solution: buy a MIDI interface with multiple ins and connect the units separately rather than daisy chaining them. Third possible solution? See next response...

That's a different issue, the sustain pedal seems to pose problems for some systems, and we actually are working on a new version that will include a fix.

2. I don't know if the issue is with UVI or you guys, but there would be no harm in deviating from the MIDI spec to kill any C2 notes upon receipt of a C2 MIDI Off message just to prevent issues stuck notes entirely. I doubt you'd be the first company to have to work around this and it would get to the root of any stuck notes other users may be experiencing (like me) and just not reporting.

Again, that was going to be my next move before the "f****** ourselves incident, and i did not even mention any of the other very nice things we got. We actually have it fixed in the next version, but the internet/emails seems to often be a very easy way to forget that you are talking to a human being and well, when i get insulted, i ask once to be polite, then the second time i don't answer and it happened here.

If you get that problem, we uploaded a temporary fix, but haven't replaced the official version yet, so just create a ticket and i will send you the updated version.

3. Did you offer a refund? Soemtimes, it's the best way to make situations like this go away without anyone's feelings getting too hurt. I'm pretty sure you'd be able to deactivate his license through iLok.

No, no refund, if it really was a bug, then of course i would have sent him a refund, but it's not. Plus what he does not say is that he has been using the software since august 2016 and reports this only now. So he had time to use it...

murnau · Post by **murnau** » Sat Feb 11, 2017 11:17 pm

Acoustic Samples B-5 organ, VST with a BUG and horrible customer support. Wasted $100 !!!

Fixed the title for you..

Spitfire31 · Post by **Spitfire31** » Sat Feb 11, 2017 11:53 pm

murnau wrote:Acoustic Samples B-5 organ, VST with a BUG and horrible customer support. Wasted $100 !!!

Fixed the title for you..

Funkybot's Evil Twin · Sun Feb 12, 2017 12:18 am

murnau wrote:Acoustic Samples B-5 organ, VST with a BUG and horrible customer support. Wasted $100 !!!

Fixed the title for you..