Jump to content

David Baay

  • Content Count

  • Joined

  • Last visited

Community Reputation

502 Excellent


Recent Profile Visitors

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

  1. The messages themselves don't carry port information. There is no 'incoming port' value that you can 'retransmit' or map to some other port. What you're wanting to do cannot be done without extending the message format beyond the MIDI 1.0 spec. For the time being, you will have to use multiple tracks outputting to separate drum maps in order to route CCs to specific ports/instruments.
  2. So basically what's needed in this case is a 'Pass-thru' option for Channel that just passes events without altering their embedded channel. I'm thinking that actually should not be that challenging to implement. The alternative would having a drum map with 128 x16 = 2048 rows (!) to handle explicit mapping all possible combinations of input note number and channel. 🤪
  3. If a drum map is still in place that outputs to the synth, it won't be deleted.
  4. Not sure there's an answer here, but there's a long discussion with additional links and info: https://www.steinberg.net/forums/viewtopic.php?t=103828 Coincidentally, it specifically mentions Lynx having issues with it.
  5. It's an inherent imitation of the MIDI 1.0 message types. Note On messages can be differentiated (and routed) by their note numbers. CC messages don't have that; there's nothing to 'tell' the drum map that a given CC is associated with a given note number. Getting that capability will require imlementing something like Steinberg's proprietary 'Note Expression' or MIDI 2.0's 'Polyphonic Expression', and will require completely re-architecting Cakewalk's MIDI engine.
  6. +1, although that should affect all DAW apps running on the same machine equally. Another random thought: Having Steinberg Cubase 'Generic Low Latency ASIO Driver' installed can cause these symptoms.
  7. Back when dinosaurs roamed the home studio, Go to From was bound to F7. That binding was discarded in X1, but the function still exists, along with similarly handy functions: Go to Thru, From=Now, From=Start, Thru=Now, and Thru=End (formerly F8, F9, Ctrl+F9, F10 and Ctrl+F10, respectively). I could not live without these and restored them with custom bindings.
  8. Any chance you enabled the non-default 'aggressive' ThreadSchedulingModel=3 in AUD.INI (Preferences > Audio > Config File) despite warnings that it's experimental? Many who have tried it had a result like you describe, and many of those promptly forgot they had made the change and blamed the update... as usual. ;^)
  9. There might be a bit of a learning curve related to default keybindings that have been altered or disabled (e.g. 'O' to toggle Envelope/Offset mode), and changes in modifier keys and hotspots to get different tool behaviors, and features that didn't exist previously like Ripple Edit and Workspaces. In particular, I recommend setting Workspaces to 'None' in the upper right corner of the UI until and unless you decide to use them.
  10. Depending on the project configuration and how the bus and insert are being used, you might try outputting the bus to an Aux track that outputs to the downstream, bus, moving the insert to that Aux track, and using the track's solo. Or just re-route the source tracks from the bus directly to the Aux track with the insert, and use that Aux in place of the bus. Otherwise, the only solution is to not use external inserts on buses in a persistent way. Dial in the sound you want, bounce the bus output to a track, and remove or mute the bus. If you can get enough noise going on a thread in the Feedback forum, maybe you can get the Bakers to fix it finally.
  11. Yes 'Stereo Mix' is the output of the soundcard. You need to be recording from the input by setting the source to Line In. I gather ARIA is the name of the wavetable synth in your soundcard, not referring to Garritan Aria Player plugin. Wavetable synths are generally not usable in Cakewalk anyway due to latency issues. You'll want to get a good orchestral VSTi.
  12. Routing notes to different physical or virtual ports should not be a probem; I have done it frequently in the past. Just make sure you're routing the right 'Out Notes' to the right ports with the correct re-mapping from 'In Note' to ' Out Note', keeping in mind the non-standardization of octave numbering as reginaldStjohn noted.
  13. I agree, but would still record MIDI rather than audio, and use Set Measure/Beat At Now to sync Cakewalk's timeline to it.
  14. MIDI buffering was revised a couple releases ago. The default now is 50, and is generous where 250 was marginal and 500 was needed in most cases under the old scheme. I've been running mine at 20 without a problem.
  15. Don't know what to tell you. It is a bit strange, but hard to see how it really matters, unless you think the MME version sounds better? What prompted you to compare them in the first place?
  • Create New...