When you come to the "rogue" VST, I'd expect the problem to reappear and you've found the culprit.Īmen, Jazzmammal.
One way to find out is to remove all VST stuff from the folder where you've assigned BB to look for them by copying and pasting All to another folder, then start bringing in one VST at a time and start up BB, play a song and shut down BB. *Peruse your VST/VSTi stuff that BB is pointed to, there may be one in there that is not working and playing well with BB.
*Switch to MME sound drivers inside BB, just to see what happens. Return to Factory Settings rebuilds that file for you. So the first crash can create a corrupted file from there on out. This is especially important after a crash, because there is a certain file (intrface.bbw) that BB must write to when it closes down and a crash doesn't allow for that to happen. * Use the BiaB Options -> Return to Factory Settings and hit the second button down so that the soundcard and MIDi synth choices get readdressed. Therefore it is still assigned to BB, but the program is no longer available. I think it is more than likely the case that whatever is causing the crash of BB does not allow for release of the Soundcard Driver. #69699 - 04/13/10 09:19 AM Re: patch 298 not the silver bullet for song ending crashes bb 2010 is a great step forward, so folks reading this post shouldn't get discouraged. Hope this helps fix bugs as you work on the next patch or release. I am resorting to tags as a work around for endings, and have not had a crash yet when I make a tag and completely remove endings in the song settings window.īesides the problem stating before, which is the most worrisome in the short run, using endings has the side effect of RT still improvising on the 2nd bar of the ending (for like a bar or two) and/or loud pops and hisses at the very end. I have gone into the song settings and disabled endings, changed from 2-bar RT to 4-bar RT and back again, and nothing seems to fix it. I know this from trying to logoff/login on my Win 7 machine to try to avoid a hard boot after a crash. I think it has something to do with the ASIO buffer since that becomes unavailable after bb crashes. I got the 298 patch, and it seems to do it slightly less often, but still happens if I don't hit the escape key before the ending (+ a few seconds.) I can't close the program on Win 7 64-bit, so each time I have to reboot. Thanks again to all concerned, very much appreciated.Within a few seconds of a song ending, bb crashes hard. Where is it possible to find a compatible ProFx or, what recent version is compatible. I found UFX for KX 3552, after searching HardwareHeaven, seems all the links to the most recent ProFx are dead. The KX listing seems to work from my limited testing, setting outputs from DAW into DSP seemed fine, yet to try inputs.Ģ.
When the 64 bit ASIO driver appears in my DAW, I see drivers listed as, KX, ASIO 1 (to) ASIO 7.
So far, though still early days (a few weeks) everything seems to be working, albeit after a lil registry (correcting paths to the 32 bit KX Mixer) and manually installing 64 bit ASIO jiggery-pokery.ġ. I recently bought an Audigy2 ZS and drivebay (SB0350/SB0250) for a Windows 7 64 bit system. I used to use KX with a sounblaster platinum live/live drive II for a number of years.
Hello all, firstly, a big thankyou to all who continue to eek out a little more life from the soundblaster/kx driver combo.įurther thanks to the developers of course. However, the ASIO Control Panel will open from within the Host program. Platinum runs better, but I wish we could use the 圆4 kX ASIO natively in Windows 10.Īlso, the 64bit kXMixer will load without error, if run in Windows 7 compatibility mode, but the ASIO control panel wont open by right-clicking the kX Manager icon in the taskbar and going to Settings>ASIO Control Panel. I'm using SONAR X3 and SONAR Platinum, but X3 runs kind of sluggishly in Win 7 compatbility mode, and the sliders for volume and such on the SONAR GUI can't be adjusted smoothly as normal.
exe and select Properties, select the Compatibility tab, place a checkmark in the box next to Run this program in compatibility mode for, and choose Windows 7 from the dropdown menu.
dll should register.ģ) Run in compatibility mode the software you will use the 64bit kX ASIO in. In the Command Prompt: type " cd C:\Program Files\kx Project" (without the quotation marks) and hit enter, then type "regsvr32 kxasio.dll" (without quotation marks) hit enter. Go to the Start menu> All Aps> Windows System and right-click Command Prompt and select Run as administarator, select Yes if the UAC prompt comes up. The Solution is to manually register the kxasio.dll and to run the DAW Host software in Windows 7 Compatibility mode.ġ) Use mole2old's fix posted in this thread.Ģ) Manually register kxasio.dll in C:\Program Files\kX Project I found a solution to get the kX ASIO driver to show in 64Bit DAW Hosts in Windows 10 Pro 圆4.