Jump to content

jkoseattle

Members
  • Posts

    285
  • Joined

  • Last visited

Posts posted by jkoseattle

  1. If you're like me, your projects take a lot of iteration. Laying down a draft, listening to it a while, making changes, rinse, repeat. What I've always wanted to do efficiently is export audio for my in-progress piece, then listen to it on my phone for a day or two, then go back to the studio and make changes, export, listen on phone, etc. I know HOW to do this, but in the past what I've done is pull my exported audio into iTunes and then sync my phone and listen that way. Painintheass. 

    I'm wondering what other people do? Ideally, I'd love to just export my project to an audio file, then go right to the phone and be able to listen that audio somehow. I'm sure this is something people do. What's YOUR method? If you don't find a need to do this, don't bother making up how you would do it IF you needed to. I'm interested in what people actually are doing that works for them.

  2. I prefer the Space key to return Now to where playback started, and Ctrl-Space to move the Now marker to wherever I stop. That's how I've always had it. But for some reason those keys have swapped, and Ctrl-Space rewinds while regular Space moves Now to the stop point. What did I did to did that?

  3. Yes, it turns out it was about Take Lanes. Things were pasting on top of an existing take. As soon as I highlight a take with empty room for the paste, it will accept it and not erase anything. I still don't know what's causing this, but at least I see what's going on. Ideas?

  4. If I copy notes within PRV from one track, then paste them to another track, still in PRV, existing notes on the target track are REPLACED with the pasted notes, rather than blended in. So I went to Preferences to Editing > What to do with existing material: And "Blend Old and New" is selected (like it has been for years, btw, I've never done anything else). For good measure I checked a different option, hit Apply, then selected "Blend..." again, hit Apply and closed Preferences. Same behavior. This makes me EXCEEDINGLY NERVOUS. 

    So I tried pasting the notes onto the same target track in different places in the project, and sometimes it erased existing material and sometimes it didn't. After experimenting a while I finally went to Track View and took all the takes in that area of the piece and Bounced to Clip. This seemed to fix the problem. But I don't understand why.

    I seldom bother with clips, and am constantly applying trimming and bouncing to clip, mostly just to simplify track view. Now I'm worried I'm going to inadvertently erase something because of some misunderstood behavior going on. Can anyone elucidate here?

  5. Is it possible to select notes in PRV and mute them with a keystroke? I can select the Mute tool from the toolbar and click on any selected note to mute all of them, but that's more steps than I'd like. I didn't see a keyboard shortcut for it.

  6. I remember at one time I learned how to begin playback in the middle of an arranger section by clicking in some special way on the section label in the Arranger window, but I can't remember how that is done. Can someone refresh my memory?

    Also, is it possible to see the Arranger Track while in PRV?

  7. Scrolling horizontally in PRV is mysteriously really sluggish. Using Ctrl-mouse wheel to scroll, the PRV screen goes chunk-chunk-chunk about 2 chunks per second. Dragging from the measure number bar to zoom in and out also seems really sluggish, as does scrolling left and right with the thumb. Vertical scrolling seems unaffected. Anyone know why this is? The piece is 10 minutes long but only consists of two midi tracks.

  8. I'm using Opus pianos. Good question though because I just installed a track of Cakewalk TTS and it does NOT exhibit the issue! So it's something to do with Opus. Thank you!! I'll go ask their tech support next.

  9. Yes that is the model. In Audacity, the input and output are set up "Speakers (Focusrite USB Audio)" and that's all I've done. If I try to set Recording to something else from the list, it doesn't work at all.

    But if the Focusrite doesn't have a loopback feature (something I vaguely recall come to think of it), then how might I have been doing it in Cakewalk before??

  10. I am unable to do loopback recording in Cakewalk. I am using a Focusrite 2+2. I am not sure what settings I need to enable.

    I can record in Audacity, but the resulting recording is poor, full of pops and clicks.

    When I try recording in Cakewalk, I am recording nothing at all, but I STILL get pops and clicks from the audio source, which continue for a few seconds even after stopping playback.

    I used to do this all the time, but like so many of these kinds of things, it's something I got set up in like 2017 and forgot all about it. Now having to reset it all it's like I have to learn it all over.

    I probably don't have all the things you need to know to diagnose this listed here, so ask away.

  11. I just re-set up my whole studio exactly how it was before (or so I believe...) I had been having problems getting Midi data into Cakewalk, but that problem just disappeared yesterday. (see previous thread).

    Now I'm finding a new problem with my keyboard which I've never encountered before. 

    On the piano:

    1. Play a note and sustain it with the sustain pedal

    2. With the pedal still down, play the same note again and hold the key down.

    3. Release the pedal without releasing the key.

    The note stops. The Note Off event triggered by the raising of the pedal is overriding the fact that the key is still depressed. 

    What is causing this?

  12. Thanks! I installed Midi Ox and it looks like overkill. So I tried yet again opening Cakewalk because I wasn't like I had already tested it 5 times in the last two days or anything...

    ...and I then remembered to try one more thing that is only rarely suggested but is probably the most reliable solution across all computer problems. And that is: 

    Try doing the exact same thing you've already done like 5 times and maybe this time it will work for some unknown reason.

    ... and that's exactly what I tried, and it worked! I have to remember to recommend that next time comes to me with a computer problem. :-)

    • Like 1
  13. All this points to a problem with the physical piano itself. I had only moved it gently from one room and back, never dropped or bumped it. Is this something that happens with these, where the connectivity is fine but the keys themselves stop working?

  14. 9 hours ago, Bass Guitar said:

    It's interesting that M audio says no driver is needed but I just checked and they defiantly have a driver posted in the downloads.  Might be worth a shot. 

    But seems you know what your doing and it is a total bummer when S--T like this happens. I too am holding off on a re build to W11. I think I'll wait until Cakewalk makes up it's mind about which version I'll be using. And , yep, Don't touch a dang thing until the albums is finished is a good fri--n idea. 

    To be clear, I did have Windows 11 on the machine for a long time before I did the reinstall. I has nothing to do with Windows 11.

    Go here: https://m-audio.com/support/drivers-search and choose Keyboard Controllers > Hammer 88 > Windows 11. You'll see "There are currently no drivers available for this product and operating system."

  15. According to M-Audio, no drivers are needed, and I already have the most recent firmware loaded. 

    I tried opening a Basic project, installed a synth, and on the standalone version of the synth it plays fine on the virtual on-screen keyboard. I thought I played a few notes successfully from the piano, but either it stopped receiving data or else it was my imagination. In any case, no difference.

    Yes I meant Cakewalk is not receiving Midi data from the keyboard. Or if it is, it's ignoring it.

    And yes, I meant the USB cable. Not only is everything plugged into the same ports, it is the exact same cables before I broke it all down.

    Input echo is enabled, But if it weren't I should at least see recorded Midi events in the project even if I can't hear them. But nothing.

    RANT: This is the EXACT reason I've been putting off remodeling my studio and doing the much-needed Windows re-install. Because I just KNEW this was going to happen and I was dreading all the stress.. It's a sad mark of the times that an entire album release (two, actually) is not happening because of this. 

  16. I am trying to reset my system up after both a re-install of Windows 11 AND a remodel of the actual room. The room is done, and I'm plugging everything back in. I am unable to get Cakewalk to hear input from my Midi Keyboard though.

    This is an M-Audio Hammer 88 and before everything got taken apart, it had been successfully connected to this same computer and Cakewalk for years using the same Surface Dock. In Cakewalk Preferences > MIDI > Devices, the Hammer 88 is listed and checked for both input and output. When I create a new project, the template I am using points to the Hammer 88 already, and that pairing still seems intact for all three tracks in the template. The piano lights up when plugged in. When I unplug the Midi cable, Windows immediately complains, and when I plug it back in, it immediately recognizes the piano again. When I playback an existing project, it plays just fine, so my synths and soundcard are working. I also hear the metronome count-in when attempting to record. I have attempted this using both MME and UWP driver modes, with no difference.

    In short, everything looks and behaves exactly as expected. Yet playing the piano, nothing is heard and nothing recorded, on any of the three tracks. 

    I dug out an old M-Audio Keystation Mini 32 which is the only other midi device I own. Cakewalk doesn't even see it at all though.

    What should I look at to fix this?

  17. 4 minutes ago, murat k. said:

    It seems you have a faulty keyboard binding registry.
    Just save your keyboard binding in a file and delete all lines in the file which contains: Kx00530B
    Then load  that keyboard binding file.

    There is a keyboard binding bug in the Cakewalk for years, I hope developers will fix it in the final CbBversion.

    That fixed it! Wow, I wonder how long I've had that bug in there. Thank you so much!

  18. No the Ctrl key is not stuck. Ctrl-S has never worked for me in Cakewalk. I do not have two Ctrl keys. When I unbind it, the menu still shows it as one of the two possible keystrokes for saving. 

  19. CW is the only application I use which does not have Ctrl-S as its default keystroke for saving a file. Arghh. So I went to Keyboard Shortcuts to bind it. But it does not work. It shows Ctrl-S (as well as Alt-S) for File | Save, but when I actually hit Ctrl-S, the default "Split Clips" dialog pops up instead. I restarted CW, problem persists. Why is this happening?

  20. When I need to edit keyboard shortcuts, CW is taking about 15 seconds to bring that panel up. Once it's up everything seems to work fine. Also, if I close the Preferences window while on the keyboard shortcuts page, then simply hitting P makes it wait 15 seconds, because it has remembered that was the last page I was on. If I don't go to Keyboard Shortcuts, then the Preferences window opens right up normally. What's going on?

  21. Long time CW user, I had to reinstall Windows and start over with everything, and finally I've gotten CW up and running pretty much. I opened an old project consisting of two piano tracks (different pianos). The weird thing is that whichever track is highlighted is slightly louder than the other. During playback I can click back and forth between the two tracks and merely moving to a track changes its output. I don't remember ever experiencing that before. I turned off effects for the tracks and it still does it. I rebooted and now it's subtler but still present. What's happening?

  22. Thanks for the pointers. I got it now and that indeed fixed the problem! Whew.

    Now, since I've been using CW for literally 34 years (OMG) I have never run into this before. I just added a new synth to this project and lo and behold, Enable MIDI Output is checked by default. I've never had to deal with this before so I don't know why it's different all of a sudden. I poked around Preferences and am not seeing anything obvious. Can I disable this by default somewhere?

×
×
  • Create New...