Jump to content

Jim Roseberry

  • Content Count

  • Joined

  • Last visited

  • Days Won


Everything posted by Jim Roseberry

  1. Make sure you have a backup if you're going to install v1903. Even with the latest patches, we've seen DPC Latency issues with current generation hardware.
  2. If you don't know what you're doing, be careful when switching! Some devices don't work (at all) with MSI... and can cause your machine to BSOD. Other devices (like RME audio interfaces) will appear fine... until you try to use it (and realize it's not actually working). Video cards and most of the core hardware work fine with MSI Audio interfaces (dedicated and onboard) and Firewire controllers often don't work with MSI.
  3. The reason you see this is due to CPU throttling. When the machine is under heavier load, DPC Latency is lower... because clock-speed is higher. If the machine has major issues with DPC Latency, putting it under heavy load won't solve the issue. Power-management necessary to achieve long battery-life is diametrically opposed to configuration for maximum performance. That's the heart of the issue. If you look at any of the top performing custom built laptops, notice that they're *all* using Clevo shells. They're expensive, bulky, and have extremely short battery-life. Physics... of such a tight space make it a complicated balance. If you're strictly talking off-the-shelf laptops, Apple (OSX on the MBPs) does a better job juggling the above than any off-the-shelf PC laptop. Custom Clevo's smoke the MBPs... but that's another topic.
  4. At the risk of repeating: If the machine suffers from high DPC Latency, there is no working around it. It has to be solved at the source. No audio interface, no setting core affinity, etc. Read the details here: https://docs.microsoft.com/en-us/windows-hardware/drivers/kernel/introduction-to-threaded-dpcs With many cases... especially when it's ACPI (power-management) related, there is no solution. The only solution is to replace said hardware (in the case of a Laptop, NUC, All-In-One) isn't possible.
  5. Getting the personalities "right"... and keeping them all focused on a single direction is the hardest part. I've been really lucky with bandmates the past 20+ years. I've played in probably half a dozen bands in that time... and I'm still friends with most them. It's not easy to leave good friends behind... but to move forward, sometimes that's necessary. We always try to make it about "the song", "appealing to the audience", trying to strengthen our performance, and trying to increase our draw. That usually keeps things going in the right direction. I've been adamant on keeping the band a 4-piece. Any more than that... and it gets complicated with schedules, etc. We always hire commercial sound. Crossing that threshold made the experience (to me) a lot more enjoyable. We're a cover band in our 30s-50s... so the "rock-star" dream has sailed. We play for fun... and to cross off "bucket-list" items. The band is paid well... but we're not trying to live off playing.
  6. Behringer has absorbed numerous great companies over the past 10+ years (Midas, Kark Teknik, TC Electronic). Some of their latest gear is very good. If you're a fan of the original 1176 and LA-2A compressors, you should check out the 76-KT and KT-2A. They're inexpensive... and sound excellent. The 76-KT works wonders on drums.
  7. ACPI.sys is power-management related... and DPC Latency issues with that culprit often can't be resolved. Unfortunately, it's not as simple as assigning your DAW software to "unaffected" cores. https://docs.microsoft.com/en-us/windows-hardware/drivers/kernel/introduction-to-threaded-dpcs
  8. Laptops that are particularly good for DAW purposes are expensive, large/bulky, and have short battery-life. IOW, The general-purpose user would hate it. 😉
  9. There is no work-around for extremely high DPC Latency. It has to be addressed at the source. FWIW, Disabling TurboBoost won't solve DPC Latency issues. If you've updated the motherboard's firmware, updated all drivers, and updated Win10... you're out of options. When dealing with a general-purpose machine, you have to keep the target end-user in mind. The typical user of that laptop would never know it suffers from a several millisecond "hiccup" in data flow. For someone wanting to use it for DAW purposes, that small hiccup in data flow results in an audio glitch or dropout. Lets say you want to run your audio interface at a 64-sample ASIO buffer size (44.1k). The machine has 1.5ms to process/fill the next ASIO buffer. If a driver is monopolizing the CPU, the next buffer won't be processed/filled in time (resulting in a glitch/dropout). The typical user cares far more about extended battery life than ultimate performance. The power-management necessary for extended battery-life is diametrically-opposed to what we want in a high-performance DAW. With Laptops, power-management is the source of many DPC Latency issues.
  10. +1 on the importance of proper backup! It's never a problem... until it's a major problem. 😉
  11. FWIW, Your DAW's CPU will not affect the sound.
  12. On eDrum Kits with really simple HiHat function, it's a switch (on/off) "closed" or "open". On more advanced eDrum Kits (like Roland's higher-end Vdrums), the HiHat controller (constantly) sends MIDI continuous controller data (to represent the foot pressure on the HiHat). I believe it sends CC# 4 (by default).
  13. A HiHat pedal (on an electronic kit) sends MIDI CC data. Thus, yes... it could potentially be used to control a Wah effect. Guitar amp modelers use CC pedals to control Volume, Wah, etc.
  14. You most likely didn't need to do a complete clean reinstall of the OS. A full manual uninstall of CbB (and or Sonar) would likely have sufficed. Use Programs And Features to Uninstall Delete all associated folders There are two locations in the Registry where software settings are retained. HKLM>Software>Cakewalk Music Software>Cakewalk (or Sonar) HKCU>Software>Cakewalk Music Software>Cakewalk (or Sonar) Now, reinstall CbB (or Sonar).
  15. I'd start by making sure all his drivers up-to-date... and make sure Win7 is fully updated. Temporarily switch CbB to the motherboard's onboard audio. Does CbB still take a long time to close?
  16. No comment on the sale... other than the Scheps Omni channel is fantastic for many things. The pair of de-essers alone are worth the cost (perfect for taming guitar-string squeaks, sibilance, and even over-bearing cymbals).
  17. CbB is the latest version of Sonar Platinum (new features and fixes). As was mentioned, install Sonar Platinum (to access your existing plugins), then install CbB. They'll coexist without issue...
  18. FWIW, When people rave about any plugin or program, they're virtually never talking about the "light" or entry-level version. ie: If a musician/engineer is raving about ProTools, they're not talking about ProTools Free. 😉 Melodyne Essentials is included with many DAW applications... and it-is-what-it-is... an entry-level intonation correction tool. All entry-level products are essentially a "gateway" to the full version. If you need advanced intonation correction abilities (and most of us do), you're left with few options (none of which are low cost). Thankfully, there's an upgrade path... and Celemony discounts several times a year. Cubase's Vari-Audio (included with the full program) is fairly close to Melodyne. That's the best "no cost" option I've seen... and that's only helpful if you've got Cubase Pro.
  19. I'm a bit late to this thread... but it's good to have this confirmed. I've been using Melodyne on bass tracks (to tighten up the pitch-center)... and to my ears it makes an audible difference. I wish I could do the same with polyphonic guitar parts... but I find the polyphonic algorithm causes phasing issues.
  20. Absolutely agree with this. First class vocal instructor can make an incredible difference. I "warm up" for about an hour on gig days. It's made an incredible difference in my vocal agility/stamina. In short, don't be afraid to work your voice hard the day of a gig/recording. Right before we go on, I do vocal "slides" up/down... to make sure the voice is ready.
  21. With 8GB RAM (if the OP is making use of virtual-instruments), the machine could be hitting VM Swap-file (in lieu of having enough physical RAM). This will absolutely *kill* performance. Additional unused RAM won't buy any additional performance. You need enough physical RAM to run your largest projects. Load said project... and have a look at the amount of RAM being used.
  22. Has the OP checked the system for high DPC Latency? That's the first thing I'd check. High DPC Latency can cause glitches or drop-outs (depending on the severity).
  23. Some plugins like Addictive Drums have an online "Sync" process that runs when the plugin is opened. This can cause CbB to take a bit longer to completely shut down. FWIW, I'm experiencing this with the latest CbB... (while mixing a project for a client). CbB will close... it just takes a little longer. If I have Task Manager open... and stop the AD "Sync" process, the Cakewalk process stops almost immediately after.
  24. Do you have an MIDI controllers connected to the machine? I just mentioned this in another thread... A MIDI driver "not letting go" can cause the CbB (Sonar) process not to stop. A good while back, the Korg USB MIDI driver caused this exact scenario.
  • Create New...