Jump to content

Ben Chase

Members
  • Content Count

    14
  • Joined

  • Last visited

Community Reputation

1 Neutral

Recent Profile Visitors

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

  1. Hey, Folks. Anyone else experiencing this? I'm on version 1.1.1 of EZBass, which opens just fine in Cubase and Studio One, but crashes every time I try to insert in in Cakewalk. Presently, I'm on 2021.09 Update 1 of Cakewalk, but have rolled back to 2021.06 and had the same experience. I've also tried using the Empty Project template, in case there was an issue with my custom template, but that didn't have any effect. It crashed then, too. I could try rolling back to an earlier version of EZBass, but would prefer not to, given the there's no issue with it in Cubase or Studio One. Any thoughts? Edit: Never mind, a simple reboot resolved the issue.
  2. I agree that the old look was better.
  3. Thanks, Scook. I appreciate the clarification. Bummer. I much prefer the old look, as it took up a lot less space.
  4. Did a search of the forum, but I wasn't able to find anything recent about this issue. My resolution is set to 1920 x 1080 and the text/app size is set to 100%, both of which are the recommended settings, but my plugin menu has been oversized since 2021.04 and I'm wondering if there's a fix in the works. Any update would be greatly appreciated. Thanks.
  5. Thanks for the reply, Mark. Sorry, I didn't see it till just now. I use Strength all the time. My understanding of the Window feature, though, is that it's the exact opposite of what the Cubase setting does. Please correct me if I'm mistaken, but I believe the Cubase safe zone leaves everything in it alone, where as the Cakewalk Window leaves everything outside of it alone.
  6. I'm having the opposite experience of a lot of other folks. The context menus for plugins are gigantic for me, even though my Windows display settings are set to 100% and 1920 x 1080, both of which are the recommended settings for my monitor.
  7. Per Cubase documentation: "Creates a safe zone before and after the quantize positions. If you specify a distance in ticks (120 ticks = one 16th note), events that lie within this zone are not quantized. This way, slight variations are kept."
  8. Please consider adding a "Smart Quantize" feature, similar to Logic Pro: https://support.apple.com/guide/logicpro/midi-quantization-types-lgcpbc6a2df2/mac https://ask.video/video/apple-logic-pro-103-recording-and-editing-midi/23-23-smart-quantize
  9. I have basically the same question, but I'm using my reverb bus for tracks other than just those that are being routed to the instrument bus, so I don't want the instrument bus to affect the reverb level of those other tracks. The only things I've come up with are grouping those instrument tracks, rather than routing them to a bus, or using two different reverb buses, one for the instrument tracks/bus and one for all the other tracks. Any other options you can think of? To me, it seems unintuitive that, so long as the reverb sends from the tracks being routed to the instrument bus are set to Post, the relative wet/dry balance wouldn't follow.
  10. Thank you so much, Noel! I just updated to 2019.01 and loading the Plug-in Manager is actually way faster for me now and switching among categories is instantaneous. I'm grateful for you getting this improvement out there so quickly. Cheers!
  11. Hi, Noel. Thanks for the response. I use custom layouts to be able to name and organize plugins the way I want them.
  12. Thanks for the responses. "Glad" to know I'm not alone. Regarding Craig's feedback, I use Waves and UAD plugins, both of which come with multiple instances of most, if not all, of their plugins. I also use a number of plugins that require an iLok. That said, those things were true prior to a month and a half ago when I started experiencing the extreme slowness, so, although I don't doubt that they contribute to slowing things down, it seems unlikely to me that they're the entirety of the explanation. Also, I don't know that the 2018.11 update was the culprit. The fact that not everyone is experiencing it seems to suggest that there are other variables. I wish these things were easier to pinpoint.
  13. Anyone else seeing this? I did purchase a number of new plugins around Black Friday, but it now takes 2+ minutes to load/change plug-in categories, which seems disproportionate to the amount by which my plug-in collection grew.
×
×
  • Create New...