User 905133

From what I understand there are better programs than Cakewalk for large orchestral scores. You might want to try those. Evidently the previous post was about tracks, not scores with staves on them; ergo, comment was unintentionally OT.

The visibility of widgets is (in part) a function of the Track Control Manager. Changing the Widget Filter / Track Control Filter to "All" is probably quicker than changing Workspace.

Thanks for raising this issue and for the various comments. It has been a while since I systematically ganged multiple midi channels on one DAW/sequencer track--certainly before take lanes and probably the current system for setting different record modes (e.g., Sound-on-Sound). I did not look at the Console faders, so to a certain extent what I did based on this thread is off-topic. However, what I did relates to the comments made in discussion. I share my attempts to recreate an ancient workflow only insofar as it relates to the discussion. After the first attempt, I found I needed to change the takes behavior and the record mode since those did not allow me to use the ancient work flow. I only mention this in case these settings also impact what the faders seem to do, not to derail the topic. Then using a usb/midi keyboard I played an external multi-channel synth module in effect through Cakewalk so I could record data from three different midi channels on a single Cakewalk track and then playback them back. The first three passes were (for the most part) note data. With three more passes, I also recorded CC data. Thus Track 1 (the only track) had note data and CCs on 3 midi channels. As expected, when the Channel Widget was set to None, the three midi channels played three midi channels on the sound module. Also as expected, when the track was forced to a single midi channel (with the Channel Widget), all three midi channels played played the sound module only on the forced channel. I don't know that I will ever develop a work flow using this ancient method in modern Cakewalk, but if I understand the discussion points raised above, this little test might have some implications. PS: Chappel shows the widgets in the Inspector pane; to force all track data to a single midi channel, I used the channel widget in the track pane. (It shouldn'y make a difference, but if you don't usually use the Inspector, its another option.

