David Baay

Focus the track and hit Shift+T to show lanes. Each clip should be in its own lane. If not, you can click + to create new lanes, and shift+drag the clips to their own lanes. To get the desired result on new tracks, right-click the Record button to open record preferences, and choose 'Create New Lane' under Take Behavor.

It's working here, but thumbnails are hidden by default. Right-click the video view and click Show/Hide Thumbnails.

What app are you using to play back the exported file? Make sure its using the same driver as Cakewalk (preferably ASIO), and its level controls are at 0dB. On the Cakewalk side: - In the Console view, drag the pane divider at the far right side to the left to reveal the hardware output channel strips. - Make sure the volume fader on the strip for the Audient's main outs (to you monitors) is at 0dB. - Make sure every track and bus in the project is ultimately outputting to the Master bus, and the Master outputs to Audient's main outs. - Export with Source Category=Buses, and select only the Master bus. - If the level is still lower in the 3rd-party app, reimport the exported file to a new track in Cakewalk that routes directly to Main Outs, and group the mute on that track in opposition with the Master bus mute. - A/B the live mix with the re-imported track to compare the metered levels as well as the audible loudness. - Assuming that checks out, something's going on with the other app.

- Enable 'Use Paste Special Options on Paste' under Preferences > Editing. - Ctrl+Alt+V to make the first paste with Paste Special options. - Select the radio button to Paste into Existing Clips, and OK. - Regular Ctrl+V will now paste into existing clips, and will persist until you use Paste Special again to change it. Alternatively (preferred) - Select the one-beat clip in the track view. - Ctrl+L to enable Groove Clip Looping. - Drag the end of the clip out to 5:01 with snap enabled at a quarter or measure.

Another useful feature for moving the Now cursor is Tab (next) and Shift+Tab (previous) to MIDI notes or audio transients in selected tracks.

Drag-move/copy in the PRV should always automatically extend the clip boundary to encompass the moved/copied material in the existing clip. Pasting will create a new clip if the start of the paste is more than about half a measure past the end of the existing clip. To avoid that, you can drag the end boundary of the clip further out in the track view before editing in the PRV. But be aware that if you move the clip in the track view, the boundaries will revert to note/controller start/end points.

If you're talking about dragging individual samples as nodes, Cakewalk does not provide that capability. You would need to link an audio editing program to the Utilities menu, allowing you to open the audio file in that app and destructively edit the file. Cakewalk does not presently have any kind of free-form curve for fades other than inserting a bunch of nodes in a volume envleope, and tweaking them individually. This information is available in different places in Cakewalk. Selection duration in SMPTE is displayed in the Export module. Now time in SMPTE can be shown in the transport module or in the time display at the top of the Tracks pane (my preference) by left-clicking to cycle through M:B:T, SMPTE, H:M:S.mS, or Samples. You can also open the video view and float it to show SMPTE time in a window similar to Big Time. Ctrl+PgUp/Dn moves earlier or later by measures. Ctrl+mouse wheel scrolls the view, and Ctrl+Alt+mouse wheel zooms horizontally. See Options > Mouse Wheel Zoom Options to customize the behavior. For nudging the Now time with the keyboard I think the CAL-based workaround is still necessary. See post #3 here, and post #23 in the linked thread: http://forum.cakewalk.com/Any-to-nudge-the-39now39-cursor-forward-and-back-one-frame-m2397628.aspx

Missed this discussion originally, but, for the record, the hotspot described in the Ref. Guide works for me at absolute minimum height and width of tracks. That said, I usually use the area to the right of the top row of widgets, as it's usually wider and easier to hit.

Quick Grouping is working here in build 63 on selected tracks. One thing that's changed is that it no longer works on all tracks when nothing is selected. I guess too many people were inadvertently hitting Ctrl when they meant to hit Shift or something, so the Bakers removed it. You have to deliberately select everything to affect all tracks now.

That's why I so often advocate for recording the best real-time performance you can get to reduce the total amount of editing and arranging you have to do after the fact. To me, the gestures of playing and recording are the simplest, most enjoyable and most productive part of a project. I realize there are genres and compositional methods that inherently involve a lot more editing, but I just don't personally have a lot of interest in that side of making music. I enjoy participating in the forum to help users understand and make good use of what already exists, and, in some cases, to work around limitations because they need to get something done, and can't wait months or years for a enhancement to make is easier. Discussing workflow efficiency, and how many clicks it takes to do this or that just isn't my bag. If something is absolutely not possible or not working as advertised, or the workaround is grossly inefficient or painfully awkward, I'm likely to be more interested in lobbying the Bakers to address it.

1. Insert > Soft Synth > TTS-1 (or other multitimbral sysnth) 2. Check only 'First Synth Audio Output', in the dialog box, and OK (this creates an audio track to handle the output of the synth) 3. Assign the Output of the MIDI track(s) to the soft synth and set appropriate forced output channels if necessary.

The only difference now is you need to click in the lane header to move focus instead of an empty part of the lane. My usual sequence for pasting a selected clip from one track to another at the same location (when not Shift+dragging) is: - F7 (restored pre-X1 shortcut for Now=From). - Click to focus target lane/track. - Ctrl+C,V

