Jump to content

chris.r

Members
 View Profile  See their activity

  • Posts

    2,880

  • Joined

  • Last visited

  • Days Won

    3

 Content Type 

Posts posted by chris.r

    Waves Plugins updated to V12!

    in Deals

    Posted

    5 hours ago, shawker said:

    I have V9, V10, V11, V12 installed and Cakewalk crashes when opening a project created before v12 was installed.  I can create a new project, add waves plugins and it will open and play back as expected.  Luckily Studio One 4.6.2 is fine with this setup.  I have open tickets with waves and cakewalk support.  I would hold off updating to V12 until the dust settles.  I didn't WUP.

    Thanks for posting, shawker! And please keep us updated if the issue gets solved. Issues with projects that already use waves plugins is my main suspect when deciding if I should update or not. I have a bunch of V9 and another bunch of V11, of which some I could update to V12 but few would have to stay at 11.

    Waves Plugins updated to V12!

    in Deals

    Posted

    11 hours ago, TheSteven said:

    Had to break up the install because it was just taking too long - so I tried installing Mercury v9 1st then everything else.

    Mercury installed OK but when installing v11 remnants plus v12 updates - my system blue screened with a corrupted heap error.

    On rebooting this popped up:
    image.png.a6837b343490691b5eac88eded62c577.png

    and when I tried installing the 2nd half again:
    image.png.2990ac2e5900940498310e9350225acf.png

    had to locate SoundGrid and shut it down before the installer would continue.
    It's still installing... waiting to see more reasons why I should have waited.

     

    It reads like fighting a malicious software infection out of your operating system.

    Amplitube Leslie

    in Deals

    Posted

    12 hours ago, emeraldsoul said:

    Chris, thank you so much! But alas I have done that already. The IK amplitude plug is the only plugin I own that will not respond to midi. It might be a quirk in my system. I've reinstalled everything. I believe I'm not the only one with this issue.

    I never rule out "operator error" . . . ?

    Oh that's bad, sorry to hear that. Are you sure you have your controller enabled in the settings prior to any MIDI learn? Maybe try with another keyboard, that's what I would do just to rule out any hardware failure.

    Amplitube Leslie

    in Deals

    Posted · Edited by chris.r

    2 hours ago, emeraldsoul said:

    To get this product to receive a midi signal to control rotor speed has been a source of continual epic failure for me. Even after two go-rounds with tech support, years apart, and having digested everything available online, still can't control rotor speed.

    So if you do buy it, please let a brother know!

    You have to assign the controller. Click the 'MIDI' button next to the MIDI diode on the bar below then 'control change' tab and click ADD. Then you have to find the Leslie that you have loaded and pick it's 'Speed'. Next click Learn button and move your controller. It should work now assuming you have enabled the controller in the preferences first.

    Edit: apparently I can't find it under Control Change>Global tab, must use the Project tab unless I'm missing something too. It is convoluted, have to admit.

    • Thanks 2

    Waves Plugins updated to V12!

    in Deals

    Posted

    16 minutes ago, Bapu said:

    The single biggest arrrrgh is that I have a long wait on initial new scans in all my DAWs on both machines. ? 

    For me it's always the first one or two scans per windows session then it get's quicker. I blame defender.

    Waves Plugins updated to V12!

    in Deals

    Posted · Edited by chris.r

    13 minutes ago, cclarry said:

    He's agreeing with what you said Chris

    Thanks, I was wondering what kind of game was it :D. Yes, I should be more clear it's my subjective opinion and I understand those who will benefit from it but I also noticed that if you want to (edit: have to) keep more and more legacy versions there is an additional wrapper added with each version and that can obscure computer resources quickly in a dense project, so I don't like it. Furthermore there is always much mess with updating my installed collection after buying a new plugin especially after announcing a new version like today. I like my waves plugins but I don't like the confusion with their authorizing method and the constant anxiety that they will drop support for legacy versions like v9 one day.

    Edit: and I think Matthew was spot on with the change in their approach in his post above.

    DCO-106 UPDATE WARNING (not a deal)

    in Deals

    Posted · Edited by chris.r

    I have a habit to let the installers run through their paces in a sandbox first and see what kind of mess they do on my disk. As an example the installation path folder can be the a folder where developer pours out all of their library dlls and all sort of config files for one developer and puts another subfolder with a single dll plugin in it for another, you can only try guessing what an installation folder means for them.

    But with this, new to me, updating from within the gui I'm vulnerable again.

    DCO-106 UPDATE WARNING (not a deal)

    in Deals

    Posted · Edited by chris.r

    I just checked and my VST2 installed into separate folder, guess I left the default path untouched when installing. Theoretically I should be safe, but no, I'll wait until this gets confirmed being safe to update.

    • Great Idea 1
×
×
  • Create New...