Jump to content

Canopus

Members
  • Posts

    1,169
  • Joined

  • Last visited

  • Days Won

    7

Posts posted by Canopus

  1. I agree, start by using TreeSize Free to find out which folders are large enough to bother moving.

    Also, another thing to watch out for when preparing to use directory junctions, is when you’ve got sample libraries from Steinberg, such as those coming with Cubase, HALion, or Groove Agent. Such sample libraries are stored in files with the extension *.vstsound, which by default are stored somewhere under the folder C:\ProgramData\Steinberg. Use Steinberg Library Manager to move such files around instead of using junctions. For some reason, Steinberg's apps don't seem to acknowledge symbolic links in Windows.

    • Like 1
  2. 6 minutes ago, WyleyR said:

    I'm thinking an upgrade to SM3 will be worth no more than $29 to me.

    If there's one thing I've learned is that in this industry especially, the early bird tends to pay top dollar for shiny new things. Then a few months later, the real prices for things tend to come out. I'll wait.

    Mm, I don't know. I paid $26 in May for my upgrade from SM2.

    <proverb-galore>Sure, all good things come to those who wait. But sometimes the early bird catches the worm.</proverb-galore>

    • Like 1
  3. 1 hour ago, Dave Maffris said:

    If anyone has an idea of why or had this happen to them and how it was resolved, I hope you can help me, as I am a daily user of this software and am stuck without it for the time being.

    Do you have a Native Instruments account? If so, try to log in to iZotope using your NI credentials. As you may know, they belong to the same owner nowadays.

    • Like 4
  4. Roland Sound Canvas VA will be discontinued on September 1, 2024. As they say on Roland Cloud,

    Quote

    Unlike other instruments and effects on Roland Cloud, Sound Canvas VA was built on an older framework that we are no longer able to adequately support. This is especially true as the various OS platforms and plug-in hosts demand regular updates for compatibility and performance.

    Read the full statement here: https://www.rolandcloud.com/home/news/final-notice-sound-canvas-va-is-being-discontinue.

    Although I’ve got a Roland Sound Canvas SC-88 Pro on my desktop since like forever, I just bought the VA as well. After all, how would I otherwise be able to listen to my old MIDI junk from the nineties when I’m away from home?

    A Roland Sound Canvas VA Lifetime Key is still available for purchase at JRR Shop for $69, or $62.10 with code GROUP.

    https://www.jrrshop.com/roland-sound-canvas-va-plugin-lifetime-key

    • Confused 1
    • Sad 2
  5. I agree. I remember your similar post from 2021. This has also been a long-standing request from me. Here’s one from 2016. And if I’d been allowed to do so, I would have told you that I also raised that request in the Beta forum just a month ago. There, I even made a picture where I envisioned it like this:

    Fit-MIDI-Content.png

    But, of course, in order to see the benefit you’d have to work with MIDI. Not everyone does. So, will it ever happen? I’ve kind of lost hope.

  6. 5 hours ago, GTsongwriter said:

    Thought they changed that to Next and Sonar which requires Bandlab subscription?

    The post below is what has been officially said. Read in particular the third paragraph. Also, maybe click the Like or Thanks button while you're there.

     

    • Thanks 1
  7. 7 hours ago, satya said:

    Take your iPad on a journey through time. Go to the Date & Time settings and set the device date to 31/12/2015 or earlier. [...] When you’ve jammed enough, remember to return the device to the current time; otherwise, services won’t work.

    If I were to go back to 2015, I doubt I would ever try to come back. Services, or not.

    • Haha 2
  8. I've now read most of those threads and have as a result at least deactivated the setting "Always Use Latest Version of NI Plug-ins" in Komplete Kontrol. But, of course, NI must make sure that you at least get a clear warning in Native Access when an update would make an instrument unusable with the Kontakt version it was once designed for. A short mention of such a requirement change, accessible from some miniscule "Read More..." link, is simply not enough.

  9. I had this problem in July. When trying to open a project containing NI Session Guitarist Sunburst Deluxe, Kontakt 6 first said that it couldn’t find the samples. After a short wtf moment, I pointed it to the correct sample folder and made a rescan. After that, when opening the instrument, Sunburst Deluxe was in Demo mode?! Unfortunately, in Demo mode, you can’t really see the interface and the settings you've tweaked. It’s more like a white blob.

    After some discussions with NI Support, I realized that Sunburst Deluxe apparently had been "upgraded" so that Kontakt 7 was now required for that instrument. And, sure, I’ve got Kontakt 7 as well, but as I couldn't see the instrument GUI in my project when in Demo mode, I would have to start anew. I could hardly believe it. How could they turn an instrument that once required Kontakt 6 all of a sudden require Kontakt 7? It was just so effing stupid.

    But I finally got a link from NI Support to the latest version of Sunburst Deluxe that worked with Kontakt 6. As I have K14U, I downloaded every instrument I found on that "upgrade" list, just in case. After downgrading Sunburst Deluxe, I managed to open my project again.

    Finally, I wrote a note to myself: Never EVER update anything using Native Access; just use it for installing NEW software. Why? Because you won’t be warned when NI raise the Kontakt bar, and thus crash your existing DAW projects.

    • Like 2
  10. 8 minutes ago, Max Arwood said:

    Can you help me with the mklink syntax for these?

    Sure. The steps 1–4 above will be the same. Then, in the Command window, for Sonar you write:

    mklink /j "%APPDATA%\Cakewalk\Sonar\Plug-in Menu Layouts" "D:\Templates\Plug-in Menu Layouts"   [Enter]

    After hopefully getting a confirmation that everything went well, for CbB you write:

    mklink /j "%APPDATA%\Cakewalk\Cakewalk Core\Plug-in Menu Layouts" "D:\Templates\Plug-in Menu Layouts"   [Enter]

    • Like 3
    • Thanks 1
  11. 1 hour ago, Max Arwood said:

    Now if I could remember how I did that! 

    These are the steps I would recommend:

    1. Make sure the latest versions of all your plug-in menu layouts are in your planned target folder.
    2. Take a copy of your source plugin folders, as they will have to be deleted.
    3. Delete your source Plug-in Menu Layouts folders.
    4. Open a command window.
    5. Having e.g. Sonar as source/slave and CbB as target/master; write:
      mklink /j "%APPDATA%\Cakewalk\Sonar\Plug-in Menu Layouts" "%APPDATA%\Cakewalk\Cakewalk Core\Plug-in Menu Layouts"
    6. Of course, if you also would like to do the same for, say, SONAR Platinum, you’d run this command one more time with the first path changed to
      %APPDATA%\Cakewalk\SONAR Platinum\Plug-in Menu Layouts

    The beauty of this solution is that you can then update your plug-in menu layouts from any of these Cakewalk applications, and the files in the master folder will be updated, and thus be immediately accessible to all your Cakewalk apps.

    • Like 2
    • Thanks 1
  12. Yes, they have the same layout.

    Even better, if you’re using multiple Cakewalk products, you might want to only keep one set of plugin menu layouts. As for me, I have one master folder and then I’ve created symbolic links from the other application locations. More specifically, I have CbB as my master at %APPDATA%\Cakewalk\Cakewalk Core\Plug-in Menu Layouts. I’ve then added symbolic links named “Plug-in Menu Layouts” from %APPDATA%\Cakewalk\Sonar\ and %APPDATA%\Cakewalk\SONAR Platinum\, targeting the same master folder. It works very well.

    • Like 3
    • Thanks 2
×
×
  • Create New...