Lord Tim

Do a null test with straight audio, and the pan laws set the same. If it sounds different, then one of the DAWs is broken. Algorithmic or evolving effects won't cancel entirely, but it'll be close enough to tell it's nulling out.

I've had good luck with an old laptop that doesn't have HDMI out that I wanted to run into a 3840x1080 monitor by using a USB to HDMI Displaylink adaptor, similar to the ones on here: https://www.displaylink.com/products/usb-adapters Not ideal but if you have the spare USB3 port, this could be the workaround that gets the job done.

Yeah, this is an odd one for sure. I'd probably be shooting Support a message in which case. It's hard to say if this is an interface thing, a Windows environment thing or something in Cakewalk that's gotten borked along the line. As a final thing to try before you do that, though, make sure Cakewalk is closed then open up File Explorer and navigate to %appdata%\Cakewalk\Cakewalk Core Look for AUD.INI and rename it AUD.OLD The next time you restart Cakewalk it'll rebuild your configuration file. That will at least rule out some weird-a$s setting or corruption there. But if that doesn't help matters, shoot Support a line I'd say. Good luck!

Just for troubleshooting, what happens if you change the driver mode to WASAPI Exclusive in Audio > Playback and Recording? Usually you're always better off with manufacturer supplied ASIO drivers but there's been a lot of work done using Win10's native WASAPI modes over the last couple of years. On my interface, I'm finding around the same latency as my ASIO drivers. I'd be curious to see if you get the same ~10ms offset.

Aha, OK! Ignore what I said then In which case, in Cakewalk open up Preferences > Audio > Sync and Caching (it may be hidden if you haven't got the Advanced view checked down the bottom of the window) Look for Record Latency Adjustment and make sure you have the right device selected and Use ASIO Reported Latency is ticked. If that's all correct, you might be able to put in a manual offset and fix the issue that way.

Your best bet is to remove ASIO4ALL and use the proper Avid driver which will report the latency correctly: Grab the proper Windows driver from here: https://avid.secure.force.com/pkb/articles/download/fast-track-solo-drivers Unzip it to a handy location (eg: Desktop) Go into your Control Panel Settings > Add / Remove software and uninstall ASIO4ALL Make sure your Fast Track Solo is unplugged, and install the correct Avid Drivers Plug it in, let it detect. Open Cakewalk and go into Preferences > Audio > Driver Settings and choose the Avid driver. This *should* fix the problem.

I definitely can agree it's regular Windows behaviour, but it still seems really touchy in this context for some reason (not saying this is any different to how Windows does it in any way, but how I tend to click on things in the browser "feels" different, for want of a better explanation). If there was some way to lock the filenames globally, that would be fantastic and save me a lot of _.wav files.

+1 on this, I've done this far too many times myself.

It's got to be something that's tricky to fix. There was a lot of work done on zooming a year or so back which improved things a lot, especially with folders, but this just seems to be the last hold out. That said, for me it's more of an irritation than a show stopper and I'm glad Articulation maps and Arranger tracks and that kind of thing got the attention lately - that's making a BIG difference to my workflow. Hopefully the lanes zoom will get a look in soon.

Throwing in my usual +1 to this.

Using workspaces is an excellent suggestion. It's a lot more powerful than even experienced users give it credit for in some ways.

I'd agree with that, and I'd also add that it would be cool to use icons as well as, or instead of text. You could do it similar to the Small / Medium / Large / Auto size modules for everything else, and have small be just icons, medium be text, and large be both perhaps. Fitting 12 icons in a module would be super easy and great to save space.

Yeah, I can say I've had this happen a couple of times randomly over the last couple of years too. @scook is on the money - if it's failing for you for whatever reason, just use a hosting service like Imgur.

I'll, uh, refrain from any gags about plugins I guess... ? (Can you tell I've been editing all day? Sigh. Sorry, guys!)

Wow, that's a good point! Lucky I got that CbB tattoo on my butt, hey? ? (You'll all have to subscribe to my OnlyFans to see that, naturally ?)