Okay, so what about recording MIDI or playing back MIDI entered via the PRV? MIDI meters are always output meters, regardless of record-arming state, so there could be a failure to echo live input, or just a problem on the output side. Also, do you see activity in the MIDI Activity monitor that Cakewalk places in the Windows System Tray (Preferences > Display > Show MIDI Activity on Windows Taskbar)? And, on the off chance that the keyboard actually has a problem, you can try patching the MIDI OUT directly to the IN with a DIN cable and see if the Motif will play itself with Local OFF.

Oops. Should have figured that out, myself. I've never paid much attention to the Lens/Workspace feature, so wasn't thinking about how they're stored. %AppData%\Cakewalk\Cakewalk Core\Lenses

.INS files are Instrument Definition files - no relationship to ruler settings. If you don't have a Workspace enabled, ruler settings are project-specific - i.e. stored in the .CWP.

Looks like an anomaly with Elastique stretching enabled on the second track. Changing the Online Render algorithm to Groove eliminates the issue. I've encountered similar issues with Elastique stretching both on and offline. Not sure if it's inherent in Elastique or related to Cakewalk's particular implementation.

If you record MIDI without hearing anything, does it record as expected, and there is activity in the MIDI meter on playback? If so, you probably just need to enable Input Echo - looks like ))) - on the MIDI track or have Always Echo Current MIDI Track enabled in preferences, and have the MIDI track focused. If MIDI records and plays back and live input is echoed per the MIDI track meter, but you don't hear anything, then the question is where is the audio coming from and how are you monitoring it? If audio is from the Motif, itself, are you using the built-in mLAN digital audio interface, or analog or SPDIF output to an audio interface? Either way, if sound is to be monitored through Cakewalk, you need to have an audio track in the project with Input set to appropriate port/driver enabled in Preferences > Audio > Devices and Input Echo enabled on the Audio track.

It sounds like possibly you haven't installed the ASIO driver for the MOTU. See 'AVB / Pro audio' section of this page: https://motu.com/download Top Google hit on 'ASIO acronym' (from Wikipedia): Audio Stream Input/Output Audio Stream Input/Output (ASIO) is a computer sound card driver protocol for digital audio specified by Steinberg, providing a low-latency and high fidelity interface between a software application and a computer's sound card.

I can't replicate this, either. All automation curve types are honored as expected with Sonitus EQ. The only idea I have is that this might be O/S specific. Are you on Windows 10?

PR is Piano Roll, usually called PRV for Piano Roll View. I almost exclusively use the Smart Tool, and Ctrl+left-click allows selecting multiple notes. But I just tried with the Select tool, and Ctrl+click did not work as expected; it's necessary to Ctrl+click and drag to lasso each note. So try it with the Smart Tool.

Actually, I did read the post fairly thoroughly, and your suggested changes to PRV tools are exactly what I was referring to. I don't have the time and patience to respond to everything at once, especially knowing that I might have misunderstood some of them, but here are a few quick examples: Screensets, Workspaces and the Multidock have already been mentioned as solutions to getting persistent and desired window layouts, and will also likely account for Control Bar and Autozoom persistence issues. As you may know, holding Ctrl while changing a control in one of two or more selected tracks change all of them; this is Quick Grouping. It works with I/O assignments as well. That should already be happening. Make a separate post to troubleshoot. Cakewalk deliberately differentiates between selection (the source of a copy), and focus (the target of a copy). This facilitates all kinds of track-to-track and lane-to-lane editing that wouldn't be possible if clicking in a lane moved both selection and focus. What might work would be to have clicking in an empty part of a lane move just the focus there, but the possible consequences to other workflows would need to be considered.

The trouble with 'laundry list' posts is that trying to have an ongoing exchange of information, ideas and opinions about any one of them rapidly leads to total chaos. Suffice it to say: - All crash/bug/fix scenarios will require detailed steps to reproduce in order for Dev to have any chance of fixing them; many of them are not reproducible as described for me. - Many features mentioned already exist in very near or exactly the form described (as I understand them). - Many suggested changes to UI input/tool behaviors would need to be optional in order not to foul up long-time users who have adapted to the current implementation, and allowing this kind of customization inherently compromises maintainability/supportability. A lot of the complexity that new users complain about is due to the already vast array of preferences and options, and the difficulty of relating an unexpected/undesired behavior to a setting. EDIT: That said, I should add that I think there's some good stuff here, too.

This came up a few days ago with another Kontakt 6 user. He found that disabling 'External Sync' in Kontakt eliminated the problem.

Looks like a side effect of the ancient bug with drag and drop option 'Slide over to Make Room'. Change that to 'Blend', in Preferences >Editing, and I think you'll be good to go. If you do actually need the 'Slide Over' behavior at some point enable Ripple Editing instead.

I can't reproduce a gap appearing when the crossfade is moved with or without snap enabled. What tool are you using, how far are you moving it, and how big a gap appears? Are the fades lost/changed or just move with the clip boundaries? And are you running the current, hotfixed, version 2019.11.63?