User 905133

Thanks for the insights. After trying a few non-logical elements, including many that >>might<< have a side effect, I'd say your gut feeling is correct. I also tried some optical illusion like effects to make the distinction more noticeable. The best I could do (and it is not really helpful) was making the name frame the same shade of gray as the selected synth rack strip in the hope that the unselected one would "seem wrong."

I was curious about this and since I enjoy learning about custom tweaks, I looked last night. Unfortunately, I didn't see any color elements or images taht would work for this; however, I was only looking at element names that seemed logical to try. Not sure if there are elements for other things that also affect the selected / unselected Synth Rack list. I will probably try again, though.

I was confused by this, too. According to the default Key-bindings, ALT+X toggles Aim Assist on/off. When I tested it (with ALT+X), the state of Aim Assist did not seem to get saved and restored via specific Workspaces. (I don't think the reference is to Key-bindings, because those can be saved with Workspaces.) I never use it (except when I see it referenced in the forum so I can teach myself about it), but just now it [the on/off status] did seem to persist regardless of Workspace or project. I think if I were to use Aim Assist, I'd like it on all the time unless I explicitly toggled it off via Alt-X, but I can understand how others might want a whole bunch of settings (including Aim Assist on/off) set up by personal Workspaces. If this is not what the comment refers to, I'll go with any forthcoming clarification. See

I think what you call "preferred Workspace in Track View (e.g. mix, i/o, fx)" is what I call "Track Control/Widget Preset" -- the set of track control widgets in effect when the Workspaced is saved, if that is chosen to be saved/restored. As far as I have seen when it says [Workspace], the widgets are the ones saved with the Workspace. I'm guessing you want it to say the specific name of the preset and not "[Workspace]." Intuitively, I seem to like knowing that the widgets are already set in the Workspace so I don't have to re-save it. Also, the way it currently is, if I temporarily change the widget preset, I know that the correct one is still stored with the Workspace because it doesn't say "[Workspace]." Also, based on what I just tested, it seems that when my Workspace is set to "None," opening up an existing project does display the widgets [i.e., track control preset] the project was saved with. Not 100% sure on all this as I am still learning the nuances of Workspaces, so I am open to corrections from those who have more experience with Workspaces and track controls.

I de-selected all my midi devices and got the same thing. Then I re-selected a midi output device.

Do you use customized Workspaces? I ask because with my personal dual monitor based Workspaces, I haven't noticed inconsistencies such as you describe. I know that "None" is often used as an option to preserve UI arrangements from session to session and often I use that. However, at times I just want to use a specific Workspace--including the one where I have a full-screen, undocked console on Monitor 2. UPDATE: I just went through my Workspaces and they seem consistent, though I did read that with 2020.05 there were some changes. That being said, the ones I have set up to put up a full-screen undocked Console View on Monitor seem to work as they did before. Also, I created a new "Undocked Test" that has three undocked panes on Monitor 2 and tested by opening up different projects. That also seems consistent from project to project.

I agree. Another benefit--I find the buttons on the bottom are great for making sure Windows audio settings Cakewalk's audio routing are working (very quick built-in diagnostic tool). If you haven't see it, there is an extensive midi implementation document available from the Help button.

At one point I had that, too (the grayed out options). Someone posted about that. I will look for the link. Did this help? UPDATE: I just tested scooks' advice, and it still works using these two steps. (I am using 2020.05 Build 039.)

Yeah--none of my parallel port MOTU midi interfaces (8 x 8s and 4 x 6s) work under Windows 10 Pro** no matter how much I try to trick them into working. Even MOTU tech support couldn't help and I have no experience in writing device drivers (nor do I have enough of a hacker mind left to try to teach myself how). **They do work on a bona fide XP SP3. Based on my experience, having multiple devices from the same manufacturer can be problematic (e.g., triggering BSODs). So far as I can tell the E-Mu device drivers identify each of the two pairs of I/Os on a single 2 x 2. I am not sure if its the E-Mu driver or Windows (or something else) which differentiates one 2 x 2 from others. To try to re-stablize them one time after a Windows 10 update which I believe was responsible for some BSODs, I disconnected them, removed the drivers (including hidden instances of the drivers), reconnected them one by one, and power cycled my PC to try to ensure that Windows 10 set up them up properly in whatever tables it makes. Unfortunately, as you can see, somehow the ports on one 2 x 2 now have the same names as a different 2 x 2. I don't dare hook up the 4th one!!!! ? You raise an interesting point--by implication: if I disconnect all the 2 x 2s (i.e., just have the nanoKontrol and the MK-249C, will I then need to exit and reboot Cakewalk when I power-cycle the MK-249C (or any other usb keyboard). I'll put that on my to-do list to test the next time I start getting a rash of BSODs and do another clean installation of the 2 x 2 drivers.

Footnote: Try using Shift in the Markers pane to select a range of markers and Ctrl to select non-contiguous markers. It works on my PC; might work for others, too.

I can't answer your questions, but thanks for raising them! I always have the SynthRack docked on the right, but now that I see what you have here it looks like something that would work very well with some of my workflows. This is new to me but so far as I can see, we are limited to two rows of virtual knobs.

EDIT: In case it was not clear, this classic from the history of mid-20th century electronic music was made with the sound of rubber bands (tie in with the previous song) and uses early techniques of tape editing that helped pave the way for current digital methods.

I don't doubt that we are getting different results. I like consistency, so I share in the frustrations. Unfortunately, there are too many variables for mere users like me to factor out the variables that make a difference. I just tested with two different projects I had. I did not reset any Cakewalk configuration files (which I did do when I was trying to get two PCI audio cards to reside in my PCI at the same time). Not sure if this accounts for my results, but (1) I have two usb midi controllers that are always connected and always on (that is, when I boot Windows 10 Pro and when I shut down my PC every night) and (2) presently I have an older evolution keyboard (MK-249C), a nanoKontrol, and several 2x2 midi interfaces connected. I believe I do not have any virtual midi port software set to boot with Windows at startup. For years I had Tobias Erichsen's rtpMIDI set to start, but IIRC I turned off the startup service for that about a month ago. I still have ChucK software on my PC. though it doesn't run unless I specifically call it. I haven't run it in ages, except to check my system using the chuck --probe command. (For a stretch of time I used ChucK as an on-the-fly quick change midi I/O router.) For what its worth, here are the midi devices Windows 10 reports via ChucK's --probe command (a) when the keyboard is powered on and (b) after I turn the power switch off. (a) (b) After turning the MK_249C back on, --probe reported the devices with the same indexes as in (a). I know from working on ChucK scripts under XP with a parallel port MIDI interface (among other devices), booting MIDI devices after XP had started changed the indexes as compared with powering up the PC with all MIDI devices power up. Again, not negating anyone else's experiences. I have spelled this out on the admittedly slim chance that something here might account for why I don't have to reboot Cakewalk to get it to see my MK-249C after I switch it back on.

I didn't realize there were limitations to the friendly names. What can't we do?

I don't know the answer, but I do remember a thread that >>might<< be related.

I was curious about this, so I started testing what happens with Cakewalk on my PC when I turn off the power switch on my usb midi keyboard. So far I have only tested this 2-3 times with a single project, but the issue seems consistent and problematic. I will probably retest a few more times, but it seems that: answering "No" at the "keep the setting" disconnected device detected dialog does not require rebooting Cakewalk once the device was turned back on--though it had to be unselected in Preferences > MIDI Devices (and applied) and then reselected (and applied). answering "Yes" at the "keep the setting" disconnected device detected setting did require rebooting Cakewalk once the device was turned back on because it was removed from Preferences > MIDI Devices. Note: I am not disagreeing that there is a problem that needs to be resolved. At least on my PC, in the first condition (above) I found it problematic that when I switched the power to the usb midi keyboard back on and then said "Yes" to add it now, I had to go into Preferences > MIDI Devices and then disable and re-enable the device before the keyboard saw the incoming MIDI data. UPDATE: After testing condition 1 several more times, I found the results were inconsistent. Sometimes I had to unselect and then reselect the controller before it would register keypresses; sometimes I didn't have to do that. Also, a few times I played notes after switching they keyboard back on but before the "Do you want to add . . . " dialog and the keyboard notes played the softsynth. In all cases I did not have to restart Cakewalk after I had said "No" when I had switched off the keyboard controller.

Hmmmmm. Now you have me thinking of possibilities--triggered pop-up notes as track-embedded reminders?????? Oh--I did see the other day that evidently there is some sort of patch switching capabilities; not sure how I stumbled onto that--maybe the midi settings.

My first inclination was to just do the math and enter the values in the Event List as you suggest. I will have to see how that goes.

Thanks for the clarification. I tried it with the new steps added, but the "smart tool" has a mind of its own. Maybe I will try septuplets in the staff view. I accept that many people find the PRV better, easier, more flexible, etc. I have no problem with that. Its just counter-intuitive for me and doesn't me save any time. I am sure I will try again over the years. Maybe there is a step that PRV users do automatically that I don't do but might stumble on one of these years. Again, thank for adding the additional steps.

Thanks for summarizing this. As an avid note taker, I tend to use the Notes scratchpad (usually docked on the right, though I know it can be floated, put into the multi-dock, etc.). I am aware of (and have tested) Track Lanes Notes scratch pad and the Inspector Description field but have yet to integrate them into my workflow. For audio tapes (family oral history tapes), I have extensively used Markers as very specific notes (content, possible ideas for editing and clean-up, etc.).* I have not used the Lyrics Track in over a decade. I do have MNotepad (a licensed version), but haven't integrated that into my workflow yet. *Oh--I believe it was scook who posted a link to a utility for pulling out markers into a csv file. I tested importing a set of markers into an *.ods file but haven't made regular use of it. PS: Thanks for mentioning MNotepad!! I only tested it once before but took another look at it just now. It looks handy. I see it has 2 ins and 2 outs; will have to read the manual!!!

As you might remember, I generally don't use the PRV. So, I am trying this to teach myself how to use it. (TY for the steps!) I get to the point where I use the select tool to highlight the seven notes I created; however, I do not know how to change the duration of the entire selection. I have tried several times, but I am am not getting it. Can you spell out the individual steps for "change the duration of the entire selection?" Here's what I have done as a test: (1) . . . create seven notes . . . (2) . . . select all seven notes. It seems at that point I have to switch to the Move tool, because none of the other tools seem to do anything useful. (3) . . . while holding CTRL, I put the mouse cursor on the last note and dragged it so that the notes all shift to fit a smaller space: Thanks for any suggestions.

[removed]

There are a number of options in Cakewalk for saving the size and position of windows. We all have different preferences and opinions based on our workflows. Some options I use: (1) maximize/dock floating windows [or un-collapse, depending on the window] and save the project, (2) save a screenset to slot 1 [or another one], and (3) use workspaces [Note: "None" as a Workspace should restore your UI to the last used configuration. Also, Screensets work on a per project basis; Workspaces work globally--from project-to-project]. (1) (2) (3) Assuming your file is a Cakewalk file (e.g., *.cwp), probably the easiest to to maximize (image 1 above) the floating window and resave it. If it is a *.mid file (as in your example), you can maximize it and save it as a Cakewalk (*.cwp) file. If you are doing this regularly with midi files (e.g., *.mid) you might want to use a workspace (image 3 above) that has a non-floating track view window. [For example, I just tested opening *.mid files with a custom Workspace and with the Advanced Workspace. Both allowed me top open midi files into a non-floating track view window automatically.] This way you won't have to re-save each file as a Cakewalk file. I am sure there are other methods; these are just some I would use as a plain old user. I hope they help.

[removed]