Jump to content

Promidi

Members
  • Posts

    4,308
  • Joined

  • Last visited

  • Days Won

    14

Everything posted by Promidi

  1. A couple of week ago, I was using a Beta version of Firefox. No matter what I tried, the version of Firefox would not allow Sonar to activate - even when opening the browser from Sonar's Help > sign out then sign in. The only way to fix this was to revert to the public release of Firefox 143 (which I am still on going forward). Another way I was able to activate Sonar was by temporarily changing my default browser to Edge for the activation procedure (changing back to Firefox when done). I am definitely going to be looking out for this issue when Firefox 143 becomes the release version.
  2. Maybe head to Preferences - Files - VST Settings and under “Scan Option”, set to Manual scan. Though this does not shield KV331from a manual VST scan from Sonar - at least you get a clean Sonar start up. The other option is to put KV331 in a folder that is not scanned by Sonar, but is scanned by Gig Performer. If you still want your plugins that Sonar can access to also be available in Gig Performer, then in Gig Performer, also include the folder where the Sonar plugins are.
  3. Works fine here What have you tried so far?
  4. If you have imported the INS files into CbB or Sonar Artist, then the INS file information would have been incorporated into your Master.ins file. For CbB, this file is in the following location. %AppData%\Cakewalk\Cakewalk Core Another option is, if you still have CbB (or Sonar Artist) and the instrument definitions are still in there, you can export the INS files from the Preferences - MIDI - Instruments > Define Instruments and names” dialogue. From the left pane, right click on the instrument, then choose “Export”. This will create the required INS files.
  5. I just revisited this. What happens if you set the Makers Window to non floating? Is the File > Print is still greyed out? On my PC, I set the Makers Window to non floating, then I was able to do a File > Print.
  6. I hate it when they refer to times by seasons... For us, Fall (or Autumn) officially starts in March 21 (ish)........
  7. See: https://legacy.cakewalk.com/My-Account/Products
  8. Just remember to deactivate any software iLok plugins from your Windows 10 PC prior to the upgrade.
  9. Another feature related to Remote Controls that would be handy is the ability to open up a dialogue box that lists all Remote Controls that have been set in a project, and what they have been mapped to.
  10. Note: This requires Kontakt Full (version 6 or later). The full Soprana installation requires approximately 18.3GB of space I could not find this information on their website. I had to contact support.
  11. I have a screenset that has a minimised Track View Window and this status is stored correctly.
  12. My projects have always remembered my zoom settings. My workflow is as follows: I use a locked screenset and a Workspace where I have configured that workspace not to load Windows Layouts and Screen settings. If I want to make a change to my screen layout in a given project, I open that project, make the change to my screen positions and zoom levels. Then quickly unlock, then lock my screenset. Then I save my project. This has always worked for me.
  13. Looks like this function was borked ages ago. I just tried it in Sonar Platinum, and when Markers list is displayed, Print and Print Preview is greyed out in there as well. Maybe drop a note to Sonar support. https://help.cakewalk.com/hc/en-us/requests/new
  14. You might have chosen a workspace that hides the Screenset module. Remember, Workspaces can load their own Control Bar configuration. Set your Workspace to None.
  15. Then it would be over to screensets to store Windows Layouts. I tried and it didn't do anything. Looking at keyboard preferences I am not sure how I was able to assign ALT+SHIFT+L to unlock/lock Screensets. Maybe it is hard coded in, but not documented. Then again, you would see it in your keybindings list. I do see ALT+SHIFT+L as being assigned in my Keybindings preference screen - shown textually, but not graphically (with the line pointing to the listed item on the right pane). If you look under the Views menu > Screensets, does “Lock/Unlock Current Screenset” have ALT+SHIFT+L next to it? It does on mine. This is there on my Sonar Platinum as well. If you unlock this, (using the menu as your ALT+SHIFT+L keybinding does not seem to be available to you), does this now remember your Windows position? Note: Every project uses at least one Screenset. If no Screenset is explicitly set, you would be using the first one. In your case, it’s locked. Maybe this is your issue?
  16. Depends on your ASIO driver. On my system (config as per sig) , I can have multiple standalone music applications accessing the same ASIO driver. They can all be using ASIO driver mode. If I ever need to do that, I make sure sample rate, but depth and buffer size is the same in all applications.
  17. Head over to Device manager (Start + run > devmgmt.msc) and view hidden devices, delete all unwanted midi devices. See if that works for you.
  18. Have you considered setting up your windows as you like them, then locking your screenset(s)? Also if you use the windows layouts in locked screensets, and you wish to use Workspaces (only available in Sonar Premium), then create a custom Workspace that is configured not to load Windows Layouts. You do this in the Workspace Manger. If I want to change my Windows layouts in my locked Screenset, I move my Windows to where I want them, then do a quick Screenset unlock/lock with a double press of the ALT+SHIFT+L Keyboard shortcut. Done! This has been my workflow since Lenses (as Workspaces were known as then) came out.... and my Windows layouts have never changed unintentionally.
  19. Where in the Preferences are you confirming that it's 24bit? Note: The Preferences screen you are taken to by clicking on the “48 / 16” in the transport Module is not it.
  20. Check %USERPROFILE%\downloads\Cakewalk
  21. I think that is for the Inspector. @Robert GlaserWhat happens if you undock the PRV?
  22. Did you configure your Workspace not to load Windows Layouts?
  23. Something weird is going on there. The "Manage Workspaces" menu item should not be greyed out. I can select Factory and User Workspaces and "Manage Workspaces" is accessible here. It would seem that if "Manage Workspaces" is greyed out , then there may be other issues going on pertaining the Workspaces on your PC. Have you contacted Cakewalk support about this?
  24. For the Workspace you are using, select that workspace. Then open “Manage Workspaces”. This is where you can configure that specific Workspace. In your case, in the right hand pane, under “Load from Workspace” deselect “Windows Layout”. (for mine, I also deselect “Keyboard Shortcuts”). Then click “Apply”, then “OK” Now when you load that Workspace, your Windows Layout from that Workspace will load and therefore will not change. Regarding Screensets: Under the “View” menu, the last item is “Screensets”, drill down to see the actual screensets. If any have a padlock to the left of the name, then that screenset is locked. It should be noted that, by default, screensets are not locked, so this may not apply to you - unless you intentionally (or accidentally) locked your default screenset. ALT+SHIFT+L toggle the current screenset lock status. Note: I do actually lock my screensets to prevent accidental windows layout changes from being applied.
×
×
  • Create New...