User 905133

I did that in reverse. Once, when I was 31, I thought I was 32. A few days before my birthday someone told me, "No, you're going to be 32, not 33!" So I ended up "losing" a year [level?] in a good way. Every so often, I forget and I do it again--thinking I will be a year older on my up-coming birthday only to learn that I am a year younger than I thought for a number of months. I recommend that rather than the reverse. ? Best wishes for good health.

I come to the world of soft synths from years of using hardware where (for the most part) changed parameters need to be stored (often as "presets" but sometimes under other names). So, I just assume that soft synths (including AIR) work the same way (for the most part); that is to say, in order to recall changes, those changes first need to be stored in order to be recalled. Is it common for soft synths to remember adjustments without them having been saved? I have not systematically explored my soft synths as far as whether or not they retain adjustments on their own, but maybe my experiences with hardware no longer apply with regard to patch tweaks.

On my PC I noticed this, too (yesterday). Plus some of the other updates (for instruments) don't seem to update the version numbers in Cakewalk even after a new VST plug-in scan (including existing plug-ins). Scook's VST Inventory Tool also indicates allegedly new files (ones with 2021 dates in the unzipped files) are not being seen. Please Note: I didn't try a complete plug-in reset yet.

Maybe this will help:

"Interesting" indeed!!! Maybe someone will chime in with an "official" answer. I just noticed it was sequential and moved on to the project at hand--most recently with my oral interview tapes, though I did notice it a while back on my XP PC using SONAR X1 during a project where I was going through a bunch of my improvs with an ear towards editing together sections of different performances.