Thanks for the reply; makes perfect sense to me. I tried to reconstruct your usage based on the description and the screen shots. I am not sure I followed your exact steps. It looks similar, but not 100%. With the steps I came up with, after opening up a project that was saved with the staff view showing and positioned under the Control Bar, I got the following--but it obviously was not constructed with the same steps you used. Working on trying to figure out your steps. EDIT: On second thought: I closed the minimized icons and used Menu Bar > View to switch and now it looks closer to yours. EDIT: I set mine up with the Console showing under the Control Bar, saved it, closed it, closed Cakewalk, reopened Cakewalk and the project. The Staff View under the Control Bar came up (with a minimized icon, too). Next, I close the project without saving it and opened and closed it 4 more times with no changes. When Cakewalk created the UI, it seems to alternate between Staff View under the Control Bar and then Console under the Control Bar. This was not what I expected. It is almost as if the UI creation project doesn't do the same thing every time--not based on the project file or the "None" Workspace, but either randomly or based on something else we don't know about. I am still not sure I have re-created the same steps you used, but to me it seems I have re-created a possible anomaly that is similar to yours--namely, that the project UI construction is doing its thing in such a way as to violate user expectations. Just a guess on my part. UPDATE: At least in my case it could be that saving a project with the Staff View showing causes a problem for Cakewalk (not sure). I have gotten "not responding" several times when saving and loading with the Staff View showing, but not with the Console showing. I have also gotten the sluggishness when the project UI reconstruction sets up the Staff View. Once it decided not to open with the Staff View, it opened to the Console View and 3 times thereafter had no trouble opening up to the Console View. FWIW, I have tested saving a temporary Workspace instead of using "None" to preserve the last state UI configuration for a specific project. IIRC it seemed to work as long as I remembered to resave the Workspace. Not sure if the results I got come from my PC (I don't have a non-MoBo graphics card), if my results relate to your result, or if others have similar issues when closing and reopening projects that have the Staff View showing when closed. I hope this helps others to sort it out.

I have played around with different designs for my Workspaces that use primarily the staff view. So, this caught my eye. I haven't tried it yet, but I am wondering if there are reasons why you use the "None" Workspace and not a custom one of your own design. Also, I am wondering what happens when you save your preferred state as a Workspace. Do you get the same problem? Just wondering as I have a number of Staff View oriented Workspaces myself.

Newcomers to Cakewalk don't have all the plug-ins and other content that came with the paid versions; no need to feel bad or guilty (in my opinion).

I am not a legal expect, and I faced a situation years ago where from an EULA it was unclear to me if I could use material commercially for my own music. I wrote the vendor, pointed out relevant sections and asked a very specific plain-English question ("Does this mean I can or can't . . . ?") I got a very nice reply explaining that yes I could . . . . I looked at this terms you link because I was curious. There are other sentences where it seems that using the Assets is only OK for electronic applications/digital media. ? There is also this: To me I think the legalese is trying here to make a statement about the Assets themselves [as Assets] as opposed to original music which uses the Assets. With live and recorded performances that are non-digital, there is no need to distribute/transfer the Assets themselves. The quote you use refers to "a non-exclusive, worldwide, and perpetual license to the Asset to integrate it only . . . ." To me (not a lawyer) "a license to the Asset to integrate it" is less clear. But I would hope that "integrating" an Asset refers to distributing the Asset as an Asset. If I were planning to use the product for any purpose, I would ask about this. (Like many people, I detest legalese. Its EULAs like this that inspire my reaction.) EDIT: I think the difference between (1) using the product and (2) distributing/transferring the digital Assets as Assets is warranted by this: In other words, permission is explicitly granted to use the Asset per Section 2.4 of the Agreement [after the Terms]. However, people who agree to using the Assets seem to be agreeing to corporate censorship: To me, by implication people who have purchased a license to use the Product and its Assets are allowed to use it in any non-explicitly "prohibited" ways without violating the agreement. DISCLAIMER: I am not a lawyer or any sort of legal "expert" and I have a strong bias against legalese. Needless to say, if you write to the company and they say you can only use the product for digital/electronic media (i.e., not for performances and non-digital/electronic media), that overrides my opinion.

You posted the website, not the app. See link immediately above.

From my browser's url bar, I copied and will now post the link directly as opposed to using a hyperlink: This is the hyperlink method.

I never pay attention to tooltips and I only have the English version; however, I gave this a try hovering first over the Inspector pane and then in the track header pane. My tooltips showed correctly. By any chance do you have your monitor or windows to display at a size other than 100%? I just tried my display at 150% and tooltips still showed up properly.

I don't use the PRV and I don't zoom via mousewheel and mousewheel + Alt, but FWIW here are my results from playing around a few hours ago: Respectively, these are 0, 1, 2, and 3 single mousewheel + alt clicks. At least on my PC the scaling is not linear. I do not use this and have no idea what Windows, mouse driver, or Cakewalk settings impact the relationships between the zoom and the PRV. I did notice that with the mousewheel + alt clicks, the zoom widget also showed more of a change from 0 to 1 than for later clicks. Maybe this will help?

Update [2020-05-05]: The short answer: "Track Pane." @Jim FogleI stumbled onto that mini track header pane a few months ago and have found it handy to have in some UI configurations. I just thought of it as a mini track header pane but maybe someone knows the official name. I seem to recall I found it in the multi dock; not 100% sure. EDIT: Evidently I found it useful (among other places) in some of my staff entry workspaces so I didn't need a large track pane. ADDENDUM: When my main view is in full screen and the multidock is undocked also as a full screen, "D" is a quick toggle between the two. I think the following shows why I started calling it a mini track header pane. Maybe @Colin Nicholls has the official name in his theme guide? FOUND IT: In the current theme guide, its in Section 5.1 "Track View | Track Pane." Looks like it could be called a "mini track strip."

I stand corrected.

I took it to mean that (1) you can use Workspaces to configure different UI arrangements and (2) then switch Workspaces as needed so that (3) the Workspaces can serve the same purpose as Screensets (and a whole lot more!!!). With this approach, it is as if you have Screensets that change the UI in predictable ways on a global basis--that is, for many projects.

Opening a *.mid file also yields separate midi tracks. I'm sticking with my old school methods since they work for me. Sorry I asked about Tezza's workflow and tried to implement James Argo's suggestion. Must be my aged computer and my aged brain. ?

This is what I started to write up yesterday but I didn't want to go into the possible need to switch Workspaces if the OP was using Basic and therefore didn't have the Event List View.

This is way too complicated. I will stick to my old school work flows because evidently there is no way I can drag and drop my old *.mid files without Cakewalk opening up individual midi tracks (see image above). Everybody else seems to avoid using midi tracks, but when I try the new-fangled methods, they make more work.

EDIT: Originally I thought this was related to the original problem, but in retrospect, it is more of a distraction. Withdrawn, but left in as there are posts that reference this. I tried a number of options, including the ones below. Drop & Drag method - yes Not a simple instrument track - yes Midi Source - yes Fisrt Synth Audio Output - yes Drag the MIDI File into the empty midi track (I tried both track panes.) - yes I keep getting all of the original MIDI tracks. The MIDI data disappears when I delete the MIDI tracks. Have I missed a step to get this all-in-one method to work?

Whoa!!! I have been impressed with the power (and potential) of Workspaces; but they really are "All Powerful." Thanks for explaining how they can even affect what shows up in the Preferences dialog system.

Is this an attempt to explain what Starship Krupa meant by "in Preferences?" Or is this an attempt to tell Starship Krupa how to use Workspaces? So far as I have seen, while we can "hide" many things, I am not sure we can hide things from Preferences. For example, in the following I have hidden Modules so they are not available to be shown in the Control Bar. I have used Workspaces that have all sorts of different personal preferences--meters, UI, Views, keyboard shortcuts, etc. However, I cannot figure out how to make things that appear in the Preferences dialogs not show up in Preferences. The online documentation states, "Cakewalk includes several factory Workspaces to get you started, and you can create your own custom Workspaces based on your personal preferences." [emphasis added] "Preferences" [the Preferences dialog system] <> "preferences" [personal workflow choices.

"in Preferences" = ????? I have just scratched the surface of Workspaces, but I haven't stumbled onto a method of hiding things from Preferences. I know we can "hide" functions that are normally accessed via the Control Bar, Views, the UI, keyboard shortcuts, etc. I am trying to imagine what can be hidden from Preferences.

EDIT: Originally I thought this was related to the original problem, but in retrospect, it is more of a distraction. Withdrawn, but left in as there are posts that reference this. I am trying to understand how this workflow is supposed to work. Here's what I did: Open Cakewalk. Open New / Empty Project. Insert Soft Synth as an Instrument Track. [I used TTS-1 to test.] Drop *.mid file onto Instrument Track. [I used an old project from 1999 which had been saved as a multi-track *.mid file.] Delete all MIDI Tracks. When I did step 5, all of the midi data from all of the tracks other than the first one disappeared and did not play. I tried using the "Make Instrument Track" command in several different ways without success.

Wait a sec? Can't it be undocked? I don't know; I almost never use the PRV. If it can be floated, maybe it can be saved at a preferred size and location in a workspace? I set up a full-sized Console that opens on my second monitor. Seems to me maybe something similar could be done with an undocked PRV. Not sure, though. I will give it a try this evening because it will teach me more about workspaces. If you want it on a per-project basis, have you tried saving the UI as a screenset? Again, I haven't tested this because I rarely use screensets any more. Withdrawn; see below.