David Baay

Yes that works because there's no difference between To and By in that case. I meant whole clips in the Track View that don't start on a measure as opposed to selecting individual notes in the PRV.

I agree Duplicate Clip should respect the To/By snap setting. It doesn't work as expected in the Track View with a whole clip (audio or MIDI) selected, either - always snaps to the grid.

Sorry to hear the problems are getting you down. Let us know if you decide to stick with it and troubleshoot. - For the Loop Construction issue, try selecting the clip, and choosing Views > Loop Constuction. If the multidock doesn't come up, hit Shift+D to maximize it, and see if you have a Loop Construction tab. - For the Dim Pro issue...I dunno right offhand. Have not seen any issue with it since the old bug with a particular drum loop that would crash SONAR. - For the Instrument track issue, split the track(s) and check the routing. Others have mentioned spontaneous re-routing of MIDI I/O, but I have not encountered it myself so long as the hardware config is stable.

So you're not changing what's enabled in the Yamaha's control panel app, only changing what's checked in Cakewalk's Audio Devices? I haven't encountered that when enabling/disabling ports on my MOTU either way. Cakewalk recently added a default input assignment for new tracks IIRC, but tracks and buses in existing projects and templates should 'remember' their assignments based on the port name initially exposed by the driver to the O/S and saved in AUD.INI. I would think the only time a default output would apply would be when starting from the BLANK template with no existing tracks or buses.

I haven't noticed a change recently. It's always been the case that starting a project with hardware ports missing or adding hardware ports while a project is open can alter MIDI track I/O assignments. It's best to just avoid changing hardware setups with a project open. And when it does happen, close the project without saving, and it should come up correctly when the hardware setup is stabilized. That said, MIDI/Instrument track outputs that are assigned to soft synths should not be altered by adding/removing hardware ports in my experience. In order to know whether what you're seeing is new and/or unexpected, you'll need to detail exactly what the scenario is in terms of the project's track I/O assignments and Cakewalk's MIDI device configuration before and after adding the keyboard.

That seems most likely to be an issue with a specific plugin or feature of the project or a combination of the two - like a specific plugin and dense tempo changes. I Googled the forum, and the only hit I got was your thread from Novemberwith and one guy responding that he had encountered it. You should PM him, and anyone else who's reported the same, and compare projects/plugins. Next time it happens try bypassing some or all FX, starting with any that aren't terribly common.

If 'fails' means export completes without errors but the audio is flatlined, that's most likely to be a selection issue. Try exporting with no tracks selected, Source Category = Buses and only the Master bus selected in the export dialog.

Any specific plugin? What's the peak level on the Master bus, and is there space between the peaks in the preview waveform (see the button to the right of mute and solo)? How would you describe the distortion? Is like clipping, like popping/crackling, like motorboating, or just general harshness? What buffer size are you running now? If you raise it does the distortion go away?

Changing to ASIO driver mode is a good suggestion, but I would guess that you're encountering plugin delay, either due to Autotune itself or some other 'mastering' plugin in the project. Some plugins use an internal look-ahead buffer to do processing. In some cases, such a plugin will offer a lower-quality processing mode that introduces less delay, but in general these plugins are not intended to be used in the tracking phase of a project. Hit 'E' on your PC keyboad to temporarily bypass all FX, and run the transport briefly to reset delay compensation with FX bypassed. If the delay is largely eliminated, that's the issue. If the delay-inducing plugin isn't on the track that you're recording (or somewhere in its output path), you can bypass the delay compensation that Cakewalk automatically applies to other tracks to keep them in sync with delayed tracks by enabling the 'PDC' (override) button in the Mix module. This eliminates delay on input- monitored tracks with live input. But I'm guessing that having Autotune on the input-monitored track is the problem, so this won't be applicable.

I would agree that's more typical. 3-4 minutes suggests some plugin is holding up the show with slow offline processing. You might want to try feezing individual tracks or bouncing buses, to determine where the bottleneck is. You might also try setting a non-zero BounceBufSizeMsec= value in AUD.INI (Preferences > Audio > Config File). By default (BounceBufSizeMsec=0), Cakewalk uses the real-time ASIO buffer size to process audio offline. Setting a higher value in AUD.INI can improve rendering performance. I have mine set to 20. Values up to 200 are reasonable.

Looks lke a clip fade. The fade tool/handle is active in the upped quarter of the clip, so you might have grabbed it inadvertently. If so, you can hover over the top right end of the line to get the fade tool, and then click and drag all the way back to the left to remove it.

Length is usually used for changing whole clips, but should work on individual notes or selected groups (200 percent to go from half to whole notes). As scook says, the Event Inspector will also accept percentages or durations in M:B:T format. Edit > Select by Filter may also be useful if you don't want to change every event in the clip. EDIT: And related ot Select by Filter is Edit > Find/Change, which can both select and change events to the desired duration.

Cakewalk does not handle triplet notation well, but the mis-interpreted notation in the staff view won't affect the underlying timing of the MIDI events, it;s just a display issue. If the MIDI sounds wonkiy, it is wonky. ;^) I record everything in real time, and it can be a chore to quantize because my stuff tends to be a mix of straight 16th, 8ths, 8th triplets and sometimes oddball figures like 3 in the time of 5/16. Usually I have to selectively quantize small sections to the appropriate value. Sometimes I'll hard-quantize a copy of a pattern, and use it as a Groove-Quantize reference to percentage quantize relevant parts of the original track. I never really think in terms of 'swing', and have seldom been able to get what I need with swing quantizing.

Yes, I can repro that.

Glad to help.

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.