hello all,
on my labtop i have the following problem :
no way to produce any sound with any VSTi instrument. the VSTi is correctly plugged. I tryied with the VST and the DX version ( hypersonic2). I have set up BIAB to re direct midi out to the DX instru, ...
and also the problem when i want to use internal Midi instrument ( microsoft or internal SW instruments). BIAB returns me that the midi instru is correctly installed but used by another application...
On my desktop station, no problem.
BIAB 2006 with latest update.
sound card : echo indigo (PCMCIA ).
Emu USB Xboard Keyboard.
thx for the help. BIAB is a great software
From the BIAB 2006 TechFAQ page:
Quote:
95. When I try to use the Roland VSC as my output driver, I get the message "...installed properly but currently in use by another program", even though there are no other programs open.
These instructions apply to Windows 2000/XP. Other possible symptoms are:
"Audio Conversion cannot be started" error message when you attempt to Direct Render your song to a wave file using the VSC.
When you open the VSC as a stand alone application (Start menu | Programs | Virtual Sound Canvas...), you may get the error "MIDI device or the audio device to be used for VSC's audio output cannot be opened. Playback unavailable at this time"
There are a few possible solutions. You should be able to resolve the problem by following one or more of the suggestions below. Alternatively, use the VSC-DXi instead of the VSC-3 stand-alone version.
Select something other than the VSC as your default MIDI driver in Windows
On Windows XP, go to Start | Control Panel | Sounds and Audio Devices | Audio tab. On Windows 2000, go to Start | Settings | Control Panel | Sounds and Multimedia | Audio.
Select something other than the Roland VSC for default audio and MIDI playback.
Restart your computer.
Make sure vscvol and vsc32cnf are enabled at startup.
Go to the Start menu | Run, type "msconfig" and press OK. This should open the System Configuration Utility. Note: Windows 2000 doesn't have the system configuration utility.
Click on the Startup tab and make sure there are checkmarks beside 'vscvol' and 'vsc32cnf'.
Press [Apply], then [OK], and restart your computer.
Reinstall the VSC
Uninstall the Roland VSC using the Add/Remove Programs utility.
Right-click on My Computer and select 'Properties'.
Click on the Hardware tab and press the [Device Manager] button.
Expand 'Sound, Video and Game Controllers' and look for 'Virtual Sound Canvas'. If you see it listed there, right-click on it and select 'uninstall'. Restart your computer.
Reinstall the Roland VSC. If you get a message saying that the VSC has not passed Windows Logo Testing, you can "Continue Anyways". You should be prompted to restart your computer again after the VSC has been installed.
Go back to 'Sound Video and Game Controllers' in the Device Manager.
Right-click on the Virtual Sound Canvas 3.2 and select 'Properties'. Make sure that Device Usage is set to "Use this device (enable)".
Change your audio output device settings in the VSC
Click once on the VSC icon in your task bar, point to 'VSC Settings Window' and click on 'Device'. Or: Go to Start | Programs | Virtual Sound Canvas 3.2 | Virtual Sound Canvas 3.2 to open the VSC panel, then click on the [Setup] button and choose the Device tab.
If the audio output device is listed as "Selecting Automatically" choose your sound card's audio driver specifically. If that doesn't work, try choosing a different audio output device if available. Press [Apply], then [OK] before trying each selection. You can also try toggling DirectSound to "On" or "Off", as this may improve compatibility with your system.
Remove old and duplicate MIDI entries from the registry
Proceed with this if the suggestions above didn't solve the problem.
There is a limit to the number of MIDI devices that you can have installed. When you install MIDI devices, windows creates a registry entry, starting with "midi" and up to "midi9". Additional MIDI devices are not recognized by Windows. This can be a problem, since new entries may be created when you reinstall MIDI devices or move a hardware device from one port to another. As well, some MIDI device uninstallers do not remove their registry entries. Even if you have not exceeded the limit, the VSC seems to have trouble if there are duplicate or old MIDI entries in the registry.
First, you should make sure that you have uninstalled any old MIDI devices that you are not using - for example, an old USB interface that you used at some point in the past but are no longer using. If this doesn't help, any old or duplicate entries for midi to midi9 can be removed from the registry. If you aren't comfortable editing the registry, you should get a computer tech to do it for you, since making mistakes can prevent your computer from operating correctly.
Go to Start | Run, type "regedit" (without the quotes), and press OK. In the Registry Editor, navigate to the following location:
HKEY_LOCAL_MACHINE\ SOFTWARE\ Microsoft\ WindowsNT\ CurrentVersion\ Drivers32.
When you click on the Drivers32 folder you should see the midi, midi1, midi2... entries on the right side of the window. Look for and delete any duplicates. If you recognize one that may refer to an old MIDI device that is no longer installed on your system, you can remove that entry as well. If you are unsure, you should probably leave it alone.
Use the VSC-DXi version, rather than the stand-alone VSC
If you are still having trouble with the VSC, we might suggest that you use the VSC-DXi instead. Band-in-a-Box 2004 and higher support DXi plugins, and the VSC-DXi would have been included with your Band-in-a-Box purchase. The DXi version has the same set of sounds as the stand-alone version, but is used a little differently with Band-in-a-Box. To use the VSC-DXi, you need to first install it on your computer. To choose the VSC-DXi as your MIDI output device in Band-in-a-Box, go to Opt. | MIDI Driver Setup and place a checkmark in the "Use DXi Synth" checkbox. When the DirectX window opens up, choose the VSC-DXi as your plugin. Close the DirectX window, and you should be back in the MIDI Driver Setup dialog. By default, Band-in-a-Box will set the Driver Latency to around 2000 milliseconds. This is a high setting, but is safe even on older computers. With most computers, you should be able to choose a Driver Latency of around 200 ms or lower. You can experiment with the Driver Latency until you hear audio glitches. A lower latency will give you a quicker response time.
If you were used to using the "Direct Render to wave" feature of the VSC, you will find that the "DXi Direct Render" feature in Band-in-a-Box will give you the same results. It is also a quicker and easier method of rendering your songs to wave.
i dont have any problem with VSC ! I dont use VSC. I have problem with ANY VSTi : Hypersonic, Hypercanvas, Sampletank...
either DXi or VSTi version dont produce any sound.
the only way it works is link with midiyoke. But I dont like to use midiyoke. midiyoke is the last chance... and is not stable.
Even though that FAQ refers to the VSC, a lot of what is said there may apply to *any* DXi synth. And since BIAB invokes VSTi as a sort of "wrapper" to DXi, it may also apply to the VST as well.
Going to need more details from you then.
Operating System in use.
Step by step on how you are attempting to invoke the VSTi inside BIAB without using Yoke.
Location of your VSTi .dll files is critical: Have you told BIAB where they are at?
--Mac
hi,
my system is windows XP professional edition.
proc is athlon XP
my VSTi are in the folder : c:/program files/vst plugins/
as i told you it doesn t work with DXi neither
Have you set the AUDIO drivers to the Echo India?
Hi. I don't really understand what your are trying to accomplish here. Is the VSTi a plugin? Is it a full synth or one instruments? I need that sort of info to be able to help you.
BIAB is, for the most part, a single synth program that can incorporate up to 4 plugins at a time. But you need instruments too. So in order for your BIAB to play it needs a full instrument synth, such as, Coyote Forte, VSC. These synths have all the instruments needed for a project and to be able to hear instruments.
Now, as to your other problem, you have probably got the synth you want to use for midi selected in the Windows System sounds. You need to go in there and de-select, say, the sound canvas as the default midi player. Also you need to see if you've selected the "Play only these instruments" box checked. If so then uncheck it. Once you remove the culprit you shouldn't get that error message anymore.
Hope that helped.
"I don't really understand what your are trying to accomplish here"
very simple thing. i want to use steinberg hypersonic2 as the main VSTi or DXi synth in BIAB.
Hypersonic is a multitimbral VST ( 16 channel ) , like hypercanvas, but better quality.
Hypersonic2 is delivered in VSTi and DXi setup. I have both on my PC.
It is also delivered as standalone application. that is the one I use with BIAB, with the midiyoke link. But i dont like this issue. I want to use HS as DXi or VSTi inside BIAB, as it should be.
What brand/model is your laptop? I use Hypersonic 2 in a regular basis in BiaB since version 2006, it work flawless and sound really cool, however I know some not so new HP laptop with Athlon processors tend to behave wierdly with BiaB,VSTi and some audio cards, in my case I got problems with a Pavillion model from year 2006 and my M-Audio Black Box USB, it was near to impossible get it working, Hypersonic 2 and any VST1 just turn muted after few bars. At start I think the cause of this was my Steinberg USB protection key being rejected but I did change the usb port and all was fine, but audio still muted. With my new Pavilion 2000 all is working perfect under Windows XP SP3 and all my audio interfaces. Maybe this can be so basic, but remember set your Hypersonic 2 in GM mode and Program Change ON at SETUP menu window, because sometimes Hypersonic 2 run by default without instruments loaded except in ch.1 (not used in BiaB by default) . Good luck
Carlos
---------------------------------------------------------------------------------------------------------------
http://www.carlosarellano.com/musichttp://www.overloud.com/media/common/carlos/OverloudTango.mp3https://www.youtube.com/watch?v=FLHoFoRudOM&fmt=18
Quote:
hi,
my system is windows XP professional edition.
proc is athlon XP
my VSTi are in the folder : c:/program files/vst plugins/
as i told you it doesn t work with DXi neither
**If you haven't already, please try Opts. -> Return to Factory Settings and hit the second button down inside BIAB. This will reset the soundcard and MIDI detection of the program.
*Have you updated XP to Service Pack 3?
At the least, you should be running SP2.
*What specific brand and model computer is that Athlon? (proc speed, type, etc.)
*Laptop or desktop?
*Can you run Hyper2 using any other host programs using it as DXi or VSTi?
*Can you run any other DXi or VSTi that you may have in BIAB?
*Which version of BIAB is it?
You've gotten some good response and at least one user with experience on the exact problem, that's a good sign that there is light at the end of this tunnel...
--Mac
--Mac
my laptop is an MSI S270. It is 4years old aprox. the proc is,I think, athlon MT37 (XP3000+).
The problem is not only with hypersonic2 but with all VSTi (hypercanvas, sampletank, sfz ...).
My soundcard is the fabulous Echo INDIGO PCMCIA. I say fabulous because it is a wondefull affordable card. very low latency and fantastic dynamic sound. if you have the occasion try it.
I will try with my other card, to check if the problem is from the echo.
other card is : line6 toneport ux1. good for guitar and mic input but not as good as the indigo for project monitoring.
thanx for the support
Did you setup the audio driver selection in BIAB for the Echo card as I mentioned a week ago?
yes of course. ASIO echo indigo.
oh no ! mme drivers are too slow
ASIO has been problematic in BIAB. The only thing that seems to work consistently is the ASIO wrapper "ASIO fo All". Try mme just to see. Why do you think you need ASIO? Are you playing the VSTi in real time with a keyboard? That would be the only reason & it's still to slow for that.
ASIO drivers have been problematic in BIAB *for some users*.
For example, I enjoy using ASIO all the time. Card here is either the Delta AP2496 on the desktop or the E-MU1616M on laptop or desktop. Took a bit of OS tweaking for both.
There may be *driver* compatibility issues going on with certain soundcards. Frustrating, hard to tell from this side of the screen, too.
If your card doesn't want to work right with its own ASIO drivers and BIAB, I think it is worth downloading and trying those ASIO4ALL drivers, which "wrap" to your soundcard's WDM drivers but will provide the lower latency for playing softsynths in realtime.
--Mac
True Mac. I also use ASIO 6 outputs worth set on BEST with the Audigy 2 ZS notebook.