User 905133

Thanks for this tip. I never use the PRV, I tend to enter drum parts from a usb keyboard and tweak either through the event list or the staff view, but with instrument names in the PRV, that sounds like a very handy use of the PRV. I haven't tested it, but I am assuming that like the event list, the PRV gets the drum names from the *.ins files. If that's not the case, where do they come from? UPDATE: I did a quick test (mouse drawn notes on staff) and sure enough the percussion names from the *.ins file I am used to in the Event List show up in the PRV.

For me, these (and similar feature/behavior requests) don't seem to be at odds with each other; they are not strictly default or set-once-and-work-for-all-projects preferences. It seems to me preferential choices are ideal to be included in lens management. Right now, some preferences in some functional categories are optionally either (a) saved with a personal customized lens or (b) not saved with a personal customized lens. So, if the preferences for which people are asking for choices to do it differently (different functions/behaviors) than either the current method and/or the default method were managed via lens management, I think one of the benefit of lenses as "This is the way I want my version of Cakewalk to work (implied: 90-100% of the time)" could be realized. With such an implementation, people who alternate between different sets of preferences for different types of projects might benefit as well. Just a thought.

I am not a visual artist (I failed art a few times in elementary school and junior high school) and I do not have the patience to design and create a theme, but I did tweak some collapsed Control Bar module visual elements to help save some wear and tear on my eyes. I think visual needs can be idiosyncratic, but if you think they will help, I would be happy to share the images I have created. This goes for theme developers, too, if they want to incorporate some of the ideas into their own themes.

The glass isn't 1/2 full; you now get 2 cases of 12 full bottles--too much to drink in one sitting! ? Seriously, though, please note that Keyboard Shortcuts are under Advanced Preferences ("P") both with and without a project loaded. Hope this helps.

As recommended by scook, videos using the Sonar X series (and later) might decrease the steepness of the learning curve. As recommended by JoseC, look in Preference ("P" = shortcut/reserved key binding). Let me add: the categories and subcategories of preferences vary--e.g., without a project open, basic, advanced. The images below are too small, but you should be able to get the idea--Sonar 8.5, Cakewalk basic with no project loaded, Cakewalk advanced with no project loaded, Cakewalk advanced with a project loaded. UPDATE: Below is the Options menu from Sonar 8.5. Other images showing Preferences from the current Cakewalk were deleted because they were too small to be useful. Please see the follow-up post which has more readable sample screenshots from Preferences as seen (1) without a project loaded (basic and advanced) and (2) with a project loaded (advanced). Hope this helps (regardless of which tutorial(s) you look at).

What happens in Studio One if you have a folder assigned to one bus and then you add a track to that folder that is assigned to a different bus and/or output?

There might be a quicker option: use Sonar 8.5. Yesterday when I saw the original post, I successfully opened Sonar 8.5 (on my Windows 10 PC). It seemed to have no problems playing a test file I created in June (2019) before I discovered Cakewalk by Bandlab. The test file consisted of two audio tracks and two midi/instrument tracks (TTS-1 and Rapture). In fact, if Sonar 8.5 still works on your computer, maybe you could have both options--with the workflow time saved doing projects in Sonar 8.5, use a portion of the time saved to explore features in the new Cakewalk at your leisure. If over time the new version doesn't click for you, you still have 8.5 (assuming it works on your PC as it seems to work on mine). Steve

Clear, excellent summary of some need-to-know differences! Should be included in a "Beginner's Guide to Exploring Lenses" perhaps under "Part 1: Choose the right tool for the task." Just one use of swapping lenses: I have my customized, easy-for-me-to-see Control Bar. However, sometimes I want to see/try what others are describing (techniques, problems, solutions, etc.). For me, its easiest to switch to the new Basic Lens which forces a standard theme. From there I can use one of the other factory lenses, which retains the forced theme from the Basic Len. Finally (when done), I can just load my preferred personal lens and my own project is pretty much back to where I started. Steve Update: The behavior of the Basic Lens forcing a standard theme has been changed. See Noel's post about this change.

Definitely one of a kind!!! If there is an afterlife, I'd expect Mr. Baker to be vibrantly active. Thanks for alerting us to his passing. I will be celebrating his life listening to his artistry

@msmcleod Asking here for Gopal's usage: Is it possible to add a list of the articulation names (like in an *.ins file, maybe) so the value for CC32 shows up as a name? (I was wondering about that before your reply, but didn't find any such option to do that in the Cakewalk Reference Guide.) Thanks.

