David Baay

Sounds like the problem from back in Platinum era with 'Remove DC Offset During Record' in Preferences > Audio Playback and Recording. As I recall, it was fixed at some point, but maybe still manifests in some cases. That, or did you maybe enable the experimental 'Aggressive' ThreadSchedulingModel=3 in AUD.INI (Preferences > Audio > Configuration File)?

I usually have Follow Snap Settings enabled, but just tried fixing at 1/8, and it persisted after save/close/re-open as expected. My guess is you're using a Workspace, and need to resave it. I currently have Workspaces set to 'None' so per-project settings reign.

WASAPI Exclusive mode is probably the best place to start for onboard sound users as it's full supported by the Bakers. That said, I was initially suspicious about the possible involvement of ASIO4ALL in this issue as well, but the faulting module is Sampletank, and I would not expect that loading samples would affect the audio driver state.

I should, unless maybe you have Transport Seeking Stops Playback enabled in that same options menu.

Have not browsed extensively, and I've mostly been playing with Syntronik inserted directly rather than loading via SampleTank. Will try using ST4 some more. I only installed the VST3. As I recall, you have to unhide VST2s with the checkbox, then also un-Exclude them individually, and then you can Exclude the VST3 if you don't want to see it.

New one on me. Hard to imagine it would affect one some project unless those affected projects all shared a common ancestor, with lurking corruption. Can't really think of anything that would cause that otherwise or any procedure that might 'break the spell' other than things you have probalby already tried like archive/unarchive, delete/undo, solo/unsolo the whole project from the mix module or by quick-grouping, etc. Maybe save as a bundle, and open it from a new location...? If the problem was really precipitated by installing Studio One, I would wonder if maybe it overwrote the a version of the C++ runtime library that CbB was using or something like that You might try re-installing Cakewalk. But many of us have Studio One as well, and no problems with CbB.

As noted earlier, I finally got to the bottom of my bad-template issue by using the hardware port monitor, MIDI-OX . You could do the same by routing a single misbehaving MIDI track out to a hardware MIDI loopback path and back in to another MIDI track that echoes to the VSTi. Then monitor the MIDI IN using MIDI-OX. One way or another, I think you will find some unexpected MIDI controllers in the stream, and will need to do further investigation to figure out where they're coming from.

Your issue is pretty clearly related to MIDI controllers in some way. The OP indicated his issue affects recorded audio tracks a well, so not likely to be related.

- Assign the MIDI track output to the hardware synth port. - Connect audio output(s) from synth to audio interface/soundcard input(s). - Assign the input of an audio track to the interface input (left, right or stereo as appropriate). - Arm the audio track to record. - Start recording (R). If you want to monitor the synth's output through Cakewalk (usually the case), enable the Input Echo button the audio track.

Very unusual. Try recording a short bit of audio in Cakewalk (flatline with no input is fine, mono or stereo), drag and drop to your desktop, and then drag back in and drop it into an open area of the clips pane.

Cool. Glad to help. I got the 700NX a few years ago, replacing an RD-300s that I bought new in 1988! It was still going strong; I gave it to my son-in-law. I just had the itch for something new with more state-of-the-art touch and acoustic piano sounds. Apart from using it as my main controller all those years, I mostly used the E.P. on the 300s; the acoustic piano was pretty sad by modern standards, but the E.P was great, and I haven't found a plugin to equal the built-in chorus on that board.

Soloed something with Dim Solo enabled? Are the levels low on the master and/or hardware output bus meters?

The next thing that's going make your head explode is that it doesn't work in lanes. ? Just make your cuts in areas of low average amplitude, and you shouldn't have too much trouble. Splitting at zero crossings is no guarantee you won't get a pop. If the surrounding amplitude is high, stopping the driver dead at zero as it comes back to center from a high peak is a more radical discontinuity than dropping it to 0 by splitting it where the amplitude is at say -30dB.

Okay, that clarifies the scenario, and I can reproduce that specific case; - Open an existing project with it enabled. - Start a new project from a template with it disabled - Close the new project. - Re-save the existing project. It seems to only happen when a new project is started from a template. Opening some other existing project with it disables does ot have the 'override' effect that starting new from a template file does. The workaround will be to enable it in all your templates and re-save them one at a time, and you should be good after that.

Yes, it's normal. I brought it up with the Bakers early on when real-time synth recording was first introduced, and they pointed out that they can't differentially compensate audio generated by existing MIDI vs. live input MIDI when they're in a common stream from the synth. Since the intent of synth recording was to allow realtime recording from a live MIDI performance the compensation is based on that scenario.

