winkpain

Thanks for the response! So it's not just me. I'm glad it's on your radar! Odd, to some of us on the front end, that the Inline PRV and full PRV behave differently enough to make this an issue, but I hope the fix isn't too difficult. AND, if it really is on the radar, the (full) PRV smooth zoom/honoring mouse wheel zoom settings issue would be a good fix as well. Perhaps it is related(?) given the odd differentiation between here and the Inline PRV (which does honor those settings).

...Perhaps it was a web site problem. I eventually got it to work.

I totally agree with @Peter Hintze What would be great throughout the Cakewalk environment is a more nuanced zoom like is seen in the referenced video and like we already get with the timeline click-drag zoom and especially with the Melodyne zoom within CW is a far more functional zoom compared to quick jumps. It allows our visual-mental focus to remain on the area in question as we approach it with an organic, flowing digital screen focus. The quick indexed jumps of zoom always leave us wondering exactly where we are, and there is a necessary period of reorientation to get our bearings before finding what we were looking at to begin with. The timeline zoom is the something towards the style we're talking about - a simple click-drag with a fluid perspective change, hand and eyes staying fixed the whole time. It, however, only functions for horizontal zoom. Exactly what we have in the Melodyne view would be fantastic in the other CW views (Track view and PRV view specifically). Here we simply hold CTRL-ALT and left-click drag, vertically for vertical zoom, horizontally for horizontal zoom and/or a combination of both, all functioning in essentially one fluid and easy to focus on movement.

I am now (I was able before) unable to upload two very small animated gifs to a post of mine. I have ~4mB left available for upload and they are less than 1 mB total. After waiting a while where it says "uploading", I then get this message... This happens no matter which browser I try.

Videos...

Here are the issues being clearly shown as described with 1 showing the envelope problem and 2 showing the Ripple Edit problem...

Crickets on this? No one else??

Today my preferred M-Audio MIDI keyboard (simple 88 key, piano keys only keyboard) stopped functioning within CW with no changes to computer or CW since it worked perfectly yesterday. Scenario is: Keyboard is selected as MIDI input in preferences MIDI input activity (in task bar) light blinks appropriately showing input data when pressing keys Keyboard is chosen as input in track with echo on With record on, nothing is recorded when playing Unplugging and re-plugging of USB cable gets the message that device has been removed/added from within CW Keyboard functions normally in other applications outside of CW (stand alone synths, other DAW, etc.) An alternate Novation MIDI keyboard works fine within CW going into the same USB cable The above is no longer true. CW is not responding (besides the MIDI activity light) to either keyboard Closing/restarting no effect What the.... ??

I am sorry to harp on these issues that I've mentioned before, but I've had no response either confirming or denying these issues, so I just don't know whether the problems are mine alone or to be fixed in a later update. There are two issues with the Duplicate command (my favorite of the "recent" additions!) that continue to frustrate my flow, man! In brief: With "Select track envelopes with clip" checked "On", selecting a clip and choosing "Duplicate" with the clip context menu or its shortcut CTRL-D does not copy the envelopes with the clip. ? However, choosing the Section (in Arranger) containing the clip(s), right-clicking and choosing "Duplicate" from the Section context menu, OR CTRL-clicking the clip and CTRL-dragging to copy does copy the envelope along with clips, as they both should do. ? AND With Ripple Edit on, choosing MIDI notes in the full PRV and then choosing Duplicate will not ripple edit the following material (it will just overlay it) ? However, choosing the exact same notes in the inline PRV of the track and choosing Duplicate will ripple edit the material as is the desired and called for behavior. The Duplicate command and its CTRL-D shortcut have come to be very oft-used and second nature in my editing and these two issues above seriously impede the flow that its use is obviously supposed to improve. Am I alone, or can these issues be replicated by anyone else and be deemed buggy?