From what I remember from playing with lenses, in 2019-07, the user created lenses were in the User folder and the factory lenses were in the Factory folder. I am not sure about pre-Bandlab folders as I didn't play with lenses before. I believe starting with 2019-09, the factory lenses are now copied into the User folder during installation. Maybe that's so (1) users can tweak the factory lens copies without messing up the official factory lenses in their own factory folder and so (2) the updated factory lenses are in both the factory lens folder and the user folder. Just tested this by loading the Advance Lens and re-saving it. YUP: what scook said (as I was pasting in the screen shot).

Interesting idea: daisy-chaining midi plug-ins. If there were "MIDI Chains" like "FX Chains" that might be fun to play around with to algorithmically (including randomly) manipulate midi data.

Have you tried this method: "When UACC is activated you can change articulation by setting CC32 to specific values that correlative with different articulations?"

@Jon L. Jacobi Not sure if I started a public reply to the following, or if I sent it as a PM.* But this might be related. If you have created a favorite lens (or two or more) and you want to be have the Screenset option on the Control Bar, try loading the lens, go to Lens Manager, check [ ] Screenset as a Control Bar Module and resave. If that doesn't work, maybe there's another issue. *I vaguely recall starting to identify in that thread some of the differences that I saw and that others have described, but I felt I didn't know enough to be able to be do a competent explanation, and I don't think I was able to find the threads/posts where others identified some differences and made recommendations on using them. ADDENDUM: Found the posts I had been looking for when I was trying to respond to the redundancy issue: here and here. I remember being too tired that night. Hope these posts are as helpful to you as they were to me.

Maybe collapse would meet your needs? Either keyboard toggle "I" as suggested or the << or the v then collapse might work for you. Not sure why you don't have Screensets listed as a module. I switched to the Basic Lense and then right clicked on the Control Bar. I know I made a lense without the Virtual Controller item under the Views menu. Not sure if you could have made a lense without Screenset. Addendum: Yup, what scook said: quickest way to see if its a lens is to switch to None! Addendum 2: Another yup--I created a lens w/o Sceenset option under Modules; so, it's possible! [3 ancient images deleted 2023-12-28]

Interesting, if I understand what you are asking for. I was in a "Matrix" screenset which had no Inspector window. Upon pressing "I" it returned as a floating window. A second "I" closed it. When I docked it, to get rid of it (i.e., not just collapse it) requires two steps--undock and close. Correct me if I am wrong, you are looking for an additional option here ("Undock and Close"). That way the "I" keyboard shortcut can be used to open and close it. I tried what arlen2133 suggested with the Inspector docked in two different locations. "I" collapsed it as opposed to closing it. BTW, I agree that for stuff like this, screensets are handier than lenses. [ancient image deleted 2023-12-28]

With this proposal, if "bus" were a property of "folder" such that all tracks in that folder were assigned to a specific bus, what would happen when a new track were moved to the folder? Would it automatically be forced to the folder's designated bus? Would it retain its original bus? Would there be a check box someplace to make the default behavior one or the other of these two (and maybe something else)? Right now, as I understand it, the option exists to assign all audio tracks currently in a folder to be assigned to an existing bus, a new bus, etc. en masse by holding down Ctrl and selecting an output. At present, I don't make extensive use of busses, but probably will during the coming year; I do make use of multiple outputs and folders and I am wondering how this proposed option might work. It seems to me that a checkbox that says "[ ] automatically assign all audio and instrument tracks in each folder to the output of the first track in the folder" should be unchecked by default so as not to catch users by surprise (maybe with an "Are you sure?" warning). I suppose there could also be another checkbox that says "[ ]allow new tracks added to a folder assigned to a single bus to retain their assigned busses." Interesting possibilities.

Forgive me for sticking my nose in here; I was casually following this thread and just have to ask-- is your friend trying to run a 32 bit OS on a 64 bit Windows 7 PC with something like VM Virtual Box? If so, was that being done to try to "install and authorize some free plugins in (32 bit) Sonar Le 8.5 from Izotope?" I can't offer anything to try to solve the problem, but there's an itch in my brain on this ("Huh?") .

