Subject: MAX Digest - 31 Oct 1999 to 1 Nov 1999 (#1999-315)
Date: Tue, 2 Nov 1999 00:00:37 -0500
From:
Automatic digest processor <LISTSERV@LISTS.MCGILL.CA>
Reply-To: MAX - Interactive Music/Multimedia Standard Environments <MAX@LISTS.MCGILL.CA>
To: Recipients of MAX digests <MAX@LISTS.MCGILL.CA>


There are 10 messages totalling 352 lines in this issue.

Topics of the day:

  1. ibook problems.
  2. good news and bad news (2)
  3. ibook problem solved.
  4. dithering
  5. Dynamics Processing
  6. VX Pocket
  7. Pace and crime
  8. MSP doesn't like my Audiomedia III
  9. nato55

----------------------------------------------------------------------

Date:Sat, 30 Oct 1999 23:53:56 -0700
From:David Zicarelli <zicarell@CYCLING74.COM>
Subject: Re: ibook problems.

"Michael P. Whyte" <matrix6k@YAHOO.COM> writes:

>If I double click on the Max icon it immediately crashes the machine.

Please download the PACE USB Floppy Enabler 2.0; ignore the name--
this init will fix your problem. A link to it is on http://www.cycling74.com

David Z.

------------------------------

Date:Sun, 31 Oct 1999 01:05:14 -0700
From:David Zicarelli <zicarell@CYCLING74.COM>
Subject: good news and bad news

on my favorite subject--Audio cards!

The good news is that I've just uploaded a new version of MSP's ASIO
support to the Cycling '74 news page that works with the Digigram
VXpocket laptop audio interface.

http://www.cycling74.com/support/news.html

The bad news is that according to user reports, the VXpocket
ASIO driver has much higher input-output latency than just using
the Sound Manager on a Powerbook, and degrades the available CPU
performance by 10 to 15 percent. Some people were hoping the ASIO
driver would be better than using Digigram's Sound Manager driver,
but alas, it appears not to be.

Also, while we're on my favorite subject, let's talk about the
Digidesign Digi 001 interface. I had been told by a Digidesign
programmer earlier this month that it would work with MSP using
Direct I/O.

I've now heard from someone who said that Digidesign is going to
prevent other software from working with the interface. So if you're
thinking about buying one these things to work with MSP, you might
want to wait until we have a definitive answer.


David Z.

------------------------------

Date:Sun, 31 Oct 1999 01:51:12 -0700
From:"Michael P. Whyte" <matrix6k@YAHOO.COM>
Subject: ibook problem solved.

I found what I was overlooking. I didn't realize that the usb enabler was a
fix for the software, I thought since I didn't have a usb drive it wasn't necessary.
Oh well, nevermind.
mike whyte
__________________________________________________
Do You Yahoo!?
Bid and sell for free at http://auctions.yahoo.com

------------------------------

Date:Sun, 31 Oct 1999 19:27:40 -0400
From:Neal Farwell <nfarwell@FAS.HARVARD.EDU>
Subject: Re: dithering

Further to my dithering meditations...

I tried some experiments with very low-level audio signals, comparing for
example the sound quality from a cycle~ sine wave at full scale and 1/1000
scale. I'm just using the built-in sound hardware on my 8600/250 - and the
conclusion here is that any quantization artifacts are masked by the noise
floor of the audio outputs; and there's probably sufficient jitter in the
DAC clocks to obviate any need for additional dithering.

Still, for anyone who's using good quality 16-bit hardware, below is a
little dithering experimentation patch. I'd be really interested to know
what sort of results you can get.


jhno said:
>i would be willing to bet that the best sounding digital representation
>would mimic the logarithmic amplitude response of the human ear (since that
>is the apparatus doing the listening in the first place... :).

In the days when the best DACs money could buy were 10 or 12 bits,
apparently there was a lot of work done on scaling d-to-a converters: you
had one dac for the mantissa (?) another for something like the exponent,
and multiplied; to avoid discontinuities, you had to switch the multiplier
value only at zero-bounded blocks, so the hardware was complicated - but
apperently it did sound good. Still, that was then - given the quality of
present day 20+ bit 96KHz dacs, there's no likely gain, at least at the
hardware end, in trying to make log-scale dacs now.


max v2;
#N vpatcher 50 40 781 492;
#P flonum 294 24 35 9 0 0 0 3;
#P user gain~ 294 82 24 100 158 0 1.071519 7.94321 10.;
#P newex 294 49 59 196617 cycle~ 440;
#P toggle 190 358 15 0;
#P newex 254 309 27 196617 + 1;
#P toggle 254 283 15 0;
#P newex 254 335 91 196617 selector~ 2 1;
#P newex 244 402 29 196617 dac~;
#P flonum 492 167 45 9 0 0 0 3;
#P flonum 413 167 49 9 0 0 0 3;
#N vpatcher 105 104 607 521;
#P newex 160 131 27 196617 / 2.;
#N comlet dither p-p (bits);


#P inlet 160 87 15 0;
#N comlet offset (bits);
#P inlet 220 87 15 0;
#P newex 220 205 45 196617 sig~ 0.;
#P newex 91 285 55 196617 /~ 32768.;
#N comlet sig;
#P outlet 91 333 15 0;
#P newex 125 205 45 196617 *~ 0.25;
#P newex 125 170 35 196617 noise~;
#P newex 91 131 55 196617 *~ 32768.;
#N comlet signal in;
#P inlet 91 87 15 0;
#P connect 2 0 3 0;
#P connect 0 0 1 0;
#P connect 3 0 5 0;
#P connect 1 0 5 0;
#P connect 5 0 4 0;
#P connect 6 0 5 0;
#P connect 9 0 3 1;
#P connect 7 0 6 0;
#P connect 8 0 9 0;
#P pop;
#P newobj 334 240 169 196617 p dither16;
#P comment 400 123 82 196617 peak-to-peak amplitude of dither signal;
#P comment 487 135 52 196617 DC offset;
#P comment 544 158 128 196617 Both specified as number of (least
significant) bits at 16 bit output resolution.;
#P comment 115 360 65 196617 patch on/off;
#P comment 180 284 68 196617 dither on/off;
#P comment 170 102 123 196617 set this amplitude low...;
#P comment 170 133 100 196617 and turn speakers UP;
#P comment 138 159 148 196622 be careful for your speakers and ears! Turn
off alerts...;
#P comment 455 310 184 196622 Playing with dithering...;
#P comment 455 352 100 196617 Neal Farwell;
#P comment 455 381 100 196617 October 30th 1999;
#P comment 216 39 70 196617 a test signal:;
#P connect 22 0 20 0;
#P connect 12 0 16 2;
#P connect 14 0 12 2;
#P connect 13 0 12 1;
#P connect 16 0 15 0;
#P connect 16 0 15 1;
#P connect 18 0 16 0;
#P connect 20 0 21 0;
#P connect 19 0 15 0;
#P connect 17 0 18 0;
#P connect 21 0 16 1;
#P connect 21 0 12 0;
#P pop;

