John Vere

Good move! I have a few VST drums and Addictive drums for me works the best. The mixer allows me to only need the stereo outputs instead of multi channel to process the audio. I find everything I need is built in. It’s not perfect but I have managed to squeeze pretty close to what I like with just the built in effects. The Overhead and room mikes makes a huge difference to even the snare, just like a real mikes up kit would be. My only complaint is that they never have super sales so I could grab more kits and pieces. Now you really gave me GAS for the Roland kits.

Deleted , OP not engaged in topic.

3 videos that cover audio set up in Cakewalk link is in my signature.

As I said my DTX kit is very basic compared to yours so it probably wasn’t as much involved in linking the hi hat pedal to the VST. Before all I got was the GM open and closed which as you know is a mile away from how a hi hat is actually played. Now I get acceptable variety of opening sounds which I have no clue how that works but it definitely made a difference. I guess my pedal sends a continuous controller event and Addictive drums has multiple samples to match that. I need to learn what articulation is all about. I’ve never looked into it and I have a feeling it’s important to create more realistic midi instruments.

Actually when you render a Melodyne edited clip the original clip is permanently changed this is what we call destructive editing, A wave editor is also a destructive. Melodyne is just a wave editor with a different user interface. Plus the pitch editing is more intuitive. Using Volume envelopes, the clip gain or split, slip editing, fade tool etc. methods are non destructive editing. The original audio is still in the folder unscathed. Before you perform any destructive editing it is recommended you have a safe back up of the original.

As I said, I found that was probably the lowest quality wave editor I had ever used. It's the only one I didn't keep on my system. Wave Lab had paid for it self over and over. I'm way behind on updates and only using Version 5. It's now version 11. As Cakewalks features have improved along with my skills of using it, I find Wave lab is not used as much anymore. I still use it for mastering the final exports. It also has the proper tools for CD tagging and sequencing. Another lost art. The below are links to the ones I use and all of them are free to try. I actually don't ever use Audacity but it's a powerful little audio app for absolutely free. I mostly use Wave Lab as like Cakewalk I've used it since 2004 so it's familiar. https://www.steinberg.net/wavelab/ https://www.magix.com/ca/music-editing/free-download/sound-forge-pro/ http://www.goldwave.ca/ https://www.audacityteam.org/

When I use Wave lab as the tool copy it opens , I edit the file and close it and it asks you to save changes, I save and the file closes leaving wave lab open and empty. When I return focus to Cakewalk it will tell me the audio file has changed and do I wish to update, yes. If I open a second tool copy it will return me to wave lab which is of course still running

Did you not read the answers? It costs money. Cakewalk is free so cannot include components that are licensed by any 3rd party. This is why we no longer have a lot of the 3rd party plug ins included like we had when Sonar was $500. At best you could include a demo version like Melodyne is.

I have a few wave editors and that Acoustica was my least favourite. In order of favourites Wave Lab Elements $100 on sale Sound Forge Free ? It came with Movie maker and a Sony USB Turntable Gold Wave unrestricted demo and only $60 to purchase. Does batch conversion of all audio files. Audacity free. But Melodyne has really become the tool for me now. You can not only fix pitch but timing, glitches and even levels are easy to fix. They thought of everything. And the comment about having to go to the menu. Custom keyboard shortcuts are your friends. Example Gain = G. Open Melodyne as regional effect = Z. Render Regional Effect = X.

Yes screensets are saved with projects. Workspaces are global. The last workspace you used opens next time. Workspaces do not save things like which browser tab you last used. It just saves the layout of what views are open in the browser. like the synth rack and where it was and how big. Sceensets still allude me as they don’t work like the workspaces in that when you like a set up you save it. Someday I’ll read the manual ? But that’s an interesting question as I’ve never really paid attention to what tab is open by default. I does seem to be the effects.

Clip mute as mentioned above. Not track mute. Had this happen. I think there’s a keyboard shortcut that you accidentally can toggle it with. Open clip properties in the track inspector and look for the mute

