sjoens

I just got notice in Windows Update that "This PC doesn't currently meet all the system requirements for Windows 11." So I researched the requirements and turns out I have everything they say I should except the initial Intel Gen8 processor req, which isn't, or is no longer, on the list. So why it says I'm not compatible ¯\_(ツ)_/¯? Do I need v21H1 1st?

Thanks. Looks like a new driver came out this month. Installing now. Unfortunately the micro lite is only bus powered - no power jack, so we'll see how the new driver works.

I found one reason CbB hangs in memory - causing it to not reopen. Safely removing & unplugging my MOTU micro lite quite often releases it. Problem is, doing so sometimes causes Windows to blue screen. This shouldn't be happening! On another note, CbB sometimes does not see the MOTU when it's connected. It's connected directly into the computer. Any ideas why? I've tried other USB ports.

Fixed a very small GUI error.

Just found another chameleon affected by the same routine above: Loop Construction - Threshold Slider & Value text. When Loop view is disabled or 1st opened: Track View | Disabled Control Text When Loop view is active (click LOOP button): Track View | Unfocused Track Text

Ok, thanks. I found them "hidden" in the C:\Users\"me"\AppData\Roaming\Cakewalk\Cakewalk Core\Lenses\User folder. Interesting they're not listed in the Preferences Folder Locations. BTW, it was a custom theme layout that raised the question. Apparently Screensets are embedded in the project (no separate file) but can be imported from another open project.

Is there a way to export or share Workspaces?

.

I learned this the hard way. I never use the Arp controls but today I moved the Chorus & Reverb levels up & down while working on a new theme, then returned them to -0-. Now each time I play the song that was loaded, the VST piano's reverb turns off . CbB's Chorus & Reverb levels are normally at -0- even when a VST's levels are adjusted. However, once you move CbB's levels, the VST's levels will also move. If you reset them in the VST, CbB will override them when hitting PLAY. ? The Arp has an ON/OFF switch. It would be nice to have one for the Chorus/Reverb also.

Possibly that assigned Track Background colors in Theme Editor are retained even after bouncing, This method is theme specific, tho. There is no universal/global approach to change background defaults for all themes, which is what some of us want. A workaround for Mercury & Tungsten is to open them in T.E., set your colors and save as a new theme.

@giovannibuchelli the Track View Clips are not graphics, so the Theme Editor won't make them transparent.

Sometimes. Theming can be quite involved. If you want to learn all about it you might take a look at this first.

Only inspector & Theme Editor can do this. They removed the backgrounds from Preferences with Sonar X1. There is this post.

Just right-click on each page & select Print... > Save as PDF, then merge the pages together using a PDF program. Downside is no links will work.

Two things I noticed about adjusting the Console View audio faders . 1. The graphical scale marks are not accurate. -audio numerical marks are either above or below fader positions. -MIDI 127 is dead center while all the rest are 1 pixel below fader positions. 2. The 2 ways to reach audio +6 & -0- have different results: -double clicking fader puts it dead center -0-. -manual value entry puts -0- 1 graphical pixel below dead center - you can see it move. -fader cannot "visually" reach +6 with value entry or dragging. Since most values must be manually entered I'd like to believe it's more accurate but is it? BTW - the scales can be "calibrated" (repainted) to be more accurate once we know which method to use!

YES! Transparent Clip Backgrounds. (Theme Editor already has transparency for colors built in but few colors can actually use it.) EDIT: Default track background colors can be set and maintained after bouncing in Theme Editor for each theme. But a more global approach might be to return Track Backgrounds to the Preferences Color menu where they can also be saved in a Color Set.clr file and used by all themes.

Is there a way to avoid this?: In PRV, copy 4 notes from track "A" and paste them in track "B". The 4 notes create a new clip in Track View that is as long as the original clip. I have to select the new clip and bounce it to get rid of the empty space.

I'm unable to duplicate this issue using "Duplicate Track". Check your hardware outputs if they are different. Also try drag-copying (Ctrl+drag) the clip to a new track.

When lock centering or justifying the Control Bar, the Custom Module Medium Background is used to fill in the Control Bar's empty spaces. This can have some "mixed" results when repainting the background to accommodate some themes: - YLIP pg 120 I would like to request using the Background Fill graphic (currently unused?) to fill in the Control Bar's empty spaces instead.

... where it would be less forgotten.

Drivers w/instructions are the only thing available ATM.

"Make sure you have "Zero controllers when play stops " selected. EDIT > PREFERENCES> PROJECT> MIDI ." Thanks RBH! That's what I was looking for. Normally these are checked for this reason but this project had them unchecked.

To me the whole idea of "freezing" is to hold the track "as-is" so "nothing " will change it and to free up resources. The online documentation is helpful, but to understand... freezing a track is the same as bouncing a clip but affects the entire track, not just a clip in the track???

Yeah, one more for posterity... Take Lane Description Background is un-theme-able so having black text show up there is another surprise. Don't use it so don't care.

Oversight? Undersight? Intended behavior? Another caveat of Skylight not designed to be themed. Mercury doesn't expose these anomalies because it uses the same colors for both instances. The Folder BG issue existed from the beginning with X1.