David Baay

Put a pipe "|" symbol between left and right channel names, and they'll show up that way in the Input pick list and in the Input widget after you select one.

In order to bring in the tempo changes along with the notes, you'll want to Open the .MID file with CbB from the File menu rather than importing to an existing project. When you import, the MIDI takes on the tempo(s) of the project. After opeing the file, save it as a "Normal" Cakewalk project.

Step Sequencer is probably a better way of producing a drum track without a keyboard, but if you really you want to "record" MIDI within CbB, you can set the Cakewalk's "Virtual Controller" as input to the track. Clicks on the virtual keyboard can be recorded in real time or by the Step Recorder (not to be confused with Step Sequencer), using either the virtual keyboard or its computer keyboard mode. Recording in real-time is challenging and with either method you need to get familiar with the mapping of drums to the keyboard. Ultimately you won't want to spend too much time messing around with this when basic used MIDI keyboard controllers are a dime a dozen.

Interesting. Definitely an oversight that the Bakers forgot that Home Studio installed to Cakewalk\SONAR (I presume it was all-caps then, but Windows doesn't differentiate). But if the more advanced versions of SONAR could open Home Studio files, I would have thought some sort of EQ "translation" would have been part of that process and would have carried over to Sonar. So I'm wondering if a template with empty Prochannel might still have been involved; like possibly you dragged a Home Studio project into a SONAR project started from a template at some point to update it...? This is normally a good way to update an old project, but not if the template has issues.

This is a bit of a tough call. I would mostly agree with John that if you re-save a template after verifying everything is laid out and working as intended you should be in good shape, but I have occasionally encountered issues in the past with old templates that seemed only to be resolved by building a new one from scratch so I tend to feel it's good to start over once in a while. For the most part I find this happens naturally at least every couple years due to changes in hardware setup, favorite VSTs and evolving compositional focus.

The number you see in the Output widget is the port number, not the channel assignment. Inputs don't show a port number. Sometimes things just are the way they are because no one stopped to think about it. But there's a severe space limitation that would make adding channel number not useful for those with multiport MIDI interfaces that have a need to know what port is assigned first and foremost.

As I mentioned in the PM, Noel made a change to accomodate the unsupported "hacked" condition of having an empty Prochannel when I reported it, and I've had no further issues with old projects that were set up that way, but I'm avoiding it going forward. I'm not sure what was special about that one track in your project that it was still having issues related to that, but the bottom line is that this condition was not something you could normally get into without hacking a preset file or continuing to use an ancient project template that was set up that way, so you can't really hold CW responsible for the resulting instability 10 years later.

Glad to help. When I need to keep track of a channel assignment (usually Output) I've historically just appended it to the track name. It's handy to see it in the widget, but I don't usually have that showing. 99% of the time, Input channel is 1.

If your "friendly" Input name is short enough (like 2-3 characters), there will be room to show the Channel. FWIW, I would call the input channel "restricted" or maybe "filtered". "Forced" applies to the output channel assignment.

Sound on Sound should have taken care of it unless you're also using Punch recording with Mute Previous Takes enabled...?

Yeah, I missed that you were doing it from Windows Explorer. That would have eliminated the need to jump through all the hoops to avoid unwanted plugin loading. I'd still be curious to look at the "un-fixed" project to see if my system has the same issue with AD2 and/or silent synths. All sounds a bit odd.

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: