David Baay

Start a new project, enable the count-in, and then Save As, change the file type to Template, navigate to the Project Templates folder in Cakewalk Content and save over the existing template file or as a new custom template with a new name.

If you set Workspaces to 'None', the layout and current zoom level will be saved and restored on re-opening the project. Selecting a Workspace will override that, but the last saved 'internal' layout of the project will be restored whenever you set Workspaces to 'None'. Personally, I still am not using Workspaces as I'm so used to every project having it's own focus and layout that evolves over time and is appropriate for what I was doing with it when I last saved it (usually with a description of the last major change I made included in the name).

A little Googling suggests the A-800Pro should support the continuous output of the DP-10. But whatever synth you're using also needs to support continuous/intermediate sustain message values. You can check the pedal/keyboard functionality by recording pedal movements, and verifying you get intermedate controller values in the PRV Controller pane and/or Event List views.

Select the clips to be grouped; then right-click one of them, and choose 'Create Selection Group'. They do not need to be in the same folder.

If the same project is working in SONAR, we know the driver and project routing are working. In addition to comparing TTSSEQ.INI files as noted, you should check Preferences > MIDI > Control Surfaces to see if the keyboard has been set up as a control surface in a way that's causing Note events to be 'stolen'. I haven't messed around with ACT (Active Controller Technology) for a long time, so not sure if you just need to re-configure it, or remove it altogether.

Select the notes. Then go to the Event Inspector module in the Control Bar, enter -5 in the 'Vel' field and hit Enter.

Sounds familiar. I believe this has been a problem with some other remote control functions in the past; will likely need to be fixed by the Bakers. Could be an issue with pedal sending two messages when depressed and released. You might try remote controlling it with just Note ON or Note ON/OFF to see if one of those works as expected.

I asked whether you can record MIDI despite not being able to hear anything in order to determine whether it's a routing problem within Cakewalk, or a problem with MIDI actually not getting to the track input. If MIDI recording works, then it's just a matter of ensuring that the Output of MIDI track (or MIDI part of a Simple Intrument track) is properly assigned to the soft synth - with the correct channel if needed - and Input Echo is enabled. %appdata%\cakewalk is a directory path with automatic substitution of path variables unique to your system (mainly the username). Enter that into any Windows Explorer window, and the relevant folder will be displayed with Cakewalk Core and SONAR Platinum subdirectories for those two applications.

Regarding the MIDI re-routing issue, Jonathan Sasor of Cakewalk responded to another thread indicating they are aware of a problem that will likely be fixed in the next release:

See what's available and enabled under Preferences > MIDI > Devices. If that looks the same as in SONAR, and it's still not working, you might want to compare TTSSEQ.INI files in their respective paths under %appdata%\cakewalk. If problems persist, please clarify the symptoms of 'doesn't work'. Are you able to select it as an Input to a MIDI/Instrument track? If so, can you record MIDI from it even though you might not hear anything?

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.