User 905133

Glad you got it solved. FWIW for years (but not recently) I have used Cakewalk/SONAR to backup and restore bulk data dumps from a number of modules--including some with terrible small buffers (VZ-8m), Proteus 2000-based gear (202K/206K sized banks), among others (probably the P/1+ Orchestral, too). I do remember having to tweak the sysx parameters occasionally, though I haven't been doing much bulk data dumping/restoring since starting with CbB. A few years ago I started using a patch librarian an E-Mu gear user developed. If someone has developed a librarian for your gear, that might be a better route if you create your own banks or if you want to juggle presets/patches from a number of different banks. For restoring banks your solution is ideal.

Using Window's file properties, you can edit them from CbB's Media Browser. Right-Click on the MP3 File. Choose the Details tab. Edit.

As a Cakewalk user since it was a MIDI sequencer (pre-Digital Audio versions), I don't do much with tempo changes, but I used your question as an opportunity to try the new Tempo Track. I didn't try using an loading an old file, but I was able to get something that looks like the traditional tempo view. It was a quick test (my first time trying the new Tempo Track). [references to the Early Release program (including feedback/bug reporting) removed since 2021.04 has now been released.]

That's the Devo version, right?

Maybe someone can figure out why TTS-1 has worked flawlessly as intended for some of us over the years? Perhaps there's something about it that makes it not work properly on newer computers with CPUs and other chips/devices built past a certain date? Toward that end, I'm willing to test drive on my PC a few TTS-1 only *.cwp files known to crash on other systems.

Got the concept down. Thanks!!

So far my theme personal tweaks have not gotten into tweaking the strips, but now that I know what's up with them, maybe I might look into it. So thanks to @murat k. for raising the issue and to @Colin Nicholls for providing the explanation. Let me see if I understand it. I booted the editor and selected Tungsten as the base for a potential new theme. Correct me if I am wrong: the Original Plug-in Tree Icons [strip] is the base editor strip and the one above it (Theme) is the strip as it is in Tungsten.

Thanks for the clarification.

No forward and back-and-forth in plugin? = ???? Guess # 1: ???? = Ctrl+Z doesn't get passed on to plug-ins Guess # 2: ???? = Ctrl+Z doesn't do anything in the Cakewalk interface itself. Until we get clarification, your guess is as good as mine.

Thanks for your thoughts and for the opportunity to clarify. My initial reason for showing the image here was to suggest that if vision/size/resizing is a concern, potential buyers might want to wait until there are some changes to CV-1 to use their 15-day trial. Today I started to assemble some images to show more. I have a draft of a CV-1 within VM within CbB that shows a comparison. So far as I can tell, the nested images reflect the size of CV-1 in standalone mode as well. Yes, I tried those panel controls, but on my PC they just changed the visibility of the left/right/bottom panels. I also tried the resizing triangle in the lower right hand corner of the frame (both within Cakewalk and CV-1 standalone). As for resizing, I much prefer that software handles that itself; I really don't like to change my monitor settings to adapt to software. On my PC some plug-ins can be resized within CbB by changing the size of the plug-in frame. Some plug-ins don't. Some have artifacts and behave badly when resized. In my experience on my PC, CV-1's content doesn't resize within CbB or in standalone mode. The frame gets bigger but the plug-in's visual content stays the same size. This might vary on other PCs. One of my concerns was a comment that CV-1 might make a good starter software modular to learn on. That was also part of my reasoning for addressing the resizing issue. As I mentioned, I like the crispness of many of the AAS sounds I have (based mostly on the free AAS Player, the Session series, and VA-3). Yesterday I listened to the CV-1 sounds and those have a similar crispness. In fact, I have tested a number of those as plug-ins within VM's plug-in hosts. To me they all work well within VM's control environment. I assume AAS will work on improving CV-1.

I was curious about this. I don't design entire themes, just elements as I need them, so I wanted to try to match the view that you use. In the image you posted, the elements are there, but you can't see them well because they are dark grey on a black editor background (Dark setting in the editor). They are more visible if you use the Light setting. Are you saying the issue is with the color of the icons Cakewalk uses in the Tungsten Theme? (I don't generally use it, because I have trouble with the preponderance of greys and black, black on greys, etc.). Or are you saying the image elements used with the Dark setting within the Editor are not the ones actually used in Cakewalk?

One of the nice things is that we all have different preferences, workflows, learning curves, etc. Learning curves really vary from person to person probably based on prior experience among other factors such has how a person's brain works. I lucked out decades ago by getting in on the ground floor when my college got a Moog modular synth. Based on that, I gravitated towards E-Mu's digital synths (Proteus/1 and later sound modules) which had virtual patch cords--digital counterparts to what I was very familiar with. So, when I stumbled onto Voltage Modular, designing presets and making music by choosing modules based on functions, patching them together, etc. was quite natural for me. It just makes more sense because I can see what's what. Personal preference. Some people have no desire to create sounds and prefer to use presets designed by other. IMO, there's nothing "wrong" with that nor with creating music with "real" instruments or with purchased sounds, loops, etc. designed to impress people. Also, I don't think there's anything "wrong" with people who post songs they made in various online locations, again, all designed to impress people. Granted, modular synths (hardware or software) may not appeal to you. That's fine, too.

If you prefer Instruments (as opposed to Voltage Modular modules) and if you haven't invested in VM yet, I would encourage you to try Nucleus (currently free**) first to see if you can get into modular sound design. With your interest in the VM2500, you might want to wait to see if they come out with an Instrument based on the modules. Cherry Audio has done that kind of thing before. Also, in the chat for the video demo someone asked if CA would be developing an instrument version and the reply (something like "anything is possible") leads me to believe it is indeed possible. Personally, I like VM--a lot!! So, I am not trying to talk you out of at least trying to get into it. But if funds are an issue, if you might prefer a VM2500 as an Instrument (if that is in the works), and if you are unsure about the modular learning curve, getting Nucleus and waiting a bit might work for you. **Just checked CA and PIB--free at both; might be others offering it free. There's a risk, though. You might really like VM and within 24 or 48 hours you might spring for Core and some modules. ?

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 (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?

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?

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)."

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?