record~ and dsp chain

    Sep 15 2009 | 11:03 am
    Hi Maxers !
    I'm working in Max5 on a MacBook and I have some problems with record~ My problem is the following : when I use a record~ to write a buffer~ (and display it with a waveform~), as soon as I add a new MSP object, the record~ starts recording from the beginning of the buffer~, overwriting what has already been recorded. In a more complex set of patches, it doesn't start from the beginning but stops recording because I have a system to handle where (in the buffer~) it should record.
    First: is this "normal" or should I say, do you have the same behaviour ? (The simplest I tested it was to open the waveform~ help patch, start recording (without loop recording) and have another patch in which I duplicate some dspstate~ object and see what happens)
    I do know that internally, adding a new MSP object means rebuilding the whole DSP chain so it is probably tricky to dynamically add or remove MSP objects without interfering with the record~ object. However :
    Second: is there a way (a workaround) to "isolate" the record~ so I can keep it working straight and do whatever aside from it. I would like to be able to load or close audio patches without any change in the functioning of the record part.
    Is this possible ?

    • Sep 15 2009 | 1:27 pm
      When you enable append mode, it continues recording.
      _ johan
    • Sep 15 2009 | 1:53 pm
      Nice trick thank's ! I didn't know that one... It doesn't avoid clics when rebuilding the DSP chain but it does preserve the recording status and position.
      So it partly solves my problem !
      Partly because of those clics but I don't think I'll be able to get rid of those and it probably isn't that much a problem for my setup. I'll see...
      Thank's a bunch Johan !
    • Sep 15 2009 | 3:00 pm
      With a print connected to the left outlet of dspstate~ it is possible to see that the dsp is in an instant turned of and on again. All signal objects (to which it applies) go back to their initial state. Live coding is, I think, not possible without clicks that are a result of this.
      _ johan
    • Sep 15 2009 | 3:12 pm
      Yep ! Actually i knew that...
      But I had not thought it could cause record~ to start back from the beginning and of course I didn't know about the append option.
      It's not exactcly live coding I'd like to do. But more being able to dynamically launch and close patches which may contain audio objects. I'll see if I can find some compromise. Maybe poly~ which allows to mute may be an option... And I'll try to minimize such loading/closing and do it really when necessary.