We were all lucky as Addictive drums came free with old Sonar versions. I think I got some kit pieces for free via Focusrite deal. I can't remember but I have a couple of full kits and some extra snares and percussion. But you can install the demo version for free to try it out. It is only one kit and no toms so it's almost less than SI drums. But then you will be all set up with an account and have the XLN installer. There's also a very good demo for their piano. Steven Slate also has a lot in their demo kit, much more than SI for sure .In the Maps is one Roland kit but my guess is someone has a map for yours out there. It also involves a log in to an installer but it's defiantly worth trying the demos for both of these.

You just click on the Control bar and choose which modules are shown. It's not technically part of workspaces but some workspaces hide extra features so choose advanced to see all features, The default Basic SUCKS! .

Make note that I just tested this and now that I have activated the DTX drum map into Addictive drums bingo, now the hi hat works exactly like the one in the brain. I just discovered the map while making a tutorial and I haven't had my drums out of the closet for about 4 years ( we moved) so I'm just like you in a way. Also take note that my DTX 500 kit is very crude compared to yours. The pads are only 1 zone etc. I dream of someday having the cash for the top of the line Roland kit. I've played one in a Music store and there's a HUGE difference. Mine is only a toy and limited in use for recording. I'm planning to integrate a real snare, hi hat and a few cymbal's into the kit and mike those up. So mostly the Kick and toms will be used. The extra pads will be assigned to cowbells. I bought the kit hoping it would add realism to my drum tracks, but it was a bit disappointing and all it added was better snare and tom fills. The hi hat is probably the biggest disapointment as I'm probably the only sound engineer I know of who always puts a mike on the hi hat and cranks it up. It is often overlooked as being important. And Midi hi hat is boring no matter what I do with it. But that changes with your kits I do believe.

My computers are way older than 5 years. My main DAW is 13 now. It does need replacing as I really don't get good performance for video editing. But my Cakewalk project are no problem at all possibly because I work no different than I did 20 years ago. 8 to 12 tracks and no more than maybe 20 effects. As far as swapping C drives I'm a huge fan of a fresh start. Cloning a drive is OK if you've do this often but I would not want to clone a system drive that was 5 years old. All the junk it has collected and stashed away is ported over so there's little change other than drive speed or capacity. I just bought a new Evo SSD drive and was all set to swap out my 4 year old Evo SSD C drive but Samsung has an app you can run that tested all my drives and it found everything other than my 1TB spinning drive working 100%. I still might do it just to have that fresh start performance boost. Sure it's a pain to re authorize all your VST's but last time I did this a year ago it only took me about 6 hours from ground zero with W10 download and install. You computer might run W11. The other thing about a fresh start is then I only install VST's and other software as need arises. They are all stored in the computers Data drive so not a problem. This spreads the re install chore out over time as well. The trick is to have good back ups of everything you need on your other drives or an external. Here's the Samsung App, It gives you full reports on all Samsung SSD drives but it will do a basic speed test of other older drives. https://semiconductor.samsung.com/consumer-storage/magician/

It’s like this. MIDI 1.0 has been with us since the 80’s. It is not multiplex so each data package has to wait it’s turn. Think of 20 people waiting to go through a door. Each midi event can take about 1 ms to travel its route to the next midi port. Short cables might improve this by a .01 ms. So when you play a 4 note chord on a keyboard the whole chord will theoretically take 4 ms. But then there’s also system latency and I actually measured this and tested all my midi devices. My Roland A49 and Yamaha drum kit were around 5 ms for a single note. My 1987 Roland controller was 11ms. I can test my A49 with both 5 pin and USB. They were very close to the same. I also tested a daisy chain of the A49 into a Sound Canvas (1987) and the 5 ms jumped to 16ms. So newer midi devices seem faster because of advances in system design but that’s as good as it’s going to be with Midi 1.0. We now will have Midi 2.0 which is multiplex and latency will no longer be an issue. My guess is your kits are only around 6ms each so a note hit on the TD 6 will possibly be 12 ms or a bit more later on the midi grid. That’s easy to fix by simply quantizing the track. You can easily test how much latency you have. Open a basic project which will give you a audio and a midi track. Put a mike within a inch of a drum pad and feed it to the audio track. Set the midi track to record the kit. Optional would be to listen to the metronome in headphones. Set in record and strike it a few times. Set the time ruler to millisecond or samples and zoom in on the transients. The difference between the audio and midi tracks is the midi latency. The difference between the midi track and the grid line is the just showing you how sloppy your timing is ?

