msmcleod

There is actually - check out the slider at the bottom of Customization->Display within Preferences.

It's now been implemented in the latest version of Sonar - i.e. you can now edit the External Insert description from within the plugin dialog, and it'll update the name in the FX bin when you close the dialog.

When Live Articulations are active on a track, any MIDI Transform articulations at the current Now Time will be applied to live MIDI input. This is useful for auditioning, and overdubbing on existing MIDI tracks with articulations. MIDI Trigger based articulations (i.e. key-switches) are not affected by this button. When the transport is running, they'll be sent out as usual - when the transport is stopped, they can be applied by clicking on the articulation section itself.

FWIW if I'm moving everything in time by a few bars, I find Project->Insert Time does the job for me. Under the hood, it's a far simpler operation than ripple edit, so there's much less chance of something going wrong. Another option is to use the arranger.

I'd suggest: - Come up with a common list of plugins, and create a custom plugin layout that only uses those plugins. Make sure you're all only using those in your projects. - If you're using Sonar, use the new CWZ format for sharing, otherwise zip your project folder up - store this file in a common cloud location. Depending on your amount of cloud storage, you could consider using a naming convention for each version of the project, e.g.: 2024-03-26_15:40_XYZ ... where XYZ are the initials of the band member. This has a few advantages: 1. When ordered alphabetically, they're also in date order 2. Doing a "Save As" to this new filename will automatically "clean up" the audio files so your project zips will be smaller. 3. You can open several versions in CbB/Sonar at once, then pick & choose which tracks you want to keep.

Pressing F1 in the Mackie Control Dialog ( Utilities Menu -> Mackie Control 1 ) will show CbB's Mackie Control help. It's worth mentioning that the button mapping is different for each DAW, so what is labelled on your x-touch may not match what Cakewalk expects. For the full-size x-touch, and MCU / MCU Pro, you would normally use an overlay that fits over the buttons to relabel them. Several companies do them ( check eBay!) - but here's one example: https://store.birchwoodstudioandevents.com/Sonar-Overlay

Bear in mind that your reference track is likely a fully mastered track. Most mixed tracks are quieter than a mastered track in order to give headroom for the mastering process. Rather than trying to match the levels of your reference track, lower the volume of your reference track to match your song ( say around 3db - 6db ). This will give you plenty of room to play with when you come to master your song.

This can happen if you changed the USB port from the one you plugged the device into originally. Windows associates the driver with the original port, and gives this a new name because it's now in a different port.

The range of the pitch wheel is fixed between -8192 and + 8191. How this is interpreted as far as pitch changes is up to the synth - it could be either a per patch or global setting. Most default to 2 semi-tones. Not all synth plugins allow you to change the pitch wheel range, and not all will allow up to an octave.

Another option is to record with a piezo pickup, then run the audio through an IR to emulate it going through a mic. Something like this will do the job: https://pasttofuturereverbs.gumroad.com/l/ovkEn?layout=profile Any reverb or cabinet plugin that supports IR's will do the job, although I found I had to increase the gain to the plugin significantly (using an FX chain gives you up to +12db pre/post gain).

Your picture cache directory is probably full. The picture folder is specified in Preferences->File->Audio Data. Go to this folder in Windows explorer, and delete all the .WOV and .TR2 files in there. Any waveform pictures that were in there will be recreated the next time you open a project.

In general Microsoft is very good with backwards compatibility of software. SONAR makes extensive use of Microsoft libraries, which makes compatibility far more likely. I've running SONAR Platinum on Windows 11 without issue. Device drivers for your audio device might be a different matter however, so best to double check there are Windows 11 compatible drivers for your audio interface.

What's the output of your Master bus set to?

Not only can you have different delay times for different instruments, you can have different delay times for different note ranges and/or velocity ranges within the same instrument. This can be useful if you have a string sound that has a slower attack at lower velocities.

It's in the oven....

If you want to keep meta data such as tempo, time signature or key signature, don't export as MIDI - "Save As" instead using the Standard MIDI File format.

Sonar will refuse to install on Windows 7. The new scalable UI relies on Windows API's that are only available in Windows 10 ( version 20H2 I think) and above.

