msmcleod

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!

@norfolkmastering / @Sal Sorice / @Heinz Hupfer There are a couple of things in the pipeline that should improve the look of Sonar vs CbB. 1. We'll be including a "Tungsten Classic" theme that more closely matches the colours of CbB, and certainly to my eyes has a more preferable contrast to the new Tungsten. 2. We're using a different graphics framework not only for the vector images, but also for drawing text. This is the same framework we're using in Next for cross-platform support. Unfortunately, because it's cross-platform, the text rendering doesn't look as good on 1080P as it did in CbB. We have a plan to fix this and will be addressing it very soon.

I don't think you'll be able to do this with a single pedal, but you could probably do it with two: 1. In Preferences->MIDI->Playback and Recording: Make sure "Allow MIDI Recording without an Armed Track" is checked 2. In Keyboard shortcuts: assign one MIDI note to "Insert->MIDI Track", and another to "Record". You should make the keys as high as possible (e.g. F#9 / G9 ), as low keys are quite often used a key switches. 3. Assign your pedal to send out the notes assigned in (2) Now you'll be able to hit one pedal to insert the MIDI track, and the other to record. Of course if your MIDI pedal device can send out one note, wait 0.5 secs, then send the other note all from a single pedal, then you'll be able to do it with a single pedal.

This has been fixed now (it was reported by the beta team). I think a new BSP release went out yesterday with this fix... if not, it'll be imminent.

I don't practice nearly enough to play barre chords perfectly every time, but one thing I have found is that they're not always desirable in the context of the song - so quite often I avoid them, preferring to limit my chords to 3 or 4 strings. If you've a bass guitar is dictating the root or inversion of the chord, question whether you need the guitar to double that up. If you've got a keyboard pad going on as well, even more so. Also from a mixing point of view, having less instruments fighting for the same frequencies can make the whole mixing process much simpler.

Windows 7 does support VST3, however Sonar 8.5 does not. IIRC, Sonar X3 was the first version of Sonar to support VST3. You might be able to use something like the VST2 version of Blue Cat's Patchwork to wrap it up for use in Sonar 8.5, but I can't say for sure without trying it. I'm also not sure if Speakerphone will work properly when hosted this way. [EDIT] - At least in SONAR X2, the VST2 version of Patchwork will host VST3 plugins.

FYI - before soft synths were a thing, and multi-timbral modules were king... Cakewalk had this for Windows 95, that would do the "two-finger" trick and play a backing to the speed of your playing. It didn't need to be a two finger thing either - if your part was already in 8th notes, that would be enough for it to work it out.

It has been fixed in Sonar too, but is much less likely to happen if you either have TTS-1 installed already, or have a default synth set. To set the default synth, just insert a Simple Instrument Track, right click on either the synth rack entry, or the track itself and select "Set as Default Synth" in the context menu.

Also, just to clarify: Melodyne 5 does not work with Windows 7 Melodyne 4 does not work with Windows 11 The only OS that works with both v4 & 5 is Windows 10.

@David Baay is correct - but it's only the first occurrence of those CC's / Program Change messages that is transferred to the track controls. Any subsequent events are left intact.

In order to use any plugin that uses iLok, you need the iLok License Manager installed. As part of that installation, it installs the iLok drivers, which usually requires a reboot. You can download the installer here: https://www.ilok.com/#!license-manager