Subject: MAX Digest - 20 Apr 1999 to 21 Apr 1999 (#1999-122)
Date: Thu, 22 Apr 1999 00:00:01 -0400
From: Automatic digest processor 
Reply-To: MAX - Interactive Music/Multimedia Standard Environments
     
To: Recipients of MAX digests 

There are 14 messages totalling 404 lines in this issue.

Topics of the day:

  1. Full Screen Movieplus & Virtual Scratch
  2. where max messages index & glossary? (2)
  3. where am I? (2)
  4. floats in msp
  5. notes from NAB
  6. Force Sensitive Resistors? (2)
  7. cliqs & klocs goweway!
  8. the BBQ object (of desire)
  9. sensor question, continued
 10. messages to max and dsp
 11. Soundbeam (was Sensor question)

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

Date:    Tue, 20 Apr 1999 21:46:07 PDT
From:    Nathan Chase 
Subject: Full Screen Movieplus & Virtual Scratch

I'm curious to know if anyone has had any luck getting the Rokeby
(sp?) object "movieplus" to do warping full-screen (640x480) with a
video capture board? The Miro DC30 seems to output the video fine,
but when any of the scaling, warping, rotation, etc. is applied, you
either get minimal line distortion or nothing at all. When using just
quicktime on screen, the warping effects seem fine. Any ideas?

I'm also cleaning up my "virtual record scratching" patch that I
posted info about a few days ago with comments and so forth due to
the great response I recieved. I'll probably end up putting it up on
node.net's ftp soon.

Thanks-
Nathan

*********************************************
**nchase@stetson.edu                       **
**Steston University - Digital Arts/CS     **
**http://www.stetson.edu/departments/digart**
*********************************************

_______________________________________________________________
Get Free Email and Do More On The Web. Visit http://www.msn.com

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

Date:    Tue, 20 Apr 1999 22:35:19 -0700
From:    David Zicarelli 
Subject: Re: where max messages index & glossary?

Roland Cahen & Ruth Sefton-Green  write:

> Where can we find all these messages together ?

Messages to the DSP object are found, where they should be,
in their own section at the end of the MSP manual. There are also
dsp driver messages found in the driver-specific sections of the
Audio Input and Output chapter. Messages to the Max
object are found in the Max 3.5 manual.

David Z.

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

Date:    Tue, 20 Apr 1999 22:38:13 -0700
From:    David Zicarelli 
Subject: Re: where am I?

Kevin Walker  asks:

>I'm trying to write an external with local scoping rules (sort of like
>_send and _recieve, but with names shared only with a patcher).  How can an
>object, at creation time, tell where it's at (i.e. which patcher or
>subpatcher it's contained in)?  Is there a pointer to a window or patcher
>structure accessible through the symbol table (gensym("#P"), or something
>like that)?  Is there another strategy for acheiving local scoping?

At object instance creation time, gensym("#P")->s_thing points to your
object's owning patcher. At this same time, gensym("#B")->s_thing
points to your non-user-interface object's box. If you're a user
interface object, you know both of these things since you
create the box and you're passed the patcher.

So that's where you are.

David Z.

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

Date:    Tue, 20 Apr 1999 22:57:59 -0700
From:    David Zicarelli 
Subject: Re: floats in msp

Michael McNicholas  writes:

>I am wondering how long a float is in MSP (been assuming it is  32 bits)
>and (excuse my inexperience) how many bits are for the exponent (asumming
>4). If people have any info on the floats in MSP or any suggestions, I
>would appreciate any tips.

