Jump to content

bvideo

Members
  • Content Count

    74
  • Joined

  • Last visited

Community Reputation

22 Excellent

Recent Profile Visitors

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

  1. Also, if you're using firewire & WDM drivers, try ASIO.
  2. 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.
  3. 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.
  4. 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.
  5. 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.
  6. Save a backup & be happy. Seriously don't worry, you won't screw it up.
  7. 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).
  8. 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.
  9. I wish it were more clear to me what the role of this 7/8 loop is in this 4/4 project.
  10. 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.
  11. When applied as clip effect, clip effect automation is available. My older version of Melodyne exposes pitch, formant and volume.
  12. A while back (2013) it was said that automatable parameters available within an ARA effect might be considered for exposure in a future version of Sonar. Has that happened at all in Cakewalk? I have no way to know what automatable parameters are available in the latest Melodyne. Or maybe Melodyne itself offers envelopes?
  13. Also, wouldn't there be a way to enter 9 notes of equal length and then use the stretch tool to modify the clip length to fit the length you would like?
  14. There's a thing called groove quantize that maybe you could use. The manual describes this in detail. Synopsis: First, construct one beat or measure of the pattern you'd like to emulate. Craft the timing and the accent you want to reproduce. Save that as a groove. Then you can apply that to a different sequence of nine notes to reproduce the timing and accents.
  15. More than just separate tracks: when you are using the same synth patch, even using two different instances or channels, playing two of the same notes can sometimes cause some undesirable phase cancellations. Two different patches may be needed, or at least some detuning or chorusing. By separating the parts, you will guarantee yourself to be able to work around any unison problems.
×
×
  • Create New...