David Baay

For me they are already 'sharper'; they just need to be slightly bigger and bolder as in CbB. I find the readability of almost all other text is an improvement over CbB at the same scale on the same monitor with the possible exception of Plugin and Media Browser text which got a little smaller, as did the numbering in the timeline and on volume/pan controls in the Console and Inspector. My vision is slipping with age, and restoring them to the size/boldness they had in CbB would be helpful to me. A larger timeline font would be especially appreciated. I find the contrast is pretty good everywhere except the Volume/Pan/Gain widget labels which are the same medium gray on dark gray as in CbB, but their differing units/appearance and consistent locations make that mostly a non-issue. This is all based on my preferred Mercury Classic theme.

When just one or a few users are experiencing sudden-onset instability and it it isn't affecting the majority of other users, it almost always means one or both of two things: 1. The root cause is at least partially external to Cakewalk - i.e. interoperability with particular environments. 2. Different users with similar symptoms are assuming Cakewalk is the common cause when the root causes are actually different, making the "issue" seem more widespread. In your case, it sounds like you're seeing similar - but not identical - issues on different machines. Together with the fact that Platinum is also unstable, this points to the root causes being both external to Cakewalk and different on the two machines (and maybe different for Platinum than for CbB and Sonar). Aside from the VC Redist issue, other common external causes are (in no particular order): - Other O/S or 3rd-party software updates, changes or new installations. - Interface hardware/firmware/driver updates or configuration changes. - Other hardware/firmware/driver updates or configuration changes. - RAM/Disk errors or other failing system hardware. - Cakewalk configuration changes (expecially related to driver mode, I/O enables and CPU - Project content changes (e.g. using new/updated plugins). If Cakewalk is launching okay and crashing only with a project open, the first step is to see if it's stable doing essential things like recording and playing back MIDI and Audioin new project started from the Basic template with only well-known stable instrument plugins. On re-reading your second post, I guess it's really down to a problem with just one project. If you want to PM me a link to a zipped copy, I'll give it a whirl here, otherwise you should submit it to the Bakers.

If I'm understanding correctly you're talking about the title bar of Prochannel modules in the Inspector following the track color in CbB, and not in Sonar, I hadn't actually noticed that til now. It would be nice to have that back.

Since a "Rewire Panel" was mentioned, I initially thought the quesiton was about Rewiring Cakewalk into Reason, but if it's about seeing Reason as an option in Insert > Rewire Device in Cakewalk, you just need to make sure Reason is enabled to be a client. Start Cakewalk first and then Reason. Once Reason is Rewired into a saved project, it should be launched automatically whenever you open that project. I;ve never used Reason, bit this is how it works with Presonus Notion.

Cakewalk can be a Rewire host but not a client.

The status bar shows your project is being saved. If the collision is happening that frequently, try lowering your Auto-save frequency.

From Cakewalk for DOS days, F7 and F8 were bound to Go to From and Thru, respectively. When Sonar X1 re-purposed them, I changed them back.

- Tracks > Bounce to Tracks - In the Bounce dialog, choose Buses as Source Category - Ctrl+Shift+Click any bus to de-select all buses, and then re-check only the Master, and OK to execute the bounce. Unless you happen to have an empty track focused, Bounce to Tracks will create a new track that you can rename and redirect to Main Outs. I usually have a Master Bounce track pre-existing in my templates. and just focus it before I execute Bounce to Track so it automatically becomes the target. Regarding busing and volume management, My templates also has 'Pre-Master' bus that's used only for summing the mix with no plugins on it, and outputs to the Master. Master holds mastering effects and outputs to a '> Main Outs' bus that goes to the hardware outs, and can be used to manage monitoring levels. It's also actually where Master Bounce and Metronome output to rather than direct to hardware outs. Since I only ever bounce/export the Master bus, the end result is not affected by anything I do on the > Main Outs bus. In reality I generally use hardware to manage my monitoring volume and there's nothing on the > Main Outs bus except possibly metering plugins.

I would wager the timeout period is determined by the activation server so it can't be hacked on the client side. Versions available when the timeout was longer used a different activation architecture and server and can't activate against the current server at all. That's why an update was forced in the first place.

CW developers have historically avoided the use of warning pop-ups to save you from yourself, and rightly so in my opinion. My suggestions: - Get in the habit of hitting Ctrl+Shift+A to deselect everything before bouncing/exporting an entire project. - Use the Project Start and End markers to define the default range. - Instead of going straight to export, bounce the Master bus to a 'Master Bounce' track that outputs directly to Main Outs in parallel with the Master bus. Group that track's mute button in opposition with the Master bus so you can A/B between the live and bounced mixes. When you're satisfied that they sound the same, export the Master Bounce track in the desired format.

Click elipsis in the upper right corner of your initial post and choose Edit. You can place your cursor in the title to edit it as well as the body. It;s customary to just add SOLVED! to the start of the existing title. I would also suggest you link Noel's post from page 3 and/or the download link for his VC Redist repair tool.

Should not be necessary to reinstall, just run the VC Redist repair tool.

I repeat:

Try the new VC Redist repair tool:

Good point. The one time I had realy chronic and mysterious crashing turned out to be due to bad RAM, verified by Memtest. And other apps were not affected; only SONAR was using RAM extensively enough to hit the bad blocks. But it seems the OP has disappeared...?

The region muting is due to the 'Mute Previous Takes' option being enabled for Punch recording. As Mark pointed out, it can be un-muted by sweeping in the top half of the clip with the Mute tool.

This doesn't make complete sense. The Quantum should be ouputting directly to and external amplifier or powered monitors; your onboard sound should not be involved. This is also oddly stated. It should the Output of the Master bus that's assigned to the Quantum's main outs, not a Send. That said, a Send would work. Are the meters on the master bus showing activity?

Understood. I often do that, and sometime regret it when someone later posts that I overlooked something. ;^)

