Jump to content

Jeremy Jensen

  • Posts

  • Joined

  • Last visited

Posts posted by Jeremy Jensen

  1. I tried Chuck's idea and it didn't work how I was hoping it would. Anytime you click one of the tool buttons in the HUD, it disappears.

    I need to be able to see, for example, where the mute tool is. It isn't immediately apparent to me which of those buttons contain it. Therefore, I need to be able to click on each of those buttons without the HUD disappearing. That's my request. Left clicking on the tiny arrow doesn't produce anything close to what I want in a desired behavior. That's fine if I'm the only one that wants the HUD to behave this way, but there isn't a work around to get what I want unless I'm missing something.

  2. I know this isn't what the original poster requested, but thought this was as good a place as any to mention my solution to recording and playing at the same time. I set up markers where I know I will need them for recording takes, and then I use my wireless keyboard and keyboard shortcuts to navigate where I need to go and use the transport controls. I set up my keyboard on a music stand near where I'm recording my takes. This obviously only works if you're within your wireless keyboard's range, and if you're close enough to your computer monitor to see what's going on. 

  3. I think a small improvement to Cakewalk would be to make it so that the Tools HUD doesn't disappear until you click outside of the boundaries of the HUD. You could also include a small "X" to close the HUD as well. Either way, simply clicking one of the HUD buttons shouldn't make the HUD disappear. When I'm right clicking each of the buttons to see where a tool resides (e.g., where the Mute tool is) it's annoying that I have to keep clicking the center mouse button to make the HUD reappear.

    • Great Idea 1
  4. I think it would be amazing if Cakewalk were to include easy reference mix comparison functionality comparable to Mastering the Mix's REFERENCE. Why this type of technology just isn't a built-in part of every DAW escapes me. Obviously you can do a lot of what REFERENCE does by other means, but not as usefully or conveniently as you can with REFERENCE or plug-ins like it.


  5. For example, I don't have the option set to "scan existing plugins", but it still takes a good 10 minutes to do a scan. It would be awesome, if possible, if I could just find the new plugin and have it just scan and add the new plugin that would be superb.

  6. Yeah. I've got to think that one of the samples in the kit selection I was using was messed up somehow, and, that, when the messed-up sample's turn came up in the round robin, I'd not hear the cymbal.

    I'm sending XLN my project for them to look at. Maybe they can fix whatever it was that caused my problem and fix it in future versions.

    • Like 1
  7. Also, just so I don't get too obtuse about this, here's the symptom, described as simply as I can:

    When my song plays, sometimes, at random, a crash cymbal decides not to play. Then you play the song again and that exact same crash cymbal WILL play.

    The only thing that makes me think it might not be Cakewalk is that in the AD2 software, in the view where you see the individual drums, it shows that the cymbal is struck, every time, even if you can't hear the cymbal.

    I hope that makes sense. It's kind of a hard thing to have to describe.

  8. The velocities vary. The problem I'm experiencing is that, for example, a velocity of one of these notes might be set to 115, but you play it back and can't hear it. But only sometimes. You'll go back and play the exact same note later and it will play as 115, like you'd expect. The problem is that, randomly, the velocity seems to go down to 0 or 5 or something even though it's set at 115 in the PRV.

    In fact, it may not be a velocity problem at all. All I know is that AD2 always registers receiving a note, but randomly (not every time) either doesn't play the note or plays it so quietly you can't hear it in the mix. It may be that AD2, at random intervals, just randomly shows that it's receiving the note, but doesn't actually play the note. I'm not sure.

  9. I've got a weird one for you, and I don't know whether this is a problem with Cakewalk or a problem with Addictive Drums 2. I've got a project where, intermittently, cymbal crashes are very quiet/non-audible. I can see in AD2 that the software is receiving some signal from Cakewalk for each of these crashes, so it must either be the case that Cakewalk is sending AD2 a very low velocity note, OR AD2 is, for some reason, playing the note very quietly even though it's been sent the correct velocity. It's not the case that the note isn't being sent at all or that AD2 is not receiving the note.

    So, yeah, kind of a weird one. I'm not sure where to go from here other than to rebuild the project track by track and see if the problem still exists. Anyone experience any issues like this?

  10. The review made some good points (e.g., lack of console undo is not great, there are some half-baked features)  but overall I think the review was WAYYYY too harsh. He's also constantly saying "tons of other DAWs do (feature X) better" without mentioning any examples. He also doesn't seem to really know how to use CW all that well. For example, he bases his statement that crossfading two clips is a really hard thing to do on... the number of steps they use to describe it in the manual. If he were to have actually used the feature he would have realized that crossfading two clips is one of the easiest things you can do in CW: just drag the edge of one clip over the top of another. At least two other DAWs I've used require you to do that and then do some sort of keyboard shortcut to do the actual crossfade. CW, and, I think, Cubase are the only two DAWs I've seen that do it as easily as CW does.

    Anyway, the bakers should definitely take some useful feedback from the review, but let's not pretend it was balanced or objective.

    • Like 2
  • Create New...