Jump to content

David Baay

  • Content Count

  • Joined

  • Last visited

Community Reputation

1,052 Excellent


Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. I believe we're talking about the Input Echo button. If you have Always Echo Current MIDI Track enabled in Preferences > MIDI > Playback and Recording, the currently focused track (track name highlighted) will always be echoing input from your keyboard as indicated by the 'A' (for Automatic) in the icon; you can force it to be always on, but you can only turn it off by changing focus to a different track. The issue with NI is likely due to it being multitimbral and needing to have a specific Channel assigned to each instrument and track. See the documentation on Intrument Track per Audio Ouput: https://www.cakewalk.com/Documentation?product=Cakewalk&language=3&help=NewFeatures.16.html#
  2. That was Linux... er, um, I mean Linus.
  3. Disable "Set Now Time with Full Restart" under Track View Options. https://www.cakewalk.com/Documentation?product=Cakewalk&language=3&help=Views.03.html "Set Now Time with Full Restart. When you change the Now Time during playback, the Transport comes to a full stop, and then restarts playback. This stops the sound for a brief moment, but makes synchronization (especially with video) more robust." It's not mentioned, but toggling Looping also forces a restart when this option is enabled.
  4. Likewise, I'm not suggesting there isn't a bug; just trying to get a handle on the steps that manifest the problem so it can be reported if necessary. My main issue with moving between CCs and envelopes is that conversion of CCs to envelopes uses linear segments instead of jumps by default and doesn't give you an option. The segment types can only be changed one at a time, and converting back will create new CC events with interpolated values.
  5. Glad to help. We were all noobs at some point. I had the advantage that the CW manual was about 30 pages at the time. ;^) Good on you for sticking around to see the answer and respond. Welcome to the forum!
  6. Been meaning to click on this for a while, but haven't until now because, as a long-time fusion fan and fusion-musician impersonator, I inevitably end up feeling both envious and lazy after listening to one of Hidden Symmetry's productions. Hurts so good. ;^)
  7. To write/re-write automation after the fact you need to enable Write automation on the track in the desired mode and write the new data during playback: https://www.cakewalk.com/Documentation?product=Cakewalk&language=3&help=Automation.04.html 1. Different instruments/patches/parameters may respond badly when receiving new CC data that conflict with exisisting values. Using Overwrite mode or deleting the automation in advance should avoid this. 2. What are the steps that reproduce "cannot move the [envelope] data back to CCs"? 3. Existing envelopes should automatically move to lanes when you show automation lanes - this will need detailed steps to reproduce as well.
  8. Assuming you don't have a dedicated audio interface you should go to Audio > Driver Settings in Preferences and set the Driver Mode to WASAPI ('Exclusive' is best if you don't need to hear audio from your browser or other sources while working with CW). This will let CW use your onboard audio. If you've installed ASIO4All or Realtek ASIO, you should remove those as they are unlikely to work better than WASAPI if they can be made to work at all.
  9. Velocity is a parameter of a Note-On MIDI message. The keyboard has to write something for that parameter value. I don't know the Nektar's capabilities, but you would need to set a flat velocity response curve at some moderate, fixed value like 64. You could also use a MIDI FX plugin to output a fixed value on playback, but then you would still see varying velocity in the PRV. I'm curious why you would want to do that often enough that flattening it after the fact is too much of a burden.
  10. This will need a reproducible recipe. Can't say I've seen anything unexpected in this regard except by my own mistake/misunderstanding (e.g. wrong selection, wrong tool, locked clips, etc.).
  11. Solo the track, bypass all FX and switch the Master or other downstream bus to mono interleave. If the only thing that changes is the L/R balance with no tonal change or narrowing of a stereo image, it's a "dual-mono" track.
  12. Yes, looks like a display bug. But I don't see "Deselect the track and the button fades again." Once the track focus is moved by any means, the Arm button in the Inspector continues to show the 'active' state until playback is restarted.
  13. The highlight in the PRV is part of the Aim Assist function, the vertical line that follows your cursor. I am not aware that it's possible to disable the highlight other than by toggling off Aim Assist (shortcut X).
  14. That dedicated Draw tool will insert a single controller with a single click. The Draw mode of the Smart tool will do it if you hold Alt. I'm not sure whether the difference is deliberate or an oversight in the evolution of the Smart tool.
  • Create New...