FAQ - Frequently Asked Questions



No. I developed this driver purely for my own satisfaction. Maybe in the future I will take on another of such project but as of yet I have no plans in that direction.



No. I have no connection whatsoever with Opcode. If you have a malfunctioning Midi Translator don't come to me. I have no expertise in those matters, sorry.



I'm afraid not. They probably don't make them anymore. Maybe you can find them secondhand somewhere if you look around.



The driver doesn't support chained devices at this moment. I only have one Midi Translator so I could not test this feature. Maybe in the future I will add this if I can find another Midi Translator.



You are using the demo version of the driver. You can get a full working version here or got to www.shareit.com and order productid 194226.



Cubase SX uses DirectMusic to access MIDI devices. DirectMusic is part of the DirectX libraries that were developed by Microsoft to enable applications to access hardware in a more direct way. As of this moment the Midi Translator driver is not a DirectMusic driver. That's why it shows up as emulated. Don't worry about this. I get excellent MIDI response using the driver in emulated mode. If there is a performance benefit to be had from using a DirectMusic driver it's probably not that big. Nevertheless I'm planning to develop a DirectMusic version of the driver in the near future.

Just for the record, Cubase SX is the only application that I know of that makes use of DirectMusic to access MIDI devices at this moment. But there may be more in the future.



First make sure that you followed the installation instructions carefully. You could try to uninstall the driver and go through the setup process again.

Next check that you have a working parallel port on your system. The parallel port may be disabled in the BIOS setup. Check the manual of your motherboard if you're not sure about this. You can check if there is a parallel port on your system by going to the device manager. The section Ports (COM&LPT) should list at least one printer port. Also the port should be configured as standard (uni-directional) port. Usually this is configured through the BIOS setup as well. Again check the manual that came with your motherboard.

A good test to check whether your system is setup allright is to see if the Midi Translator works on Windows 98 with the original Opcode driver. If it works with that it should work with my driver as well.

There is a possibility that your printer port is incompatible with the Midi Translator. I experienced this with one system on which I tested the driver. Again a definite test is to try it on Windows 98. That's how I found out that the parallel port on that motherboard simply refused to work with the Midi Translator.

If you find that the parallel port is faulty you can buy a parallel port extension card for little money.
If the parallel port is OK and you've carefully followed the installation instructions and still no luck then you can send me an email asking for support. Please describe the problems you're experiencing as precisely as you can. If you get error messages please copy them to your support request. Also add your system setup, describing motherboard, processor, operating system and anything else that may be helpful. The more information you give me the easier it will be for me to investigate the problem.



The zip files that are created by my mailing engine seem to be incompatible with some applications that claim to handle zip files. Apparently a problem exists with the files in sub-folders. The zip utiltity that is part of Windows XP is one of the applications that are unable to handle these files.
The solution is to use a different application to unzip the files. All versions of WinZip can extract the files without any problems. A trial version of WinZip 8.1 can be downloaded from www.winzip.com.


It is unknown to me whether the error lies in my zip packages or that the extracting utilities are at fault. Future distributions of the driver will no longer suffer from this problem.



This is a bug in the old version of the demo driver. There is a new version (1.1.0.244) you can download that will fix this issue.
The problem occurs when you are running the driver on Windows XP. If you open an input while the driver is active, the system will freeze if the input receives MIDI data after the time-limit has elapsed. You have to reset the computer to bring it back to life.
The problem occurs only with the demo driver (versions lower than 1.1.0.244) and only if you run it on Windows XP.



In the past I have been (over)optimistic about this. My view of the current situation is that the need for a 64 bit driver is not that great. Most people are still on 32 bit and I don't see that changing rapidly the coming years. So in view of a lack of resources both financially as well as time-wise, I decided to postpone my plans. That is no to say there will never be a 64 bit version. It is just going to take a little longer.



If you are running software protected by a Syncrosoft protection key you might run into this problem. Such a device, commonly referred to as 'dongle', comes with Cubase for instance. Nowadays they come in the form of a USB stick, in the older days they used to be connected to the parallel port. I myself had some trouble with apparently an old version of the protection device driver. It seemed it still did some things to the parallel port, even though I have a USB dongle. It was quickly solved by disabling the Nsynas32 service. It is probably always best to install the latest drivers of these devices.