David Baay

MIDI port assignments can get messed if your USB MIDI devices aren't powered up before booting and/or launching Cakewalk or if they're moved to a different port on your PC. MIDI channel assignments should be stable. Whatever you do, when a project comes up out of whack, don't re-save it. Close without saving, and make sure all devices are present and accounted for in MIDI preferences. If that's not it, you'll need to give a more detailed description of the problem, when it happens, and what hardware is involved.

The tempo needs changing? Or the start position of the clip is off by a fixed amount? What interface and driver mode? If it's a fixed offset of samples/milliseconds, and you're using ASIO driver mode, you probably just need to enter a Manual Offset in Preference > Audio > Driver Settings to acount fo un-reported 'hidden' latency in the interface (not to be confused to 'Timing Offset' for MIDI in Preference > Audio > Sync and Caching). If it's a whole measure, it's probably due to a problem with how Cakewalk reads sample position from the interface when metronome count-in enabled. This seems to happen with some interfaces. Often rebooting will fix it, but I've heard of cases where it's persistent. You might try a different driver mode. If it's actually that the tempo of the recording drifts steadily away from the click over time... I dunno. That would be very unusual.

Got the same result about 30 minutes ago. No confirmation e-mail from either Paypal or Soundspot, so I think nothing went through.

FWIW, V-Vocal is also launching fine and working nominally here in CbB under Win10 though I never use it.

If the PC is new, high specs alone don't guarantee smooth audio streaming. Have you checked DPC latency and done the basic tweaks to prevent CPU throttling and DPC spikes (Disable SpeedStep, C-States, Bluetooth and WiFi adapters in BIOS and set Power Managment to High Performance)?

Are you maybe using a project template or copied project that has reduced input gain to the track left over from some previous project? Input gain doesn't affect live input, which could explain playback being weaker.

Check Preferences > MIDI > Control Surfaces to see if keyboard controller ports might have been taken over due to a previously configured control surface being disconnected.

Hmmm... good one. Any chance you have inadvertently overlapping/duplicate note events causing phasy sound that manifests as a pitch shift? If not that, what happens if you deliberately insert Wheel events with a value of 0 before and through the note to hold the pitch constant?

The only other suggestion I have is to make sure you're inserting it in the synth rack, and not in the FX bin of an audio track. I've seen the symptoms like this when synths are inserted in FX bins. Cakewalk supports this configuration but it's not the preferred setup.

Well, seeing the IK sale coincidentally going on at the moment. I broke down, and actually purchased MODO bass. It's working fine here, but I did notice immediately that - like a lot of bass synths - it's programmed to sound an octave lower than standard keyboard tuning and doesn't play below the standard low E on an electric bass. So any notes below MIDI Note# 40 ( the second E up from the bottom of an 88-key controller) won't be heard. I haven't yet figured out whether the synth has a transposition option built in - didn't see one at a glance. Otherwise, it's all good here even at very low audio and MIDI buffer settings. EDIT: Spent some time getting up to speed with videos and playing around, and realized the transposition is necessary to make room for keyswitches. All in all a very cool and good-sounding instrument. I just love modeled stuff.

I can almost hear Spock's eyebrow going up. ;^) If MODO is fine in other DAWs, and Cakewalk is fine with other synths, the logical conclusion is that there's an interoperability issue between the two, but it's not possible to conclude that the issue is attributable solely to one or the other. It takes two to tango as they say. The first thing I would suggest is raising your MIDI Prepare Using Buffer. In SONAR the default was 250ms, which was too low for some synths/FX in some situations. Recently, the MIDI buffering process was re-engineered so that that buffer values are lower and more representative of what's actually going on. I believe the new default is 50ms, and the buffer is supposed to increase dynamically 'under the hood' as needed. But I wouldn't be surprised if that adaptation is still imperfect, and suggest you increase it manually. Try 100 or 200, and work down from there to see if you find a sweet spot. Also, if it has both VST2 and 3 flavors, you might try the alternate one. If that doesn't get it, I'll download the demo and see what I get. Have been meaning to do that, anyway. I'm pretty sure some others around here are using it without a problem, so there's hope it can work for you as well with the right configuration.

