From:
                                                            8/27/97 11:00 PM
Subject: MAX Digest - 26 Aug 1997 to 27 Aug
1997To: Recipients of MAX digests 

There are 4 messages totalling 187 lines in this issue.

Topics of the day:

  1. timein on MAX 3.5 (2)
  2. notes, IAC delay
  3. more on MAX timing

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

Date:    Wed, 27 Aug 1997 13:04:26 +0200
From:    Dirk Haubrich 
Subject: timein on MAX 3.5

Hello from Holland,

the timein object doesnt seem to work with OMS.
i am using STUDIO 3 and MAX 3.5 on a IIci to syncronise MAX with SMPTE.
the OMS application is receaving the timecode correctly from STUDIO 3,
but MAX TIMEIN is not reacting.
Any suggestions?

dirk

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

Date:    Wed, 27 Aug 1997 09:40:19 -0500
From:    Terry Nigrelli 
Subject: Re: notes, IAC delay

> b) There is a delay from the time the note is sent til it appears on the
> screen. This delay could have three causes-
>  Overture, (in step enter mode) processes the notes at note off time,
>  Overture takes a noticable time to do this processing (it is display,
> after all), and a little less time when the note comes in on the modem
> port.
>  This would imply a delay on the IAC buss between Max and Overture, but
> when notes are played by max and the thru feature of Overture, there is no
> noticable delay.

Peter,

One workaround might be to use two computers. Computer A running MAX
sending MIDI note messages to Computer B running Vision/MIDIKeys or
Overture.

You could also try connecting a MIDI cable from
your interface MIDI OUT to a MIDI IN on the same computer.
(disable MIDI through, of course)

It would bypass the IAC bus but there still might be a delay.

Terry Nigrelli
--

my home page: http://home.earthlink.net/~terryn/

Bay Shore Schools home page: http://www.bayshore.k12.ny.us/

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

Date:    Wed, 27 Aug 1997 16:10:17 +0200
From:    Tom Mays 
Subject: Re: timein on MAX 3.5

>>the timein object doesnt seem to work with OMS.
i am using STUDIO 3 and MAX 3.5 on a IIci to syncronise MAX with SMPTE.

I've done this successfuly (albeit twistedly) by using tcin to input the
timecode in bits and timeout to create OMS timing with it. Then you can
read the timecode with timein (since it reads OMS timing). In the=20
following patch the timein in milliseconds goes to a setclock.=20

Question: Is the OMS timing method heavier than decoding the MTC from mid=
iin?
Does it have a higher potential resolution?

tm

----

max v2;
#N vpatcher 4 326 537 730;
#P newex 308 52 45 196617 loadbang;
#P message 308 72 48 196617 format 7;
#P comment 308 284 158 196617 timein in milliseconds (at left) can then b=
e sent into a setclock to create a new clock sync that can be used by all=
 of the timing objects and Timeline;
#P comment 308 224 194 196617 OMS timing is then read with timein \, in a=
 multitude of formats \, of which milliseconds or 25 frames/sec... (see t=
imein help patch for formats).;
#P comment 115 91 113 196617 start and stop OMS timing \, or create OMS t=
iming with tcin (external MTC source). Zero resets. No need to start timi=
ng if using tcin as source!;
#P comment 251 85 39 196617 on/off;
#P comment 111 54 42 196617 locked;
#P comment 402 79 76 196617 25 frames/sec;
#P newex 308 105 154 196617 timein 7 40;
#P number 308 130 53 12 0 0 0 3;
#P comment 307 152 32 196617 hours;
#P comment 358 152 51 196617 minutes (non-Bits time code);
#P number 452 130 35 12 0 0 0 3;
#P comment 451 152 36 196617 frames;
#P comment 406 152 41 196617 seconds;
#P number 410 130 35 12 0 0 0 3;
#P number 364 130 35 12 0 0 0 3;
#P toggle 291 84 15 0;
#P newex 55 155 53 196617 timeout 7;
#P newex 55 29 114 196617 tcin =D4Studio 4=D1Modem =D5;
#P toggle 89 52 20 0;
#P toggle 78 212 15 0;
#P comment 85 336 65 196617 milliseconds;
#P number 78 314 77 12 0 0 0 3;
#P newex 78 294 60 196617 timein 0 20;
#P comment 89 279 64 196617 milliseconds;
#P comment 94 213 39 196617 on/off;
#P newex 78 354 99 196617 setclock msecs pass;
#P newex 200 294 62 196617 metro 1000;
#P message 217 273 62 196617 clock msecs;
#P toggle 200 235 15 0;
#P button 200 315 15 0;
#P newex 200 337 33 196617 timer;
#P number 200 357 48 9 0 0 0 3;
#P newex 200 252 27 196617 t i b;
#P number 10 54 46 9 0 0 0 3;
#P message 89 259 48 196617 format 0;
#P newex 89 237 45 196617 loadbang;
#P message 84 91 31 196617 start;
#P message 84 110 27 196617 stop;
#P message 84 129 14 196617 0;
#P newex 23 316 49 196617 s timems;
#P connect 41 0 40 0;
#P connect 40 0 33 0;
#P connect 33 0 32 0;
#P connect 33 1 25 0;
#P connect 33 2 26 0;
#P connect 33 3 29 0;
#P fasten 24 0 20 0 296 199 83 199;
#P connect 24 0 33 0;
#P connect 22 0 6 0;
#P connect 22 0 23 0;
#P connect 22 1 21 0;
#P fasten 21 0 24 0 94 76 296 76;
#P connect 20 0 11 0;
#P connect 20 0 17 0;
#P connect 18 0 14 0;
#P connect 17 0 0 0;
#P connect 17 0 18 0;
#P connect 13 0 10 0;
#P connect 12 0 13 0;
#P connect 11 0 7 0;
#P connect 10 0 9 0;
#P connect 10 0 9 1;
#P connect 9 0 8 0;
#P connect 7 0 13 0;
#P connect 7 1 12 0;
#P connect 5 0 17 0;
#P connect 4 0 5 0;
#P connect 2 0 23 0;
#P connect 3 0 23 0;
#P connect 1 0 23 0;
#P pop;

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

Date:    Wed, 27 Aug 1997 10:12:51 -0000
From:    Jeremy Roberts 
Subject: more on MAX timing

I continue to be somewhat frustrated with my inability to figure out
Max's handling of certain time sensitive events... I was moderately
successful accomplishing my goal of using a keyboard as a "trigger" where
a list of midikeys is established in vision, and the keyboard is simply
telling max "next". Max decides what midi event the "next" midikey will
actually be.

To do this, I used an in/out port on the studio 5 and simply had max send
the noteout to the midi cable, then told vision to look to the incoming
port (i named it "from Max to Vision"). This works well, but not well
enough for my application.

For 70% of my needs, the latency is *probably* tight enough - we'll see,
I have to test it further... but there are certain TIGHT events that the
extra 20-50ms is just too much. Vision handles this quite nicely, so for
now I'm just sending those  events as dedicated triggers directly to
Vision/midikeys... but of course I'd prefer to simply use my "next" key...

ANY thoughts from the super users is very much appreciated...

Thanks,

Jeremy

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

End of MAX Digest - 26 Aug 1997 to 27 Aug 1997
**********************************************