Jump to content


  • Content Count

  • Joined

  • Last visited

Community Reputation

42 Excellent

Recent Profile Visitors

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

  1. Almost two years have past since this request, and so many people adhering to it. Plenty of updates to other features, but nothing about the necessary support for true mono send and return for the external insert plugin. It was mentioned that because of CW´s support of multiple driver modes its "harder to do". But it certainly can´t be impossible... so many other daws have support for multiple driver modes, and yet they have had true mono external send and returns for so long. It was also said that it was "lower on the priority list" a year ago. It would seem that some items in that list are simply not moving upwards in the cue, as so many other things keep being updated, but not a fix for this in sight. Again... please address this. After almost fifteen years of the external plugin being introduced, it´s due time for an update that fixes it and brings it to a contemporary standard for serious mixing duties. Hopefully it will soon.
  2. Indeed, truly disappointing. More so when something that should be considered an essential feature doesn´t get acknowledge by the developers. Please, give as an answer as to what to expect. Will it be implemented? Is there a timeline? Or is it simply not seriously considered, even after so much time and almost every other daw having it implemented? This feature is essential for anyone trying to do any midi programming. Is not only a thing with orchestral libraries (in which it is indispensable), but with all virtual instruments. A midi-tick based approach is just not workable. Hope this gets an answer.
  3. This feature is absolutely necessary. It´s no use having it on a midi tick basis, as the absolute time would depend on the tempo of the piece. Libraries that need this require a consistent time offset, set in milliseconds, regardless and independent of the tempo. No, nudging does not help, as stated by other posters here. Every articulation within an instrument usually requires a different offset time. Indeed, that´s why so many other daws have it, like Cubase, Studio One and Reaper. It took Reaper one minor update to implement this. How hard can it be for Cakewalk to implement it? It makes CW almost useless for setting and orchestral template. Sadly, these are the things that keep me from fully returning to it. Guess we´ll have to see how long it takes to be implemented, if at all.
  4. This is a request that has been made for several years now. Sadly, it was never acknowledge, until almost recently, when the answer was that it was "lower on the priority list" because "Cakewalk supports other driver modes that have stereo channels so it makes it harder to do". A program like Reaper (which I have had to start using more and more because of this problem) supports WDM, WASAPI and ASIO driver modes too, and can handle true mono inputs AND outputs. So, its not like it can´t be done. Updates keep coming and coming, and this issue keeps getting left out. So, after so many years of requests, I wonder how long is the priority list for this to be so low? Will we ever see it solved? Hopefully more people will join in this request... besides all those who already have over such a long timespan, including the ones that have fled to other daws in search of this feature alone, which is indispensable in a professionally oriented mixing platform. Anyway, here is the thread from which I´m quoting Noel Borthwick:
  5. Indeed, driver bit depth is NOT the same as audio file bit depth. To OP: You need to go to Preferences/File/AudioData and toggle the File bit depths as needed. If your audio files are 24bits and the Import bit depth is set to 16, cakewalk is converting them to 16. If Import bit depth is set to Original, they will still be 24 even if the Recording bit depth is 16 (which makes the transport show "16").
  6. It is necessary to understand correctly signal routing as a universal concept, and then understand how the tool at hand (in this case cakewalk) functions, to make these kind of things work as one wants. -A send is a send. It SENDs audio to where ever you want it to be received. It can be a bus, or a track (used as an aux track in cakewalk). In analog, a send does not need a dedicated "return", you can return it to a bus (if it has an input port) or a track, as you can do in cakewalk. -In a patchbay, a mult is the result of an input being duplicated in a given number of outputs. You would have to patch the output of a track to the mult input, and then the outputs of the mult to the inputs of the tracks you want it to be duplicated at. In cakewalk, if you want a track´s signal to be received by multiple other tracks (thus creating a "mult") then: set the output of the track to a patch point (the "mult input"), then in as many tracks as you want, set their inputs to said patch point (the "mult outputs"). If you want to receive that signal also on a bus, send it through a... send, having decided for it to be pre or post fader. Understanding the signal flow and the software´s functions, this should take a couple of minutes to figure out, and another couple to experiment if it will work. Hope it helps.
  7. Sadly, I can see this as being an inevitable path for everyone that would like to use CbB as a serious hybrid mixing tool. We will all end up migrating elsewhere. So far, for me reaper seems a viable alternative, it can even open most CbB projects directly. Would rather keep supporting and working in CbB, though. But it just won´t be possible. And also sad, is that the problem is still not being addressed by anyone on the developing staff. Again, this has been going on for more than thirteen years. Multiple request have been made in this time span. Not a single serious response from anyone. Not a timeline, nothing. Lots of other features that cater for composition and midi work. Lots of other requests get responses and feedback from developers. Barely nothing for audio work. And lets not get started on multitouch support, GUI resizing support, routing menu organization, and some other stuff. Remember, when Cakewalk made the jump from only midi, it called itself Cakewalk PROAUDIO. I wonder were the PRO part went, as it seems to have been left behind for the serious audio work.
  8. No one uses multitouch simply because no daw has a solid implementation of it, not the other way around. Multitouch screens are way cheaper now than they used to be, and more people are getting them. I use a 43" tv with a pqlabs ir frame, and it is great. Even with poor implementations, mixing is way more speedy and intuitive than using a mouse. So, don´t knock it till you try it. Cakewalk was one of the first to introduce touchscreen capabilities, but (just like with other features) it has never been updated since its introduction many years ago, so it indeed would be nice to see improvements on this front. Just off the top of my head, some improvements could be: -Swipe solo, mute and record (and whatever else could benefit from this), which work with the mouse but not upon using a touchscreen. -More precision with controlling faders and knobs, sometimes moves are a bit jumpy, or when raising fingers, controls jump to other value than the one just set. This makes it unusable for drawing automation. -Touch capability for tools in track view, and not just for zoom. -Per track vertical zoom in track view. -One touch open for plugin windows (as with mouse). -More buttons in Custom panel and/or more Custom panels. -When assigning Console view to Custom panel buttons, make them full screen (as if having pressed "shift-D"). There´s no use for having a button assigned and then having to use the keyboard to expand the dock. -Scalability of faders in Console view. Not asking for vectorial drawings (like studio one or reaper) but at least give us two or three fixed sizes to choose from, as right now faders are too small for good resolution (besides having to deal with jumpy controls as stated before) -Customizable behavior of knobs: up-down or left-right or circular motions to choose from. -Quick group (Cntrl modifier) for touch control (only works with mouse). These are the ones I can think up just now, will be taking notes during my workflow as to what else could have better implementation. Or maybe I´ll start another thread with other enhancements too... even though just a solid implmentation of multitouch and true mono hardware inserts would make CbB a really advanced daw for mixing already, there are a couple other enhancements that would take it to another level.
  9. Well... Another major upgrade for the software, but not even a mention about this problem. Because, it IS a problem. A DAW that is hindering the functionality of an audio interface, is most definitely a major problem. As I wrote in the OP, this issue has been mentioned, requested, and implored to be solved for thirteen years... 13!! And as far as I have seen, not once has it been acknowledge in a serious manner by the developers. For all the amazing other features CbB might have, this one thing just prevents it to be taken seriously as a professional mixing tool, and literally throws it at the bottom of the pile for this purpose. What a disappointment.
  10. kc23


    Sorry, I was away and posted from memory. The correct tip is: Put cursor on fader or knob: "+" or "-" in numeric pad change value by 0.2 or 0.3 (basically, 0.25) Put cursor on numeric value, press enter: While value is highlighted, "+" or "-" in numeric pad changes value by 1.0. I´ll edit the previous post with this correction. Cakewalk[1].mp4
  11. kc23


    Put cursor on fader or knob: "+" or "-" in numeric pad change value by 0.2 or 0.3 (basically, 0.25) Put cursor on numeric value, press enter: While value is highlighted, "+" or "-" in numeric pad changes value by 1.0.
  12. Set Snap properties to Landmarks-Events. Before clicking, turn off time-snap in snap-module in control bar. Click near start of clip, cursor will snap to start.
  13. Hit record, recording will start where cursor (now-time) is. Or, make a time selection, go to punch-in module in control bar, press "set punch points to selection" button. This behavior has been implemented a long time ago.
  14. Use PluginManager. Make new layout. You can set as many folders and subfolders as you want. Drag plugins where you want them. Save layout. Upon loading new fx, go to plugin layouts, load saved layout. This feature has been implemented for many years.
  15. Make presets. Load a kit, click on presets, write name, save. Load new SessionDrummer, click on presets, click name of preset, kit will load. Presets have been implemented for many years.
  • Create New...