Der große Kurzweil Thread

  • Ersteller DschoKeys
  • Erstellt am
HammondToby schrieb:
Hach, dann gehöre ich auch zu den Jungspunden hier mit 35 Jahren ;)

Kleine Anekdote zu gestern: ich habe meine Setups zu Hause auf meiner PC361 (aktuelles OS) programmiert und auf die Studio-PC3X (OS 1.3) geladen. Fazit: sie hat sich in einer Bootschleife verfangen. Also das OS upgedatet und die Images neu drauf gezogen und alles war gut. Für die entsprechende Show kommt nur die PC3X und der Ventilator als Leslie zum Einsatz, ich bin der zweite Keyboarder. Macht schon Spaß, die Kiste vor allem als Synth einzusetzen :)

Grüße vom HammondToby
Zum Vergrößern anklicken....

Der Setup Mode ist einfach fantastisch. Ich kann mich da ohne dämliche Hürden und Fallen vollkommen ausleben, was Controllers und Layers/Splits angeht. Da lebe ich lieber mit ein wenig angestaubten Natursounds, als mich ständig mit Hirnlosigkeiten rum zu schlagen. Wenn man dann mit Händen, Füßen, zwei Wheels und dem Ribbon einen Lead kontrolliert ist es einfach Spaß pur. :)

Noch bin ich der Jüngste!! :D
 
  • Gefällt mir
Reaktionen: 2 Benutzer
hi Hallöle..na da bin ich Quasi fast in der Mitte mit 40..genau....:)
 
HammondToby schrieb:
Hach, dann gehöre ich auch zu den Jungspunden hier mit 35 Jahren ;)

Kleine Anekdote zu gestern: ich habe meine Setups zu Hause auf meiner PC361 (aktuelles OS) programmiert und auf die Studio-PC3X (OS 1.3) geladen. Fazit: sie hat sich in einer Bootschleife verfangen. Also das OS upgedatet und die Images neu drauf gezogen und alles war gut. Für die entsprechende Show kommt nur die PC3X und der Ventilator als Leslie zum Einsatz, ich bin der zweite Keyboarder. Macht schon Spaß, die Kiste vor allem als Synth einzusetzen :)

Grüße vom HammondToby
Zum Vergrößern anklicken....

das hab ich auch schon mal angestrebt um mein vk8 mal daheim zu lassen. hat mir aber nicht so gefallen vom sound. was nimmst du denn für einen grundsound vom pc3x?
 
mdccclx schrieb:
das hab ich auch schon mal angestrebt um mein vk8 mal daheim zu lassen. hat mir aber nicht so gefallen vom sound. was nimmst du denn für einen grundsound vom pc3x?
Zum Vergrößern anklicken....

Ich nehme neuerdings den HX3 Expander für Orgelsounds. Das kleine Kästchen lässt sich wunderbar mit dem PC361 fernbedienen und spart den Ventilator, weil die HX3 Lesliesimulation mittlerweile fast auf Augenhöhe mit dem Ventilator ist. Die HX3 Rockzerre ist sogar eine ganze Ecke besser.

Und so klingt's:

https://soundcloud.com/organaut/sets/hx3-organ-leslie-comparison

https://soundcloud.com/carsten-meyer-1/hx3-mk3-demo
 
Ja, das schlimme an nem guten Organ-Sound ist, man gewöhnt sich sofort dran :redface: Seit ich ne C2 hab, spiel ich die Kurzweil KB3 nur noch selten und wenn ich nur das PC3 dabei habe, fehlt mir da schon was.
Wie lange musstest du denn auf den Expander warten? Ich liebäugle schon damit, oder so wie es toby macht, den venti am 2. ausgang am pc3 dranzuhängen. Aber das gleiche wirds nicht sein.
 
klingt schon sehr gut der hx3. aber eigentlich wollt ich ein kastl weniger.
 
KB3 ist schon ok, mit Ventilator allemal. Aber richtig glücklich macht HX3, wenn man Geduld hat. Zur Zeit warten alle auf die neue Version.
 
Nach Frusterlebnis im Übungsraum und reichlich Internetlesen hab ich da nochmal ne Frage...: habt ihr einen ultimativen Tipp, wie man den Akustik-Klaviersound (insbes. Über PA) so verändern kann, dass es nicht nach Kinderspielzeuggepiepse klingt ( ...bezieht sich eigentlich auf alle vorhandenen Presets im PC3LE aber auch auf das Yamaha P 95)?
 
OMMH schrieb:
Nach Frusterlebnis im Übungsraum und reichlich Internetlesen hab ich da nochmal ne Frage...: habt ihr einen ultimativen Tipp, wie man den Akustik-Klaviersound (insbes. Über PA) so verändern kann, dass es nicht nach Kinderspielzeuggepiepse klingt ( ...bezieht sich eigentlich auf alle vorhandenen Presets im PC3LE aber auch auf das Yamaha P 95)?
Zum Vergrößern anklicken....
Stellt sich natürlich die Frage, was für eine PA-Anlage im Proberaum steht?
Gerade bei den gerne genutzten Zwei-Wege-Systemen - möglicherweise noch mit Horn als Hochtöner - besteht das Problem, dass die entscheidenden "Mittenfrequenzen" für den "vollen" Pianoklang etwas undifferenziert abgebildet werden. Oft sind auch EQ-Einstellungen am Mischpult etwas unglücklich gewählt. Hier würde ich für deine Keys am Anfang alles auf "bypass" stellen und später vielleicht störende Frequenzen absenken.