Uh, if you're actually writing the objects you would know your
perform routine gets passed a vector of floats. If you really
want to know how long a float is (it's always 32 bits but let's
assume you don't know that), do a sizeof() on something
pointed to by the vector which will return the number of bytes
occupied by the item (4 in this case).

The format of an IEEE 754 float uses bit 31 as the sign bit,
bits 23-30 as the exponent, and bits 0-22 as the significand.

btw "significand" is one of my favorite words.

>I have been masking each number by -1024 to remove the exponent bits and
>high frequency noise. The affect of the operation is distorion for complex
>tones and quasi ringmodulation for simple tones.

I've observed that just about any crude DSP operation will produce
distortion and quasi ring modulation, but this has to be one of
the crudest I've heard of. Good luck getting a patent, son!

David Z.

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

Date:    Tue, 20 Apr 1999 22:58:49 -0700
From:    Alex Stahl 
Subject: notes from NAB

I saw a couple of things at the NAB exhibit this week that may be of
interest to travelling Max/MSP users, Real Soon Now...

Digigram says that their forthcoming VXpocket PCcard will support
simultaneous SPDIF input and output via Sound Manager and ASIO drivers. The
price is much lower than the existing unidirectional card but it's still
around US$800 and it's not expected until at least July. Their PCXpocket
card v.3 has an onboard DSP chip and a timecode input but the person I
spoke with said they are not planning to write Mac drivers for that model.

Magma is working on a "very compact, very portable, under $500" 2-slot PCI
expansion chassis which also connects to a Powerbook PCcard slot. No
shipping date was mentioned, but they said they are planning on qualifying
it with MOTU 2408 and Korg 1212 cards. The currently available 4-slot unit
costs as much as a base model G3 desktop and is almost as big, so I've felt
that lugging a desktop and an LCD monitor is a better way to go. But if the
new small chassis lives up to its description it may be a decent solution
for multichannel I/O on the road.

For what it's worth, someone else showed an ADAT-Lightpipe format repeater
which makes 50 meter fiber runs possible. And of course, there was
CopterVision, a lot of really cool looking antennas, and a guy who will
launch your satellite for less. The future of television engineering is
digital, and it isn't pretty.

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

Date:    Wed, 21 Apr 1999 02:23:30 -0400
From:    jmw/cmu 
Subject: Force Sensitive Resistors?

I'm looking for a source of FSR & linear potentiometers ( ribbon
controllers).
I did a search but only found some large industrial mnaufacturers.
Any help would be appreciated.

jmw

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

Date:    Wed, 21 Apr 1999 09:18:53 +0200
From:    Roland Cahen & Ruth Sefton-Green 
Subject: cliqs & klocs goweway!

What kind of solution can you find to get rid of digital cliks ?
Is there an existing anticlick MSP object ?
One which would detect a steeper amplitude slope variation in a short delay
preferably in a quiet moment ?
or something like this
At least how can a line~ could be used for this purpose

How can you use a line~ for smoothing ?

Roland

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

Date:    Wed, 21 Apr 1999 10:42:08 +0200
From:    Michael Wieser 
Subject: Re: Force Sensitive Resistors?

Hi!

Where? In Europa?

If you would do some craftwork (?) put some pieces of the antistatic foamed
plastic, which is used to transport Integrated Circuits between 2
electrodes. If you press onto the 2 electrodes, the resitance of the
antstatic-plastics goes down. Its not a 0,05% solution, but it works fine
(and cheap)

hth

>I'm looking for a source of FSR & linear potentiometers ( ribbon
>controllers).
>I did a search but only found some large industrial mnaufacturers.
>Any help would be appreciated.
>
>jmw
>
>
Michael Wieser
m.k.w@magnet.at

Service and Audiodesign

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

Date:    Wed, 21 Apr 1999 06:43:42 -0500
From:    Gregory Taylor 
Subject: the BBQ object (of desire)

>From:    Peter Nyboer 

>Peter "Is BBQ off-topic?" Nyboer

(with apologies to our wonderful vegetarian and vegan colleagues)

The tradition in my family has, for years, been to find excuses to
make a journey from my ancestral home base in Grayson County,
KY to some destination which allows one to stop off in Owensboro,
Kentucky (it would appear that my 75-year-old mom's current fave
is a jaunt with the local Senior Citizen's club to blow some quarters
at the riverboat casino, oddly enough) at The Moonlite Bar-B-Q Inn
(on West Parrish [checks palm pilot....] 2840 West Parrish). This is
Bar-B-Q of the NON-dry variety, but hubba hubba.

So, what does the Bar-B-Q object or Pluggo module do?

Generate greasy backbeats?
Do the pulled pork thang on an input stream?
Delay the input N hours for slow roasting?
Greatly magnify any noise components (to simulate the
sound of the signal being rubbed with spices)?

Man....*Never* type this stuff before 7 AM when you're miles
from the restaurant you're reminiscing about....

far from home (in more ways than this),
Gregory

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

Date:    Wed, 21 Apr 1999 12:14:49 +0100
From:    Bob Gluck 
Subject: sensor question, continued

