GreenLight

How it avoided TFS? It's because of us! This forum is at least 20-40% more helpful than most forums! (I don't even remember the origin of that joke anymore... ?)

Empty track-subfolders cannot be moved, they are always "stuck" at the bottom of the parent folder (below all the tracks). You can "grab" them with the mouse, but they won't move when you release the button. Is this by design or a bug? I kind of expect subfolders to be movable, even if they are empty. Sorry if it's the wrong thread, I just ran into this with the latest build and thought it might be new?

These new bindable actions are absolutely brilliant for a fast workflow! Thank you! ❤️ Now if you could also make Archive Track [Track View] and Transform Tool [PRV] bindable for shortcuts, we would be scarily close to keyboard nirvana... ?? And while I'm brainstorming: it would be logical to have a single action for Archive/Unarchive Track and also combine existing actions like Freeze/Unfreeze Synth. It's like we have a single light switches in our homes, not separate on/off buttons.

So there is no way of moving or making a track selection (when a track's number is highlighted) with the keyboard? ? This would be so very useful! Maybe a new setting "Track selection changes with up/down arrow"? ?

Hm, yeah that sounds pretty weird... I have never had that issue myself. And I do not own any of Spitfire's custom VST instruments.. unfortunately. I think you should email support@cakewalk.com and tell them all the details and ask what they think. And also, if you have the time, email Spitfire as well and get them to talk to each other. Noel/Cakewalk is very forthcoming with these things.

If you right click, can you select Freeze from there instead?

Has the auto-save feature gone bonkers? I assume you have tried turning it off? (I saw your other thread, weird stuff!)

A visual indicator for this is actually a great idea! ? I don't know how many threads and questions that have been created about this in the forum... It certainly feels like a bug if you don't know what it is and activate it by mistake.

Brilliant! I'll have to wait testing the EA after an upcoming deadline, but these will be great for a fast workflow! ? Thanks for listening to us (pinging for example @Rogério! ) who've requested these. ❤️

This is great news, thank you so much for listening! ? ...and sorry for all the whining, it must be a bit hard to sit through... ?

The location actually resets for me during a session as well, without me changing any options in the Export window... it's a bit annoying. I'm smelling a bug here somewhere, I just need to figure it out. ?

Hey all! Using the built-in Mercury theme, I often find that the active automation envelope is too hard to see, it's so thin and it's often in a color that blends in too well with the background. Some releases ago, the automation curves in Cakewalk were made thinner, a change that absolutely improved visual clarity overall in a good way. Do I remember wrongly, or was a setting introduced to re-enable the "fat" envelopes? To be a little picky, I don't really want them all to be thick again, just the active one... ? Thanks for any insights!

Thanks for 2021.12, it's great! I have a few thoughts about the new Export Audio additions: The added keyboard navigation support in the Export Audio dialog is great! But could you make it so that pressing Enter would equal pressing Export? This was how it worked in the previous dialog, and it reduces mouse clicks. (The Space key could be used instead of Enter for toggling checkboxes, etc. This is actually how it works in Windows 10 Settings dialogs.) The Location box does not allow any typing, nor copy & paste. It would be nice if this worked. Even less mouse clicking! The Location box value has to be changed every time... it would be so amazingly convenient if it remembered the previous export location, on a per-project basis. A Clear Queue button would be very convenient. Keep up the great work!

Hm, so it's the stretching that degrades the audio quality? Do you have access to any version of Melodyne, to see if stretching with that would give better results? Also another random thought: if the realtime playback sounds good, maybe you could try recording that (in realtime) to another track (maybe using a Patch Point)? Kind of tricking the system... And oh, welcome to the forum!

I actually tried with hidden archived tracks as well, but they still caused problems with the last Alt+S in the same way... weird that it doesn't cause issues for you. ? But this means that you can confirm that the workaround doesn't work if you have (not hidden) Archived tracks in a project?

Hi @Rogério! Since your workaround involves automating keystrokes (Ctrl+A, Alt+S, Alt+S plus an additional Ctrl+Shift+A), you should run into problems with the second Alt+S if you have tracks with Archive status in your project. (I attached a video of the problem, reproduced in a blank project, see a couple of posts above.) Could you please confirm if Archived tracks cause issues for your workaround as well? Thanks a lot! ?

Hehe, I am not sure that we really follow each other's reasoning... ? With the video above I only wanted to explain that if you have archived tracks in your project, they prevent you from using the suggested workaround for "unsolo all" (pressing ALT+A, ALT+S, ALT+S). Even hidden archived tracks seem to prevent it. We need a proper keyboard bindable "unsolo all" function. ?

Absolutely, that is exactly what I have set for ALT + S. ? Can you reproduce this bug? If I Archive a track, I can no longer unsolo it with ALT+A, ALT+S, ALT+S. See video below: first it works, but then with an Archived track, it doesn't work.

Thanks for chiming in @msmcleod! ? A few things to note about this: This workaround obviously works, but is not that convenient for an action that is done so extremely often during all sessions. The workaround does not always seem to work either, in fact I think I just found the cause of a bug: if one (or more) tracks are Archived, then the last ALT+S to unsolo everything does not work. I can reproduce it in a blank project, can you? Our goal here, the "single-button-to-unsolo-everything" feature, is already present with a mouse click in the Control Bar. Do you think it would be a lot of work for the developers to make the same action available to bind to a key in Preferences / Keyboard Shortcuts? It would be the holy graal here! ? (As I could not find a graal emoji, the tropical drink will have to do!) Footnote: Archive is also one of those commands that is not keyboard bindable (yet)... but it would really rock if it was! /The Cakewalk keyboard nerd ?

Could we please make Unsolo All bindable for keyboard shortcuts? It would really, really help my daily workflow.

This bug is reproducible with Cakewalk 2021.12 (Build 102) as well. I have now emailed support@cakewalk.com.

@msmcleod Thanks, great tip! I have used that way a lot but totally forgot about it. It would be great if the bindable rename clip action would work on multiple clips in the same way. As I say, "Always think about the keyboard". I always look for a way that requires less mouse clicking. Example of how quick it could be: Lasso clips Hit your Rename shortcut (mine is SHIFT+ALT+R) Type your name and press enter Done.

I totally agree... it should be simpler. I know @msmcleod wrote that "There's no way for Cakewalk to guess your intent here" in the EA thread. But as I see it, there are three scenarios: If you drop it on a track folder, the track goes into the folder, to the bottom. (If there are nested folders you want to target, you need to hover on top to expand them first.) if you drop it in between fully collapsed folders it should stay on the top level If you drop it in between tracks that are on different levels, only then is a destination ("drag") indicator needed to show which level your track will end up on.

Great post, Olaf! But I don't think you'll get a reaction here, as this is about the EA. Try creating separate thread, and I'll help you out getting attention by replying to it. But: I think you need to create multiple posts for it to make sense. Especially since you mention some 3rd party plugins with issues. In those cases you need to contact the developer to get it fixed and/or have them make contact with Cakewalk.

Hm, couldn't the behavior be a bit simpler, which would also make it clearer: If you drop it on a track folder, the track obviously goes into the folder, to the bottom. (If there are nested folders you want to target, you need to hover on top to expand them first.) if you drop it in between fully collapsed folders it should stay on the top level (like in Mark's example) If you drop it in between tracks that are on different levels, only then is the drag indicator needed to show which level your track will end up on. (This has been a bit tricky before...) Maybe I'm not just understanding something here... that's been known to happen.