User 905133

(1) I can. (2) That's why I asked if he tried clicking on the ">" arrows hovering over the categories. It might not work on his PC; if so, it sounds like a bug to me, but we don't know. Some people see difference and assume the worst. I'm like that, but then I make a cup of tea (or coffee) and try again. ?

Did you click on the ">" arrows to see what's in each category? Did you hover over the categories? Many of us like the new menu system. (I just wish the DX/VST2/VST3/32-bit colors were assignable via the theme editor like they were in EA1.)

It might, as you point out. The size issue aside, the presets sound crisp to me like the sounds in other AAS products. I think it might appeal to people who want it for the presets. I am not sure it has advantages to help those new to modular sound design over other software modulars that are available. Not sure if CV-1 is easier on CPU load, but that might be another positive.

Just an FYI: The behavior is the same in 2021.01. I don't think its a bug, just a change from the SONAR X series. In SONAR X3 (presumably like Platinum), the cursor changed to horizonal parallel lines with and up and down arrow. It does that in CbB, too. There's probably a reason why CbB has the "grab bar." Some people seem to never notice cursor changes, so maybe the bar makes it easier for those people. Who knows?

Just an FYI (based on CV-1 trial): Although VM's Plug-in Host can hold CV-1, not many of the parameters are available for VM control. To me this is significant because I can resize VM, not CV-1. Size comparison also included here so people with vision concerns can save their 15-day trial for when (and if) AAS makes improvements.

I'm getting old--never thought of 1990s as retro! ? Nice video. Nice happy tune!

How-to-check-incoming-messages-using-MIDI-OX mini-tutorial removed to reduce footprint.

FYI, I installed a trial version of AIR Music's Boom last November and used the installer's default location. Maybe yours is in the same place? Mine is at C:\Program Files\Steinberg\VstPlugins for the x64 version (C:\Program Files (x86)\Steinberg\VstPlugins).

mini-tutorial removed: retrospectively OT.

Is the suspend box checked or unchecked?

NOTE: After changing 2/3 of my pre-2021.04 EA custom Workspaces, testing them, and finding inconsistent results, I am not sure the simple open and save to replace method is a good one. I am rolling back to 2021.01 to test. In short, the simple method might work for some pre-2021.04 EA workspaces.

