User 905133

Some people might use it. I agree as was discussed in another thread there should be an OPTION not to show MIDI tracks, but for some users not having the ability to show MIDI tracks in the console would be problem.

Since Creative Labs seems to have had zero interest in doing anything with the Emulator X3 for many years, perhaps Bandlab could get the intellectual property for a bargain basement price (as I have suggested before). It is extremely efficient and runs very well as a standalone and as a plug-in within Cakewalk. Very low CPU usage in my experience with dynamically-assigned polyphony (notes don't cut-out with preset changes, etc.) with efficient multiple output ports . (I gave up on Independence.)

Thanks for the confirmation.

I just tried the Track Options tab > t > p as noted above. Next to having a single keyboard shortcut or a macro or software that sequences keystrokes, Options tab > t > p seems quite efficient to me. No need to set up screensets or re-juggle floating windows. Options tab > t > h and Options tab > t > v also work for horizontal and vertical meters respectively. All the floating windows stay where they were. Just so there's a smaller chance of misunderstanding (which is always possible): we all have our own workflows, preferences, personal efficiencies, etc. What's personally efficient for one person might not be as efficient for another person.

IMO Windows 10 is notorious for changing settings, but for me the recent updates haven't changed as much as a few years ago. Overnight (after about 16 hours) my Win 10 1909 updated to 2004. I found some things changed and some things didn't. My guess is that what gets changed with the newest Win 10 update can be very different for each of us. In my experience, automatic rollbacks after failed updates did not restore all my previous settings. So, I often had to redo my audio tweaks--including my sound settings (preferred devices, etc.). If you used some of the handy audio tweak guides available at different sites, you MIGHT want to revisit those and redo the same tweaks you've done previously before doing the Windows 10 version rollback. Caveat: I have no professional experience in this area, just several years of having to redo what Windows 10 has undone (much like many Cakewalk users, I suspect). BTW, this time I did have to re-enter my password for several third-party synths. Fortunately, I have not yet had to re-adjust my sound device settings or the Windows Sound settings. Also, I did not have to reinstall my HDD extended partition software as I have had to do on some previous Win 10 updates.

Question: If you (1) set up Screenshots 1, 2, and 3 (with horizontal meters, vertical meters, and no playback meters, respectively), (2) use floating/undocked windows, and then (3) move around and resize windows when you are in Screenshot 1 (for example), when you switch to Screenshot 2 and/or 3 do the previously saved positions and sizes revert to the way those Screenshots were saved, or do they inherit the locations and sizes from Screenshot 1? When I last tried it (a few days ago), the Control Bar's position and size persisted, but the floating/undocked windows reverted to the previously last used sizes and locations. I know from experience the way my PC works is different from what others experience. Not sure if there is a setting that would affect this on different PCs, if it depends on graphics chips, etc. UPDATE: To make sure this didn't change (Win 10 v. 2004 update finished approx . 3-4 hours ago), I retested. As before the update on my PC, after being moved/resized the Control Bar's location/size persisted through different screen sets but the various floating/undocked windows didn't. Also, in duplicating a screenset, the floating Inspector window disappeared each time and had to be re-opened for the benefit of the new screenset. As with other things, I assume that not everyone's Cakewalk will exhibit these properties. As we all know, what works for one person (and I don't mean just in terms of workflow/preferences) won't necessarily work on someone else's PC.

I seem to recall seeing this issue (or a similar one). I might be misremembering, though. What version (including build) are you using? I will look for the post I am remembering.** Edit: **Still looking. Maybe this is what I was remembering? I didn't find any public follow-up discussion on this. Not sure if the cause hasn't been pinpointed yet, or if there has been a solution. Others might know.

I am usually more subtle, less confrontive, but if you look at this: I hope you will see that I posted it with "not-unreasonable" well before you decided to call attention to my typos in the later posts. Please note: I still don't feel like these irrelevant issues are worth debating. For me it is a distraction from a legitimate question/concern about having a keyboard shortcut for meters and I would hate to see this thread closed. Peace.

