GUI locks up DAW SONAR PROFESSIONAL Windows 10
Can you advise me on this
@rannijohns Please provide a bit more detail. Can you run the Unify stand-alone OK?
The audio output can be heard but there is no activity in the graphic interface. Drop downs are stuck in drop position. “Not Responding “is the message I’m getting within DAW
I running Window 10 on DellXPS10 i7 gen intel processor with multiple cores 64 GB Ram. Focusrite Safire pro audio interface
Dell XPS 10 “desktop”...
Sonar has been discontinued in November 2017 and as far as I know there wasn't any updates since then - I wouldn't be surprised if it's not compatible with the latest version of Windows. I'd strongly recommend to switch to Cakewalk by Bandlab (this is a successor of Sonar and its available for free now - and it's being updated monthly). All your Sonar Pro plugins are also compatible with this (you'll need to keep your original Sonar Pro installed). I've been using Cakewalk by Bandlab with Unify for a while and it works with no problems.
Here is the screenshot of Cakewalk by Bandlab with Unify docked to the multi-dock window - you can dock as many instances of Unify as you want and then quickly switch between them just by clicking the tabs at the bottom.
- @robert-p. I’m running the latest version of Bandlab Cakewalk Professional. I appreciate your comments
I see. Does changing Cakewalk preferences make any difference? (ie. check-boxes "use multiprocessing engine", "plugin load balancing" etc). It also may be related to your specific computer/OS configuration. Also, updating the graphic card drivers sometimes can fix the GUI problem. In my case, everything works fine: Unify and Cakewalk on Win10pro ver 2004, on Dell Precision mobile workstation with 16GB RAM
- @getdunne The fact that standalone is running with no problem suggest that DAW is probable cause??
- @getdunne I have an old version of Sonar X2 running Unify and so far it’s stable. I’ll monitor for a while longer. I will try to uninstall Bandlab and reinstall it to see if that makes a difference. I appreciate your help
Here we are almost 5 months later and still have issues using Unify 1.2.1 with latest update version of Cakewalk BandLab. Please note that you, in a previous reply, suggested that the probable cause was with DAW, since it responded well in Standalone. I want to point out no other software synth or plugin presents this type of issue, making me believe that there is a unique relationship with Unify and Cakewalk where as it’s the only plugin that this happens. If others instruments were experiencing the same problem then I would consider identifying then making adjustments to the config files in Cakewalk. Would appreciate any feedback. Running Window 10 on Dell XPS Desktop on C:/ SSD, 64 Gb ram and Unify data folder is on D:/1TB Focusrite FireWire Pro 26 Audio Interface
I have been using Unify (all versions) with Cakewalk by Bandlab since the first release of Unify, and have had only one problem that was solved in the current update of Cakewalk (it was a Cakewalk problem). Otherwise, Unify has worked well. I would be happy to help if I can. I have songs with as many as 7 instances of Unify, with some of them having many instruments. I have run into a situation where I was just overloading my computer, but that was only when I was going crazy adding instances with multiple instruments.
Does this problem occur with a single instance of Unify that has only a single instrument?
I would be happy to share settings with you, if you like. I am also running on a Dell Precision Workstation with all SSD drives, as is RobertP. I also have a Focusrite interface (Scarlett 2pre).
i usually run only 1 instance and varies the nunumber of instruments in a patch. It starts out running smoothly but what triggers the freeze I have not been able to ascertain but once it locks I have to close that instance and start a new. What really has me baffled, why it happens only when using Unify. No other soft synth presents that kind issue within Cakewalk
Are you, by any chance, copying a Unify track to another track? That was the problem that locked up Cakewalk, and in fact made it crash. It was fixed in the latest Cakewalk update.
If you send me a project folder with all the assets that demonstrates the problem, I will try it on my system. You can upload it here as a zip file.
This will be a difficult issue for me to debug, because I don't have that DAW, and I don't think it's even available anymore.
I'm sorry that Unify is working poorly for you. Please do continue to gather evidence and try to find out what triggers the problem. That may be enough to help me identify the cause.
The DAW that I’m using is the latest version of Cakewalk Bandlab not Sonar Professional which has been discontinued. No matter which version the problem persists. I will continue to work with this hopefully something will show itself. Thanks
@rannijohns This is good. I have Cakewalk by Bandlab, so (at some point, when I finish chasing bugs) I'll be able to test.
I installed Evaluation Version of Reaper DAW and ran one instance of Unify, no problems at all still running since this morning. I’m leaning towards swapping out DAW to Reason or Avid Pro Tools
As far as I remember the default option in Cakewalk is to omit any Vst2 plugin if Vst3 version is also available. Try to force the Cakewalk to load Vst2 version of Unify either by changing the application settings or by temporary moving Vst3 dll to another location.
Robert P, I’m showing 2 instances of Unify in my list of Soft Synth “Insert Soft Synth“drop down. Would that be a good indicator that VST3 and Vst2 are present and competing with each other and causing the glitch effecting the GUI. Are you running Unify from your C:/ I have data folder on internal D:/ and Unify is operating from C:/Programs/Unify. What should the proper file structure be with both on same drive?
Just maybe my file structure is whacked when first install and then subsequent updates 🤔
Anyone familiar with this thread please respond. Consistently observed lockup of GUI when initiating the recording of Midi data to a track using Roland A 800 Pro Controller input source to Cakewalk Bandlab(Sound on Sound or Comping)Does this point you to anything relative making a link between the two?
I do not have a Roland controller, but I record midi on Unify tracks all the time with my Focusrite Scarlett 2pre and Korg Triton Le into the Focusrite midi in using Cakewalk by Bandlab.
How are you setting up the tracks? Do you add a Unify instrument and just record on that track, or use a separate midi track?
Are using CBB update 1 (build 26.11.0.099)?
Is the Roland A800 Class Compliant or does it need specific Roland drivers? I'm wondering whether it's an issue with the drivers for the Roland. Is it only Unify that locks up in this scenario? Do you have any other MIDI devices that you can try to record with to see if you still get lockups? Maybe even using the virtual keyboard or an IOS/android tablet with a MIDI controller app.
I have also never had any issues with Unify in Cakewalk by Bandlab (running the latest version of both here). I currently have a Nektar Impact LX61+ controller and had an Arturia Keylab Essential 49 before that which worked fine with CbB and Unify.
Yes sir, only Unify, only within DAW, no other soft synth. I can maintain audio output but not able to navigate other features like add layer or add patch to current layer. I’ve kinda ruled out Controller, OS, Audio Interface which leaves me with Cakewalk or Unify. Unify standalone is fine, so Unify within Cakewalk is my conclusion. But what and why, I’m lost, out of my pay grade and technical savvy. I’m gonna try using older version of Cakewalk Professional and see plus change out Audio Interface from FireWire to Focusrite USB CLARET 2Pre... see what happens
How about your Cakewalk MIDI settings for recording and playback? See how they compare to mine (attached).
Cakewalk MIDI devices - I'm assuming your Roland presents as two devices - one for the keys and the other for the transport controls etc. Can you see both on the MIDI devices settings and are they both selected.
Are your plugin scans up to date in Cakewalk and in Unify using the same scan paths. I have had problems when the two reference the same plugin but one is out of date compared to the other.
Have you ever swapped the USB connection for the Roland controller i.e. moved it to a different USB port than it was originally connected to with Cakewalk by Bandlab? If your USB devices switch which ports they are connected to then that confuses Cakewalk. Just to rule this out try going into Cakewalk Preferences, and explicitly removing the A800 midi controller as a MIDI Input device and as a MIDI Output device and click Apply.
Then exit Cakewalk, and relaunch it. Then add the A800 back in again and that should re-establish its connection to Cakewalk.