FWIW, I don't see that here with a wireless Logitech mouse using its proprietary dongle. Maybe depends what you're hovering over in the TV...? Othewise could totally be hardware/firmware/driver-specifiic.

That all works for me, but because it's a "Selection Group", you have to select the group to have the edits apply to the group. This is actually handy because it allows you to still make individual edits to unselected clips in the group or to deselect a subset of the group without having to jump through hoops.

a.k.a. "new code". In an application as complex asa DAW, even the best coders will occasionally produce problematic code that fails to anticipate some use case or set of conditions that leads to bad/unexpected behavior and even the best beta-testing process can miss things. The point is simply that all code changes are potential sources of regression and instability. Obviously there's no avoiding this if the software is to be enhanced, and some changes are riskier than others. In this particular case, I would say the risk is relatively low except that adding new tracks is one of the most fundamental and frequently-used functions in a DAW so any breakage would have a big impact. In any case, I never expressed any particular objection to it; I simply suggested that track templates largely address the need. IIRC, the old forum did have a voting system for feature requests. Here, the 'Like' option should suffice. But the level of participation in the forum these days is so low, I'm not sure how useful any voting system would be.

Seriously? Where do you suppose bugs/instability come from if not from adding new code/features?

Shouldn't you be posting this on Microsoft's forum since a Windows Update precipitated this? That's a lot of vitriol for someone who has apparenly only found it necessary to come to the forum with a problem once in years of using CW. In any case, it seems you missed this post about CW's fix for Microsoft's blunder:

I knew I should have asked for a screenshot that wasn't zoomed in so far to see the full context, but given that the clip gain was having a visual (as well as audible) effect on part of the clip, shouldn't his screenshot show a color change in the clip where the Region FX starts?

Clip Groups. These can be created after the fact or while recording (see record options): https://legacy.cakewalk.com/Documentation?product=Cakewalk&language=3&help=Arranging.34.html