Promidi

See: (whether this will be noticeable with an SSD, I am not sure) https://spitfireaudio.zendesk.com/hc/en-us/articles/360003699998-What-does-Optimise-mean-in-the-Spitfire-App-

And if you are scoring film music, maybe Albion ONE is the library to go for......

Just pulled the trigger on BBC Orchestra Core. Glad I resisted when someone said “It would never get less than 40%”

It would probably be better to list those known not to work. That would be a shorter list.

Please define “the app”

I think the Music Rebalance tool in RX8 Standard (and now RX9 Standard ) is a vast improvement over RX7 Standard. I also had RX7, but held off updating at the time when RX8 was released. I am glad I did. I grabbed RX8 while the free update to RX9 was offered. I am glad I did.

The reason I mentioned it is for those who have Windows 8.x who might have missed that little detail.

Note: The system requirements for RX9 for PC lists Windows 10 only.

Change log https://s3.amazonaws.com/uvi/Release_Notes/uviworkstation_changelog.pdf

When I started using CbB, recording was flawless. It was only with playback that I experienced the very rare pop and click. That was usually when notes requiring CPU heavy synths (MSoundfactory comes to mind) kicks in. In my case, the setting that fixed that, was to disable C-States and Intel Speedstep. That's basically telling the CPU to run at full speed at all times rather than stepping down the clock speed when a higher speed in not needed. As you can imagine, this can play havoc for DAW use that needs a batphone to a full speed CPU. What you can also do is set CPU min and Max to 100% These days, it's not just the shear power of PCs that makes for flawless DAW operation. It's more how they are optimised. Remember, on my lowly, 2014 i5 4670 CPU, I do not get clicks and pops during playback within CbB. For me, 256 samples seems to be my sweet spot. I do play VSTis inside CbB in real-time and I do not notice the very slight latency. Remember, if you are 2 metres from your monitors, the delay there is 5.8 milliseconds.

I am using a PC as per my signature and I do not get “latency/pops/clicks” To me, “Adjust the buffer settings accordingly” simply means adjust so that the latency is tolerable (or barely noticeable) but not getting pops/clicks. There is a document doing the rounds that can help reduce pops and clicks. See: https://download.cantabilesoftware.com/GlitchFree.pdf One other thing I would suggest is to use the Beta Focusrite drivers. The release notes for this specifically mentions fixes for Cakewalk by Bandlab. Using a non Firefox browser, head over to here http://beta.focusrite.com

When you say “I don't use Workspaces”, you mean it is set to “none”? If not, then you’re using a workspace.

I wrote my own in VB2010. I enter a time duration in seconds (to 3 decimal places) and the number of beats in that duration. Then it spits out the tempo.

Are you using any Workspaces? Unless you configure used workspaces not to, those Workspaces will load their own specific Keyboard shortcuts. I use Workspaces and many custom Keyboard shortcuts. However, I have configured the Workspaces I use, not to load Keyboard shortcuts from those Workspaces (Done in “Manage Workspaces”)

Worked for me. Got confirmation email with download link in about 20 seconds.

Desinstale y vuelva a instalar el VST. Sería útil saber de qué VST en particular y de qué versión de Cakewalk by Bandlab estás hablando.

Please let's stop all this talk about screensets being abandoned. There has never been any official evidence that this is ever going to happen. I have used screensets and workspaces (FNA Lenses) in my projects for quite a while now For me, Screensets and Workspaces have worked flawlessly and harmoniously to date. Scroll up my previous post in this thread (April 30, 2020) for more info.

The latest version is actually 3.1

How are the pitch bends getting there in the first place? I do many MIDI only projects and use pitch bend all the time. The only pitch bends that get put in there are the ones I have intentionally put in there. I always remember to put a Bend = 0 event afterwards. I have written a CAL script that zeros last pitch bend event of a group of selected pitch bend event to make the easier. This CAL script is bound to ALT E I have written another CAL Script that automatically places a Bend = 0 slightly before every selected note. If no notes are selected, it puts it at the NOW cursor. This CAL script is bound to ALT W

Ok. There is not really way for the PRV to ignore previous controller changes. It has to be programmed in the synth. For instance, to get a synth to not respond to pitch bend, you have to find a way to set that synths pitch bend range to zero. The method depends on the synth. You may be able to issue a specific NPRN command - again, depends on the synth. Some synths respond to RPN0 > 0 (TTS-1 being an example) Events to set the pitch bend range to zero.

Which synth?

Well it depends on the synth. TTS-1 can use RPN0 for pitch bend range. Rapture needs to use an NRPN event If a synth’s pitch bend range can be automated, then that same parameter will be listed as an NRPN If you check the list of any synth’s automatable parameters, you will find that list will match the list of that synths NRPN parameters. If the pitch bend range of Cakewalk Sound Centre can be automated, then it will be there somewhere in its NRPN parameter list (I don’t have CSC, so I can’t test)

The NRPN parameter names that appear depend on the actual synth used. The Bend Up/Down parameters are Rapture. The NRPN parameters you’re seeing are for TTS-1 For TTS-1 you need to use RPN0 This is the GM standard for pitch bend range, which TTS-1 adheres to. In TTS-1, to get the actual RPN value , you multiply 128 by the pitch bend range you want. To get a range of 4 semi tones, you use RPN 0 > 512 (128 x 4) To get a range of 7 semi tones, you use RPN 0 > 896 (128 x 7) To get a range of 12 semi tones, you use RPN 0 > 1536 (128 x 12) I tested this in TTS-1 and this works.

RPN 0 to control pitch bend range is a Roland GM standard (also Yamaha XG). TTS-1 also follows this standard. Even then the RPN values are derived by 128 x Range. However, with many modern synths and VSTis, this standard goes out the window. These synths have their own method. Let’s have another look at Rapture Pro. With NRPN events, you can have 16384 discreet values. However, with Rapture Pro's pitch bend you have 25 discreet values (24 including zero) What the formula does is changes Rapture Pro's 0 to 24 pitch bend range to NRPN Events 0 to 16384 so you know what NRPN value to use Another way to get the NRPN value from the required range is to multiply the range by 683 (Which is 16384 / 24 rounded up) So to get: A range of 4 semi tones, you use NRPN Bend Up 01 > 2732 A range of 7 semi tones, you use NRPN Bend Up 01 > 4781 A range of 12 semi tones, you use NRPN Bend Up 01 > 8196 I tested this by plugging these values into the event list view and the range does change on the fly as the track is playing I had 4 notes (All B2) playing, each proceeded by an NRPN Bend Up 01 event and a pitch bend event at maximum (in that order) Audibly, the notes played the correct intervals (4, 7, 12) even though the note was still displayed as B2 notes according to the PRV I also opened up the Rapture's edit screen and I could see Element One’s pitch bend value change accordingly while the track played.

I just checked mine and they are all there. Maybe flick an email to support@cakewalk.com