Jump to content

Canopus

Members
  • Posts

    849
  • Joined

  • Last visited

  • Days Won

    1

Posts posted by Canopus

  1. I think you would normally keep the plug-ins on the C:\ drive, and only move the sample libraries elsewhere. After all, a plug-in normally has a very small footprint compared to its samples. It usually works to move the sample folders, but there is no one single answer. On those rare occasions when it’s not possible to change the location from within the plug-in, you might have to use symbolic links to do it. Search for "symbolic link" in this forum if you need advice on that topic.

    But regarding iZotope Iris 2 it’s easy: after manually moving your preset and sample folders, just click on the wrench in the upper left corner of Iris 2 and click the Set… button in the LIBRARY pane. After browsing to and selecting the new folder location you’re good to go.

    Iris-2.png.7c46063e969f229f53cdcca3a98ddb9f.png

    But having said that, if you really want to minimizer disk usage on your internal drive, installing the plug-in to an external drive and adapting your plug-in scan path in Cakewalk will most likely work. Just be aware that many plug-ins normally would place your samples in the %AppData% or %ProgramData% folder (or, for very misbehaved installers, in the Programs folder), and if so you would have to find and move the samples manually to another disk anyway.

     

  2. 43 minutes ago, Jon Sasor said:

    When Locked, there are no scroll handles in the Control Bar.

    Well, actually there are. If you select "Lock Module Order", the scroll buttons will be present when the modules overflow the boundaries.

    682312504_ScrollButtons.png.6d364fee3f79b79ba62bb279b505314e.png

  3. I might have spotted another small bug in 2019.07.

    There seems to be some problem with the new Lock Module Order and Justify/Center functions. If the modules selected are too many to fit within the space occupied by the Control Bar, you would normally see scroll buttons at the left-most and right-most edges of the Control Bar that will make it possible to scroll its content. And this is how it still works if you don’t lock the Control Bar, or if you select the tried-and-true Lock Module Order option.

    However, if you select one of the new options “Lock Module Order and Justify” or “Lock Module Order and Center” and the excess modules at the far left and far right partly or fully disappear outside the visible area, there are no scroll buttons turning up. And without any scroll buttons I can’t understand how you are supposed to reach the modules that have fallen off the edges. Or am I just missing something simple?

    Edit: Having a second look, I now see that you can drag the content of the Control Bar to the left or right to see the modules that have fallen off the edges. Is this by design, that dragging should be used instead of scroll buttons in those two particular cases? If that's the case, I don't know if that was a very wise decision to make. Having two different ways of scrolling, depending on what locking option is selected, is not very user friendly in my book.

     

  4. I think I’ve spotted one small bug in 2019.07: whereas the new Smart Tool icon in the Control Bar always changes if at least one of its default functions is removed, the same is not true for the floating Tool Window (a.k.a. HUD, which you reach by pressing the middle mouse button). The filled pointer icon is always displayed in the floating window regardless if the Smart Tool is customized or not. I assume this is not the intended behaviour.

    I already wrote this in another thread as there wasn't any official 2019.07 feedback thread open at the time, so sorry for cross-posting.

    • Thanks 1
  5. Both the Gran Vista Black & Blue and Carbon themes have now been updated to reflect changes in CbB 2019.07 with new buttons for Smart Tool, Smart Tool (customized) and Select.

    Additionally, the Record button in the small Transport module has now been modified so that it displays currently selected recording mode. Previously the recording mode was only visible when large buttons were displayed. Although this was consistent with how both Mercury and Tungsten displays the small Record button, a forum thread made me aware of the lack of indicators in the stock themes and I saw no reason why not to add it to these custom themes.

    Download the modified themes from the links supplied in the OP.

  6. 40 minutes ago, Pragi said:

    [An abundance of extremely eloquent posts, unfortunately too many to quote in detail]

    I give up, you win.

     

     

     

     

     

     

     

    But you still have some work to do on your member reputation/post count quotient.

    • Haha 1
  7. Oh, that’s nice. Looks like he’s met the audio mixing people at the beach. Now he doesn’t have to feel so lonely anymore. Or at least hungry.

    image.png.61896e83c8c5827fbdd24290d7107ccc.png.2578ee913d2631dafd479893dc37a7a6.png

    • Like 1
    • Haha 2
  8. When you want to make persistent changes to a theme, locate the following nodes in the Theme Editor treeview:

    • Space between strips: Console View > Background #1
    • Empty console strips: Console View > Background #2
    • Populated console strips: Console View > Unfocused Strip Background

    Also, some ideas on how to locate graphical elements in the Theme Editor when you don't know their names are discussed in the following thread.
     

  9. This may be old news to some of you, but I just noticed that a new version of Thorn is available at Plugin Alliance. As some of us previously noticed, the VST3 version of Thorn 1.2 had some serious issues with Cakewalk, throwing an unhandled exception error during load and took Cakewalk down with it when crashing. However, after downloading and installing this new version I managed to run the VST3 version without any problems. The installation file was created May 23, so it seems to have been around for almost two months now.

    According to the change log the following fixes have been made to Thorn 1.2.1:

    • Fixed a startup crash in Cakewalk by Bandlab
    • Fixed AU opened in mono configuration in Studio One 4
    • Fixed a crash when selecting generic UI option in Reaper
    • Installer always copy Thorn resource files to the correct location now

    https://www.plugin-alliance.com/en/products/ds_thorn.html#downloads

    • Thanks 3
  10. Look for a pedal (sustain) event (MIDI CC 64 with a value > 0) placed ahead of time to your inserted events. The sustain will affect all subsequent notes until there is a MIDI CC 64 event with a value of 0.

    To turn off the sustain, either modify the curve at the bottom pane of the PRV or optionally in the event list add another CC 64 event with a value of 0 where you want the sustain to end.

  11. 22 hours ago, Notes_Norton said:

    Thieves made away with the lute. 

    A lute? To me, crimes like these simply defies logic, far beyond reason. Just as Mark said, having used pro tools, breaking in must have been a cakewalk. And still – just a lute? Was that instrument made for live gigs or was it a studio one? As musicians these thieves obviously aren’t into any digital performance. And that kind of instrument would hardly be used in a garage band. I think the crime investigators need a cue: base the police investigation on the "modus operandi". There’s simply no endo to the possibilities.

     

     

     

     

     

     

    Sorry for the last ones. Ok, all of them.

    • Like 1
    • Haha 5
  12. You’ve got a point there. But looking back, both the Key Suite Acoustic and Key Suite Electric were introduced at $149 and UVI offered existing owners of related instruments a $50 extra discount. So with UVI Attack 88EP currently going for $59 and assuming a similar intro price of $149 for a Key Suite Processed, you’d probably only risk losing $9. Which is about the price of a Whopper Meal for Edith.

    • Haha 1
  13. Using the voucher I just bought the Lindell ChannelX for $9 plus VAT. Remarkable price really when you consider what this channel strip used to cost when it came to the market some four or five years ago. Noice indeed.

    • Like 1
  14. My impression was that the soundbanks in this deal mostly were older ones and most likely not their current best sellers. That’s probably why the prices could be set as low as they were. Asking to replace them with new ones fresh out of the owen might be granted (what do I know?), but maybe not ethically correct.

  15. Well, I'm able to find your thread with a Google search but when clicking on the link it doesn't show up as expected. It is however possible to see the cached version here:

    https://webcache.googleusercontent.com/search?q=cache:03W7KWJD9zoJ:https://discuss.cakewalk.com/index.php%3F/topic/3877-sun-lightning-mix-thoughts-and-feedback-please/+&cd=3&hl=sv&ct=clnk

    Something must have happened, not sure what.

    Edit: When reading through the cached thread it seems as if you initial links were targeting mediafire which required some kind of download. Maybe these links were considered containing malware by the forum software and removed because of that? Just my two cents.

    • Thanks 1
  16. Let’s hope that this amazing deal will help increase the interest for AAS' instruments. Hopefully an even greater customer base will help them in the long run make up for almost giving things away like this. I’ve had their Modeling Collection for almost three years now and I really like it. And for those who think they already have enough virtual instruments, take a look at AAS' awesome Objeq Delay.

    • Like 1
×
×
  • Create New...