Jump to content

kc23

Members
  • Content Count

    44
  • Joined

  • Last visited

Community Reputation

31 Excellent

Recent Profile Visitors

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

  1. 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").
  2. 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.
  3. 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.
  4. 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.
  5. 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.
  6. kc23

    Volume

    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
  7. kc23

    Volume

    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.
  8. 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.
  9. 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.
  10. 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.
  11. 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.
  12. If you select group, and then copy: -Put cursor on time you want to paste, normal paste (cntrl-v) will paste accurately where the cursor is. -Put cursor on time you want to paste, paste-special (cntrl-alt-v) will paste accurately in time you set in "starting at time" slot. Just tried it, it is expected behavior.
  13. Inspector is showing "multi" because in a group there are multiple clips grouped. Individual clips in a group can also be selected. Click on the "body" of the clip, then check inspector. Also, select group, check selection module on control bar, it will show start of selection=start of first clip.
  14. No assumptions. The facts shown by your operation and your answers lead to this inevitable conclusion. Ideas, suggestions and creativity require to know the correct operation of whatever tool one wants to wield. Again, the facts shown by your operation expecting the desired result, and furthermore your answers to the questions asked and suggestions given, show you don´t know the way the tool works, or the reasoning behind it. This answer further proves the point. Haven´t insulted anyone. In any of my posts, in any of the threads I have posted. I have addressed you directly in one other thread. If you are tired, get a rest. However, you do have insulted at least a couple of posters in other threads just this week, not counting your insult to me just now. You just don´t like being called on it, and then take it personal. Nothing to give up here. My pair are well grown in to maturity, something your answers say otherwise about your own. Again, just because you don´t like an answer given to you, does not mean it is an insult. I would think in order to "belong here", one would have to know what they are talking about, or at least be willing to learn about it, none of which seem to apply to you at the moment. No more left to say on my part.
  15. These answers suggest you don´t have a good grasp on how signal flow and/or the routing in CbB work. The question and later suggestion are showing the error in your assumption. And the solution to the desired routing. Which will end up in a mono sounding track on the bus configured as Master, most likely raised in level by 3db. Hence, it is not a bug.
×
×
  • Create New...