When the Output was set to Microsoft GS Wavetable Synth in the Cakewalk, the playing back of this file resulted the six consecutive C5 notes, with bending up to 1, 2, 4, 8, 16 and 24 semitones at their ends, according to the MIDI Pitch Bend Sensitivity (RPN 0) messages, i.e. Then I have inserted MIDI Pitch Bend Sensitivity XXX messages just before the note message, where the values denoted by XXX were 128, 256, 512, 1024, 20 in order to specify 1, 2, 4, 8, 16 and 24 semitones as limits of the expected bending range. It contains only 6 consecutive C5 notes in the first MIDI channel.
The reproduction of the symptome: I created a simple test file, see the enclosed file "svca-test-pitch-bend-range.mid". Until I met that problem related to setting the pitch bend range, which one I mentioned in the Symptome above. I was able to play different MIDI files through the SVCA with quite good sounding, so I was really satisfied with the first results. I set the path to SVCA files for the Cakewalk, the Cakewalk recognized it as a VSTi successfully, so I immediately started learning about the SVCA. The installation seemed to be taken place without any problem. After the payment was completed, I was able to initiate the installation of SVCA from Roland Could Manager by a single click into my PC (CPU: Intel Core i5-4460 3.2GHz RAM: 8 GB) having Microsoft Windows 10 Home version 2004 operating system. The story and the circumstances: At the end of December of 2020, I purchased an SVCA software synth via Roland Cloud Manager. My question: what settings are needed for the proper operation of "Pitch Bend Sensitivity" MIDI messages in case of SVCA VSTi in CbB? RPN 0 XXX) messages do not modify the sensitivity range, but set the MIDI Channel Volume according to the value of MSB part of XXX, instead. Symptome: in case of Roland Cloud Sound Canvas VA version 1.1.6 (hereafter: SVCA) VSTi in Cakewalk by Bandlab version 2020.11, build 099, the MIDI Pitch Bend Sensitivity XXX (i.e. I have some problem with SCVA in CbB, please, do read it below:
0 kommentar(er)
