Jim Roseberry

If you're trying to mount a 2.5" drive (typical SATA SSD) in a 3.5" or 5.5" bay, you'll need an adapter. Most more recent cases have 3.5" drive trays that allow mounting 2.5" drives (via four screws).

Most likely, the VST plugin DDL (for the full TH3) was installed in a folder that's currently not being scanned for plugins.

CbB is an updated version of "Sonar Platinum". As scook mentioned, the only things "missing" are some of the bundled 3rd-party content. For the moment, leave Sonar Platinum and CbB installed side-by-side. Once you are fully up-to-speed with CbB, you can always uninstall Sonar Platinum. No reason to be anxious/apprehensive...

Sounds like the issue is with that specific Absynth patch. You can run Absynth standalone or in another DAW application like Reaper (small download) to test. If the glitches persist... but are limited to Absynth (and specifically that patch), then the issue is with the patch itself.

FWIW, You don't need to open Bandlab Assistant before opening CbB.

If it's only larger projects crashing CbB, I'd test your system's RAM.

Hi Wayne, It's pretty easy to do a full/manual uninstall of Sonar. Most of the bundled plugins (from Sonar past) can be installed without installing Sonar... but there's no harm if you go ahead and install Sonar. If you need help with a full/manual uninstall of Sonar, I'd be happy to remote-in and show you how it's done. Take just a couple of minutes... I like to have separate 32Bit and 64Bit VstPlugins folders: c:\Program Files (x86)\VstPlugins_32Bit c:\Program Files\VstPlugins_64Bit At this point, I don't use any 32Bit plugins, but I like to have the 32Bit folder as a "repository" (for those plugin installers that don't offer the option to not install the 32Bit version).

</Meh> 😎

Agreed. Looks like management decided to get back to the basics of what Gibson does best (traditional/classic instruments). The price point of $2500 (to me) seems reasonable... assuming QC/consistency is good. If you're one of the "Master Builders", on some level it must be frustrating that you can't really innovate. Pigeon-holed by your heritage success... OTOH, Rickenbacker hasn't bothered to change much of anything in the past 70 years. 😉

After watching those videos, I decided to use Live to trigger samples and play keys at gigs. It can be as simple or as complex as you need it to be. Once everything is configured, switching songs is as easy as pressing a key/button/pad. Works perfectly for our 4-piece. We move a lot... and don't want a large keyboard up-front. I use a Q-Nexus and a 12-Step... to trigger/play the parts. Super small footprint... but effective to cover "just enough" keys.

For the piezo system

Focusrite makes some nice high-end gear (Red series, ISA preamps, etc)... but I've never been a fan of their audio interfaces.

You can use Top Ten Software's Cantabile to do the same type of things as Main Stage. Cantabile presents all your virtual-instruments and plugins as a virtual Rack of gear. You use Scenes (similar to a multi-patch) to setup advanced splits/layers. You can remap/scale controllers, etc. You may also want to look at Ableton Live. Lots of worship teams us Live. Advanced click-tracks (clicks, count-downs, sections called out) Tempo can be stored with each song Can host virtual-instruments and can be programmed to seamlessly switch between advanced splits/layers Can be programmed to disable unused virtual-instruments for each song (greatly conserving CPU) If a worship team member is absent; you can have all parts prepared in Live (muted)... and just un-mute the needed part Virtual-Instruments can be played live Samples can be triggered live Watch some videos showing worship teams using Live. Pretty amazing...

Mac only... You'd have to build a "Hackintosh" to run it. Hackintosh can be a fun learning project... and is close to a Mac... but not really a Mac (devil is in the fine details).

No, sir! You can hear the metal influencing the tone. 🤢

Love the features Don't love the aesthetics Not typically a fan of guitars/basses that use metal in the neck/body... as it seems to impart a "metalic" tone (especially on the attack). Tones shown in the video weren't bad.

When setting intonation on my guitars, I always double-check at various fret positions (helps when making smallest adjustments sharp/flat).

If you've used a Zoom guitar processor, this is the Native equivalent. Not bad by any stretch. Not going to lure you from a top-tier modeler.

Leaning to use High-Pass filters will do wonders for your mixes. There's no need for guitars/piano/vocals to be competing with the kick/bass down in the sub-bass frequencies. As was mentioned, use a high-pass filter on the bass (roll out the lowest sub-bass frequencies) to create separation from the kick.

