David Baay

Okay, yes, I misunderstood the quesiton is about non-Maximized project windows. Basically, Sonar does not allow floating project windows outside the main application window as it does lower-level views, and that's just how non-floating windows are displayed. Right offhand I can't think of any other apps I have that allow having multiple projects/documents open and not maximized so I can't say that what Sonar does is atypical.

Use Sound on Sound record mode instead if Comp recording and either manually mute previous takes as you go or enable Auto Punch with Mute Previous Takes and set a punch range wider than where you're recording.

The screenshot posted by Glenn is a non-Maximized/Restored window as evidenced by the visibility of the dekstop around the window. What you are getting is definitely a quirk of your Windows configuration or some setting you've enabled in properties for the executable or possibly due to interference from some 3rd-party app/utility. I have never seen SONAR/CbB/Sonar's main application window appear modal like that.

Try disabling the 64-bit Double Precision Engine and/or Playback Overampling if enabled for Kontakt.

That setting is for WDM drivers. It's grayed out when driver mode is ASIO. A project-specific issue is likely plugin-related, but if increasing the ASIO buffer size is not helping, you may have some other issue. When you say "dropouts", is the transport actually stopping with a dropout code, or you're just hearing the audo drop out? An unlicensed/expired plugin on the Master bus could cause this but it would be more consistent. Next time it happens, try clicking the Audio-MIDI Reset button in the tranport while holding Ctrl to re-initialize the driver.

Enable Punch recording and check the box to Extend Takes to Punch Out Time in record options. When loop-recording in COmp mode, this happens automatically for the last partial take, but if you're stopping the transport in between takes you need to use the Punch option.

Other options: Set the initial value in Offset mode - less likely to be altered inadvertently once you’re back in Envelope mode. Or use an Automaton envelope with single node at the start to hold a value.

Not at my DAW to check, but should not happen with conventional routing, I think. Do you see output signal in the kick track meter? If not, the compressor may be leaking sidechain input to the bass track output or kick track also has a prefader send to a bus…?

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.