Search the Community

Hi there I'm trying to record the drum sounds from VST3 drums using say Steven Slate or PowerDrum kit etc. and I can get audio OK, BUT when I hit record I cannot get that track to actually "record" Here's a screen shot of the setup I created, and also a short video clip of what seems to happen when I hit record. The one thing I cannot seem to alter is the "Input Echo" button, but I'm not sure if this is an issue or not?! Any ideas on what I'm missing here please? For context I have an orchestral violin score audio file that I've been asked to add a drum track to, and I just wanted to try and generate a few ideas direct from the PC rather than sit at a kit to do it. so the plan was to have the audio track of the violins play and I could just "tap" along to try out ideas I have, then listen back to the entire thing in Cakewalk afterwards. Many thanks in advance. Not recording drum sounds into Cakewalk (Dec 2024) - Made with Clipchamp_1735225018901.mp4

Howdy - I posted this in a post earlier, but thought it would be good to add it here, in case anybody wanted to save themselves some work. I created a custom Drum Map, for all the note mapping data for the Cutya Kit, from SSD5-5. Along with it, I created a Project and Track Template. The templates have a track folder, an instance of SSD5 with the Cutya drum kit loaded, and that instance of SSD5 has each Mixer kit piece channel routed to use a separate audio output channel. Additionally, in the template track folder (both project and track templates), there are 2 midi tracks (one main midi track, and a 2nd for click track midi data, if desired). There are also audio tracks for every audio output channel coming from the SSD5 synth rack instance, and a number of buses (Drums Master, Parallel Compression, Kick, Snare, Hi-Hat, Toms, Ride, Cymbals, Percussion, OH, and Room), and I set up gain staging for all kit piece audio tracks, and the buses, to be set to approximately -18 dBFS. The buses for Kick, Snare, Toms, and Percussion have sends that go to the Parallel Compression bus, which has some parallel compression dialed up - which can be seasoned to taste, or removed, as desired. I did assign track icons, and track colors, which will persist if you open a new project, using the project temlate. For some reason, bus colors do not persist when inserting the track template into a project. I did choose a different color for the 2 midi tracks, to make it easier to see them in the track folder, because of all the audio tracks. In the Project Template, I also have the Master bus set to a different color than the other buses, for the same reason - to make it stand out better as the Master bus. I hope folks with SSD5 find the components I created useful. Even if you don't like the other choices I made in what I set up, at least the drum map will have saved you a bunch of typing. In the Dropbox folder I uploaded (link will be below), I also put a 2 text files. One contains the mapped drum note numbers and names, which you might find easier to read than if you tried to read them in either the Drum Map Manager, or if you open Step Sequencer and you see the note names there. (the text boxes containing the note names are pretty narrow, and cannot, to the best of my awareness, by widened, so if you open that text file, you will see them all listed vertically, at full width. The 2nd text file, contains the list of components in the folder, and instructions for where to place each of the components (templates, and drum map). I also included a shortcut that uses a standard variable that will automatically resolve to your user's AppData\Roaming\Cakewalk\Cakewalk Core\Drum Maps\ folder, which is the location Cakewalk stores Drum Maps in. Just double-click on the shortcut in the Dropbox folder, after first copying the drum map file, and then you can simply paste it into the Drum Maps folder the shortcut takes you to. I did not create shortcuts for the templates, as lots of folks these days, move those to different hard drives than C:. but the instructions in the text file tell you where to place each of the 2 templates. One last note about the gain staging. Some of the mapped kit piece note numbers, are different variations of 'hits' for a given kit piece, such as Tambourine Tip, Tembourine Up, and Tambourine Down, or Ride Bell Tip, Ride Bow Tip, and Ride Bow Shank, etc. For at least those kit pieces, those variations can vary by as much as 8-10 dB, so addressing that with gain staging alone, is not possible. For such variations in volume, you wil have to control it with either velocity editing, and/or by volume automation. Just be aware of that. I tried to strike a reasonable balance with what I set up. HOPEFULLY, the above will be similar, for other kits to be mapped, so I hope I can save folks some typing, and some time. I think that should cover it, except the link: Drobox folder with custom components I created for SSD5 Cutya Kit with split audio output channels Bob Bone