David Baay

It only happens at 1:01:000? If it doesn't also happen when starting playback further into the project, it's not the audio engine. What audio interface and driver mode? Did you maybe have a non-zero Fade On Start value set in older versions that was obscuring the click? Maybe share a simple demo project just to be sure it's not the project itself. Try disabling the 64-bit Mix Engine. Also try Reset Config to Defaults in Preferences > Configuration File. Sonar will back up your AUD.INI and replace it with a default.

No, playback basically stops as fast as it can wherever it is. I find Tab to transients/notes and Next/Previous Measure shortcuts to be pretty handy for getting back or forward to a note on which I intended to stop. I have the latter bound to single keys so don't have to hit a modifier.

Yeah, all bets are off when it comes to level consistency from live synths. Samplers/Romplers will generally be pretty consistent, depending on what internal FX are used, but anything that does 'real' synthesis or uses physical modeling is likely to be a lttle variable. And I second Jonesey's comment about digital clipping. When I first read it, I thought you meant -.5dB and had just left off the minus sign. It's common mix to -.3 or -.5 or less to allow a little headroom for intersample peaks and/or conversion to MP3 which can result in a clipped peaks if the source is at 0dB.

I believe there was only one other mention of high CPU usage in 8 pages of posts to this thread, and CTO Noel Borthwick responded that there have been no changes to the audio engine that would have precipitated a problem. Every new release elicits some spurious reports of performance issues that almost inevitably turn out to be due to other causes. You'll need to look for other changes to your environment, Sonar configuration or project content that would account for this.

Clicking the Export module will show the length of the selection in SMPTE (hours:minutes:seconds:frames). To get milliseconds, add milliseconds scale to the Timeline, enable Aim Assist with X and toggle Aim Assist Time on with Alt+X. As you drag a selection in the Timeline, the Aim Assist Time will show the duration of the drag as well as the current position.

In the mena time, just disable them in Preferences; they can be easily re-enabled when needed.

I recently reported that soloing an Archived MIDI track via the button in PRV tracks pane can invisibly solo that inactive track, causing the whole project to go silent, and re-clicking that button will not reverse it. Similar to your solution, toggling the Global Solo on/off in the Mix module resolves it.

Did you migrate/move projects at some point? I could imagine Sonar creating a new project without a project folder (by having the 'Copy all audio' option unchecked as mentioned), leaving recorded/imported audio in the Global 'Audio Data' folder, but I can't see how it would eliminate an existing project folder established by CbB.

But why is only the first project he opens affected? And how is a Workspace affecting track heights? I'm not seeing that track height is controlled by Workspaces...?

But I can still only repro when lassoing Automation Nodes. If Edit Filter is Clips, the focus frame remains on the plugin, but it does not get deleted; the clip gets deleted as expected. Maybe a function of O/S? My laptop is Win11. Or maybe you guys are running Sonar 'As Administrator' or something like that. Grasping at straws as to why I can't repro.

Better to use Google. I found the one I liked by searching on: plugin gets deleted site:discuss.cakewalk.com Interestingly that thread was saying it can happen even when clicking to select the clip, not just lassoing, adding lasso tot he search yielded nothing. I also found this report suggesting it was specifically related to attempting to delete automation, and was also difficult to reproduce for some users. One said it only affected automation on buses, not tracks. EDIT: I just tested and I can repro the problem when lassoing automation nodes on tracks so that might be the scenario I recall confirming previously.

If you Save As a project to a new location without having the 'Copy all audio with project' option checked, you'll have a project file without a per-project folder referencing audio in another location. Right-click any audio clip in the project and choose 'Associated Audio Files' to see where the referenced file is living. Your missing file is likely still in that folder. Or if you've been splitting longer recordings or loop-recording, it may be part of another audio file referenced in that track.

I haven't yet found the thread to which I contributed but I found a couple others on the topic. The general idea was that if the square brackets remain on the plugin, indicating that it has focus, it's going to get deleted. But I'm not finding that to be the case. Even when I hit Delete having just focused a plugin, it can't be deleted by the Delete key. Is this maybe about using the Del key in the Numkey Pad? My laptop doesn't have one.

Yeah, that's exactly what I did, and it deleted the clip as expected, so I think there must be at least one other factor. I might have to hunt up the previous thread and see if there was some additional detail. I might even have entered my own report.

