You
didn't say if you got your patches in Soundlib only or if you have sysex files
available. You can always use a midi dump program like MIDIOX to send sysex
files to your VFX or receive sysex dumps.
I've
tried jsynthlib a while ago and the vfy implementation was a bit raw. Someone
experienced in JAVA programming could probably improve this and jsynthlib
definitely has even the capacity to build a VFX patch
editor.
For
myself I decided not to go with jsynthlib out of two main
reasons:
1. I
don't like JAVA because I find JAVA based programs too big and too slow (there
are also some other concerns I don't want to bother you
with)
2. I wanted to have floppy disk operation included and that's
something I havn't found a way in JAVA so I decided to go with
C++.
Unfortuantely this will still take some time because my priorities are on
another project - not related to VFX.
You're
saying "after a failed install of Windows XP SP2", so why don't you reinstall
Windows instead of reinstalling Soundlib? Always use the install routine from
the soundlib zip file instead of just copying the soundlib folder into the
programs folder.
You
could also try to get rid of all soundlib related entries in the registry before
reinstalling soundlib (use regedit, search for soundlib and be
careful!).
Ahh,
and don't install into a path containing blanks or unusual characters, e.g.
simply use C.\SOUNDLIB\, and stay with the simple filenames from the before w9x
times...
I've
tested Soundlib on XP SP2 and it works fine. Only the 'TEST' option to transfer
a single program crashes after transfer - but this had always been a
problem?
Another problem, which doesn't crash Soundlib but could mess up transfers
is transfer speed. Unfortunately Soundlib has no means to adjust speed, and
devices like the VFX could not keep track in receiving sysex messages from a
fast PC - this seems to be resolved in XP SP2 - at least it works for me. If
such problems occur (or maybe the 'TEST' issue could be solved as well) you
could try to use the MIDI Yoke NT driver to route your MIDI signal
through MIDIOX where you can adjust the transfer rate.
And remember, everytime a MIDI application
crashes you must logout and login again. I tell you why: when the application
crashes the MIDI ports cannot be closed and, due to a bug in
Windows, unclosed MIDI ports can cause Windows to crash. And Soundlib
cannot be restarted because the unclosed ports cannot be reopend
properly...)
What
would be Windows without bugs?
;
Let me
know if any of this was helpful.
Regards,
Hans
Show quoted textHide quoted text
Guys/Gals,
I've been experiencing some problems with my SOUNDLIB
program (namely,
that since a failed install of Windows XP SP2 it has
caused access
faults and won't open, no matter how many attempts to
re-install
it...grr...), and in a search for another option to
transfer patches
from the comp to the keys, I came across jsynthlib, a
JAVA-based
librarian/editor. It appears to be fully functional with the VFX
(in
library capacity only...have to blow the money on MidiQuest to get
a
pc-based patch editor, I guess!), and has already
successfully
accepted a sysex dump from the vanilla VFX, but it's still
not
auditioning/playing patches on-demand.
My question is, I
guess, have any of you used this program with your
VFX (mine's vanilla, but
I don't think that matters) with positive
results?
Failing that, does
anyone have any advice about the soundlib problems?
VFXLib causes the same
problem, so that's a no-go.
If it helps...
Vanilla VFX -->
M-Audio Uno USB MIDI port --> DELL Dimension w/ 256 MB RAM
Lemme
know what you think, I'm at a loss, and I'd really like to get
my old
patches back on the system.
Best,
justin