=========================================
Neal Farwell

Visiting Fellow in Composition

Music Department
Harvard University
Cambridge MA 02138

(617) 591-9478

nfarwell@fas.harvard.edu

http://www.fas.harvard.edu/~nfarwell
=========================================


------------------------------

Date:Sun, 31 Oct 1999 20:24:04 -0500
From:Nick Lloyd <nxlloyd@IX.NETCOM.COM>
Subject: Dynamics Processing

Anyone know of any good dynamics-processing patches out there? I'm looking
for a rudimentary gate and limiter.

Thanks,

Nick

------------------------------

Date:Mon, 1 Nov 1999 11:51:54 +0000
From:"Carlos \"Zingaro\"" <car.zngr@MAIL.TELEPAC.PT>
Subject: VX Pocket

Hi there,

Been using the i/o stereo mini jacks for audio with my PowerBook G3.
Thinking of upgrading to one of this Digigram VX Pocket PCMCIA cards.
Anyone knows of problems with these cards and Msp? Will there be a need for
some specific drivers?
Thanks.

--
Carlos "ZINGARO" Alves
R. Prest. Arriaga, 59-4o
1200-771 Lisboa - Portugal
ph.fx: +351.21.3970052
car.zngr@mail.telepac.pt
http://www.shef.ac.uk/misc/rec/ps/efi/mzingaro.html

------------------------------

Date:Mon, 1 Nov 1999 21:05:43 -0000
From:Nick Rothwell <nick@CASSIEL.COM>
Subject: Re: good news and bad news

