Jump to content

HIBI

Members
  • Posts

    602
  • Joined

  • Last visited

Posts posted by HIBI

  1. First of all, I personally think that changing the OS drive from HDD to SSD is worth more than the cost. This is because the processing speed associated with drive access will increase dramatically.

    However, your PC is not officially compatible with Windows 11. Support for Windows 10 will end in October, but do you have any plans after that?
    That will affect whether you should upgrade to an SSD or get a new PC.

  2. On 3/1/2025 at 2:00 AM, MisterGreen said:

    It gets worse when I move my mouse around.

    This may be off the mark, but if you have a wireless mouse that uses a USB dongle type receiver, this could be the cause. In that case, try moving the USB receiver to a port a little further away (such as the front port).

  3. 5 hours ago, Glenn Stanton said:

    so, in terms of the understanding established to some degree on this forum: SONAR (all caps) = SONAR and derivatives from pre-Bandlab days. Sonar (proper case) is the new DAW product from Cakewalk (a Bandlab brand). think of it as "case sensitive programming"

    This comment by Cakewalk staff below will further clarifies your view.

     

  4. 20 hours ago, msmcleod said:

    So Tonex 1.6 was installed,  I updated to 1.7.1 and it crashed Sonar... so I did my usual with VSTi's that are also stand-alone:

    1. Run Tonex standalone... let it sort itself out, then exit the app
    2. Run Sonar
    3. Run VST scan from Preferences
    4. Drag Tonex into an FX bin -  success!

    What will be changed by step 1? (Is it mandatory?)
    Does step 3 simply scan without resetting?

  5. 33 minutes ago, Kevin Walsh said:

    That wasn't the problem in this instance.

    Yes, I knew, that because it seems you were creating a folder with a different name (IK-TONEX), so my comment was not directly relevant to the problem you had.

    I was merely referring to what often happens with recent plugin updates in response to OutrageProductions' comment. Sorry if I confused you.

    Anyway, I'm glad to hear your problem has been resolved.

    • Like 1
  6. 19 hours ago, OutrageProductions said:

    CbB has had similar issues with other (but, strangely, not every) plug that gets installed into a nested folder with a vst[3] in the name, like Spitfire BBCSO Discovery and several others.

    I am guessing that the problem may occur in the following case.

    If an old version "C:\Program Files\Common Files\VST3\PluginName.vst3 (actual plugin file)" is originally existed and it's already scanned with Cakewalk, and a subsequent update installed the actual plugin file "PluginName.vst3" under a folder named "PluginName.vst3", such as "C:\Program Files\Common Files\VST3\PluginName.vst3 (folder)\Contents\x86_64-win\PluginName.vst3 (actual plugin file)".

    In this case, resetting and rescanning the plugin may solve the problem. (Just rescanning is not enough)

    So, I believe the baker should review the behavior of "VstScan.exe".

    • Like 2
  7. My understanding is that when the trial period expires, the editing functionality is locked and it switches to Melodyne player which can playback only, and there is no charge. Therefore, there is no need or way to cancel your trial.
    (If you want your editing functionality back, just purchase license and activate it)

    FYI: If I remember correctly, in the previous version Melodyne 4, some functions such as "audio to MIDI conversion" were still available after the trial period ended, but they should not work after version 5.

  8. "ACEDAO.DLL" appears to be a file related to Microsoft Office.
    In the Cakewalk preferences, has a folder other than the plugin folder been added as the scan path for the VST plugin? If a non-plugin folder is listed in the "VST Scan Paths", remove it.
    (e.g. "C:\Program Files", "C:\Program Files (x86)", etc...)

    If you are not sure how to set it up, please provide a screenshot of the Preferences - File - VST Settings.

    Or, if by some mistake you have copied the file "ACEDAO.DLL" into the plugin folder, simply remove it. (Might need to put it back where it belongs.)

  9. The activation toast appeared and automatically opened the browser login page. All I had to do was log in.
    FYI: Nothing happened when I clicked on the notification toast.

    This time it seems to have expired after about 3 months instead of 6 months. Maybe something changed on the back end.

  10. When you say cwp icon, are you referring to the icon image of the project file or the project file (*.cwp) itself?

    If you cannot find the project file itself, try to search the entire drive by typing *.cwp in the Explorer search box.

    If there is no icon image in the project file, check the cwp file association.

×
×
  • Create New...