David Baay

8.5 and earlier allowed customizing the interaction of modifier keys with the various tools, but I don't recall that clip hotspots were ever adjustable. I suspect you're just thinking of the images in the Ref. Guide that show where the hotspots are for various tools.

The first project I tried did have secondary snap defaulted to 1 tick, but after changing it to a 16th and saving/closing the project, the setting was restored on re-opening. I even opened another project with different snap settings in between, and it worked as expected. You're certain you don't have a Workspace enabled.

Snap settings are project-specific unless you're using a Workspace. With Workspaces set to 'None', saving the project should preserve the settings for that project. I don't use Workspaces, so can't verify that's working.

Apparently not; I was unable to find a single instance of another thread mentioning this issue. That's not to say there isn't one out there, but it definitely was never a common complaint. It's possible it was working as expected in some previous version of SONAR, but I doubt it. I no longer have an installation of SONAR 6 or 7 that had the '1.0' version of Audiosnap, but my guess is it has always been this way. One clue is that the context menu that gives the option to Quantize comes up when you right-click the clip, not when you right-click a selected marker.

I agree the Smart Grid goes to finer resolutions too quickly, and it would be really nice to be able to adjust the relationship of resolution to zoom level. That's one reason I've never used it much. But I checked, and it is possible to disable snap in one or both of the primary and secondary snap resolution settings, and use Ctrl+Shift+N (or your preferred keybinding for 'Swap primary and secondary snap settings') to change between two grid resolutions while leaving snap disabled.

Nudge should also work on selected notes in the Inline PRV. Maybe try moving the clip to a new track; it seems like the existing one has gotten into a bad state somehow.

Looks like a programming oversight that was never reported... or not reported often enough for Bakers to prioritize it. I doubt it was deliberate or too difficult to implement quantizing only selected markers. Tried some workarounds, but could not get the desired result. Disabling other transient markers allows their transients to move proportionally as quantized transients move, which is not what you want. The only way around it is to split at transients and quantize individual clips. But then you might as well just take the time to manually snap drag individual transients.

The Move tool will only appear when you hover over the middle third of the note; outside that area, you get tools to change the start and end time of the note. Possibly you're hovering over a different part of the note in this particular track because the notes are longer at the current horizontal zoom level, and when you zoomed vertically, you just happend to hover over the correct area...?

Yes, I can repro that. Did not happen in SONAR 17.10, but the Freeze button should really be disabled and grayed out by Archiving.

Already implemented. Shift+Spacebar

I'm not sure about the transport button because I almost never use the mouse to control the transport, but the 'W' keyboard shortcut still works that way.

Utilities . Clean Audio Folder now gives you an option to searhc only the project path or the whole PC. so it;s very efficient for cleaning a single project folder now. Personally, I still prefer to clean my whole project folder periodically, using Utilities > Cakewalk Audio Finder Tool. CWAF tool can do all projects in one go, and gives much more information about what audio belings to which projects, and more control over what happens to 'cleaned' audio. Here's how i use it: Preparation: - Create a folder called “CWAF Excluded WAVs” on the drive that contains your projects folder. - Create a shortcut to \Program Files\Cakewalk\Shared Utilities\cwaftool.exe so you can run it with Cakewalk shut down. Usage: - Close Cakewalk. - Empty the Recycle Bin. - Start CWAF Tool. - Add your “Excluded” folder and any other paths that will never have Cakewalk projects in them to the 'Folders to Ignore' list. - Select a drive to search (i.e. the one containing your projects folder). - Click Find – The button label will change to Stop, and you will see paths being searched in the status bar at the bottom. - Wait for the Stop button to change back to Find, indicating the search is complete. - Click the Status column header twice to get all the Orphaned files floated to the top. - Select all the orphans, click the Move button, and select the CWAF Excluded WAVs folder on the local drive as the target. - Repeat the search and sort, and scroll through the list to be sure there are no Orphaned or Missing files reported (i.e. you found all the orphans, and didn’t inadvertently move something that wasn’t an orphan). - You can now safely Shift+Delete (permanently deletes, bypassing the Recycle Bin) all the files in the “Excluded” folder.