Several options: - Set the intermedate size of the multidock larger by dragging the divider up. This will be the default size whenever it's opened. - Shift+D to maximize the multidock. - Don't ever close the PRV tab. Use D to open and close the maximized multidock, and use the PRV tracks pane to change tracks. - Undock and 'unfloat' the PRV, maximize it, and Ctrl+Tab between it and the Track View. - Define a screenset with an undocked, floated and maximized PRV (full-screen), and switch screenset with number keys. - Various combinations of the above are possible, also.

Yes, the issue with virtual ports getting mixed up may have been be resolved already, but at this time, Cakewalk will still re-assign tracks that use hardware MIDI ports to the first virtual port it finds in the project if the hardware isn't online.

By default, Cakewalk uses the ASIO buffer size when processing audio offline. Too small or too large can cause problems for some plugins. Try a moderate setting like 256-512 samples, and if you get more consistent results, you can set a corresponding non-zero value for BounceBufSizeMsec= parameter in the AUD.INI (Preferences > Audio > Configuration File) that will alway be used for offline rendering, regardless of your setting for realtime playback (BounceBufSizeMsec=0 tells it to use the realtime buffer size). Note that it's in milliseconds, not samples so 256-512 samples is on the order of 5-10ms, depending on your sample rate. I run at 48kHz, and have had BounceBufSizeMsec=20 (960 samples) set for years without any problems.

It's complicated, and I have not revisited the issue for quite a while so my recall is fuzzy, but... the 16PART+PERF mode in the RD-700 (NX in my case) allows for an external sequencer/DAW to use the sound module as a 16-part multitimbral instrument at the same time that a performer has access to an additional 5 parts by Local Control (i.e. live 'PERFormance' parts), and the patches assigned to those parts can be different from the other 16 MIDI-driven parts. To ensure the sound from playback of recorded MIDI is the same as what you heard while recording, you want to make sure your playing the MIDI driven parts from the keyboard. And there are some additional complications related to selecting patches from the DAW vs. selecting them from the front panel which get simplified by disabling the PERF mode.

First, on the RD-700, go to Menu > Utility > Rec Setting , and set 'Local Switch' to OFF. This stops the Roland's sound module from responding to 'Local' input coming directly from the keyboard. Now you'll only hear the Roland responding ot your live input if the MIDI track controlling it has Input Echo enabled. turning of Local Control is standard operating procedure for using any keyboard synth synth (i.e. combined MIDI controller keyboard and sound module) with a DAW. Another setting you'll want to make it is to go to Menu > System, page right a couple times, and change 'Part Mode' at the bottom of that page from 16PART+PERF to just 16PART . This is needed to get the piano to play back using the same sound you have selected in the front panel (or via patch change commands from Cakewalk if you get to that point) as you hear when playing under Local Control.

It's assumed that when recording a soft synth in real time, it will be driven by live MIDI input from outside the DAW, and the performer will be listening to a delayed audio metronome, so the audio is compensated accordingly. But playback of existing MIDI isn't delayed by audio output latency, so the audio resulting from that is going to end up over-compensated. Normally existing MIDI would be rendered offline by Freezing or Fast Bounce which will result in correct timing regardless of the realtime buffer setting. If you actually have a need to record soft synth audio from existing MIDI in real time for some reasone, you just need to use the lowest possible buffer size, which should always be the case in any real-time recording situation when audio is input monitored through - or originates from within - the box.

I just double-checked and cannot reproduce a problem getting the desired behavior saved in a template or saved and restored in a project created from that template or changed and resaved. One thing I noticed that could be misleading is that if you have two projects open at the same time with opposing settings, the display of the setting in Preferences may not update properly as you switch back and forth between projects, but the actual snap to zero behavior is always consistent with the state of the setting in each project when it was last saved.

- To snap to zero crossings without also snapping to a musical grid, set the snap resolution to a single sample. - To have it enabled in new projects, save a project template with it enabled, and create new projects from that template. - I don't really use the loop construction view, but 'editing' consists primarily of moving slice markers around. Your screenshot appears to be showing the waveform before the first marker. If you zoom in on a marker, you can drag it to a zero-crossing (grab the slice line inside the waveform, not the flag above it), but it doesn't appear to have a snap function or honor global snap.

Ripple Editing enabled?

I'm not familiar with Kontakt Mapping View. You're familiar with zooming by Ctrl+Alt+Mouse Wheel...? And dragging up/down/left/right in the timeline...? And selecting a region or clicking/Alt+clicking with the Zoom tool (enabled by Z)...? If none of those are ideal, I think the Bakers will need you to clarify how a new method will work significantly better, beyond just being able to chose which modifiers /hotkeys to use (which is always good). Also I'm not fully understanding: "some keys are fixed defaults which are far apart and not close to the left hand (e.g.. Z, U etc.) " Z certainly is close to the left hand, and U is unassigned by default. Not trying to discount that there's a better mouse trap out there. But if I don't get exactly what is needed and why, the Bakers might not either