Translator PC : OMS : Translator II : Translator Pro : Translator ProSync : Studio 3 : Studio 4 : Studio 5 : Studio 64X : Studio 64TXC : Studio 128X : MIDIport 32 : MIDIport 96: DATport : SONICport : >Studio 64XTC help files >PC Drivers help files >Win 98SE/ME help files > Translator PC The Translator PC more or less took over from the old MusicQuest boxes as a solution for PC laptop users and those who wanted a portable interface. Again it's a parallel port interface, 32 channels , 2 x 2 ports with a power supply, although it can be powered from the computer itself. You can also chain MTPC's together to give you more channels or plug a printer into the back of it. Note that the TPC needs to have your Printer Port set to Uni -directional in the BIOS (why? - don't ask). You can usually access this by hitting Delete or something at boot up - go to Peripherals, Parallel Port Mode and set it to SPP or NPP or Normal. Avoid ECP, EPP etc etc See installation notes below. driver -------------------------------------------------------------------------------- Opcode Macintosh Interfaces OMS 1. When using OMS with Opcode interfaces, if you are getting serial overrun errors, ensure you have OMS>Edit>Preferences>Use 'Serial DMA Drivers When Available' turned OFF. 2. The Digi 001 system does work with Studio Vision Pro and Vision DSP. Make sure you do NOT have the Digi 001 defined in your OMS Studio Setup - this causes SVP/VDSP to refuse to recognise the Digi I/O driver in Acadia. Weird but apparently true... 3. Latest and almost certainly last ever version is 2.3.8 Download it -------------------------------------------------------------------------------- > Translator II Most basic Mac interface. 1 in 3 out, with a thru. 16 channels - powered off serial port. Can use OMS or run at 1 mhz setting in Cubase etc. -------------------------------------------------------------------------------- >Translator Pro Essentially two Translator II's in a box. Needs to use both Printer and Modem ports to access its 32 channels. 2 in, 6 out , powered from Mac. Half Rack. >Translator ProSync As above but with SMPTE support -------------------------------------------------------------------------------- >Studio 3 More professional version of the Translator Prosync in that it 's a 1u 19" rack device. Still 32 channels requiring both serial ports although there are thru switches so you can plug a modem etc in the back. Outs can be configured via OMS. Mains Powered via IEC lead. I've had one of these for years, it's virtually indestructible. Notes... Studio 3 / G3 Powerbook fixes... The reason as to why your Studio 3 works fine on the G3's printer port, but not on the G3's modem port, is a matter of the G3 ports' sensitivity to the Studio 3's 1 megaherts (MHz) clock output. Specifically, a typical Studio 3's 1MHz clock output has a peak of about 2 volts. The G3 also requires that the 1MHz clock has about a 2-volt peak for serial communication to ensue. At this point, you may think all is well because the Studio 3 has satisfied the G3's voltage requirement for the 1MHz clock. However, due to slight variances in component tolerances (as no component manufacturer is perfect or exactly the same as others) inside the Studio 3, the 1MHz clock output of the Studio 3 may be substantially fall below 2 volts. As a result, no serial communication can ensue with the G3. Similarly, component tolerances in the G3 modem and printer ports may cause one port to become either less or more sensitive to the 1MHz clock level. Evidently, your G3's printer port is more sensitive than the modem port--hence, your Studio 3 works fine when connected to the former but not the latter. The powerbook mod will raise the voltage level of the 1MHz clock output of the Studio 3 above 2 volts, thereby eliminating the adverse effects caused by varying component tolerances. After the mod is performed, I'm confident your Studio 3 will work on the modem port of your G3. In other words, the modem and printer ports of your G3 will no longer behave differently. from Opcode tech support discussion forum 21/8/98 (posted by Renan Sanchez, Opcode tech supp). Powerbook Mod It's not an upgrade to the software that's needed. The problem is with a couple of resistors inside the Studio 3. This should help... Any model of a MAC PowerBook will properly recognize a Studio 3 by simply adding two, 220-ohm pullup resistors at U12 (26LS31 differential line driver chip). U12 is located between the two MIDI/THRU switches. The most convenient way to implement the PowerBook modification on the board is as follows: 1) Ensure that the Studio 3 is unplugged from the AC wall outlet to avoid the possibility of getting a severe electrical shock. 2) Remove the top half of the chassis to expose the board inside the unit by unscrewing a total of 8 screws, which are located as follows: 2 in the front panel, 2 in the rear panel, 2 on the left side of the chassis, and 2 on the right side of the chassis. 3) Solder the first 220-ohm pullup resistor between U12-2 and U12-4. Again, U12 is a 26LS31 driver chip located between the two MIDI/THRU switches. DO NOT confuse the 26LS31 driver chip from the 26LS32 receiver chip. The latter is located just above the former. 4) Solder the second 220-ohm pullup resistor between U12-10 and U12-16. 5) Reinstall the top cover. -------------------------------------------------------------------------------- >Studio 4 Very popular 8 x 8, 128 channel interface w/ SMPTE. Studio 4 can operate at 1 Mhz or Fast mode. You can also network them together for extra channels or hook up a Studio 3 or other standard MIDI interface. Supports OMS patches Works at 1 MTP with Cubase etc, A common problem with the Studio 4 are that it ceases to be recognised by the computer - I've found this is often down to the PSU. I think it shipped with 2 types, the earlier ones being suceptible to not working after a while. Even if the power LED is on, if the unit doesn't get enough power it will fail to be seen . Solution - get a new PSU. They shipped with 9VDC 2A centre positive supplies. -------------------------------------------------------------------------------- >Studio 5 LX Huge MIDI interface - supports 240 channels, SMPTE , OMS Patch Storage Support etc, etc. Good info section at http://www.fm-music.com/v/ so I won't bother going into detail here. Be warned that some people have had a rather trying time attempting to get Cubase and the Studio 5 to talk to each other. Not fun. -------------------------------------------------------------------------------- Opcode Cross Platform Interfaces After the discontinuation of the MusicQuest and Studio 3,4 etc (not 5) came a new range of interfaces that could hook up to a Mac or a PC (or both). They all use 1 x serial Port on a Mac and a COM Port on PC ( changing from the earlier Parallel Port devices). OMS Compatible and shipped with Windows '95, '98 drivers, Patchbay and Diagnostics software. All can be re-initialised if neccessary by holding down the 'Program' button for a few seconds while turning theunit off/on. >Studio 64 X 4 in 6 out ( ports 1 + 2 mirrored) 1u , 19" rackmount box with SMPTE support. Decent reliable 64 channel interface. When using with Logic and no OMS , check "MTP Cable Mode" only. This is the only Opcode box that really worked with Windows NT even though the drivers were still beta. 8 Port SE also had drivers but I don't think they were too successful. driver windows driver NT ( beta) >Studio 128X As above but 8 x 8 ports. Works at 1 MTP slow with Cubase. driver >Studio 64XTC As per the Studio 64 but with additional synchronisation features. 64XTC was the only Opcode box to feature wordclock, superclock (for synchronising to Digidesign systems), Blackburst and ADAT sync. Had an expansion slot for Sony 9 pin but this never evenuated. driver Using the 64XTC with Sequencers + ADATS cubase (mac) 1. Configure Cubase to use OMS 2. Choose Options>Synchronisation 3. Do the following... Timecode Base = MMC From Input = any MMC Output = ADAT (port 5 in OMS) Frame rate = 25 fps Tempo Base = internal Sync Out, MID Timecode,MIDi Clock = off Offset, Song Start = 00:05:00:00:00 4. Close Synchronisation dialogue box 5. Highlight Sync button on Transport bar 6. Press button on Transport bar to initialise time code in Cubase 7. Press . XTC will generate timecode, ADAT shold rewind/forward to correct location and start playing. Once ADAT plays Cubase will receive sync and start playing (hopefully) logic (3.0 - but more or less the same for more 4.x) 1.Options> MIDI Options 2. Transmit MIDI Clock = off 3. Transmit MTC = off 4. Auto Sync in = on 5. MMC = on 6. Options > Serial Port Communications. Use OMS drivers. 7. ADAT Online The "ADAT Online" option lets you specify whether the Studio 64 XTC communicates with a connected ADAT. Normally, if an ADAT is connected to the Studio 64 XTC, it is detected and any MMC commands sent to the Studio 64 XTC are sent to the ADAT as well. Taking the ADAT offline causes the Studio 64 XTC to act like there is no ADAT connected, so it will not, for example, shuttle about constantly if you are simply editing MIDI data in your sequence. To take the ADAT offline using the front panel controls of the Studio 64 XTC: 1. Turn on the Studio 64 XTC and ADAT. 2. Using the PROGRAM button, call up the Sample Rate sync function. The LED for the selected sample rate is lit, along with the ADAT LED (indicating it's detected and online). 3. Press the SYNC button repeatedly until the ADAT LED is selected (it should blink rapidly). After a few seconds, the sample rate LED will again become lit, and the ADAT LED will then blink slowly (indicating it's offline). 4. Repeat the previous step to place the ADAT back online. ADAT ROM Versions The Studio 64 XTC has been successfully tested with the following versions of ADAT firmware: ADAT - version 4.03 ADAT XT - version 1.06 If you are experiencing problems with your ADAT not responding correctly to MMC commands and your ADAT firmware is earlier than the versions mentioned above, contact Alesis for an ADAT firmware upgrade. You can check the version of your ADAT firmware by simultaneously pressing the Set Locate and Fast Forward buttons on the front panel of your ADAT. ADAT and ADAT XT Hookup Order If you have 2 or more ADAT's of mixed types (such as one original ADAT and one newer ADAT XT), always place the ADAT XT first in the chain, before the original ADAT. ADAT Loses Communication If for some reason the Studio 64 XTC loses communication with your Alesis ADAT, you should power cycle both the ADAT and the XTC. You should, however, always lower the volume completely on your audio system before turning off the Studio 64 XTC. ADAT and Powering Down the XTC If you are using an Alesis ADAT with the Studio 64 XTC, you should always lower the volume completely on your audio system before turning off the Studio 64 XTC. ADAT and MMC Window Controls When controlling the ADAT via MMC from your sequencer, the "play" and "record" controls located in most MMC windows (such as in Vision and Cakewalk) will not function properly. To get around this problem, you can use the main transport controls for playing and recording. Using MIDI Machine Control >The Studio 64 XTC's Sync Reference mode must be set to "Internal" when using MMC. >For the fastest possible startup times in Vision, make sure that your Studio Setup does not contain any unnecessary MMC devices. Vision queries each port containing devices that are set to send and receive MMC. Networking with a Studio 4 The manual states on page 84, step 4, that the Studio 4's MIDI/B Thru Switch should be set to "Thru." This is incorrect. To successfully network the Studio 64 XTC with the Studio 4, this switch must be set to "MIDI." -------------------------------------------------------------------------------- > How to Install and Test a Translator PC or other Opcode PC Interface < All Opcode PC interfaces come with a driver disk that contains a very useful bit of software - the Diagnostics test, listed on the disk as MTPCDIAG.EXE. (or 64XDIAG.EXE etc etc). The good thing about this is that you don't even have to install the device driver to see if the actual unit is working or not. I find the best thing to do is run the diagnostics from the floppy, so you can avoid typing in tedious DOS pathnames. - plug in the Power Supply to your TPC (sometimes the PC won't have enough power to run it even thoughthe LED is on, and the diagnostics consequently won't see it..) -restart the machine in DOS (go to Shutdown / Restart in MS-DOS mode) -if you get the C:\Windows prompt, type cd.. -should get you to C:\ type A:\ -should access your floppy drive (which you have already stuck the driver disk into...) -type DIR - this will list the contents of the floppy -enter the name of the diagnostics program ie MTPCDIAG.EXE - this will run it. Now all you have to do is enter the Port and IRQ that the interface is physically on and how many TPC's there are. For parallel (printer port) interfaces this is usually LPT 1, IRQ 7. For COM port (serial) interfaces it's usually COM 1 or COM 2 IRQ 3 or 4, but it can obviously change from machine to machine. It can be a case of trial and error but when you've entered the right info you should see 'trace' 'scale' etc across the top of the screen - you can then play notes that will scroll up the screen in hex, or have the diag. program play a scale out of the interface. If not you will get the familiar "No Response At Selected Port. Setting or Connections may be incorrect. Press any key to continue" message. - If you've tried all settings etc with no luck you probably either have a resource conflict (not good) or a dodgy unit (even worse) If the diagnostics sees the interface you're half way there. Make a note of what settings you entered (ie COM 2, IRQ 3 ) and get back to Windows... (exit diagnostics and type "win" ) If you haven't already installed the drivers from the floppy do it now and restart. -Go to Control Panel/Multimedia/Devices and select MIDI Devices and Instruments, you should see TPC Out 1 and Out 2 listed there. - click on one of the Outs (either one) and select Properties. From the next page select "Settings". In this dialogue you must make sure that IRQ and Port match what you entered in the Diagnostics - otherwise the interface won't be seen and you will be angry. >Notes The Cakewalk TTS Virtual Piano Driver has been reported to have caused problems. Try removing it. >Deinstall / Reinstall I've found the best way to reinstall an Opcode PC Driver is to do the following: 1. Edit your System.ini file. You can find this in C:\Windows. Make sure that you have your View Settings set to "show all files" and that "hide file extensions" is unchecked or you will go mad trying to find it. Open it with Notepad - it looks scary but don't worry, so long as you only edit lines that are to do with Opcode you'll be OK. Having said that you can always make a backup first just to be on the safe side... Scroll down until you get to the [386 enh] section. Depending on your interface you should have an entry here that looks something like " device=opcodev.386" or "device=vstud64.386". Delete that line. Scroll down to [drivers] and delete the line that looks like "midi1=studio64.drv" or similar. Below that, near the bottom you'll have a whole section dedicated to the interface, headed [Opcode Drivers] - it should be fairly apparent that this refers to your interface. Delete the whole section. That's it - save the document and exit, then restart. Next you have a couple more files to take care of.... Go to C:\Windows\System (n.b. note 1 above re: view settings) There are two files here that need to be dealt with and what they are called will depend on your interface. Some examples are... Translator PC - opcodev.386 and TPC.drv Studio 64X - Vstud64.386 and Studio64.drv Studio 64XTC - Stu64xtc.386 and Stu64xtc.drv Studio 128X - Vstud128x.386 and Stud128x.drv Trash them. Trash them all. When you've done that you can restart happy in the knowledge that you won't be re-installing over an old driver. This can cause problems in some situations, particularly with 8 port SE driver updates.