I usually zoom with Ctrl+Alt+Scroll Wheel, but just tried the buttons and cannot reproduce any issue. And I don't recall seeing any other reports of this. In order for the Bakers to fix whatever you're encountering, you'll need to give them a project and/or recipe that reproduces it consistently.

So a quick Google indicates the x32 includes a 32-channel USB audio interface. Dumb question, maybe, but since you're new to audio recording... Did you install drivers for that interface and record individually miced instruments to separate tracks in Cakewalk or did you just record a stereo mix via analog output from the x32 into the line input of your laptop?

Check the section of the keyboard manual on Auto Accompaniment.

You just need to be able to log in to Cakewalk Command Center, and you can re-install any legacy content. EDIT: I just checked, and the Nomad plugs are part of the Studio Mixing FX Suite under the SONAR branch (Platinum in my case).

If you have X2 Producer, I think you have the Nomad BT Chorus...? EDIT: Oops, maybe not. looks like that was an X3 add-in.

I like it, but the drums (especially cymbals) are pumping and breaking up in a way that makes me feel a bit queasy - overcompressed I would guess, and maybe also with some distortion/bitcrusher FX that's a little overdone...?

Not much of a mixologist, myself, and the production quality of all your stuff is generally a cut above, but FWIW: I agree with Lynn that the drums sound like they're in a dfferent space, but given the spacious ambience on other instruments, feel they're maybe a bit too dry. The snare, especially could use a little more 'tail'. I also agree with emeraldsould about the repetitiveness of the hi-hat beat over the first couple minutes, but I think it's maybe more about the lack of space in the pattern. I much prefer the later arrangement when that 8th-note pattern is taken up by a ride at a much lower level, and even more so the sparser pattern starting at around 2:35 when the ride drops out - it suits the slow tempo better. Maybe start there, and build to the busier pattern. A beautifully crafted piece otherwise.

Yes, as mentioned, you can send from the bus to an Aux track as well. That will give you all the track FX (but not the bus FX unless you output it to the Aux track). If the track you want to use already exists, send the bus to a new Patch Point, and then set the input of that track to the same Patch Point.

Yes, an Aux track will do it, but you still need a separate audio track (or audio side of an Instrument track) to host each instrument's output. Not sure if you were hoping to eliminate multiple tracks...? Ad a send to a new Aux track from one of the instrument tracks, and then add sends from all the other tracks to the same Aux track, disable input echo and arm that track to record. The sends will all be Post-fader by default so they will follow mixing moves you make on each track, but they'll be dry. In order to have track FX included, you would need to temporarily output all the tracks to the Aux (leaving input echo enabled), or to a bus that sends to the Aux and outputs to Master

If input quantizing is enabled, the record arming button in the track will have a Q in it. Your's doesn't so that's not it. And having snap enabled should have no bearing on what gets recorded. But I'm not really understanding what your screenshot is showing. The durations look very different, but it's hard to see that start times have been quantized at that zoom level. And the recording preview screenshot doesn't show the timeline so it's hard to relate the two.

Hmmm... I tried it and got the same result. Then tried a second time, and got the .cwb as expected. Not sure what that's about. Personally, I've always preferred just zipping up the project folder. Zip files are generally smaller, more reliable, have no limitations on saving audiosnapped clips, and allow selectively extracting individual files if desired.

Display Multiple Controllers and the Edit Filter are only active when the Controllers pane is closed and controllers are displayed in the Notes pane. With the controller pane open (as your screenshot shows), you just click the 'button' for controller type that you want to see/edit.

Keyboard shortcut 'N' toggles snap on/off.

That's an interesting function I've never used. Seems to work consistently here. You are aware that the percentage quantization increases (or decreases) the further you drag up a max/min of +/-100%, right? I just noticed you wrote 'With the Timing tool...'. I used the Stretch tool per the documentation.