yeah, I had that issue as well, the bye bye midi yokes issue. So for me,
persoanlly, just sticking to sfz and perhaps hoping bassVST can exist one
day. with bank selection options. traditional creative or sfz style.
----- Original Message -----
From: "alexander" <[email protected]>
To: "QWS list" <[email protected]>
Sent: Thursday, September 22, 2011 4:28 AM
Subject: Re: QWS List qws + bass midi driver = no sysex?
well mate, base midi was fun to play with but it deleeted all my midi
yokes. So what did I have to do? repair midi yoke. Then it conflicted
with the base driver for winamp, and wouldn't allow it to do anything. So
similar yet different bahavior
Alexander Nelson
Online contacts:
skype cordova5029
Aim Cordova5029
msn, [email protected]
Cell phone: 218-343-9616
----- Original Message -----
From: "Arthur Pirika" <[email protected]>
To: "QWS list" <[email protected]>
Sent: Wednesday, September 21, 2011 1:26 PM
Subject: QWS List qws + bass midi driver = no sysex?
HI there, it's been a while since I poked my nose in here. I've come up
with an interesting find, however. Recently I tried the new bass midi
soundfont driver, which is fine in itself, and is a good way to get
soundfont support on any system, almost as good as your original creative
card. However, I noticed after a few days that any sysex based reset
command wasn't going through to software synths, no matter if it was via
a midi yoke or a standard windows driver. AFter having tried almost
everything, even going so far as to delete and recreate my config, and
nothing, I uninstalled the bass driver. and now? no problem! Sysex are
back in fully working order. I'm almost certain it was the bass driver
itself causing the issue, however, two things make me not so sure.
1. Another free sequencer I tried sent sysex in midi files just fine,
where as qws wasn't after the first play of such a file.
2. Perhaps related to this, a restart was needed after the bass driver
uninstallation. Perhaps the restart was enough to make sysex work again?
However, thinking on it, I'm not sure, since I'm almost certain I've had
to reboot while the driver was installed, and still no sysex.
So, can anyone confirm this behaviour?
Arthur
To unsubscribe or change list options, see http://lists.andrelouis.com
for archived list posts, see
http://www.mail-archive.com/[email protected]
To unsubscribe or change list options, see http://lists.andrelouis.com
for archived list posts, see
http://www.mail-archive.com/[email protected]
To unsubscribe or change list options, see http://lists.andrelouis.com
for archived list posts, see http://www.mail-archive.com/[email protected]
