User 905133

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.

Thank you for the recent updating of the Cakewalk Reference Guide (to 2020.04).

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.

No, but I did take a very brief look at some of the code to see how open it was.

Found them!

Thanks for mentioning this. I went to 5 or 6 sections and tried them in my web browser, but didn't see a Task app. I will be sure to look for it, though.

Since Citizen DJ has been made available for review & feedback, why not make positive suggestions so maybe when it is launched it will be better? (As of right now, I would agree with anyone who claims it is seriously underdeveloped in content and form.)

I seem to remember trying to do this (without success) a few months ago when I was teaching myself workspaces. IIRC the most I was able to do was create a customized floating Control Bar, have it sized to just show a few modules, and then have it in recalled via a workspace. Not ideal to have to switch workspaces, but if it cannot be done any other way, it might be worth trying. EDIT:

Are you talking about the old plug-in layouts? If so, I think they still work; however with CbB there is an option to create categories for plug-ins. I stumbled onto this last week when I was going through my plug-ins. I ended up with several categories for bad plug-ins. Very helpful feature, IMO. Not sure this is what you are describing, but maybe it overlaps with what you have in mind.

For me, I envisioned this as being an option, not mandatory and not a default behavior--kind of like: select, right-click, choose color. I thought it was obvious, but maybe it wasn't; so, thanks for calling attention to this omission. In fact, even Mr. Torture referred to it as an "added feature"--which I infer meant optional, not mandatory nor default. There are plenty of people who post in this forum that think their methods are the best and everyone else should be doing it their way; so, it makes sense that you would want it left alone. As for editing verbal/vocal artifacts, I had in mind using different colors/shades for different classes of things--for example, "ums," "ers," "whe--whens", "he-errr-we," false starts, unneeded details, etc. If it doesn't work for hissing esses, plosive pops, etc., that's fine with me.

Thanks for confirming this. Just to let you know, the first two pictures were done with different zoom amounts while in the third one the left track was hand-colored using MS-Paint. They are from a project which involves marking and editing oral history tapes. Having a color picker for fills so different waveform sections could be colorized would be great for marking up tracks--easy to see and would augment the use of text-based markers.

I like to try tips from other users to learn possible techniques so I tried this (Ctrl+Tab). On my specific PC here's what I learned so far: Ctrl+Tab seems to do nothing when I have things docked in a single window (main view). When I undock [float] the Console, Ctrl+Tab switches my PC's focus between the main view [all-in-one view] and the console. When I undock [float] something else (I used the browser). Ctrl+Tab seems to toggle between the most recent two floating views. When I switch to my Web Browser, Ctrl+Tab rotates through browser tabs. When I bind Ctrl+Tab to "Next Tab," Cakewalk allows me to rotate through tabs in the multidock. That's as far as I got, but I have found the key combo (which I almost never used before) to be quite handy--so thanks to DocBob for raising the issue and for others who chimed in, esp. noynekker whose explanation got me exploring in greater detail than a simple test. As for me, for my workspaces that have an undocked console on my second monitor, I will probably use the default key binding (unassigned) so I can toggle between the main view and the console view. For my workspaces where I tend to have multiple tabs in the multidock, I will probably bind it to "Next Tab." Like many others, for keyboarding I tend to use a right-hand mouse + left-hand keyboard shortcut technique and overloading the Ctrl+Tab combo depending on workflow context/workspace fits in with this. So, thanks to all for helping me to discover this!

"Millions of cases, small amount of death. Millions of cases, small amount of death."

Unless I am mistaken, Mr. Torture is asking for the space between the amplitude and zero to be filled in--maybe.

From teaching myself workspaces, I have made use of both. However, I have made some workspaces that intentionally have no screensets. In other workspaces, I have screensets enabled. When enabled, the screensets come from the project. That is, screensets that have been saved in a project can be used (or not used) depending on the workspace. I probably understand how to use them more than some users, but much less than others. So, I will let others explain it further. Just wanted to say they are not mutually exclusive from what I have seen. PS: I recently discovered a problem on my PC that seems to be related to some plug-ins which use OpenGL routines that I don't have. As a result, it interferes with screensets under certain conditions. I am pretty sure this is related to my specific PC, but wanted to mention it because your description is vaguely similar.

I don't use templates--other than base project templates from which I derive variants of specific projects. I am used to adding soft synths one by one as needed. So, I can just continue to add the midi tracks as needed. It would be easier to just add 16 separate midi tracks (or however many I need) all at once as the soft synths are added. I did create a massive template for about 6 to 8 sound modules, each with 32 midi channels, but I found it was quite cumbersome to use and it is easier to just add midi tracks as needed. Was just thinking it would be nice to have in the wizard. Having the wizard automatically create 16 instrument tracks (for example) with only one midi track probably works for different workflows. I will look into changing my workflow. Thanks for the suggestion.