refalogistics.blogg.se

1. 32 BIT VSTS WONT LOAD LIVEPROFESSOR INSTALL
2. 32 BIT VSTS WONT LOAD LIVEPROFESSOR 64 BIT
3. 32 BIT VSTS WONT LOAD LIVEPROFESSOR DRIVERS

Note the ASIO Link PRO windows can be closed (they will minimise to the taskbar) provided you keep the application that has called them open.Ħ. Doing so should pop open another instance of ASIO Link Pro window. Instead, select ASIO LINK PRO as the audio driver. DO NOT select ASIO SCOPE as the audio hardware device in the apps setting (you are at risk of BSOD if you do). Open an application with which you want to use the SCOPE audio hardware. Then ensure that "Enable multi-clients" is green (click it if red).ĥ. If not, click on "pick driver" and select it. COLLECTIVE 2018 near the top centre of this window, make sure it lists ASIO SCOPE as the device it is using. Press START ASIO in the ASIO LINK PRO 32 Tool.

32 BIT VSTS WONT LOAD LIVEPROFESSOR 64 BIT

With Scope 7 running, open the ASIO LINK PRO TOOL 32 - DO NOT run the 64 bit version (simply labelled ASIO LINK PRO TOOL with no number to follow) as it will cause a BSOD listing ScopePCI.sys as the problem.Ĥ. Then run the patcher for both the 32bit and 64 bit versions.ģ.

32 BIT VSTS WONT LOAD LIVEPROFESSOR INSTALL

Install the ASIO LINK PRO software (I find it helpful to check the box which states "install 16 stereo WDM devices).

32 BIT VSTS WONT LOAD LIVEPROFESSOR DRIVERS

Get your scope hardware installed in the PC with drivers functioning properly, software activated, and ASIO source/destination modules in your project.Ģ. My experience in getting this working runs as follows:ġ. If you are not comfortable with that, do not proceed, and do so at your own risk.

Please note: we are dealing with issues that can cause BSOD and consequent problems with Windows boot up, need for safe mode, etc. The software and the patcher for it are available here: I am very grateful to all involved in providing this. His nephew, who was passed the rights to the software, has blessed an effort by "Give Academy" to produce a patcher for the software which effectively makes it free to use. I bought this software years ago, and then the producer of it unfortunately passed away. The key problem solver here is ODEUS Asio Link Pro. Fortunately, this BSOD work around also solves this issue. In my case of a brand new installation, Windows was also not able to access to Scope Wave devices properly for bog standard MME playback: it would list the Scope speakers devices in the sounds control panel but could not use them. I don't think I am alone in wanting to be able to run ASIO using apps outside of a DAW that works with the SCOPE ASIO driver. Regardless of where the fault lies, users like me simply want a work around. Years ago, I tried to get garyb and FXPansion to work together to solve this with no success. Garyb (whose help I value enormously!!) will interject that this problem is caused by poorly written apps which don't implement the ASIO protocol properly, while the SCOPE hardware is not a regular windows soundcard. Like many users here, I run into frequent BSOD errors when I try and run standalone versions of VST instruments and access the ASIO Scope driver. I recently built a Win10 pro 64 bit PC for the purposes of running 3 Pulsar 2 PCI cards and with the idea of also using it to take some of the VST instrument CPU load off my main PC running Cubase.