Gibson has been thru the wringer (mostly due to ULM decisions)... but they're still a Heritage musical instrument company. The Les Paul is a classic/staple guitar... that's more than withstood the test-of-time. Even withstood minEtune... 😁 I think this leads some to almost want to find fault with Gibson guitars. "They're too expensive" "They're too heavy" "Upper fret access is poor (compared to other designs)" I do think that (at times) QC could have been better. If you pull a Standard off the wall at GC (where it's been used/abused for months), that can taint experience/opinion. I had a R9 for a couple of years. Ultimately sold it because I prefer other designs (ergonomics). I still consider that R9 one of the best guitars I've ever owned. Plug it into a decent Marshall amp... and it's instant Rock guitar.

FWIW, It's not hogging the "slot"... the driver is monopolizing CPU time (High DPC Latency). That can cause a "hiccup" in data flow. A typical general-purpose user would never notice say a 5ms hiccup in data flow. For someone running a DAW at a 32-sample ASIO buffer size, that 5ms hiccup in data-flow results in a glitch (at best)... or a transport drop-out. At a 32-sample ASIO buffer size (44.1k), the machine has 0.75ms to process/fill the next ASIO buffer. If it's not filled in time, you'll experience a glitch or drop-out. The X99 Deluxe II doesn't blanketly have a problem with high DPC Latency (it's the video card's driver). If you don't need much in the way of video processing, go with a GTX-1050 or one of the new GTX-1650 video cards. Right now, the AMD Vega-64 and Radeon VII result in lower DPC Latency than Nvidia GTX video cards. The difference isn't huge; GTX video cards can be effectively used when running DAW applications at small ASIO buffer sizes. Right now, Nvidia RTX-2xxx series video cards result in high DPC Latency. Ultimately, I'd expect this to be ironed out. I wouldn't blanketly say that AMD always results in lower DPC Latency than Nvidia. That's the case when comparing these video cards (at this point in time). Several months down the road (or with different models), things could change radically. That's the nature of computer hardware. A brand/model that's not a particularly great performer *today*... may be tomorrow's best-in-class. ie: Years ago, there was a time when Maxtor HDs were poor performers. Then, a couple years down the line, they were some of the best performers. Flash forward to the year 2006... and Maxtor was absorbed by Seagate. If you're not working with video, the video card's processing capabilities are (obviously) a secondary factor. Well-behaved drivers and low noise are more critical factors for DAW purposes.

Wow! RIP Bo

Now available for Mac and PC. It's certainly interesting... but I'm not generally a fan of any type of "automatic" adjustment/correction. You can hear it in action in this video:

Check to make sure power-management is disabled for all USB Root Hubs and newer Controllers. If power-management is enabled, the OS can decide to shut that port/s down to conserve power. That would (of course) cause the audio interface to disconnect.

Let me clarify: If your video card is causing DPC Latency of 500+uSec, installing a video card that doesn't increase DPC Latency (where the driver is much better behaved) would certainly solve that problem. With low/consistent DPC Latency, you'd achieve better DAW performance. Note that this isn't the same as the video card itself allowing you to run more audio processing. In your case, you need the video card to essentially "get-out-of-the-way" when it comes to impeding performance (high DPC Latency). I'll give you another example. Say you're using the onboard UHD-630 graphics on a i9-9900k CPU. The UHD-630 drivers are well behaved (don't cause high DPC Latency). If you then wanted to upgrade to a Radeon VII (drivers are also well behaved - low/consistent DPC Latency); you'd see no increase in DAW performance vs. using the UHD-630. Regarding the Izotope plugins: Your problem with glitches is due to high DPC Latency (not from poor video performance with the plugins enabled). IOW, Upgrading to an RTX-2080Ti (which currently suffers from high DPC Latency - but is a much faster video card), would still leave you with audio glitches. The lower your ASIO buffer size, the more critical to have low/consistent DPC Latency. If you're also working with video, what you need is a faster video card that doesn't significantly increase DPC Latency... and that's quiet when working with audio. Right now, for many folks a good sweet-spot (price/performance) is the new GTX-1660. When working with video, you may be surprised that there's not a huge (realtime) performance difference between using a RTX-2080ti vs. a GTX-1660. IOW, Previewing realtime VFX like Trapcode Particular doesn't run significantly faster with the RTX-2080Ti. The RTX-2080Ti would help a bit more on long video Renders.