Colin Nicholls

I'm getting random click/pop artifacts in my WAV audio exported from Cakewalk by Bandlab. It doesn't happen very often that I can tell, but I have some quiet sections where, almost inevitably, I hear a tick or pop in the exported WAV where there is none in the source project. If I re-export, the defect goes away, or appears in a different location. Honestly, I can only detect it if it happens in a quiet region, it might be happening more often. Question: Does Cakewalk use the audio interface to perform audio export? Will changing the ASIO settings affect audio export?

Everything I know about Control Bar backgrounds is written up here. (Firefox understands that link and goes directly to the page. It's pages 118-119.

@scook has leveled up and now all solutions are attributed to him.

I'm getting MiMu Gloves vibes from that controller. Much more expressive than the D-Beam on my Roland keyboard ? EDIT: Surprise surprise. The latest Sound On Sound includes an article about MiMu gloves, and talks about how Leap Motion is using related tech.

1. Yes 2. Unfortunately, not possible. Setting a color for a bus will affect the foreground color only, and the track will also use the bus's foreground color as the waveform.

Imma gonna just paste that into an appendix all of its own, Erik. EDIT: Document has been refreshed at the usual URL

Let's eliminate the (other) obvious things. What does your devices look like under Edit > Preferences > MIDI Devices ? Are the correct ports enabled?

I've never used ACT (that I know of) and therefore I deliberately glossed over (well, ignored) how ACT is handled in the UI. I agree that it could be reviewed and expanded. Or at least, re-factor that section slightly to make it clear that ACT is not being covered.

Wait, what? ...Huh. I have no memory of doing that. I mean, it was some time ago, and my memory isn't what it used to be. I certainly like what the QC flyout looks like. I may have stolen it from someone else's theme, I definitely can't take credit for it in its current form, although I think it is a simple color inversion, and if I were tweaking it I know exactly what I'd do.... *opens Paint.NET*

Zip file now contains a .clr that, hopefully does what @Starship Krupa needs ?

It|Works|Great, @Noel Borthwick

Release 2.10 Minor cosmetic changes to Console view module headings, and Time Ruler background and tick marks, all in the name of improved clarity.

What's the snap resolution? Samples? Try changing it to smart grid, or experiment with changing the resolution.

To be fair, the waveform preview also needs to show clipping using a different color so I'm not sure the outline would be a good thing.

I use the Arrangement Track to add instrumentation notes along the timeline. That might be helpful for you to try that.

I found the problem. It was the Swanky Amp Pro plugin. I will follow up with the developer. Not quite that simple. The same behavior also occurs with Voxengo Boogex. The same behavior occurs when instead of an AuxTrack, I use a stereo bus. If either of these plugins are used directly on the track, I can pan it hard R and the audio stays audible. So, something about using these VSTs in Aux Track or Bus makes them only pass signals on the LEFT channel. I guess they are mono FX ? I can't believe I haven't noticed this behavior before. If I use instead Blue Cat's Free Amp, it works fine, as an Aux Track or Bus FX. I guess that one's stereo-aware. So, I also tried putting all three clips into separate Take Lanes on one track, and using clip automation to pan two of the left and right. Same behavior. Voxengo Boogex and Swanky Amp Pro only "hear" the left channel and emit a mono output. Blue Cat Free Amp treats Left and Right as separate channels. Alright alright. I guess this is just how it works.

Hi. This is driving me crazy. It must be something simple I've done. Any insights welcome. Situation: I had a mono track of guitar. Decided I'd like to split it out into Left, Right, Center, feeding a common Aux track with all the FX. I've done this before. It works. Well... I selected my track, changed its output from the GTR buss to "new aux track", named "ox:JazzGtr". Then I duplicated the track a couple of times, and panned each one L, R, C. Only clips on the L, C tracks are audible. The R track does not play, although I can see the audio meter active during playback. If I pan the R track so that it is anywhere left of hard R, I can hear it fade in as I move the pan position. Picture: As you can see, track 75 is panned hard R, marked with an arrow, and is inaudible (trust me) until I pan it back towards Center. More information: 1. Tracks 73,74,75 each take their input from 1 mono input on my I/O (Left 1|2) 2. I changed the interleave on tracks 73-75 from Mono to Stereo to see if this made a difference. It didn't. 3. Version: 27.04.0.175 (I rolled back to check if this was something new) 4. I checked, and the Input of Aux Track 76 is stereo output of the underlying patch point: 5. I manually added a new audio track (instead of duplicating 73) and assigned its output to the patch point, panned it hard Right, moved the clip into the new track, and playback. No joy - still didn't hear the audio. 6. If I switch the panning, Track 74 hard Right and Track 75 hard Left and now I can't hear track 74, while 75 plays back fine. Help me, forumites! I must be missing something really obvious.... (Followed up below)

Uh, thanks for "solely" ? Well, since you asked, It's all about usability, and preventing boredom. For me, it also needs to dissolve into the background. I don't want to be reminded of what theme I'm using, it needs to be invisible, whilst still providing a comfortable working environment. That means consistency, and for me, the best way to be consistent is to chose some constraints, and get creative within the constraints (works for music creation too). The constraints vary. STEAM PUNK was just me exploring theming for the first time, and deciding half-way along that I needed a goal, and it looked, well, steam-punky. POLAR BLUE 2020 is really SteveC's work, I just gave it a polish for my own entertainment. I learned some stuff. TUNGSTEN SLATE was a second attempt, this time starting from Tungsten but warming it up slightly, giving it a slate-blue flavor. I learned some more stuff. MIL-SPEC ALPHA was an attempt to make a mid-tone flat theme somewhat inspired by Ableton, avoiding "all grey and no play" and ending up in a khaki zone, hence the vibe. For FLAT WHITE it was, "how far can I go in taking MIL-SPEC ALPHA and making a really "light" theme?" For FLIGHT DECK I really wasn't planning on creating another theme. It was seeing a screen shot of an aircraft interior in MS Flight Sim 2020 and thinking, "that looks comfortable, like it would be hard to do the wrong thing". I have no plans for more themes. (I was considering 1960's NASA but it would just end up somewhere near MIL-SPEC ALPHA and FLIGHT DECK so I don't see the point) Honestly, I find myself switching between FLIGHT DECK and MIL-SPEC ALPHA every other week. Or FLAT WHITE (matcha).

What's your windows display resolution? The minimum required is 1280x800.

What type of audio file are you attempting to import? Could the filename extension be mis-asigned? What process are you using to import? Drag-drop from explorer into Track view? Or, select audio track and File > Import > Audio ?

Is this AAS String Studio? VS-2 or VS-3? If you've reinstalled from scratch into a clean machine, you will need to enter a serial number supplied by AAS.

This is definitely an area I prefer Cakewalk to take care of automatically, as opposed to offering up a dialog with a prompt along the lines of "Do you want to delete this object? Hint: Both answers are wrong"

You are correct. If I save the project, then re-open it, the Aux 1 patch point no longer exists as a destination. Okay, well let me update my post above.

Just to be clear, this is easy to duplicate from scratch: Set up: Create a new empty project. Add new Audio Track 1 Set Output of Track 1 to "New Aux Track". (Track 2 "Aux 1" is created) Delete tracks 1 and 2. Add new Audio Track 1 and open the Output selector menu Situation: Aux 1 is an available output destination. A) How to remove Aux 1 from the output destination list, according to @scook: In the new audio track 1, add a send to Aux 1. Drop down the Send destination menu and select "Delete Send" Observe: Aux 1 is no longer an available destination. B) How to remove Aux 1 from output destination list, according to @Lord Tim: Save the project and close it Re-open the project Observe: Aux 1 is no longer an available destination. Thanks, @scook & @Lord Tim, this was driving me crazy. Is it just me or is this counter-intuitive?

I created an aux track and then decided I didn't need it at all. I deleted the tracks, but the associated new Patch Point still shows up in the input/output list. How can I delete it from the project?