brundlefly

The metronome is automatically suppressed during bounce/export. To get it included in an export you need to first record it to a track, and then export with that track included. 1. Insert a Send from the Metronome bus to a New Aux Track. 2. Arm the Aux track, and record the click out to end of your project (use punch if you want it to have an exact length). 3. With nothing selected, export Master Bus or Entire Mix.

You gotta give up on holding N and changing the secondary setting; I think we've confirmed it casues isues with mouse pointing and clicking. Just switch to the secondary setting by hitting Ctrl+Shift+N (briefly, not held). Then set the resolution as usual by right-clicking, Then you can toggle between the two settings by Ctrl+Shift+N. I don't usually use 'B' to open the browser, so I assigned that to swap them since it's conveniently right next to N.

It's very dependent on how the application is programmed. For example, in Wordpad, I can hold a letter key down and enable/disable the italics button in the ribbon bar while it's repeating, and the font will change as expected. It seems clear the the Bakers programmed the primary-secondary 'temporary swap' function to ignore key repeats, and it does for me. But something's gone wrong with the right-click functionality to present the resolution dropdown.

I got the Ref. Guide method to work once, but on subsequent attempts to change the value while holding N, the button did not respond to right-clicking to get the dropdown list. Also the mouse pointer stops responding to movement intermittently. That looks like a bug. But the method I outlined of simply switching to the secondary snap value with Ctrl+Shift+N and changing it works fine. Holding N to temporarily get the secondary snap value with snap enabled also works, but I continue to have the mouse pointer become intermittently unresponsive while holding N which renders it largely unusable.

Yes, double-clicking opens the Audiosnap Palette which is another way in too Edit Clip Map. The Palette also shows the average tempo and allows you to change it directly, but you really need to see the beat markers in the clip map to know which tempo is correct, unless you already have a good idea what it should be.

Have not looked into this, but if automation were not compensated for latency, iI would expected it to be happening too early, not late/delayed, relative to the audio. But it might depend where the automation is happening relative to where the plugin is operating. If I'm understanding correctly, you're automating volume on a reverb bus, and there is a delay-inducing plugin(s) is on track that sends to that bus. Is that right? Is the reverb also a convolution type, or otherwise inducing delay of its own?

Not sure where you're getting that. Just right-click the snap value and choose the one you want. then Ctrl+Shift+N, and choose value for the other setting. No, that's why I asked about your keyboard driver. I just checked, and Ctrl+Shift+N does continue to alternate between primary and secondary snap, but N (enable/disable snap) does not.

It's making a best guess at what the tempo is, and offering various multiples and fractions of that guess that might also fit. Melodyne also does this, and also often defaults to half or double the actual tempo.

It may not happen with a recording that has a very tight tempo. I checked, and in that case, Melodyne may set a single constant tempo. But it if detects a little drift, it can get a little carried away inserting changes in my experience.

Hmmm... I had forgotten about the 'hold N' gesture, but it works here. Possibly you have a 3rd-party/wireless keyboard driver that's generating the repeat...? The alternative is to use Ctrl+Shift+N, or bind some other shortcut to 'Swap primary and secondary snap settings' in Global Bindings.

It wasn't clear that the OP actually wanted to have the project tempo reset to the clip tempo; just that he wanted to know the clip tempo. That's one reason I suggested Audiosnap. Also, if the clip was recorded to a click, I would recommend just setting the project tempo to that average tempo to avoid complications that can result when Melodyne inserts a tempo changes at every 8th note with interpolated changes of a fraction of a bpm.

It occurs to me that the first step will be to disable the Smart Grid option if you haven't already done that. It's enabled by default in the 'Basic' project template.

Oops. Disregard my earlier post. When I see 'SD3', I think 'Session Drummer 3', and I skipped over the video.

I'm attaching a project that has primary and secondary snap set at an 8th and 8th triplet. Snap is disabled for both, but the grid should change with Ctrl+Shift+N. Check if it works for you. Primary-Secondary Snap Grid Demo.cwp

I have experienced in the distant past that when a pattern is dragged from SD3, the wrong MIDI file may be referenced. IIRC, you can ensure you get the correct pattern by checking the file name associated with the pattern button, and pulling it in directly from the file system.

Set the Edit Filter to Transients, right-click the clip and choose Edit Clip Tempo Map. Average tempo is shown at the bottom of the clip. It may often be off by a factor of two. Play the track and verify that the downbeat markers are aligning roughly with the downbeat transients. If not, choose one of the alternate tempos from the dropdown. If all you want is that average tempo, you can just change the Edit Filter back to Clips.

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...?