Yes, once you have an approximately correct tempo, Sonar will guess the nearest quarter-note beat. If it's wrong, you can just Tab to the Beat field and type the correct number. My only wish is that I could have it guess the nearest 8th note as my syncopated compositions often don't have notes on beats so I'm always typing beat 3.5 or something. Also SM/BAN has issues with odd 8th-note time signatures like 7/8. The way I usually work with it is to just count along in my head as I'm listening, bash the Spacebar to stop the transport when it starts getting out of sync, Shift-Tab back to the previous transient/note, and Set that point, knowing what beat it should be from my counting in case Sonar guesses wrong. Also in cases where there's a sudden dramatic rit. or accel. you'll want to Set the previous note so that Sonar doesn't average the tempo all the way back to some point a measure or two earlier, throwing off everything in between. I also recommend binding a single key to the command because Shift+M is awkward. I use it enough that I bound S for 'Set'.

I recall that this has been reported and I have been able to reproduce it in the past but not now in the latest release of Sonar. Is there maybe some additional condition that precipitates it?

Track heights should save along with saving the project. Easiest way to set them all is to select all, and Shift drag the height of one. What version of Windows is this, and what is the language/locale? Another user just posted about this and the language is Spanish. Also confirm you are on build 35 and whether it's the free tier.

I think the OP is referring to all track and bus heights being minimized which another user also reported. I checked, and I don't think Workspaces can control track heights. Seeing the language is Spanish makes me wonder if this might be a Locale-specifc issue.

An actual project would be best.

I hear you. I've definitely had days when Sonar seemed especially uncooperative, but ultimately it turns out to be either my own mistake/misunderstanding or something going on with 3rd-party hardware, drivers or plugins. I'm still trying to figure out why so many are reporting problems with view persistence. There definitely seems to be something going on there. but I'm not seeing any problems in the latest update. I think some of them are actually cases of people not understanding Workspaces and screensets or something to do with the free tier not giving access to Workspaces where CbB did.

It's still not clear to me what you're saying. To me '"fader volume level" is the position of the fader control and has no direct relation to meter colors. And when you say "calculated audio level adjustment based on the fader level reading", this is the opposite of the way I would express it which would be "calculated fader position based on audio level reading (vs. desired reading). That 'reading' could be either an estimated peak or RMS level in the meter or the precise numeric peak value shown at the top of track meters and the bottom of console meters. Also, aside from custom themes in CbB, Sonar's track and console meters don't really have what I would call a "yellow" range or a red range that you can be "in", only green below -6dBFS and orange above it with red clipping indicators at the very top that light when you hit them, and don't reset until you restart the transport. It might be best to share a small demo project and tell us exactly what to look at, where in the timline, and what you expect to remain stable over time or from one session to another.

If want to zip up a handful of them and PM them to me, I can have a quick go. The issue may also be tempo - and/or ASIO buffer-specific. You never answered whether you continue to see signal level on the Preview bus...? If you don't have a dedicated Preview bus, add one, and right-click to set it as Preview.

In addition to making sure Worspaces is set to None as Noel suggested (or at least not automatically applied on load which is an option), make sure you haven't locked the current screenset. The layout of a locked screenset, including timeline zoom level, can be changed while working, but will revert to the state it had when locked on save/close/re-open. If it's not locked, the changes save when the project is saved.

You specify the measure and beat (or fraction of a beat where needed) that you want to correspond to a certain absolute Now time in the audio, and Sonar calculates the number of beats since the last set point (or 1:01:000 if nothing has been set yet) divided by the absolute fraction of a minute to that point in the audio, and that gives bpm for that interval. It shifts the timeline accordingly around both audio and MIDI without changing the absolute playback timing of either. It's magic. ;^) If you find later that the tempo for a four-bar (for example) segment that you set is letting the audio drift away from the timeline in between, you can set intermediate points as needed to dial it in; you don't have to do everything in order from start to finish. One caveat: Never delete a tempo change that SM/BAN has made; always Undo back to the point just before you picked the wrong beat or transient to set, and re-do it. Actually this isn't so critical for pure audio projects but is for MIDI or projects with clips that don't all start at 1:01:000.

Not the typical experience. As strongly as you might feel that Sonar has issues, I bet the vast majority of what you've encountered has an identifible root cause that is not a bug. In particular, anything that's not easily reproducible is likely not a bug. Most of the reproducible issues I know of in Sonar have been with us since CbB or earlier. And any new ones that have cropped up have been addressed pretty promptly, but you need to be able to reproduce them with some level of consistency.