![sampletank 3 input problems sampletank 3 input problems](https://www-vintageking.com.imgeng.in/media/catalog/product/cache/c8660c81d7196df55c33284290821786/i/k/ik-multimedia-sampletank-4_124780_1.jpg)
Powered down MIDI controller and removed sustain pedal.Hardware reset to factory defaults on keyboard controller have no effect on behavior.Changing MIDI preferences to timestamp events default, High Precision and Low Precision timestamps, enabling/disabling input for control messages have no effect on behavior.Performing these same steps with Studio One 3.02 with any VST3i (including Sampletank 3.51) behavior is normal and notes do not stick.Performing these same steps with 2 other VST3i - Waves CODEX and Elements - behavior is normal and notes do not stick.WORKAROUND: -> Use the Sampletank VST2 instrument. (It is not down)īUG: -> Occasionally, notes played on the controller do not "fire" at all, but when they do, they stick. Insert the Sampletank VST3i on a track and arm it for MIDI from an outboard MIDI controller.īUG: -> Sampletank detects the MIDI ON for the key, but the note "sticks" as though the sustain pedal is down. Triple Play Synth 1 slot was set to a fast attack piano in SampleTank 3.
SAMPLETANK 3 INPUT PROBLEMS 64 BIT
Fishman Triple Play audio to MIDI SW (using the 64 bit version of the Fishman app 'just because,' it comes with both 64 and 32 bit). I posted another thread on the compatibility thread, but I have firmly established that this is a Reaper 5.x bug with the Sampletank VST3i plugin.ġ. Yes, the GR-50 is long in the tooth but works fine): 1. For now, I'll just use the VST2 version and all seems well.Īny ideas here? Is there something wrong with VST3i and Reaper? I seem to remember some kind of errant midi message being sent with one of the 5.x previews, but I thought this was fixed. I haven't tested all my VST3i's yet, but I can tell you that this is completely reproduceable with the VST3i of Sampletank.
![sampletank 3 input problems sampletank 3 input problems](https://cdn.mos.cms.futurecdn.net/646cefbcb16e3daf87132fd31d797d62-1200-80.jpg)
If I switch back to the Sampletank VST2 version, everything works fine with the Pro40's midi interface and with the 2626 as well. On ARC 3, this permission is required in order for your measurement analysis to appear in the plugin. If you are having issues accessing presets, or if your instruments arent appearing, this may be why.
SAMPLETANK 3 INPUT PROBLEMS PRO
I also borrowed my son's M-Audio Axiom 25, and it did not have this problem, so I'm guessing that it has something to do with my midi input - which right now is a Focusrite Saffire Pro 40, but my M-Audio 2626 has the same issue. This permission is required in order for IK software to access presets, instruments, measurements/analysis, and other crucial software files. I checked everything- unplugged the sustain pedal, ran MidiOX to see what messages were being sent (both ON and OFF were being sent correctly) and tried a bunch of different midi preferences and hardware reset the controller. And, occasionally, some of the keys wouldn't work at all, but when they did work, they would stick on as well. When I fired up my trusty Studio Logic midi keyboard, I started having the weirdest issue- the keys would "stick" on. The other day, I accidentally chose Sampletank's VST3i within a Reaper 5.01 project. Here's an interesting one- just discovered it.