User 905133

I agree!! That's why I really appreciate that a list of UI changes is maintained and easily available (plus now we have a link to it so we don't have to search for it).

Just in case it wasn't clear from the context or my earlier posts, my intended use of overlays is for small sets of elements, not an entire theme. 2021-06-21: Example related to the general use of "overlays" but unrelated to this thread removed.

Then there is no excuse for people not reading the manual!!

I knew it!!!! But just watch--someone will come along and not understand that you were making a statement of the way it is. BTW for the benefit of others (I know you and most--if not all--of the contributors to this thread already know: While a picture is worth a thousand words, maybe a translation is needed: "If you have downloaded the Theme Editor, look on your computer for the pdf manual or just use the help button in the editor as scook states immediately below."

Some people reading this thread might not realize you are making a statement of the way it is.

@scook and @Colin Nicholls Yup! Not much more to be said, except maybe a few little things: Just to clarify, I was trying to help you by doing the steps I described when I wrote: So, to summarize: people with more experience creating full themes have given you expert advice. I tried to present the steps I would take if I had a theme that wasn't being maintained by the person who created it and I wanted to update it for my own personal use. So, no one has come forward to fix your theme for you; others have tried to help you to fix it yourself. Explanations and steps have been given in a number of ways, but if those explanations and steps aren't helpful to you for whatever reason (but not for a lack of help offered by forum members), then it seems prudent that you use either the factory supplied themes or one that has been updated by its designer.

Thanks for the confirmation. I don't want to step into the issue of responsibility. I was very glad when were given the list of theme element changes a number of updates ago, am very glad that the list is maintained in one spot so we have a record of the changes, and am very glad that there is now a compatibility check that has the link to the list of changes. I also understand that finding theme elements and tweaking them can be a lot of work. 2021-06-21 N.B.: Just to be clear: I was being polite here. At no point did I ever think think that Cakewalk had a responsibility to fix your tweaked theme. Apologies for not saying this yesterday.

This sounds familiar. I seem to remember a discussion about this (possibly in the 2021.04 thread?).** If I am remembering correctly, is it safe to assume that you never repaired the theme? Maybe I am misremembering, but I thought you had experience with tweaking themes and were going to fix the element(s). If I had offered to help but dropped the ball, I apologize. (I have zero experience designing themes myself, but I have made tweaks). **ADDENDUM: Found it! You have people in the current thread with more extensive theme experience than I have; so, I will defer to them. But, to better understand the issue (assuming it is the same), they might want to review the previous discussion. PS: Not sure about this, but it might help others to better help if you were to post your last working version of the theme and a link to the original theme before you tweaked it.

Thanks for this reminder to check for changes caused by Windows 10 Updates. Sometimes (more with earlier updates than recent updates) one of my HDD's extended partitions disappears. It took a while but I found an easy solution (run/reinstall an Acronis "extended capacity" disk manager). With a recent update to 21H1, I totally missed that this particular solution once again needed to applied. So, thanks! I wanted to mention the details because perhaps with other hardware that the update changes (e.g., monitors), perhaps there is a similar fix--reinstalling a hardware management tool.

(1) I've had Nils' K1v for a little while and I forget how I installed it. I probably used the basic method: (1) using the K1v installer and (2) re-scanning my plug-ins with Cakewalk's scanner (which is found under [P]references > File > VST Settings). I never just copy or move around *.dlls. I have heard of others doing that, sometimes with problems. So, I generally just use the manufacturer's installer. If you used the installer and the dlls are in the right place, running Cakewalk's VST Scanner could help. Double check to make sure that the location of the K1v is in the scan path. [For info on rescanning, see scook's post/link from March 28th above--the second post in the thread.] (2) My FYI might not have been as clear as it could have been. I allowed the image to do some of the explaining. I wanted to test Nils' K1v only to make sure the K1v wasn't causing a conflict with Vital FX (if there were such a thing; but so far as I can see there isn't). To test, I loaded the K1v and tested it with both z3ta+ FX and Surge FX. (See the image which has the K1v as an instrument with both z3ta+ FX and Surge FX in the FX bin.) I hope it was clear from the image that the FYI wasn't saying the K1v processed external audio with FX.

Agreed!!! And thanks to you and others for calling attention to this! I just tested it (I'm using the Early Access Release) and it works!!! I have some Workspaces with a full screen Console on a second monitor and can easily imagine tweaking a Workspace (making variants) to easily switch strip display configurations (assuming the preferences get saved and restored).

Oooops.

I don't have vital, so I looked it up and like others have said and as the webpage says (if we are talking about the same plug-in) "Vital is a visual synthesizer." That being said, there are some virtual instruments that have FX that do allow the processing of sounds that are external to the instrument. For years I used Z3ta+ to process audio from non-Z3ta+ virtual instruments. More recently, I have done this with Surge. In both those cases, the synths come with separate files (dll files) that handle the FX. If Vital boasts the ability to process non-Vital audio, you might want to see how they do it. Maybe they also use an FX dll that's in the wrong place. ADDENDUM: I don't see anything in the Vital Press Kit that leads me to believe it can process external (non-Vital) sound sources. FYI: The method I described does indeed work with Nils' K1v.

Nice catch!

You can click on View in the Event View to select the >>viewing<< filter. But it sounds like you want an editing filter: Just did a quick test with some midi events in something I was working on. (1) While in the Event View, I did Ctrl+A to select all events. (2) Then I used the E shortcut as Mark suggested but to the Global Binding > Select events meeting certain criteria function (which brought up the Event Filter while in the Event View). (3) I unselected everything in the Include column of the filter except for [x] Note and set the Note range for C0 to Bb3. Maybe there are other ways, too? If so, here's another one.

Yeah--that would work for me if it can be done. Not urgent for the current release.

Just in case it wasn't clear, before the new automatic numbering, I numbered ports myself based on my needs. In the images I posted, I only labeled the ports with duplicate names (OUT, ANLG, ADAT) because of Cakewalk's change. I don't need two sets of numbers for ports--mine and ones assigned by the software. So I got rid of my numbers in those examples. I would prefer my own labelling system, which is why I wondered if there could be an option not to use Cakewalk's numbering system. (Not a major issue for me.)

I used to assign them with my own numbers: OUT 1 & 2, OUT 3 & 4, etc. The only way I can do that is if I have them all "OUT" and let CbB assign the numbers. Also, I would want ADAT 1 & 2 to be ADAT 1 & 2 not to be assigned ADAT 9 & 10. If I name outputs the way I used to, I get redundant duplication. As far as not knowing where I was assigning something, I kept track of my hardware routing. Honestly, I never understood why so many people got confused that port 1 was a stereo pair for what might be called 1 and 2, etc. For me, I just numbered them myself as friendly names. But I can live with being forced to have good habits. I would rather that ADAT 1 and 2 be called ADAT 1 and 2 not numbered 9 and 10. But I can live with it. Was just hoping there could be an option to not have the automatic numbers added.

RE: Improved input/output port naming . . . If this is the way its supposed to be, I can get used to it, but I am wondering if it is possible to have an option to suppress the new automatic numbering when we choose to use friendly names.

If the alleged legacy apps improvement makes my PCI audio card work the way it did a few Windows 10 updates ago, bring on Windows 11!!!! Maybe we will have options like: [ ] It used to work under Windows 10 v. 1809 . Maybe all the Compatibility Telemetry activity over the past year or two will be put to good use with the release of Windows 11.

method withdrawn

In a section of the forum designed to give feedback to the makers of Cakewalk, a fellow user requested some changes to make the Audio and MIDI tabs in the Inspector easier to see. Since I am an explorer by nature who now has age-related vision issues, I did a quick test of concept. For other users who might want to customize their own tabs based on vision (or other) needs, they are indeed tweakable.

Ooops. Wrong sub-forum. My bad.

I remember feeling this way back in November (hence my minimalist initial reply back then and my subsequent choice not to engage in a the discussion of others) and I still agree that any discussion of the possible benefits of a midi data flow chart within Cakewalk belongs in its own thread. I am surprised that no one opened up a discussion in another thread or put in a request between then and now. (I thought I had, but I might have decided not to.) As for me, I decided months ago to give up on the idea that the remote control functionality in the Inspector-based Arpeggiator would either be explained or fixed. But this is not the thread to discuss that issue. I was just offering a simple example off the top of my head as to where a midi signal flow might be helpful.

You might not understand but that doesn't mean that others wouldn't find it useful. There are problems in CbB because the flow of MIDI data doesn't seem to work in some circumstances and for those of us who haven't given up, it would be helpful to know what CbB is doing with MIDI data under the hood. One example: MIDI Remote Control doesn't work with the Inspector-based Arpeggiator. It would be nice to see the alleged flow to determine if its a bug or if CbB is doing something that users don't know about.