...also, since I am the sole user with only one user account on my computer(s) and that account being an "Administrator" account (which is why I don't totally understand the need to "run as administrator" to begin with), wouldn't the presets be saved in my user account folder in either case, whether "Run as..." is chosen or not? I see no other user account AppData folder (except for the "Public" one) on my machine, with "Show hidden files and folders" checked off. OR does this have something to do with the "hidden administrator account" that I read of?

Ok. This helps clarify a bit for my situation. Thanks! SO, I am maybe in a similar situation to you, then, in that I have been running CW "as admin" from early on, and if I were now to follow this advice and uncheck that Properties option, I may run into these VST issues. The presets one is easy enough, right? I just move them to myaccount\AppData folder. BUT the license issue requiring the re-install would make itself known obviously? I would get a message saying the plugin is not registered when trying to use an instance of it? Or would I get messages for the affected ones when starting CW with a VST scan?

Interesting. The plot thickens! I just sometimes want to save to a SD card but don't mind saving to desktop, then dragging to SD if need be. I don't want to have to re-install plugins just to do so. But! I'd like to at least understand what you bring up. So you're saying by choosing to run or not run CW as administrator would affect how the plugins work, depending on the plugins? Does that depend on whether the plugins were installed with administrator rights or not? And how then would the issue make itself known? Not until I attempted to use an affected plugin and it didn't work? There would be a error/warning message, or...? I have always been thrown off by the permissions/administrator rights issues, never understanding why I, as the sole user and administrator of my computer, need to choose or sometimes not choose to "run as administrator". I've read enough here and there around the edges of it to know it has evolved as Windows evolves, but I can't admit to really understanding how to behave with it. This is likely why I chose to set CW to "run as administrator", because to me it seems like the "better" choice. This is obviously a bigger question than my original, which is really no big issue, but it is certainly a bigger curiosity on my part.

Not sure what you mean here. How would reinstalling plugins make a difference in CW saving to a SD card?

Gotcha. That is the smart way to go. I do not have a sick Win 7 system at all. It was a machine meant to come with Win 10 to begin with, but at the time of the build i wasn't sure of compatibility with my plugins, specifically Waves, so opted for Win 7. But I've since upgraded everything crucial, have the same versions on both systems and all works fine. I have no other hardware or software concerns like you did and no other practical reasons other than the end-of-life concerns for Win 7. So in my case, since "it ain't broke" , I'd like to think that it could just be an easy, labor free upgrade scenario. But.... can it be?

I'm curious, did you do a "dirty" upgrade to Win10 or a clean install and then reinstall everything? I am on the edge of doing similar, for different reasons, bringing my Win7 system to 10. I have had a secondary mobile system with 10 on it from day one and all my same (same as the Win7 system) versions of CbB and plugins up and running from the beginning there with no issues. Of course I'd love to just do an in place, dirty upgrade to Win 10 and not re-install everything else since I have all the same stuff running on the 10 and know that it "works". Is this just wishful thinking?

Oh I definitely had clicked/selected the clip. I'm well versed in the protocol for applying FX from the bin when bouncing. Yes. It's supposed to. That's why this is a curiosity. That's what I'm saying. This is weird. In the case of bouncing to track and this Waves Tune in the bin, CW simply rewrites the original unprocessed clip to the new track. And it's only with the Wave Tune plugin. Any other FX plugin, and bouncing to clip or track works as it should, processing the inserted FX and creating a new track or clip as the case may be. I guess there's something amiss with this particular Waves plugin. But why would moving it make the difference??

Here's a very bizarre situation. I have a vocal clip and I put the Waves Tune plugin in the clip FX bin. I make my adjustments in plugin as needed. Everything sounds good with the plugin running in the bin. I choose Bounce to Clip (or Bounce to Track) to commit the FX edit, it shows the "mixdown" of the audio, and the FX bin is cleared. However, nothing is changed in the audio of the clip per the Waves Tune plugin Exporting out the track to a .wav file does apply the edit. In running the many, many permutations of changes to find the issue (deleting everything else, FX, other clips, etc.), I found that (here's where it gets bizarre) moving the clip to the somewhere else in the project allows the bounce operation to succeed as expected. (There is no automation on the track, BTW.) And then....sliding the clip back to the original position after having done that (and doing an undo in order to test again) and then trying the bounce again with the FX, it succeeds! But not without moving it first and applying a bounce there, then undoing. This situation is true on any of the clips/tracks where I have placed the Waves Tune plugin, and is true when I place it in the track FX bin. All other FX that I've test with, including other Waves pitch plugins, placed in the bin are fine with the bounce operation as normal. Look that up in your Funk and Wagnalls ! ?

Fascinating! That is all good stuff. Thanks. I'll give that a go.

Perhaps it's a Windows 10 thing? I just tried the exact saving process, onto the same SD card, from my CW on the Windows 7 machine and it worked fine.

I have CW set to always run as admin.

It feels like it. But what do I look at to see? Folder Properties on the SD card don't have a Security tab where permissions are set...

I have an HP laptop with touchscreen, just tested this to be sure, and have no delay issues with the touching and immediately dragging/fading. Don't know what the issues would be that create the difference, but I have done nothing special to "enable" this function. I have to say that being able to use the pen for drawing envelopes makes the touchscreen experience really a game changer for me!

I am trying to save some CW bundled projects to an SD card for taking to another machine. The card is not write protected, has plenty of room on it, and I am freely able to write, create, drag-and-drop files onto this card. However, when choosing a folder (any folder) on that card for saving my bundle files, CW returns with a message that it "can't" and to "Please choose another location". I can then just save the bundle to my desktop and drag-and-drop it to the desired location, so it's not a critical issue, but.... What is preventing CW from saving here? Are SD cards special in this regard?

Well, let's just say it has caused me a lot of confusion , perhaps self-induced, as I wasn't aware it was "allowed" (I am familiar with other programs having key bindings settings that ask "Are you sure" when you attempt to bind something that is already bound) and hadn't noticed the tangled mess of multiple similar bindings I had built up over the years. I am one of those who needs this "Are you sure" with everything (and infinite undo's) ? It seems I misunderstood your comment there. But yes, I can confirm the successful zooming either with a custom binding or mouse wheel with the Now Time staying put.

Separate keyboard shortcuts being bound to the same action is a peculiarity of Cakewalk and causes quite a bit of confusion to be sure. You are not alone in that regard! Also (if I understand your question) you can set your mouse wheel to horizontally zoom in/out (along with ALT, CTRL, and SHIFT as modifiers) with the cursor as the focus, leaving the Now Time wherever it is (which will then likely pass out of the screen as you zoom somewhere else). This is done in Track View's Options tab. Otherwise, you can go the Track View category in the Key Bindings settings and bind something to the action "Fast zoom" in and/or out. This will also zoom with the cursor as the focus.