Sorry to disappoint you, @John, but I had deleted the post and fixed a number of typos (probably not all of them) BEFORE I saw your reply. I disagree with your assessment of my post, but don't feel like it is worth wasting my time, your time, or anybody else's time debating. Suffice it to say that on my PC, the Shift+F7 shortcut under discussion not only didn't toggle the meters, but it didn't do diddly-squat with the meter options dialog as you seem to have suggested. Just to fill others in on the "facts/alternative facts" non-controversy (in other words, I hope this doesn't inspired more barbs), I had laid out a sort-of parallel example with a Drag and Drop Options keyboard shortcut. In so doing I presented several images as "facts" (FACT # 1, FACT # 2, etc.) because I thought that "premise" was too esoteric and I didn't want to be accused of being pedantic again. So, at the end of the post, I threw in what I intended as a joke about facts and alternative facts. The statement was punctuated with an icon that to me was intended to ridicule what I think is an absurd idea ("alternative facts"). It was in part a reference to the images I had posted in the beginning (a) from the reference guide, (b) from [P] references > Keyboard shortcuts, and (c) from Track View > Options presented as facts (really, they were premises, but that's three words syllables ? !!!). Now, you see that icon? To me, I intended that to convey a reflexive irony joke kind of meaning. However, icons (just like language itself) can be interpreted (and misinterpreted) in different ways. For example, someone else might see that icon and thought I was being disrespectful--kind of like I was sticking out my tongue in defiance. (I don't know if that's the case here). Peace! Yup: reasonable = not unreasonable = it would not be unreasonable--as if to say: I can understand how someone would see this when setting up a shortcut and conclude that the shortcut would "Reset All Meters" as opposed to do something else. TY for helping to make the clarification.

oops

I guess we disagree on what is reasonable and what is not-unreasonable with regard to what that dialog is supposed to do. ?

Suppose you split the instrument track into midi and audio (and just choose to show audio strips in the Console)? Would that work around meet your needs?

This would not be the first time my computer performs differently than what other people in the forum describe. By unchecking one Workspace option, I just tweaked what would normally be the Advanced Workspace in such a way that I do not have the Screen Sets Module on the Control Bar nor do I seem to have any of the access points to change screensets (Menu, Shortcuts, etc.). Oh well. Sorry for any confusion I might have caused.

(1) The last time I looked it was possible to disable Screensets, though that might have changed. (2) The times that I used floating windows (aka undocked windows), I used them so I could move things around. Correct me if I am wrong, but if I (a) set up a screenset with playback meters, (b) duplicate that to a different screenset, and then (c) hide the meters in one of them, the toggle doesn't work if I move or resize one or more floating windows. I just tried this (a couple of times) and while the Control Bar persisted (location and length) between screenset toggling, some of the floating windows return to the original size and position when switched using a different screenset. Thus, if someone has floating/undocked windows that are moved/resized/etc. the toggling between screensets doesn't work as desired. (Yes, it works in terms of capability, but not as in terms of the preference that a shortcut key would provide so far as I can tell from a few tests just now.)

Sometimes I like to make a distinction between capability and preference. Not sure if this is of concern to the OP here, but it could be. For example, I took the following to be about a preference: Yet, another reading of it could be about capability. With the Shift+F7 shortcut attempt, I think it is not-unreasonable to conclude that assigning a shortcut should work.

Cool! I can't remember when I last use screensets (before tonight, that is). I have tended to set preferences up globally via Workspaces and even took screetsets out of a number of my personal Workspaces. But you are are right! They seem to provide a workaround for this issue. Also, I had totally forgotten, but evidently in my blank project template, I have some screensets with horizontal track view meters and some with vertical track view meters. So, thanks for the tip to check for non-global solutions and for the reminder about some of the benefits of screensets. BTW, I can see that with constantly changing floating windows when working on a project, someone might have to be constantly saving two screensets (with and without meters) since they evidently cannot be switched with either a keyboard shortcut or even a button in the Custom Module in the Control Bar (so far as I can tell).

By device preferences in the above statement, are you referring to ASIO4ALL's Control Panel? Also, does it make a difference if you turn the devices you are not using off in ASIO4ALL's Control Panel itself? When I used to use ASIO4ALL, sometimes turning off I/O ports on a device in the CP solved some ASIO4ALL audio port management issues. No guarantee, but if you haven't tried it, it might be worth testing (assuming your preferred device doesn't have a manufacturer's device driver).

One set of options I tried yesterday was Workspaces.** If you know how to save one Workspace with the playback meters showing and an identical Workspace with the playback meters hidden, please share the details on how to do it.**** (Please note: I am not asking for a "Read the Manual" style reply.) I have designed a number of personal/custom Workspaces but couldn't make the show/hide meters happen via Workspaces. I can do quite a number of other things with Workspaces, though. In fact, I vaguely remember that at one point I could use Workspaces to have different meter settings but later on, they didn't happen as they had previously. When I have a chance, I will try to revisit those Workspaces. There may even be some posts and discussions about this. ****Not sure if you tried yourself or just replied as above.

I tried binding Shift+F7 to the playback meter display option (toggle on/off). It didn't work on my PC either. I tried a few other things; none of them worked.

Sorry to hear, but thanks for confirming this. It seems unlikely I will ever be able to get back whatever I had at one point that let me do polyphonic audio to midi conversion within SONAR/Cakewalk. Oh well. ?

Strictly voluntary link put here with the intention of providing a link to the above referenced "the deal came up on another . . . thread." Just to be clear, I would hope this is understood by all as well-intentioned and a positive contribution to this thread since Peter - IK Multimedia elaborated on the method of obtaining the $50 discount and listed some other insights regarding the deal. And just to be clear, I don't think any of the prior contributors to this thread is stupid or anything negative.

Thanks for raising these points. I have some interfaces capable of multiple outputs (routed to multiple speakers) and have done some brief tests routing audio to multiple speakers (greater than two), but not individual multi-(greater than two)-channel software FX processors/plug-ins.

This ^^^^. One of my legacy soft samplers allows users to set up the plug-in to have up to 19 output channels. Cakewalk's insertion methods support them all, though I don't generally use more than 16.

I can relate to using a "legacy" PC to support a "legacy" interface. My E-Mu 1820m Audio Dock + PCI Card + Sync daughter card continue to work well under XP SP3, although I have both midi and audio connected to a Win 10 PC. SONAR X1 Producer Expanded still works, too. An Ultra Sampler with an RFX-32 Module connected via ADAT also works. JMO: Long Live Legacy Gear--even if the manufacturers have toss their user base to the wind!

If you get the theme compatibility dialog that says it needs to be updated, click on the link. Here ya go.