Lord Tim

2 ways that I could think of: 1. Freezing the clip, then slicing it and putting the delay on there as a clip FX. I don't recommend this though because A: you lose the flexibility of having the MIDI playing the synth back directly, and B: if you ever un-freeze the track, you'll lose the delay FX and have to go through the process again. 2. Adding it as a send to a Bus or Aux track. So either insert a new Bus or Aux track, put the delay on there and set the wet/dry to 100% wet. Then on your synth track, add a send to that Aux or Bus with the delay on it. Then you'd add automation to turn up the send level only for that part that you want to hear the effect on. Option 2 is great because not only will it do what you want, but you can adjust the curve to smoothly add in delay where you want it, and you can use this same delay for multiple tracks if you like - just make a send to it on each of the tracks, so it's going to be better for your CPU usage overall.

Hey forum people, can I pick your brains for a bit? So I grabbed a couple of sets of Neewer 660 RGB LED lights - great value for what you get and will come in handy for my "other" day job as a videographer. Cheap 'n' cheerful, but also comes with a handy app control too, but sadly (and not unexpectedly considering the price) no DMX or anything like that. But that got me thinking, if there's app control using Bluetooth, couldn't there also be some kind of app or script that you could run from a PC that would control it? Apparently I'm not the only person who thought along these lines and I came across this Python script. OK, cool. So my next bit of thinking was, how do I get a DAW to send MIDI commands to this script (eg: CC messages to control brightness or hue, note on/off to control lights on/off, etc)? Apparently this script can also run a local web daemon that exposes a web page to control the lights too, and that made me think of Web MIDI. Does anyone have any thoughts about how to expose a MIDI input inside Cakewalk, that could either send data to the web daemon, or directly to the Python script? Perhaps something like LoopBe to create the MIDI I/O and then something to intercept the messages from that? I mean, ideally this would all be in a VSTi I could drop into CbB onto a track and control it directly, but for the moment I'm just kicking some tyres to see if anyone has any good suggestions (I mean besides going out and buying some proper lights with DMX ?)

Yep. agree. I think I'm pretty knowledgeable when it comes to Cakewalk, but there's still parts that I don't use much (or at all) that I'd still fumble around with, and even the stuff that I'm very familiar with, it's amazing how many times someone on here has come along with a new way to use it, or some feature of it that I didn't know about and taken me to school - and I'm always grateful for that! It's a big app, but if you start at the basics, you can learn as you go.

Additionally (and definitely DO start a new thread), the Bandlab Assistant is not required now that the Cakewalk Installer is available for the initial install, and then after that all of the updates are handled in-app. But @Base 57 is right - there's something very wrong here, none of those things are anywhere near that big.

Bam!

No, this sounds familiar to me too. Likely in an EA thread, actually. To capture it, try something like LiceCap. But let me go for a search now, you've dragged me down the rabbit hole now too, dammit! HAHA!

You shouldn't need to do any of those things you mentioned to "make it go" but remember, this is a complete recording studio you have here. You need to learn where everything is before you jump in and get frustrated. Start here: https://discuss.cakewalk.com/index.php?/forum/35-tutorials/ There's some great tips to get you started, and this thread in particular has links to some excellent YouTube channels that take you from complete beginner to pro level:

Yep, anyone who chases an artist tone is asking for wailing and gnashing of teeth. Even if the gear is exactly the same between each album, move a mic a centimetre away from the cone and the tone is DRAMATICALLY different. I'm kind of in the same boat where I was chasing that George Lynch singing lead tone for years and you only need to listen to the difference between Tooth and Nail, Under Lock and Key or even between each Lynch Mob album how different the tone was every time, even though at the core of it he was using the same old Plexi (the secret, besides his nutty angular playing and vibrato, turned out to be a pre-EQ and greenbacks), but the spirit of that sound was there at the core of each thing, and it was built upon differently each time.