In my limited experience, every time you import a file (I've seen it with wav files), there's a sequential number in parentheses. Maybe its the same for cda files. EDIT: Since the first one in that images is (4), by any chance did you import 3 other audio files in that session of Cakewalk (or maybe using the same project)? My Example: I have been working on a series of oral history interviews. I started with a previously digitized version of Tape 1 side a and then imported a digitized wav file of Tape 1 side b. After I marked up one tape [using Cakewalk's markers plus comments in Notes] I saved Tape 1, erased the data in the track, and then used the same project for Tape 2 sides a & b. So, Tape 5 side a is the 11th importing of a wav file for that project--even though I saved a project with the contents of one two-sided tape after each mark-up session. Perhaps you have all of the converted files in your Audio folder for that project?

Maybe, but please re-consider that the following had already been posted in August 2020 at the time of the original thread. So, by March 2021 there had been a question, some clarification, some civil discussion, some valid points raised (including the option to use the Mix Module or Ctrl+R), etc. And so the drama continues.

I see a legitimate question asked plus a clarifying exchange. Obviously some people didn't understand that you were looking for a single button that would arm one track and at the same time disarm all other tracks--an "exclusive arm" button as suggested on 8/16/2020. Maybe my reference to a "radio button" confused people? Several months later suggestions were made that (1) you use either the Big red button in the Mix Module on the Control Bar or Ctrl+R (implied: if you weren't already doing that) to disarm all the tracks before (2) arming a new track. Just a hunch, but I suspect the subsequent tone of ridicule by other was abetted by this piece of sarcasm: In case you missed it: Between August 2020 (the time of the original post) and March 2021 (the time of this reply) was almost 7 months.

I have never used a Behringer interface, but I remembered reading a few years ago that they didn't have ASIO drivers. I just Googled "Do Behringer interfaces have ASIO drivers?" and found a source that says "Although most Behringer audio interfaces have their own driver (version 4.38 as of July 2018), some of the smaller interfaces will require the third-party driver, ASIO4All. These interfaces include the UMC22, UM2, UCA222, and UCA202. " I don't know if this has changed, but you might want to check if you haven't done so already.

No, don't do that. It would be mean for sure.

This comment makes perfect sense to me.

(1) TL/DR = too late/didn't read ????? (2) Are you talking about Bandlab (the web app) or going between Bandlab and Cakewalk? I ask because I have been waiting for the new integration features before starting to use Bandlab (other than for some casual tests). Thanks.

I assumed it meant "out of time" [i.e., having some sort of timing issue].

@Ben Staton Any chance you could make the DX, VST2, VST3, 32-bit text designations use theme editor colors as in 2021.04 EA 1?

Sorry for the confusion. Yes, by "Colin's Most Excellent Theming Guide" I am referring to his YLIP to Creating Cakewalk Themes. As for the colors, I finally reconstructed some of my track color tests. Looks like one series of tests started with Boston Flowers: To do this, I tweaked the colors in the Theme Editor under Track View > Clips Pane > Clips. To verify, I did this today: Again, I probably didn't post this method previously because msmcleod's solution using the Inspector seemed much more efficient and quicker to me, but it can be done in the theme editor if you want. I have not systematically given thought to the advantages of the different methods, but surely there must be different benefits to each method (and maybe others?). Hope this helps.

This ^^^^^ .

Would customizing a Workspace help with this? Here are the factory Tempo Workspace and the same Workspace slightly tweaked.

I used Cakewalk's Tap Tempo feature for the first yesterday. I found it to be quite handy. Used to use a hardware button on one of my sound modules, so this is nice to have conveniently located in Cakewalk's new Tempo Track.

You have far more experience WRT customizing keyboard shortcuts, so I defer to you on this. I see what happened with 2021.01 Build 098 on my other Audio PC. For some extremely odd reason I was on the Basic Workspace (which I never use). Thanks for correcting me. From developing personal Workspaces I knew we have the option of saving and restoring custom keyboard shortcuts. Of course I haven't yet transferred them to the Audio PC I have been setting up. In fact, I just installed CbB and only did two tests (so far). Good to know that the default Basic Workspace excludes certain keyboard shortcut categories (as well as the shortcuts themselves) for excluded features.

Recently someone asked about changing colors using the theme editor. Related posts / discussions: here, and here (using the Inspector), and Colin's Most Excellent Guide to Theming (such as the section on Clip Colors) NOTE: In response to a previous post (the first "here" above) someone asked: It looks like I didn't answer that specific question, probably because msmcleod's reply using the Inspector (the second "here") was quicker to do / and seemed to me to be more efficient than the method I used (theme-editor based). However, it can be done with the theme editor--just in case someone wants to do it using the theme editor.

@Herbert Zio Would something like this or this be helpful? PS: This question is not really 2021.04 Feedback. If there is additional discussion, I'd suggest using a different thread maybe under Q & A or the UI Themes Sub Forum? Clarification of my intent: Anything I have to say WRT colorization and the theme editor is not specific to 2021.04; therefore, I do not plan to address the question with additional posts in the current thread. Sorry for the misunderstanding.

Yeah. I saw that. I wrote Oops earlier, but it was too late. Sorry. Update: I don't do much with personalized key bindings,** so to familiarize myself with them, I compared the category [Area] choices in the current build with 2021.01 Build 098. (It was handy because I have it on a second PC I have been setting up.) FWIW, the current 2021.04 adds four categories (Loop Construction View, Surround Panner, Sysx View, and Video View) and loses two categories (Tempo View and Track View). I have no idea if Functions have been added or removed and I am not going to look. Just wondering if they are in a document somewhere (either changes or the Reference Guide). Thanks for mentioning this issue. I have been thinking about customizing shortcuts but its usually a low priority for me, This might change as I now see some Areas and Functions that would save me time if I had custom key bindings. **I usually use Global Bindings. EDIT: Correction done per the following discussion. Thanks @Promidi.

Oops.

I agree in principle--not that it came bundled with SONAR (ergo, not free for me, because I paid for SONAR for a good number of years) and not that some people throw it away--but that some people have pushed it use to such extremes. To be clear, I now know that it can be finessed far beyond its original purpose. For me the time spent exploring the crash issue experienced by others has been a personally fruitful learning experience for reasons stated above--primarily because I now understand some generalizable options for overcoming the loss of using my PCI Card. While I could choose to use TTS-1 in this way, the value for me here is in methods that can apply to other plug-ins.