msmcleod

No, Cakewalk actively prevents feedback.

It was my error! I should have said go back to 4/4 at measure 20 !

It could be that some of your plugins are using the new "put the plugin in a .vst3 subfolder" structure that Steinberg now recommend. Although Cakewalk's VST Scanner has been fixed to work with the new structure for Sonar, the new version of the VST Scanner wasn't packaged with the last version of CbB. I believe there will be a new CbB update fairly soon, and the new scanner will be bundled with that when it's released, but in the meantime you can download it here:

FWIW I've found Antares plugins have never played well with SONAR/Cakewalk/Sonar. I've set the three Antares plugins I've got to use JBridge, and this solves it for me, although it does mean I'm stuck to using the VST2 versions.

It looks like 80bpm is the correct tempo for the next section. You should be able to add a meter/key key change at measure 20 of 1/4, then a meter/key change of 4/4 at measure 21. Measure 20 then becomes one beat long, and the "WANT HERE" then starts on measure 21. Alternatively, add a meter/key change at measure 18 of 5/4, and the a meter/key change of 4/4 at measure 19 - in this case "WANT HERE" will start at measure 20.

What you need is a tempo map that matches what you're playing. What I'd do as a first try: 1. Set the first tempo to 85bpm Assume the period between start of the silence and the 80bpm section is 2 measures of "n" bpm, and for arguments sake say it starts at measure 100 2. Set the now time to measure 99 and use "Set Measure Beat at Now", setting the measure to 99 3. Set the now time to measure 100 and use "Set Measure Beat at Now", setting the measure to 100 This is essentially reinforcing that the tempo is still 85bpm up until measure 100 4. Set the now time where it starts again at 80bpm, then use "Set Measure Beat at Now", setting the measure to 102 At this point, it should have added a tempo entry for "n" bpm that makes the gap between the silence and where it starts up again two measures long. 5. Add a 80bpm tempo change at measure 102 What you'll end up with: 1. The first part of the song at 85bpm 2. The silence / intro to 80bpm part as two measures long (probably at a fairly small bpm) 3. The 80bpm starting again on the next measure.

FWIW, I've got an old Intel Core Duo Dell Laptop running Windows 7 32 bit, SONAR Platinum connected to a Yamaha 01X, i88x and Behringer ADA8000. I've no problems recording projects (up to 24 simultaneous tracks) on the laptop and going to either CbB or the new Sonar for mix duties or further editing. I can even re-open the project in SONAR Platinum for further overdubs, however if I think I might have to do this, I try to avoid using any of the new features missing in SONAR Platinum. Most features are fine though, with the notable exception of the Arranger - for that I just save the arranger track as an arranger template, so I can re-import it again. Nested track folders can be tricky too - the folders will get flattened out when opened in SONAR Platinum, but they should keep the hierarchy when loaded back into CbB/Sonar as long as you don't move tracks around. Obviously the older the version of SONAR, the more features you'll "lose" if you save the project in the older version... and as @Jonathan Sasor says, avoid 32 bit DirectX plugins apart from the Cakewalk stock ones (e.g. Sonitus).

For individual clips you can use scrub.

If this is in Sonar, expect some big improvements in the next update. We found a bunch of areas that were causing slow operations in larger projects. In CbB, turning off the audio engine and/or closing the synth rack can speed things up significantly.

Whether 1TB is big enough all depends on your usage. I've got a 4TB SSD in my DAW machine, partitioned 512GB for my C Drive, and all my Kontakt libraries/sample based synth data on the 3.5TB "E" drive. My projects are on a separate 1TB SSD "F" drive. It's worth mentioning though, that all I have on my C drive is DAW related programs - i.e. SONAR, CbB, Sonar, MixCraft and Studio One... plus the odd utility... so no office programs at all. If you're using your PC for anything else, then you want at least 1TB for a C drive, and a separate drive for your data.

IIRC SONAR X1 Expanded was a version of X1 with an early implementation of the ProChannel. The X1e update was available to all versions, but you may find there is a specific X1e update for SONAR X1 Expanded, just as there was for artist/professional/producer.

It's a known problem with Izotope plugins, and not just with Sonar either... other DAW's are having DPI problems with Izotope plugins too. Izotope are aware of the issue, so I guess its just a matter of waiting for them to implement DPI support in their plugins. The only workaround is to disable DPI awareness in Sonar - this essentially makes it behave as CbB did... but it'll affect the entire app and all other plugins too. Personally, I'd just avoid using Ozone 11 in my projects. If I need it for mastering, I'll run it standalone with a stereo mixdown of my project. I find Ozone grinds my machine to a halt on the best of days, so I avoid using the VST for that reason too.