Mein "Rezept" wäre:
Den Piano-Sound trocken (kein Hall), oder mit einem sehr kleinen Hallraum, spielen. Beim PC3 nutze ich Live eigentlich nur den Medium- oder Small-Hall. Gezielt die unteren Mitten (um 800Hz-1200Hz) etwas anheben und vielleicht die Höhen (größer 8000Hz) und Bassfrequenzen (weniger als 400Hz) absenken.
 
Gibts am LE auch das 842 Pro Piano bzw. 843 Pop Piano?
 
Miss ich im Proberaum kontrollieren...ich glaube aber schon...
 
Ja, gibt es!
 
Ich bin am verzweifeln. Mein K2500S, den ich bei der Coverband einsetze, hat in letzter Zeit immer mal wieder Probleme mit den Outputs gemacht, sprich aus dem Master kam nur ein dünnes verzerrtes und sehr leises Signal. Ich konnte mir akut helfen, indem ich die Subouts A genommen hab, wo ich dann allerdings nur ein Signal ohne Effekte hatte. Mir egal, weil ich eh nicht viel Effekte einsetze. Hauptsache, der Gig konnte durchgezogen werden. Zurück im Poberaum war alles wieder gut. Beim nächsten Gig auch alles gut, dann beim folgenden die selbe Problematik wieder. Zuhause konnte ich das Problem wenigstens noch nachvollziehen, hab dann einen Systemreset gemacht, und alles ging wieder - zumindest im Proberaum. Beim Gig dann wieder dasselbe, zumindest auf dem linken Master Out. So hab ich zwar Mono gespielt, aber mit Effekten. Zu Hause war gleicher Zustand. Ein Systemreset hatte diesmal keine Veränderung gebracht. Ich hab ja noch einen K2500X, dort hab ich dann das Audio I/O Board ausgebaut und in den 2500S verfrachtet. Ergebnis: Beim K2500X funktioniert nachwievor alles, beim K2500S auch. Audio Board defekt oder war's doch was anderes? Wer weiß, egal. So spiel ich erst einmal weiter.
Dann leider das nächste Problem. Ich will meine Sicherung wieder zurückspielen, denn der RAM in der Kiste ist nach Systemreset natürlich gelöscht. Natürlich hab ich alles auf die interne Festplatte gesichert. Aber - Ich kann nicht auf die Festplatte zugreifen. Sie läuft, aber SCSI 0, 1, 2 ... not found: "Problem with mounting disk"! Auf Floppy hab ich leider keine Sicherung. Alle Kabel hab ich überprüft, Platte läuft ja auch. Woran könnte es liegen? Irgendjemand einen Tipp für mich?
Mir würde sonst höchstens noch einfallen, die Platte auszubauen, entweder in ein Externes Gehäus, um sie am PC auszulesen (wenn das überhaupt aufgrund des Formats geht) oder worst Case in den K2500X einbauen, um sie dort auszulesen, und das Backup auf die Floppy schieben. Das ist aber ein sch.e.i.ss Aufwand... :(
 
Hi
Ich hab hier so'n alten K2000 und den noch über SCSI mit nem ebenso alten Mac verbunden - kann mich noch dunkel erinnern, das ich damals mit so ner Spezial Utility die Platte im Kurzweil über den Mac auslesen konnte ist aber bisschen tricky gewesen. Ich hab hier so'n paar alte Unterlagen, vielleicht ist das hier hilfreich:

Kurzweil SCSI Connection Advice


Advice on how to connect your Kurzweil K2000/K2VX/K2500 to other SCSI devices (Hard disks, CD-ROM, Computer). This is an exceedingly thorny area for Kurzweilers and this page will grow as more people contribute -or- I do more research as I get into the SCSI waters myself. Send any suggestions to Palermo@sprynet.com.


Kurzweil's Latest SCSI document.A possibly updated version is available from Kurzweil's website.
Other SCSI Advice.
SCSI, Win95 and Sound Forge
SCSI Corruption of Data
Sharing your Computer's HD with your Kurzweil
Various SCSI configurations
Connecting Ultra Wide SCSI devices to a Kurzweil
See the separate page about How To Enable/Disable SCSI Termination on a Kurzweil


Kurzweil K2000/K2Vx/K2500 SCSI Help
Date: March 6, 1997
From: David Fox, Kurzweil Tech Support (kurzweil@aol.com)
Subject: Kurzweil's Official SCSI Connection Info


[Guidelines | SCSI Chain | Mac | Win95 ]​
The following document contains information on using SCSI with the K2000/K2vx/K2500, as well as specific sections dealing with the using the Kurzweil in a SCSI chain with your computer. For all info below, any reference to the K2000 also applies to the K2vx.
Here are some basic guidelines to follow when configuring a SCSI chain:

  1. Never, ever plug or unplug SCSI cables when your equipment is turned on.
    SCSI cables carry power. The act of plugging or unplugging cables causes momentary short circuits, which can result in damage to the internal circuitry of your SCSI device. The only damage that usually occurs to SCSI hardware comes from static electricity "zapping" SCSI connector pins when the cables are disconnected. The silver colored shell of the SCSI connector on the end of the cable is connected to ground and is safe to touch, but the brass colored pins inside eventually lead to the SCSI interface chip and are vulnerable. One should discharge static from one's body before touching SCSI connectors by touching the 1/4" jacks on the rear of the Kurzweil or another grounded metal object. Any devices connected to the SCSI bus should be turned off when plugging or unplugging SCSI cables.
  2. Including a minimum of 1 foot for internal cabling of each device in the chain, the total length of the chain should not exceed 18 feet. There are some people who suggest that you shouldn't go over 10 feet, but in our experience, if you use good cables and follow the rules of SCSI, you can create a chain up to 18 feet in length (which is what the SCSI specification says is allowed).
  3. No single cable length in the chain should exceed 8 feet.
  4. The first and last device in the chain must be terminated.
    Poor termination is a common cause of SCSI problems. Having more than two terminators on the bus will overload the bus drivers. This will not cause permanent damage to the hardware. However, poor termination can corrupt the data on your disk. There are two "exceptions" to this rule. If the chain is less than 18 inches only 1 terminator is needed. If the chain is 10 feet or more, the chain may need to be terminated at the 10 feet point, using a pass through terminator. The reason that we say you "may need" to do this is that we have found that some people don't seem to require a third terminator, while others can't get a longer SCSI chain to work without one.
    The Kurzweil comes internally terminated, and so you will normally want it to be on one end of the chain. The K2000 keyboard must be at the end of the chain since it has only one SCSI port. (If you are hooked up in a chain with a computer, the computer will always be the other end of the chain.) If you need to have the Kurzweil in the middle of the chain, the termination must be removed. This should be done by an authorized service center. In the case of the K2000, it involves removing termination resistors. In the case of the K2500, there are several different possibilities - some have termination resistors that must be removed, others have jumpers that get moved. The newest K2500s have a termination switch on the back, so you can disable termination yourself.
    If you install an internal drive in the Kurzweil, termination must be removed from the Kurzweil. If the Kurzweil is at the end of the chain, termination resistors should be removed from the K2000 and the termination left on the internal drive. This makes the drive at the end of the chain. If you install an internal drive and the Kurzweil is in the middle of the chain, termination must be removed from both the Kurzweil and the drive. If you add an internal drive and the Kurzweil is not hooked to any other devices, termination should still be removed from the Kurzweil. (See the rule about a chain less than 18 inches, above.)

    NOTE: For the K2500 keyboard models:
  5. If you install an internal drive, the SCSI through port will not work and you must hook up only to the main SCSI port. Therefore, in this case the Kurzweil can only be at the end of the chain.
    External drives may or may not be internally terminated. If a drive is not terminated and is on the end of the chain, you can purchase an external termination clip, which plugs onto the second SCSI port (most drives will have two ports). Some drives also have an automatic termination feature - if you only have a single SCSI cable plugged in, the drive terminates itself, but if you plug in a second SCSI cable, termination is turned off.
  6. Use only true SCSI cables - high quality, twisted pair, shielded SCSI cable. Do not use RS232 or other non SCSI cables. The majority of SCSI cables we've tested were poorly made and could cause damage to data transferred to and from the disk. Nearly all the SCSI data problems Young Chang's engineering department has had have been due to bad cables that didn't twist pairs of wires properly. Cables made by APS Technologies (800.233.7550) are very good and are highly recommended. Good cables that use twisted pairs of wires and twist each SCSI signal wire with a ground wire are essential to reliable data transfers to and from the disk drive.
  7. Impedance mismatching between cables from different manufacturers can cause problems. Avoid this when possible by getting all your cables from the same manufacturer.
  8. Each device in the chain (including internal hard drives) must have its own unique SCSI ID.
    There are 8 ID numbers (0-7). The default Kurzweil ID is #6. Macintoshes use ID 7 and SCSI cards for PCs are also normally set at 7. The internal drive of a computer is normally set at 0. For an external drive, there will usually be an external switch which allows you to choose the ID, although with some drives, it may have to be done by opening the drive and changing jumper pins. Most drives will allow you to choose any ID, although there are some which limit your choices - for example the Zip drive only gives you the choice of 5 or 6. You can change the SCSI ID of the Kurzweil on the MIDI Receive page, but we recommend leaving it at 6 and changing your other devices if needed, since each time you hard reset the Kurzweil, it returns to 6. If you forget to change it after a reset and have a SCSI ID conflict, you can lock up your SCSI chain and forget the reason why.
    One thing to watch out for if having a hard drive installed in the Kurzweil - many fixed drives come set with their default at 6 (the same as the Kurzweil). Make sure your service tech knows to set the ID to a different number (this is normally done by moving jumper pins on the drive). One curious side effect of this problem - if the internal drive is set to the same number as the Kurzweil and you have nothing else in the SCSI chain, then you will see the drive show up on every ID except for its own (the Kurzweil shows up on that ID, since it is also on the ID).
    If you do have more than one device with the same ID, the Kurzweil may lock up when you scroll through the SCSI numbers in Disk mode, or if you are in a chain with a computer, it may not boot up at all.
    If you have more than one Kurzweil, they can be on the same chain and both be able to access any drive in the chain (though not at the same time). Make sure to change the ID on one of them.
    If you are having problems getting the Kurzweil to see a device on the chain, sometimes just changing its ID to a different number may fix the problem, even there was no device ID conflict before. There is no logic to this phenomenon - it's just another SCSI weirdness.
    As a general rule, we recommend only changing the ID of a drive when the system is powered off. It is possible (although unlikely) that data could be corrupted if the ID of a drive is changed while it is turned on.
  9. Theoretically all eight SCSI IDs can be used, however, we often here of users having problems with more than 5 IDs. This may be more of a result of not following all the other rules (especially concerning cables), but some SCSI devices seem to be picky. We have also gotten reports from users who state that they can only get their SCSI chain to work when their devices are hooked up in a specific order. Other than having the two ends of the chain terminated, order should not matter, and yet it does for some people. This may be due to impedance variations in the various units, varying internal cable lengths, etc. The bottom line is that if you are having problems getting your chain to work and you have followed all the other rules, try changing the order of the devices.
  10. If the Kurzweil is in a chain with the computer, power up the Kurzweil and other devices before booting up the computer.
    Some people report that they can't get their computer to boot up if the Kurzweil or other devices are turned off, while others are able to do this Your best bet is to have everything turned on.
  11. Like with any disk that is read to and written from many times, the data on a Kurzweil disk can become fragmented.
    If the disk becomes severely fragmented, there is a chance that the file allocation table can become corrupted and some or all of the files unreadable. For this reason, we recommend that every so often you back up all your data to another drive and reformat your disk. Or, if the disk was formatted in DOS from a computer (see below),you can run a program such as Norton Utilities on a PC and optimize (defragment) the disk. For Mac users, this is not an option - Norton for the Mac won't work with a DOS formatted disk, even if you have a DOS mounting utility.


Using the Kurzweil in a chain with your computer:

  1. SCSI was never designed originally for the concept of having more than one master on the chain. Therefore, the computer assumes that it is always in charge of the chain, and the SCSI bus is always free for it to take control. The Kurzweil will act as a slave until you go to Disk mode and select one of the functions; at that point, the Kurzweil tries to take control of the chain. If the computer tries to access the chain while the Kurzweil is in control, the computer and the Kurzweil are both likely to lock up, and your only solution will be to reboot both devices. It is even possible that data on a disk may be corrupted when this happens (although this is less likely). To prevent the computer from accessing the chain when you don't want it to, you should make sure to turn off and/or disable screen savers, e-mail, network file sharing, and any INITs or TSR's that run in the background - anything that might cause the computer to access the SCSI chain, even if it is the computer's own internal hard drive. For the PC, if your main internal drive is an IDE instead of a SCSI drive, you won't have to worry about accesses to that drive. But it is still wise to make sure you have nothing in your system that would cause the PC to access SCSI when you aren't touching it. If you only occasionally need to have the computer hooked to the Kurzweil, you are best off plugging and unplugging it from the chain, to prevent the potential problems described above. But if you do need to have it in the chain regularly, one solution is to get a SCSI switcher. This box allows you to switch back and forth between specific connections without having to power off your units and plug or unplug cables.
    Because of the potential hassles, you may want to consider whether you really need to have the Kurzweil in the chain with the computer.
    There are a few reasons why you would need to have it in the chain:
  2. A. You are using a sample editor, such as Alchemy, Recycle, or Sound Forge, which allows you to send samples back and forth between the Kurzweil and software via SCSI.
  3. B. You have a removable media drive and want to use it for both the Kurzweil and the computer (with separate cartridges for each device).
  4. C. You want to use the computer for reorganizing or renaming files.
  5. D. You want to use the computer for backing up data from a drive which holds your Kurzweil files. This is especially useful since the computer can access SCSI devices much faster than the Kurzweil (depending on drive speed). It also allows you to use backup devices not supported by the Kurzweil, such as DAT backup drives.
  7. Let's talk about these last couple of situations. While the Kurzweil floppy format is DOS, the SCSI disk format is not a true DOS format. It is very similar to DOS, but does not fully follow the DOS specification. Therefore, your computer may or may not be able to recognize a SCSI disk formatted by the Kurzweil. (Some SCSI drivers for the PC and some Macintosh DOS compatibility utilities do recognize our format - more on this in the sections on platform specific issues.) However, if you have a K2000 with version 3 or later or a K2500 (any version), it can read and write to a DOS formatted disk. Kurzweil does not support disk partitions, so if the drive is formatted with partitions, the Kurzweil will only see the first partition.
    If you do plan on hooking the Kurzweil to your computer, we strongly recommend that you format any Kurzweil drives in DOS, even if your computer is able to recognize our Kurzweil-DOS format. Even though the software may recognize our format, there could be subtle problems that arise in certain situations, since the computer thinks the drive is a true DOS formatted drive when in fact it isn't. If you have a drive that is already formatted by the Kurzweil, we recommend you backup your data and reformat the drive in DOS from the computer.
  8. Even when your computer can read a disk with Kurzweil files on it, the Kurzweil file format itself is a proprietary format, so the computer can't do anything with the file besides rename it and move it around. However, these two features can be very handy, especially if you need to reorganize a complex file hierarchy. If you have a K2500 or a K2000 with v3 or later, then you can also export songs in the .MID format and samples in the AIFF or .WAV formats. These standard formats can be read by your computer if you have software which knows how to read them.
  9. Extremely Important!
    If you have a drive in the same chain with the Kurzweil and the computer you need to be careful about making any changes to the disk from the Kurzweil. When you boot up the computer, it looks at all the SCSI devices. If it sees a drive whose format it recognizes, it will attempt to mount that drive. When it does this, it will look at the File Allocation Table (FAT). The FAT is a table that describes where all the data resides on the disk. Anytime you write to the disk from the computer, it updates the FAT so it knows about the changes to the disk. The same thing happens with the Kurzweil - if you write to the disk from the Kurzweil, the Kurzweil will update the FAT. But in this case, the computer DOES NOT KNOW the FAT has been changed. At this point, if you write to the disk from the computer, you could corrupt your data, since the computer could write to spots on the disk that were just written to by the Kurzweil.
    The solution is to unmount and then remount the disk. That will cause the computer to look at the FAT again and see the changes you made from the Kurzweil. In the case of removable media drives, this is simple. Just eject the disk and stick it back in the drive. In the case of a fixed drive, you will have to use some type of disk utility to have the computer unmount the disk and then remount it.
  10. Some users report that their computer won't boot up if the Kurzweil is powered on. This is normally a sign of a SCSI ID conflict, but these users have sworn that they have every device set to a different ID. We have never been able to discover a pattern as to why this occurs, but the solution is to power up the Kurzweil after the computer has booted up. Then you can use a SCSI utility to have the computer scan the SCSI chain again, if you need the computer to see the Kurzweil's internal drive. If you do encounter this situation, double check to make sure that every device has a different ID. (Other users report that the computer won't boot up if the Kurzweil is powered down, but this seems to be rare if your chain is properly terminated.)
  11. The Kurzweil can read other sampler's SCSI format disks (Roland, Akai, and Ensoniq). None of these other companies use DOS for their disk format. So if you have a foreign format disk such as a CD-ROM or removable media cartridge, as soon as you stick it in the drive, the computer will inform you that it can't read the disk and ask if you want to Eject or Erase the disk. At that point, do nothing on the computer. Instead, go to the Kurzweil and perform whatever disk function you need. Once you are done, you can click on the Eject option on the computer to eject the disk. The computer will then return to normal operation.
  12. CD-ROMs for computers are normally formatted in the ISO 9660 format. This is a standard format that allows CD-ROM manufacturers to have both DOS and Mac applications on one CD and have the computer recognize only the files on the CD intended for that platform. Kurzweil does not support the ISO 9660 format. Instead CD-ROMs are burned as Disk Image copies of a Kurzweil or DOS formatted source disk. So if you have a CD-ROM of .WAV files (which is essentially in DOS format), the Kurzweil won't be able to read that CD. You will have to copy those files to another DOS disk, at which point they can be imported into the Kurzweil. For those of you who have a CD-ROM Writer and wish to burn your own CDs, you need to configure your software to make a Disk Image copy. With some software this means that the source disk must be smaller than the maximum capacity of the CD, since the software wants to copy every sector on the source disk. However other software (for example, the Toast program for the Mac) will allow you to define only part of your source disk and burn a Disk Image of only that part of the disk.
    Another issue is what happens when you put a Kurzweil CD into your CD-ROM and it is connected to the computer (particularly significant for those using an internal CD-ROM in their computer). In point 5, above, we discussed what happens with a foreign sampler format CD. In the case of a CD created in Kurzweil format, the computer may or may not be able to recognize it. For Mac owners, if you have the proper DOS recognition utility (see the Mac section below), a Kurzweil formatted CD will simply show up as a DOS disk.
    But for PC owners, it is more complicated. Depending on the SCSI card and SCSI drivers in your system, the computer may or may not be able to recognize the Kurzweil format and may or may not be able to handle a CD which is not ISO 9660 (see the PC/Win95 section below).


Macintosh Specific Issues
Please read the entire section on using the Kurzweil in a SCSI chain with your computer before continuing.
We recommend that you don't scroll on the Kurzweil to ID 7 (the ID of the Mac itself). You are likely to lock up the Kurzweil and crash the Mac. Some people also report having this occur if they scroll to ID 0 (the Mac's internal drive). If you do scroll on the Kurzweil to the SCSI ID of any Mac formatted hard drive, make sure that you don't press one of the soft buttons while that drive is set as the current drive, since it is possible you could lock up your SCSI chain, or even possibly corrupt some data on the disk.
The biggest issue for Mac owners is that the Kurzweil can read and write to a DOS formatted drive, but not a Mac formatted drive.
For Mac owners who want to hook up their Kurzweil drive to the Mac for backup purposes or have the Kurzweil in the SCSI chain with other drives, this has presented potential problems. Much of the DOS compatibility utilities that are available were designed originally just for floppies and don't deal well with various types of SCSI drives.
If you have version 7.5 or later, included in your system is a utility called PC Exchange. Although PC Exchange will recognize some DOS formatted removable drives, the problem is that you can't format various drives such as the JAZ and other large removables in DOS from the Mac, and the Mac won't even see DOS formatted fixed drives.
However, we have discovered software which changes all this. It is from a company called Software Architects. They have two programs which can be used. (See below for contact info.)
The first is called FormatterFive. This software will allow you to both Format and Mount virtually ALL types of drives on your Mac. You can easily format any drive in DOS right from the Mac. Even better, it recognizes the Kurzweil format as DOS! (Remember that our SCSI format basically is DOS but is not fully implemented DOS.)
With FormatterFive installed, any Kurzweil formatted drive, including the Kurzweil's internal hard drive will automatically show up on your Mac desktop. You can then open up the drive on the Mac and use it to rearrange and rename files with ease. You can also format a JAZ cartridge (or any other drive)in DOS from the Mac without problems. The Mac will also recognize a Kurzweil format CD-ROM (Remember that Akai, Roland, and Ensoniq formats are still not recognized by the Mac).
A second program from the same company is called DOS Mounter 95. This works similarly but only for removable media drives (it doesn't support fixed drives). DOS Mounter 95 doesn't format drives - it simple allows you to mount DOS drives. But it comes with a second application called Multi Formatter which allows you to format any removable drive in DOS. This combo is a better choice if you don't have a fixed drive, because it is less expensive than FormatterFive.
There are a couple of issues that you still have to watch out for:
The first issue has to do with formatting in DOS vs. formatting from the Kurzweil. Even though these programs recognize our format, we still strongly recommend that you format in DOS from the computer. While testing these programs with a Kurzweil formatted disk, we noticed that sometimes the computer would not recognize an updated FAT when it had been changed by the computer and the disk unmounted and remounted. When the cartridge was formatted in DOS by the Mac, this problem was not encountered and everything worked perfectly. So if you have a drive already formatted by the Kurzweil, you should plan on backing up the data to another drive (which you can do with the Mac), then reformat the drive from the Mac and restore your data to the drive.


Second, you still have to watch out for the situation where the FAT gets changed and the Mac doesn't know it (see point 4 in the SCSI Chain section)


As we mentioned before, in the case of a removable media drive, the solution is simple - simply eject the cartridge and reinsert it. This causes the Mac to read the FAT again. But in the case of a fixed disk, you obviously can't eject the disk. In the Formatter 5 utility, there is a button that lets you unmount a drive. But when testing we found that sometimes when you go to a SCSI ID for a fixed drive, the button becomes grayed out and can't be selected. However, we have discovered a way around this problem.


What you need to do in order to unmount a fixed disk is to drag the icon for the disk into the Trash. Once you do this, the Mac will unmount the drive, and the Unmount button on the screen turns to Mount and can be selected. You can then press the button to remount the disk. Once you have done this the button turns back to Unmount and can now be selected. During our testing, it appeared that the disk needed to be dragged to the trash only once. After that, the Unmount/Mount button was always available.
For more information on these programs contact:
Software Architects
19102 North Creek Parkway #101
Bothell, WA 98011-8005
(206) 487-0122, 487-0467 (fax)


PC/Windows95 Specific Issues
Please read the entire section on using the Kurzweil in a SCSI chain with your computer before continuing.
The PC, unlike the Mac does not have SCSI built in as a standard part of the computer. Instead you have to have a SCSI card added. As is often the case with these things, not all cards are created equal. We recommend that you use an Adaptec SCSI card, or any other card that uses the ASPI standard protocols (ASPI was created by Adaptec).
The PC may or may not recognize Kurzweil formatted drives. This depends on both the SCSI card and your SCSI driver. Since our format is not true DOS, it is not surprising that the PC won't recognize our format, but some drivers seem to be more tolerant than others. Some users have reported to being able to recognize our format with a Future Domain 1670 SCSI card used in conjunction with a Corell ASPI SCSI driver. Other card/drivers combinations may work as well. Even if your PC can recognize a Kurzweil formatted drive, we still recommend that you format the drive in DOS, to help prevent any potential problems.
The SCSI driver you install can also affect other things. We have heard reports of users who could not do SMDI transfers using Sound Forge. The problem turned out to be the SCSI driver they were using. Sonic Foundry can recommend SCSI cards and drivers which will work with their software.
Since the Kurzweil recognizes DOS formatted drives, it will be able to see the internal hard drive of your PC, as long as it is SCSI and not IDE (it will only see the first partition). We STRONGLY recommend that you NEVER write to this drive from the Kurzweil. Since this drive most likely contains your system software, you are just asking for trouble if a SCSI conflict between the two devices corrupts your data on that drive. Of course, it is perfectly acceptable to use the PC to copy Kurzweil data from another drive onto that drive. As long as the PC is in control, no problems will occur.
If you have Windows 95, you will encounter another issue. Apparently Microsoft changed Win95 so that it thinks it must have a SCSI driver for every device in the SCSI chain. (Previous versions of Windows don't require this, nor does the Mac.) Of course, there is no driver for the Kurzweil itself, and there is no need for one, since the computer won't normally have any SCSI transactions with the Kurzweil processor. The only situation in which this occurs is if you are running sample editing software such as Sound Forge. In that case, the software already knows how to communicate with the Kurzweil via SCSI (using the SMDI protocol).
So here is what happens when you boot the PC and the Kurzweil is powered up and connected to the chain: The PC gives you a "New Hardware Detected" message and asks you to install a driver from disk. You can then select "No driver available, don't ask again" as an option. The PC will give you this message 8 times! Apparently it asks once for each Logical Unit Number, which is a subset of the SCSI ID number. If you go to your Device Manager, you will see 8 K2000s (or K2500s), but these represent only one SCSI ID. Once the PC asks these questions, you should not see these messages on subsequent power ups, unless you reconfigure your SCSI setup.
NOTE: See the Launch Pad page about the Windows95 "Unknown Device" problem and solution for exact instructions on handling this annoyance.
Questions should be directed to David Fox at Kurzweil Technical Support.


Date: March 2, 1997
From: Al Jewer (AlJewer@aol.com)
Subject: Re: K2500 + SCSI + WIN95 + Soundforge
I have been using Sound Forge with my K2500 to edit and transfer samples, and it is wonderful. The SCSI transfer is very fast, and Sound Forge has a very complete collection of tools to do virtually anything you would want to do.
The trick is to get the K2500 working on your external SCSI bus. There has been a large amount of discussion, and I guess most of it boils down to the following:

  1. Proper SCSI termination. I put an external connector at the end of my SCSI chain, and use an external terminator when the K2500 isn't plugged in. Make sure that the drive in the K2500 IS terminated. Also, set it to an ID that doesn't conflict with any of your computer's disks or other peripherals. (I use ID 2).
  2. BIOS settings. Make sure you turn the transfer rate for the K2500 down to 5 Megs/second. This can help overcome the problems of the additional cable.
  3. Turn on the computer and the K2500 at the same time. This lets the K2500 boot while the computer is doing RAM checks, so as to not have two bus masters competing for resources during bootup time. It is not advisable to plug or unplug the SCSI cable with things turned on.
Disk setup in Win95: Set the disk up to be "removable" (although it is not).
Also, other setup parameters can help make it work. Perhaps some benevolent soul can post more details on this. Mine works OK now, but I understand that different systems can have various problems if the K2500 disk is not set up correctly.
Best of luck!
-al


Subject: Various File Corruption Questions...
Date: Tue, 15 Apr 1997
From: Ethan Miller (ethan@bass-station.com)
Greetings.
Let me preface these questions with the following, just in case, though it is nor really a scsi issue I think....
I have my K2000 on the same SCSI chain as a Mac using PC Exchange to mount a drive that has been partitioned and formatted using FormatterFive... one partition formatted for DOS one for MacOS. All entities on the SCSI chain seem happy enough, read and write files, boot when they should, etc.
However...
I am having a *wide* variety of apparent file format corruption problems going both to and from the K2000...
For example:
Samples exported from the K2000 to either .AIFF or .WAV appear corrupt to both Sound Designer II and other auido format conversion utilities. This is also true after using Res Edit to set corrrect file and creator types for these files. I also tried exporting these files directly to a DOS formatted floppy (as opposed to the partioned HD), same problem.
Various files (bank saves, macros, etc.) are routinely going bad just sitting on disk. They look fine, but when the K2000 tries to open them it gets 98% throught the load and then reports a bad file: Error 0.
Personally I think, something about PC Exchange is trashing these because if I load programs straight from a K2000 floppy they work fine, but if I copy the same files from the k2000 to the DOS formatted HD, and then load them, I get the "Error 0" condition described above.
Obviously this is a nightmare.. anyone experienced these kind of behaviours?
Thoughts, suggestions, solutions?
ethan




Subject: Sharing a partition of your computers' HD with the Kurzweil
Date: Tue, 15 Apr 97
From: NM1@shafer.usa.com
Just in case anyone is tempted to act on my drive-combining idea of partitioning a portion of a Mac's hard drive, then intitializing that portion in Kurzweil format, well, FORGET IT!!! Here's what Kurzweil's David Fox had to say:
>I don't believe this can be done, and even if it could, it is an extremely bad
>idea. You don't want the Kurzweil writing to the disk that contains your system
>on it. If any SCSI weirdness happens, you could destroy all your Mac data.
Oh well, I'm off to the Zip disk store again.
Neil
nm1@shafer.usa.com


(Here's my original message):


>>Does anyone know if it's possible to partition a portion of my Mac's hard
>>drive, then initialize just that portion in Kurzweil format? If so, would my K2000
>>then be able to recognize it on the disk page, and access that portion?
>>
>>It would be nice to use a part of my Mac 7600's 1.2 GB hard drive for my
>>K2000 (while using the rest for my Mac), but as we all know, any drive the
>>Kurzweil uses has to be initialized in Kurzweil format.






Subject: Terminating various SCSI configurations
Date: Tue, 15 Apr 1997
From: Josef Rabitz (josef.rabitz@sea.ericsson.se)
With: Tony Palermo (Palermo@sprynet)
A SCSI chain must be terminated on both ends--and only on both ends. For short SCSI chains like those within a Kurzweil, you may leave one end with the termination disabled. You will find diagrams of several typical SCSI chains below. Once you have figured out how you want to configure your SCSI chain, see the separate page about Kurzweil SCSI Termination advice for a step-by-step tutorial on setting up your Kurzweil for flexible SCSI chains. If you need to terminate a SCSI device, you can use an inexpensive passive SCSI terminator available from Radio Shack or an electronics store. For terminating CD-ROM and hard drives, make sure to get a terminator that matches their SCSI connector. See Adaptec's SCSI connector diagram page for examples. For terminating a Kurzweil from it's external SCSI port, you will need a DB-25 style terminator. There are also active termination schemes, but I don't know anything about them. The newest K2500s have a termination switch on the back, so you can disable termination easily.
Kurzweil SCSI Chains and Proper Termination
Internally, a K2000 from the factory looks like this:
K2000.SCSI.connector
|
|
K2000--------------------------+
|
|
K2000.internal.HD.conn---------+
|
|
K2000.SCSI.TERMINATION---------+ <-------- Factory installed Termination here.
|
|
K2000.SCSI.thru.port


Hard disks come terminated from the factory. If you have a HD installed in your Kurzweil, remove the internal termination of the K2000 and make sure your HD is terminated. See the Launch Pad's separate page about Kurzweil SCSI Termination Advice for a step-by-step tutorial on this operation.
With a single-ended termination, it looks like this:
K2000.SCSI.connector
|
|
K2000--------------------------+
|
|
HD.internal--------------------+
|
HD.internal.TERMINATION--------+ <-------- Termination #1 here.
|
|
-------+ <-------- Internal termination was REMOVED here.
|
|
K2000.SCSI.thru.port


If you use only external disks, then leave the K2000's internal termination on and terminate the last unit of the external SCSI chain:


HD.external.TERMINATION.3------+ <-------- Termination #1 here.
|
HD.external.3------------------+
|
|
HD.external.2------------------+
|
|
HD.external.1------------------+
|
|
K2000.SCSI.connector
|
|
K2000--------------------------+
|
|
-----------+
|
|
K2000.SCSI.TERMINATION---------+ <-------- Termination #2 here.
|
|
K2000.SCSI.thru.port


For configurations using both internal and external HDs, leave the K2000's internal termination off and terminate the internal HD and the last external HD:


HD.external.TERMINATION.3------+ <-------- Termination #1 here.
|
HD.external.3------------------+
|
|
HD.external.2------------------+
|
|
HD.external.1------------------+
|
|
K2000.SCSI.connector
|
|
K2000--------------------------+
|
|
HD.internal--------------------+
|
HD.internal.TERMINATION--------+ <-------- Termination #2 here.
|
|
-----------+
|
|
K2000.SCSI.thru.port


If you use the K2000's SCSI thru port, then remove all terminations inside the K2000:


HD.external.TERMINATION.3------+ <-------- Termination #1 here.
|
HD.external.3------------------+
|
|
HD.external.2------------------+
|
|
HD.external.1------------------+
|
|
K2000.SCSI.connector
|
|
K2000--------------------------+
|
|
HD.internal--------------------+
|
|
-----------+
|
|
K2000.SCSI.thru.port
|
HD.external.4------------------+
|
|
HD.external.5------------------+
|
|
HD.external.TERMINATION.3------+ <-------- Termination #2 here.


Perhaps this is useful for some of you.
Josef Rabitz






Subject: Connecting an Ultra Wide SCSI device to a Kurzweil
On December 18, 1997, Steve Schow wrote:
I own a K2500 and a PC, which is equipped with an Adaptec 2940UW SCSI adapter. That SCSI adapter has two channels on it. It has an Ultra-Wide (SCSI-3) channel and an Ultra non-wide(SCSI-2) channel. Both of those connectors are internal. There is also an external connector...though I'm still a little unclear about whether that external connector can be used for the SCSI-2 channel or whether it must always be used for the SCSI-3 channel. It has the 68-pin interface.
Internally, my PC will have two HD's. One will be an Ultra-Wide 7200 rpm high speed AV drive and will be plugged in to the SCSI-3 port. The other one will be a run-of-the-mill 5400 rpm SCSI-2 drive and will be plugged into the SCSI-2 channel. Keeping them on seperate channels will prevent the slower drive from slowing down the data rate of the faster drive. My SCSI CD-ROM's will also be plugged into that SCSI-2 channel.
Barry Reynolds had this reply:
I solved exactly this situation. See Adaptec's website.
You CANNOT use all three ports of the 2940UW at once. You can only use two at once. So you probably want to use the internal 68pin and the external 68 pin, right?
Run 68pin ribbon cable from your internal UW port to your UW hard drive. Continue your 68pin cable but attach it to your internal SCSI-II harddrive using an INTERNAL 68pin-50pin adaptor made by Adaptec. They have a list of dealers at their website. I think it is around $31.
Here's the tricky part. Your internal SCSI chain must EITHER 1) end with a UW device OR 2) you must use an actively terminated SCSI ribbon cable (4 devices plus active termination for sixty something dollars), also made by Adaptec.
I elected to get this cable, because I also installed an internal CD-R, and I needed more devices on the chain than my original ribbon cable would allow. But if you put your UW harddisk on last in the chain, you'd be ok without active termination.
So, now let's consider the EXTERNAL 68pin port. DO NOT attempt to merely get a 68to50pin cable. Instead, order a 68pin-50Pin SCSI-II EXTERNAL adaptor ($31), made by Adaptec. If ALL of your devices for external connection are not UW (as would be the case in you are attaching external cd-roms, cd-r, k2500, zip, jaz, syjet, etc), then attach this adapter directly to the external 68pin port, attach appropriate SCSI cables, and you are rocking. The ADAPTEC 2940UW automatically determines what is attached at boot up and selects the correct termination status of the 2940, which, with everthing attached, would be unterminated at both ends, right? You still have to set the termination for your attached devices, however.
So, I ended up spending about $150-180 for these cables and adaptors, but it works great.
Now, there is a less eloquent but less expensive solution. Computer parts stores sell adaptors that continue Internal ribbon cable (50pin) to the outside of the computer. If you got one of these, you could attach your UW drive to the 68 pin internal port, attach your scsi-II drive to the internal 50pin port, and continue to run this slower ribbon cable to the outside of the computer, where you would attach all the other stuff. I considered this, but didn't do this, so I don't know if it works.
But the big bucks solution described above works like a charm.
Barry
Bernie had a totally different approach:
I have an Adaptec 2940 and i had a similar situation. You can solve your SCSI problem real easy. just go buy a second scsi card! I bought an Adaptec 1505 for $40 way cheaper and easier than dealing with a bunch of cables. (it has a regular old 25 pin port on the back of it. just hook a short shielded male to male serial cable up to your zip or k2000, and you have no problems.)
here's what my setup looks like:
----------------------------------
Adaptec 2940 UW <----> Seagate 4gig UW drive
(simple. fast. no danger of corrupting boot drive from the K (also leaves your external ultrawide port open for a CD burner in the future.)
K2000 <---> Zip Drive <---> Adaptec 1505 <---> 2gig SCSI drive <---> 4x SCSI CD ROM


[ Top | K2000 Launch Pad ]​


Webmaster: Tony Palermo
Comments: Palermo@sprynet.com
Created: March 2, 1997 / Revised: December 20, 1997

 
Zuletzt bearbeitet von einem Moderator:
Halloooo? Das hier ist das WWW, da gibt's sowas wie Links, da brauchst du nicht gleich eine ganze Datei in einen Post abladen.
 
  • Gefällt mir
Reaktionen: 4 Benutzer
Ich hab's hinbekommen. Hab gesehen, dass der SCSI Terminator-Schalter auf "disable" stand, und ihn einfach mal auf "enable" geswitched, und schon war meine HD wieder da. Ich weiß nicht, warum das vorher funktioniert hat, denn theoretisch macht es ja Sinn, dass der Terminator auf "enable" steht, wenn ich weiter keine Devices extern angeschlossen habe, was ich auch sonst nie hatte, und auch nie den Schalter betätigt hab. Na ja, dies würde auf jeden Fall auch die Probleme mit dem Mounting erklären.
 
Du musst dich einloggen oder registrieren, um hier zu antworten.

Ähnliche Themen


Quick Links

Tipps & Tricks
Fragen (FAQ)
Regeln
Board-Mitarbeiter
Unser weiteres Online-Angebot:
Bassic.de · Deejayforum.de · Sequencer.de · Clavio.de · Guitarworld.de · Recording.de

 Musiker-Board Logo
Zurück
Oben