The acoustic guitar was actually pretty easy to achieve - it was a cheap Cort guitar (believe it or not!) with a small diaphragm condenser pointed at around 12th fret, about a hand's length away from the guitar. No EQ or anything on the way in, but it was a fairly dead acoustically treated room. Once in, I rolled a lot of low off, compressed it fairly hard using the CA-2A compressor, and then added a little bit of reverb, and chorus'd slapback. And that's it In the mix, we did double it up for a lot of the song, and for the bigger parts (choruses, middle-8, etc.) we mirrored the acoustic with a strat in the middle+neck position, and that was running through a Fender Blackface ampsim with a fair wad of chorus on it. Fairly simple stuff, but it had to be to keep the integrity of the "this is an acoustic duo" vibe there, even with all of the stuff I snuck onto it later... HAHA!

I can see what you're getting at re: vertical space, but I think the benefits outweigh the drawbacks here. Having a visual correspondence between the tempo changes in the Tempo Track and the actual track view itself is super useful, and you can hide it immediately with a ALT+T, and obviously you can show or hide the Tempo Inspector by pressing I. So you really don't need to see either of these things if you don't want, but they're just there the moment you want them. But of course, each to their own! We all have our preferences

Yeah, the Tempo View was originally down in the Multidock but I always found that kind of clunky. They've moved that view over to a tab in the Inspector, and introduced a Tempo Track, which is MUCH better for visualising where the changes are: Plus new curve types between tempos as well. This is a fairly simple song as an example, but I've done some pretty nutty prog songs with a lot of tempo and meter changes and this has been a huge workflow improvement for me. If we can get the Meter view shifted over to the Inspector and a Meter Track similar to the Tempo Track brought in, I would be a happy man.

