Jump to content

jono grant

  • Content Count

  • Joined

  • Last visited

Posts posted by jono grant

  1. What I mean is that when you expand a manufacturers plug list, it gets all melted in with the other manufacturer entries. Here's a picture (below)

    *Shown here, the Antares menu is expanded, but the plug list look like they're part of the continued list on the right. They used to have graphic separators for each plug. It looks like a graphics glitch in the update is what I mean. It's confusing. 

    Is no one seeing this?



    plug menu.jpg

  2. On 6/21/2021 at 9:19 AM, Tommy Byrnes said:

    I've found the best way to deal with UAD plugin problems like this, and many other VST problems as well, is to make sure I only have one VST2 folder location, which for me is Cakewalk\VST Plugins. Have the VSTScan only scan that one folder. I've always used that location, no matter the DAW just because I've been doing it since the early Sonar days. VST3 defaults to its normal place (C:\Program Files\Common Files\VST3). I copy (don't cut) the dll for the plugin I own from the main UAD Powered Plugins folder and paste them into a new UAD Plugins folder in my main VST2 folder and there they stay, unaffected, unless I buy an update for one of them or there are fixes to specific plugins. This way the VST folder and their contents aren't changed and there aren't all the UAD plugins to scan, just the ones you own.

    Just don't scan the normal UAD folder and you're good. Keep the UAD Powered Plugins folder intact because Console uses that location to load the plugins.  I hope this helps.

    (edited for a stupid spelling error)

    Sorry, I'm a little confused here. Is it something like this: Perhaps if I create a special folder for UAD plugs in my cakewalk vst folder, I can just copy the plugins I want/own from the current vst folder (x86/steinberg/powered plugins) and only have cakewalk scan that folder. Then run the newer update, copy anything I want from it to that cakewalk vst folder I made and never scan the steinberg folder where it gets installed. Then it will utilize any new console updates but cakewalk only sees the plugs in the cake vst folder? Something like that? Just wondering if the update/firmware itself might not allow me to run the older plugins. hmmmm Maybe i'm way off here... thanks! 

  3. 49 minutes ago, Tom B said:

    Yes, version UAD 9.12.2 has the older Neve 33609 version. Our registry data should be the same for UAD 9.12.2 (except, maybe path names).  

    The latest UAD version is 9.14.5.  I decided to update to that version about a week ago, and now have the updated Neve 33609C.  Interestingly, my Cakewalk test project was able to automatically find the 33609C. There are a few differences in registry data for UAD 9.14.5:  The dll  is now "UAD Neve 33609 C.dll",  the DosName is different, the uniqueId (i.e. plugin ID) is the same,

    My test project uses  Cakewalk 2021.04 (perhaps it started one rev earlier). I'm guessing your projects started out with earlier Cakewalk versions. 

    Note:  I haven't activated the 33609 plugin because it's only being used to understand this issue.  However, I don't think that matters.  For those not familiar with UAD,  the installation includes all the VSTs  whether activated or not.  I think this is done to make it easier demo and/or purchase the plugin.  An inactive plugin can be inserted, but it isn't functional.

    Thanks! I'll do some more digging!


  4. On 6/25/2021 at 2:03 AM, Tom B said:

    My UAD software is two versions behind the current version.  I have the older "UAD Neve 33609" (inactivated).  I'm wondering whether my older registry data might be helpful in understanding the update problem with the current "UAD Neve 33609c" experienced by Jono.

    If helpful, I'll post the pertinent data for the plugin such as:  DosName, UniqueId, Path Name, etc.  I'm running UAD V9.12.

    I've been delaying updates for UAD software because of a similar issue regarding the newly updated and enhanced UAD 'API Vision Strip'.  Eventually, I'll  update.

    I think I'm on the same UAD version 9.12.2 as that's the last version that still had the older 33609 version. Our data is probably the same


  5. On 6/21/2021 at 4:12 PM, Noel Borthwick said:

    >>Because the name has changed, Cakewalk will not open the Neve 33609 in older session files because Cakewalk identifies plugins by their name rather than a plugin ID#.

    I'm not sure where you got that from. Cakewalk has always utilized the plugin ID. However for VST2 plugin its not sufficient to do so (because the ID is not guaranteed to be unique and many vendors make mistakes). So we use an expanded ID scheme that utilizes part of the file name (in this case its the 8.3 file name). Many years ago I improved on this to be less dependent on 8.3 file names. However you must save your projects with the plugins for this scheme to kick in. If you have old projects they will not benefit from this obviously. 

    Also look into the details that Kevin posted above. If the session isn't opening its because the something more drastic changed in the name resulting in the ID's not matching. We don't have any UAD plugins in-house to test this with. Are the plugins still tied to UAD hardware?

    If you send a dump of your VST inventory from the registry and a sample project file that won't find the plugin, I can take a look at why it fails to load.

    Hey Noel, UAD support made the assumption it might have to do with plugin #ID. Cakewalk is the only DAW they've had reports on this issue. Other DAWs are not having the issue. 

    Don't understand all the 8.3 file name info, sorry. 

    The sessions are opening fine, they just won't open the updated plugin (that has a new name)

    When I say old files, I mean files that could be from yesterday, I don't mean ancient files. I use that Neve compressor on everything across a zillion sessions, so I really need a work around for this. I do tv/film and album production, projects can go on for years.

    I clicked on the vst inventory folder from the registry and clicked on export. Hope that's what you mean by a dump. I'll attach it here.

    I'll need to reinstall the whole UAD firmware and update in order to show you that CW won't open the plugin and send a sample file.

    I will do that soon. Here is the dump file (hopefully) *Too big to directly attach 6 MB, but here's a link on dropbox: https://www.dropbox.com/s/14v1v5k2xvwta50/VST inventory.reg?dl=0 

    Trying to understand the note above about making a specific folder for UAD. Currently, they get installed to x86 prog files/steinberg/powered plugins.

  6. On 6/20/2021 at 1:50 PM, scook said:

    There are a few issues with this setup though

    rescan plugins.jpg

    1) Do not have nested paths in the scan path.

    The image shows both "C:\program files (x86)\vstplugins" and  "C:\program files (x86)\vstplugins\eventide"

    The second path is unnecessary as any path under "C:\program files (x86)\vstplugins" will be scanned. 

    Having redundant paths causes unnecessary work for the scanner and has caused scan errors in the past.


    2) Do not leave the "Rescan Failed Plug-ins" and "Rescan All Plug-ins" enabled.

    By default, these options are off and are meant to stay off most of the time.

    They cause extra work for the scanner which can lead to scan failures.

    These are intended to be used to resolve specific one-off scanning problems.

    Once a scan is run with these options, they should be turned off.

    Running both options at the same time is functionally the same as a VST Reset.


    3) Enable Scan in sandbox.

    By default, this is enabled. This was added to improve the safety and reliability of the scanner.

    Hi scook, that screen shot is from another gent that commented on the post, not from me (OP Jono) I have my vst setup as you describe, no redundant folders etc. Sandbox, yes and no checks on rescan failed or all plugins. Don't think it's that. Gonna go through the rest of the comments. Thanks. J

  7. Hi there, I've been back and fourth with Universal Audio, complaining about an issue with their recent updates (last two updates)

    When UAD updates a plugin, they change the name of it. So, a "Neve 33609" compressor gets renamed to "Neve 33609c".

    Because the name has changed, Cakewalk will not open the Neve 33609 in older session files because Cakewalk identifies plugins by their name rather than a plugin ID#.

    I was complaining to UAD over and over that they shouldn't be renaming plugins, however they came back to me saying the problem is independent to Cakewalk because it uses the plugin title rather than the plugin ID#. They don't have complaints from other DAWs with this issue.

    This is a huge drag because it means Cakewalk/UAD users can't update their plugins or Cakewalk will not open older sessions that contain that particular plugin.

    It's something Cakewalk needs to fix. 

    How can I bring this to the attention of the right person at Cakewalk?

    Cakewalk needs to work properly with UAD, it's one of the best systems around (agree or not)

    Perhaps there is a workaround, not sure, i don't think renaming does anything.

    Who can I tag or where can i post this issue so that someone sees it?





  8. Hey there,  I had purchased Sonar Platinum right before the Band Lab thing happened years back.

    I know it's late in the game but is there any reason the Platinum version is better than the free bandlab version?

    Still confused about this.



  9. Hey there, when I update my UAD software to latest version, the "Neve 33609" compressor has been updated... all good except they changed the name to 33609c and Cakewalk doesn't open the plugin in any older session that have the original 33609 plugin. I think simply because of the name. (Which can't be renamed, doesn't work)

    Anyhow, I've gone to UAD tech support and of course no one has that problem... is it a Cakewalk issue?

    Anyone have a solution or work-around? I keep having to roll back my UAD version which is not what I want to do.

    Please help!




  10. On 5/25/2021 at 8:02 AM, rfssongs said:

    One thing that really bugs me is that when you slide tracks the automation lane does not move with it. Is there a fix for this ?

    Annoying, yes! I think you have to cut/paste or cut/paste special to include envelopes etc

  11. Hmmm. In Sound Forge, you select one bar and go to edit tempo and say how many beats are selected, it does the math. I thought there must be something in Cakewalk that can do it as efficiently. Perhaps audio snap or something.

    There really should be a simple plugin for that. I have on for iphone that creates a tempo map etc.


  12. Hey, is there anything I can use within Cakewalk that will tell me the tempo of an existing clip?

    I usually bring it into sound forge and do it there but wondered if there was something I could use in Cakewalk.



  13. I'll try to reproduce the issue and send a small bundle file.

    I know that consolidating the clips or trimming would prevent this, but sometimes you want to keep the clips un-bounced for various reasons. Like you might not wish to commit something.

    I only mentioned it as I don't remember it happening in the past.

    I rarely use the process/apply effect methods much anymore as there are so many ways of doing things nowadays.


    • Thanks 1

  14. Hi, I've noticed a bug in Cakewalk, where you select multiple clips, apply a gain effect, and get crazy distorted or missing clips after.

    If you do them one at a time the problem doesn't occur.

    The clips I've noticed often have clip fades on them.

    Anyone else get this?

  15. On 4/4/2021 at 8:45 PM, Clovis Ramsay said:

    You know whats funny about Mike's is that he avoids a step to keep from crashing his session which is EXACTLY THE SAME FOR ME!   To be able to quantize and slip edit multiple tracks longer than 30 secs long would be an ability I have not yet experienced with audiosnap.  The future is funny like that

    I've got most of this info in my brain now, a few things I didn't know. 

    The main thing I'm wondering is: How to get audio snap to put so many random, poor markers, right in the middle of a transient. Not even sure why it decides to put them there. It would certainly help to find a way to add the marker in a better place. 

    • Like 1

  16. Thanks for the info Clovis, such a great feature! Though, by the time I go through and correct all the weird markers etc. it's close to the time that it takes to do it manually. I will dig in and find out what I can. Just trying to get it to work better. Cheers


    • Like 1

  17. Hi, 

    Is there a place one can go to adjust the settings of how Cakewalk will "Split clips at audio snap pool"?

    Audio snap puts it's markers at the peak of the transient, I feel like that's not the best split-point when trying to quantize real drum multitracks.

    Also, after splitting, it seems to put crossfades but they don't cross, so there are gaps all over the place.

    Wondering if I can tweak any settings to get this working better?




    • Like 1
  • Create New...