> I've now heard from someone who said that Digidesign is going to
> prevent other software from working with the interface.

I predict that Digidesign (i.e. Avid) are going to go spectacularly
bust in the next couple of years. Clearly, it couldn't happen to a
nicer bunch of people.

--

Nick RothwellCassiel.com Limited
nick@cassiel.comwww.cassiel.com
systems - composition - installation - performance

------------------------------

Date:Tue, 2 Nov 1999 06:49:28 +0900
From:Rob <rmahad@OSK2.3WEB.NE.JP>
Subject: Re: Pace and crime

> Date:Wed, 27 Oct 1999 10:47:46 +0100
> From:
Roland Cahen & Ruth Sefton-Green
> Subject: Pace & crime
>
> >
> >PACE announced its USB Floppy Enabler 2.0 that allows PACE-protected
> >software to run under OS 9 on new machines. I downloaded the updated


> >enabler and tested it on a G3 Powerbook, and it seems to work--
> >at least to enable PACE's own software (protected, of course, with
> >PACE) to run under OS 9.
>
>
> Thank you very much for this information.
> Lucky if you one day plan to buy a new machine.
> For the time beeing, at home, I can't offer anything better than a 7200.
> But unfortunately, my last floppy key disk has decided that I had practiced
> piracy and doesn't want to authorize anymore my external disk.
> I only retreived files from my system disk after a crash using Norton.
> Is that a crime ?
>
> Couldn't we create an association of max users and try something against Pace ?
>
> ------------------------------
>
>

Same happened to me with Max. I lost 3 hard drive installs on my floppy install
disk. With Opcode as it it now, I have to authorize Max with the key disk every
time I use it.

------------------------------

Date:Mon, 1 Nov 1999 20:04:01 EST
From:"please. Thank you very much." <Wiltz0023@AOL.COM>
Subject: MSP doesn't like my Audiomedia III

Hello,
I recently authorized MSP and it will not recognize my Audiomedia III card.
When I startup MAX I receive an error message in the MAX window that says,
Direct I/O Audiodriver: error-6011 acquiring device. I am also unable to
output from ProTools via the Audiomedia card (something that has never
occurred prior to MSP authorization). I have Digisystems Int 3.4.2. (>3.3)
and have made sure The Direct I/O MSP Audiodriver is in the MAX folder not
audiodriver folder. I received a suggestion to click on a message box
containing "; dsp driver setup". This was to open a Digidesign dialog box
that would allow me to identify the AMIII card. But nothing happened. Too
bad, it sounded so good. Any other ideas? I am very thankful for any
knowledge about this predicament.
Best-
Chris Willits

------------------------------

Date:Mon, 1 Nov 1999 21:39:09 -0800
From:Peter Nyboer <pnyboer@SLAMBASSADOR.COM>
Subject: nato55

Hi folks,

I recently purchased nato. It's lovely, but deep. I have only scratched
the surface, playing with some controls for quickdraw (type, to be
specific) and multi-video-track movies. (BTW, to add a video track in
MoviePlayer Pro, do an "option-paste")I've been testing it on my
7100/Sonnet G3, and it's been quite fun, with a few crashes (I am not
surprised, given my minimal machine).
For example, I had a three track movie (Sorensen 100x72 5fps) and was able
to show each track numerous times (I had at least 6 of each at times,
perhaps more), reposition them with a mouse click, and "spray" words of
varying size, type, and color all over the screen.
THere is an insane amount of control possible. Commands, documentation and
help files are terse and in the easy version of "m9ndfukcese," but pretty
readily understood. When I get frustrated by the language, I simply
comfort myself with "hey,at least it's not in Danish!"
A simple description is that it seems to be tons of QT and QD and QD3D


routines "rerouted" for use in max.
Even with the hacking described above, I was able to create things that
just wouldn't happen in Photoshop, Illustrator, or AfterEffects, due to the
generative power of Max.

Thought I should let you know,

Peter.

Peter Nyboer
pnyboer@slambassador.com
www.slambassador.com
"If I had the power....
to make a woman....
yeahhh"
--Johnny "Guitar" Watson

------------------------------

End of MAX Digest - 31 Oct 1999 to 1 Nov 1999 (#1999-315)
*********************************************************