| Author |
Topic: BIAB Msg: Roland VSC in use by another Program |
Bob Kagy
From:
Lafayette, CO USA
|
Posted 24 Aug 2005 2:39 pm |
|
I've been getting this message for the last couple of months and have had no luck in tracking down the "another program" culprit.
So I've switched to my Creative SoundBlaster sound card to play the BIAB tracks; of course it works, but doesn't sound as good, so it would be nice to have the unchallenged use of VSC back for BIAB.
It doesn't seem to be Windows Media Player - I've upgraded to V10 and the audio devices being used don't include VSC. Same problem existed on V9 WMP.
I have Windows XP SP2 with all the latest updates, no other problems.
Anybody had this? Know how to find the culprit?
Thanks,
BK
|
|
|
 |
Ron Victoria
From:
New Jersey, USA
|
Posted 24 Aug 2005 3:00 pm
|
|
I get that also sometimes and have to reboot. I will be interested what answers you get.
Ron |
|
|
|
Bob Kagy
From:
Lafayette, CO USA
|
Posted 24 Aug 2005 5:47 pm
|
|
Interesting Ron. Rebooting doesn't change anything for me, I thought at first it would do the trick.
I've also been to the PG Music website looking for someone with a similar situation. The search isn't over, but the FAQ section didn't help.
BK |
|
|
|
Ron Victoria
From:
New Jersey, USA
|
Posted 24 Aug 2005 5:55 pm
|
|
Bob, Why not do a post. I've used them a few times, BIAB wizards. Also, email George Wixon from the forum. He's an ace with this stuff.
Ron[This message was edited by Ron Victoria on 25 August 2005 at 07:25 AM.] |
|
|
|
Jim Baron
From:
Madera, Ca.
|
Posted 25 Aug 2005 6:58 am
|
|
Give this a read and see if it dosen't help some. "http://www.pgmusic.com/techfaq10.htm"
On mine I usually just click ok and go on without problem. Also, helps to have the latest upgrade, think that is build 163 now.
Jim |
|
|
|
Bob Kagy
From:
Lafayette, CO USA
|
Posted 25 Aug 2005 9:35 am
|
|
Ron, Jim,
Using you guys suggestions, I just found the answer, applied it and the problem is now solved.
If you're getting this error, as Jim suggested, go to
www.pgmusic.com/techfaq10.htm
Then go to FAQ #95; the question states the exact problem I had.
The answer consisted of some steps to follow. Step 1, I had already done. Step 2, the one about making sure the two vsc programs were being started at Windows startup was the fix that made it work for me.
So for right now, it worked, sounds good, and I'm happy to have this go away.
Jim, I'm still back on BIAB v12; I didn't upgrade in the last couple of years, and there were no upgrade downloads for v12 that I didn't already have.
I had a major software blivit in the May, June timeframe that Microsoft helped me out of - probably the VSC startup options got modified during the long troubleshooting/recovery process.
Hope my experience helped Ron, and maybe it'll even clarify what might be happening with yours Jim.
Many thanks to both of you for your suggestions - I would've fished around for at least another month if it hadn't of been for you.
BK |
|
|
|
Ron Victoria
From:
New Jersey, USA
|
Posted 25 Aug 2005 9:58 am
|
|
I went thru the list from ques #95 and found everything in order. The next thing is to uninstall and install VSC. It doesn't happen too often, so I just reboot.
Ron |
|
|
|
