![]() Delete the Liquid Rhythm folder within your User folder. ![]() Some Mac users have run into an issue where they will install Liquid Rhythm and upon startup they keep getting this message. You can also try a complete uninstall (and reinstall), and if that doesn't help please contact Apple Mac TroubleShooting Steps ![]() If you are still having issues and get a Windows crash report then please look at this article: Liquid Rhythm Standalone crashing. If you launch from the command line (Command Prompt or PowerShell), and it fails, it will sometimes produce useful diagnostic information. If it doesn’t appear, we can launch LiquidLoops.exe from the command line. In the Task Manager you want to observe the LiquidLoops.exe which is the Audio Engine for Liquid Rhythm in standalone mode.Ĭtrl-Alt-Del to show the task manager to verify that LiquidLoops.exe is able to launch. You can launch the Task Manager by hitting the ‘Ctrl-Alt-Del’ key on your computer at the same time. One driver we have had an issue with specifically are the M-Audio/Protools drivers.Īfter a successful Liquid Rhythm launch, we would expect to see two Processes listed in Task Manager, as shown below. Please check if the audio drivers are up to date. ![]() In some case, old drivers in the system will cause it to fail abruptly. In testing at WaveDNA, we discovered that the Audio Engine will attempt to discover all of your audio related drivers. If LiquidLoops.exe starts, but then soon disappears, it likely means our Audio Engine failed in its startup. If you have tried launching Liquid Rhythm use the Task Manager to see if there are both processes are started. Would you like Liquid Rhythm to try again? (It’s recommended to try again at least once). Liquid Rhythm is having difficulty starting up its Audio Engine (LiquidLoops.exe). Warning message received when Audio Engine cannot be started by Liquid Rhythm. Note, these troubleshooting steps do not apply if you are launching Liquid Rhythm as a VST/AU/RTAS plugin or through the special Max For Live integration. The first thing to note is to give the Audio Engine a chance to startup, before attempting the troubleshooting below. Of course, if you are ever stuck or need further help, please don’t hesitate to contact Warning MessageĬhances are you are on this page because you receive the following warning message when you started Liquid Rhythm. If Liquid Rhythm will not launch in standalone mode, here are steps we can take to help trouble shoot the problem. On subsequent launches, it should take less time. Usually on the very first launch of the application after a fresh install, the audio engine takes longer to startup, as it needs to configure itself to the new environment and version. When we are run in a standalone mode (for example, if you launched Liquid Rhythm by clicking on the icons on your desktop), we use Cycling ’74 MaxMSP as the core component of our audio engine. Thus when Liquid Rhythm starts it will launch two processes, and the graphical user interface will need to connect locally to the second process. The main application’s graphical user interface is separate from the Audio Engine for performance reasons. Liquid Rhythm runs in a two process model.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |