Nigel Mackay

I need a linear velocity scaler. Similar to the MIDI EQ, but with a tilt facility. For existing MIDI projects that have too much dynamic range. (Or too little.) If set to 50%, it must move velocities below 63 upwards, closer to 63, and velocities above 63 downwards. This maintains the dynamic feel of the piece. I have written a CAL script to do this, but of course it is destructive, and so potentially dangerous if you forget your backups.

Found this: To see if a piece of hardware is reserving a large chunk of physical address space, launch "devmgmt.msc", select Resources by Connection in the View Menu, and expand the Memory node. See what is reserving the RAM. Also, if your motherboard is not happy about the way the RAM is arranged in the slots, Windows will flag it as Reserved. One example: with purchased pairs of memory cards, sometimes one of them HAS to be in Slot 1. Swap the 2 cards around.

It is not Cakewalk per se that is reserving the RAM. Do you have an input device that could be doing it?

Thanks. Fiddling with the velocities is not really an option. 19 instruments. Lowest velocity is 15, highest is 127. If I do nothing the dynamic range is 57dB. On reflection, maybe it is just me that struggles with that much! I will let someone with younger ears listen to it. ?

Ok, this would apply to any system, DAW or hardware, but where else do I ask. If if have a MIDI arrangement that has too much dynamic range, what is the best way to handle it without destroying it? It is classical music. Want to hear that little solo run as well as the piercing blasts on the combined trumpets and trombones. I have tried putting a Sonitus Compressor on each track - Threshold minimum (-60dB), Ratio 1.5:1, Knee 10dB, Attack 0ms, Release 200ms. Am I basically correct?

For what it is worth my vstscan.exe is also version 6.0.3.0. Dated 03/06/2020 15:00. And it works. Details are identical to Milton's.

Start off by watching these 2 tutorials: Number 2 Number 1

Did it work? Or is that where it stops?

When you install it asks you: VST, VST3, AAX. You must install the VST3 version, and you must use the VST3 version.

You just run Bandlab Assistant and go to the extras tab. As soon as you have Cakewalk running, download the SI instruments. That gives you free drums, pianos and bass guitar. Something to experiment with to get you started.

Generally speaking, first install Cakewalk, and then go back for the extras. It seems to give less problems that way. Melodyne is a 30-day free trial, so rather wait until you are ready to experiment with it, and don't waste your trial time.

ProChannel doesn't open if you have a MIDI track selected. Must be audio or instrument.

Try uninstalling and reinstalling Cakewalk. Windows 10 upgrades do nasty things to PCs. ?

I've never actually used AD2, but I have it. And I agree with you about Googling the open HiHat problem - all you get is people struggling with drum controllers. To me it seems that there is a bug with the GM mapping in AD2. Playing A#4 does not trigger a hit, even though it works in the GUI. You can use the "alternative" notes: A#9 - Fully open B9 - 3/4 open C10 - 1/2 open G#9 to E10 are various HiHat sounds. In AD2, click the ? on the top right. Select Map Window. Top left Map Preset GM. Then on the right it shows you all the mapping. Except that A#4 does not work in real life. Because Cakewalk starts at C1 and not C-2 you have to add 3 to the note name they show.

Maybe there is already one somewhere. I just like programming. ? Really old MIDI files used the modwheel for modulation (read vibrato.) These days VSTis use the modwheel for volume/expression. And use aftertouch for modulation/vibrato. This script changes modwheel events to aftertouch events, keeping the value. Will work with any controller, just defaults to modwheel. Change Controller to Aftertouch.CAL

Much obliged. A lot of stuff there.

Does anyone know if there is a CAL script or the like to achieve this? Have a lot of MIDI files that use Velocity to control the volume of the note being played. And too many VSTis only use Velocity to control articulation - all "volume" is controlled with the mod-wheel.

With respect, there may be 30 people struggling to install, but there are 3 million who had no problems. If you look at the posts where people eventually succeeded it is almost always a) not installing BandLab Assistant as administrator b) a missing Visual C++ redistributable c) downloading the addons at the same time as the app d) a missing dll. The first is human error, the others are Windows problems. Windows is the source of many, many problems.

Will do. When I watch YouTube tutorials no-one has ever said that there is a caveat when using aux tracks. Even with a tutorial about aux, busses and patch points.

Version 2020.05. Windows 10. WASAPI shared. Select audio track output and route it to New Aux Track, Route a few more audio tracks to this aux track. Rename the aux track by double-clicking on the name in the track. (If you select the Input entry -> Rename Patch Point it renames for routing but not display.) Everything works fine. Save and close project. Hibernate PC. Wake up PC, open project - no audio routed through the aux track. Route audio to Master, works, route back to aux track, nothing.

Version 2020.05 My project ends at measure 653. When I bounce it processes to measure 1097. Definitely no events past 653. You can see that, and the Events view tells me that. The resulting audio track is silence from 653 to 1097. All the tracks do it. I have tracks with Expression automation. They all draw the line up to measure 1097. If I add an automation lane , leaving it at the default Volume, it draws a solid line from 1 to 1097, and then a dotted one to infinity. If I insert a blank MIDI track and open the automation lane, it draws the line up until measure 1097. And even though all these extra measures are empty, it still takes ages to bounce, as though it is processing events. The announcement points to the wrong rollback installer, so I can't rollback to 2020.04 to crosscheck. EDIT: Just started a new Basic Project, and it doesn't do that, so it seems there is something odd with my project. EDIT: Found a node in automation at measure 1097, but can't find anything else, but selecting any track select all up to 1097. Don't know how/where to look for a stray event. EDIT: Deleted all automation. The moment I add automation it adds the end node in measure 1097. Solution: Found a stray node in the automation of the Master fader. Don't ask.

Right-click in the MIDI track at the beginning of the gap.) Select Split. Choose Split at Selection. Do the same for the end of the gap. Now the bit that has the gap is separate from the rest. Click on that bit and delete it. Now click and drag the left edge of the right-hand bit up to the left-hand bit to close the gap. You might have to play with the Snap settings to get it exact.

No. @Max Arwood has made a mistake. Your workspace is set to Custom. Click on Custom, then select Track Control Manager. For Audio Strips, switch on Interleave/Phase. Make sure that Interleave (just to the right of O Master here) is the same as the mono/stereo input you select (here it is stereo) and also that the phase invert button is also not selected. You might have to make the track height bigger to see them. Not saying that anything is wrong there, but just check. And it is kinda important to have them visible when recording.

Got to Edit -> Preferences-> Audio -> Playback and Recording. If Driver Mode is WASAPI Exclusive it means Cakewalk reserves the PCs audio system for itself. Change it to WASPI Shared.

Drag the Controller pane at the bottom of the PRV open like this: If the controller you want is not shown, then click on the + to add add it. Here, only Velocity is available. Select Draw from the Tools (F9) and click and drag. Snapping is available/optional: