Jump to content


  • Content Count

  • Joined

  • Last visited

Community Reputation

23 Excellent

Recent Profile Visitors

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

  1. If you truly mean a MIDI track, what is the thing that should be generating audio? Is it an external device which you have wired to send audio back into cakewalk? If so, you would need to make sure that device's audio track is grouped with the MIDI track's solo button so it doesn't get automatically muted along with all your other tracks.
  2. Back there you said "peaks, clicks, etc.". Clicks could be a performance issue, but what did you mean by 'peaks'; also 'etc.'? Is there some audio distortion happening that could be independent of performance issues?
  3. As a point of information, try recording one of those non-controllable patches from the keyboard, then see how that bank & patch is labeled in the event view of Cakewalk. To be complete, make the keyboard change banks as well as programs as you record. The event view might work as your debug log. You can open the event view by selecting a track and pressing ALT-8.
  4. Also, if you're using firewire & WDM drivers, try ASIO.
  5. A straight line with boxes would not be able to explain anomalies in the mute & solo & input echo parts of the MIDI signal flow or how prerecorded material merges with live input or the entanglements with instrument tracks and their synth components.
  6. Disclaimers: I didn't watch any of the videos you did, and I don't know if your laptop has a LAN (ethernet) port. But if it does, and if you aren't using it, there are some designs for laptops that trade off hardware for software, which could cause the bad latency. In the software case, the software has to service a special part of the LAN at high priority in a loop. It's worst when the LAN port has no connection (no cable or nothing at the other end of the cable). Not even sure this would show up in wdf01000.sys, but if you haven't already, it's worth trying to disable the LAN interface if you have one.
  7. Seems wdf01000.sys is a module that can be coupled with other driver modules for many different devices. The latency reporter combines the report for all devices that use that module. Finding which device is invoking that module with the outrageous processing times is a puzzle.
  8. For USB devices, the establishment of uniqueness depends on the type of device. Disks and many other device types have unique identifiers down to the serial number of the individual device. Unfortunately, the USB MIDI class was defined without a serial number, just vendor ID and product ID. So two devices of the same make and model are not distinguishable. Can they be distinguished by which hub and port they are plugged in? Maybe, so don't ever shuffle them. Do Cakewalk and Windows do everything that could be done to uniquely identify devices, I'm not sure. But it's definitely an imperfect situation in the USB MIDI specs.
  9. Save a backup & be happy. Seriously don't worry, you won't screw it up.
  10. If you don't see those variables in the [options] section of TTSSEQ.ini, cakewalk uses the default values. The file most likely for you to add those variables is %AppData%\Cakewalk\Cakewalk Core\TTSSeq.ini (where %AppData% is based on your windows ID).
  11. Is the flaky project gone or still saved somewhere? I love looking for mysterious noises. If it's still around, strip it to the least audio that still makes noise, as John Vere says, and send it to the cloud.
  12. I wish it were more clear to me what the role of this 7/8 loop is in this 4/4 project.
  13. Bounce the whole thing then edit is one way to go. All your notes are preserved, but the loop property is lost obviously. Another way is to snip off where you want to edit and bounce just that part, leaving the loopable part as it was.
  • Create New...