Frequently Asked Questions
This page includes three FAQ's: and
one covering MIDI problems, one for DX Manager and one for SY Manager .
The most common issues I get mail about concern MIDI related problems -
how to get DXM or SYM to work with your particular setup.
It's extremely frustrating to have found the software you want and you just can't get it to talk to your synth.
I've put together a couple of checklists to guide
you through troubleshooting your MIDI setup for DX Manager and SY Manager. Much of this
information is also available in the on-line help systems for my programs.
Most downloading and installation problems with DXM2 occur because of a misunderstanding about how the ClickOnce installer works.
ClickOnce does away completely with the need to unpack zip files and run setup programs.
As the name suggests all you have to do to install and run DXM2 on your computer is click on the Download DXM Now button on the download page.
This brings up the license agreement and after clicking on the I Agree button download, installation and first time run will normally be entirely automatic.
If you do not have the .net framework version 2 or later installed this is detected and you will be asked whether it should be installed as part of your download.
DXM2 requires the .net framework so it must be installed if not aleady present for DXM2 to run.
The ClickOnce installer puts the DXM2 program files in a pre-determined location in your user account on your harddrive.
You cannot choose an alternative location and if you move the program files from this location, or use a download manager to put the files somewhere else,
DXM2 will not work properly. The installer must be able to locate the program files in order to provide automatic updates.
Whilst the program files are installed to a fixed location, you can of course store your patches and other data used by DXM2 anywhere you like.
Initally the PD patch library and various other data files are placed in a folder with the following path: Drive:/Documents and Settings/All Users/FM-Alive/DX Manager/Data.
If you do encounter problems during the download or installation process ClickOnce will ask whether you want to view the installation log file.
This should help pinpoint why the install failed: the usual reasons are either a download manager interfered with the download process or the DXM2 program files
have been manually moved from the installation folder. Either way the log will typically contain an error message with the following information:
--- Inner Exception ---
System.Net.WebException
- Could not find a part of the path 'Drive:\Some Folder\DXManager_2_0_0_0\DXManager.exe.manifest'.
To rectify the problem first delete the DXM2 files from the failed download location, disable the download manager if one is in use, and then simply re-download the application.
IMPORTANT NOTE: The current version of ClickOnce will only work properly in Internet Explorer.
In particular if you try to download DXM2 using Firefox the following error message will appear:
"Cannot Start Application. Cannot download the application. The application is missing required files. Contact application vendor for assistance."
Microsoft are working on cross browser support for ClickOnce - if you're interested read more here.
A patch for Firefox that will enable it to run ClickOnce properly is available here.
Download DXM2 from here. When the installation is finished DXM will run automatically. You can then purchase either by clicking
on Register Now in the Help menu, or simply close/reload DXM2
to see a purchase option dialog - in either case click on Buy Now in the dialog. You will be transferred to Paypal where you can complete the purchase using either your Paypal account or a credit card.
On completion of the purchase DXM2 will be automatically registered and activated.
Sorry, no. The MIDI spec. for these synths is substantially different to the 6-operator synths like the DX7.
I hope to add support for these synths in a future edition of DXM.
The MKI DX7 came with two ROM cartridges which contain 4 banks of 32 patches:
Master,Keyboard & Plucked group, Orchestral and Percussive Group and Synth Complex and Effects Group,
of which the first contains the patches originally in the DX7's internal memory. You can
download a zip
file that contains these four banks as .dat files - use DXM to upload them to your synth.
The MKII DX7 has two internal banks of 32 patches. Download
a zip file that contains these two banks in .dat format - use DXM to upload them to your synth.
Yes - DXM2 supports this format.
You can download the DX7 manuals in .pdf format from
Yamaha. - just enter DX7 in the search dialog.
You can download the DX7II MIDI specification here.
Sorry DXM does not support the extra features of E! , but it is compatible - you can upload/download and edit patches
in the usual way. I plan to add support for the E! Card in DXM3.
Yes, but they are not supported. Regarding the PLG 150DX plug-in, I understand that the DX simulator
supplied with the board uses a proprietary sysex format that is not compatible with the traditional DX formats.
However I have had reports that DX Manager can be used to upload traditional format patches to the PLG 150DX.
Please note that the following section only applies to DXM version 1.0 and 1.1. The current release, DXM version 2, is installed directly
from my website.
I can't complete setup because I keep on getting messages about my system files being
out of date - what's wrong ?
I get an error message when DX Manager starts-up.
This error message sometimes occurs
during installation. It occurs because DX Manager requires later versions of some
system files than are installed on your system and a dialog box appears asking whether
you wish these files to be updated. If you choose yes the updated files will be
installed, your system reboots and installation can then complete.
Occasionally, rebooting does not complete
the installation of the newer system files and you may get multiple "System files
are out of date" messages. This
MSKB article explains
the circumstances under which this condition can occur and the steps to take to
resolve the problem. Typically the problem arises when you try to install DX Manager
on a different drive to your system drive.
If you know which files are causing
the problem you can update them manually although from Win2000 on this cannot be
done from within Windows as the operating system files are protected. One alternative
in these circumstances is to boot up your system to DOS and use the Copy command
to transfer the updated files to your system directory (thanks to Detlef Kruse for
this tip).
Here's some suggestions for the brave
: try them entirely at your own risk. If you don't feel comfortable working in
DOS then don't experiment as you could easily end up trashing your hard disk
IMPORTANT NOTE: It is most likely
that Oleaut32.dll is the file that is causing the problem. However there are several
system files that must be installed before DX Manager setup can run. Here's the
complete list which is contained in the file Setup.lst in the DX Manager zip file.
As well as the name I've listed
each file's creation date/time, size in bytes, and version. It is this information
which is used during Setup to determine if your existing system files are out of
date:
VB6STKIT.DLL,7/15/00 12:00:00 AM,101888,6.0.84.50
COMCAT.DLL,7/22/02 7:05:04 PM,3856,5.0.2195.1
STDOLE2.TLB,7/22/02 7:05:04 PM,16896,2.40.4518.0
ASYCFILT.DLL,7/22/02 7:05:04 PM,143632,2.40.4518.0
OLEPRO32.DLL,,7/22/02 7:05:04 PM,164112,5.0.4518.0
OLEAUT32.DLL,7/22/02 7:05:04 PM,626960,2.40.4518.0
MSVBVM60.DLL,3/12/02 3:26:44 PM,1388544,6.0.92.37
Compare the properties of your existing
system files carefully with the above before continuing and substitute one or more
of the above for oleaut32.dll in the following steps if they are newer than your
current versions. Make a boot disc or a copy of the one you created when you
installed Windows - you did make one didn't you? If not you'll find instructions
on how to create one in your Windows Help system or
get one here. Unzip the DX Manager zip file to an empty directory. Click
on the .cab files (DXMan1.cab etc.) to locate the file(s) you want to put in your
system directory. Right click on your selection and choose the Copy command
on the menu that appears. Copy OLEAUT32.DLL (or whichever files need to be replaced)
to the boot disc. When you've copied the file(s) you need to update, leave
the boot disc in your machine and reboot. Your machine will boot to DOS. At the A: prompt type Copy c:\windows\system\oleaut32.dll
a:oleaut32.bak -
this makes a backup copy of your system file. If your Windows directory
is on a different drive then substitute the appropriate drive letter Now type Copy oleaut32.dll c:\windows\system\oleaut32.dll
- This puts the updated file in your system directory ( again, substituting for
c: if your Windows directory is on another drive). Repeat steps vi and vii for any other files you need to replace. -
Remove the boot disc and restart your machine.
Run the DX Manager setup program.
These error messages sometimes occur
under Win95/Win98 after a successful installation of DX Manager 1.0, immediately
the program is run.
The error indicates that the version of Microsoft Data Access
Components installed on your machine is not compatible with DX Manager.
The problem can be resolved by
downloading
and installing a compatible version of MDAC (2.7 or later).
(Yamaha's advice on non-functioning floppy drives is
here - search for SY77)
Well first, here's the good news. Its
99% certain your disk drive is NOT broken - more likely its' drive belt has worn
or broken. You can easily replace this by unscrewing the bottom plate on your SY
- lots of screws but it's not difficult. There are three screws holding the drive
in place - remove these and the ribbon cable connector from its' socket on the main
chassis. Now you can lift the drive out of the machine - turn it over and remove
the four small screws holding the drive guard plate in place. Then remove the single
screw holding the plastic drive belt guide in place -voila ! You can now replace
the drive belt by threading it round the motor spindle.
Replacement belts are available from
audio stores - the belt dimensions are 9.6" X .025" x .124" but I have found
a rubber band will do the trick just as well - thanks to Nick Martello for the tip.
In the UK you can get the belt from Chris at
Cadishead Motorcycles- Chris' site is well worth a visit just to see the photies of the pipe organ he's building !
The bad news is that if it's not the
belt and your drive has been drinking it's way to terminal alcoholism then there
is no straightforward way to transfer SY format files (*.t01 etc) to SY Manager.
The reason for this is that, just like the drive itself, the file formats are Yamaha
proprietary which they have declined to put in the public domain. Nontheless I will include the ability
to read .t01 files in the next version of SY Manager.
If you are handy with a soldering iron
then it is possible to replace the SY's drive with a standard PC drive, but you
will need to make a custom connecting cable. You can download a zip file
with the pinout details , and thanks to Mike Foo for the information. If you want a direct replacement
try Route66Studios.
When you select a file to open as a
voice data file in SY Manager, it checks to see that the file really contains valid
voice data. If it doesn't or there is anything else in the file you get the above
error.
Most commonly the error occurs when
downloading patches to the PatchView window in SY Manager using the Get All button.
This does as it says - it downloads everything your SY has to offer which
includes multis, samples (SY99) and waveforms (SY99) in addition to voice data.
So when you save the download and then attempt to re-open the file you get the above
error.
To avoid getting the corrupt file error
message whilst downloading in PatchView:
-
Select the voice patches you want to download - click on the first voice,
press and hold the shift key and then clickon the last voice.
-
Press the Get button
-
Confirm the download buffer only contains
voice patches
-
Press Save Buffer and choose a file
name for the patches
-
Open the file for editing etc.
This is not possible at present due to incompatible file formats - see above
If all your DX7 files are of the same type (for example .SYX files which are usually 4104 bytes long
and contain 32 packed patches with an 8 bytes sysex wrapper) then you can put some or all of them
into a single file and then convert them using SY Manager.
To make a single file out of several files do the following:
-
Make backup copies of the source files - DO IT or REGRET IT !!
-
Copy the files you want to join together (it's called concatenating) to a separate directory.
NB Make sure you have made backups first !!
-
In the directory you have copied your source files to, from the DOS prompt,
type the following :
copy *.syx /B newdx7.dat /B
This should put all of the syx files
into a single file called newdx7.dat. Obviously, if you are converting some other
file format (.DX7,.32 etc) then substitute the appropriate extension in the above
command line.
For more info on using the DOS copy command
just type copy /? at the DOS prompt for help.
I have only tested SY Manager on the SY77 and SY99 but, as far as I know, it will work on the SY85,TG77 and SY55/TG55
which have basically the same MIDI spec. However the SY22 is a cut down version
of the SY77 and is not compatible with SY Manager.
Although SY Manager is compatible with
the rackmount version of the SY77, the TG77, it seems their hardware MIDI implementations
differ. A number of users have reported problems downloading patch banks in PatchView
from the TG - SY Manager times' out after receiving the first couple of patches. This problem
will be resolved in the next release of SY Manager.
SY Manager 2.2.2 uses a simple polling technique
to scan for incoming MIDI messages. Although normally very reliable, it is possible
to overrun its' internal buffers at high transfer rates and it seems this is what
happens with the TG77.
At present the only solution I know of is to download patches
individually. This is not as bad as it sounds however as you can select all 64 internal
patches in PatchView and then drag the selection to the patch buffer.
SY Manager runs under any Windows operating
system from Win95 Service Release 2 onwards.
Sorry, No !
You can upload samples to your SY using
the MIDI/Send File... menu option. The sample must be in Sample Dump Standard (SDS)
format which is the only format recognised by the SY. There are a vast number of sample format
converters available, but if, for example, you just want to convert a WAV file to
SDS format then I'd recommend Wave-to by Richard Goodwin.
Assuming your drive is working - the
red indicator lights up and there is the usual grinding noise as the drive tries
to read your disk before you get the message "Bad Disk" - the most likely reason
for this error is that you are using a 1.44MB HD floppy disk. The SY will only read
DS-DD floppies formatted to 720K. It shouldn't matter whether the floppy is formatted
on your PC or the SY but if you are still getting the "Bad Disk" or "Illegal
File" message then try formatting the disk on your SY first (Utilities/Disk/Format).
Note that Windows XP doesn't offer a 720K format option, so you have to
do the format in DOS
If this doesn't work then your drive belt may be worn - see above
For the SY77
here
For the SY99
here
No, the floppy drive in the SY series
uses a proprietary format that is different from the MIDI sysex file format used
by SY Manager. Unfortunately there is now no-one at Yamaha who can provide this
information. However I intend to include this option in the next version of SY Manager.
|