Jump to content

apt

Members
  • Content Count

    26
  • Joined

  • Last visited

Community Reputation

16 Good

Recent Profile Visitors

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

  1. Thanks for sharing! That is a good temporary solution. However, such third-party plugins all have a big problem in Cakewalk - they also delay the "input monitoring" signals of the tracks that don't have a nagative delay. This causes a very big latency when recording notes by the keyboard :( That "Live Input PDC override" option doesn't help. Because it also bypasses the PDC of the existing MIDI data on the recording track, causing that track playing ahead of other tracks... So we still hope that Cakewalk can add this must-have feature ASAP. Studio One has just added this in their version 5.2 or so. Now almost every other DAW has this feature! Please consider adding this! Many thanks!!
  2. You surely can fix all the latency and any other imperfections in the stage of mixing... But nowadays most DAWs have that feature, so many sample libraries now have a quite noticable latency, for several hundreds of milliseconds, in order to get more realistic sound. It is very annoying to compose and program with that latency, isn't it?
  3. I'll second this request. However, AFAIK many of them have been requested for many years in this forum, but it seems that the Bakers are not interested in them...
  4. I'm glad that someone else also found it necessary... I made this request last year, and I believe there were several requests for this in the old forums many years ago. But unfortunately there's no official reply yet I'm an orchestral composer and have been using Sonar/CbB for over 10 years. Cakewalk has so many great features that can make my workflow efficient. But it's truly disappointing that this necessary feature has not been added into Cakewalk for so many years, while almost every other modern DAW has it... I think many people don't know there is a feature like that, and how much it can speed up their workflow. Therefore not many people are requesting for it... @Noel Borthwick @msmcleod Dear Bakers, could you please consider adding this necessary feature for orchestral composers? Thank you very much!
  5. I'm sorry that these bugs may not be related to this update, but could you please check them? I posted them two months ago, but no replies till now. And they are still there in2021.11 . Many thanks!
  6. Could you please consider adding this feature to CbB? I think this is a necessary feature in modern composing workflow, and many people including me rely on this so much... There's even a sticky thread in the VI-Control forum titled "Negative Track Delay Database / Spreadsheet"... Many other DAWs, like Cubase and Studio One, can do this. I really hope to see this feature in CbB! Many thanks!
  7. I'm using 2021.09 build 145. Every time I export the project as MP3, the bitrate is set to 256, no matter which I selected last time. Is there a way to change this default setting, or let it remember the last bitrate I select? Thanks!
  8. This bug could be annoying while using Ripple Edit. But it was not fixed in the 2021.09 release. Anyone encountered the same issues? Is there anything wrong with my Cakewalk settings?
  9. I'm glad that this was fixed for the drum grid pane However, Alt+Scroll is still not working in the Velocity and CC pane. Hoping to see this to be fixed soon. Thanks!
  10. I set a time selection with a note's "tail" included. If I delete this time selection with Ripple Edit on, the MIDI CC under the whole note would be deleted (not just the CC under the selected tail):
  11. Thank you for discussing with me! I've been using Cakewalk for nearly 10 years. I've tried several other DAWs but Cakewalk just fit me best. There are only a small number of things which I think could be better. So I decided to post some FR's and bug reports hoping to help make Cakewalk better.
  12. One of the reasons why I posted this thread is that, this feature is already avaliable to the free-hand tool while drawing envelopes. It's just been introduced in the 2021.6 update: So I think processing load also shouldn't be a problem. Anyway, it's not a bad thing to let smoothing be an optional process and give more freedom to the user, isn't it?
  13. @Glenn Stanton @Terry Kelley Thank you for the advice! But, not only faders can do modulations. Actually I use a breath controller. Recording vibrato with a breath controller is a common thing. It gives much more humanity to the resulting sound. I think this "limit" is truly not necessary. It narrows the use of automation in the level of software. IMO, "Real-world faders cannot move that fast" shouldn't be the reason to do this limitation in a DAW. It would be better if this can be decided by the user.
  14. @Noel Borthwick Here's a more obvious example. I recorded a vibroto that's not so deep, and the smoothing process completely ruined the vibrato.
  15. Thanks for the reply! But usually it removes so many nodes that the recorded envelopes are not accurate, especially when you want to record "vibrato", or some complex, detailed modulation to the synth. I really think it would be better if we can choose to save or not to save CPU. And this feature is already added to the freehand envelope drawing. I use "manual" vibrato a lot and also make EDM in Cakewalk. This is an important feature and I really hope to see it in Cakewalk.
×
×
  • Create New...