Colin Nicholls

PDF updated with the latest contributions

Ha! You would be right about that. Looking good.

It runs. It complains there are no audio devices. But you can open a project and even run an export. It looks like it is working but the exported file will be 4kb and empty. So, you know, I figure exporting DOES use the audio interface and therefore changing it might result in, um, different results.

Not what I meant. I mean, with Cakewalk indicating that there is no audio interface available to it.

Not disagreeing, but have you tried exporting audio without an audio interface? Good idea about the latency and background tasks. Time for an audit.

Listed in my sig. After I disabled the ECHO Layla3G in the Device Manager, I switched on the Focusrite USB and re-tested the export. My first thought was that this solved the issue, but then I noticed a glitch in one of the track exports, right at the end. Background: I have five projects, each being one movement in a suite. I export these to 44.2/24 WAV, and use a sixth project to combine them into a single continuous composition, applying level balancing and a final polish, multiband compression to -14 LUFS. This is exported at 44.2/16. I also export each track separately (with the same processing) to give me 5 additional mastered WAV files for each movement. So, that's 11 export operations. I have listened to the end results several times over checking for glitches, and quite fatigued at this point. However: Having the Focusrite instead of the ECHO did seem to be much less prone to glitching. As I mentioned, I did get one glitch right at the end (so frustrating!) but eventually I managed to get a full set of glitch-free exports, and that will be going up on BandCamp later this week. So, job done. With that project out of the way, I'll be listening more carefully in future projects to see if I can find a pattern.

I bumped it up to 1024 during my most recent test; still detected glitches. Currently I'm testing with a different audio interface to compare.

Thanks, Will. You'd think those types of things would be consistently found in the same location in the exported audio, though, wouldn't you? And I can't hear them when I play the project in Cakewalk. They show up in the export. Yes, headache!

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)