Its really a matter of personal taste (let your ears be your guide), but I like low-end for filling in the audio spectrum. Not sure you have considered adding a double bass to your orchestration. If you are using staff view to write parts, having each instrument on its own track has some advantages. The suggestion of doubling parts seems like a good one given your instrumentation. Other possibilities include your choice of rich/full patches/sounds, "thickening" the sound/patch used, production techniques, etc. Are you are scoring for an actual ensemble of a set number of performers? If not, you could do something as simple as double a part (duplicate track), put it on a different instrument/patch/sound/multisample at a lower octave for starters and then tweak the part for variety. Obviously, if you are scoring for a string trio + piano, you might have to make it a string quartet to do this. Anyhow, just some thoughts. Hope they help.

Thanks for following up and thanks for asking. I had at least two files open with different midi clock sources and switched between the open projects from the Windows drop-down menu. One was set to use midi sync, the other set to use audio. I confirmed that at least twice today before posting my question. Later in the day, I got a code 13 dropout; I am not sure what prompted that. (I dealt with it and moved on.) I will see if I can replicate it now with the code 0. Results of quick test: With three specific files, after switching I got code 13 four times. With two of the files open, I got code 0 four times when switching. It is possible that something within those files other than the midi clock source makes a difference as to which dropout code I get. BTW, when I consider having two projects open at the same time with different clock sources "User Error" (i.e., not a bug). Easy fix: Don't do it! Update: Currently narrowing down possibilities when switching with the two-files loaded. Drop out code 0 seems to happen when I switch with the transport off (not playing back). When playing back just not (several times), there was no audio dropout, though there was a consistent audible glitch. (Dropout Msec = 250) It is possible the code 0 comes from (1) Cakewalk not receiving midi clock (i.e., not being sent) and (2) the transport being stopped. To be tested. Update: I need to sort this out for my own needs (real-time performance stability), so I will be doing further testing, probably tomorrow. But for now, I can get audio dropout code 0 both when my external clock source (1) is and (2) is not transmitting midi clock. This is prior to putting Cakewalk into external midi clock standby mode (i.e., prior to pressing play on the transport and getting "Press <Esc> to cancel. Waiting for MIDI Sync.") Once in external midi clock standby mode, the Window drop down menu is disabled, so no switch can take place until after the transport has been started from the external source. Then an external stop command successfully stops the playback, Cakewalk goes back to midi clock standby mode, there is no audio dropout, etc. as expected.

Just a footnote about ghost cursors. I just had one, but it's gone now, so there's no way to diagnose it further. I am guessing there can be multiple triggers/causes. Here are somethings I observed: 1. I was exploring the potential to cut and paste from one project to another. I had multiple projects open. 2. When I switched to one project's main window (Track View), I got a ghost cursor. 3. When I switch back to the other project's main window, I could see that the ghost cursor had been in the position of the first project's main window. It's gone now, but perhaps this leads to what I previously thought, possibly the ghost cursor comes a re-draw function. I have no experience coding GUIs, using GUI APIs, but in case the ghost cursor continues to affect users, maybe this info will be useful.

I have had floating windows from two different projects on a second monitor (i.e., parked so I can take a quick look or to drag it to my main monitor to edit. That being said, I had some issues with multiple projects open and the floating/undocked windows (panes?) when I was testing different lenses. Other than that, I can't tell you much more, because I stopped exploring lenses. Also, having different midi clock sources (midi v. audio/internal) caused problems (dropouts and possibly shut downs--i.e., crash and dmp report generated). That's all I know--if I understand what you are asking for: it can be done; I have found some problems. I am guessing there are others with more knowledge and experience who can clarify what can be done and what can't be done with multiple monitors. I defer to them. ADDENDUM: I know its too small to see any detail, but the image shows multiple window panes from three projects on two monitors. So far as I know you cannot have more than one main window open. If not, maybe that's what you are requesting.

A link was posted in another thread*--link to online document. (*from 2019-09 Feature Overview.) UPDATE: The online doc (dropout codes) for 2019-09 opened in my browser when I clicked "Help" in the lower right corner.

Showing dropout codes as a tool to empower users to problem-solve (including reporting the code for support if they cannot remedy it themselves) is brilliant! Is there a preferred place to report what might fall under "unknown" reasons? For example, a week or two ago , I uncovered circumstances that seem to consistently cause audio dropouts. I didn't ask for help because (1) it falls under "user error" (IMO) and (2) I know the user-error cause , how to avoid it, and how to undo it if I forget and do it again. I don't think its a bug in the software, though telling users "Hey, this is what you did; the dropout will happen again if you make the same mistake" politely with an error code might be helpful. UPDATE: The online doc (dropout codes) for 2019-09 opened in my browser when I clicked "Help" in the lower right corner. NICE!!!!