David Baay

It's a workaround; take it, leave it or avoid it as John suggests. Everyone has his/her pet bug that they encounter all the time because of some particular workflow they use frequently. I have some going back a decade or more, so I'm both sympathetic and not. ;^) Development priorities are based on a number of things, including the number of independent reports of the problem. Yours (and the formal one I made to the Bakers to help you out) are the only two I know of. I would wager not many other people are trying to punch in to a Melodyne clip. Most will do one or the other, not both. This is actally the kind of thing I try to avoid. The more non-destructive edits you pile on a clip, the more likely you are to get a weird result from a combination that was never anticipated or tried by anyone during development and testing, and when one of those edits involves two complex 3rd-party technologies (Melodyne and ARA) all by itself, I am not surprised when this kind of issue crops up.

See Noel Borthwick's explanation in the following thread from last year about this issue that was recently bumped to life. If you re-save the project with the the Media Browser set to a different location it will re-open to that location (default would be \Cakewalk Content \Audio Library). It's not entirely clear why it sometime picks up on archive files in other Locations, but I've run into myself as mentioned in that thread.

Look for a large zip archive in the path that the media browser is referencing or possibly on your desktop.

Have you been using a common custom template to start all your porojects since then? If you open the Media browser what directory does it default to, and is it the same as the fast-opening projects?

A track can be focused without having anything selected in it. In addition to being shown in the Inspector, the focused track (name highlighted) is the track that will respond to keyboard shortcuts like Alt+R to arm it for recording or Shift+T to show its lanes. And it's the default target for pasting. Among other things, separating focus from selection allows selecting something in one track, and copy/cut-pasting it to another track with keyboard commands. This is handy for pasting to a precise Now time that's different from the start time of the selection or that would be hard to hit by dragging and/or that's far offscreen from where the selection is.

They're talking about zip files they created themselves for various reasons. I ran into this issue a few years ago when I was moving files to an SSD and zipped up my Projects folder and didn't immediately remove the archive file after unzipping it in the new location.

Yes, it has a lot of different functions depending on the context and what part of the clip your cursor is over. Adding Ctrl/Alt/Shift modifiers or combinations of them can give you almost all the available functions without having to change tools. https://legacy.cakewalk.com/Documentation?product=SONAR&language=3&help=Tools.04.html

When the Smart tool is used in the top half of a clip, it should automatically operate as the Move tool and display the relevant cursor.

I don't believe so. I agree it gets too fine too fast.

Google says (excerpt from Microsoft): Go to Start > Settings > Update & Security > Windows Security > Virus & threat protection. Under Virus & threat protection settings, select Manage settings, and then under Exclusions, select Add or remove exclusions. Select Add an exclusion, and then select from files, folders, file types, or process.

It's not random, it uses the velocities of the selection you specify as the Groove reference, and applies them at the specified strength. 100% means the reference velocities will completely overwrite the existing velocities.

You know, I thought I remembered this being the case, but when I took a quick look at the Ref. Guide to refresh my memory, I somehow missed it. Good catch.

A must-see handpan video:

Hmmm... twice in one hour: Disable "Always Import Broadcast Waves at Their Timestamp" in Preferences > File > Audio Data before dragging them in.

Disable "Always Import Broadcast Waves at Their Timestamps" in Preferences > File > Audio Data.

You have officially crossed a DSP Rubicon when you start using plugins to remove effects of other plugins.

Velocity is part of the Note On message and can't be manipulated independently. But what you can do is add a Clip Envelope for MIDI Velocity [Offset], create three nodes to offset the next three fixed-velocity notes to achieve the desired values, and copy-paste the three nodes as needed to affect the rest of the notes. You can leave the Vel+ envelope in place to preserve editing flexibility or Bounce to Clip to write the velocity offsets into the note events. EDIT: Looks like I was wrong about this. The MIDI clip automation cannot be copy-pasted independently of the notes, either.

No good ideas what might be going on. Are you recording mono or stereo from the patch point? Can you see distortion or variable amplitude in the waveform? Can you post a short audio clip?

Regardless of which view you do it in, the entire track/clip has to be selected first. Select by Filter operates on whatever is selected. If nothing is selected, there's nothing to filter.

Got it. No worries. ;^)

As noted ealrier, the question is actually about the display of clip stretch percentages not tempos. The tempo snap setting is not relevant. That said, for the benefit of the OP, Alt+T will open the Tempo Track, and right-click there will show the option to snap tempos to whole numbers. This just affects what happens when you drag a tempo node.

Hmmm... I don't know. When I enter a value for Stretch Amount of "202" in Clip Properties (I mis-stated to use Process Length for this), the clip displays 202.00%, and I'm not aware of a setting that affects this. EDIT: I checked this in Platinum 17.10, and it only displayed whole numbers in clips and tenths in Clip Properties, but it allowed entering decimals to thousandths and would stretch accordingly. It seems the display of decimals was enhanced at some point. because clip properties shows 100ths now as well.

Omni is an Input setting; promidi's talking about the forced Output Channel setting that dynamically overwrites the embedded channel information in each event as it's transmitted. But I don't really think that's relevant to this issue. And I highly doubt the project is actually corrupted. Most often the "corruption" conclusion is just a failure to identify the root cause of unexpected behavior. I don't own anything from EastWEst, but if you can share a track that's misbehaving, and the cause isn't East West itself, I'm sure I can fix it. The crashing issue definitely sounds like it was a problem with EastWest. A quick Google found other reports of Reaper/Studio One/Finale crashing "after 10 minutes" using EastWest Play; sounds like a memory leak.

Just to be clear, that's a stretch percentage of a clip that's been stretched by dragging. You can't eliminate the display of decimals, but you can get a whole number by using Process > Length instead of manual stretching.

Yes, I also noted the soloing the instrument allowed it to freeze properly, but it shouldn't be necessary. As noted, freezing with the instrument outputting to a a soloed bus worked in the last release of Platinum.