for longer time I could not find out what's the problem with RackAFX not showing up after start: you can see a process running in Windows Task Manager, but the user interface does not show. On another computer however no problems. Recently I probably discovered the possible cause. After upgrading to Windows 10 Anniversary Update I noticed happily, that for the first time since long RackAFX DID WORK! AT the same time my Scope Pulsar board quit working, stating it can find no driver or card. I have two soundards in the "problematic" PC: SCope Pulsar (quite old, but still excellent - 17 years) and a common cheap PCI card. The problem seems to be, that if I want to use Pulsar, I need to install unsigned Scope driver, for that I must turn off windows driver signing, after doing so however Rack AFX behaves the way I discribed above. RackAFX version doesn't matter, it does the same thing in any version.
Can you do anything about it ?
To answer the question: no, there is no signed driver for Scope and there will be no one.
Thanks in advance
Some additional info: I reinstalled the distribution packages of VisualC++ 2008 (those were also included in the Scope installation package and overwrote the previous version). Now if I run RackAFX with Scope software driver, it shows some checks at the start, detects correctly the Scope parameters (sample rate, ports, etc.) and finally writes: 'Could not initialize the Port Audio system, then good bye. If I turn off Scope and want to run the other PCI card generic driver, it starts a process in the background, says nothing and does npothing
RackAFX uses the PortAudio library for all driver communication. I've only had one other user report an issue with it and that post is here:
The popular software Audacity also uses the same PortAudio library, so if you are having issues with RackAFX then it is likely that Audacity will also not run with your particular sound card.
The PortAudio initialization occurs early on in the startup of RackAFX. It is a single function call into the PortAudio DLL that gets a return code. If this call fails, then RackAFX will be mostly useless as you won't be able to hear anything. In the current Beta I've changed the behavior to check the most common errors and report these (guessing the error will be "Invalid Device") but not shut down RackAFX. In this way, you get the error code but could still use RackAFX in a limited manner.
Since the function call is into a DLL, there is nothing RackAFX can do if the call fails. Also, the function call has no parameters, so there is nothing RackAFX can change to try to get the initialization to work. I'm not sure if the PortAudio website has any information on bad behavior with certain sound adapters.
If you want to test the Beta version, use the Contact form and I will send you the password.
Most Users Ever Online: 152
Currently Browsing this Page:
Guest Posters: 1
Newest Members:duo.dirtykidz, Paul, Reakenzo, jflo, dan_1, phlub, josh, bmarx, Tom Helvey, Ludovic
Moderators: W Pirkle: 555
Administrators: Tom: 74, JD Young: 80, Will Pirkle: 0, W Pirkle: 555, VariableCook: 3