issue10
EMUSIC-L Digest Volume 46, Issue 10
This issue's topics:
Opcode Max performance on various Macs
PowerBooks and MIDI (3 messages)
Your EMUSIC-L Digest moderator is Joe McMahon .
You may subscribe to EMUSIC-L by sending mail to listserv@american.edu with
the line "SUB EMUSIC-L your name" as the text.
The EMUSIC-L archive is a service of SunSite (sunsite.unc.edu) at the
University of North Carolina.
------------------------------------------------------------------------
Date: Sun, 29 Nov 1992 12:40:34 PST
From: Leigh Smith
Subject: Opcode Max performance on various Macs
Hi,
I'm considering purchasing a Mac to run Max exclusively. I'm currently a
PC guy, I admit it, so it will be a second machine only. My question is:
Opcode (or at least Carter Scholz's Keyboard article) have listed a Mac Plus
with 2Mb and a Hard Disk as recommended minimum. How does such a
configuration perform? Being a real time system, is Max workable on such,
what about an SE? SE/30? Classic? I'm basically trying to gauge Max's
performance on lower end (cheaper) Mac's. Nick, what can you suggest?
--
=--=--=--=--=--=--=--=--=--=--=--=--=--=--=--=--=--=--=--=--=--=--=--=--=--=
| Leigh Smith _--_|\ Email: leigh@psychok.DIALix.oz.au |
| / \ Tel (H): +61-9-450-2014 |
| Perth --> *_.--._/ Perth, Western Australia |
| v |
=--=--=--=--=--=--=--=--=--=--=--=--=--=--=--=--=--=--=--=--=--=--=--=--=--=
------------------------------
Date: Mon, 2 Nov 1992 16:35:13 PST
From: "(metlay)"
Subject: Re: PowerBooks and MIDI
>Everything I've heard says that the Powerbooks are unusable for MIDI, but Nick
>says that Doug Wyatt at Opcode has sorted out the mess. What did he do, and whe
>re can we get it?
>
> --Mark Simon
First of all, "everything you've heard" is at least partially wrong.
The Powerbook 100 works like a charm, and always has. Secondly, the
mess has not been "sorted out," but Doug Wyatt has implemented a
partial fix for the 140 and 170, assuming you can run whatever
software you want to use under OMS, and you don't try to use the
Printer port. The 140's problems can be minimized by applying OMS
1.2beta, which fixes problems with the Modem port although the Printer
port is still hosed. If you use OMS and/or a PB100, you'll be fine.
We tested the three PBs with a wide variety of software, and as reported
in ELECTRONIC MUSICIAN this month, our findings are available for free
by email request. Although I suppose I could just put them right here
and now and save myself the hassle of fielding a zillion requests....
Yeah, that's the ticket. OK, it'll be appended to this letter. Enjoy.
And BTW, Mark, in case you're wondering how "everything you've heard"
about the PowerBooks could be so far off base, it's simple. You probably
listened to Apple, which has been lying through its collective teeth about
the PowerBooks and MIDI in every public music forum for over six months.
--
metlay | and she's a master of return hitting
atomic city | giving rhythm to her posts
| so you read her and think hey it sounds good
metlay@netcom.com | and wish her posts had a soundtrack too (f. ercolessi)
--------------------------- cut here, dudes and dudettes -------------------
This letter contains the sum of Atomic City's current knowledge of
MIDI with respect to the Apple Powerbook computers, containing the
findings of recent tests of the 100, 140, and 170, combined with
late-breaking new results. We hope you find it useful.
A. THE POWERBOOK 100
The 100 works fine if you keep in mind that it's only a 16MHz 68000;
Finale can make it choke. Old versions of Alchemy won't boot, but
that's not a PB problem. The "big name" software we were able to try
(Performer, Vision, Cubase, UpBeat, Galaxy, and MAX) runs fine. It's a
good idea to disable Appletalk, and have software up and running under
MIDI Manager. (Actually, on the 100, you MUST disable AppleTalk, as it
will grab and munge the only available port for MIDI, the printer
port.) If you use Opcode stuff, OMS goes a long way toward
deglitching your work. We weren't able to test everything in the
universe (the test occurred as part of a recording session, not as an
end in itself, but that fact got trimmed from the article in EM), but
here are some highlights....
1. The older version of the MTP desk accessory won't run, but the
MTPII utility, which runs under MIDI Manager, should be fine. In
Nick's words: "The MTP-II DA will run with MIDI Manager, so using that
(via OMS for example) should be OK (and this is the main reason that
I'm considering buying an MTP-II). I don't know if the MTP-II DA runs
on a PB100 using its own drivers. Oh, unless I'm mistaken, the MTP-II
software is a proper application rather than a DA; but I could be
wrong."
The PB100 can run reliably at MIDI speeds - just. Any faster
communication speed (such as MTP's fast handshake) will not work
reliably. To be honest, I've never (in two years of MTP use) notice
any improvement in using fast handshake.If that limitation is
understood and nothing faster than ordinary 1MHz mode is attempted,
the PB100 printer port can handle the MTP, MTPII, and any Opcode
interface up to but possibly not including the Studio 5.
2. MAX handled a patcher designed on the IIci, one that was designed
to kill portables (and really hung up an Outbound 2030 badly), on the
PB100 without breaking a sweat. Nick points out that MAX performance
can be sluggish on the PB100 with really big patchers, but that's true
of any Mac-- you just have to determine the limits of "really big" by
trial and error with your particular platform. I should point out that
Nick uses MAX as a controller-data remapper for live performance with
CASSIEL, and places tremendous burdens both upon the code and the
computer running it.
3. UpBeat ran like a dream.
4. The worst timelag we got with Performer pumping eight MIDI streams
of arpeggios through the MTP from another Mac into the PB was about
2 milliseconds. Not a major issue.
5. Galaxy handled input and output of bundle data from the worst synths
in our rig, the Roland D-70 and Korg Wavestation EX, without a hiccup.
Repeated attempts could NOT produce a failure with ANY synth SysEx dump.
We tested Oberheim, Sequential, Korg and Roland gear without a hitch.
6. Vision and Cubase were not tested as extensively as Performer, but
they run, do not lose input data, and no noticeable timing glitches
were found, although the torture tests weren't as heavy-duty as the one
for Performer. I am currently using Vision on my PB100 with an Opcode
MIDI Translator interface, and it works like a charm.
B. THE POWERBOOK 140, 145, AND 170
Nick Rothwell owns a PB140, which he only considered reliable for
output (it lost a LOT of data on input, not just long sysex dumps.
Apple was wrong on that point, as on many other points) until a recent
Tech Note suggestion by Apple was augmented and implemented by Opcode
in a new version of OMS, 1.2beta. Under 1.2b, the input problem is
solved, but incoming data loses its timestamping. We're still testing
just how bad a problem these 6 msec hiccups can be. NOTE that this fix
only works for interfaces attached to the Modem port! The printer
port is and always will be unreliable, apparently, for input. In his
own words, Nick says: "I haven't hammered my machine heavily yet (and
won't be doing until the next live project I have to prepare, in which
case I'll be using both PowerBooks), but the tests I did (including
SMPTE lockup) suggested the PB140 is OK. 6msec isn't too bad, but you
can hear/feel that length of time." The 170 should have no differences
in performance than the 140 or 145.
C. FUTURE DESIGNS
According to the latest technical data, the 160 and 180 will suffer
from the same problems as the 140, 145, and 170. There is not enough
data available to render a judgement on the Duos. We are not authorized
beta testers of these machines, and cannot promise any early results
at this time. If we do learn something of use, we will see to it that
the Editor of EM, who has been very kind and helpful in his efforts
to relay our findings to a larger audience, will hear of it and pass
it along.
We hope this helps possible Powerbook buyers with any decision they
make. Our findings neither carry nor imply any guarantees from
ourselves or any of the manufacturers involved (especially Apple!).
We would, in closing, like to compliment Opcode on the excellent
reliability of OMS on the Powerbooks, and to thank Doug Wyatt for the
1.2beta patch that renders the costlier Powerbooks at least partially
reliable.( We would also LIKE to express our opinion of Apple's
handling of the whole MIDI question, Powerbook and MIDI Manager
support included, but we'll refrain for legal reasons.)
Please feel free to write or email me with any comments; we do not plan
any addenda to this study at this time, but circumstances may change.
Dr. Michael Metlay
Atomic City Productions
P.O. Box 81175
Pittsburgh, PA 15217-0675
metlay@netcom.com
Many thanks to Dr. Nick Rothwell of CASSIEL for his technical expertise,
and to Mr. Eirikur Hallgrimsson of DEC for his input and encouragement.
------------------------------
Date: Mon, 2 Nov 1992 23:12:31 EST
From: "(Marshall Gilula)"
Subject: Re: PowerBooks and MIDI
is it false that 7.1 fixes the problems for all Pb other than PB 100
-73-
Marshall Gilula
mgilula@newssun.med.miami.edu
------------------------------
Date: Tue, 3 Nov 1992 06:54:58 PST
From: "(metlay)"
Subject: Re: PowerBooks and MIDI
>is it false that 7.1 fixes the problems for all Pb other than PB 100
Almost assuredly. From what we've garnered so far, 7.1 adds more bugs
than it takes away. No official test data on this yet, tho, only rough
trials. Don't bank on an Apple-sponsored MIDI fix any time soon.
--
metlay | and she's a master of return hitting
atomic city | giving rhythm to her posts
| so you read her and think hey it sounds good
metlay@netcom.com | and wish her posts had a soundtrack too (f. ercolessi)
------------------------------
End of the EMUSIC-L Digest
******************************