#Plugsound box. zip pro

Here's already a detailed list of the sustain working/not working vsti's, all tested 1by1 without any tweaks, to be sure which ones work 'out of the box' and which ones don't (default install's of Reaper & vsti's) : ДЇor all the same vsti's, when notes are triggered via Behringer UMA-25S (UMA25S midi in port USB) while sus-pedalling on the 2 DSP24 midi-in port keyboards, they are sustained correctly. Vsti's triggered via Main keyboard (88-keys Technics PR-60 E-piano (with it's own incl.sus-pedal) and/or 61-keys Roland D-50 (with a Roland sus-pedal) connected to DSP24 midi-in port. I'll test the ReamoteMidi (with log-check) + eventual Sampletank/Kontakt 5 remappings a bit later today (I have to work a bit ^^)

If that's the case, how can I tell Reaper to consider by default sustain as 0-1 ?Дunno which codes to wrap around the list to make it 'Spoiler-button-like', sorry in advance for the length:eek: of this post. Thus not knowing/being able to interpret a simple On/off command. Nuendo seeing and treating my sustain pedal correctly as 0-1, and Reaper (and supposely Studio One also, but haven't opened it since a while), both see by default my 0-1 pedal as a continuous one with intermediate positions. Not sure, but it looks like the exact opposite of your description : While playing in Reaper & drawing sustain in midi editor, I noticed that I could draw up & down (like velocity), thus looking like partial damping, and that the 'picture' wasn't a 'block' that stretched across the whole measure, but a thin line having the length of the note. Block ON, or Block OFF + length of On/off. ДЄ big red 'block' that I can only re-draw/narrow/widen to Left & Right (sustain start-end). In Nuendo, controller lane for sustain seems to be 0-1 (on-off). it's the first one in weeks that seems to get somewhere :)ДЄn interesting hint/path you're pointing out here. ( If I can't hear the sustainpedal while recording a piano-part. I'd really love to switch to Reaper for good, and this sustain-issue is the last thing keeping me from taking the leap. Please, any hint that could help me understand this issue would be highly appreciated. Why does it occur with only certain vsti's, and not with others ? What is different about Midi sustain-pedal implementation between Steinberg/Presonus/Cockos ? How come that some DAW's function normally, and some don't ? Since Midi is a standard, and sustain cc64 is essential. If so, all my un-pedaled notes should be sustained & shortened when I press pedal.

Д¬an't imagine a pedal-polarity thing either. if it was so, then Nuendo 3 would also reject/bug with the cc64 information/audition. How could a sustain-pedal on one physical midiport affect the notes/sounds on another keyboard that's on a different physical port ?) and press the sustain pedal on my main keyb connected to DSP2000 midi in, the sounds sustains normally. (Strange thing, if I set input to 'all midi inputs' and I trigger the notes (piano f.ex) on the behringer mini keyb. In Nuendo 3, all the vsti's react like they should to my sutain pedal. ДЄnd even without cc64 pressed, some sounds sound 'cut' when I release note (like decay/release inexistent). Midi monitoring shows activity when the pedal is pressed/depressed, but the sustain isn't heard. Their internal Instruments work ok, but Kontakt, Sampletank, Truepianos, AAS stuff (except Tassman which works ok) + others don't.

Д«ut in those 2 DAW's, 3/4 of my vsti's don't react to Sustain pedal (cc64). 'freshness') and I demo-ed Studio One 2.62, and demo-ing Reaper 4.61 now, which seem both to correspond to my needs/vibes. I know my rig is old, but working fine for my uses.

#Plugsound box. zip pro

WinXP Pro SP3, STAudio DSP2000 Audio/midi interface with 88-keys-Master Keyboard connected + Behringer UMA25S mini keyboard with its own USB-midi interface/port (used as transport control + occasional synth line), Steinberg Nuendo 3 & various VSTi's. I have a cc64 issue that drives me crazy, as I can't seem to find out the 'why'of it.

2022.04