The cheapest interface that will give you acceptable results is probably the Behringer UMC22. Personally, I'd avoid it and go for a second-hand Focusrite Scarlett 2i2 or Scarlett Solo. I'm still using 1st generation Scarlett interfaces (2i2, 6i6, 18i8 and 18i20), and they're solid good sounding interfaces. The 2i2 is now on the 4th generation, and they're also (apparently) the world's most popular interface... so finding a 1st or 2nd gen interface on eBay or Reverb should be easy. Also, if your guitar has a single-coil pickup and you're less than 2 - 3ft from your laptop/PC, you will likely get a buzzing noise - this is the guitar pickup picking up RF interference from the PC. It's even worse if you're using an old CRT monitor. Sometimes, running on battery (if it's a laptop) can help, but ensuring you're a couple of metres/6ft or so away from your PC will solve it.

IIRC, I think the answer is either no, or at the very least it won't affect everything. I think it's an overhang from the pre skylight interface days. Maybe @Ben Staton can clarify?

Auto-save works in two ways: 1. Automatic saving based on time and/or changes The automatic saving will save a temp copy called "Auto-save Copy of myproject.cwp" when the auto-save criteria kicks in. It leaves the original copy of your project alone, but the "Auto-save Copy of..." file is overwritten with the latest version every time it auto-saves. Due to how some plugins are (badly) implemented, it's probably best to leave the "changes" at zero, and stick to a time-based auto save. 2. Project versioning Project versioning works slightly differently. Every time you manually save, it'll rename your current project file on disk (adding it's last modified date/time as a file extension), and saves your current project using the original project filename. You can specify how many versions of the project you want to keep on disk - older versions will be deleted once it gets beyond the number of versions specified. There's nothing stopping you using both methods at the same time. These options can be found under Preferences->File->Advanced: I've often questioned why these methods are separate, but actually the more I think about it, it does makes sense: The auto-save is a backup copy you can go back to if something goes wrong (e.g. crash/power outage etc) The project versioning is a deliberate history of your saves, allowing you to essentially "check-point" your project every time you decide to save. If auto-save was also using project versioning, there would always be the danger of either filling your disk up with loads of project files, or deleting an older version of the project that you really wanted to keep.

FWIW the soon-to-be-included Tungsten Classic theme has distinct button backgrounds, rather than the transparent background of the newer themes - it's no where near as flat/2D looking. It's not exactly the same as CbB, but when running the two apps side by side, they look very similar.

There's no hard & fast rule for specs, as it's totally dependent on what you're doing. As a general rule however: If you're low on RAM, avoid any sample based synths or any plugin that loads lots into memory. Also Save / Reload your project regularly (or clear your undo history). If you're low on CPU/cores, limit your plugins (that includes soft synths), and avoid CPU hungry reverbs - maybe consider a hardware synth module Also, once you start running out of memory, you'll see a drastic drop in CPU performance as it attempts to swap blocks of memory to/from your HDD. So don't assume a CPU problem is to do with plugin CPU usage - it could be caused by low memory. I would say the bare minimum is 4GB / 2Ghz / 4 Core... but only if you're recording just audio, using hardware MIDI, and/or using very CPU-lite soft synths that are either not sample-based, or have a very small sample set (e.g. TTS-1, S-YXG50 etc ). The ProChannel / Sonitus suite should be fine for FX for most purposes. I managed to record 16 simultaneous audio tracks while playing back 32 audio tracks (20 mins worth), on a 8GB/2Ghz /4 core MeLe silent PC (only slightly larger than a compact cassette case). I did this using both CbB and Next. I've also done the same on a 4GB/2.2Ghz/dual core laptop... but this was running Sonar Platinum 32 bit.

I'm pretty sure you can't. The file format is different. However, if you're hosting a VST3 inside a VST2 plugin like Patchwork, then saving the Patchwork state as a preset should also save the state of all VST3 plugins its hosting.

The fix will be based on DPI rather than resolution, so yes, it should.

I've tried this in the past, and it works a treat... it's difficult to unlearn 40 years of bad habits tho!