David Baay

Might as well close the forum, then.

Are you able to install any other new software? These look like pretty low-level file system permissions issues that would be best addressed by Window Support.

Note Properties is double-click now. I also preferred right-click, but I guess Bakers felt that facilitating Delete was more important. Beyond that, Smart tool can do just about everything. I know some old-timers preferred the earlier tool impementation for writing music in the PRV. I've always recorded everything in real time with a minimum of editing needed, and there's been a lot of water under the bridge since Sonar 8, so I don't recall all the differences. What specific workflow is requiring you to switch tools?

Try pre-creating the target track.

FWIW, I used to use Percussion Strip regularly to gate noisy hardware synths, and sometimes for its other functions, and don't recall ever encountering any issues. It still loads (Installed with Platinum) and works fine.

Was "latest update" build 33 or 36? If "drum machine" is hardware, you would need to bounce with Render in Real Time and Live Input options enabled. If "drum machine" is a VST, I'm not seeing any issues in build 36, and you would need to provide a demo project and specific steps that reproduce the issue.

But PDC gets recalculated when playback is restarted, and the contribution of any plugin that's disabled in the bin will be eliminated at that point. In addition to disabling the plugin, Sonar has a PDC [Override] button in the Mix module that will override PDC on input-monitored tracks so long as the PDC-inducing plugin(s) is/are not on that track or in its path to the ouput.

Right click the Draw tool in the Tools module; "Pattern" is the second option.

In my experience, Melodyne will not do a great job with a piece having that much rubato, and you will do better to use Set Measure/Beat at Now.

Yes, the Pattern tool in the PRV. But OP is converting MIDI to Groove Clips and. Rolling out iterations. I should add it might be worth a try to increase the MIDI Prepare Using buffer from the default 50ms, but the symptoms don’t fully align.

What happens if, instead of doing this, you just copy & paste a range of notes? Or Bounce to Clip the MIDI after rolling it out? EDIT: Also, did you sequence the MIDI or was it recorded from a drum controller? - if from a controller, possibly there are issues with the denstity of Hi Hat control messages or something like that...? What if the same MIDI track is assigned to a different synth or a hardware MIDI out?

So you have an Instrument Definition for the Arturia assigned it to the hardware port with the Bank Select Method in the defininition is set to Controller 0 Only? The only thing I can think is possibly Sonar is sending the Bank and Patch messages too quickly in succession for the Arturia to respond properly. What if you set only Bank from the track widget, leaving Patch set to None, and do the program/patch change in the track? Maybe try to confirm what's actually being sent using MIDI-OX or similar 3rd-party utility.

There's a link under Cakewalk in the menu at the top of the forum: https://bandlab.github.io/cakewalk/docs/Cakewalk Sonar Reference Guide.pdf

If you're talking about the dB scale on audio tracks, track 7 is un-zoomed and showing the default full scale. It will show more subdivisions below -3dB if you increase the track height. Tracks 8 and 9 are zoomed so dB values above -12dB (i.e. closer to 0dB peak) are off the scale.

What interface and driver mode (preferably ASIO), what buffer setting, what are you recording (MIDI, soft synth audio, hardware synth audio, DI guitar, miced instrument/voice), and are you direct-monitoring through the interface or by Input Echoing the recording track in Sonar? If recording audio, what does Sonar show for Record Latency Adjustment in Preferences > Audio > Sync and Caching?

Assuming "lag" means audio latency, it's unlikely your issue is interface/driver-related. If it's not just that your ASIO buffer is set too high, noticeable latency is usually due to plugins that use lookahead buffers inducing plugin delay compensation. If the plugin is not on the track you're input-mpnitoring or in its path to main outs, you can override the delay compensation by clicking the PDC [override] button in the Mix module. Otherwise you'll need to disable or remove the offending plugin from the project until you're done tracking. Such plugins are generally intended to be used during mixing and mastering when latency isn't an issue. If thi is happening in a basic project with no plugins, let us know exactly what you're doing - i.e. playing a soft synth, playing a hardware synth, recording from a mic...? And ideally you should start your own thread so people don't get hung up reading the OP and responses to it which are probably unrelated.

If you have a licensed installation of SONAR, TTS-1 will remain available. No action is needed to preserve it.

I have not in terms of quantizing, but I did try creating a tempo map from audio which I was told it could do well. The result was not good, but it could easily have been driver-error.

Actually, if you don't intend to use Platinum ever again (or you only installed it to get plugins as I did on my laptops), it shouldn't be a problem to delete its Content folder as all those directories will only be referenced by Platinum, either based on Folder Location paths in Preferences or by Platinum-specific registry entries (e.g. for the metronome samples). But you'll want to copy any custom content you might have created in Platinum like FX Chain and Prochannel Presets, Project Templates, Track Templates etc. to their respective Sonar folders. What I've been doing for years is maintaining a common set of content folders directly under Cakewalk Content to which all installed versions of Sonar/CbB/SONAR refer.

Audiosnap in Sonar. Expand the Audiosnap section on the Clip Properties tab in the Inspector and check the Enable box. Click on the clip to open the Audiosnap Palette that gives access to the various functions including Quantize. You can also hit Q for general quantizing, and the dialog box has an option to Audiosnap Beats which shuold be checekd by default. First thing to do in the Palette is to make sure the Clip Tempo was detected correctly andchange it if necessary, the drag the Threshold slider to adjust the transient detection sensitivity and/or Resolution setting to leave a transient marker active on each bass note, and no superfluous ones, Sometimes you wil need to manually enable some individual transient markers that the Threshold adjustment is suppressing or vice versa. Beyond that you will want to read up on the Clip Tempo Map and other Audiosnap features in the Ref. Guide.

Yes, but the key to your amp's "re-amping facility" (I assume) is that the re-amping input matches the low-impedance, high-level, balanced output from your interface to the high-impedance, low level, unbalanced input of the amplifier's pre-amp circuit so that it behaves the same as if the signal were from a guitar. If you're going to use pedal FX designed for a guitar signal, you should ideally use a stand-alone re-amping box between the interface and the pedals to do the same thing:

I forgot the fix hadn't yet been included in one of the updates already released. That should take care of it.

In that case, John has you covered with direct monitoring and the Input/Playback mix control.

... or when mixing with real-time external processing as in this case. And there are many other valid use cases. As a long-time and ongoing hardware synth user, I have always monitered through the box since it became possible to do with reasonable latency. I assume the the reason the OP wants to do it is to be able to tweak the amp to get a good-sounding mix before recording or maybe even to rehearse control moves that he wants to execute while recording.

Try disabling the 64-bit Double Precision Mix Engine and/or Always Stream Audio Through FX. It might also be worth toggling the state of Use MMCSS and/or Enable MMCSS for ASIO Driver. I just recently tried enabling MMCS for ASIO and got some minor glitching when looping. I believe it's off by default and its potential benefit is very driver-specific. More generally, whenever this kind of bad streaming behavior crops up, it's always worth executing Reset Config to Defaults unde Preferences > Audio > Configuration File as a troubleshooting step. Sonar will back up your AUD.INI and replace it with a default configuration.