In most cases, the track name should be part of the file name that is reported 'missing' unless it was changed sometime after the recording was made.

Are you running the current release of Cakewalk? There was a bug carried over from SONAR that was fixed a while back that the metronome could be broken by changing metonome preferences while FX Bypass was enabled in the Mix Module. Toggling FX bypass Off/On would fix it. If that doesn't get it, delete all the tracks from a non-working project and share a copy somewhere.

Slow? You mean GUI response to the mouse or meter/spectrum analyzer animations or... something else? Possibly you enabled CPU Conservation Mode with the Pause key that reduces UI updates to once per second...?

FWIW, I recently discovered that my crummy dual-core laptop - which I use mostly just for referencing Cakewalk behavior and menus when posting to the forum - does not perform well with the 'Agressive' ThreadSchedulingModel=3 set in AUD.INI (Preferences > Audio > Configuration File). I don't think this is the default (?), but the new option 3 was just introduced in the last release, and some users may have deliberately changed from 1 or 2 to 3 and promptly forgotten about it rather than checking to see how it worked as suggested in the release notes: "Experimental aggressive task scheduling model We continue to work on improving our multi-threaded engine performance and have added a new "aggressive" task scheduling model. The aggressive task scheduler utilizes more efficient task management that can result in better multi-processing and fewer thread context switches. This feature is still experimental so report back if you notice any improvements or problems when using it."

That's generally true for me, too, but there have been many times over the years that something I played while improvising a new piece or rehearsing a part (lead solo, melody, bass line, high-hat pattern, whatever...) just worked perfectly, and I wished I had been recording because I couldn't reproduce it exactly. I've mostly learned to just go ahead and hit 'R' when there's a chance some magic might happen, but I still miss things occasionally.

What if you turn down the output level of the synths, disable input monitoring or disconnect them and monitor directly with headphones? In other words is the sound from the synths or from some sort of radio interference/feedback inside the DAW?

If it works in some projects, it almost has to be a project config issue. Check routing of audio metronome. If it's to a bus, as it should be, make sure that bus is passing audio (i.e. not muted) at a decent level, and has an output path to your interface main outs. And, of couse, it needs to be enabled in the Transport module. You might also check that the click sample and levels for First Beat and Other Beats in preferences are the same as in working projects. An obscure possibility that I sometimes encounter is that I've recorded a click track and inverted the phase so it nulls the live metronome output when both are enabled, but that wouldn't affect count-in.

It would be best to get the R8 working at reasonable latency, have it set as both Playback and Record Timing Master, and use headphones for monitoring the metronome as well as the instrument input. What driver mode are you using with th R8 (preferably ASIO, if supported, or WDM), what buffer size, and what's the total reported round-trip latency?

Okay, so the the audio file was just imported from the Zoom. The same steps apply for whatever interface you are using. If it's onboard sound, you will probably want to set the Driver mode to WASAPI Exclusive in Preferences, and go from there. But you might want to consider using the Zoom as your audio interface if you don't have some other dedicated interface.

Things to check: - Zoom drivers installed and Zoom is set to Interface mode in its menu system. - Appropriate driver mode selected in Preferences > Audio > Playback and Recording (not sure what Zoom R8 supports) - Zoom I/O ports are available and checked in Preferences > Audio > Devices. - Zoom drivers are selected as Playback and Record Timing Masters in Preferences > Audio > Driver Settings. - Track meter shows signal. - Track outputs to Master bus. - Master bus outputs to Zoom and meter shows signal. - Monitors are connected to Zoom outputs and powered up.

In my world, 'stems' usually are buses. I guess you mean individual tracks with track FX...? In that case, it might be related to mono-stereo interleave setup. In any case, you should start a new thread, and detail the routing and export options.

This might need to be a sticky: Menu Items Missing? Change to Advanced Workspace.