Jump to content


  • Content Count

  • Joined

  • Last visited

Community Reputation

37 Excellent

Recent Profile Visitors

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

  1. Supposing that it is taking time loading up audio files to start playback (more files, slower startup), maybe it's worth playing with the file I/O settings, such as buffer size and caching. If other daws are very different in this scenario, maybe they are optimizing by preloading the audio whenever the playback cursor lands, not waiting for a "start playback". Hard to imagine any other differences. Related issues may be the speed of your drive and the fragmentation of your recorded audio.
  2. Besides DC offset it could also be an extreme low frequency component. Also, it could be the nature of the waveform, which could have equal energy but different maxima on the plus or minus side of center. There's some discussion about these things here.
  3. In Kontakt. Do they let you edit or view the instrument definition? But then what can you do about it? Can you do a single tempo change just before that note is played? Or just after it stops?
  4. Check inside the instrument definition for that MIDI piano. That same thing happened to me with Dimension.
  5. Tempo change ought not affect a sample. Could be a tempo-based effect, either part of the instrument definition or on the audio path.
  6. "Pressing Enter": this may trigger focused buttons.
  7. You can create a junction on your new F: that directs the system to find the files in the folder on H:.
  8. bvideo

    CbB not finding new USB device

    FYI for future reference: the term "class compliant" does not apply to ASIO. Most operating systems provide a common driver for "class compliant" devices so they will work with the driver model(s) built into the OS. But Windows does not provide ASIO, so class compliant doesn't apply. P.S. The term "class compliant" refers to compliance with the USB specifications for device classes. Device classes include audio, mass storage, midi, and several others.
  9. Switching back and forth between program and combination mode: if it's a Korg, it will transmit a sysex when you push the button. Capture each button into a Cakewalk sysex bank and you can embed them in each track where you need them. Other makes probably do something or other on their MIDI out when you push buttons, so same idea.
  10. User 905133, I'm very sorry for all the confusion. I meant to say that your rewording ("Your recent take") of my earlier post was right in its overall effect. My quoting of your modified quote of mine lost the color from your post, as well as the notion that I was requoting your modified quote from me. I haven't yet found post numbers to help make references to previous posts more precise. Now the quotes are looking nested, and that's getting confusing too. My original "strictly speaking" post was in response to trying to draw a parallel between Cakewalk's echo input and standalone MIDI module connections. I think that was 12 or 13 posts back*, so a lot of posts have intervened. As far as the workflow you mentioned in the post 2-back* from here, yes I agree it's convenient to automatically mute previously recorded stuff that we are rerecording. I think Cakewalk might have attempted to cover that with the various modes for recording and take lanes and such, so previous takes are not heard while we are rerecording. Same situation for audio too, I'm guessing. The old old original resurrected post was not about recording. * my post counting does not take into account what happens when someone posts while I am still typing.
  11. Hi User 905133, Your recent take: Right, though I was talking from the strictly hardware point of view of setting up connections. I was speaking in terms of the impossibility of connecting (cabling) the sound module's input to the sequencer's two jacks, output and thru, at the same time. (Typical MIDI module: one input, one output, and usually a thru.)
  12. Hi Starship Krupa, Here's how I originally read your post: I took it to mean: "its" and "it"= the sequencer [keyboard OUT] ---> [ Sequencer IN] [Sequencer OUT] ---> [Sound module IN] [Sequencer (or? ...) THRU] ---> [Sound module IN] ("to the sound module ("Thru")") ... so it sounded like the sound module had two inputs. We should probably sync up on the MIDI jack and cable models we are using before we use up too many colors. 😄 The thread probably got revived because I referenced it in a different thread by someone talking about the lack of a clear MIDI signal path.
  13. Strictly speaking, if you have your sound module connected to the sequencer's MIDI output, you don't have it connected to its MIDI thru*. Also, the MIDI thru jack is usually not programmable**. There would rarely be way to suppress (mute) the notes going through it***. In those ways it doesn't correspond very well with Cakewalk's echo input. Cakewalk's sequencer doesn't require a "thru" concept because it can deliver a single MIDI source to multiple tracks, hence to multiple synths****, without any notion of a daisy chain. The requirement to mute the recorded data while echoing the input data seems somewhat arcane. Does anybody miss having that feature for audio? ------------------------- (* If you could do that, imagine the headache of your sequencer sending your synth's output through both the "output" and the "thru" to your sound module.) (** Sometimes a synth will have only one output, hardware switchable between out and thru.) (*** Since it was originally meant as a daisy chain, it was not meant to be acted on by the equipment that provides it.) (**** or even multiple paths to a single synth)
  14. bvideo

    MIDI Track Mute Q?

    This MIDI failure to mute and goofy solo bothers me too, as does the lack of a midi signal flow chart.
  15. bvideo


    MIDI output to an external synth goes to a "port" on your MIDI interface. You can route multiple midi tracks to a single port using the widgets on each track. For softsynths, each softsynth behaves like a port and you can send multiple midi tracks to it. In another sense, there is no such thing as any kind of bus for MIDI, namely a position in the track view or a channel in the mixer view that can aggregate MIDI data the way an audio bus does for audio data.
  • Create New...