Timeline still buggy


    Jan 08 2007 | 2:41 pm
    I would really like to use timeline but in the past it was so buggy that I
    gave up. This morning I tried it again assuming that it had been fixed.
    The very first thing I tried caused max to crash.
    I opened the tutorial and dragged the envelope labeled "volume" a few ticks
    to the right. The crash has happen on each of the five times I retried it.
    I also tried pasting a new list into one of the message boxes at 8000. I
    reported this several years ago and it still doesn't work.
    Cheers
    Gary Lee Nelson
    Oberlin College
    www.timara.oberlin.edu/GaryLeeNelson

    • Jan 08 2007 | 4:28 pm
      same with me: I tried edetonate some weeks ago and gave up because I
      could not navigate thru an imported MIDI file.
      falk
      Falk
      Am 08.01.2007 um 15:41 schrieb Gary Lee Nelson:
      > I would really like to use timeline but in the past it was so buggy
      > that I
      > gave up. This morning I tried it again assuming that it had been
      > fixed.
      > The very first thing I tried caused max to crash.
      >
      > I opened the tutorial and dragged the envelope labeled "volume" a
      > few ticks
      > to the right. The crash has happen on each of the five times I
      > retried it.
      >
      > I also tried pasting a new list into one of the message boxes at
      > 8000. I
      > reported this several years ago and it still doesn't work.
      >
      > Cheers
      > Gary Lee Nelson
      > Oberlin College
      > www.timara.oberlin.edu/GaryLeeNelson
      >
      >
    • Jan 08 2007 | 9:20 pm
      If you treat timeline like a handicapped friend (be glad about the
      things he CAN do), you'll get a lot out of it. You need to know its
      idiosyncrasies to make it work for you, though. I'm happy he's around.
      Speaking about idiosyncrasies, I can report that detonate still has
      its own too. Try to create entries for track 0 and track 33, for
      example; the limit should be 1 and 32.
      Georg
      On Jan 8, 2007, at 3:41 PM, Gary Lee Nelson wrote:
      > I would really like to use timeline but in the past it was so buggy
      > that I
      > gave up. This morning I tried it again assuming that it had been
      > fixed.
      > The very first thing I tried caused max to crash.
      >
      > I opened the tutorial and dragged the envelope labeled "volume" a
      > few ticks
      > to the right. The crash has happen on each of the five times I
      > retried it.
      >
      > I also tried pasting a new list into one of the message boxes at
      > 8000. I
      > reported this several years ago and it still doesn't work.
      >
      > Cheers
      > Gary Lee Nelson
      > Oberlin College
      > www.timara.oberlin.edu/GaryLeeNelson
      >
      >
    • Jan 08 2007 | 10:44 pm
      I've run into some of these weird problems with timeline too. Looks like a great idea but there's a lot of crashes so it's unnerving at best to use it...
      I'd love to see a version using jit.cellblock or even LCD that lets you indicate what's going on based upon graphical indicators. Maybe multiple "tracks", each with its own LCD, with a "scrub" bar that could be moved by hand or automatically (or mtr-recorded). It wouldn't have the same functionality as timeline, but I can imagine multiple colors meaning different messages or commands.
      Maybe jit.matrix (in an editable window) could also do this, or some kind of multislider configuration, or a bpfunction editor. Essentially, a collection of tracks of graphically-controlled messages that play / send messages to whatever you want. Could be neat.
      --CJ
    • Jan 08 2007 | 11:11 pm
      I suggest that if there's no viable solution in Max 5.0, those who
      are interested in a nice timeline object start collecting money
      Wikipedia style and contract a programming whiz to do the work.
      Lately, I had the pleasure working with Emmanuel Jourdan's js
      function object. Something similar could probably also be realized
      for timeline. If we all give $50, we might be able to raise a
      considerable amount.
      What does everybody think?
      Georg
      On Jan 8, 2007, at 11:44 PM, Seejay James wrote:
      >
      > I've run into some of these weird problems with timeline too. Looks
      > like a great idea but there's a lot of crashes so it's unnerving at
      > best to use it...
      >
      > I'd love to see a version using jit.cellblock or even LCD that lets
      > you indicate what's going on based upon graphical indicators.
      > Maybe multiple "tracks", each with its own LCD, with a "scrub" bar
      > that could be moved by hand or automatically (or mtr-recorded). It
      > wouldn't have the same functionality as timeline, but I can imagine
      > multiple colors meaning different messages or commands.
      >
      > Maybe jit.matrix (in an editable window) could also do this, or
      > some kind of multislider configuration, or a bpfunction editor.
      > Essentially, a collection of tracks of graphically-controlled
      > messages that play / send messages to whatever you want. Could be
      > neat.
      >
      > --CJ
    • Jan 08 2007 | 11:30 pm
      Im down for $50.. As long as it uses jitter @ attributes :)
      On Jan 8, 2007, at 6:11 PM, Georg Hajdu wrote:
      > I suggest that if there's no viable solution in Max 5.0, those who
      > are interested in a nice timeline object start collecting money
      > Wikipedia style and contract a programming whiz to do the work.
      > Lately, I had the pleasure working with Emmanuel Jourdan's js
      > function object. Something similar could probably also be realized
      > for timeline. If we all give $50, we might be able to raise a
      > considerable amount.
      >
      > What does everybody think?
      >
      > Georg
      >
      > On Jan 8, 2007, at 11:44 PM, Seejay James wrote:
      v a d e //
      www.vade.info
      abstrakt.vade.info
    • Jan 09 2007 | 12:10 am
    • Jan 09 2007 | 12:46 am
      I'm down as long as its an open system. the maxer needs to be able
      to add her own features like repeat, reverse, quantize,randomize
      etc... so I guess What I'm saying it can't just have a record and
      playback. its gotta integrate. (the difference between presets and
      pattr) a static one would be kind of useless.
      gotta run.
    • Jan 09 2007 | 8:59 am
    • Jan 09 2007 | 9:45 am
      The thought that MaxMSP 5.0 *won't* include a significant upgrade to the timeline object is too painful to consider. I would *love* an upgraded version, and I'm sure it's high on c74's "must have" list. I have a feeling that the deeeeep silence surrounding v5.0 is a good indication that they're really going above and beyond to make it something special. The whole graphical programming idea for music seems to really be taking hold (Reaktor, Audiomulch, Bidule, etc.), so I'm sure c74 wants to make their next major upgrade really shine, and to widen the gap between them and all these other apps -- I mean, I realize the gap is already pretty wide, since the integration of synthesis, processing, midi, and logic in MaxMSP is a far stretch beyond the competition, but still...
      (As an example of how far they *might* be going, some may recall the rumors of drool-worthy features like compositing in the main patcher window! "ooooh" --Merv Griffin-style. The more time I spend at the computer, the more I realize that interface design and user control are pretty lame in most commercial music software. And since Max is all about spurring the user's imagination, I'm sure c74 will give us lots to play with in order to help remedy the situation.)
      Anyway, I'd probably throw-down for a snazzy openGL timeline object. But I suspect c74 will provide one before we could actually get a 3rd-party one built. Personally, I think we should pool our money to pay the PWGL developers to incorporate OSC... then we'd have graphical options AND a super-hot score editor (which includes graphical notation as well, btw).
      J.
    • Jan 09 2007 | 10:03 am
      Seems I was wrong on this one.
      > solutions like Iannix
      Georg
    • Jan 09 2007 | 10:22 am
      hey! That looks promising... time to mess about!
      J.
    • Jan 09 2007 | 10:29 am
      Wow - maybe it's time to learn some of that OpenGL I've been hearing so much about :)
      Yeah I'd like to keep this thread alive too. I also had contemplated LCD, sounds like you guys got pretty far with it. It could still come in handy with some stuff I guess. Interested to see what you ended up with.
      Detonate could be nicely used as a timeline, especially if the notes were used as triggers, sending messages, storing numbers, etc. Maybe a track per pitch, with assignable behavior by velocity? Not to mention the other values.
      A concurrent, parallel Detonate (or multiple ones for that matter) could have the same notes / durations. Changing the velocity on these would control the level or type of effect in the main timeline sequence, depending on the value held by the "notes" in it---if the values are numbers it provides interpolation or scaling, if they are messages it changes the particular message sent (play sample2.aiff, play mtr / seq), or it turns on and off the “notes” (either the events happen or they don't). Lots of design possibilities and considerations there, with the advantage of the detonate UI and playback capabilities.
      For the messages that are in either of these examples: Common message “parts” could be stored in multiple drop-downs, so the user can build full messages piecemeal--take this action, on this name / symbol, at this level, etc. Combinations could then be stored too, in a coll and a drop-down.
      With a bit of mousestate and some transparent buttons you can make any object draggable (maybe hold down shift while in drag mode, or the reverse). Then you could do a fair bit with panels that “size themselves” automatically by setting the event’s duration / beat length. Choose common note lengths and drag them onto the tracks, with lots of preset patterns and filling functions, and a snap-to-grid function (use split object for the number of pixels around the nearest gridline, and an if-else to snap the panel and update the cursor? use modulus for the screen grid coordinates, based upon resolution and zoom level?).
      When you click a panel / event, you could edit the current number / list / message(s) it contains (a master editor panel at bottom switches to the current panel clicked). Also a master setter for the whole track, or whichever events are enabled to receive master track commands. The most recent screen coordinates of dragged or generated panels are stored for playback.
      Each track has independent playback rates; the note timings are determined using panel size and the screen pixel coordinates; there’s a slider above each track as an indicator and for scrubbing; there’s a range bar for looping; there’s a main level scaler for events that are numbers / lists; there’s maybe 6 levels of 2X zoom, out to about 4800 pixels horizontally; and there’s tons of presets / whatevers for all these… this sounds relatively doable, and would provide a lot of possibilities. Now let me just go and brew another pot…
      just thinkin’ out loud, so if you got this far, my appreciation
      C
    • Jan 09 2007 | 10:36 am
      I would like to chip in. I am desperate for a reliable "Timeline"
      environment. Let me know how to help (specifications etc),
      regards Pere Josep
      On 09/01/07, Georg Hajdu wrote:
      >
      > I suggest that if there's no viable solution in Max 5.0, those who
      > are interested in a nice timeline object start collecting money
      > Wikipedia style and contract a programming whiz to do the work.
      > Lately, I had the pleasure working with Emmanuel Jourdan's js
      > function object. Something similar could probably also be realized
      > for timeline. If we all give $50, we might be able to raise a
      > considerable amount.
      >
      > What does everybody think?
      >
      > Georg
      >
      > On Jan 8, 2007, at 11:44 PM, Seejay James wrote:
      >
      > >
      > > I've run into some of these weird problems with timeline too. Looks
      > > like a great idea but there's a lot of crashes so it's unnerving at
      > > best to use it...
      > >
      > > I'd love to see a version using jit.cellblock or even LCD that lets
      > > you indicate what's going on based upon graphical indicators.
      > > Maybe multiple "tracks", each with its own LCD, with a "scrub" bar
      > > that could be moved by hand or automatically (or mtr-recorded). It
      > > wouldn't have the same functionality as timeline, but I can imagine
      > > multiple colors meaning different messages or commands.
      > >
      > > Maybe jit.matrix (in an editable window) could also do this, or
      > > some kind of multislider configuration, or a bpfunction editor.
      > > Essentially, a collection of tracks of graphically-controlled
      > > messages that play / send messages to whatever you want. Could be
      > > neat.
      > >
      > > --CJ
      >
      >
      --
      Course Leader
      Msc Creative and Computational Sound
      Creative Technologies
      Portsmouth University
      Eldon Building
      Winston Churchill Avenue
      Portsmouth PO1 2DJ
      00 44 23 92 848484
      www.port.ac.uk/courses/coursetypes/postgraduate/MScCreativeAndComputationalSound/
      www.perevillez.com
      www.centuryofnoise.com
    • Jan 09 2007 | 11:54 am
      Quote: pvillez@gmail.com wrote on Tue, 09 January 2007 11:36
      ----------------------------------------------------
      > I would like to chip in. I am desperate for a reliable "Timeline"
      > environment. Let me know how to help (specifications etc),
      >
      > regards Pere Josep
      I don't think max is ready to be used as a real sequencer and event editing solution. I started programming my own in Java a few months ago. It communicates with max via OSC, which works very nice.
      Mattijs
    • Jan 10 2007 | 2:33 am
      Gary (and others on Mac OS),
      You might want to look at iCE Tools as an alternative to timeline.
      It's a different paradigm, but ice.lattice is (a) simple, (b)
      reliable, and (c) stable.
      iCE Tools costs more than the $50 ante people have been positing in
      this thread, but its price is, frankly, more realistic given the work
      involved. As f.e has discovered, this sort of thing is not a trivial
      task. To give you an idea of just how much work was involved, note
      that ice.lattice needed almost 3 years development to market.
      I will respond to the question about availability for Windows in the
      thread in which the question was explicitly asked ("iCE sequencer
      opinions").
      Best,
      Peter
      On 8-Jan-2007, at 9:41, Gary Lee Nelson wrote:
      > I would really like to use timeline but in the past it was so buggy
      > that I
      > gave up. This morning I tried it again assuming that it had been
      > fixed.
      > The very first thing I tried caused max to crash.
      -------------- http://www.bek.no/~pcastine/Litter/ -------------
      Peter Castine +--> Litter Power & Litter Bundle for Jitter
      Universal Binaries on the way
      iCE: Sequencing, Recording &
      Interface Building for |home | chez nous|
      Max/MSP Extremely cool |bei uns | i nostri|
    • Jan 10 2007 | 3:39 am
      Peter, thanks for the information, I had considered ICE as it looks (on the
      surface) like the kind of thing I could use, but there is mention of
      standalone licensing restrictions on the website. What would these be?
      regards Pere
      On 10/01/07, Peter Castine wrote:
      >
      > Gary (and others on Mac OS),
      >
      > You might want to look at iCE Tools as an alternative to timeline.
      > It's a different paradigm, but ice.lattice is (a) simple, (b)
      > reliable, and (c) stable.
      >
      > iCE Tools costs more than the $50 ante people have been positing in
      > this thread, but its price is, frankly, more realistic given the work
      > involved. As f.e has discovered, this sort of thing is not a trivial
      > task. To give you an idea of just how much work was involved, note
      > that ice.lattice needed almost 3 years development to market.
      >
      > I will respond to the question about availability for Windows in the
      > thread in which the question was explicitly asked ("iCE sequencer
      > opinions").
      >
      > Best,
      > Peter
      >
      > On 8-Jan-2007, at 9:41, Gary Lee Nelson wrote:
      > > I would really like to use timeline but in the past it was so buggy
      > > that I
      > > gave up. This morning I tried it again assuming that it had been
      > > fixed.
      > > The very first thing I tried caused max to crash.
      >
      > -------------- http://www.bek.no/~pcastine/Litter/ -------------
      > Peter Castine +--> Litter Power & Litter Bundle for Jitter
      > Universal Binaries on the way
      > iCE: Sequencing, Recording &
      > Interface Building for |home | chez nous|
      > Max/MSP Extremely cool |bei uns | i nostri|
      > http://www.dspaudio.com/ http://www.castine.de
      >
      >
      >
    • Jan 10 2007 | 6:19 am
      Pattr sequencer!
      On Jan 9, 2007, at 9:33 PM, Peter Castine wrote:
      > Gary (and others on Mac OS),
      >
      > You might want to look at iCE Tools as an alternative to timeline.
      > It's a different paradigm, but ice.lattice is (a) simple, (b)
      > reliable, and (c) stable.
      >
      > iCE Tools costs more than the $50 ante people have been positing in
      > this thread, but its price is, frankly, more realistic given the
      > work involved. As f.e has discovered, this sort of thing is not a
      > trivial task. To give you an idea of just how much work was
      > involved, note that ice.lattice needed almost 3 years development
      > to market.
      >
      > I will respond to the question about availability for Windows in
      > the thread in which the question was explicitly asked ("iCE
      > sequencer opinions").
      >
      > Best,
      > Peter
      >
      > On 8-Jan-2007, at 9:41, Gary Lee Nelson wrote:
      >> I would really like to use timeline but in the past it was so
      >> buggy that I
      >> gave up. This morning I tried it again assuming that it had been
      >> fixed.
      >> The very first thing I tried caused max to crash.
      >
      > -------------- http://www.bek.no/~pcastine/Litter/ -------------
      > Peter Castine +--> Litter Power & Litter Bundle for Jitter
      > Universal Binaries on the way
      > iCE: Sequencing, Recording &
      > Interface Building for |home | chez nous|
      > Max/MSP Extremely cool |bei uns | i nostri|
      > http://www.dspaudio.com/ http://www.castine.de
      >
      >
      v a d e //
      www.vade.info
      abstrakt.vade.info
    • Jan 10 2007 | 10:19 am
    • Jan 10 2007 | 12:57 pm
      On Jan 10, 2007, at 1:19 AM, vade wrote:
      > Pattr sequencer!
      In a very simple way, you can already do this. Use an [mtr] object
      to record you preset changes for [pattrstorage]. Playback at will.
      I have done this to build layers for a recording of a composition.
      Worked like a charm.
      -------------------
      Nathan Wolek, PhD --- nwolek@stetson.edu
      Assistant Professor of Music Technology
      Stetson University - DeLand, FL
    • Jan 10 2007 | 2:20 pm
      I considered mtr as an alternative to timeline but I cannot see how mtr can
      be made to participate in a pattr. Mtr is not an UI object. Do you have an
      example?
      BTW. I am having great success using textedit with pattr. With a small
      wrapper I have made a kind of qlist that is more easily edited and allows me
      to specify action times as well as delta times. As soon as I deliver my
      current piece I'll make up a small demo.
      Cheers
      Gary Lee Nelson
      Oberlin College
      www.timara.oberlin.edu/GaryLeeNelson
      On 1/10/07 7:57 AM, "Nathan Wolek" wrote:
      > On Jan 10, 2007, at 1:19 AM, vade wrote:
      >> Pattr sequencer!
      >
      > In a very simple way, you can already do this. Use an [mtr] object
      > to record you preset changes for [pattrstorage]. Playback at will.
      > I have done this to build layers for a recording of a composition.
      > Worked like a charm.
      >
      > -------------------
      > Nathan Wolek, PhD --- nwolek@stetson.edu
      > Assistant Professor of Music Technology
      > Stetson University - DeLand, FL
      > http://www.nathanwolek.com
      >
      >
    • Jan 10 2007 | 4:34 pm
      On 9-Jan-2007, at 22:39, Pere Josep Villez wrote:
      > Peter, thanks for the information, I had considered ICE as it looks
      > (on the surface) like the kind of thing I could use, but there is
      > mention of standalone licensing restrictions on the website. What
      > would these be?
      The page at the Kagi store has a Contact link specifically to answer
      this question. But since the question has been asked here, I'll
      answer it on list (not for the first time, probably not the last!-)
      It's basically a formality where you say to DSPA "I want to be able
      to build standalones with iCE Tools." That's all. DSPA requires an
      additional license, encompassing an assurance not to directly compete
      with DSPA's sequencer products. There are no additional license fees
      involved.
      Hope this helps,
      Peter
      -------------- http://www.bek.no/~pcastine/Litter/ -------------
      Peter Castine +--> Litter Power & Litter Bundle for Jitter
      Universal Binaries on the way
      iCE: Sequencing, Recording &
      Interface Building for |home | chez nous|
      Max/MSP Extremely cool |bei uns | i nostri|
    • Jan 10 2007 | 6:43 pm
      I've done the same things with the text object instead of mtr. But it
      doesn't seem like you can as easily scroll content in a textedit box,
      particularly when you deal with hundreds of lines.
      Georg
      On Jan 10, 2007, at 3:20 PM, Gary Lee Nelson wrote:
      > I considered mtr as an alternative to timeline but I cannot see how
      > mtr can
      > be made to participate in a pattr. Mtr is not an UI object. Do
      > you have an
      > example?
      >
      > BTW. I am having great success using textedit with pattr. With a
      > small
      > wrapper I have made a kind of qlist that is more easily edited and
      > allows me
      > to specify action times as well as delta times. As soon as I
      > deliver my
      > current piece I'll make up a small demo.
      >
      > Cheers
      > Gary Lee Nelson
      > Oberlin College
      > www.timara.oberlin.edu/GaryLeeNelson
      >
      >
      > On 1/10/07 7:57 AM, "Nathan Wolek"
      > wrote:
      >
      >> On Jan 10, 2007, at 1:19 AM, vade wrote:
      >>> Pattr sequencer!
      >>
      >> In a very simple way, you can already do this. Use an [mtr] object
      >> to record you preset changes for [pattrstorage]. Playback at will.
      >> I have done this to build layers for a recording of a composition.
      >> Worked like a charm.
      >>
      >> -------------------
      >> Nathan Wolek, PhD --- nwolek@stetson.edu
      >> Assistant Professor of Music Technology
      >> Stetson University - DeLand, FL
      >> http://www.nathanwolek.com
      >>
      >>
      >
      >
      >
    • Jan 10 2007 | 6:57 pm
      Two questions prompted by this thread:
      1) how much functional example code is supplied alongside iCE Tools?
      2) what do we know about Max 5.0? Will we hear anything at NAMM or is
      it far too soon?
      -A
    • Jan 10 2007 | 7:16 pm
      Perhaps i should have said
      Pattr Timeline!
      There is a bit of a difference (perhaps in my head) between the two.,
      being able to store not only your presets, but the time delta between
      them, etc. Yes, you could prob. finagle something, but there would be
      niceties of having something in the pattr family native.
      Anyway.
      On Jan 10, 2007, at 7:57 AM, Nathan Wolek wrote:
      > On Jan 10, 2007, at 1:19 AM, vade wrote:
      >> Pattr sequencer!
      >
      > In a very simple way, you can already do this. Use an [mtr] object
      > to record you preset changes for [pattrstorage]. Playback at
      > will. I have done this to build layers for a recording of a
      > composition. Worked like a charm.
      >
      > -------------------
      > Nathan Wolek, PhD --- nwolek@stetson.edu
      > Assistant Professor of Music Technology
      > Stetson University - DeLand, FL
      > http://www.nathanwolek.com
      >
      >
      v a d e //
      www.vade.info
      abstrakt.vade.info
    • Jan 10 2007 | 7:32 pm
      Scrolling works by selecting text and dragging to the line you need. I am
      only dealing with 20-30 lines maximum. Saving segments in a pattrstorage.
      On 1/10/07 1:43 PM, "Georg Hajdu" wrote:
      > I've done the same things with the text object instead of mtr. But it
      > doesn't seem like you can as easily scroll content in a textedit box,
      > particularly when you deal with hundreds of lines.
      >
      > Georg
      Cheers
      Gary Lee Nelson
      Oberlin College
      www.timara.oberlin.edu/GaryLeeNelson
    • Jan 10 2007 | 9:21 pm
      Nathan Wolek skrev:
      > On Jan 10, 2007, at 1:19 AM, vade wrote:
      >> Pattr sequencer!
      >
      > In a very simple way, you can already do this. Use an [mtr] object to
      > record you preset changes for [pattrstorage]. Playback at will. I
      > have done this to build layers for a recording of a composition.
      > Worked like a charm.
      That's what I do too. To me this is by far the most intuitive way of
      working with structures that change over time. Pattr friggin rules for this.
      Andreas.
    • Jan 10 2007 | 9:29 pm
      how about using jit.cellblock instead of textedit?
      each line would be a row in it, something like this:
      hth,
      nesa
    • Jan 10 2007 | 9:36 pm
      Yes, pattr seq timeline or something, but with layer flexibility. I like
      pattr a lot especially as I deal with a lot of transitional data over time.
      I agree keep it in this family of objects. Maybe easier said than done, but
      I can imagine an extension to the interpolation asoect of this class of
      objects.
      best Pere
      On 10/01/07, vade wrote:
      >
      > Perhaps i should have said
      > Pattr Timeline!
      >
      > There is a bit of a difference (perhaps in my head) between the two.,
      > being able to store not only your presets, but the time delta between them,
      > etc. Yes, you could prob. finagle something, but there would be niceties of
      > having something in the pattr family native.
      >
      > Anyway.
      >
      > On Jan 10, 2007, at 7:57 AM, Nathan Wolek wrote:
      >
      > On Jan 10, 2007, at 1:19 AM, vade wrote:
      >
      > Pattr sequencer!
      >
      >
      > In a very simple way, you can already do this. Use an [mtr] object to
      > record you preset changes for [pattrstorage]. Playback at will. I have
      > done this to build layers for a recording of a composition. Worked like a
      > charm.
      >
      > -------------------
      > Nathan Wolek, PhD --- nwolek@stetson.edu
      > Assistant Professor of Music Technology
      > Stetson University - DeLand, FL
      > http://www.nathanwolek.com
      >
      >
      >
      >
      > *v a d e //*
      >
      > *www.vade.info*
      > *abstrakt.vade.info*
      >
      >
      >
      >
      >
      >
      >
    • Jan 17 2007 | 3:15 am
      On Jan 10, 2007, at 9:20 AM, Gary Lee Nelson wrote:
      > Do you have an example?
      Sorry for the delay. As I said it is very simple. Store your
      presets then sequence them.
      ------
      Nathan Wolek, PhD
      nathan@lowkeydigitalstudio.com
      max v2;
    • Jan 17 2007 | 4:25 am
      Quote: vade wrote on Wed, 10 January 2007 11:16
      ----------------------------------------------------
      >
      > Pattr Timeline!
      >
      agreed. something that stays in the [pattr] gang.
      Jeremy you might get the 50$ per timeline seeker ;)
      i would like to see a dynamic timeline where events writen in the past will have the possibility to influence what is to come in the future. which could make a "flexible" score which's content or stucture will always stay the same but vary according to any interactive means one can think about.
      this is a nice thread , i hope idea will keep flowing .
      best,
      ko
    • Jan 17 2007 | 6:35 am
      It would be nice to use a visual paradigm. For interactive work, it's
      always nicer to know what's inside that box. I appreciated Emmanuel's
      function editor with two synchronizable objects, one great for visual
      programming, the other optimized for efficiency.
      Georg
      On Jan 17, 2007, at 4:15 AM, Nathan Wolek wrote:
      > On Jan 10, 2007, at 9:20 AM, Gary Lee Nelson wrote:
      >> Do you have an example?
      >
      > Sorry for the delay. As I said it is very simple. Store your
      > presets then sequence them.
      >
      > ------
      > Nathan Wolek, PhD
      > nathan@lowkeydigitalstudio.com
      > http://www.lowkeydigitalstudio.com
      >
      >
      > max v2;
      > #N vpatcher 10 59 464 312;
      > #P window setfont "Sans Serif" 9.;
      > #P window linecount 8;
      > #P comment 5 125 170 196617 RECORD 1) when mtr is set to record ,
      > it will record changes in the selected preset 2) be sure to choose
      > stop when you are done 3) select play and your will have your
      > changes played back;
      > #P window linecount 3;
      > #P comment 5 81 169 196617 SELECT choose number from number box or
      > name from ubumenu;
      > #P window linecount 1;
      > #P hidden newex 504 99 48 196617 loadbang;
      > #P user umenu 295 138 61 196647 1 64 154 0;
      > #X add stop;
      > #X add record;
      > #X add play;
      > #X add mute;
      > #X add unmute;
      > #X add delay 0;
      > #X add first 0;
      > #X add read;
      > #X add write;
      > #X add clear;
      > #P newex 253 138 40 196617 mtr 2;
      > #N vpatcher 20 74 620 474;
      > #P window setfont "Sans Serif" 9.;
      > #P newex 201 51 56 196617 route text;
      > #P newex 50 51 40 196617 t b s b;
      > #P newex 90 51 109 196617 pack store 1 slotname;
      > #N vpatcher 10 59 230 306;
      > #P window setfont "Sans Serif" 9.;
      > #P newex 86 125 51 196617 zl ecils 1;
      > #P newex 108 164 62 196617 prepend set;
      > #P newex 86 102 67 196617 grab 1 to_ps;
      > #P message 86 84 79 196617 getslotname $1;
      > #N comlet (int) slotnum;
      > #P inlet 86 64 15 0;
      > #N comlet (msg) set textedit;
      > #P outlet 108 186 15 0;
      > #P connect 1 0 2 0;
      > #P connect 2 0 3 0;
      > #P connect 3 0 5 0;
      > #P connect 5 1 4 0;
      > #P connect 4 0 0 0;
      > #P pop;
      > #P newobj 259 50 96 196617 p retrieveslotname;
      > #P inlet 139 31 15 0;
      > #P inlet 259 30 15 0;
      > #P inlet 50 31 15 0;
      > #P inlet 201 31 15 0;
      > #P outlet 90 73 15 0;
      > #P outlet 80 73 15 0;
      > #P outlet 259 72 15 0;
      > #P outlet 50 73 15 0;
      > #P connect 5 0 10 0;
      > #P connect 10 0 0 0;
      > #P connect 10 2 2 0;
      > #P connect 10 1 9 0;
      > #P connect 9 0 3 0;
      > #P connect 7 0 9 1;
      > #P connect 11 0 9 2;
      > #P connect 4 0 11 0;
      > #P connect 6 0 8 0;
      > #P connect 8 0 1 0;
      > #P pop;
      > #P hidden newobj 415 64 85 196617 p presetmanager;
      > #P hidden button 487 100 15 0;
      > #P hidden toggle 394 237 15 0;
      > #P hidden message 408 237 78 196617 changemode $1;
      > #P hidden message 448 119 39 196617 set $1;
      > #P comment 254 87 97 196617 **select preset**;
      > #P window setfont "Sans Serif" 12.;
      > #P user ubumenu 302 100 112 196620 0 1 1 0;
      > #X add (undefined);
      > #X prefix_set 0 0 0;
      > #X pattrmode 1;
      > #P window setfont "Sans Serif" 9.;
      > #N vpatcher 10 59 267 338;
      > #P origin -448 -339;
      > #N comlet (bang) when done;
      > #P outlet 175 238 15 0;
      > #P button 175 216 15 0;
      > #P window setfont "Sans Serif" 9.;
      > #P window linecount 0;
      > #P newex 51 122 77 196617 route slotname;
      > #N comlet to ubumenu;
      > #P outlet 126 238 15 0;
      > #N comlet (bang) fill ubumenu;
      > #P inlet 51 31 15 0;
      > #P newex 51 55 22 196617 b 1;
      > #P newex 51 102 67 196617 grab 1 to_ps;
      > #P window linecount 1;
      > #P newex 51 167 31 196617 t 0 b;
      > #P newex 98 167 55 196617 unpack 0 s;
      > #P newex 143 188 75 196617 prepend append;
      > #P newex 51 75 121 196617 t getslotnamelist 1 clear;
      > #P newex 51 142 57 196617 route done;
      > #P newex 126 209 27 196617 gate;
      > #P connect 8 0 7 0;
      > #P connect 7 0 2 0;
      > #P connect 2 0 6 0;
      > #P connect 6 0 10 0;
      > #P connect 10 0 1 0;
      > #P connect 1 0 5 0;
      > #P connect 1 1 4 0;
      > #P connect 2 1 0 0;
      > #P fasten 5 0 0 0 56 203 131 203;
      > #P connect 2 2 9 0;
      > #P connect 0 0 9 0;
      > #P connect 4 1 3 0;
      > #P connect 3 0 0 1;
      > #P connect 5 1 11 0;
      > #P connect 11 0 12 0;
      > #P pop;
      > #P hidden newobj 413 100 74 196617 p slot_manage;
      > #P window setfont "Sans Serif" 12.;
      > #P user ubumenu 192 63 75 196620 0 1 1 0;
      > #X add store;
      > #X add insert;
      > #X prefix_set 0 0 0;
      > #X pattrmode 1;
      > #P window setfont "Sans Serif" 10.;
      > #P user textedit 302 63 414 83 32896 3 10 (undefined);
      > #P window setfont "Sans Serif" 12.;
      > #P user ubumenu 191 100 76 196620 0 1 1 0;
      > #X add read;
      > #X add write;
      > #X add writeagain;
      > #X add getclientlist;
      > #X prefix_set 0 0 0;
      > #X pattrmode 1;
      > #P window setfont "Sans Serif" 9.;
      > #P hidden newex 193 253 42 196617 r to_ps;
      > #P window setfont "Sans Serif" 12.;
      > #P number 267 100 35 12 0 0 1 3 0 0 0 221 221 221 222 222 222 0 0 0;
      > #P number 267 63 35 12 0 0 1 3 0 0 0 221 221 221 222 222 222 0 0 0;
      > #P window setfont "Sans Serif" 9.;
      > #P hidden newex 236 253 248 196617 pattrstorage my_presets
      > @changemode 1 @greedy 1;
      > #X client_rect 0 0 640 240;
      > #X storage_rect 0 0 640 240;
      > #P objectname my_presets;
      > #P comment 254 50 91 196617 **store preset**;
      > #P window linecount 4;
      > #P comment 4 27 170 196617 STORE 1) select number using number box
      > 2) enter name in textbox 3) click store from ubumenu;
      > #P hidden connect 4 0 2 0;
      > #P hidden connect 13 0 2 0;
      > #P hidden connect 6 1 2 0;
      > #P hidden connect 5 0 2 0;
      > #P hidden connect 16 2 2 0;
      > #P hidden connect 18 1 17 0;
      > #P hidden connect 17 1 4 0;
      > #P hidden connect 10 0 4 0;
      > #P hidden connect 4 0 17 1;
      > #P hidden connect 16 1 7 0;
      > #P hidden connect 16 3 7 0;
      > #P hidden connect 9 0 10 0;
      > #P hidden connect 12 0 10 0;
      > #P hidden connect 14 0 13 0;
      > #P hidden connect 16 0 9 0;
      > #P hidden connect 15 0 9 0;
      > #P hidden connect 8 1 16 0;
      > #P hidden connect 3 0 16 1;
      > #P hidden connect 4 0 12 0;