Notifications
Clear all

UAD Apollo X8 hangs when browsing some patches

2 Posts
2 Users
0 Reactions
468 Views
(@brucew)
New Member
Joined: 4 years ago
Posts: 1
Topic starter  

This is a random issue but consistent using Unify 1.1.10.   Loading some Unify patches causes the audio to stop.  I have to go into the settings menu under Audio/Midi and reset the interface.   I was wondering if anyone else is having this problem.   

I had the buffer settings set to 128 samples and then tried 512 which seemed to help a bit.   Maybe you could add a way to change the buffer setting from within in the Audio Settings?  or auto-adjust it?  Right now it only displays the setting. 

I had a similar issue another app called Lie from Expressive E Touche and they fixed it in their latest release after I submitted a bug report.  Could it be a similar issue on Unify?   

I am using the latest UAD driver 0.12.2 and I'm on Windows 10 Build 19041.450 (v2004).

 

Suggestion ideas:

I have a couple of UI suggestions for the main window.  I find it extremely annoying having the browse windows close every time you select another window.   It just doesn't want to stay pinned open.  Maybe another user setting to have it stay pinned if others like the current behavior?

The CPU meters I find mostly useless as there is no reference for the bar activity.  It would nice if there was a percentage of CPU time also available when the CPU meters are visible?

 

 

This topic was modified 4 years ago 2 times by BruceW

   
Quote
(@getdunne)
Illustrious Member Admin
Joined: 5 years ago
Posts: 4435
 
Posted by: @brucew

Loading some Unify patches causes the audio to stop.

Which patches?

Maybe you could add a way to change the buffer setting from within in the Audio Settings?  or auto-adjust it?  Right now it only displays the setting.

This may be a limitation of your particular audio device driver. The displayed value can normally be changed.

I find it extremely annoying having the browse windows close every time you select another window.

This is on the to-do list. Many people find this irritating, myself included. I did it originally because if you change patches (even accidentally) in any view other than the layer-stack view, there is no visual feedback. Possible alternatives include:

  1. Leave the patch browser open, but disable it when any view other than layer-stack is chosen.
  2. Automatically switch to the layer-stack view if the patch is changed while in any other view.

The CPU meters I find mostly useless as there is no reference for the bar activity.  It would nice if there was a percentage of CPU time also available when the CPU meters are visible?

Have you read the user manual page about the CPU meters? It explains why the standard operating system "percentage of CPU time" has little meaning for audio applications. Nothing is stopping you from opening the Windows Task Manager to see overall CPU usage.


   
ReplyQuote
Share: