Colin Nicholls

Reminds me of the whole "Folder description background" anomaly. So, yeah, I agree that there are items that take their color from different sources depending on ... something... switching themes mid-session vs loading at start-up, etc. They are probably really low-priority bugs that never reproduce when you want them to. I guess we should document these anomalies as we find them.

I tried to reproduce this and failed. Here's what I see: Track View / Disabled Control Text: Video Thumbnail Track Control Values Track Folder Statistics "0" values (!?!) Track View / Control Text and Values: Track Folder Description Text Track Take Lane Description Text Track View / Clips Pane / Track View Clips Pane Background: Video Thumbnail track background (no video loaded) (Yup, I'll update the YLIP with this, thanks) Track View Clip Pane background (empty space below tracks) So, you're either wrong, or Cakewalk is having fun with us. Could be either.

Please, no. The Blue contrasts very nicely with the Tungsten Dark/Orange, which is as it should be for something you want to highlight visibility of.

"Today I learned..."

@sjoens, are you suggesting the YLIP needs changing? I thought I covered this pretty well. Unless the "Synth Name Bezel (undocked)" is actually visible under some circumstances, are we arguing about whether "invisible in practice" is the same or different than "no longer used" ?

@Billy86, those are denoted "Track Header Icon Thawed" in the Theme Editor. I guess this means they were at one point frozen synth tracks but have been un-frozen. I'll be honest and say that I've never understood exactly when and why these track header icons appear, given that an unthawed track should look just like a pre-frozen track. Certainly when I do a simple test, my frozen tracks have blue header icons, but then when I un-freeze them, they revert to normal white, not the "blue with orange background". "Thawed" doesn't even show up in the reference manual that I can find. Maybe someone else knows the difference.

The one time this happened to me, there was a difference between source clip and destination format. I can't recall if it was bit depth or off-by-one pixel width or something, but it was totally user error. Doesn't preclude there being a real problem in your experience, though.

PDF updated with the latest contributions

Good things take time. And poor @confire might even have a full-time job or something.

Are you sure you're deleting them from the correct directory? Even after a reboot?

Sure is

Sorry you experienced that. It's working for me now. It's possible you tried during a period of site maintenance yesterday. Give it another try, please.

Last time something like this happened, it turned out to be a sticky "M" key

Well, that's a relief. The '99 build puts the FX plug-in flyouts back to "normal", to match the instrument plugin menus. Must have been a bug.

I've double-clicked on a task to load up the settings, and I've noticed that the collapsed "Destination" section summary does not reflect the actual values in the expanded section. In the gif below, compare the collapsed text on the right side with the actual values in the expanded area:

@#$%#$%. Add Track > Instrument is still the correct polarity. Can't they at least check to see if the current theme is based on TUNGSTEN or MERCURY and select menu colors to match?

Well, it's all on BandCamp ?

This suite was inspired by a trip taken to Oregon in 2017 to witness the Solar Eclipse, but expanded with a fictional account from an Indonesian photographer for dramatic and metaphorical effect. This is the first time I've used Cakewalk By Bandlab for every aspect of the production, including Mastering. (-14 LUFS average). BandCamp: The Prodigal Sounds: Annulus Suite Thanks for listening; I hope you enjoy.

To be fair, I've lived in the U.S. now for 22 years but I'm also dyslexic, so I'm basically at the mercy of my spelling checker. "Bloke" works for me, an ex-pat Kiwi.

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.