I do what Greg shows but only split once. Once you split a clip you can slip edit to remove the silence or cross fade. But I also do as @sjoenssaid and I often export the track as a stem at 48/32 no dithering and delete the messy track and drop the nice tidy one in its place. I used to do this for timing issues but I now use Melodyne for vocals and harmonies. Guitar still gets the zillion clip treatment if needed. Of course there is a back up available if this goes wrong but I’ve done it a hundred times and it never does.

+1 to that. It’s been found to be invasive and interferes with other drivers. It gets installed with their software just like the other pesky Steinberg generic driver. You need to delete them in Reg Edit. Then use WASAPI shared mode if you don’t have a proper interface. But that said I would guess it’s because you didn’t set up the export dialogue properly A screenshot would be useful.

B

Thanks for the reminder, I totally forgot about that trick and that was actually much better than the clip gain. Super fast. But all I will do is split right in the glitch and add a fade out and fade in.

Ya the first time I did it it didn’t stick. The list might not always have the function you want or it might have a completely different name than you thought. But I’ve just figured this all out not that long ago and since I’ve swapped out lots of stuff I never used for stuff I always use. The best one was to open Melodyne and then render all with just 2 keystrokes. Huge time saver for me.

You got to be kidding, not to come across as being a smart azz but did you try the views menu???? I found it is 3 seconds and I never use the notation view. I'm glad you asked though, because I didn't even know it existed! Cool.

No but you can use clip gain to lower the aptitude so it's not heard. I know what you are saying as Cubase does that too. But Cakewalk is not a wave editor.

Don't the drums have USB? Daisy chaining midi with DIN cables will result is a huge increase in latency from the TD 6 as it has to pass through the midi system of the TD 8. So using USB will solve that. Latency is very noticeable on digital drums so I record all my tracks only listening to the Drums brain so there's no latency at all. My kit has an Auxiliary input so I patch my headphones from my Audio interface using a 1/8" TRS cable you can usually get at a dollar store. Then I plug my headphones into the drum brain jack. I guess with 2 modules you would need a small mixer? Or possibly there's a way to daisy chain the headphones and aux inputs. You sort of need a 4x4 interface. SI drums only has 8 kit pieces. It looks like your kit is at least 20 pieces. You will need to use a better VST with more pieces. All the free kits are limited so I won't bother mentioning those. But example a full set of Addictive drums has 18 kit pieces. But that actually doesn't matter as you can deal with that later buy using more than one Drum VST. As far as the recording of the kits this will depend on if you use Midi cable or USB. With the DIN Midi cable you select the Scarlett Midi as the input for the midi or instrument track and set it to OMNI so both channels will be received. I actually don't see a reason to change the TD 6 to channel 11. Unless it's re triggering the TD8. But I would be then inclined to change the note assignments in the TD 6 to sounds not being used in the TD8. Then they can share a channel. If you use USB midi you will install the Roland Midi driver and the kits will be identified in Cakewalks Midi device list and in the track header as an input source. I'm pretty sure they probably share the driver so not sure if they will be listed as TD6 and TD 8 or just Roland TD drums and Roland TD drums2 I would record the midi while monitoring in the drums brain. Once the midi is recorded you can edit it and assign it to any drum kit VST. The Roland has good drum sounds that you could then simply route the midi tracks output back to the kit and then connect the audio output to the Scarlett and record that. I do this with mine for the hi hat because it seems to be in better sync with the pedal. This leads us to also requiring a VST that can have a drum map applied so CC events etc are correct. Lucky for you most good drum VST will already have drum maps for Roland kits. As you see in the screen shot below.