Evidently, the structure of *.lns files [that's lower-case LNS for Lenses now known as Workspaces, not INS] has changed with the 2021.04 EA Release. Based on what I read as discussed in the EA thread, previously developed user Workspaces evidently did not save and/or restore information related to the new Tempo Track. So far the solution that seems to work is for users to load each pre-2021.04 EA Workspace [*.lns file], scroll to the bottom of the Workspaces list, and choose "Save Workspace." This can be quite time consuming because it requires excessive mouse movements for each Workspace. To me it seems like it would be quicker and easier on the hand to have a shortcut key assigned to something like a Workspace | Save function. The flow would be: ||: select Workspace to be updated, press shortcut key :|| In my mock up, I had searched for "save" and found the first functions existed and tried to show where I'd like to see some additional functions if at all possible. Like all other shortcut keys, they would save time. Sorry that is not clear; I will re-do the image with a box around the functions I am suggesting and some wording (like "please add these functions"). Also, apologies for my use of "File structures." I did not mean specifically *.cwp files. The idea started from the issue I had with having to update *.lns files. Since the 2021.04 EA thread also mentioned that template files, I tried to make my request general to all instances where Cakewalk file structures might be changed in such a way as to need fixing by simply loading and resaving them. I will try to figure out a way to make my request more specific and yet open ended. Related to this request, I really like the new compatibility check for user themes (another type of file) and have been thinking of requesting that the same thing be done with Workspaces (and other changed file structures) if possible. Just like when you select a theme that uses a file structure that has changed, Cakewalk detects an incompatibility and others some choices. So, it might be handy to have something similar for cases where a user selects an Workspace with an older format. It would be nice if there were an option to immediately re-save the Workspace (*.lns file) thereby updating it to the new format. The use of a shortcut key occurred to me before I thought of a compatibility check solution. I would much prefer the latter. As for expanding the list of assignable functions, I have seen other posts where people wished for functions that were not available. Personally, I think that having more shortcut functions available adds to Cakewalk's flexibility and customizability, but generally I don't use more than a few. It was really that my hand was hurting from having to do repetitive motions to click/load/scroll/click/save over and over. Thanks for giving me the opportunity to clarify my original request and to add the comments about the compatibility check. CORRECTION: I was previously under the impression from several posts in the 2021.04 EA thread that previously developed user Workspaces did not save and/or restore information related to the new Tempo Track and the solution was to update them by loading them and resaving them one at a time so they would save and/or restore Tempo Track information. However, " . . . workspaces have no information saved as to how the tempo track should be displayed (i.e. its size & visibility)."

IMO, favorite features / benefits of using Cakewalk (or anything for that matter) vary from user to user and in no way can used to assess its usefulness to other users. That being said, for me, they are: (1) Cakewalk's flexibility / ability to be customized based on user preferences. (2) The ability to work with a wide range of external gear and virtual gear, including the automatic migration of many plug-ins (instruments and FX) owned/licensed by users of SONAR. (3) The developers' interest in and helpfulness in working to help debug and if possible solve individual issues even when the issues are the result of user lack of knowledge, user error, etc. or the result of things Cakewalk has no control over (e.g., third-party plug-ins). (4) The ability to work with a wide range of audio and midi interfaces / devices. (5) The developers' interest in user experience and dedication to continually implementing changes/ improvements and fixes. (6) A forum for staff and knowledgeable power users to help users. For me the top weaknesses are: (1) Some default color choices that cannot yet be customized (e.g., dark grey text on a light b ackground). (2) Lack of built-in polyphonic audio-to-midi conversion (without having to pay big bucks for third-party products). (3) Non-resizable track control images ("widgets"). (4) A staff view that has not been updated nearly as much as other features (including the lack of rhythmic triplet-like structures beyond 3, e.g. 5 or 7). (5) Lack of small scale and large scale compositional midi data generation (21st century equivalent of musical "figures" like mordents, turns, etc.). Again, what I like about Cakewalk and what I find needs improvement should not be used to assess Cakewalk. Thank you for asking. I hope this helps. PS: Will you be making the paper available to us to read?

Heads up for users systematically loading and saving custom Workspaces to update them: While loading and saving each custom Workspace one at a time, I came to one that restored an arranger track which I have yet to use in any custom workspaces. To double check the Workspaces I had already re-saved, I started loading them beginning at the top of the list . Without any warning, Cakewalk suddenly closed (no error messages). It is entirely possible that this was caused because I tried to reload a Workspace before the previous one had been fully restored. Also, it is a tedious process because the "Save Workspace" item is near the bottom of the list.

It would greatly facilitate the resaving of changed file structures (such as *.lns files) if users had the ability to assign shortcut keys to save those file types. UPDATE: Feature request withdrawn because re-saving custom Workspaces doesn't help resolved inconsistencies, since " . . . . workspaces have no information saved as to how the tempo track should be displayed (i.e. its size & visibility)."

Thanks for calling the solution to my attention. With 10 pages of posts in such a short time, evidently I missed the solution.** I tested the method by saving the "NO VIEWS 2" Workspace with a new name. So now that I know the method, I can backup all of my workspaces and resave each as I need them. I do wish though that we had the new list structure (folders/categories and fly out lists) for Workspaces. **EDIT: I am laughing at my forgetfulness--not only did I see the post, but I even gave it a "Thanks" emoji on Saturday. Update: AHA Moment: I now understand better that Workspaces are not supposed to save/restore the Tempo Track since " . . . workspaces have no information saved as to how the tempo track should be displayed (i.e. its size & visibility)." Update 2021-04-03: The above statement has now been clarified in another thread. Prior to the 2021.04 release workspaces had no information saved as to how the tempo track should be saved.

As I PMed you, I looked through my E-Mu files and a number of the usual websites that have E-Mu resources. A search of several site captures at the WayBackMachine also turned up nothing. In fact, although links to the old E-Mu.com resources (including legacy sound modules) almost never work, even the list of links I looked at don't show listings for Proteus FX bank files. When Creative Labs first started making the E-Mu resources disappear, a couple of us took it upon ourselves to preserve what we had. I might have some e-mailed *.zip/*.rar files on my XP PC from a fellow E-Mu user that had things I didn't have (not sure I have the right HDD in there, though). I could take a look over the next few days. Also, I know a few people that had either the Morpheus or Ultra variants. I can see if I have their e-mails in case they also had the FX version. (Yes, I know that those two had different banks from the Morpheus and the Ultra.) The only other option I can think of (if you haven't already tried there) is to try the Facebook groups. After Verizon killed off Yahoo! Groups a number of active E-Mu users migrated to Facebook. It might not work to restore banks 0 and 1, but it couldn't hurt to replace the battery (unless you damage the unit). If you replace the battery and restore doesn't give you back banks 0 and 1, perhaps you can create your own. UPDATE: After an exhaustive search, I was unable to find evidence of any *.syx bank files for the Proteus FX. And since I never owned one, I never created a backup for my self.

Free as in freedom, not free as in cost?

Thanks for mentioning this! I am not sure if the implication is that we now have to tweak our existing Workspaces and resave them all to take into account the Tempo Track View [or whatever its called]. I was exploring this with a current test of something else and got a legendary c.......5 exception error. Addendum: I tried something with a new project with an empty Instrument track added. I switched to an existing Workspace called "No Views 2" which was designed to explore minimalist Workspaces. Note that the Tempo View is not under Menu > Views. Tempo Track Show/Hide is however available under Track > View. I can live with this, but I suspect it might cause lots of confusion. Not a showstopper for me; just adding this in case it helps.

Does it also speed up when you open the midi file instead of importing it? https://www.cakewalk.com/Documentation?product=Cakewalk&language=3&help=Recording.36.html ADDENDUM: The import v. open issue comes up at times in the forum. Here's a recent post that might help explain the "speed up" issue:

Maybe I don't understand this, to me the type is shown, though you do have to expand the folders/categories to see them (at least with the manufacturers).

Amen--awesome early developer!

NOTE: Customizations that used to work seem to no longer work. So it is unclear if these kinds of customizations will work in the future. So far: Addendum: As Colin notes in the Theme Guide, sometimes changes don't occur until a Cakewalk reboot. Today, I got this with the same theme elements as above: In case it doesn't stand out, today the VST3 / Plug-in Tree text color/colour (Green) now shows up in the Plug-in Browser. (No change in the new and improved soft synth list. Also, not sure where the "DX" color/colour is coming from.)

ooops - posted to wrong thread.

moved and summarized visually; more relevant to UI theme thread than EA thread