Using "Fit Improvisation" with real recorded material is always going to give unpredictable results. It's designed to be used on a track with only quarter notes recorded, and at every quarter note - in other words, a track where you've "tapped along" to the beat. From the docs: "To use this command, you must record a reference track containing a single clip that matches your original track or tracks but has only a single note on each beat boundary. You should make sure that the reference track has one event for every single beat, with no extra beats or missing beats. The first beat of the reference track should be at 1:01:000"

Windows doing updates in the background? This catches me out all of the time.

FX plugins can only be inserted on to a single track, which is why the track name can be displayed. Synths can be "fed" from multiple tracks - i.e. I could have 16 or more MIDI tracks feeding a single synth instance, along with the audio track that it is fed to. This is why a track name isn't displayed.

In my experience, a laptop's onboard sound device is fine for playback/mixing but unsuitable for audio recording in most cases - the electrical interference alone makes this a blocker. Use WASAPI Exclusive, as most ASIO drivers for on-board devices are no good. Latency won't be as good as ASIO (but not that far off ), but it may not be low enough for recording virtual instruments if you're particularly fussy about timing. In my experience, synth pads are fine but piano is a no-go. One thing to add though - it's unlikely the headphone amp on a laptop will be good enough to drive professional headphones, so bear that in mind. A small portable audio interface is a far better solution. Tascam, Focusrite, Presonus, Zoom and M-Audio all do entry level 1 or 2 channel interfaces that are pretty small (about 2-3 times the size of a mouse).

You're better off using Articulation Maps if you're using Ample Guitars rather than relying on MIDI notes. @Creative Sauce did a great tutorial on how to use them with Ample Guitars:

All I can say is, whatever size you build it's never going to be big enough. I started off with 22' x 10' and it's ended up tiny inside, although perfectly useable if I'm the only person in the room. I've got another building which is approx 16' x 10', which I was hoping to put a drum kit in... but with sound insulation added it's gonna be too small to get a kit inside. I may still put a drum kit in it... but I'll be limited to using it when my neighbours are away (thankfully there's only two nearby). FWIW you can get great results from a log cabin with a room inside a room which can cut down costs significantly. My 16' x 10' cabin cost around £6K - soundproofing it would probably add another £2 - 3K.

Essentially, you need to create a tempo map for the pre-recorded audio. There are three ways to do this: 1. Drag the audio track to the timeline, and let melodyne extract the tempo. I can't remember if this is the case or not, but you may also need at least Melodyne Essentials for this to work if you're using v5. v4 should be fine. 2. Use "Set Measure/Beat at Now". For this, you move the now time to the start of each measure/beat in your audio file and call "Set Measure/Beat at Now" specifying the measure/beat in the dialog. Start at the beginning and work your way through to the end. You can try doing this for each measure only, and then drill down to the beats if you need more accuracy. 3. Create a new MIDI track, arm it and record a single note or drum hit for each beat while the audio is playing. Select the MIDI clip, then from the main Process menu select "Fit Improvisation".

... and it works surprisingly well. I can crank up my two 150W monitor speakers to full, walk around the outside my studio, and hear practically nothing. What it doesn't cope with as well is incoming low frequency noise, e.g. (real examples from personal experience): - People revving their Harley's like crazy - Guys digging up the road up to 1/2 mile away - Visiting US destroyers trying out their fog horn - Low flying Chinooks ... but perhaps the most baffling one, was a phantom kick drum that I kept hearing... turned out my neighbour's kid was practicing drums on his acoustic kit, inside his house around 80 yards away. The only thing that was getting through was the kick drum. It's worth noting that none of these would likely make themselves heard in a recording, and if they did they'd be drowned out in the mix (or you could easily gate them out).

If you clone the partition ID's as well as the data, then most activations should be fine. This is why I use Clonezilla rather than other "move your OS drive" utilities that come with new drives. Clonezilla clones everything, whereas some other utilities only do the partition contents. When cloning to a larger drive, I let Clonzilla do its thing, then use PartitionWizard (free edition) to resize the partitions to use the extra space.

This isn't a network issue - it's probably down to a corrupt plugin layout database file. The file is called Library.db and can be found in %APPDATA%\Cakewalk\Library If you rename this file to Library.db.corrupt (while Cakewalk isn't running), a fresh one will be re-created on startup. If you're lucky, there may be a backup file there, in which case make a copy of that and rename it to Library.db

It says your sign-in was successful, which is different from activation. In other words, it recognises that you have a valid user account, but it appears you don't have a valid paid subscription?

All CC's such as Pan, Modulation etc are channel wide, whereas velocity is specific to a particular note. There's nothing we can do about this - it's the MIDI spec.