Promidi

If you don't use the Nvidia output - disable that. That's done in device manager under system devices > "High Definition Audio Controller". You might have three there. One of them is for the Nvidia, the other two are for the LGTVs. As a test, disable them all. See if that makes a difference. Then enable one at a time until you find the one for the LGTV audio. Just leave that one enabled Also, when you have found the LGTV one, make sure its sample rate is the same as the Focusrite.

Not possible. That would make this a feature request.

Look for everything you can on your system that could use sound and set the sample rate to match that of your project. That noise in the MP3 sounds like something else is attached to the Scarlett at that same time. Even though that "something else" isn't actually generating anything, it might still have a handle on the Scarlett. Go to your Windows sounds settings and make sure the sample rate set there matches what you use in your project Quick short to Windows sounds settings, start run "%SystemRoot%\System32\mmsys.cpl" Also, while you're there, turn off windows sounds (Under the "sounds" tab, set to "No Sounds" Mind you, it's strange that the exports also contain the noise. Does the noise also happen in the exports when you turn off fast bounce (in the export options, lower tight)?

Knowing which version of Cakewalk by Bandlab and which Instrument would be handy. Try turning off "Zero controllers when playback stops" Preferences | Project | MIDI > deselect Zero Controllers When Play Stops Another thing to look at your MIDI prepare buffer Preferences | MIDI | Playback and Recording > under playback , try increasing this value (The default is 200)

Also, the MIDI transforms can convert one set of MIDI data to another on the fly. For instance, say you have a synth that uses polyphonic aftertouch (an example being Z3ta2) . Now, at this time, the PRV has no way to display polyphonic aftertouch (maybe a feature request). However, it can display Channel aftertouch MIDI events in the PRV. The MIDI Transform in articulation maps can convert the displayed Channel aftertouch into Polyphonic Aftertouch in real time. The beauty of this is that you can keep the Channel aftertouch events in a form that can be readily edited in the PRV. Articulation maps will convert them to Polyphonic Aftertouch in real time. Before articulation maps, editing polyphonic aftertouch events was a real pain.

You can route the audio data via an audio send. However, at this time, there is no such thing as a MIDI send. Until this is available in Cakewalk, you could use a VSTi that has a MIDI Thru function. Then you can route its MIDI out to as many synths as your CPU can handle. MIDImonitor 1.3 is an example of a VSTi that does MIDI Thru https://pw.promidi.com.au/softopen/midiMonitor_x64.zip

Are you sure it's this Monday? Nothing on their website yet? Maybe a timezone thing? (It Monday midday here as I type this)

What driver mode are you using (ASIO is prefered) What sample rate, bit depth and buffer size are you using?

You might want to update your Vdist runtimes. See: https://support.microsoft.com/en-au/help/2977003/the-latest-supported-visual-c-downloads

The answer to that question is only going to come from someone who has deep programming knowledge. Maybe drop a note Cakewalk support at https://help.cakewalk.com/hc/en-us/requests/new?ticket_form_id=360000025633

It won't show you the actual note. However, you can tell which note it was pitch bending it to by working out how many semitones you have raised the pitch by. In the particular example above , and assuming you've configured Surge to use the default range of two semi-tones, it would raise to pitch by a semi-tone, or one interval. (although that final Pitch band event would be out of tune because it's not exactly half) Now , say you have increased the range of Surge's pitch bend to 12 semi-tones, then you need to do a bit of maths The maximum range of numbers a pitchbend event value can have is -8191 to 8191. To raise the pitch by an octave, you would have to issue a pitch bend of 8191 Say you still had Surge's pitch bend range set to 12 semi-tones and you wanted to raise the pitch by 5 semitones. In that case you would issue a pitch bend of 8191 multiplied by (5 divided by 12). The equates to 3413. That would give you the 5 semi-tones bend. I know this sounds complicated, but the latest version of Cakewalk by Bandlab has articulation maps. With these you can build MIDI transforms that can convert pitchbend events that use the entire range to any other range. You can create 12 MIDI transforms, each named interval number 1 to 12 respectively. So say you want to to an articulation map to convert an octave shift to a shift of 5 intervals. First set Surge to have a pitch bend range of 12 semi-tones. Then create an articulation map with the following settings: Under the "Transform Existing MIDI Events" section set both Kinds to "Wheel" Leave the range on "In(min/max)" to between -8192 to 8191, but set range on the "Out(min/max)" to between -3413 to 3413 Then you can use articulation maps to convert existing full ranged pitch bend MIDI events to the range as set by the articulation map. Of course you would have to create another 11 articulation maps for the other ranges. However, you would only have to do this once, then you can export these articulation maps for use in future projects.

.

The only option with this synth is for the pitch bend to affect all notes at once. What is it exactly you wish to achieve?

Pitch bend usually acts on all notes at once. Unless the specific synth acts on just the highest or lowest note played. I really depends on the synth and how it responds to pitch bend. What synth are you using?

Are you talking about using pitch bend events of a single note, or are you talking about using portamento on two notes where first note ends after the second note begins (legato). All methods are possible in the PRV. Whether your synth responds depends on the synth itself.

Thinking further about this, I am thinking that the Vdist runtimes might have been the culprit here (which would have been reinstalled).

No. I mean internally able to take advantage of multiple cores or your CPU. I.E. I believe a a single instance runs on one core only.

The reason I said test that specific plugin is to make sure that the GPU on your Graphics card is doing it's job of increasing GUI performance. If this was a common issue among Cakewalk by Bandlab 2020.11 users, these forums would have lit up with "me too" in response to your question. Personally, I am suspecting something with your system rather than Cakewalk itself. Sure, uninstall and reinstall Cakewalk by Bandlab if just to rule that out.

I am not sure a reinstall of Cakewalk by Bandlab will actually make a difference. As a test (and if you have the plug in) try an instance of Cakewalk's Linear Phase EQ (The one that was added to Sonar in April 2016). Then mess around with the GUI (adding bands) and see what kind of graphic performance you get there. (This plugin uses OpenGL for the GUI) Is Cakewalk the only program experiencing this lag? Are there any other processes running in task manager hogging the CPU (I guess you would have checked that)

Not here. What graphic adapter do you have? Do you have the latest drivers for it? (Check using manufacturer's websites rather than Windows updates)

Did anyone notice MTurboAmp is now in Alpha? Select it when installing. Also, it appears to be part of the MCreativeFXBundle bundle.

Personally I have found the VST2 version to be more stable than the VST3 version - especially when using multiple tracks. I find I have to use several instances as ST4 itself is not multi-threaded.

The latest version of Bandlab Assistant is 6.2.0 Download the latest installer from here https://www.bandlab.com/download/assistant/windows Make sure the Bandlab Assistant process is not running before installing. Go to Task Manager and make sure Bandlab Assistant is not listed under "Processes"

All Meldaproduction plugins have been updated to 14.12 https://www.meldaproduction.com/downloads List of changes here https://www.meldaproduction.com/changes-test#changes-14.12 https://www.meldaproduction.com/changes/?product=MSoundFactory https://www.meldaproduction.com/changes/?product=MPowerSynth

"IPP" was a little obscure (to me anyway) - I did not even notice it....