Jump to content


  • Content Count

  • Joined

  • Last visited

Community Reputation

6 Neutral

Recent Profile Visitors

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

  1. Whenever I see my friends (I have quite a few facebook musician friends or when it comes up in conversation) asking what DAW they should get, I always recommend Cakewalk. I make it clear that it's a legit, completely unhindered DAW for free... so it'd be pretty senseless NOT to try it, or even use it alongside another already paid DAW. I think that in and of itself is pretty effective, to be actively recommending it as individuals whenever the topic comes up as word of mouth will always be powerful. I want it to be as popular as it can to keep the support ball rolling!
  2. i would either add a second HDD or get an SSD to replace your main drive and use the HDD for backup/other files. sounds like your computer is doing what you need it to do still, so I'd hold off on the upgrade (unless you are bored and just want to, by all means). I'm still running a 1st gen core i7 860, and it does everything i want it to still. granted, im not a super power user, but it handles everything i do in cakewalk with ease (albeit my projects are pretty small, admittedly).
  3. this is definitely a valuable post. this has been a point of contention with AMD vs Intel in DAW performance since ryzen first launched. glad to see this issue is resolved and that one can confidently get pure low latency performance from team red... thank you for sharing this!
  4. Could be a good opportunity to turn people onto trying cakewalk and letting them know it's alive and well, if they didn't know already. I was on the fence about upgrading from a very old cubase until i found out about cakewalk being free now... so i figured "why not" and tried it out. Needless to say i didn't need to buy cubase haha.
  5. Running a 10 year old system myself, core i7 860 on windows 10 1803... Runs amazingly with everything I need it for, including cakewalk! I've upgraded from windows 7 to 10, so its also a 10 year old windows install all on old HDD drives haha. Good to know that 1903 should continue being awesome when i upgrade in a few weeks.
  6. that is not the issue i'm having, i am using overwite mode. what i am asking is if there is a way you can "disable input monitoring" for MIDI tracks, exactly like you can with audio tracks. this is for pre-punch playback, where i prefer to NOT hear the MIDI input i'm playing and only the recorded MIDI performance until i hit the punch point
  7. no, but i will set the punch point and play along to the already recorded material a few measures before the punch actually occurs in order to get a more natural flowing performance, and in doing so i can hear both the existing MIDI notes as well as what i'm playing at the same time, which is very distracting this is the exact method that i use to punch in audio tracks, and it works very well for me... would be nice if you could use the same method for MIDI tracks as well
  8. is there a way to disable input monitoring during playback and automatically enable it during recording on MIDI tracks, like you can for audio tracks? i am recording using an E-drumkit and during punches, i'd like to hear only the previously recorded material up until the punch point. as of right now, i can hear the playback AND monitor the kit at the same time, and its very distracting. thanks!
  9. Yeah now that I know how to unmute the audio afterward, I will certainly give it some experimentation... I definitely see how it could be advantageous. Yeah not having to click around as much while you have the guitar in your hands could be a lot better, definitely going to test this out
  10. Yeah that makes sense. I've decided the best method for me going forward for doing simple punches on the fly as I record is to use the overwrite option. This is the most similar to what I'm used to in cubase. instead of layering the audio over top of the existing track and sliding it around (in cubase), in Cakewalk I have to open the track lanes to drag and line up the punches exactly where I want them... Which is fine, just a little different. Thanks again for all your help! Thanks dude!
  11. Hi Larry, tonight I've done some extensive testing and I will try to be as clear as I can about what I've found using comp mode: when I click the record button with no punch, I correctly monitor only what im playing and not the track underneath when i use punch, when the scrollbar hits the punch in, i hear both what im playing AND the audio underneath(it sounds exactly like "sound on sound" mode), as in 2 sources of audio at once. Both of these scenerios are with "mute previous takes" UNCHECKED when I then CHECK the "mute previous takes" box to try to use comp without hearing 2 audio sources playing at once while recording, it greys out the audio that is in the punch region as soon as i click record. this would be fine if i could unmute the greyed out waveform somehow, but I'm not sure if that is possible
  12. Thank you Larry, I really appreciate you helping me with this... I will give it another go tonight or tomorrow night and report back.
  13. It is confusing to try to explain in text. In comping mode it works as expected when just hitting record but not when using auto punch. I watched a Cakewalk tutorial that exhibited the same behavior that I'm experiencing so I'm not sure what to think. I've put in a feature request for a tape style monitoring option so maybe someone there can verify this issue further
  14. hello! I have a feature request to add "tapemachine style monitoring" to cakewalk. for those who may be unfamiliar, this mode would: 1. disable monitoring during playback 2. enable monitoring and disable playback simultaneously during record/punch, just like a tape recorder would behave when recording/punching. many other DAWs have this option and its a HUGELY better workflow for doing punches than what's in cakewalk right now here are a couple of examples of the option i am referring to: thank you! hope to see this option make it to a new release in the future!
  • Create New...