Thanks for the many suggestions regarding sensors for vocal data. There were
a few
questions about why no microphone. Its because I'd like to send data at some
points without making any sounds, but simply via mouth cavity shape changes.
I
guess that I could work around this by simply turning down the amplitude at
those
points (!) The video options sound a bit intrusive for live performance (or
am I
missing something about their use), but are pretty interesting. Maybe the
simplest
option is just to go the MSP vocoder direction--which I have planned to also
do.
Further thoughts--on or off list (I don't know if this is interesting to
people)
are welcomed.

Bob Gluck

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

Date:    Wed, 21 Apr 1999 10:39:11 -0600
From:    Kevin Walker 
Subject: Re: where am I?

David Zicarelli  writes:

>At object instance creation time, gensym("#P")->s_thing points to your
>object's owning patcher. At this same time, gensym("#B")->s_thing
>points to your non-user-interface object's box. If you're a user
>interface object, you know both of these things since you
>create the box and you're passed the patcher.

Great -- thanks.  Two more questions:

(1) Do the patcher structs stay put in memory?  (I suspect the answer is
yes but I thought I'd check anyway.)  More specifically, if an object wants
to know, at object creation time, whether it's living in the same patcher
window as another previously created instance in the same class, can it
compare gensym("#P")->s_thing with a previously stored value of
gensym("#P")->s_thing?  Will this work even if the second object is created
interactively long after the first object was created (as opposed to both
of the objects being created while the patcher is built from a file)?

(2) I think I know how to navigate down through contained subpatchers, but
how about navigating up through containing patchers?  Does

  ((Patcher*)(gensym("#P")->s_thing))->p_pushed

always point to the containing patcher (if there is one), or is this true
only while the patcher is being constructed from a file/binbuf, or is it
never true?

Thanks, very much and in advance, for any light shed on this subject.

Kevin

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

Date:    Wed, 21 Apr 1999 09:55:16 +0100
From:    Christopher Dobrian 
Subject: messages to max and dsp

Roland Cahen & Ruth Sefton-Green Subject: where max messages index & glossary?
>...Where can we find all these messages together ?

Messages to max are on pp. 6-7 of the "Max Addendum 3.5".
Messages to dsp are on p. 290 of "MSP.pdf" (v. 1.1).

The "playthrough" message is not there because it was added by David Z.
after the documentation, in response to the ingenious G3 change by Apple.

There may well be other messages to max and dsp not documented, but I don't
know 'em.

--Chris

                                   ----------
  Christopher Dobrian / Department of Music / University of California,
Irvine
  Phone: (949) 824-7288 / Fax: (949) 824-4914 /
http://www.arts.uci.edu/dobrian

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

Date:    Wed, 21 Apr 1999 20:52:23 +0100
From:    Trond Lossius 
Subject: Re: where max messages index & glossary?

In the latest update of MSP there is a chapter on messages to DSP (p.
290) listing messages understood by DSP. There are a few additons to
this list. First there are some messages that only work with a certain
sound card. These are generally described in the Audio Input and Output
section of the manual. With the latest update of MSP (6) this message
was added  (described in the READ ME file):

; dsp driver playthrough 1
; dsp driver playthrough 0

Turns audio thru on (1) or off (0). As far as I have understood, this
message will only work if you are using Sound Manager.

You might want to know that Acrobat Reader can search the text (use Find
from the Tools menu).

Trond L.

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

Date:    Thu, 22 Apr 1999 07:16:54 +1000
From:    David Rodger 
Subject: Re: Soundbeam (was Sensor question)

Gordon wrote:
>Hi -- I missed the beginning of this thread, but thought I would chime in:
>I have used the SOUNDBEAM (which is a sonar-based system) with physically
>handicapped kids.  It can indeed be set at a high enough sensitivity that
>it can  respond to the mouth cavity -- if I remember correctly, the low end
>of its range is about 15cm (adjustable to up to 8m), at which it can send
>7-bit continuous controller data.  Be forewarned, though, that this is only
>gives you a reflection of distance, not volume, and won't distinguish
>between teeth, tongue, etc.

Since Gordon didn't mention it...

http://www.soundbeam.co.uk

David Rodger:  Audio Engineer, RLSS Lifeguard Trainer, General Curmudgeon
  mailto:auricle@alphalink.com.au   http://farben.latrobe.edu.au/motion
http://www.alphalink.com.au/~auricle  http://www.alphalink.com.au/~adzohu
=========================================================================
      Stop the bloat: no auto-HTML'd e-mail, no ms-tnef, no .vcf

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

End of MAX Digest - 20 Apr 1999 to 21 Apr 1999 (#1999-122)
**********************************************************