If you want to convert the MIDI tracks to audio, freeze the tracks first, or bounce them down to new tracks inside the project and archive the MIDI/Synths. If you're just doing a Save As and saving the project in the same location, it won't actually copy anything anywhere - you'll need to choose a new folder to copy everything over. For example, you might have your original project like this: C:\Cakewalk Projects\Project Name\MyProject.cwp and the audio would be in C:\Cakewalk Projects\Project Name\Audio If you just did a Save As in this same directory, you wouldn't really be copying anything, you'd just be making a different project referencing the same audio. What you'd want to do is make a new folder somewhere, eg: C:\Cakewalk Projects\NEW PROJECT\ And then you'd do Save As / Copy all audio with project and navigate to the NEW PROJECT folder. That'll save the MyProject.cwp file in that folder, and copy over all of the active audio files into an Audio sub folder. The NEW PROJECT folder and everything in it is what you'd copy to your backup media or a new computer. If you open the MyProject.cwp file in this NEW PROJECT folder, it'll reference the WAV files in the Audio subdirectory in that folder, rather than the previous location. In other words, everything in the NEW PROJECT folder is its own self-contained thing now. (Obviously these are just example names, call this stuff whatever you like ) But as I said and you discovered, this is basically replicating your existing project, so if you do try to open this on a machine without your current synths or effects on it, it won't play properly, so freezing or bouncing down the synths to a new track is a good idea regardless I think.

1. Yes 2. Don't worry about it 3. One file per clip means that if you've, say, copied in a hand clap sample 40 times into a project, rather than referencing that one WAV, it'll save an individual copy of each. In some ways that can be handy, but usually it's just a big waste of disk space. After you save the project to its new location, you should see the audio files being copied over. I'd double check that everything is there by closing Cakewalk down, reopening it, and then opening up the new version that you saved, just to ensure everything copied over OK. I've never had this go wrong on me, so I personally don't bother any more, but it's good for your own peace of mind when you try this out the first time.

Your best bet is to do Save As, and save the project to a new location, ensuring Copy all audio with project is checked in the Save dialog. That way, you'll get only the active audio you've got in the project and the CWP file saved to that new location and none of the other unused takes. You should be fairly safe to delete the original project folder after that.

Fantastic!

No, that's actually wrong. 1. Find an audio clip. (Not a MIDI track or clip) 2. See if you can find a pitch envelope anywhere, either on the track or clip level. 3. Tell @Josh Wolfer he's actually correct. I agree with the OP, this would be a pretty great feature to have.

Your best bet, if you haven't done so already, is to use the supplied ASIO drivers for your 18i20 - they're always going to give you the lowest latency out of everything. Make sure there's no other ASIO drivers on your system because you'll find things like ASIO4ALL or the Generic Low Latency Steinberg driver can cause you issues too, even if you're not actually using them. HP can be fairly problematic on some models, and might need the inbuilt audio driver disabled, and the power settings checked too. But definitely start with choosing the ASIO driver first. I'd recommend unplugging the 18i20 first and then going to the SUPPORT page and downloading the latest drivers, installing them and rebooting, then reconnecting the 18i20. Then start Cakewalk up again and choose ASIO as the driver. This should at least give you a baseline to work with, if it doesn't solve the problem completely.

I've been surprised with some gear though. Long and boring story how I got to this point but I found that all of my DI options weren't working out for the purpose that I needed them for in a particular instance and the only 2 devices I had laying around was some cheap $50 job, which was utterly terrible - noisy and destroyed the guitar impedance - and an old ART Studio V3 that I had sitting in the live room collecting dust. I wasn't expecting much from that but wow, it ended up being surprisingly good, especially on bass. I wouldn't call it transparent but I really kind of dig what it does change and that's what I'm using for my main DI for guitars now. It's always worth giving something a try if you have it on hand!

Ah, interesting! Good knowledge, thanks @DeeringAmps - I was considering a Radial for a DI in down the track but I reckon you've just sold me on the Redeye.

Can vouch for the Radial stuff, I use the X-Amp for sending recorded DI signal back out to an amp for re-amping. The Little Labs Redeye does look pretty great though - putting that on the to-investigate list.

Yeah, so you'd get a DI box (preferably a good one that's specifically for re-amping guitar) and it'll have 2 outputs: the DI out and a Thru out. Run the DI out into one channel of your interface and it'll record basically the dry sound of your guitar, and then you'd send the Thru out to your pedal, amp, mic, etc and then run that into another channel of your interface. That way you have your clean guitar as well as the sound of the pedal/amp as a backup to re-amp later, or use plugins, or have it there as a good visual guide for editing or quantizing. (Seriously, if you've slammed your guitar through a cranked fuzz pedal into a blasting loud amp, good luck seeing any transients in the solid brick waveform you'll get ? ) It's a great method. I can't begin to tell you how many old recordings I've revisited and gone "man, if only I'd used a different mic or could change the amount of gain on the amp - it'd mix down so much better now." DI means no regrets (other than going back in time and telling yourself to practice more so that fast part isn't so sloppy ?)