msmcleod

Do you have the spectrum analyser turned on in the console view? Try turning it off - on some machines this can make a huge difference.

I've had this issue in the past a few times - in all but one of the cases, cleaning the contacts solved the issue. The case where it didn't work needed both the contact replaced on the PCB (using conductive silver paint), and the rubber contact switch replaced (this is literally a matter of lifting the old one off and putting the new one in place). Before opening it up, first try (in this order): 1. A vacuum cleaner across the keys 2. Spraying under/between the keys with a can of compressed air. 3. Try spraying some contact cleaner or WD40 in there while wiggling / playing the keys. WD40 is usually better than contact cleaner as it won't damage the carbon on the PCB / rubber contacts. Don't use switch cleaner - it's way too harsh. If all those fail, it's time to open it up and clean the contacts with Q-tips. If the contacts themselves are damaged, sometimes you can get away with using a pencil to replace the carbon, but that won't last forever... you can buy a conductive carbon (or silver) pen for $10 - $20 which will do the job properly. Obviously check everything with a multi-meter before you close up.

Time delay in ms is currently in development. It probably won't make the next update, but hopefully the one after.

By far the best way to expand the 1820 is the Behringer ADA8200.

This seems overcomplicated to me. Why not just create presets in the Track Manager? You can then select which preset to use either using the Track Manager button drop down menu (in Sonar), or the Track Manager itself in either CbB/Sonar.

I think the reason this was required was so that the command knows what automation to snapshot. Otherwise it has no way of knowing.

There shouldn't be any need to go to these steps. Click on the Patch browser button, and you can choose definition for any .ins file you've imported, then search/select the patch from the list:

Have you changed the Velocity trim (MIDI gain) control on the track?

This has been fixed for the next update.

It's working fine here, however the documentation is somewhat misleading: To create a snapshot of a track or bus parameter 1. Move the parameter control to where you want it. 2. Move the Now Time to the location where you want to create the snapshot. 3. Right-click the control and choose Automation Snapshot in the pop-up menu. You don’t have to write-enable the track or bus module. An indicator will appear on the control to show that automation has been added, and a node will be added to the control's envelope on the track. 4. Make sure the appropriate Automation Read button is enabled, play your project and listen to the results. You can undo the snapshot by using the Undo command, or by taking another snapshot at the same Now Time. This is all true for right-clicking the control, however for the keyboard shortcut to work you do have to write enable the parameter (i.e. within the corresponding automation lane). The keyboard shortcut will take an automation snapshot for all write-enabled parameters.

I'd seriously consider shutting your PC down overnight. I used to have a PC tower that ran my email / source code / media server that was on constantly. I replaced it with a fanless low-powered PC primarily to cut down noise, but the saving in power usage was shocking... like several £100's over the course of a year... enough that I could buy a new guitar every year if I wanted.

Thanks - found the issue, and it's fixed for the next update.

Can you send a copy of the project to @Jonathan Sasor so we can investigate?

Can you show more of the dialog? In particular the "What to Export" section.

Are you sure you don't mean Sound on Sound? - Overwrite mode literally overwrites what you've previously recorded. - Sound-on-Sound allows you to build up a track by recording several takes, whilst hearing the previous ones - Comping records several takes while muting the previous takes, so you can quick-comp the takes choosing the best bits afterwards.

Actually, it is setting the Time+ to a negative value... but the key difference is to also be able to specify this in milliseconds, rather than the current implementation which is in musical ticks only. A lot of orchestral libraries require a negative millisecond delay. This is to account for things like the bow touching the string on a violin before it actually plays the note - i.e. you get the note to start early so you hear the "bow" effect, but the actual musical sound starts playing on grid. A delay in musical ticks is fine if you've got a single tempo in your project (you just workout how many milliseconds a tick is for that tempo, and enter that tick value), but if you've got tempo changes, then the actual length in milliseconds of each musical tick will change with every tempo change. Also, I believe the current implementation allows you to enter negative time, but doesn't actually respect it (it clamps it to zero). The workaround in CbB is complicated. Essentially, you have to add a positive delay for all other tracks, equal to the tick equivalent for the largest millisecond delay. For each tempo change, you're going to need a complete new set of tracks with a different delay. As to why it's not here yet - simple answer, is it's really complicated. The MIDI engine schedules groups of notes ahead of time in time windows (based on musical ticks). A negative delay requires scheduling notes early, meaning they might need to be added in an earlier time window, with the reverse being true for positive delays. Get it wrong, and you get doubled notes or missed notes (we suffered both issues in the early implementations of the negative articulation delay). Not only that, each and every MIDI event needs to be time adjusted, converting the millisecond value to its new tick value - this requires a lookup of the tempo map for every event. Add looping / user seeking in the timeline, and it gets complicated really fast.

If you uncheck "Always Echo Current MIDI Track" in Preferences->MIDI->Playback and Recording, it'll stay set to None.

When this happens, I just record a cover song... not only does it help to get back into the swing of things, it also gets your muscle memory re-engaged without having the pressure of being creative. There's nothing more frustrating than not being able to "drive" your DAW without having to to think about it.

Glad you sorted the issue. What plugin manufacturers should be doing if possible, is ensuring their automation parameters match between VST2/VST3 - I guess this isn't the case for some of your plugins, which is likely the reason it didn't work.

My bet is you're using a Workspace that is hiding surround. Try setting your Workspace to "None".

I think it's more likely to be a plugin version issue than a Cakewalk version issue, especially if the plugin went through several upgrades from an earlier version on your previous machine.

FWIW, you do have the following options: - Use "All External Inputs", which will exclude any soft synths. This option appears as soon as a soft synth is inserted. - Use an input preset

Back in the hardware days, you had three flavours of MIDI ports: 1. MIDI In, MIDI Out, MIDI Thru - where Thru was an exact copy of what came from In, and Out was whatever the device generated 2. MIDI In, MIDI Out - MIDI Out only had what the device generated 3. MIDI In, MIDI Out/Thru - here, the MIDI Out had both what came from MIDI In and whatever the device generated. There is no MIDI Thru in software synths, so it's up to the plugin vendors to decide what their MIDI Out does - i.e. some behave like (2) above, and some behave like (3). If you have one that behaves like (3), then the synth will essentially repeat whatever it received from the MIDI track. If you have another track that is set to "All MIDI Inputs", then it'll receive MIDI from that soft synth. This isn't a bug - it's just how it behaves. You just need to be aware of your MIDI routing.

@Kurre is correct - the option wasn't available in CbB. CbB doesn't support different DPI settings - instead it tells Windows that it's not DPI aware, and Windows automatically scales the UI accordingly. For the most part it does a pretty good job, but can lead to fonts/icons being slightly blurred as part of the scaling. Sonar on the other hand is DPI aware (a mammoth development task), which is why those options are available. Dealing with Plugins, especially those that are DPI aware and/or support scaling is tricky, as depending on how the plugin is doing it's scaling, Sonar's DPI adjustments can end up fighting with the Plugin's DPI adjustments. For 99% of plugins, there's usually a setting that will work for the plugin - iZotope being a notable exception, although I believe they are aware of the issue and are working on it (it's not just Sonar that has scaling problems with some of their plugins).

FYI - to stop MIDI Output being enabled on newly inserted synths: 1. Open Synth Rack View 2. Click on the "Insert Synth Options" dialog button 3. Ensure "Enable MIDI Output if Available" is unchecked, then click OK.