Jump to content

Michael Vogel

Members
  • Posts

    578
  • Joined

  • Last visited

Posts posted by Michael Vogel

  1. On 11/27/2019 at 6:59 AM, craigb said:

    Kids who are too young to have ever seen them: "What's a record?" 😏

    It’s a very large, double sided CD with one long groove on each side. My description, many years ago, to a 10 year old who fit your description as I was showing him a “record player” at a HiFi show.

    • Haha 1
  2. Jim Rosebery does this for a living. He provides a paid for service where he will spec a PC for you to purchase the components and assemble yourself. I’ve used the service myself and its well worth the small fee. Used to be US$40/half hour. I told him my budget and he provided a list of component choices (that his company has tested for compatibility) with links to where I could buy them. I’m in Australia so I got mine locally but knowing the components were tried and tested gave me all the confidence I needed to make my choices.

    • Great Idea 1
  3. Further info.

    I’ve checked all my other duplicate VST2 and VST3 installations and it seems that only Waves V11 were effected.  ie. not respecting the:

    Preference settings “Hide related VST2 plugins and/or Replace if possible on project load”.

    Possibly a waveshell or update to V11 problem. The only way forward is to create a special VST2Plugins folder for just the Waves plugins and leave that folder out of the CbB VST scan path. This will make the VST2 versions available for a few programs I have, that are  not yet able to make use of VST3 plugins.

  4. 11 hours ago, scook said:

    I can find no reference to Toontrack releasing this in VST3 format. I usually only install VST3 when given the choice and I only have the VST2 format installed. Just ran the update to be sure. Can't say anything about the other Toontrack plug-ins, SD3 is the only one I own.

    You’re right Steve. Whilst all the Toontrack Plugins were Installed into the default VST3 path they are in fact all VST2. Weird. I cant explain how the plugins were installed incorrectly. Like you, if given the choice to install VST3s I choose them in preference to VST2s. Cakewalk accurately allocated the plugins as VST2s. I’ve been completely confused by their location. Obviously the plugins don’t have the VST3 extension in the file name.

    Still there is a problem regarding a situation where both VST2 and VST3 versions of the same plugins exist on the system. CbB will not recognise the VST3s. Eg Waves VST3 plugins (I have them all) were not recognised by CbB until I renamed the waveshell file for VST2 plugins so it wasn’t scanned. I’m having a similar problem with the latest version of (EWQL) Play which now doesn’t load at all  despite renaming the VST2 version so it doesn’t scan  Renaming a plugin refers to appending “.old” extension to prevent scanning without deleting the file altogether.

    I have confirmed this to be the case regardless of the Preference settings “Hide related VST2 plugins and/or Replace if possible on project load”. 

    11 hours ago, Noel Borthwick said:

    If they show up in your VST2 menu then there is definitely a VST2 plugin in your path.
    You can check the registry key to see what dll its pointing to.

    For example:
    HKEY_CURRENT_USER\Software\Cakewalk Music Software\Cakewalk\Cakewalk VST X64\Inventory\c:/program files/Cakewalk/vstplugins/SI-Bass Guitar/SI-Bass Guitar.dll

    The FullPath value in this case shows "c:\program files\Cakewalk\vstplugins\SI-Bass Guitar\SI-Bass Guitar.dll"

    You can also look at the path by viewing the plugin properties from the effects window after inserting the plugin (from the VST2 dropdown).

    Thanks Noel. I’m aware of all this and did all these things before posting. My initial problem was regarding the Waves VST2 plugins showing up despite having VST3 plugins installed as well. The Toontrack plugin “problem” only came to light as I investigated further. See further on in this post.

    As per my reply to Scook, That’s been the problem as the VSTscan log clearly shows that the Toontrack VST2s were installed into the VST3 default path. Have no idea why. Ive fixed that by moving the effected “.dll” files to their appropriate VST2 path and Resetting/Rescanning.  

    However - There is a problem regarding a situation where both VST2 and VST3 versions of the same plugins exist on the system. CbB will not recognise the VST3s. Eg Waves VST3 plugins (I have them all) were not recognised by CbB until I renamed the waveshell file for VST2 plugins so it wasn’t scanned. I’m having a similar problem with the latest version of (EWQL) Play which now doesn’t load at all  despite renaming the VST2 version so it doesn’t scan. Renaming a plugin refers to appending “.old” extension to prevent scanning without deleting the file altogether.

    I have confirmed this to be the case regardless of the Preference settings “Hide related VST2 plugins and/or Replace if possible on project load”. 

    I need to check other programs I have to see whether this is a CbB or global problem with my installations.

    BTW I’m on the very latest Win 10 Pro 1909 update And CbB 2019.11 update having previously run Early access 2019.11 when I uncovered the problem.

  5. It’s really weird  With the Toontrack plugins, I’ve reset the plugin database and scanned again and have a log file. It clearly shows the plugin files are in the correct Program Files/Common/VST3 folders but nonetheless continue to show up in VST2 menus etc. 

    The plugins work fine they are just in the wrong menus  

    i’ve even uninstalled the plugins, deleted the Registry key for the Cakewalk VST hive, reinstalled and it’s still the same. I’ve restarted the system to clear any possible memory issues. 
    in the plugin Browser window, those plugins are a different Color tone than other VST2s. I’ll have to organise some screenshots. Sorry I haven’t done more yet to follow up.
    This caught by complete surprise 3 days ago when  I installed the Early Access 2019.11.54 file. It had not been like this with 2019.7. I had to install 2019.09 to permit the Early Access installation but I never ran that version.  I went straight from 2019.07 to 2019.11
    I run Cubase 10,5, Studio One Pro 4.5 and a few other programs that use VST plugins so my next step is to check them to see if this is a global or CbB specific issue. 

  6. Problem from Early Access 2019.11 persists in update.

    Waves V11 VST3 and VST2 installed only VST2 showing in Cakewalk. Had to uninstall VST2 before all my VST3 V11 Plugins show properly.

    Toontrack Superior Drummer V3 and EZMix, and EZKeys etc. I only have VST3 installed but all Toontrack programs show in menus and the Plugin Manager as VST2. When i load the plugins I see a VST2 drop down. Don’t understand this as only VST 3 installed ion the computer. 

    I haven’t tried other plugins yet but it’s very weird. Add EWQL Play to the list only when deleting VST2 version the VST3 version doesn’t appear in the Manager or menus. It’s in its installation directory as expected.

    Is it a Win 10 latest update problem? Or CbB?

  7. On 10/26/2019 at 3:08 AM, InstrEd said:

    Really I think most of us here having another DAW or two just in case CbB doesn't make it. Plus for me the other DAW's do things that CbB doesn't do at the moment. 

    I have many many DAWs for compatibilities sake for clients. Having now retired though that’s no longer necessary however. 
    None were bought in case Cakewalk doesn’t make it. I did however buy Cubase 9 ( or 9.5, I forget which) when Steinberg made an attractive cross grade offer at the time Gibson dumped Sonar. It was an opportunity to get a DAW I had thought was too expensive up to that time. 
    While there are some features I would love Cakewalk to adopt from others, there are none that important that their being absent in CbB,  push it to second place for most of the work I do now. 
    Occasionally, I try using other DAWs to start a project but none feel as comfortable or familiar as CbB. Anytime a musical idea comes to the fore it’s CbB I load up to give substance to my creativity. 

    • Like 3
  8. On 10/24/2019 at 4:09 AM, Misha said:

    Still does not answer specific question I asked... C'mon guys and gals, stay focused, it is really not that difficult.  90% was answered by Noel, the last 10% is, will a cloned HD with active Cakewalk will work on same machine clone was made from without server authorization/offline?

    Thank you. 

    I’m pretty sure that cloning a drive will not circumvent the need to contact the server every 6 months. I just think this would have been big news in a lot of computing areas and we would have heard about it.

    HOWEVER:
    If it was me that was so concerned I would conduct an experiment. 
    1. Create a  cloned Drive making sure to record the date. 
    2. 6 months and 1or more day/s from that date, restore your system with the cloned  drive and see if CbB goes into Demo mode. Of course make a backup so you can flip back to your “current” system at that time. 
    3. Report back here to tell us the wonderful or not wonderful news. 

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