Like actual hardware, you mean? Might be worth grabbing an IR of this stuff, and doing a neural model of the distortion too, using something like ToneX. That way you can just dump it into any project later without the messing around (and I'm sure others would appreciate the model too)

^^ That tangled Aux thing I *have* seen, and it's a tricky one to get a definitive repro on to get over to the devs. I haven't seen a crash from it, but it's certainly annoying trying to work out why your bass sounds underwater and finding out later its output is set to your Reverb bus. I know for sure if someone could get a repeatable "before and after" project over to the Bakers, they'd appreciate it!

I think a bigger box is a good idea in general though. Doing huge orchestral scores, it's certainly not out of the question to have more than a hundred tracks.

Yep, confirmed here too. I wonder if this is just a field length UI thing rather than the number being misreported? Either way, I'll throw in a bug report for it

Heh. Looks like Waves has just passed the "Find Out" part of the "F#ck About and Find Out" cycle.

Yeah, this is a great feature - I wrote most of our upcoming release this way. I marked out each part with their own Arranger section, then dragged down the sections into different orders until I liked what I heard. You can also have many different Arrangements too, so no need to decide right away to lock it in. When you're ready and you like the way it sounds, hit Commit and you're set.

IRs are both kind of EQ snapshots (thus the cab emulation thing), and time based snapshots (eg: reverb, echoes, etc.), and can be both things at the same time. I usually use reverb IRs to simulate rooms or even vintage reverb units, and I'm always using them on my guitar sims - that's the absolute key for getting a great tone; the better your speaker sound (real mic, or IR) the better your guitar tone will be. If you're purely talking about EQ style IRs, check out NadIR, which is free. Libra is also on there, and is nuts, but it's a paid VST. You'd typically run these on the track itself with the wet/dry set to 100% wet. There was a great chat about reverb based IRs in THIS THREAD. This sounds more like what you're after, and you'd use them like any other reverb, eg: as a send, or adjusting the wet/dry blend if you're dropping it into a track. It's really going to come down to how you plan to use these things as to what's going to work best, I think. You might find layering them is a good thing - so you'd find a short slapback IR with a particular EQ curve might be good to insert onto your track itself to shape the sound and put it in a basic space, and then running another IR as a send to get the full room sound to blend in. Can't hurt to experiment!

We need to know a bit more about your settings and hardware first. What audio interface are you using? Does it have proper ASIO drivers that are correctly installed, and you've chosen ASIO as the driver model? Are you using (or even have on your system) anything like ASIO4ALL? Any one of those things can influence a problem like this.

Please don't take this as me being combative or antagonistic (text can give the wrong impression!) but there's not a real lot that can be done unless you go through methodical steps, so this is going to be something that will keep happening unless there's definitive steps to try and lock the cause down and fix it. I'm sure you understand that I definitely get the amount of work involved in breaking it all down, though, and I sympathise. It's a no-win situation at this point. One thing that did cross my mind, and it did when Lynn posted a similar thread to this and now in here, I wonder if this is related to track indexing once sub folders were brought in? I'm not seeing this issue at all, personally, but if a project was built prior to or around the time sub folders were brought it, I know quite a lot of changes had to be made under the hood to accommodate it. Could it be possible this is what got these projects into the bad state in the first place, perhaps? @msmcleod - any thoughts? Are you guys using a lot of sub folders? And about when did you first start working on these projects? I might be just shooting into the breeze here, mind you, but it's something worth clarifying!

Yeah, Juz and Aggii's voices really do complement each other, I agree. It's a funny thing, Juz was always a great songwriter, both when he was in my band in the 90s and his glam/punk band just prior to this, but since he put My Whisper together, his songwriting has just lifted to somewhere else entirely! It sounds like I'm taking a lot of credit for stuff in the OP for what I did with the song, but the reality is that I really just did embellishment of an already great song - strip that back to just the 2 of them as an acoustic duo and it's already excellent. Did I mention I'm fan? HAHA!

See my post earlier. Come at this with a plan rather than just guessing, that way we can zoom in on the problem and save you a lot of time and possibly an even more broken project. What I suggested won't fix stuff right away, but it's not meant to. We need to work out the HOW before we work out the WHY.

I think it's more so the really loose VST3 spec that's catching everyone out, rather than the language. Steinberg really dropped the ball on this one, IMO.

Yeah, I'm with Erik here - this doesn't sound like a Cakewalk problem as such, so reinstalling anything won't help things. That's not to say there's not a problem inside Cakewalk that's allowing these problems to happen if you use a specific plugin, or do a specific chain of events, however! But if the program had these core issues, it would be something many more people would be seeing, and definitely not project-specific like this seems to be. Let's be methodical about this and rule out the things that it's NOT. First, are you able to get one of these corrupted projects to someone (or yourself) with a different computer to see if the project still displays the problems? The idea of this is to rule out if this is something that's only happening on your machine with this project, or the project itself is damaged. Secondly, I'm going to echo what Erik suggested. I'm not sure of how you have these projects set up, but there's obviously a lot of tracks and routing, etc. going on, so they sound fairly complex. Can you save the broken project as a MIDI file for a start, so you have your tempo and markers saved, then open that .MID as a new project, save it as as Cakewalk CWP and then copy and paste in the audio tracks from your broken project? This obviously will lose you a lot of work, but that's not the point of this part yet - what I want to establish is that if you have this huge number of tracks dropped into a brand new project, rather than a 2 year old one that's getting more and more broken over time, does this new project show any of those weird issues? I'd like to narrow this down to it being a project specific thing, so we're not chasing our tails. If it does work out to be a project specific thing and new ones don't exhibit the problem, then you might have a path forward to make something which might be a pain to rebuild in the short term, but will be something which won't lose you everything once you keep working on it. If the new projects DO start showing these problems, we should look at any effects you've dropped into them for a start, or of there's anything funky going on with the WAV files themselves. That would seem unlikely but stranger things have happened! If it turns out there's a plugin that's misbehaving and causing Cakewalk to write bad data to bad places, then it's worth investigating to see where the problem is, either on the vendor's side, or if it's something that's exposing a shortcoming with how Cakewalk is protected against this stuff. I'm sure I speak for all of the devs when they say they don't want anyone to have this kind of crappy experience, and if they can prevent it from happening, they'll make it a priority. But we need to know where to look first to pass on the right info to them.

Milson's Point is a beautiful area I was signed as a writer to BMG which was a few blocks up the road from there, and it was always really nice passing through on the way to meetings with the boss!