User 905133

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.

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.

The one to the problem that was discussed over a year ago? IIRC there were some changes to the Staff View since then, so perhaps the original issue has been resolved.

F1 should bring up the *.chm file, though it might pop up behind another window. Or, if you have a third-party tool that can filter a file list, search for vel*.chm. Another thread that might have useful info: Turn off Velocity Sensitivity. I just ran a quick test of the Cakewalk Velocity MFX with TTS-1 just to make sure it affects volume. I split the Instrument Track into its MIDI and audio components, put the Velocity MFX on the MIDI track (in the track's FX bin), and recorded both midi and audio with the settings that were there. (See image.) Low velocities and high velocities sounded very close to my ears. If necessary (based on what you want to do), you might need to tweak the settings per the help file if the plug-in meets your needs. Since I recorded the audio through the Velocity MFX Plug-in, the loudness has been corrected based on the settings. However, the MIDI track is as I played it (with low and high velocities). With the plug-in on, all notes sound at the same level to my ears. If I turn the plug-in off, I hear the notes as played (softer and louder notes). Hope this helps. Clarification: Based on the following, I don't think the settings I used is the ideal solution you want. Also, I am not sure that you can use the plug-in by itself to adjust for different levels across your keyboard in real time (if that's what you need). That's why I referenced the Help file.

Have you tried this? [MTuner]

(1) These manuals? (2) Is the automap guide applicable? I have plain old MIDI interfaces with multiple ports and they show up as numbered ports. Is it possible that the ports are for user configuration and not specially dedicated to certain functions? If so, perhaps the automap utility is just a tool for helping users to set up the flexible MIDI ports?

Thanks for mentioning this. I saw previously owned "instruments" got reset for a new round of 180 days, but had no idea the files were changed. Did you compare the sizes of the unzipped files or just the zip files?

I haven't used Mobius in like a decade; so I am not sure what newer versions look like and I forgot how to use even the old version, but let me ask: Are your plug-ins VST2 or VST3? If VST3, try the VST2 versions. This might not be the solution you need, but if I had the issues you described, that's the first thing I'd check. Hope its that easy of a solution. If not, maybe some others here have more current experience with Mobius. UPDATE: I just looked it up and if its the same Mobius I was thinking of, it looks like same software I used a decade ago on an XP PC, probably with SONAR X1. (The copyright date on the site says 2011!) If the software itself hasn't been updated since then, you might want to consider newer looping software--unless others here have gotten it to work properly more recently.

A year or so ago I was exploring an issue related to this IIRC. I remember doing an awful lot of trial-and-error testing to try to see what was going on mainly because I have had successes with my Workspaces set up for two monitors. I seem to recall the specific issue you are mentioning, but I don't recall if there was a "solution." I seem to recall confirming somethings. If I am remembering this correctly, maybe the previous discussion will at least confirm the issue. I will look for it. Found the thread I had in mind. I will try to re-read the thread this evening to see if it relates to your current issue.